Messages JES200 through JES2xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

JES260S OID=orderId OPEN OF DDNAME ddName FAILED

Explanation: Control-M monitor failed to open a work data set defined by the ddName DD statement.

This data set must be defined as a temporary or fixed work area for Control-M monitor. The ddName DD statement is probably missing.

Control-M monitor will shut down with errors.

Corrective Action: Correct the JCL for the Control-M monitor, and start again.

JES261S taskTypememNamejobName/ jobId OID=orderId ALLOCATION OF {SYSOUT FILE | ARCIVE FILE} dsn FAILED: R15=rc ERR=erc INFO=irc

Explanation: Dynamic allocation to the specified dsn failed.

Control-M dynamically allocates the job sysout data sets, and/or the archive data set. The allocation failed for the specified reasons. For an explanation of the return codes displayed as part of this message, see the IBM manual MVS Programming: Authorized Assembler Services Guide.

Return codes in this message:

• rc - the contents of R15 in hexadecimal notation.
• erc - error reason code in hexadecimal notation.
• irc - information reason code in hexadecimal notation.

The requested function is stops. If analysis of job results was in process, the job terminates NOTOK with Reason Unknown (*UKNW).

Corrective Action: Check the relevant IBM publication for the reason.

• For sysout data sets, check if the sysout was purged while the Control-M monitor was trying to read it.
• For archive files, the Control-M monitor allocates archive files with DISP=(NEW,CATLG). Therefore, the same data set name should not be used in different sysout archive instructions, even for the same job.

If your system programmer is unable to resolve the problem, prepare the Control-M monitor full output and contact BMC Customer Support.

JES262W taskType memName jobName /jobId OID=orderId num UNSUCCESSFUL ATTEMPTS TO READ JOB DATA BY SUBSYSTEM REQUEST. RETRY CONTINUES

Explanation: This message is issued every num unsuccessful attempts to read job data by subsystem request.

Whenever the Control-M monitor does not succeed in reading job sysout, this message appears on the operator console. For example, when a job is not run due to a JCL error, then the third sysout data set is missing and this message is issued.

Control-M continues to retry reading the job data for a predefined number of times. If the error persists, this job is not read and error message CTMD50S is issued.

Corrective Action: For the appropriate action, refer to the section on the Control-M Monitor and JES in the Control-M for z/OS Administrator Guide.

JES263S taskType memName jobName/jobId OID=orderId OPEN OF SMB FILE DSNAME dsn FAILED. RC=rc

Explanation: Open of sysout data set of the job by Control-M monitor failed. Control-M cannot read the job sysout and analyze it. Possible causes are:

• Someone purged the output of the job while Control-M monitor was trying to read it.
• Internal Control-M monitor error.
• General problems with JES that caused JES to terminate.

The job will finish with status FAILED - REASON UNKNOWN.

Corrective Action: If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

JES264S taskType memName jobName/jobId OID=orderId POINT TO DSNAME dsn FILE FAILED. FDBK code

Explanation: Control-M reads the jobs output as a VSAM file. For some reason it failed in a VSAM operation. Control-M cannot read the jobs sysout and analyze it. Possible causes are:

• Someone purged the output of the job while Control-M monitor was trying to read it.
• Internal Control-M monitor error.
• General problems with JES that caused JES to terminate.

The job will finish with status FAILED - REASON UNKNOWN.

Corrective Action: If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

JES265S taskType memName jobName/jobId OID=orderId GET TO DSNAME dsn FILE FAILED. FDBK code

Explanation: Control-M reads the jobs output as a VSAM file. For some reason it failed in a VSAM operation. Control-M cannot read the jobs sysout and analyze it. Possible causes are:

• The output of the job was purged while Control-M monitor was trying to read it.
• Internal Control-M monitor error.
• General problems with JES that caused JES to terminate.

The job will finish with status FAILED - REASON UNKNOWN.

Corrective Action: If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

JES266S OID=orderId READING JOB DATA BY SUBSYSTEM REQUEST FAILED

Explanation: Control-M monitor could not read all the data sets of the job, and analyze the data.

Possible causes are:

• Internal Control-M monitor error.
• General problems with JES that caused JES to terminate.
• Someone has purged the output of the job while the Control-M monitor was trying to read it.

The job finishes with status FAILED - REASON UNKNOWN.

Corrective Action: Look for prior messages in the IOA Log. If the job was not purged, and JES did not have any problems, prepare the Control-M monitor full output and contact BMC Customer Support.

JES267S taskType memName jobName/jobId OID=orderId ARCHIVE FUNCTION ABENDED ON abCode

Explanation: An abend occurred during sysout archiving function. Common abend codes:

• SB37, SE37 - No more space for the sysout in the file.
• S913 - Security violation.

Archiving stops.

Corrective Action: For an Sx37 type of abend, consult your INCONTROL administrator for the possibility of changing the default Control-M archive file allocation size in the Control-M installation parameters (CTMPARM). For an S913 abend, check with your security administrator. For other abends, check IBM publications for the reason.

JES268S taskType memName jobName/jobId OID=orderId INVALID INSTALLATION PARAMETERS FOR SYSOUT ARCHIVING

Explanation: Highlighted, unrollable message.

Invalid values of the Control-M Installation Parameters (CTMPARM) which control the sysout archiving function.

The archiving function is terminated. Control-M will not perform any sysout archiving and valuable data may be lost.

Corrective Action: Consult your INCONTROL administrator immediately. See the section on Control-M operational parameters in the Control-M chapter of the INCONTROL for z/OS Installation Guide for the valid values of the sysout archiving parameters. To load new parameters, shut down the Control-M monitor and start it again.

JES269W OID=orderId INVALID RESPONSE FROM IEFSSREQ: SSOBFUNC=func R15=r15 SSOBRETN=ssobrc PHASE=x

Explanation: A failure during sysout operation. The Control-M monitor is using subsystem request services to process the job sysout. A sysout function failed.

The Control-M monitor sometimes recovers from this kind of situation, and completes the function. If another error message indicating a sysout operation failure follows this one, then follow the User Response instructions.

Corrective Action: If the Control-M monitor does not recover from the failure, consult BMC Customer Support. To solve the problem, support personnel require the data of the message, a list of all the IOA Log messages concerning the problematic job, and the small SNAP (DUMP) of storage areas that the Control-M monitor produces in this event.

JES26AS OID=orderId ABEND code WHILE READING SYSOUTS. JOBORDER joborder HELD

Explanation: Control-M could not read the output of a job from the spool. Control-M may be unable to read the output of a job because the OUT180 data set in which the data is placed overflows. The reason for this abend is either that the job output is unusually large, or that a spool corruption occurred that caused Control-M to read a very large amount of information, not related to the specific job, into its OUT180 data set.

The Control-M monitor changes the job status to HELD PROBLEMS READING SYSOUT.

Corrective Action: If the OUT180 data set is too small for the job output, increase the space value in the OUT180 DD, restart Control-M monitor, and free the job order in the Active Jobs file (AJF).