Coding Each AOF Rule Type › Command Rules › )CMD—Event Specifier of CMD Rules › Respond Rules For JES3 Command Guidelines

Respond Rules For JES3 Command Guidelines

When writing rules that respond to JES3 commands, do:

Begin the cmdverbspec event identifier string with the first character in the JESCHAR parameter string. Only the first character in JESCHAR is meaningful in a JES3 environment.

CA OPS/MVS attempts to match the command prefix with one of the JES3 system or sysplex prefixes, while processes a command.

When CA OPS/MVS, finds a match it creates a common command verb (CMD.VERB). Regardless of which command prefix was used or whether the command was abbreviated.

Use these guidelines, to write a single command rule only for each JES3 command, regardless of how it was issued.

The command verb (and CMD.VERB) consists of the real command verb with the original prefix stripped off and replaced by the first character in JESCHAR. This first character does not affect the command text itself, only the verb that is used to execute the rules.

Example

JES3 SYN prefix =  8
JES3 PLEXSYN prefix = %%
CA OPS/MVS JESCHAR parameter = *

When issuing the JES3 command 8I S, a rule with a command verb (CMD.VERB) of *INQUIRY is executed. CMD.TEXT does not change and remains 8I S unless the rule itself changes CMD.TEXT. The same rule is executed when the command %%I S. CMD.VERB is the same as in the prior case but the CMD.TEXT is %%I S.

CA OPS/MVS supports the use of multiple system or sysplex command prefixes, whether these prefixes are single- or multiple-character.

When decision making using a CMD rule-based on the original JES3 command prefix, use the following three environmental variables:

CMD.JES3PREFIX

Indicates the original command prefix

CMD.JES3SYN

Set to 1 if the original JES3 command prefix is a system scope prefix (SYN)

CMD.JES3PLEXSYN

Set to 1 if the original JES3 command prefix is defined as a sysplex scope prefix (PLEXSYN)

When the JESCHAR is set to the same value on all your systems. One rule works on all JES3 systems, regardless of the SYN and PLEXSYN values are on those systems.

• When the first character in JESCHAR is a wildcard (*) character. Perform additional checking in the PROC section of the rule.
• The cmdverbspec string in the event definition section begins with the wildcard (*) character. A rule that is triggered by an INQUIRY command is also triggered by NOINQUIRY (not a JES3 command) and INQUIRY (a possible z/OS command).
• This issue is solved by coding the processing section of the rule as follows.

  )CMD *INQUIRY
  )PROC
   if CMD.VERB ¬= '*INQUIRY' then
   return 'NOACTION'
  

• A CMD rule can change:

  *START PRTR1 to *START PRTR2
  

  But not to:

  VARY 2F0,OFFLINE