Legacy ID:KA428516
Cause
This happens in case a sysout dataset is released by the still ececuting job and transferred back to the original node. This does not prevent Control-M from tracking the job's status on the remote host (provided that enhanced NJE support is active (ENHNJE=Y in CTMPARM)) and so . at the end. the job's status is OK or NOTOK depending on the job's result.
Solution
There is no need to do anything, the messages can just be ignored. You may have a look at the job and the program that create these sysout datasets. In some cases changes in the JCL can prevent such a sysout from being transferred back before the job stops executing.
Additional Information
The sysout reading attempts at this stage (and the messages that accompany them) are unnecessary, and development will consider changing this behaviour in a future release of the product
Related Products:
- Control-M for z/OS