Previous Topic

Next Topic

Book Contents

Book Index
Messages CTM400 through CTM4xx

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.

CTM400S INVALID RETURN CODE FROM SORT = rc. CHECK THE SORT MANUAL

Explanation: A sort program that has been activated internally by a report ended with an unexpected return code (rc).

The report stops executing with a condition code of 08 or 12.

Corrective Action: To clarify the reason, see the documentation for the sort program and to the sort messages of the job.

CTM401I A KEYSTROKE REPORT STARTED

Explanation: This information message is a normal start message of a KeyStroke Language Report.

Corrective Action: No action is required.

CTM402I KEYSTROKE REPORT ENDED SUCCESSFULLY

Explanation: This information message indicates that a KeyStroke Language Report ended successfully.

The report ended successfully from the point of view of report syntax and execution. A user may set the condition code to any condition code and send a message indicating otherwise. It is recommended to check the condition code as well (using the Control-M or Control-D facilities).

Corrective Action: No action is required.

CTM409E A KEYSTROKE REPORT ENDED WITH ERROR(S)

Explanation: A syntax or execution error occurred during processing of a report.

The KeyStroke Language Report will terminate with a condition code of 08 or 12.

Corrective Action: Look for the error in the report listing (the DAKSLOUT DD statement).

CTM411S OPEN OF DDNAME "DAPROG" FAILED

Explanation: This message is issued by the New Day procedure. The data set described by the DAPROG DD statement contains a list of programs to be activated by the New Day procedure. Possible causes are:

  1. The DAPROG DD statement is missing.
  2. The data set described by the DAPROG DD statement cannot be opened for sequential read.

For more details, see the chapter that discusses implementation issues in the appropriate user guide.

The New Day procedure stops executing.

Corrective Action: Correct the JCL for the job and rerun it.

CTM413E PROGRAM pgm WAS NOT FOUND

Explanation: The pgm program was not in the load list of the Daily subsystem. The DAPROG DD statement describes a data set that contains a list of programs to be activated as part of the Daily subsystem.

The Daily subsystem terminates with errors.

Corrective Action: Check whether IOA Load library is concatenated as STEPLIB to the Daily subsystem. Correct the JCL and consult your system programmer about running the Daily subsystem again.

CTM414E INVALID CONDITION CODE FOR PROGRAM pgm

Explanation: The pgm Control-M or Control-D internal program, which was activated by New Day processing, finished with return code higher than the maximum allowed in the program list. Positions 10 through 11 in the program list indicate the highest return code that is still considered OK for this program.

Corrective Action: No action is required.

CTM415I PROGRAM pgm IS BEING INVOKED

Explanation: This information message indicates that an internal Control-M or Control-D program was activated by New Day processing.

Corrective Action: No action is required.

CTM416I {CTMILY | CTDILY} ENDED

Explanation: This information message indicates that New Day processing is finished.

Corrective Action: No action is required.

CTM417E UNRECOGNIZED PARAMETER ON EXEC STATEMENT: expression

Explanation: The CTMTDAY procedure was executed with an unsupported or invalid NEWDAY parameter value expression. (For more information on the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”)

The CTMTDAY procedure is not executed.

Corrective Action: Correct and re-execute the CTMTDAY procedure.

CTM418E UNRECOGNIZED PARAMETER ON EXEC STATEMENT: expression

Explanation: The CTMTDAY procedure was executed with the following NEWDAY parameter: date. However, the date format or contents are invalid. For more information regarding the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”

The CTMTDAY procedure is not executed.

Corrective Action: Correct and re-execute the CTMTDAY procedure.

CTM419I PROCESSING MODE IS mode

Explanation: The CTMTDAY procedure was executed with one the following NEWDAY mode parameters:

  1. ORDERONLY[, date ]
  2. FORMATONLY

Special NEWDAY processing will be performed according to the mode (FORMATONLY or ORDERONLY) specified in the procedure. For more information regarding the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”

Corrective Action: No response is required.

CTM41AW DATE IGNORED IN 'FORMATONLY' REQUEST: xxxxxxx

Explanation: The CTMTDAY procedure is executed with the following NEWDAY parameter:

FORMATONLY,xxxxxx

where the operator probably intended xxxxxx as a date value. (A date is not valid with the FORMATONLY mode.)

Special NEWDAY processing is performed according to the FORMATONLY mode, ignoring xxxxxx. (For more information regarding the Control-M CTMTDAY procedure, see the INCONTROL for z/OS Administrator Guide, “CTM,” “New Day Procedure Flow.”)

Corrective Action: No response is required.

CTM422S OPEN OF USER DATE CONTROL-RECORD FAILED - DDNAME "DACHK"

Explanation: Open of the file containing the User Date Control Record failed (the DACHK DD statement).

This message is issued by the CTMCHK, CTDCHK, or CTBCHK program, which is usually activated by the New Day procedure.

Possible causes are:

  1. The DACHK DD statement is missing.
  2. The data set (member) described by the DACHK DD statement does not exist.

The CTMCHK, CTDCHK, or CTBCHK program ends with errors.

Corrective Action: Correct the JCL for the job or CLIST.

CTM424S INVALID ORIGINAL SCHEDULING DATE IN USER DATE CONTROL-RECORD (POSITIONS 1-6)

Explanation: Invalid original scheduling date in User Date Control Record (positions 1 through 6). This date should be earlier than the current installation working date. The valid format is ddmmyy or mmddyy.

Valid formats are:

  1. ddmmyy
  2. mmddyy

Possible causes are:

  1. The previous run of the CTDCHK or CTMCHK program did not finish OK.
  2. Someone has incorrectly modified the contents of the User Date Control Record (DD statement DACHK).

For more information, see the INCONTROL for z/OS Administrator Guide.

The New Day procedure ends with errors.

Corrective Action: Correct your Date Control Record (DD statement DACHK).

CTM425S INVALID POST DATE IN USER DATE CONTROL-RECORD POSITIONS 67-72

Explanation: The contents of the Date Control Record for this Daily are invalid.

Valid formats are:

  1. ddmmyy
  2. mmddyy

This message usually indicates that the User Date Control Record was incorrectly modified. The date should be earlier than or equal to the original scheduling date defined in positions 1 through 6.

The New Day procedure ends with errors.

Corrective Action: Correct the Date Control Record (the DACHK DD statement).

CTM426W {GENERAL |dailytype } "DAILY" DID NOT RUN FOR nnn DAYS

Explanation: Highlighted, unrollable message.

The difference between the current working date and the original scheduling date (positions 1 through 6 in the Date Control Record) is more than one day. The New Day procedure has not run for nnn days. A New Day procedure is expected to run once a day.

This message is usually generated due to one of the following:

  1. The computer has not been working for at least one day.
  2. The Control-M or Control-D monitor has not been working for over 24 hours.
  3. The contents of the Date Control Record were incorrectly modified for this Daily.
  4. In the case of the New Day procedure, the computer may have been IPLed with the wrong date.
  5. In the case of a User Daily, the Daily has not run for a few days.

The value of dailytype can be:

  1. GENERAL for the New Day procedure
  2. the job name of a regular User Daily job

The system action is determined by the process or procedure:

  1. For the New Day procedure, this message appears highlighted on the operator console, together with messages CTM427W or CTD427W and CTM428W or CTD428W. If the operator answers YES, processing continues, taking the RETRO parameter of each job into consideration. If the operator answers NO, the New Day procedure stops executing with an error message.
  2. For User Daily jobs, processing continues. Missions are selected according to the RETRO parameter.

Corrective Action: If the computer was IPLed with the wrong date, answer NO, correct the problem, and then activate the New Day procedure manually. Control-M or Control-D will not work until the problem is resolved.

CTM427W IS IT TRUE? (ANSWER "YES" OR "NO")

Explanation: Highlighted, unrollable message.

The last run of the New Day procedure was more than 24 hours ago. This message appears together with the CHK426W, CTM426W, or CTD426W and CHK428W, CTM428W, or CTD428W messages. For more details, see the CHK426W message.

The General New Day procedure waits for the operator response.

Corrective Action: If the computer was IPLed with the wrong date, answer NO, correct the problem, and then activate the New Day procedure manually. Control-M or Control-D will not work until the problem is resolved.

CTM428W YOUR ANSWER IS:

Explanation: Highlighted, unrollable message.

The last run of the New Day procedure was more than 24 hours ago. This message appears together with the CHK426W, CTM426W, or CTD426W and CHK427W, CTM427W, or CTD427W messages. For details, see the CHK426W message.

The New Day procedure waits for the operator response.

Corrective Action: If the computer was IPLed with the wrong date, answer NO, correct the problem, and then activate the New Day procedure manually. Control-M or Control-D will not work until the problem is resolved.

CTM429S {CTMCHK | CTDCHK | CTBCHK} ENDED WITH ERRORS

Explanation: The CTMCHK, CTDCHK, or CTBCHK program ended with errors. It is activated as part of the New Day procedure. IOA Log should contain an earlier message about the error.

The New Day procedure finishes executing with a condition code of 08.

Corrective Action: Check the IOA Log for error messages. If necessary, manually correct the Date Control Record (date-3 and date-5) to allow the next run of the User Daily job. For details, see the INCONTROL for z/OS Administrator Guide.

CTM430E POSSIBLE ABEND OF PREVIOUS DAILY RUN!

Explanation: A previous run of the same New Day procedure probably abended.

The New Day procedure terminates with errors.

Corrective Action: Correct the Date Control Record and rerun the New Day procedure. As a result of the last abend, dates 2, 3 and dates 4, 5, in the Date Control Record are not identical, but they should be. If you correct them to the values of date 3 or date 6, a rerun of the New Day procedure schedules all the jobs in the New Day procedure for the days after dates 2-5 until the date designated in date 1 (the current original scheduling date). Do not schedule the same job twice.

For more information, see the Control-D and Control-V User Guide.

CTM431I {CTMCHK | CTDCHK | CTBCHK} STARTED

Explanation: This information message indicates that the CTMCHK, CTDCHK, or CTBCHK program, which is activated by the New Day procedure, started executing.

Corrective Action: No action is required.

CTM432I {CTMCHK | CTDCHK | CTBCHK} ENDED

Explanation: This information message indicates that the CTMCHK, CTDCHK, or CTBCHK program, which is activated by the New Day procedure, ended normally.

Corrective Action: No action is required.

CTM433S DIFFERENCE BETWEEN CURRENT AND LAST RUN OF THIS DAILY IS NEGATIVE BY num DAYS

Explanation: The current working date in the computer is before the last original scheduling date of this New Day procedure.

This message is issued by the New Day procedure as a result of incorrect dates in the Date Control Record. For more details, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

The New Day procedure stops executing with an error message.

Corrective Action: Correct the contents of the Date Control Record, and rerun the Daily. If this problem occurs under the New Day procedure, call your system programmer. The problem should be resolved immediately as the Control-M or Control-D monitor will not be able to operate. Check whether the computer has been IPLed with the correct date.

CTM434W THIS DAILY HAS ALREADY BEEN RUN TODAY

Explanation: The same New Day procedure has already been run today. The current working date in the computer is equal to the last original scheduling date - positions 1 through 6 in the Date Control Record (the DACHK DD statement).

For details, see the Control-M for z/OS User Guide or the Control-D and Control-V User Guide.

Processing terminates with a return code of 8.

Corrective Action: Check the result of the run carefully for possible errors. If the Control-M or Control-D monitor is up and running, there is no need to run the New Day procedure, because it was probably started by accident. In any case, have your INCONTROL administrator look at the problem. It is possible that the computer was IPLed with the wrong date.

CTM435S OPERATOR RESPONDED "NO"

Explanation: The operator answered NO to the CHK428W, CTM428W, or CTD428W message.

The New Day procedure stops executing.

Corrective Action: Correct the problem, which is usually date-related, and rerun the New Day procedure.

CTM436S USER DATE CONTROL-RECORD IS EMPTY

Explanation: The data set described by the DACHK DD statement is empty (the New Day procedure).

The New Day procedure terminates with errors.

Corrective Action: Correct the JCL for the job and rerun it.

CTM437E INVALID DATE date SPECIFIED FOR action

Explanation: While processing a CMEM or Control-O request for the FORCEJOB, ADDCOND, or DELCOND action, the Control-M monitor encountered an invalid date.

Either the date was not a valid date, or it was not in the format specified by the DATETYP parameter in IOAPARM.

This message is followed by the WKJA59E or WKJC39E message, which identifies the failed action.

No additional action will be taken for the failed job or table order.

Corrective Action: Make sure that the date format corresponds to the DATETYP parameter in IOAPARM.

CTM437I date control record content

Explanation: This informational message is generated when Newday processing is initiated. In place of date control record content, it displays the contents of the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK in the Newday procedure. For explanations of the dates displayed, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Date Control Records and Enhanced Daily Checkpointing.”

Corrective Action: No response required.

CTM438E INTERNAL ERROR ON THE COMMUNICATION FILE. A SNAP IS PRODUCED

Explanation: Control-M has detected mismatches in the communications file while processing SHOUT to Log records from Control-O.

The affected records are not written to the IOA Log. A snap dump is written to the DADUMP DD statement.

Corrective Action: There are two possible causes for this problem. The user response varies according to the cause of the problem.

Problem Cause

User Response

The number of subsystem-to-monitor file (S2M) records is not the same in the CTMPARM member and in the FORMSUB2 job, the file allocation and format job.

Compare the CTMCPU statements in CTMPARM with the FORMSUB2 job that was run for each system. If the problem persists, save the snap (dump), prepare the Control-M monitor full output, and contact BMC Customer Support.

The value of the SMODE parameter in CMMPARM or CTOPARM is not F.

Ensure that the SMODE parameter in CMMPARM or CTOOPARM is set to F.

CTM438W REPLY 'U' TO UPDATE DATEREC TO CURRENT DAY EXECUTION OR 'E' TO END

Explanation: Highlighted, unrollable message.

An error condition is detected while processing the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK in the Newday procedure. This message is usually preceded by another error message detailing the error encountered. Some reasons that this message might be issued are:

  1. Invalid date date1 (see message CHK424S).
  2. Invalid dates date2- date7 (see message CHK43BE).
  3. The difference between the current working date and the date on which Newday was last run (date7) is negative (see message CHK433S).
  4. The current working date is equal to date1 (Newday was already run--see message CHK434W).
  5. The DATEREC member is empty (see message CHK436S).
  6. An attempt was made to run the New Day procedure twice in the same day (see message FRM454E).
  7. date7 is later than date1 (see message FRM455S).
  8. date7 is more than 28 days in the past (see message FRS476S or JOB50S).
  9. For an explanation of the dates in question, see INCONTROL for z/OS Administrator Guide, “CTM,” “Date Control Records and Enhanced Daily Checkpointing.”

The Newday procedure waits for the operator response.

Corrective Action: Review the preceding error messages to determine the actions necessary to correct the problem. If the problem can be corrected by setting the dates in the DATEREC record to the current working date, enter U. After Control-M automatically updates the DATEREC record, Newday processing resumes.

Otherwise, enter E and then correct the problem manually. For example, if the computer was IPLed with the wrong date, enter E, correct the computer date, and then reactivate the New Day procedure manually.

CTM439E MISSING JOB jobName IN TABLE tableName IN lib

Explanation: The jobName job was not found in the tableName table.

A FORCEJOB request for the jobName job in the tableName table failed.

This message is followed by the WKJA59E message, which contains more details about the error.

No additional action will be taken for the failed job order.

Corrective Action: Check that the job exists in the indicated scheduling table. For further actions, see the WKJA59E message.

CTM439W REPLY 'C' TO CONTINUE, 'U' TO UPDATE DATEREC TO CURRENT DAY EXECUTION, OR 'E' TO END

Explanation: Highlighted, unrollable message.

Following initiation of the Newday procedure, Control-M issued message CHK426W (warning that more than a day has passed since the previous run of Newday).

The Newday procedure waits for operator response.

Corrective Action: Examine the explanation of message CHK426W to help determine the situation and then respond according to one of the following situations:

CTM43AI NEWDAY EXECUTION CONTINUING WITH ODATE odate

Explanation: This informational message is generated when the response to message CTM438W or CTM439W was U. It informs the user that Newday processing continues, using odate as the current working date.

The Newday procedure resumes.

Corrective Action: No response needed.

CTM43BE DATE CONTROL RECORD CONTAINS AN INVALID DATE AT POSITION col

Explanation: During Newday initiation, an invalid date was detected in the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK. The date in error is in column col of the record. (For explanations of the dates displayed, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Date Control Records and Enhanced Daily Checkpointing.”)

Message CHK438 is generated.

Corrective Action: Respond to message CHK438.

CTM43CI CONTENTS OF DATE CONTROL RECORD:

Explanation: This message serves as a header for message CTM437I, which follows.

Corrective Action: No response needed.

CTM43DW REQUESTED ODATE IS odate

Explanation: Highlighted, unrollable message.

This message is issued in response to any of the following operator commands:

  1. F CONTROLM,NEWDAY=hhmm [ ,date ]
  2. F CONTROLM,NEWDAY= hhmm ,ORDERONLY [ , date]
  3. F CTMTROLM,NEWDAY= hhmm ,RERUN
  4. S CTMTDAY,NEWDAY=date
  5. S CTMTDAY,NEWDAY='ORDERONLY, date '

For more information, see the INCONTROL for z/OS Administrator Guide, “CTM,” “Special Newday Parameters.”

Message CTM43GW is issued.

Corrective Action: Respond to message CTM43GW as instructed.

CTM43EW JOB jobName (OID=orderId) HUNG IN SUBMISSION

Explanation: The jobName job is used to trigger a Control-O or CMEM ON JOBARRIV rule that contains a DO FORCEJOB command. However, the jobName job has been hung in submission status for several seconds.

Control-M does not order and submit the job identified in the DO FORCEJOB command.

Corrective Action: Consider manually forcing the job identified in the DO FORCEJOB command.

CTM43FI TRIGGER JOB jobName (jobId) NOT FORCED

Explanation: The jobName job is used to trigger a Control-O or CMEM ON JOBARRIV rule that contains a DO FORCEJOB command. However, the jobName job is one of the following:

  1. a cyclic job found on the Active Jobs file
  2. in Hung in Submission status
  3. currently being handled by one of the local sysplex monitors

Control-M does not order and submit the job identified in the DO FORCEJOB command.

Corrective Action: Do the following:

  1. Check to see if JES is hung. If it is, find out why, and address that problem.
  2. Consider how to act in relation to
  3. the jobName job, that is, the job that is hung
  4. the job identified in the DO FORCEJOB command

CTM43GW REPLY 'C' TO CONTINUE OR 'E' TO END

Explanation: Highlighted, unrollable message.

Upon entry of the F CONTROLM,NEWDAY=hhmm,date command, message CTM43DW displayed the ODATE entered. The current message asks the operator to either confirm that the Newday procedure continue with the specified ODATE or not continue.

The Newday procedure waits for operator response.

Corrective Action: One of the following responses:

  1. C --confirm Newday execution using the ODATE displayed by message CTM43DW. (Dates in the first record of the DATEREC member in the CTM PARM library pointed to by ddname DACHK are not modified.)
  2. E --cause the NEWDAY command to be ignored.

CTM440I CONTROL-M MONITOR IS READY TO RECEIVE CMEM REQUESTS

Explanation: This information message indicates that the CMEM facility in the Control-M monitor was successfully initialized and the Control-M monitor is ready to accept requests from Control-O or from CMEM subsystem functions.

Corrective Action: No action is required.

CTM441E CONTROL-M MONITOR CMEM FACILITY IS DEACTIVATED AS A RESULT OF A FAILURE

Explanation: Highlighted, unrollable message.

A severe error has occurred while processing requests from one of the following:

  1. Control-O
  2. CMEM subsystem functions
  3. Control-M DO FORCEJOB

Information about the error that caused the deactivation of the On Spool Jobs Facility was previously displayed on the operator console.

Control-M monitor stops processing requests from:

  1. Control-O
  2. CMEM subsystem functions
  3. Control-M DO FORCEJOB.

Other parts of Control-M monitor will not be affected.

Corrective Action: Look for previous error messages. Correct the error, shut down the Control-M monitor and start it again.

CTM442E ERROR WHILE LOADING CTMJOB\CTMMEM FOR CMEM PROCESSING

Explanation: Highlighted, unrollable message.

The CTMJOB or CTMMEM modules could not be loaded by the Control-M monitor for one of the following reasons:

  1. There was insufficient storage.
  2. The modules could not be found in the libraries specified in the STEPLIB DD statement or in the Linklist.

Control-M monitor will not process requests from:

  1. Control-O
  2. CMEM subsystem functions
  3. Control-M DO FORCEJOB

Corrective Action: Correct the error, shut down the Control-M monitor and start it again.

CTM443E OPEN ERROR OCCURRED DURING CMEM PROCESSING, DSN=dsn

Explanation: The Control-M monitor has encountered an open error while processing CMEM or Control-O requests.

An open error occurred on one of the Control-M communication data sets. Possible causes are:

  1. An incorrect communication file was defined.
  2. A security product failed the OPEN request.

Control-M monitor stops processing CMEM or Control-O requests.

Corrective Action: Do the following:

  1. Check that CTMPARM points to the correct communication file.
  2. Check the dsn communication file, and make sure that it is properly defined, formatted, and cataloged.
  3. Make sure that no restrictions are imposed by MVS, a security package, and so on.
  4. Correct the error, shut down the Control-M monitor and start it again.

CTM444E I/O ERROR OCCURRED DURING CMEM PROCESSING, DSN=dsn

Explanation: The Control-M monitor has encountered an I/O error while processing CMEM or Control-O requests.

An I/O error occurred on one of the Control-M communication data sets.

Control-M monitor stops processing CMEM or Control-O requests.

Corrective Action: Do the following:

  1. Check the dsn communication file, and make sure that it is properly defined and formatted.
  2. Check that CTMPARM points to the correct communication file. If the file and CTMPARM appear correct:
  3. After correcting the error, stop the Control-M monitor and start it again.

CTM445E DYNAMIC ALLOCATION ERROR, RC=rc, REASON CODE=rsn, DSN=dsn

Explanation: The Control-M monitor has encountered a dynamic allocation error while processing CMEM or Control-O requests.

A dynamic allocation error occurred on one of the Control-M communication data sets. Possible reasons for this failure include:

  1. The dsn communication file is not cataloged on the correct disk.
  2. The dsn communication file is cataloged in a catalog which cannot be accessed by the Control-M monitor.
  3. The wrong communication file name, or no communication file name, was specified in IOACPRM.
  4. The MVS allocation exit failed the allocation request.
  5. A security product failed the allocation.

For information about the return code (rc) and the reason code (rsn) see the IBM manual MVS Programming: Authorized Assembler Services Guide. Reallocate and format or re-catalog the file if necessary.

The Control-M monitor stops processing CMEM and Control-O requests.

Corrective Action: Check the definitions in CTMPARM, and correct them as necessary. After the error is corrected, stop the Control-M monitor and start it again.

CTM446W SYSPLEX TABLE MISSING - SYSTEM LOGGER INTERFACE DISABLED

Explanation: Control-M attempted to read the Sysplex Table and failed.

Control-M could not find the Sysplex Table or encountered errors while reading the Sysplex Table. This could be due to one of the following:

  1. The Sysplex Table is not present in the STEPLIB concatenation of load libraries.
  2. The Sysplex Table has an invalid internal format.
  3. The Sysplex Table has no valid, active table entries.

Control-M attempts to allocate, open and use the subsystem-to-monitor (S2M) communication files to implement CMEM-Control-M communication.

Corrective Action: Check why the Sysplex Table is not in the load library or has an invalid format. Correct the problem and recycle Control-M.

CTM447E SYSTEM LOGGER REQUEST req FAILED: R15=r15 RETURN=rc REASON=rsn

Explanation: A System Logger request failed.

One of the following System Logger requests failed:

Request

Explanation

DEFCFS, IXGINVNT

Define coupling facility structure

DEFLGS, IXGINVNT

Define log stream

CONLGS, IXGCONN

Connect to log stream

WRITEL, IXGWRITE

Write a log stream log block

BRWSEL, IXGBRWSE

Browse a log stream log block

DELETL, IXGDELET

Delete a log stream log block

DISLGS, IXGCONN

Disconnect from log stream

DELLGS, IXGINVNT

Delete log stream

DELCFS, IXGINVNT

Delete coupling facility structure

r15 is provided by Control-M and is one of the following:

R15

Explanation

08

Minor System Logger request error

12

Intermediate System Logger request error

16

Major System Logger request error

20

Permanent System Logger request error

24

Internal Control-M error

28

Operating system does not support System Logger interface

32

Internal Control-M error

The return code rc and the reason code rsn are documented in the IBM manual MVS Programming: Assembler Services Reference. Check that publication for the system action relevant to the return code and reason code in the message. Each System Logger request is in a separate section of the guide. The return and reason codes are described in the topic “Return and Reason Codes” for each System Logger request.

Corrective Action: When a System Logger error occurs, check the system log or the console that displays error messages for the IXGLOG System Logger address space for further details. If the problem persists, prepare the Control-M monitor full output and contact BMC Customer Support.

CTM448E CMEM LOST num TRANSACTIONS FROM THE CPU WITH SMFID=smfid

Explanation: Control-M was down, or stopped processing CMEM and Control-O requests.

During the time that the Control-M monitor was inactive (due to a problem or daily maintenance), the CMEM subsystem functions or Control-O wrote to the Communication file more records than its size allowed. Therefore the oldest CMEM or Control-O requests were overwritten and lost.

No additional action is performed.

Corrective Action: Take one of the following steps in order to prevent this situation from recurring:

  1. Make sure that the Control-M monitor will not remain inactive for a long time.
  2. Increase the size of the Communication files.

CTM449E MISSING TABLE tableName IN lib.

Explanation: The tableName table was not found in the specified library, or the table was empty.

A FORCEJOB request for a scheduling table or a specific job failed.

This message is followed by the WKJA59E message, which contains more details about the error.

This message may also be issued in the following situations:

  1. the library in which the member resides is being compressed
  2. the disk volume on which the library resides on is being reorganized or defragmented

These actions should be avoided during job ordering periods.

No additional action is taken for the failed job or table order.

Corrective Action: Check that the table exists in the indicated library. For further actions, see the WKJA59E message.

CTM44AI SYSTEM LOGGER INTERFACE ACTIVATED

Explanation: This information message indicates that Control-M has successfully initialized the System Logger interface.

Control-M can now begin communicating with CMEM.

Corrective Action: No action is required.

CTM44BE SYSTEM LOGGER NOT SUPPORTED ON THIS OPERATING SYSTEM

Explanation: Control-M cannot utilize the System Logger interface on the host operating system.

The host operating system does not support the System Logger interface.

The CMEM facility is deactivated.

Corrective Action: Change the parameters in the appropriate IOA PARM library members to use the Subsystem-to-Monitor (S2M) communication files to implement communication between CMEM or Control-O and Control-M.

CTM44CI ATTEMPTING TO RECONNECT TO MVS SYSTEM LOGGER

Explanation: Control-M has detected an MVS System Logger error, and is attempting to reconnect to the MVS System Logger.

Control-M tries several times to reconnect to the MVS System Logger.

Corrective Action: No action is required.

CTM44DE ATTEMPT TO RECONNECT TO MVS SYSTEM LOGGER FAILED

Explanation: Control-M detected an MVS System Logger error, and attempted several times to reconnect to the MVS System Logger, without success.

Corrective Action: No action is required.

CTM44EE MVS SYSTEM LOGGER ERROR - CMEM FEATURE DISABLED

Explanation: Control-M detected an MVS System Logger error. Either this error was so severe as not to be recoverable, or Control-M attempted several times to reconnect to the MVS System Logger, without success.

Control-M has stopped attempting to reconnect to the MVS System Logger. The CMEM facility is deactivated.

Corrective Action: If and when the MVS System Logger becomes operational, stop and restart the Control-M monitor.

CTM44FI TRIGGER JOB jobName (jobId) FOUND ON AJF. JOB NOT FORCED

Explanation: This information message refers to a Control-O or CMEM ON JOBARRIV or ON JOBEND rule with a DO FORCEJOB command. The job used to trigger this DO FORCEJOB was found on the Active Jobs file.

Control-M does not order and submit the DO FORCEJOB.

Corrective Action: No action is necessary.

CTM44GA REPLY "ABORT", "CONTINUE", OR "RETRY"

Explanation: After displaying a CMEM-related error message, Control-M disables communication between CMEM or the Control-O monitor and Control-M. Control-M then displays message CTM44GA giving the user the choice of how to continue.

The subtask is suspended until a response to this message is received.

Corrective Action: Enter one of the following responses:

  1. ABORT - terminate the Control-M monitor
  2. CONTINUE - disable communication between CMEM or the Control-O monitor and Control-M, but allow the Control-M monitor to continue processing
  3. RETRY - retry the failed dynamic allocation request

CTM450S OPEN OF WORK FILE FAILED - DDNAME "DAJOBLST". PLEASE CHECK THE CONTROL-M MESSAGES AND CODES MANUAL

Explanation: The New Day procedure was unable to open the file pointed to by the DAJOBLST DD name for update.

After reading the list of CDAM files to be deleted from the file pointed to by DAJOBLST, the New Day procedure empties the file and writes one record indicating that there are no more entries. Possible causes are:

  1. file not found on the disk
  2. incorrect security authorization

Corrective Action: Determine the reason for the problem, and correct it. Reinstall Control-M/Restart.

CTM452I FORMATTING OF activeFile FILE STARTED

Explanation: This information message indicates that the Control-M Active Jobs file (AJF) or the Control-D Active Missions file (AMF) is currently being formatted.

Corrective Action: No action is required.

CTM453S OPEN OF DATES CONTROL-RECORD FAILED. DDNAME "DACHK"

Explanation: Open of the Control-M or Control-D Date Control record failed in the DACHK DD statement). This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program as part of the New Day procedure. Possible causes are:

  1. The DACHK DD statement is missing.
  2. The data set (member) described by the DACHK DD statement is not the Control-M or Control-D Date Control Record.

Corrective Action: Correct the JCL for the New Day procedure.

CTM454E FORMAT (format_pgm) ALREADY RUN TODAY

Explanation: An attempt was made to run the New Day procedure twice in the same day. The New Day procedure issues format_pgm. This program should not run more than once a day.

Possible values of format_pgm:

  1. CTMFRM - formats the Active Jobs file (AJF) in Control-M
  2. CTDFRM - formats the Active Missions file (AMF) in Control-D

The AJF or AMF is not formatted, but the New Day procedure continues to execute other programs in the program list.

Corrective Action: Check why the New Day procedure is being run twice, and whether jobs or missions were accidentally ordered twice because the General Date Control Record was erroneously modified.

CTM455S LAST FORMAT DATE GREATER THAN ORIGINAL SCHEDULING DATE IN CONTROL-M DATES CONTROL-RECORD

Explanation: The last format date is later than the original scheduling date in the Control-M Date Control record or the Control-D Date Control record. The New Day procedure issues this message. For more details, see the appropriate user guide.

New Day processing stops.

Corrective Action: Correct the Control-M or Control-D Date Control record, and run the New Day procedure again.

CTM456S OPEN OF activeFile FILE FAILED. DDNAME "ddName "

Explanation: Open of the Control-M Active Jobs file (AJF) or the Control-D Active Missions file (AMF) defined in the ddName DD statement failed. The New Day procedure calls the program that issues this message.

In Control-M, ddName is DACKPT and activeFile is the Active Jobs file (AJF).

In Control-D ddName is DAAMF and activeFile is the Active Missions file (AMF).

Possible causes are:

  1. The ddName DD statement is missing.
  2. The data set described by the ddName DD statement is not the AJF or the AMF.
  3. The data set described by the ddName DD statement is the AJF or the AMF, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure, and rerun it.

CTM457S OPEN OF BACKUP FILE FAILED. DDNAME "DABKUP"

Explanation: Open of backup file for the Active Jobs file (AJF) or Active Missions file (AMF) defined in the DABKUP DD statement failed. This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is usually activated as part of the New Day procedure.

Possible causes are:

  1. The DABKUP DD statement is missing.
  2. The data set described by the DABKUP DD statement is not the Active Jobs Backup file or Active Missions Backup file.
  3. The data set described by the DABKUP DD statement is the Control-M Active Jobs Backup file or the Control-D Active Missions Backup file, but of another Control-M or Control-D monitor, or of a different version of Control-M or Control-D.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure, and rerun it.

CTM458S ERROR IN activeFile - RECORD 0. SHOULD BE FORMAT OR FREE

Explanation: Record 0 of the activeFile file contains incorrect data. This error message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is usually activated as part of the New Day procedure.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D, activeFile is the Active Missions file (AMF).

Possible causes are:

  1. The activeFile file is corrupt.
  2. The data set described by the DACKPT DD statement (Control-M) or the DAAMF DD statement (Control-D) is not the activeFile file, but is very similar to it.

Program execution stops with a condition code of 08.

Corrective Action: Check the validity of the data set described by the DACKPT or DDAMF DD statement. If necessary, correct the JCL, and rerun the New Day procedure.

If activeFile is corrupt, use a standard copy utility, like IEBGENER, to copy activeFile, and send it to BMC Customer Support. If necessary, run the FORMCKP utility to reformat the Active Jobs file or the CTDFRAMF utility to reformat the Active Missions file. However, these utilities also erase all the jobs or missions in the respective files.

CTM459I activeFile IS RESTORED FROM BACKUP

Explanation: This information message indicates the beginning of a rerun of the New Day procedure after an earlier abend during the format of activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D activeFile is the Active Missions file (AMF).

activeFile is restored from the appropriate backup file, and processing continues normally.

Corrective Action: No action is required.

CTM460S DATE CONTROL-RECORD IS EMPTY

Explanation: The DACHK DD statement describes an empty data set or member. For more information, see the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Correct the Control-M or Control-D Date Control Record and run the New Day procedure again.

CTM461S ERROR WHILE FORMATTING IOA CONDITIONS FILE

Explanation: I/O error while formatting the IOA Conditions file.

Possible causes are:

  1. The data set described by the DARESF DD statement is not the IOA Conditions file.
  2. An I/O error occurred while reading the IOA Conditions file.

Program execution stops with a condition code of 08.

Corrective Action: Correct and run the New Day procedure again. In case of an I/O error, you may need to recreate the IOA Conditions file. This erases all the conditions from the file.

CTM462S INVALID LAST FORMAT DATE IN DATE CONTROL RECORD

Explanation: Invalid format of last format date in the Date Control Record. This message is issued by the CTMFRM or CTDFRM program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy. Possible causes are:

For more information, see the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

CTM463S INVALID ORIGINAL SCHEDULING DATE IN DATE CONTROLRECORD

Explanation: Invalid original scheduling date in the Date Control Record. This message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy.

Possible causes are:

For more information, see the sections that describe NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

CTM464S FILE ALLOCATED TO DDNAME "ddName " IS NOT YOUR activeFile

Explanation: The data set described by the ddName DD statement is not the file specified by activeFile.

In Control-M, ddName is DACKPT and activeFile is the Active Jobs file (AJF).

In Control-D ddName is DAAMF and activeFile is the Active Missions file (AMF).

Possible causes are:

Program execution stops with a condition code of 08.

Corrective Action: Correct the problem in the data set name indicated by the ddName DD statement, and run the New Day procedure again.

CTM465S FILE ALLOCATED TO DDNAME "DABKUP" IS NOT A BACKUP OF activeFile

Explanation: The data set described by the DABKUP DD statement is not a backup of activeFile.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D, activeFile is the Active Missions file (AMF).

Possible causes are:

Program execution stops with a condition code of 08.

Corrective Action: Correct the Control-M Date Control Record and rerun the affected procedure.

CTM466S NEED MORE MEMORY TO FORMAT activeFile

Explanation: There is not enough memory to format the activeFile file.

In Control-M, activeFile is the Active Jobs file (AJF) or the History file (HST).

In Control-D, activeFile is the Active Missions file (AMF).

Program execution stops with a condition code of 08. Control-M and Control-D monitors will not start after this error.

Corrective Action: To enable monitors to start, set REGION=0M and rerun the affected procedure. If the REGION is already set to 0M, then ensure that the MVS exit IEFUSI allows sufficient virtual storage memory to be allocated above the 16M line. For example, since each record of the above files requires 1024 bytes of storage, a file containing 200,000 records requires 200M of storage above the line.

CTM468I FORMATTING OF activeFile ENDED

Explanation: This information message indicates that the New Day procedure finished formatting the activeFile file. This message is issued by the CTMFRM (Control-M) or CTDFRM (Control-D) program, which is activated as part of the New Day procedure.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D, activeFile is the Active Missions file (AMF).

Corrective Action: No action is required.

CTM469S OPEN OF IOA LOG FILE FAILED

Explanation: Open of IOA Log file failed. The message is produced by the New Day procedure. Possible causes are:

  1. The DALOG DD statement is missing.
  2. The file allocated to the DALOG DD statement is not the IOA Log file.
  3. The file allocated to the DALOG DD statement is the IOA Log file, but it is of a different version or of a different IOA monitor.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL and run the Daily again.

CTM470S ERROR WHILE FORMATTING THE activeFile, FILE WAS NOT FORMATTED

Explanation: An error occurred during formatting of the activeFile file. The New Day procedure issues this message.

In Control-M, activeFile is the Active Jobs file (AJF).

In Control-D, activeFile is the Active Missions file (AMF).

Program execution stops with a condition code of 08.

Corrective Action: Look for a previous message that describes the type of error. Correct it and rerun the New Day procedure.

CTM471S OPEN OF IOA CONDITIONS FILE FAILED. DDNAME "DARESF"

Explanation: Open of IOA Conditions file failed (the DARESC DD statement). This error message is issued by either the CTMFRM or the CTDFRM program, which is activated as part of the New Day Procedure. Possible causes are:

  1. The DARESC DD statement is missing.
  2. The data set described by the DARESC DD statement is not the IOA Conditions file.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the Daily Subsystem and rerun it.

CTM472S OPEN OF IOA SYNCHRONIZATION FILE FAILED. DDNAME "DASINC"

Explanation: Open of IOA Synchronization file failed in the DASINC DD statement. This error message is issued by either the CTMFRM or the CTDFRM program, which is activated as part of the New Day procedure. Possible causes are:

  1. The DASINC DD statement is missing.
  2. The data set described by the DASINC DD statement is not the IOA Synchronization file.
  3. The data set described by the DASINC DD statement is an IOA Synchronization file, but it is of another Control-M or Control-D monitor, or of a different Control-M or Control-D version.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure and rerun it.

CTM475S INVALID LAST FORMAT DATE IN DATE CONTROL-RECORD

Explanation: Invalid format of last format date in the Date Control record. This message is issued by either the CTMFRM or the CTDFRM program, which is activated as part of the New Day procedure. The valid format is ddmmyy or mmddyy. Possible causes are:

  1. The record described by the DACHK DD statement is not the Control-M or Control-D Date Control record.
  2. Someone modified the contents of the Date Control Record incorrectly.

For more information, see the sections on NEW DAY processing in the Control-M and Control-D chapters of the INCONTROL for z/OS Administrator Guide.

Program execution stops with a condition code of 08.

Corrective Action: Do one or both of the following, as necessary:

  1. Correct the JCL for the New Day procedure, and rerun it.
  2. Correct the format date in the Date Control Record.

CTM476S LAST FORMAT DATE IN DATE CONTROL-RECORD WAS MORE THAN 28 DAYS AGO

Explanation: The difference between the current working date (date-1) and the last format date in the Date Control Record is greater than 28 days. Possible causes are:

  1. Someone modified the contents of the Date Control Record incorrectly.
  2. The Control-M or Control-D monitor has not been used for more than 28 days. Correct the date to “yesterday.”

Program execution stops with a condition code of 08.

Corrective Action: Correct the dates in the Date Control Record in the DACHK DD statement, and rerun the Daily Subsystem.

CTM477S FILE ALLOCATED TO DDNAME "DASINC" IS NOT YOUR IOA SYNCHRONIZATION FILE

Explanation: The data set described by the DACNDF DD statement is not the required IOA Conditions file. The CTMFRM or CTDFRM program issues this error message as part of the New Day procedure when one of the following occurs:

  1. The file allocated to the DACNDF DD statement is not the IOA Conditions file.
  2. The file allocated to the DACNDF DD statement is an IOA Conditions file, but for a different version, or for a different Control-M or Control-D monitor.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL for the New Day procedure and rerun it.

CTM478I FORMATTING OF IOA CONDITIONS FILE STARTED

Explanation: This information message indicates that the formatting of the IOA Conditions file was started by the New Day procedure. The CTMFRM or CTDFRM program clears all the conditions from the day following the last formatting date until the next working date, that is, the first date in the General Date Control Record.

Corrective Action: No action is required.

CTM479I FORMATTING OF IOA CONDITIONS FILE ENDED

Explanation: This information message indicates that the New Day procedure formatted the IOA Conditions file. The CTMFRM or CTDFRM formatting program called by the New Day procedure ended.

Corrective Action: No action is required.

CTM480S ERROR WHILE FORMATTING IOA CONDITIONS FILE.

Explanation: An error occurred while formatting the IOA Conditions file by the New Day procedure. An earlier error message describes the type of error.

Program execution stops with a condition code of 08.

Corrective Action: Check the IOA Log or the utility output for a previous message concerning the error.

CTM481S OPEN OF WORK FILE FAILED - DDNAME "DAJOBLST". DELETE OF ARCHIVED SYSOUTS FAILED

Explanation: Open for the DAJOBLST file failed during the execution of the New Day procedure.

This error message is issued by the CTMDAS program, which is usually activated as part of the New Day procedure. The DAJOBLST DD statement is probably missing.

Program execution stops with a condition code of 16.

Corrective Action: Make sure that CTR (CONTROL-M/Restart) is set to Y in IOAPARM, in the PRODUCTS section.

CTM482S INIT OF RES FILE FAILED

Explanation: The New Day procedure failed to initialize the Control-M Resources file. An accompanying message identifies the reason for the failure.

The New Day procedure stops with an error code of 12.

Corrective Action: Check the accompanying message to determine the reason for the problem, and correct the problem accordingly.

CTM484I FORMAT OF RESOURCE FILE HAS STARTED

Explanation: This information message indicates that the Control-M Resources file is currently being formatted. This procedure is usually part of the New Day procedure.

Corrective Action: No action is required.

CTM488I FORMAT OF RESOURCE FILE HAS ENDED

Explanation: This information message indicates that formatting of the new Control-M Resources file is complete and the resource is available.

Corrective Action: No action is required.

CTM48CI Preceding clear history did not complete. Process may run longer.

Explanation: During the AJF compression process, Control-M detected that the last clear process of the history file (HST), which followed the preceding AJF compression, did not successfully complete or did not run at all.

The AJF compression process continues, but the process might take longer than usual to complete.

Corrective Action: Usually the issue is resolved automatically by the next run of the history clear process, which either runs by default as part of the Control-M Daily run (step CLRHIST, program CTMHSC) or as a standalone utility (CTMHCLN). Make sure that the clear history process is included in the Control-M Daily run, or that the CTMHCLN utility runs on a daily basis. Make sure the process ends without errors.

CTM491S OPEN OF DDNAME "DA34F" FAILED

Explanation: Open of the file containing the operator commands failed (the DA34F DD statement). The CTM34F program is usually activated as part of the New Day procedure. Possible causes are:

  1. The DA34F DD statement is missing.
  2. The data set described by the DA34F DD statement does not exist, or cannot be opened for sequential read, or record length is not 80.

Program execution stops with a condition code of 08.

Corrective Action: Correct the JCL of the job. For more information, see the INCONTROL for z/OS Administrator Guide.

CTM493I {IOA34F | CTM34F} STARTS EXECUTING COMMANDS

Explanation: This information message indicates that the IOA34F or CTM34F program is ready to execute the operator commands from the supplied list. This program is usually activated as part of the New Day procedure.

Corrective Action: No action is required.

CTM495I {IOA34F | CTM34F} FINISHED EXECUTING COMMANDS

Explanation: This information message indicates that the IOA34F or CTM34F program finished executing the list of operator commands. This program is usually activated as part of the New Day procedure.

Corrective Action: No action is required.

CTM496E PROGRAM {IOA34F | CTM34F} IS NOT APF-AUTHORIZED

Explanation: The MVS operating system rejected the operator commands issued by the CTM34F program. The CTM34F program should reside in an APF-authorized library and must be link edited with the AC attribute set to 1 in order to be able to issue operator commands.

The issued commands are rejected. The CTM34F program terminates with a condition code of 08.

Corrective Action: The IOA34F or CTM34F program already has the AC attribute set to 1. The INCONTROL administrator should verify that the library in which CTM34F resides is APF-authorized.

CTM497S VM HOST NOT AVAILABLE

Explanation: An attempt was made to issue a VM command while MVS was not running under VM. A command whose name starts with the prefix CP was passed to the IOAOPR utility. This prefix signals to Control-M that the command is intended for a host VM operating system, but the IOAOPR utility detected that no VM environment was available.

Corrective Action: Verify that a VM environment is running before issuing VM CP commands.

CTM498S LOAD OF MODULE IOAVMC FAILED

Explanation: The IOAOPR utility could not load the IOAVMC module.

Corrective Action: Verify that the IOAVMC module resides in the STEPLIB library.

CTM499E INVALID VALUE "val " FOR "RESPONSE" KEYWORD

Explanation: The user entered a value other than YES or NO for the Response keyword.

Corrective Action: Correct the entry to either YES or NO.

Parent Topic

CTM messages