Purpose: The OSJOB command is used to start z/OS procedures. It was
designed for use by the SCC Explorer GUI to initiate actions to be executed
on the host system, but it can be used directly from the host system.
Syntax:
ENABLE OSJOB {name} ID(id) OUTDD(dd1,dd2,dd3) TCPIP PERM|NOPERM WAIT|NOWAIT MSGID|NOMSGID PING|NOPING
start-parms
DISABLE OSJOB {name} ID(id)
Comments: ENABLE OSJOB will start a z/OS procedure.
The ID is optional, but it can be used on the DISABLE
OSJOB to delete the procedure. An alphanumeric ID can be up
to 8 characters long.
OUTDD(dds) is a list of ddnames in the started procedure. Each DD in the
procedure must be allocated to a permanent z/OS data set. When the job finishes,
DIF will allocate to the data set DISP=(OLD,DELETE) and
send all records in the data set to the standard output destination.
Therefore, commands issued from a DIF console command will return the output to the console. Commands requested by the GUI will receive the command output over the TCPIP connection.
OSJOB facility tests the IP
connection using a PING request. PING requests, so
NOPING should be used in these situations.
PERM specifies the job should continue to run even if DIF
terminates.
NOWAIT specifies that DIF should not wait for the job to
finish and do the output/TCPIP functions.
MSGID indicates that the message-id should not be suppressed from the data
record. The MSGID is used by the MON-Explorer GUI
results table.
Start-parms are parameters passed to the z/OS procedure.
Examples: In the following example, the ENABLE OSJOB command starts a
z/OS procedure that executes a MONRUN program to pass the result set back to
the MON-Explorer GUI via TCPIP.
ENABLE OSJOB MONRUNX TCPIP SYSIN=DTS.R71.RULE-LIB(#MONREP),P=INCLUDE(VOLUME({volser}))