The commands below initiate a job (only MODIFY-JOB-OPTIONS refers to an existing job) and offer the option of defining a job variable for monitoring this job in the MONJV operand. In addition, a password which is required for job variable access can be specified in the JV-PASSWORD operand.
Command | Function |
ENTER-JOB | directs the system to execute a command sequence as an independent (batch) job (see also Note on ENTER-JOB) |
ENTER-PROCEDURE | starts a command sequence stored in a procedure file, as a batch job |
MODIFY-JOB-OPTIONS | modifies the parameters (logging and job monitoring) of an existing job (see also Note on MODIFY-JOB-OPTIONS) |
PRINT-DOCUMENT | initiates a print job |
SET-LOGON-PARAMETERS | initiates an interactive or batch job (see also Note on ENTER-JOB) |
TRANSFER-FILE | transfers a file from the local to the remote system, or vice versa (see “openFT” [15]) |
Table 23: Commands for defining job monitoring
Notes on the use of a MONJV
The job variable must not be protected against overwriting.
If the job variable cannot be accessed at the time of command processing, an error message is output to SYSOUT and the command is rejected. If the specified job variable does not yet exist, it is created by the system (only if the job is accepted by the system) and is made shareable.
If the job variable is protected by a password, it can be declared as a monitoring job variable only if the job submitter has already entered the password in the password table (by means of ADD-PASSWORD) or specifies it in the JV-PASSWORD operand of one of the commands listed in table 24. The JV-PASSWORD operand is ignored if no MONJV is declared.
Note on ENTER-JOB
When monitoring a repeat job, the MONJV can only contain one TSN and the associated job status at a time. Repetition of the repeat job (next job) can only be taken from the start time of the MONJV. This is especially important when the MONJV is to be used to identify a job in commands (e.g. CANCEL-JOB).
The status “$S” cannot be queried for job repetitions, since logging begins only at the start time (with “$R”). It should also be remembered that from the termination of the current job to the start of the next job, the MONJV is not protected (risk of loss of access).
Operand entries in the SET-LOGON-PARAMETERS or LOGON command at the start of the cataloged command sequence are evaluated only if the operand concerned is not specified in the ENTER-JOB operand and the job is started either at the console or by specifying DEFAULT-FROM-FILE=*YES. In all other cases a MONJV can consequently only be defined in the ENTER-JOB command.
A batch job that is to run on a remote processor can only be accessed by a MONJV if each catalog ID of the home pubset of the partner processor is entered in the MRSCAT of the processors involved.
Note on SET-LOGON-PARAMETERS
In a batch job, this is the first command in the command sequence to be processed. The batch job is submitted to the system by means of the ENTER-JOB command.
When a batch job is executed that was not started on the console or by specifying DEFAULT-FROM-FILE=*YES, the operand entries in the SET-LOGON-PARAMETERS or LOGON command are not evaluated. In this case a monitoring JV can only be declared by means of the ENTER-JOB command.
Note on MODIFY-JOB-OPTIONS
Only a privileged user (TSOS privilege) can modify the monitoring of an existing job using the MODIFY-JOB-OPTIONS command. The privileged user can terminate existing monitoring prematurely in the MONJV operand, start monitoring with the specified job variable or, in the case of existing monitoring, transfer it to the specified job variable.