Passing data in CLIST EXECs
The CLIST receives data to perform its task through the PROC statement. MainView AutoOPERATOR uses these parameters to pass values to an EXEC when the EXEC is scheduled.
The information passed through the PROC statements varies, depending on the way the EXEC is scheduled. For example, an EXEC can be scheduled by a Rule or by a user and the values passed to the EXEC for these two methods are different.
The PROC statement syntax is
where
Item | Description |
|---|---|
parmnum | is the total number of positional parameters on the PROC statement The maximum is 99. The maximum length of the parameter list when running under TSO/E V2 is 255 characters; the maximum when running under TSO/E V1 is 200. |
P1 P2 P3...Pn | Are symbolic names you can choose for positional parameters The first character must be alphabetic. If the PROC statement receives more values than parameters defined, the remaining values are ignored. If fewer values are received, the extra parameters are filled in by MainView AutoOPERATOR with a dummy value of a “.” (period). It is not necessary to use each symbolic parameter in the logic section of the EXEC. You can use any 1-32 alphanumeric character string to name a positional parameter but the first character must be alphabetic. MainView AutoOPERATOR uses the positional parameters to pass values to an EXEC when the EXEC is scheduled. |
For example, you can code the following PROC statement
where
MSGID | is a name you might use as a symbolic parameter to denote that the first positional parameter is the ID of a message |
WORD1 | is a word you might use as a symbolic parameter to denote the first word of the message |
WORD2 | is a word you might use as a symbolic parameter to denote the second word of the message |
In MainView AutoOPERATOR, EXECs can be scheduled in seven ways and the information (or input) passed to the PROC statement varies depending on how EXEC is scheduled. 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 shows a PROC 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 MainView AutoOPERATOR panel. MainView AutoOPERATOR searches BBPROC and executes the EXEC when it finds a member named PAYROLL. It passes a START or STOP value to the PROC P1 positional parameter, and passes the EXEC name, PAYROLL, as the first positional parameter in the variable named PAYROLL.
You also can use the EXEC Manager application to schedule a user-initiated EXEC. Refer to the MainView AutoOPERATOR Basic Automation Guide, Volume 1: Using Rules for more information about using the EXEC Manager application.
The following table lists where you can find complete discussions of each type of CLIST and the parameters that are passed to them.
To read about | Refer to |
|---|---|
Rule-initiated EXECs | |
ALERT-initiated EXECs | |
user-initiated EXECs | |
time-initiated EXECs | |
EXEC-initiated EXECs | |
externally initiated EXECs | |
end-of-memory–initiated EXECs |