TSO/E

In z/OS® V1R4, JES2 discontinued monitoring TSO/E logons. Because duplicate instances of a given user ID can be logged on at the same time, it is highly recommended that the GRS RNL list be updated to convert SYSIKJUA to a SYSTEMS ENQ in order to prevent such duplicates. If the RNL is not updated and duplicate instances of a user ID are logged on, then TSO GR and SEND messages sent to the duplicated logged on user IDs will not function.

To revert to pre-z/OS V1R4 processing of duplicate logon checking, use the supplied JES2 sample Exit 44 (HASX44A). see z/OS JES2 Initialization and Tuning Reference for further exit information. Using this exit might result in a delayed re-logon for a given user ID with its accompanying erroneous error message.

Jobs submitted by TSO/E can execute anywhere in the configuration, subject to their affinities (as previously discussed). However, held output data sets are accessible (by the TSO/E OUTPUT command) to the submitting user, regardless of where he is logged on or where the job was executed. If you are not using the shared broadcasting function (BRODCAST=NO is either specified on the OUTDEF initialization statement or the default), JES2 processes the NOTIFY messages as requested on the JCL JOB statement as follows:

If the user is logged on, the NOTIFY message is returned to that user.
If the user is not logged on, the NOTIFY message is issued on the member from which the job was submitted, and the message is added to the SYS1.BRODCAST data set associated with the originating member. Also, output generated from that job is not available until the originating member has issued the NOTIFY message.

If, however, you are using the shared broadcasting function (BRODCAST=YES is specified on the OUTDEF initialization statement), JES2 processes the NOTIFY message as follows:

If the user is logged on, the NOTIFY message is returned to that user.
If the user is not logged on, the NOTIFY could be issued on any member in the complex, and the message is added to the SYS1.BRODCAST data set.

Jobs submitted by TSO/E users can also execute on any configuration in the NJE network. When a job is successfully transmitted to another node for execution, it is purged at the entry node.