CA IDMS DMLO Session › Using the CA IDMS DMLO CLIST Processor › CLIST Execution

CLIST Execution

Use the following command to request execution of a CLIST:

EXEC [S.]clist-name a1 a2 a3 a4 a5 a6 a7 a8 a9

Where:

• S. - forces access to global CLIST if both a user and global CLIST of same name exist.
• clist-name - 1-8 character CLIST identifier.
• a1 ... a9 - represent optional arguments for replacement of CLIST variables appearing within the body of the CLIST.

You may incorporate CLIST variables within any CLIST statements. These variables are of the form %1 ... %9. This variable capability allows you to prepare general-purpose modules for frequently used functions.

Arguments supplied with the EXEC statement may be record, area, set, scratch/queue names, element names, keywords, or literals of any acceptable format. The arguments will replace all occurrences of the corresponding variables within the CLIST statements at the time the statement is executed.

You may indicate that an optional argument is null by entering "," for that argument. This will cause the corresponding symbol to be replaced by a null string in the CLIST command. You may test if argument n is null with a conditional test for %NULLn. This conditional name is "true" if the corresponding argument is supplied as a null value.

The CLIST facility allows you to use DEFINE symbols (:%n) for documenting the use of CLIST arguments ahead of the executable CLIST commands. Not only will this provide documentation for a user who is editing the CLIST, but it allows the CLIST processor to prompt for missing arguments. If a CLIST command is encountered which includes a CLIST variable for which a corresponding argument has not been provided, the processor will display a screen which allows you to supply the missing argument value. If a DEFINE exists for the missing argument, the associated documentation is also displayed as shown below.

For more information, see CLIST Editing Commands.

mm/dd/yy.....................GETCALC  COMMAND PROMPT...................hh:mm:ss
THE FOLLOWING COMMAND CONTAINS UNRESOLVED CLIST ARGUMENTS. YOU MUST PROVIDE
VALUE(S) TO CONTINUE EXECUTION. AFTER ENTERING VALUES, PRESS THE "END" KEY

CINIT %1

:%1 = RECORD TO BE OBTAINED
:%1 001-064..
:%1 065-128..
:%1 129-192..
:%1 193-256..


DML/O Rnn.nn === CLIST = GETCALC              DEPTH C=01 R=00 ======== CA, INC.
RECORD=EMPLOYEE         STATUS=0000  DBKEY=0000075008-0001 KEY0=0000000000-0000
EXEC GETCALC

SUBSCHEMA=EMPSS01   SCHEMA=EMPSCHM   VER=0100    COL 001-080  LINE 0001 OF 0012

If you have no idea of what arguments are needed for a given CLIST, "EXEC clist-name ?" will cause the CLIST processor to prompt for all arguments, and display all DEFINE information. Such documentation for any non-trivial CLIST is highly recommended. Note that a CLIST may EXEC another CLIST. Thus, you may define CLIST subroutines called by other CLISTs. CA IDMS DMLO will ensure that recursion does not occur; i.e., a CLIST does not appear at multiple levels in an active EXEC nest.