Messages CTD200 through CTD2xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CTD200I CTDCBTR STARTED.

Explanation: This information message indicates that the CTDCBTR Control-D utility has started.

Corrective Action: No action is required.

CTD201I CTDCBTR ENDED OK.

Explanation: This information message indicates that the CTDCBTR Control-D utility has ended normally.

Corrective Action: No action is required.

CTD202S INSUFFICIENT MEMORY FOR CONTROL-D MONITOR.

Explanation: Insufficient memory for the initiation of Control-D monitor.

Control-D monitor will shut down.

Corrective Action: Increase the Control-D monitor region size.

CTD202S CTDCBT ENDED WITH ERRORS.

Explanation: The CTDCBTR Control-D utility ended with errors.

The utility stops executing.

Corrective Action: Check the job sysout for any error messages, and correct the problem accordingly. Rerun the job.

CTD203S DELETE FAILED FROM BTR FILE

Explanation: The CTDCBTR utility failed to delete a record from the Bundle Tracking (BTR) file.

The CTDCBTR utility terminates.

Corrective Action: Check for other messages relating to this problem, and correct accordingly. Rerun the utility.

CTD204S PROBLEM DETECTED IN UTILITY CTDCBTR PARAMETERS.

Explanation: A problem was detected in the input parameters of the CTDCBTR utility. This message can be triggered by a number of causes, for example, if no parameters were specified at all, or if the DABTRIN DD statement is absent.

The CTDCBTR utility ends.

Corrective Action: Check the parameters specified for the utility, and check for a DABTRIN DD statement. Correct the input accordingly and rerun the job.

CTD205I NUMBER OF DELETED RECORDS: num

Explanation: This information message indicates the number of records deleted by the CTDCBTR utility.

Corrective Action: No action is required.

CTD206I INPUT CARDS: inputStmts.

Explanation: This information message displays the input parameters which were specified in the JES log of the job for the CTDCBTR utility.

Corrective Action: No action is required.

CTD207E REDUNDANT PARAMETER: inputStmt.

Explanation: A superfluous parameter was specified for the CTDCBTR utility.

The CTDCBTR utility ends.

Corrective Action: Remove the superfluous input parameter and rerun the utility.

CTD229S OPEN FAILED FOR DDNAME "DARES".

Explanation: Open of a debugging output file failed (the DARES DD statement).

This is probably because the DARES DD statement is missing in the Control-D procedure.

Control-D monitor will shut down with error message.

Corrective Action: Correct the JCL for the Control-D monitor procedure and start it again.

CTD230S OPEN FAILED FOR DDNAME "DARESC" OR "DASINC".

Explanation: Open of IOA Conditions file failed (the DARESC DD statement or the DASINC DD statement).

Possible causes are:

• The DARESC DD statement is missing.
• The DASINC DD statement is missing.
• The data set described by the DARESC DD statement is not the IOA Conditions file.
• The data set described by the DASINC DD statement is not the IOA Conditions synchronization file.
• The data set described by the DARESC DD statement is the IOA Conditions file, but it is of a different version or of a different Control-D monitor.

Control-D monitor shuts down with error message.

Corrective Action: Correct the JCL for the Control-D procedure, and start the procedure again.

CTD241W OUTPUT CONDITION cond_date NOT UPDATED - NO MORE SPACE. NOTIFY THE IOA ADMINISTRATOR.

Explanation: Highlighted, unrollable message.

No more space to add output conditions to the conditions file. The date is in mmdd format.

The record for that specific day of the month is full. For example, if a condition with date reference of January 3rd cannot be added, an entry in the Conditions file that contains conditions for January 3rd, February 3rd, March 3rd, and so on, is full.

The condition is not added, and a highlighted message is displayed on the operator console. Control-D continues to function, but missions that depend on the condition are not submitted.

Corrective Action:

Immediate action:

1. Enter Control-D Online Facility Resource Map (screen 4). By changing the date range limit, look for conditions with the same day (but of a different month) as the condition that could not be added, and delete them manually - providing that they are not needed.
2. Add the failing condition manually in order to maintain production flow.
3. Report the event to your system programmer.

Long term action:

1. You should run the IOACLCND Control-M utility more often.
2. You may want to increase the record length of the IOA Conditions file. For more information on how to do this, see the section on expanding IOA files in the INCONTROL for z/OS Administrator Guide.

CTD256E ERROR WHILE READING SYSOUT FROM SPOOL OR FROM CDAM FILES

Explanation: Internal Control-D error.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Look for additional messages on the IOA Log. Call BMC Customer Support for assistance.

CTD260E ERROR IN ACTIVE USER REPORTS LIST FILE. USER UPDATE FAILED.

Explanation: The update to the Active User Report List file failed. Perhaps the Active User Report List file is full or the Index component is corrupted.

The status of this decollating mission is set to ENDED NOTOK.

Corrective Action: Examine relevant CTDU99E and CTD908S messages, take appropriate corrective action, and then rerun the decollating mission. Use the CTDDIG utility to check the integrity of the user file. If the problem persists, contact BMC Customer Support.

CTD261E SEVERE ERROR WHILE LOCATING SYSOUT PARAMETERS FROM JES

Explanation: Highlighted, unrollable message.

An internal test of the JES control blocks failed.

Control-D retrieves data set characteristics from the JES2 control blocks. These blocks are release-dependent. To avoid abends, Control-D tests the blocks at the beginning of its process. If the test fails, the CTD261E message is displayed.

This error is often caused by MSGCLASS for started tasks being set to PURGE or DUMMY. Control-D uses the settings of MSGCLASS for started tasks for test SYSOUT.

Snaps are produced and put in the DADUMP DD statement. Control-D continues to process without retrieving characteristics from the JES Control Blocks.

Corrective Action: Do the following:

1. Ensure that the MSGCLASS output class for the started task (STC) in the JES2PARM member of the SYS1.PARMLIB library is not set to PURGE or DUMMY.
2. If MSGCLASS is set correctly, collect the relevant snaps from the DADUMP DD statement and contact BMC Customer Support.

CTD266E CTDPARM GENOTFND SETTING INVALID FOR CURRENT ENVIRONMENT
CTD266I GENERIC DECOLLATION PROCESSING STOPPED.

Explanation: The setting of the GENOTFND parameter in CTDPARM is not supported by the MVS/JES configuration of the computer. These two messages are always issued together.

Some options of the GENOTFND parameter in CTDPARM are valid only in certain MVS/JES configurations. For example, JES3 supports only CLASS and DELETE as values for the GENOTFND parameter.

For a description of the GENOTFND parameter, see the Control-D chapter of the INCONTROL for z/OS Installation Guide.

The unmatched sysout file remains unchanged.

Corrective Action: Do the following:

1. Manually remove the problematic sysout from the generic class.
2. Correct the GENOTFND parameter in CTDPARM.
3. Restart the Control-D monitor after compiling CTDPARM.

CTD26AE MISSION ABENDED S nnn U nnnn.

Explanation: Highlighted, unrollable message.

The decollation mission abended with the system code or the user code or both these codes displayed in this message.

The decollation mission finishes NOTOK. Control-D tries to process other missions.

Corrective Action: If Control-D cannot process other missions, stop and restart the Control-D monitor. Save the job log of the Control-D decollation monitors and the output referenced by DD statement IOADUMP of the decollation monitor which processed the problematic mission. Call BMC Customer Support.

CTD26BE SUBSYSTEM REQUEST FAILED FOR JOB jobName. RC15= rc, SSOBRETN= rtrn_code.

Explanation: A “sysout processing” request caused an unexpected return code to be received from JES. JES was unable to satisfy the request.

The variables in this message are:

• jobName - the name of the relevant job
• rc - the code returned in register 15
• rtrn_code - the contents of the SSOBRETN field of the request block

Corrective Action: Verify that JES is active and functions normally. If JES is functioning normally, save all sysouts of this execution of the Control-D monitor and contact BMC Customer Support. Request RESTORE of the problematic report again.

CTD26HE GENERIC MISSION ABENDED SXXX UXXXX. GENERIC DECOLLATION PROCESSING STOPPED

Explanation: Highlighted, unrollable message.

The generic decollation mission abended with the system code or the user code or both these codes displayed in this message. The decollation mission finishes NOTOK. CONTROL-D deactivates the Generic decollation process.

Corrective Action: Save the job log of the CONTROL-D decollation monitors and the output referenced by DD statement IOADUMP of the decollation monitor that processed the problematic mission. Call BMC Software Customer Support.

CTD271I GENERIC JOB DECOLLATION IS INACTIVE

Explanation: This information message indicates that Generic Processing is not active. The reason the message is issued depends in which of the following formats the message is issued.

• regular, rollable message - indicates that the corresponding Control-D monitor does not perform the Generic Processing. The Control-D monitor issues the message when it is started and after new day processing.
• highlighted, unrollable message - indicates that a job is waiting to be decollated in one of the Generic classes, but Generic Processing is not active. This message will appear every 10 minutes, until Generic Processing is activated.

Control-D continues processing, but no Generic Processing will be done.

Corrective Action: Use the following guidelines to resolve the problem:

• If you have Generic Missions that CTDNDAY processing should order, ensure that the GENLIST member contains the library and table name for your Generic Missions
• If you have a Library and table names in the GENLIST member, ensure that the MEMBERS really exist in the library. Also verify that the library is the correct name.
• Check to see if CTDNDAY processing had an error during the ordering of GENLIST. If an error occurred the deactivation of Generic Processing is automatic.
• Check to see if someone issued the STOPGEN command.

Issue the following command, to activate Generic Processing:

F CONTROLD,STARTGEN

The application will respond by displaying the following message:

CTD139I GENERIC JOB DECOLLATION IS ACTIVE ON CLASSES (claslist)

To verify your classes, check the GENCLAS= parameter in the CTDPARM member.

Note: If there are NO Generic Missions being ordered during the CTDNDAY processing, you need to manually activate Generic Processing if you are manually Forcing/Ordering Generic Missions.
For more information on activating and deactivating generic processing, see the INCONTROL for z/OS Administrator Guide.

CTD272W SYSOUT REMOVED FROM QUEUE
CTD272I GENERIC DECOLLATING MISSION NOT FOUND FOR JOB jobName.

Explanation: Control-D found a non-held output on one of the classes dedicated for Generic processing. There is a Generic decollating mission for the class, but there is no applicable decollating mission for the sysout. These two messages are always issued together.

Whenever a non-held output appears on the spool in one of the classes defined for Generic processing, Control-D looks for a Generic decollating mission (on the Active Missions file) which matches the job name. If a match is not found, the sysout is processed according to the GENOTFIND Control-D installation parameter. For more information, see the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

Corrective Action: Check to see if the Generic decollating mission for this job should be on the Active Missions file. If so, order the decollating mission. If not, purge the sysout.

CTD273I SYSOUT CLASS CHANGED FROM CLASS x TO ESCAPE CLASS y.

Explanation: This information message indicates that Control-D found a non-held output on one of the classes dedicated for Generic processing. There is a Generic decollating mission for the class, but there is no applicable decollating mission for the sysout.

Whenever a non-held output appears on the spool in one of the classes defined for Generic processing, Control-D looks for a Generic decollating mission on the Active Missions file that matches the job name. If a match is not found under JES3, Control-D changes the sysout’s class to an Escape Class as specified in the GENOTFND Control-D installation parameter, and the output remains on the spool. For more information, see the INCONTROL for z/OS Administrator Guide.

Corrective Action: Check to see if the Generic decollating mission for this job should be Active on the Active Missions file. If so, order the decollating mission. If not, purge the sysout.

CTD276I MESSAGE MOVED TO MQ ESCAPE QUEUE queueName

Explanation: This information message indicates that the message was moved to the queueName queue that was defined in the CTDMQPRM parameter of the MQNOTFIND CTD PARM member.

Corrective Action: No action is required.

CTD277W THE DATA LENGTH IS ZERO IN THE MESSAGE FROM MQ QUEUE queueName

Explanation: The message from the IBM WebSphere MQ queue cannot be decollated because the message data length is zero. The message will be moved to the IBM WebSphere MQ escape queue.

The name of the escape queue must be defined with the CTDMQPRM parameter in the MQNOTFIND CTD PARM member.

Corrective Action: No action is required.

CTD278E SYSOUT ALLOCATION FAILED, JobName,JobId,DDName, RC=rc, ERROR=rsn

Explanation: An error was encountered when Control-D tried to allocate a sysout for decollation.

The variables in this message are:

• jobName - the name of the job with the problematic sysout
• jobId - the job ID of the job with the problematic sysout
• DDName - the name of the DD statement with the problematic sysout
• rc - dynamic allocation return code
• rsn - dynamic allocation reason code

Corrective Action: Try to correct the sysout. If the problem persists, contact your system programmer for assistance. Keep all sysouts from this execution of the Control-D monitor, and contact BMC Customer Support.

CTD27FI jobId,jobName,ddName SYSOUT IS HELD IN GENERIC CLASS clss

Explanation: The sysout of the identified job cannot be decollated by a generic decollation mission. The reason is an error identified in a previous message.

The variables in this message are:

• jobName - the name of the job with the problematic sysout
• jobId - the job ID of the job with the problematic sysout
• ddName - the name of the DD statement with the problematic sysout
• clss - the spool class of the sysout

Processing continues, but the status of the sysout is set to HELD.

Corrective Action: Examine the log for the previous message that identifies the error, and proceed according to the User Response for that message.

CTD27GE jobId,jobName,ddName JES I/O ERROR RSN rsn FOR SYSOUT CLASS clss

Explanation: A JES I/O error occurred during the reading of sysout from the spool.

The variables in this message are:

• jobName - the name of the job with the sysout that was being read when the mismatch occurred
• jobId - the job ID of the job with the sysout that was being read when the mismatch occurred
• ddName - the name of the DD statement with the sysout that was being read when the mismatch occurred
• rsn - the reason code from the FDBK field of JES
• clss - the spool class of the sysout

The decollation mission finishes NOTOK.

Corrective Action: Try to correct the sysout. If the problem persists, keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.

CTD27HI ZIIP ISN'T USED

Explanation: This information message indicates that the zIIP processor is not being used by the Control-D decollation monitor, as it is defined in the CTDPARM.

Additional messages identify the specific reason why the zIIP processor is not being used.

Corrective Action: Check the IOA log file and the system log for the reason. Contact your system programmer for assistance if needed.

CTD27II ZIIP IS USED

Explanation: This information message indicates that the zIIP processor is being used by the Control-D decollation monitor.

Corrective Action: No action is required.

CTD27JE jobName, jobId, ddName OPEN ERROR RS rs ERFLG err FOR SYSOUT CLASS clss

Explanation: An error occurred while attempting to open a SYSOUT for decollation.

The variables in this message are:

• jobName - the name of the job with the sysout that caused the problem
• jobId - the job ID of the job with the sysout that caused the problem
• ddName - the name of the DD statement with the sysout that caused the problem
• rc - the return code from the OPEN
• err - the reason code from the ACBERFLG field
• clss - the spool class of the sysout

The decollation mission finishes NOTOK. The CTD27FI message, which follows, indicates that the status of the problematic SYSOUT is set to HELD.

Corrective Action: Try to correct the sysout. If the problem persists, keep all sysouts of this execution of the Control-D monitor, and contact BMC Customer Support.

CTD280E CANNOT SAVE. MASK RULER ALREADY EXISTS FOR THIS REPORT.

Explanation: Only one MASK RULER can be defined for a report with the same RECIPIENT NAME, JOBNAME, and REPORT NAME.

Corrective Action: Use existing MASK RULER for editing. If you want to create a new MASK RULER with a different name, first delete the original MASK RULER.

CTD281E A MASK RULER HAS NOT BEEN SPECIFIED FOR THIS REPORT.

Explanation: The user entered the RULER MASK command, but there was no MASK RULER defined in the VSA USER record.

Corrective Action: If the MASK RULER exists, update the VSA USER record, either manually or using the CTDUFUPD utility. If the MASK RULER has not yet been defined, use the Edit screen to create a MASK RULER.

CTD282I text (usr).

Explanation: Highlighted, unrollable message.

This information message is activated by the SHOUT Facility.

The variables in this message are:

• text - the information
• usr - the user ID of the job order requesting the SHOUT

Corrective Action: No action is required.

CTD284I NEW DYNAMIC DESTINATION TABLE LOADED.

Explanation: This information message indicates that a new Dynamic Destination Table has been loaded by the Control-D monitor. The message also appears on initialization of the SHOUT Facility under the Control-D monitor

Corrective Action: No action is required.

CTD285W DYNAMIC DESTINATION TABLE NOT LOADED.

Explanation: Loading of the Dynamic Destination Table by the Control-D monitor failed.

It could be due to one of the following:

• There is insufficient memory for loading the table.
• The IOADEST table does not exist in the IOA PARM library.

If the failure happens during the initialization of the Control-D monitor, then SHOUT notifications will not be controlled by the Dynamic Destination Table. If this happens as a result of an F CONTROLD,NEWDEST command (operator command instructing the Control-D monitor to load a new Destination Table), the old destination table will remain in effect.

Corrective Action: Check the MVS Log for the reason for the failure (probably a system abend code). Correct the problem and then, in order to load the table, issue the operator command F CONTROLD,NEWDEST.

CTD286E RULER DEFINITION TOO LONG (NOT SAVED). TRY TO OMIT "INSERTED" LINES

Explanation: Ruler definition exceeded the maximum allowed length.

The rule is not saved.

Corrective Action: Decrease size of the ruler by omitting Inserted lines.

CTD295E PLEASE FILL IN STRING, FROM COLUMN AND UNTIL COLUMN

Explanation: One of the obligatory fields was not specified in the ruler definition screen. String and column fields must be filled in.

Corrective Action: Fill in these fields.

CTD296E COLUMN MUST BE A THREE DIGIT NUMBER (001-256)

Explanation: Column specification is incorrect. Column number must contain only digits.

Corrective Action: Enter correct column number.

CTD297E "TO COL" MUST BE GREATER THAN "FROM COL"

Explanation: Column specification is incorrect. FROM column number must be not greater than TO column number.

Corrective Action: Enter correct column numbers.

CTD298E LINE MUST BE A THREE DIGIT NUMBER 001-256 OR L99-L01

Explanation: The specified line is out of range. Line range is 001-255 or L99-L01 (from the bottom of the page).

Corrective Action: Correct the line range specification.

CTD299E "TO LINE" MUST BE GREATER THAN "FROM LINE"

Explanation: The specified FROM LINE is greater than the specified TO LINE. The TO LINE value must be greater than or equal to the FROM LINE value.

Corrective Action: Correct the TO LINE and/or FROM LINE values.

CTD29BW INSUFFICIENT MEMORY TO COMPLETE PROCESSING OF THE PRINT RULER rulerName FOR REPORT recipientName / jobName / reportName

Explanation: This warning message is issued if there is insufficient memory for using PRINT RULER rulerName for report recipientName / jobName / reportName. The report is printed without the ruler formatting.

Corrective Action: Increase region size of the corresponding address space and rerun printing.

CTD2T0I FILE TRANSFER MONITOR SHUTTING DOWN

Explanation: Highlighted, unrollable message.

This information message indicates that the File Transfer monitor is shutting down.

Corrective Action: No action is required.

CTD2T1S FILE TRANSFER MONITOR ENDED WITH ERROR

Explanation: This information message indicates that the File Transfer monitor ended with an error.

Corrective Action: In the printout of the File Transfer monitor, check the messages which preceded this FTM121S message for an indication of the cause of the error, and take appropriate corrective action.

CTD2T2W FILE TRANSFER MONITOR IS ACTIVE. QNAME " qName "

Explanation: Highlighted, unrollable message.

The user attempted to activate the File Transfer monitor when it was already active. More than one File Transfer monitor cannot be active at the same time.

The new File Transfer monitor is not activated.

Corrective Action: No action is required.

CTD2T5I validModifyParm

Explanation: This information message displays a valid modify parameter that can be used in File Transfer monitor operator commands. It is issued together with the FTM103E message.

Corrective Action: No action is required.

CTD2T8S RECIPIENT TREE WAS NOT LOADED BECAUSE OF ERROR - MONITOR IS TERMINATING

Explanation: The attempt to load the Recipient Tree failed. As part of the initialization process, the File Transfer monitor attempts to load the Recipient Tree.

The File Transfer monitor shuts down.

Corrective Action: Check other messages in the IOA log and JES log to determine why the Recipient Tree could not be loaded. Fix the Recipient Tree. Then try again to start the File Transfer monitor.

CTD2T9S NO RECIPIENTS WERE FOUND WITH IP ADDRESS. MONITOR IS TERMINATING

Explanation: The File Transfer monitor was unable to find a recipient with an IP address.

The File Transfer monitor terminates.

Corrective Action: Contact BMC Customer Support.

CTD2TAS SUBTASK IS TERMINATED BY TIMEOUT FOR IPA = ipAdd.'

Explanation: The subtask has timed out and been terminated.

The monitor main task periodically checks the status of all its subtasks. When the CPU of a subtask has not changed since the last check, the subtask is considered to be inactive ("hanging"), and the main task of the monitor interrupts the subtask.

The subtask is terminated.

Corrective Action: In the printout of the File Transfer monitor, and in the log of your PC session manager, check the messages which preceded this FTM121S message for an indication of the reason why the subtask was left inactive, and take appropriate corrective action.

CTD2TBS SUBTASK IS TERMINATED BY CANCEL REQUEST FOR IPA = ipAdd. PORT = portNumber.

Explanation: The File Transfer monitor subtask with the IP address identified in this message has been terminated by an operator modify CANCEL command.

The identified subtask is terminated.

Corrective Action: No action is required.

CTD2TCS THERE ARE NO ACTIVE SUBTASKS

Explanation: This information message indicates that the File Transfer monitor has no active subtasks.

Corrective Action: No action is required.

CTD2TDS FORMAT OF THE MODIFY COMMAND IS NOT CORRECT

Explanation: An invalid operator modify command has been entered.

The command is rejected.

Corrective Action: Correct and reissue the operator modify command.

For more information, see the File Transfer Monitor section in the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

CTD2TES THE SUBTASK NUMBER IS NOT DIGITAL

Explanation: An invalid subtask number has been specified in an operator modify CANCEL command.

The command is rejected.

Corrective Action: Enter a valid subtask number and reissue the command.

CTD2TFS THE SUBTASK NUMBER EXCEEDS THE TOTAL NUMBER OF THE ACTIVE SUBTASKS

Explanation: The subtask number entered in an operator modify CANCEL command is invalid, because it is greater than the total number of active subtasks.

For more information, see the File Transfer Monitor section in the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

The command is rejected.

Corrective Action: Enter a valid subtask number in the operator modify CANCEL command and reissue the command.

CTD2TGS SUBTASK IS ALREADY NOT ACTIVE FOR IPA = ipAdd PORT = portNumber

Explanation: The File Transfer monitor subtask with the ipAdd IP address and portNumber port number is already inactive.

The command is rejected.

Corrective Action: No action is required.

CTD2THS SUBTASK IS TERMINATED BY SUSPEND FOR IPA = ipAdd PORT = portNumber

Explanation: The File Transfer monitor subtask with the ipAdd IP address and portNumber port number has been terminated by an operator modify SUSPEND command.

The subtask is terminated.

Corrective Action: No action is required.

CTD2TIS IPA SPECIFIED IN THE CANCEL COMMAND IS NOT CORRECT.

Explanation: An invalid IP address was specified in an operator modify CANCEL command.

The command is rejected.

Corrective Action: Enter a correct IP address in the CANCEL command and reissue the command.

CTD2TJS THE INTERVAL PARAMETER VALUE IS NOT DIGITAL.

Explanation: An invalid File Transfer monitor sleeping interval has been specified in an operator modify command.

The File Transfer monitor sleeping interval must be a 3-digit number from 1 through 999 seconds.

For more information, see the File Transfer Monitor section in the Control-D chapter in the INCONTROL for z/OS Administrator Guide.

The operator modify command is rejected.

Corrective Action: Enter a valid value for the File Transfer monitor sleeping interval and reissue the command.

CTD2TKI THE MODIFY COMMAND cmdText IS ACCEPTED

Explanation: This information message indicates that the cmdText modify command has been accepted by the File Transfer monitor.

Corrective Action: No action is required.