e.g. the completion message sent to QTOCxxxx. The spooled joblog for
the submitted job would show details about the WM that
defined\started the batch job.
You lost me on the QTOCxxxx part.
A joblog spooled [with log(4 0 *seclvl)], in contrast to a copy\paste of just
the message identifier and first level text, will show some context for the message
We started years ago with a retrieval of the GO SAVE 21 program and
modified it for our purposes. In 2002, we added ENDTCPSVR, ENDHOSTSVR,
and ENDTCP per IBM recommendations. <<SNIP>>
Apparently the CPC1221 was logged following one of those requests?
If LOGCLPGM(*YES) is in effect, then where the message appears in the
joblog with respect to the Request messages being logged, also can be
used to help infer what\which request had issued the SBMJOB request.
Given the unfathomable stupidity of various circumventions for effecting
the successful ending of the TCP\IP that I have seen floated here on this
list [apparently recommendations from IBM], mostly IIRC two DLYJOB requests
for five or more minutes each, it is easy for me to expect that the submitted
job is just another daft attempt to deal with [uh, circumvent] what appears
to be a design problem :-(
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact