When JES2 first reads in the job, the TSO/E user ID is stored in the job header record if NOTIFY= was specified on the JOB statement. The TSO/E user ID can differ from the RACF® userid specified in USER= on the JOB statement. The originating node name is also stored in the job header.

If the job header contains a NOTIFY userid and the job is transmitted from its origin node for execution on another node, the job transmitter issues a message to the NOTIFY user ID indicating that the job was transmitted for execution.

When the job completes execution, the JES2 output processor on the execution node examines the NOTIFY user ID in the job header. If the NOTIFY userid is present, a notification message is issued and directed to the userid on the origin node. If the origin node and execution node are the same, the result is an issuance of an MVS™ SEND command specifying the userid. If the origin node and execution node are different, the notification is sent back to the origin node through the JES2 remote console processor and RTAM; the JES2 system on the origin node issues the SEND command.

When a job's system output (or any part of it) reaches its ultimate destination, the SYSOUT receiver on the destination node examines the userid in the job header. If NOTIFY= was specified on the job card, the SYSOUT receiver issues a message to the specified user indicating that the job's SYSOUT was received and where it was received. JES2 sends the message to the job's origin node (as explained previously for the end-of-execution message). For transmissions that entered the network through the TSO/Extensions interactive data transmission facility, NOTIFY= is automatically specified. For further discussion, see the “Other Programming Considerations” topic of the description of Exit 40 in z/OS JES2 Installation Exits.

If an installation wants local TSO/E userids notified when mail is placed in the output queue (from either another node or a spool reload procedure), specify MAILMSG=YES on the NJEDEF initialization statement.