Parameters passed to REXX EXECs in BMC AMI Ops Automation

The topics in this section describe how parameters are passed to REXX EXECs in 

BMC AMI Ops Automation

.

Understanding the four components of a REXX EXEC

There are four steps to writing REXX EXECs:

  • Defining the language: all EXECs are assumed to be CLISTs unless the first statement identifies the EXEC as a REXX EXEC. See the IBM documentation TSO/E: REXX User’s Guide for more information.
  • Passing data: you must include a statement, called the ARG statement, that defines the input parameters to be used by the EXEC logic.
  • Documenting the EXEC: you can include comments, enclosed by /* and */, throughout the EXEC to describe the purpose of the EXEC statements.
  • Writing the logic: a logic section contains REXX EXEC statements and commands, and BMC AMI OpsA IMFEXEC commands that perform user-defined automation tasks. Use the IMFEXEC commands to specify the automation actions and commands that you want the EXECs.

In addition, it is important to understand how BMC AMI OpsA schedules EXECs to run. 

This section contains the following topics:


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*