Writing Rules › Writing Command Rules

Writing Command Rules

A command rule begins with the CMDIN keyword followed by characters that identify a specific command or group of commands that cause the rule to execute. For example, a rule beginning with CMDIN(DRL) executes when CA Automation Point determines that a command starting with DRL is issued through CA Automation Point.

Command rules can also contain any of these rules keywords:

Command rules can be used when you issue a command from the red command area or from the Command dialog using the Automation Point Desktop, the Remote Viewer, or the Web Viewer.

Command rules do not execute if you enter the command directly in the session window. CA Automation Point checks the command rules, as well as the time rules, regardless of whether the session is configured as an automated session.

Note: You define a session to be automated by checking the Automate Session checkbox in the session definition.

In many instances, command rules and message rules are implemented similarly. However, two keywords, SUPPRESS and REWORD, have slightly different meanings in command rules than they do in message rules. See the descriptions of these keywords in the Command and Keyword Reference Guide.

Command rules let you suppress a command or allow operators to enter a pseudo-command from the command line and reword it as another command, without going into REXX mode. The command rule can also intercept the command and invoke a REXX routine or take other action as required.

Examples

• The following rule prevents an unauthorized remote operator from using an MVS STOP command to remotely stop CA OPS/MVS, and issues a write-to-operator message to the CA Automation Point message console.

  CMDIN(STOP) WHEN(&WORD2 EQ 'OPSS' AND &USER NE '' AND &USER(1:9) NE 'SYSADMIN@') SUPPRESS WTXC(&USER is not authorized to remotely stop CA-OPS/MVS)
  

• The following rule enables an operator to get a complete list of the outstanding replies using the DRL pseudo-command, which is converted to the D R, L, CN=(ALL) command.

  CMDIN(DRL), REWORD(D R, L, CN=(ALL))
  

• The following rule rewords a complex MVS command so that the operator can issue the pseudo command 'SLIP0C1' instead of the complete MVS command.

  CMDIN(SLIP0C1), REWORD(SLIP SET, ID=P0C1, COMP=0C1, A=SVCD, MATCHLIM=1, JOBNAME=TESTPGR, END)
  

• When an operator issues the PAGE Bill command through CA Automation Point, this rule executes to intercept the command. It keeps (suppresses) the PAGE pseudo-command from being issued to the host, invokes the page.rex program to page Bill on demand, and issues a write-to-operator message to the CA Automation Point message console.

  CMDIN(PAGE), SUPPRESS, REXX(page.rex &WORD2), WTXC(Requested paging &WORD2)
  

• The following rule enables an operator to get a complete list of the outstanding replies using the DRL pseudo-command, which is converted to the D R, L, CN=(ALL) command. rule tracks the date and time the START command is issued through CA Automation Point.

  CMDIN(START), SET (&LAST_START = &TIME  &DATE), WTXC(Most Recent START issued at &LAST_START)