How BMC AMI Ops Automation schedules an EXEC

Also, the information (or input) that is passed to the REXX EXEC varies depending on how the EXEC is scheduled. For example, the input passed to the positional parameters can be different if an EXEC is scheduled by a Rule (Rule-initiated EXECs) or by a user (user-initiated EXECs).

The following example is an ARG statement for an EXEC named PAYROLL that starts or stops a payroll application when a user schedules the EXEC:

To schedule the EXEC, enter its name (PAYROLL) and the parameter value (START or STOP) on the COMMAND line of any MBMC AMI OpsA panel. BMC AMI OpsA searches BBPROC and executes the EXEC when it finds a member named PAYROLL. It passes a START or STOP value to the P1 positional parameter and passes the EXEC name, PAYROLL, as the first positional parameter in the variable named PAYROLL.

BMC AMI OpsA does not do the parsing of the message text for message-initiated EXECs. For example, to parse the message

you must code the REXX EXEC as

The result is

P1 = E

P2 = JOBNAME

P3 = PERFORM

P4 = 999

The following table lists where you can find complete discussions of each type of REXX EXEC and the parameters that are passed to them: