At 12:33 -0500 on 06/18/2015, Tom Marchant wrote about Re: TSO XMIT
NOTIFY -- Part II:
In JES2 z/OS V1R7, exit 13 has been deleted because the existing
notify message
and associated exit receive control too early in SYSOUT data set receive
processing. When a SYSOUT data set is received over NJE, a header record is
received first, followed by the actual data. If the SYSOUT data set
is large, a TSO user might issue a RECEIVE command and find no data
to receive even though
exit 13 has already issued message $HASP549. To avoid these problems, in z/OS
V1R7, exit 40 is enhanced to allow for control over the $HASP549 message.
Question - When any SYSOUT or JOB is received via NJE a "received"
message is displayed. In the case of a SYSOUT does this message get
displayed/issued when the SYSOUT starts to arrive or when it
completes and gets queued to spool. If the latter, then the trigger
of Exit 13 (or whatever exit has assumed this function) should be at
that time and the "too soon" situation would not occur.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
