OPUS_ONSOGS
The OPUS_ONSOGS command file allows the user to bring up an OPUS
process in the pipeline mode without using the Process Manager (PMG).
Format: @OPUS_COM:OPUS_ONSOGS process_name data_path_file [queue]
Context
Inputs
Outputs
The requested processes are started on the specified batch queue.
Each process that is started creates a log file and Process
Status File in the directory defined by the logical OPUS_HOME_DIR.
Constraints
The job limit on the specified batch queue must be set high enough
to accommodate the number of processes sent to it.
Parameters
PROCESS_NAME
The six-character process name. In OPUS there is a six character
fixed length process name requirement. This requirement is imposed
so the software can create the correct length Process Status File
name. Each process brought up using the OPUS_ONSOGS command file
must have a process resource file. The resource file has the same
six character process name and an extension of '.resource'. This
file resides in the logical directory, OPUS_DEFINITIONS_DIR.
DATA_PATH_FILE
The path file defines the pipeline directories for the process. It
also can direct the process on database updates, and polling time
information. Path files are defined by the user and placed in
OPUS_DEFINITIONS_DIR. See the OPUS User's Guide for further
information.
QUEUE
Queue is an optional parameter which specifies the desired batch queue.
Any Queue in the cluster that can access the pipeline disks may be used
to run OPUS processes. The default batch queue is the batch queue of
the CPU where the OPUS_ONSOGS command file was executed.
Examples
$ @OPUS_COM:OPUS_ONSOGS cp10dp opus_definitions_dir:blue.path nessus$batch
Starts the CP10DP process on nessus$batch with relevant pipeline
directories and other required information extracted from the path file
'opus_definitions_dir:blue.path'.