Coding Each AOF Rule Type › Command Rules › )CMD—Event Specifier of CMD Rules › JES2 Stacked Command Guidelines

JES2 Stacked Command Guidelines

Use these guidelines when you are creating CMD rules to process JES2 stacked commands:

• When CMDDELIM is set to a semicolon (;), and the issuing console is an MCS or SMCS console. Then stacked JES2 commands can only be issued in the form of: $cmd1;$cmd2;$cmd3. For example, $PI1;$TI1,C=X;$SI1.

  Each stacked JES2 command triggers an associating unique CMD rule. Or a wildcard catch all JES2 CMD rule is executed for each stacked command.

  Example

  A )CMD $* rule would execute three times (once for each command).

  A )CMD $P rule would execute once.

  A )CMD $T would execute once.

  A )CMD $S rule would execute once.

• When CMDDELIM is not set there is not any z/OS command stacking.

  When CMDDELIM is set:

  To some value other than a semicolon (;). Or is set to a semi-colon (;) and the issuing console is not an MCS or SMCS console. Then the stacked JES2 commands can be issued in the form of:

  $cmd1;cmd2;cmd3.
  

  For example:

  $PI1;TI1,C=X;SI1.
  

  The entire list of commands that is stacked together is treated as one command. This command processes by either one CMD rule that processes all JES2 commands. Or a specific CMD rule that processes the first command within the list of stacked commands.

  Example

  A )CMD $* rule would execute once for the complete stacked command.

  A )CMD $P rule would execute once for the complete stacked command.

  In both cases, code additional rule logic to interrogate the value of the cmd.text environmental variable.

  To process and automate various JES2 commands, create a catch all JES2 rule that rejects command stacking. To implement this type of control logic, see the sample rule JESSTACK in the CCLXRULS data set.