The Global Messages for Events screen is used to determine the message recipients for specified events.
This section describes the fields and selection options provided on the Global Messages for Events screen.
To define global messages for events
From the System Services Menu, select the Global Messages for Events option and press ENTER.
A Global Messages for Events screen similar to the example below appears:
16.10.18 ***** Entire Operations ***** 15:03:54
Global Messages for Events
------------------------------------------------------------------------------
Definition of events, for which messages will always be sent or stored in the
SAT Event Store. Please note that the recipient table must be valid for
message sending. You can use PF6 to modify the recipient table.
Message Event
Events Sending Store Symbols to be used
Monitor Runtime Information Y Y Owner ==> SYSDBA____
Monitor Runtime Errors Y Y Symbol Table ==> GMSG-RCV__
Activation and JCL Load Errors N Y Version ==> (unnamed)_
Latest start time exceeded N N Escape ==> @
Job executing after deadline N N
Job not ok, or execution error Y Y
Network or Job not terminated N Y
Awaiting Symbol Prompting N N
Symbol not found N Y
Calendar undefined for year Y Y
Node Errors Y Y
Execution time threshold reached Y Y
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save RcpTa Symb |
For all events marked with Y in the input
fields of the Message Sending column, a predefined message
will always be sent to all recipients defined in the recipient table (opens
with PF6) for these events.
This function works only if the recipient table contains at least one recipient.
Note:
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 screen.
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 marked with Y in the input
fields of the Event Store column, 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 screen, 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 use
the asterisk (*) as a wildcard to select a name from a selection
window.
| Field | Description |
|---|---|
| Owner | Owner of the symbol table used for symbol replacements within the recipient table. |
| Symbol Table | Symbol table to be used for symbol replacements within the recipient table. |
| Version
(Symbol Table) |
Version of the symbol table to be used.
If you do not specify a version, the unnamed version is
used. Specify |
| Escape | Read-only field.
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 Events section of the Global Messages for Events screen, 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 entering
Y (Yes) in the input field next to the required events. Events for
which N (No) is entered are not selected.
| Events Selected | Messages Sent | |
|---|---|---|
| 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 Default Setting (1) 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. | |
| Node Errors | 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 in the Scheduling Parameters window (see the section Schedule Maintenance in the User's Guide). | |
| PF Key | Name | Function |
|---|---|---|
| PF6 | RcpTa |
Recipient table.
Use this PF key to open and modify the recipient table. |
| PF7 | Symb | Symbol table.
Definition of symbols to be used in message recipient definitions. You can view and modify all symbols defined for the specified symbol table. |