This section describes the fields and selection options provided on the Global Messages for Events page.
For all events checked in the Recipient section, a predefined message will always be sent to all message recipients defined in the Recipient Table for these events.
This function works only if the recipient table contains at least one recipient.
Only one recipient table is available for all defined events.
You can use e-mail addresses as recipients. These must be stored in the symbol table, which can be defined on the Global Messages for Events page.
The recipient table contains the symbol, preceded by the global activation escape character, representing the recipient in this case.
The fields contained in the recipient table are explained in Fields and Columns: Message and Message Recipients in the section Message Sending in the User's Guide.
You can limit the number of messages distributed among users by storing part of the messages in the event store of System Automation Tools. The messages can then be checked only if required.
For all events checked in the Event Store section, a predefined message will always be saved in the event store (if used) of System Automations Tools.
For detailed information on the event store, refer to the appropriate System Automation Tools documentation.
In the Symbols to be Used section of the Global Messages for Events window, you can specify the symbol table to be used for all symbol replacements within the message recipient table.
In the input fields, you can enter a valid name or select a name from a drop-down list box.
|Owner of the symbol table used for symbol replacements within the recipient table.
|Symbol table to be used for symbol replacements within the recipient table.
|Version of the symbol table to be used.
If you do not specify a version, the unnamed version is
The escape character to be used is the global activation escape character.
The value is derived from the global activation escape character. It cannot be modified here.
In the Event message to section of the Global Messages for Events window, you can specify the events for which messages are to be sent and/or stored in the event store.
Prerequisite: The recipient table must be valid.
You specify the events to be selected by marking the check boxes next to the required events.
|Monitor Runtime Information
|Messages are sent each time the Monitor starts or shuts down a task.
|Monitor Runtime Errors
|Messages are sent each time the Monitor error routine is activated due to a Monitor runtime error.
|Activation and JCL Load Errors
|Messages are sent by the Monitor if activation or JCL load errors occur.
|Latest start time exceeded
|Messages are sent each time a job was not submitted before the defined or calculated start time was reached.
|Job executing after deadline
|Messages are sent each time the Monitor detects that a job was not terminated before its defined or calculated deadline time.
|Job not ok, or execution error
| Messages are sent:
|Network or Job not terminated
| Messages are sent by the
network deactivation routine if the active network or job is not terminated.
In this case, the active jobs will be deactivated if the retention period for active jobs is reached. The retention period is defined in the Defaults for Time Ranges described in the Administration documentation.
|Awaiting Symbol Prompting
|Messages are sent each time the Monitor detects that at least one symbol is to be prompted for network activation.
|Symbol not found
|Messages are sent each time a symbol cannot be found and cannot be handled successfully by the global symbol not found exit.
|Calendar undefined for year
|Messages are sent each time Entire Operations detects that a calendar is undefined for the current or the next year.
|Messages are sent by the Monitor if errors occur during node access.
|Execution time threshold reached
|Messages are sent if a job runs three times longer than the estimated elapsed time defined for the job on the Scheduling Parameters page (see the section Schedule Maintenance in the User's Guide).