JSUACT

Purpose

The JSUACT command is used to activate or inactivate the job submission function.

Usage

You can invoke the JSUACT command as a TSO command or by using a batch job that executes program EQQEVPGM. If you invoke JSUACT as a TSO command, you must allocate the EQQMLIB data set to the TSO user address apace, either by adding DD statements to the logon procedure, or by using the ALLOC command after TSO logon. In the TSO environment, error messages and trace records are sent directly to the terminal user. Messages are not delivered to indicate successful command execution.

In any case, appropriate messages are issued in the controller log to indicate whether or not job submission has been activated.

Use of the JSUACT command can be restricted using the fixed resource JSUB. The authority of the requester is verified by the subsystem name identified in the command if an AUTHDEF statement is defined for that subsystem. When SUBSYS(MSTR) is specified, all subsystems defined on the z/OS® system to which the command is directed will attempt to verify the authorization. It is possible to be rejected by one subsystem and accepted by another.

You must be defined with update authority to the JSUB resource to be able to use the JSUACT command. Resource codes are described in Customization and Tuning. Check with your scheduler administrator to confirm that you have this authority before trying to use JSUACT.

The subsystem to which you direct the command does not have to be active when the command is issued. An event will be generated and queued in CSA along with other job-tracking events. If a subsystem is not active when the command is issued, the authorization of the requester is verified by using the class name specified in the AUTHDEF statement when the subsystem was started. If the subsystem has not been started since a z/OS® IPL, no authorization verification can be performed.

Format


1?  JSUACT  ACT  (
1 yes
1 no
2  )
2?  SUBSYS (
3.1! OPCA
3.1 MSTR
3.1 subsystem name
2 )
2?  TRACE (
3.1! 0
3.1 trace level
2 )
2?  TYPE (
3.1! H
3.1 B
3.1 S
3.1 Z
2 )

Parameters

ACT (Y | N)
If you want to activate the job submission function specify Y, otherwise N.
SUBSYS (MSTR | subsystem name | OPCA)
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.

TRACE (level | 0)
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 will not generate trace records.
TYPE (B | H | S | Z)
Indicates whether the job submission must be activated or deactivated for:
  • All the workload (B)
  • z-Centric and host workstations (H)
  • host workstations (S)
  • z-Centric workstations (Z)

Examples

These two examples demonstrate how you can use the JSUACT command in TSO, or in a batch job (using the batch program EQQEVPGM).

JSUACT
Example 1 - TSO command 
ALLOC F(EQQMLIB) DA('OPC.MESSAGE.LIBRARY') SHR REUSE
 
JSUACT ACT(YES) SUBSYS(OPCB)
Example 2 - Batch job 
//JSUACT   JOB (ACCOUNT),'Deactivate',CLASS=A
//STEP1    EXEC PGM=EQQEVPGM
//STEPLIB  DD DSN=OPC.LOAD.MODULE.LIBRARY,DISP=SHR
//EQQMLIB  DD DSN=OPC.MESSAGE.LIBRARY,DISP=SHR
//EQQMLOG  DD SYSOUT=A
//SYSIN    DD *
JSUACT ACT(N) SUBSYS(OPCB)
/*