When a job is not run due to a JCL error, only two SYSOUT datasets exist for the job. Therefore, Control‑M cannot read the expected third SYSOUT dataset, and the above message is displayed.
When JES is very busy, a period of up to a minute (in extreme cases) may pass between the time the job has finished executing and the time JES enables Control‑M to read its SYSOUT (in other words, JES is "stuck" in the output processing stage).
By default, CTM262W is displayed every 5 times the Control‑M monitor attempts to read the job SYSOUT and does not succeed. If after 20 attempts the Control‑M monitor still cannot read the SYSOUT, the following message is displayed:
CTMD50S READING JOB DATA BY SUBSYSTEM REQUEST FAILED AFTER n ATTEMPTS. LAST RC rc FILE filename jobname/jobid
These two default values can be changed using installation defaults.
On the other hand, message CTM262W can indicate serious problems with the job’s sysout. The following problems can cause this message to be displayed:
When a job’s output is released for print (that is, the job’s output is no longer held), the job’s output must be printed or purged.
In a multicomputer environment, the following chain of events can occur:
Control‑M monitor submits the job from computer A.
Computer A crashes (or is shut down).
Control‑M monitor is activated on computer B and the job executes in computer B. When the job finishes executing, Control‑M cannot read the job’s output, and message CTM262W is displayed.
This is caused by the job waiting to be "handled" by the JES of computer A.
This problem can be overcome by assigning the job to computer B using JES command $TJnnn,S=sysid. Control‑M then reads the output, and the message is removed from the operator console.
