Understanding the four components of a CLIST

There are four steps to writing CLISTs:

  • defining the language

    All EXECs are assumed to be CLISTs unless the first statement identifies the EXEC as a REXX EXEC. For information about writing REXX EXECs, refer to the IBM publication TSO Extensions Version 2: REXX/MVS User’s Guide.

  • passing data

    You must include a statement—called the PROC 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 This is optional but highly recommended.

  • writing the logic

    A logic section that contains TSO CLIST 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 you want the EXECs to perform.

Each of these parts is described in the following sections.

 

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