ALERT-initiated REXX EXECs
An ALERT–initiated EXEC (also called a follow-up EXEC) is scheduled by a user from the ALERT Management Facility.
When coding the EXEC that issues the IMFEXEC ALERT command, use the EXEC parameter to specify the name of the follow-up EXEC.
The EXEC is then scheduled from the ALERT Detail panel of the ALERT Management Facility by entering any value (up to five characters) in the RSP column of the panel.
To read about | Refer to |
|---|---|
scheduling the EXEC | Chapter 3, 'ALERT Management Facility' in the MainView AutoOPERATOR Basic Automation Guide, Volume 1: Using Rules |
coding an ALERT with an associated EXEC |
Potential use
When an ALERT appears on the DETAIL display, it may require an advanced automation response.
An ALERT-initiated EXEC can handle such a response. By entering any value (up to five characters) in the RSP column of the ALERT Detail panel, you can schedule a follow-up EXEC.
One possible use for an ALERT-initiated EXEC is to log messages in the BBI-SS PAS Journal.
Parameters passed to the EXEC
When an ALERT–initiated EXEC is coded, the IMFEXEC ALERT . . . EXEC(ABC) command can schedule the follow-up EXEC with or without parameters.
In this example, the EXEC name is:
without optional parameters:
'IMFEXEC ALERT ... EXEC(ABC)'with optional parameters ( x y z ):
'IMFEXEC ALERT ... EXEC('ABC x y z')'If the EXEC has parameters, you must enclose them with the EXEC name in single quotation marks ( ' ' ) . If you do not, only the EXEC name will be passed and the parameters will not be passed.
For more information, see Example of input without parameters andExample of input with parameters.
The first positional parameter passed to the ALERT-initiated EXEC is always the EXEC name. The characters that you enter in the RSP column of the ALERT Detail Display to schedule the EXEC are also passed. However, the position that those characters have depends on whether or not you use optional parameters.
Example of input without parameters
For example, the user enters
DEF
in the RSP column of the ALERT DETAIL DISPLAY panel.
Then, the ARG statement receives data passed in the following way:
Positional parameter | Value passed | Description of value passed |
|---|---|---|
1 | EXEC name | name of the EXEC |
2 | DEF (contents of the 5-character RSP column) | up to five-character string the user enters in the RSP column of the ALERT DETAIL DISPLAY panel to actually invoke the ALERT |
3 through n | text of the ALERT | actual words of the ALERT associated with the scheduled EXEC |
n + 1 | .... | period pads the positional parameter |
Example of input with parameters
For example, you enter
DEF
in the RSP column of the ALERT DETAIL DISPLAY panel.
Then, the ARG statement receives data passed in the following way:
Positional parameter | Value passed | Description of value passed |
|---|---|---|
1 | EXEC name | name of the EXEC |
2 | x | first parameter passed to the EXEC |
3 | y | second parameter passed to the EXEC |
4 | z | third parameter passed to the EXEC |
5 | DEF (contents of the 5-character RSP column) | up to five-character string the user enters in the RSP column of the ALERT DETAIL DISPLAY panel to actually invoke the ALERT |
6 through n | text of the ALERT | actual words of the ALERT associated with the scheduled EXEC |
n + 1 | .... | period pads the positional parameter |