This document covers the following topics:
See also:
Global Messages for Events in the Administration documentation.
You can define or modify a message to be sent as the result of a defined event, or if the job terminated ok or not ok. This is especially useful to notify appropriate personnel of job failure.
The Entire Operations Monitor continues to send a message until it has been successfully transmitted.
A message can be defined for any one event or at the job level according to All checks ok and Any check not ok.
To do so:
Type U in the line command input field of
the appropriate event on the End-of-Job Checking and Actions
Screen. Press Enter.
A Message and Message Recipients window opens.
+------------------------------------------------------------+ ! ! ! Owner SN Network A-1 Version V00003 ! ! Job A-1 ! ! Job ended ok ! ! Message and Message Recipients ! ! ! ! Text ==> hugo_________________________________________ ! ! ! ! to ==> Destination Type Node ! ! §ESN______ =EMAIL__ N0517 ! ! __________ ________ _____ ! ! __________ ________ _____ ! ! __________ ________ _____ ! ! __________ ________ _____ ! ! __________ ________ _____ ! ! __________ ________ _____ ! ! __________ ________ _____ ! ! ! ! Execute if temp. Dummy (EOJ only) ===> Y ! ! Enter-PF1---PF3---------PF5--------PF9---------------- ! ! Help End Save Delete ! +------------------------------------------------------------+ |
Add your definitions in the corresponding fields.
For further information, see the following sections:
Press PF5 (Save), to save your definitions.
Press PF3 (End), to close the Message and Message Recipients window and return to the End of Job Checking and Actions screen.
Please refer to the common description of the message receiver table definition.
The fields and columns provided to define a message and message recipients are described in the following table:
| Field | Description |
|---|---|
| Text | Text of message to be sent if the associated event occurs.
If the text is not modifiable on the map, the effective message text will be generated for the event automatically by Entire Operations. If the message contains an activation escape character, text replacement is performed from the active symbol table. |
| Destination | Enter CONSOLE to send the message to
the operator console (mainframes only).
For Con-nect: enter a valid Con-nect user ID. In z/OS and z/VSE: enter the user ID of a TP system user. In BS2000: enter a terminal name. In UNIX: enter a UNIX user ID valid in the UNIX environment of the addressed server. The message is sent with the UNIX mail function. This field can also contain a symbol. This allows you to define a longer destination as well, for example an e-mail address. If e-mail addresses are to be defined (in an EBCDIC character set) on the mainframe, the string "(a)" must be used instead of "@". |
| Type | See Message Destination Types for a detailed description. |
| Node | Enter the Entire System Server node, by which the message is to
be sent. This is not necessary for messages to Con-nect.
Default: the execution node of the job. |
| Execute if temporary Dummy | This field has a meaning for End-of-Job actions only.
If If the field is left empty, the defaults for the action apply. |
| Type | Description |
|---|---|
| Sends the message by email to any receiver in the Intranet or
Internet.
The email will be sent in plain text mode. Since the receiver field is usually too short for an email address, it is recommended to put a symbol into the destination field, preceded by the activation escape character. The effective email address must be defined as symbol value in the symbol table used. The "at" sign (@) must be entered as (a) on mainframes (in the EBCDIC character set), for example:
For UNIX, see also Email on UNIX and Windows Systems. As Windows does not have a built-in Only for Entire System Server with version lower than
3.2.1:
For z/OS, some special definitions, which are used for message sending, must be made made for Entire System Server nodes with version lower than 3.2.1. See Other Definitions for a Node (Mainframe) in section Definition of Nodes of the Administration documentation. |
|
| =EMH | Sends the message by email to any receiver in the
Intranet or Internet.
The email will be sent in HTML format. Please refer to the |
| =EXIT | Use the global message sending exit.
See Global Message Sending Exit in section Global User Exits of the Administration documentation. |
| =MAILBOX | Sends the message to the mailbox specified in
Destination.
|
| =COMPLET | Sends the message explicitly to a Com-plete user (z/OS only). |
| =TSO | Sends the message explicitly to a TSO user (z/OS only). |
| =CONSOLE | Sends the message to the operator console (mainframes only). |
| Other | BS2000: The processor name related to the BS2000 terminal name to be specified in the Destination column. |
If Con-nect is installed in your system, the message is routed to the defined Con-nect user ID(s). The message includes the environment (Owner, Network, Job, Run) and the standard event text.
If sending to Con-nect is not possible, the message is routed via Entire System Server to the TP system user with the designated user ID. If no special node has been defined, the executing node is used.
If you enter =MAILBOX in the Processor field, the message is sent to the Entire Operations internal mailbox.
Note:
If no message recipient is defined for a network, the messages are
sent to the SYSDBA mailbox.
For further details on mailboxes, see the section Mailboxes.
The PF key assignment in the lower area of the Message and Message Recipients window is as follows:
| Key | Name | Function |
|---|---|---|
| PF9 | Delete | Delete all message receiver definitions.
Caution: |
The sender name contains "Entire Operations" for all sending platforms.
An additional line with the Entire Operations event text is added to the mail.
All further changes can be done in Entire Operations, when the future Entire Operations Server view for e-mail sending will be available.
Before using an z/OS Entire System Server node for sending e-mail,
you must invoke the node definition in Entire Operations and enter the line
command S (specials) for that node.
For further information, see the subsection Special Definitions for a Node (Mainframe) in the section Definition of Nodes of the Administration documentation.
Mail Destination and Mail SYSOUT Class must be defined.
The e-mail send routine for z/OS performs an Entire System Server logon, if necessary. The user ID for the logon is the active job's submit user ID. If no submit user ID is defined for the job, the default user ID for the node will be used.
To use a z/OS (MVS) Entire System Server node with version 321 or higher for sending e-mail, make sure that all users who send e-mail, are correctly defined in the security systems (if applicable). It might be necessary to define user ID as USS users.
For more information, see the documentation for Entire System Server, for the operating system and for the security system.
E-mail can be sent via BS2000 nodes, if Entire System Server nodes with version 321 or higher are used.
Before using a BS2000 Entire System Server node for sending e-mail,
you must invoke the node definition in Entire Operations and enter the line
command S (specials) for that node.
For further information, see the subsection Special Definitions for a Node (Mainframe) in the section Definition of Nodes of the Administration documentation.
The e-mail send routine for BS2000 performs an Entire System Server logon, if necessary. The user ID for the logon is the active job's submit user ID. If no submit user ID is defined for the job, the default user ID for the node will be used.
To be able to send e-mail on UNIX machines from Entire System Server, the following mail programs must be available there:
| AIX, HP-UX, Linux, Sun Solaris | sendmail |
|---|---|
| others | rmail |
Note:
The Return-Path: of the e-mail is being
set to the same value as Reply-To:.
To be able to send e-mail on Windows machines from Entire System Server, you must define a message command. This is a (third-party) command line tool to be used for sending e-mail via Entire System Server / Windows.
Before using a Windows node for sending e-mail, you must invoke the
node definition in Entire Operations and enter the line command
S (specials) for that node.
For further information, see the subsection Special Definitions for a Node (UNIX and Windows) in the section Definition of Nodes of the Administration documentation.