CONTROL-M for z/OS - Why is Control-M having a problem reading sysout? Errors messages issued: CTM262W, CTMD50S, SPY276E.

Knowledge Article

Article Number

000196019

Old Article Number

000014823

Article Type

FAQ/Procedural

Title

CONTROL-M for z/OS - Why is Control-M having a problem reading sysout? Errors messages issued: CTM262W, CTMD50S, SPY276E.

Summary

Why is Control-M having a problem reading sysout? Errors messages issued: CTM262W, CTMD50S, SPY276E.

Product

Control-M for z/OS

Component

Control-M for z/OS

Applies to

Control-M for z/OS all versions

Question

Control-M is having problems reading the jobs sysout and is issuing the messages like:

CTM262W 0020 UNSUCCESSFUL ATTEMPTS TO READ JOB DATA BY SUBSYSTEM REQUEST. RETRY
CTMD50S READING JOB DATA BY IEFSSREQ FAILED 0021 TIMES. LAST RC 0004. 001-IATT2F
SPY276E JOB memname jobname/jobid OID=02K1V READING SYSOUT FAILED

Jobs are also receiving a status of : Failed - Reason Unknown Ended-Not "OK".
Control-M is not able to read their sysout in JES.

Answer

Check all the following and set the recommended parameters:

- In ioa.PARM(CTMPARM) in section SPYER set parameters SAPI=Y and SDSB=Y.

- Make sure the Control-M held output class defined in ioa.PARM(CTMPARM) section MONITOR parameter HLDCLAS is defined in JES as (HOLD,HOLD)

=>To specify the held output class, the following JES definition must be made:
OUTCLASS(h) OUTDISP=(HOLD,HOLD) /* IS A HELD CLASS */
OUTPUT=PRINT /* PRINT CLASS */
where h is the sysout class specified in the HLDCLAS parameter in the CTMPARM member.

=> To display and check the current CLASS details use the JES2 command:
$D OUTCLASS (<HLDCLAS>)
Exemple:
$D OUTCLASS (X)
RESPONSE=CMB2
$HASP842 OUTCLASS(X)
$HASP842 OUTCLASS(X) OUTPUT=PRINT,BLNKTRNC=YES,
$HASP842              OUTDISP=(HOLD,HOLD),TRKCELL=YES

- Make sure that the job submitted by CONTROL-M have in JOB card MSGLEVEL=(1,1)

- If the job is an "ON SPOOL" jobs, e.g. a JOB/STC not submitted but tracked by Control-M, make sure that the TASKTYPE parameter in the job SCHEDULE definition is the correct one:
=> STC when tracking a started task
=> JOB when tracking a regular job.
Else the sysout will NOT be found leading to message CTMD50S.

- Also make sure that the tracked job is using a MSGCLASS equal to HLDCLAS, when working in a JES3 environment, and equal to any held SYSOUT class (not necessary the same one as HLDCLAS), when working in a JES2 environment.

- When an NJE job is returned to Control-M running on JES3, make sure the outputs are in HOLD EXTWTR (not HOLD TSO). If this can't be achieved, the use of JES3 exits IATUX37 or IATUX38 can be helpful to change the "sysout class type" to "20" which means External writer.

- Make sure that the messages such as IEF375I, IEF376I, IEF033I are not suppressed by any software.

See the complete list of required messages in the manual:
INCONTROL for z/OS Installation Guide: Installing
APPENDIX-F Message considerations
Table 177 Messages that should not be modified or suppressed

Note:
Processing of MSGCPRES:

If MSGCPRES in CTMPARM is set to Y, then two extra statements are added to the job at submission time that look like:

//DEFAULT OUTPUT JESDS=ALL,CLASS=*
//JESDS OUTPUT JESDS=ALL,CLASS=X

This has the effect of:

- Preserving the jobs original MSGCLASS (DEFAULT card)
- Creating a second set of sysouts using the JESDS statement where the class is set to the value of parameter HLDCLAS that is set in CTMPARM.

With SDSB set to N, the control-M monitor is only able to read sysouts that are created in a HELD class, so in the example above, one of the DEFAULT or JESDS sysouts MUST be in a HELD class. If both these sysouts are in a non HELD class, then Control-M will not be able to read the sysout.

With SDSB set to Y, Control-M will be able to read the sysout regardless of weather it is on the HELD or OUTPUT queue in JES.

Check if the sysout of the problem job can be viewed via TSO OUTPUT facility.

If the problem cannot be solved using the above instructions/recommendation, open a new case to BMC Support and collect the following data for analysis:

1. On CONTROL-M monitor:
=> Set on trace levels 33, 39, 49 using command: F controlm,TRACE=(33,39,49)
=> Reproduce the problem
=> Stop trace using the command: F controlm,TRACE=(-33,-39,-49)
=> Collect the full CONTROL-M sysout

2. Run the MVS/JES2 command: $DJOBCLASS(STC) and collect the answer.

3. Open a new case to BMC Support on message CTMD50S and attach all the previous data collected.

4. If the PTF PG06644 is applied or the maintenance level is equal or above 9.0.21.000,
=> then SET SDSB=F in section SPYER of the &ILPREAFA.PARM(CTMPARM).
=> Restart the CONTROL-M monitor.
This will force SDSB=N so using the old SPOOL reading method.
=> If it works fine using this parameter SDSB=F then inform the BMC Support and
keep this mode until the trace has been analysed and the root cause identified.

Attachment(s):