JSUACT

The JSUACT instruction invokes the TSO JSUACT command, which you can use to activate or inactivate the job submission function in the z/OS® environment, in the distributed environment, or in both environments.

For a description of the keywords that you can use, see Keywords used in the JSUACT Instruction.

Table 1. Keywords used in the JSUACT Instruction
Keyword	Requirement	Multiple Values Allowed	Description
ACT()	Required	No	If you want to activate the job submission function specify YES, otherwise NO.
SUBSYS()	Optional	No	The name of the tracker the JSUACT is directed to. This parameter can be four characters in length. The first character must be alphabetic; the remaining characters must be alphanumeric. All lowercase characters are converted to uppercase. If you specify MSTR, the JSUACT command is directed to all scheduler subsystems on the z/OS® system where the JSUACT command was issued. Default is OPCA.
TRACE()	Optional	No	Event tracing indicator. When a nonzero positive number is specified, a trace entry is created for each event generated by the JSUACT command. The trace record is written to the message log file identified by ddname EQQMLOG. The record identifies the name of each receiving subsystem. The default value 0 does not generate trace records.
TYPE()	Optional		Indicates whether the job submission must be deactivated. Possible values are: H To deactivate job submission in the z/OS® environment. It is the default value. F To deactivate job submission in the distributed environment. B To deactivate job submission in both environments.

Example:

JSUACT ACT(YES) SUBSYS(OPCB) TYPE(H)

In this example the JSUACT instruction is used to activate the job submission function in the z/OS® environment.

The JSUACT instruction returns one of the following return codes:

RESULT = 0: Job submission function changed
RESULT = 8: Invalid instruction