Parameters passed to REXX EXECs in MainView AutoOPERATOR

Understanding the four components of a REXX EXEC

• defining the language: all EXECs are assumed to be CLISTs unless the first statement identifies the EXEC as a REXX EXEC. Refer to the IBM publication TSO Extensions Version 2: REXX/MVS User’s Guide for a complete discussion.
  
  
• 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 MainView AutoOPERATOR 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 MainView AutoOPERATOR schedules EXECs to run. 

Each of these is described in the following topics:

• How to define the language
• How data is passed to the EXEC
• How to document REXX EXECs
• Writing the logic section
• How MainView AutoOPERATOR schedules an EXEC
• ALERT-initiated REXX EXECs
• End-of-memory-initiated REXX EXEC
• EXEC-initiated REXX EXECs
• Externally initiated REXX EXECs
• Rule-initiated REXX EXECs
• Time-initiated REXX EXECs
• User-initiated REXX EXECs