Messages CTD300 through CTD3xx

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

CTD304E func NOT OK WITH cc Y REASON CODE rsn MQ NAME uuuuuuu

Explanation: An error was detected during interface with IBM WebSphere MQ Series.

The variables in this message are:

func - can be one of the following interface functions:
- MQCONN
- MQDISC
- MQOPEN
- MQGET
- MQPUT
- MQCLOS
- MQCOMMT
cc - the completion code, which can be one of the following:
- 0
- 1,,,
- 2
rsn - the reason code, which can have many different values. More detailed information about reason codes is included in the IBM WebSphere MQ Series documentation set.

System action is determined by the completion code and reason code combination. More detailed information about these codes is included in the IBM WebSphere MQ Series documentation set.

Corrective Action: User response to a particular completion and reason code combination is determined by that combination. More detailed information about these codes is included in the IBM WebSphere MQ Series documentation set.

CTD305E INSUFFICIENT MEMORY TO DECOLLATE MESSAGE FROM MQ

Explanation: Insufficient memory to decollate the message from the IBM WebSphere MQ queue.

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

CTD306E IOAUCODE INITIALIZATION FAILED RC rc REASON rsn

Explanation: An error was detected during initialization of the table used in the translation of an XML report or in the checking of Xpath values of the mission definition. The message can be issued from

the R screen
the A.Z screen
the Control-D monitor

Possible causes of this error are:

the ENCODTBL member was not found in the IOA IOAENV library
the ENCODTBL member contains more than 100 entries
some other internal error

The system performs the following actions:

Mission definition edition is terminated. The IOAE2FS (International format) issues on the R.S and A.Z screens.
The translation of the XML report does not proceed. Control-D continues processing.

Corrective Action:

Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate the IOA Online facility, and continue the mission definition edition.

Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate Control-D, and run this mission again.

If the problem persists contact BMC Customer Support.

CTD307E UNICODE TRANSLATION FAILED RC rc REASON rsn

Explanation: An error was detected during translation of an XML report to EBCDIC or during the checking of Xpath-values of the mission definition for XML reports. The message can be issued from

the R screen
the A.Z screen
the Control-D monitor

The variables in this message are:

rc - the return code. Valid values of rc are:

rc	Meaning
4	Incomplete translation, due to separator (FF)
8	The encoding pair that was specified in ENCODTBL is not supported
12	The input data in the XML report was incorrect
16	Internal error: incorrect parameters
20	One of the members that was specified in ENCODTBL was not found in the IOA IOAENV library

rsn - the code that disclosed the detailed reason for the internal error

The system performs the following actions:

Mission definition edition is terminated. The IOAE2FS (International format) is issued on the R.S and A.Z screens.
The translation of the XML report does not proceed. Control-D continues processing.

Corrective Action:

Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate the IOA Online facility, and continue the mission definition edition.

Check the ENCODTBL member in the IOA IOAENV library, make any necessary corrections, reactivate Control-D and run this mission again.

If the problem persists contact BMC Customer Support.

CTD30AI MQ DECOLLATION IS STOPPED

Explanation: The MQ interface process has stopped.

This message can appear for two reasons:

The STOPMQ modify command was issued
Errors occurred during MQ interface

Corrective Action: If errors occurred during MQ interface, review the LOG to determine the cause, make appropriate corrections, and issue the STARTMQ modify command.

CTD30BE LOADING OF MODULE OF MQ STUB IS FAILED, THE NAME IS mmmmmmmm

Explanation: The prefix.LOAD library is not installed or the IBM WebSphere MQ Series is not installed for the user, but an MQ decollation mission was defined.

The CTD30AI message will be issued and IBM WebSphere MQ decollation will be stopped.

Corrective Action: If the IBM WebSphere MQ Series is not installed, delete the MQ mission. Otherwise correct your installation configuration and then issue the STARTMQ modify command.

CTD30CE ANY OF MQ QUEUES CAN NOT BE OPENED

Explanation: Control-D tried to retrieve a message from every IBM WebSphere MQ queue, but all attempts failed.

The CTD30AI message will be issued and IBM WebSphere MQ decollation will be stopped.

Review previous messages and issue appropriate responses. After you perform the necessary corrections, issue the STARTMQ modify command.

Corrective Action: No action is required.

CTD30DI MQ QUEUE IS BEING CLOSED BECAUSE PUT/GET IS FAILED, QUEUE NAME dddddd

Explanation: The access to this IBM WebSphere MQ Series queue is being closed because of failure of MQPUT for the ESCAPE MQ queue, or failure of MQGET for the MQ queue.

Control-D continues processing MQ decollations until this message is issued for all MQ queues.

Corrective Action: For additional information see the IBM WebSphere MQ Series documentation set.

CTD30EE MEMBER CTDMQPRM IS NOT FOUND IN CTD PARM OR VALUE OF MQNOTFIND PARAMETER IS NOT DEFINED

Explanation: The CTDMQPRM member was not found in CTD PARM, or the value of the MQNOTFIND parameter has not been defined.

The CTD30AI message will be issued and IBM WebSphere MQ decollation will be stopped.

Define the CTDMQPRM member or add the name of the MQNOTFIND parameter; then issue the STARTMQ modify command.

Corrective Action: No action is required.

CTD310S OPEN OF RECIPIENT TREE (DD STATEMENT "DATREE") FAILED

Explanation: Open of the Control-D Recipient Tree failed. There is a problem with the DATREE DD statement in the Control-D CLIST.

It is due to one of the following:

The DD statement DATREE is missing.
If the DD statement DATREE is allocated to a library, the requested member name is not found.

You will not be able to use the User Report List screen.

Corrective Action: Correct the Control-D entry CLIST DMAN (or TMAND or other) to include the DD statement DATREE. Then exit the Control-D Online Facility, and reenter.

CTD311S SECURITY VIOLATION - YOU ARE TRYING TO BYPASS THE RECIPIENT TREE

Explanation: The Recipient Tree data set name or member name is incorrect. Control-D security exit CTDX004 checks if the data set name and member name of the DATREE DD statement are correct.

You will not be able to use the User Report List screen.

Corrective Action: Do one of the following

Correct the Control-D entry CLIST by changing the data set name or the member name of the Recipient Tree. Then exit from the Control-D Online Facility, and reenter it.
Correct security exit CTDX004 in the SAMPEXIT library by checking for the correct Recipient Tree data set name or member name. The called routine is TREEVER. Then exit the Control-D Online Facility, and reenter it.

CTD312S ERROR WHILE LOADING THE RECIPIENT TREE

Explanation: The loading of the Control-D Recipient Tree failed. An appropriate error message is displayed on the operator console and the IOA Log. The error message specifies the exact cause of the problem.

Note:

ll error messages relating to the Recipient Tree on the IOA Log start with TRE.

You will not be able to use the User Report List screen.

Corrective Action: Correct the Recipient Tree. Then exit from the Control-D Online Facility, and re-enter it.

CTD313E YOU ARE NOT AUTHORIZED TO RECEIVE REPORTS FOR THIS RECIPIENT

Explanation: The user has specified a value in a filter for the RECIPIENT field, and is not authorized to view report entries for recipients that match this value.

The requested function is not performed.

Corrective Action: To obtain authorization to view these report entries, contact your INCONTROL administrator.

CTD314E YOU ARE NOT AUTHORIZED TO DO THIS ACTION

Explanation: You are not authorized to perform this function on the User Report List file.

The attempt to perform one of the following functions does not have the required authorization:

add an entry
update an entry
delete an entry
restore a report
reprint a report

The requested function is not performed.

Corrective Action: To get authorization to perform this function, call your INCONTROL administrator.

This message is the result of the action of the Control-D Security Exit CTDX004. For more information, refer to the following routines within this exit:

RECINS - add an entry
RECUPD - update an entry
RECDEL - delete an entry
RECRST - restore a report
RECRPRT - reprint a report

CTD315I SOME REPORTS WERE HIDDEN BY USER SECURITY EXIT

Explanation: This information message indicates that, for security reasons, one or more reports on the User Report List file was not displayed. The RECCONF routine of Control-D security exit CTDX004 determined that the requestor is not authorized to look at some report entries on the User Report List screen.

One or more report entries on the User Report List file is hidden.

Corrective Action: No action is necessary. All entries for which there is authorization will be visible. To see all report entries, call your INCONTROL administrator.

CTD316E YOU CANNOT UPDATE THE COP# ABOVE THE MAXIMUM SPECIFIED ON DECOLLATION

Explanation: The number of copies on the User Report List screen is above the maximum. The maximum number of copies allowed for this report is specified in the Report Decollating Mission Definition screen. The number of copies on the User Report List screen cannot be greater than the maximum number of copies on the Report Decollating Mission Definition screen.

The User Report List file is not updated.

Corrective Action: Do one of the following:

Change the number of copies to a lower value.
Ask the INCONTROL administrator to increase the maximum number of copies allowed.

CTD317E USER DOES NOT EXIST IN THE RECIPIENT TREE

Explanation: This user to be added or deleted to the User Report List file is not defined in the Control-D Recipient Tree.

The User Report List file is not updated.

Corrective Action: Do one of the following:

Correct the user to be added or updated.
Request the INCONTROL administrator to add the user to the Recipient Tree.

CTD318S YOU ARE NOT AUTHORIZED TO USE THIS SCREEN

Explanation: You are not authorized to use the User Report List screen. Control-D security exit CTDX004 checks the Recipient Tree to determine authorization to look at entries on the User Report List screen.

You cannot enter the User Report List screen.

Corrective Action: To get authorization to enter the User Report List screen, contact your INCONTROL administrator.

CTD319E YOU ARE NOT AUTHORIZED TO LOOK AT $SYSDATA RECORDS

Explanation: You are not authorized to look at $SYSDATA records on the User Report List screen. Control-D security exit CTDX004 (routine USERLIST) determined that you cannot look at $SYSDATA records.

The requested $SYSDATA entries are not displayed.

Corrective Action: To get authorization to look at $SYSDATA records, contact your INCONTROL administrator.

CTD31AE YOU ARE NOT AUTHORIZED FOR THIS APPROVAL

Explanation: The user has specified a value in a filter for the APPROVAL NAME field, and is not authorized to view report entries for Approval names that match this value.

The requested function is not performed.

Corrective Action: To obtain authorization to view these report entries, contact your INCONTROL administrator.

CTD320S UNABLE TO VIEW THIS REPORT - ALL COMPRESSED DATASETS WERE DELETED

Explanation: There are no compressed data sets for this report entry on the User Report List screen. You attempted to perform the V (View) function on the User Report List screen. The IOATOLV Control-D internal program was unable to find any compressed data sets for this report entry.

The view function is not performed.

Corrective Action: Ask the INCONTROL administrator to check why all the compressed data sets for this report were deleted.

CTD321S UNABLE TO VIEW THIS REPORT - RC FROM IOATOLV=rc

Explanation: The report cannot be viewed due to an error in the IOATOLV internal module or in a routine called by it, which resulted in return code rc. The V(View) option was specified on the User Report List screen. The IOATOLV internal module was called to perform the view function.

The following table shows the problem indicated by each return code, the routine in which it occurred, and the suggested action to take.

rc	Routine	Explanation	Action
04	IOATOLV	Internal error in module.	1
08	IOATOLV	Internal error in module.	1
12	IOATOLV	Internal error in module.	1
20	IOATOLV	Too many GETMAINs - report too large.	2
24	IOATOLV	Internal error in module.	1
28	IOATOLV	Internal error in module.	1
32	IOATOLV	All compressed data sets were deleted.	1
204	CTVINX#	Index access internal error. Invalid function code passed to routine.	1
220	CTVINX#	Index access internal error. Unexpected end of file reached on index file.	1
224	CTVINX#	Index access internal error. Open error on the index file.	1
236	CTVINX#	Index access, internal error. Error in reading the continuation records.	1
240	CTVINX#	Index access, internal error. Unexpected end of file reached on index file.	1
244	CTVINX#	Index access, internal error. Invalid parameter passed to read index routine.	1
248	CTVINX#	Index access, internal error. Problem in the search for the index value.	1
252	CTVINX#	Index access, internal error. Dynamic deallocation of index file failed.	1
280	CTVINX#	Index access, internal error. Open of subindex failed. Invalid code from CTVSRTN.	1
284	CTVINX#	Index access, internal error. Close of subindex failed. Invalid code from CTVSRTN.	1
288	CTVINX#	Index access, internal error. Locate subindex failed. Invalid return code from CTVLSUB.	1
292	CTVINX#	Index access, internal error. Close subindex was requested but no subindexes are open.	1
296	CTVINX#	Index access, internal error. Error in FREEMAIN.	1
300	CTVINX#	Index access, internal error. Locate of value failed under Quick Access.	1
304	CTVINX#	Index access, internal error. Open subindex failed under Quick Access.	1
316	CTVINX#	Index access, internal error. PREPINX failed under Quick Access.	1
324	CTVINX#	Index access, internal error. Inconsistent IXA table and IXT table under Quick Access.	1
328	CTVINX#	Index access, internal error. Invalid request code passed to CTVSINX.	1
332	CTVINX#	Index access, internal error. Internal error in CTVSINX.	1
336	CTVINX#	The IOA Archive Server not active.	4
340	CTVINX#	Index access, internal error. Block not in cache.	1
344	CTVINX#	Error in cache routine. OSIS (open session entry) was not active.	4
348	CTVINX#	Index access, internal error. Error moving $index record or user RBA ranges to IOA Archive Server.	1
368	CTVINX#	Index access, internal error. GETMAIN failed.	1
400	CTVINXR	Index access, internal error. Invalid function code passed to routine.	1
404	CTVINXR	Index access internal error. Load of CTVINX# failed.	1
424	CTVINXR	Index access internal error. No more room for IXP entries.	1
428	CTVINXR	Index access, internal error. Problem reading continuation error.	1
432	CTVINXR	Index access, internal error. Index name found in IXA table not found in $INDEX record.	1
444	CTVINXR	GETMAIN failed.	1
448	CTVINXR	Index access internal error. Error in IXA table. IXAXCNT is 0.	1
604	CTDTFLL	OK, but one or more continuation records were not found.	None
620	CTDTFLL	Insufficient memory. Too many RBA ranges in the report to be viewed.	2
1004	CTDBOX	Internal error in module.	1
1008	CTDBOX	Internal error in module.	1
1012	CTDBOX	Internal error in module.	1
1016	CTDBOX	Internal error in module.	1
1020	CTDBOX	Internal error in module.	1
1024	CTDBOX	Compressed Dataset Access Method not active.	3
1028	CTDBOX	Compressed Dataset Access Method not active.	3
1104	IOASCRQ	Error in cache routine. OSE (open session entry) was not active.	4
1108	IOASCRQ	Error in cache routine. Another request was issued with this OSE.	4
1124	IOASCRQ	The IOA Archive Server not active.	4
1204	IOASAOS	Error in cache routine. ENQ query for user existence failed.	4
1208	IOASAOS	Compressed Dataset Access Method not active. The Compressed Dataset Access Method was terminated or not started.	3
1212	IOASAOS	IOA Archive Server not active. The IOA Archive Server was terminated or not started.	5
1216	IOASAOS	Error in cache routine. No free OSE exists (open session entry).	4
1308	IOAXPC5	Error in cache routine. REQ (request queue element) error.	4
1404	IOAXPC5	The media to which the report migrated is not active in IOA Archive Server.	6
1408	IOAXPC7	Error in cache routine. Requested media not defined in the IOASPRM member.	4
1502	IOASCAW	Error in cache routine. Cannot copy the OSE (open session entry).	4
1504	IOASCAW	The report migrated to a media which is not active in IOA Archive Server.	6
1508	IOASCAW	Error locating migrated report. Requested report not found in the catalog.	7
1512	IOASCAW	Requested volume not in OSS Database. Report migrated to a volume that was manually deleted from the OSS database.	8
1516	IOASCAW	Requested platter not in OSS Database. Report migrated to a volume on a platter that was exported or manually deleted from the OSS Database.	8
1520	IOASCAW	Cache request failed. Media error in adding request to chain.	4
1524	IOASCAW	Cache request failed. Media error in GETMAIN for TVL.	4
1528	IOASCAW	Cache request failed. Media error handling multivolume file.	4
1532	IOASCAW	No devices active for this media. The media to which the report migrated has no currently active device in the IOA Archive Server.	9
1536	IOASCAW	Cache request failed. Media error: File resides on more than five volumes.	4
1560	IOASCAW	Cache request failed. Media error: An RQC was queued without RBAs.	4
1564	IOASDVT	Cache request failed. An RQC was queued with a zeroed RBA.	4
1568	IOASDVT	Cache request failed. Media error during deallocation. See the DVT191E or IOA191E and DVT192E or IOA192E messages in the IOA Log file for the error code and more information.	4
1572	IOASDVT	Error allocating device. IOA Archive Server could not allocate a device to retrieve a migrated report. See the DVT191E or IOA191E and DVT192E or IOA192E messages in the IOA Log file for error code and information about the failed allocation.	10
1576	IOASDVT	Cache request failed. Media error: Open failed.	4
1580	IOASDVT	Cache request failed. Media error: Task abended during open. See the DVT194E/IOA194E message in the IOA Log file for the abend code.	4
1584	IOASDVT	Cache request failed. Media error: I/O error on device. See the DVT193E/IOA193E message in the IOA Log file for I/O error description.	4
1592	IOASDVT	Cache request failed while reading descriptor block of migrated CDAM file.	4
1596	IOASDVT	Cache request failed while acquiring storage for a migrated CDAM descriptor block. See the DVT180S message in the IOA Log file for more information.	4
1600	IOASDVT	Cache request failed while reading the first block from a migrated CDAM file.	4
1604	IOASDVT	Cache request failed while acquiring storage for the first block of a migrated CDAM file. See the DVT180S message in the IOA Log file for more information.	4
1608	IOASDVT	Cache request failed while acquiring storage. See the DVT180S message in the IOA Log file for more information.	4
1612	IOASDVT	Cache request failed. An extent number in the RBA is out-of-range.	4
1616	IOASDVT	Cache request failed while translating RBA to BBB.	4
1620	IOASDVT	Cache request failed. Block number is out-of-range.	4
1624	IOASDVT	Cache request failed while translating BBB to RBA.	4
1628	IOASDVT	Cache request failed while issuing ENQ to test user existence. See the DVT181E or IOA181E message in the IOA Log file for more information.	4
1632	IOASDVT	Task abended during cache request processing.	4
1636	IOASDVT	Operator did not mount the tape volume requested by the IOA Archive Server. Operator could not find requested volume or did not mount the volume for some other reason.	11
1640	IOASDVT	Cache request failed. Media error: Assigned device could not be allocated because it is unavailable. See the DVT191E or IOA191E and DVT192E or IOA192E messages in the IOA Log file for more information.	4
1644	IOASDVT	Cache request failed. Index Access. Internal error in index cache chaining.	4
1648	IOASDVT	Cache request failed. Index Access. Internal error, invalid call to CTVSRTN.	4
1652	IOASDVT	Cache request failed. Index Access. Internal error, invalid call to CTVLSUB.	4

The report is not displayed or only partially displayed.

Corrective Action: Do one of the following, as indicated in the preceding table:

Report the message number and return code to BMC Customer Support.
This report is too large to view online. Report this to your INCONTROL administrator.
Ask your INCONTROL administrator to bring up the Compressed Dataset Access Method (CDAM) so you can view this report.
Examine the IOA Log file for messages regarding the event. Use the return code to determine what caused the IOA Archive Server cache mechanism to fail. If the error cannot be resolved, contact BMC Customer Support.
Ask the operator to start the IOA Archive Server.
Ask the operator to activate the required media in the IOA Archive Server.
Contact your INCONTROL administrator to find out what happened to the required data set.
Contact your OSS operator to find out what happened to the required volume or platter.
Ask the operator to activate at least one device of the required media in the IOA Archive Server.
Correct the problem that caused the allocation to fail and retry.
Contact the operator to determine why the requested volume was not mounted.

CTD322S UNABLE TO VIEW THIS REPORT BECAUSE OF AN INTERNAL ERROR

Explanation: The IOATOLV routine encountered a problem, and returned an invalid return code. Control-M/Tape called the IOATOLV routine when the user specified the V (View) option in the User Report List screen.

The report cannot be viewed.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTD32BE NUMBER OF PRINT MISSIONS EXCEEDS THE ALLOWED MAXIMUM

Explanation: A large number of PRINT missions were specified in the deferred print request for reports created by a Decollation Mission with STORED=Y in the DO PRINT parameter.

The PRINT mission name specified in the DO PRINT parameter, is hidden in both the User Report List Print Window and the Control-D/WebAccess Host PRINT Window. Nevertheless, since the PRINT mission name is stored in the report entry it is included in the total number of PRINT missions stored in the report entry. The maximum number of PRINT missions, whether immediate or deferred, that are stored in one report entry cannot exceed 5.

The print request is not performed.

Corrective Action: Perform the deferred print request again with less PRINT missions.

CTD323E VIEW|MASK RULER rulerName DOES NOT EXIST FOR THIS USER/REPORT/JOB

Explanation: The rulerName ruler was not located. The name may have been misspelled, or the ruler has not been defined.

No ruler is activated.

Corrective Action: Specify a valid ruler name.

CTD324E AT LEAST ONE PRINTING MISSION NAME MUST BE ENTERED

Explanation: No Printing Mission was defined. At least one Printing Mission name must be entered in the MISSION NAME field for deferred printing.

An error message is issued, and the cursor is positioned at the MISSION NAME field.

Corrective Action: Enter at least one mission name.

CTD325E DEFERRED PRINTING - RULER NAME MUST BE "DEFAULT"

Explanation: The RULER NAME field does not contain the value DEFAULT. In case of deferred printing, the ruler name must be DEFAULT to use an existing DEFAULT ruler.

An error message is issued and the cursor is positioned at the RULER NAME field.

Corrective Action: Correct the ruler name to DEFAULT.

CTD326E DEFERRED PRINTING - FROM PAGE NUMBER MUST BE EQUAL TO 1

Explanation: The FROM PAGE field contains a value other than 1. In case of deferred printing, the FROM PAGE must be defined as the first page.

An error message is issued and the cursor is positioned at the FROM PAGE field.

Corrective Action: Correct the value in the FROM PAGE field to 1.

CTD327E YOU CAN ONLY SELECT THE ENTIRE PAGE RANGE FOR DEFERRED PRINTING

Explanation: An invalid page range was defined for deferred printing. For deferred printing, the entire page range must be defined.

An error message is issued, and the cursor is positioned at the PAGE RANGE field.

Corrective Action: Correct the page range.

CTD328S UNABLE TO EDIT A RULER - INVALID RC rc FROM CTDTEXT

Explanation: An internal error occurred that caused the CTDTEXT subroutine to return an invalid return code.

The ruler is set to OFF.

Corrective Action: Have your INCONTROL administrator call BMC Customer Support for assistance.

CTD329E INVALID parm PARAMETER

Explanation: An invalid value was specified in the User Report List Print window. Control-D Exit 4 found an invalid value in the parm parameter.

The report is not printed.

Corrective Action: Correct the parameter.

CTD330I COMPRESSED DATASET ACCESS METHOD MAINTENANCE UTILITY STARTED

Explanation: This information message indicates the normal start of the CTDAMUTI utility.

Corrective Action: No action is required.

CTD331I COMPRESSED DATASET ACCESS METHOD MAINTENANCE UTILITY ENDED OK

Explanation: This information message indicates the normal termination of the CTDAMUTI utility.

Corrective Action: No action is required.

CTD332S COMPRESSED DATASET ACCESS METHOD MAINTENANCE UTILITY ENDED WITH ERRORS

Explanation: The CTDAMUTI Compressed Dataset Access Method utility ended with errors.

This is a general message when the CTDAMUTI utility ends with errors. The job sysout should contain prior messages detailing the reasons.

Corrective Action: No action is required.

CTD333E INVALID CDAM MAINTENANCE UTILITY FUNCTION: func

Explanation: An invalid function (func) was given to the CTDAMUTI Control-D utility.

For more information, see the section on the CTDAMUTI CDAM maintenance utility in the Control-D and Control-V User Guide.

The CTDAMUTI utility terminates with a return code of 08.

Corrective Action: Correct the function, and rerun the CTDAMUTI utility.

CTD334W NO CDAM FILES FOUND FOR THE SPECIFIED SELECTION CRITERIA

Explanation: No CDAM data sets were found that match the data set identification parameters given to the CTDAMUTI utility.

The CDAMUTI utility attempts to locate CDAM data sets based on the data set identification parameters given to it. One of the following problems is present:

An error was made by the user in the data set identification parameter.
Someone deleted the required CDAM data sets.

For more information, see the section on the CDAMUTI CDAM maintenance utility in the Control-D and Control-V User Guide.

The CTDAMUTI utility will terminate with a return code of 04.

Corrective Action: Do one of the following, then rerun the utility:

Correct the data set identification parameter.
Restore the requested CDAM data sets.

CTD335S OPEN OF PARAMETERS FILE FAILED. DDNAME "SYSIN"

Explanation: The open of the SYSIN DD statement failed.

Possible causes are:

The SYSIN DD statement or the DAMUTIN DD statement is missing.
The data set described by the SYSIN DD statement or the DAMUTIN DD statement cannot be opened for sequential read.

For more information, see the section on the CDAMUTI CDAM maintenance utility in the Control-D and Control-V User Guide.

The CTDAMUTI utility terminates with a return code of 12.

Corrective Action: Correct the CTDAMUTI JCL and rerun the utility.

CTD339S OPEN OF OUTPUT (SPOOL PRINT) FILE FAILED

Explanation: Internal error in the CTDAMUTI utility.

The dynamic allocation of a sysout print file by the CTDAMUTI utility failed.

The CTDAMUTI utility terminates with a return code of 12.

Corrective Action: Have your system programmer call your IOA representative for assistance.

CTD33AS NO SELECTION PARAMETERS ARE SPECIFIED

Explanation: No CDAM selection parameters were specified in the input of the CTDAMUTI utility.

At least one CDAM selection parameter must be specified in the input of the CTDAMUTI utility.

The CTDAMUTI utility ends with an error.

Corrective Action: Rerun the CTDAMUTI utility specifying CDAM selection parameters.

CTD364I WAITING FOR ACTIVE PRINTING MISSION(S) IN ORDER TO SHUT DOWN

Explanation: Highlighted, unrollable message.

This information message indicates that the Control-D monitor was shut down, but is waiting for print tasks to finish in order to complete the shut down.

The Control-D internal Printing Missions Manager task received a request from the Control-D monitor to shut down. However, one or more of the print tasks under the control of the Printing Missions Manager is still printing. As soon as all the print tasks are completed, the Printing Missions Manager task will shut itself down.

Corrective Action: No action is required.

CTD390S OPEN OF DDNAME ddName FAILED.

Explanation: Open of the ddName DD name failed. Possible causes are:

The ddName DD statement is missing.
The data set described by the ddName DD statement does not exist.

Execution stops.

Corrective Action: Correct the JCL of the job and rerun.

CTD394S INVALID PARAMETER - parm

Explanation: An invalid parameter was specified to the report or utility.

If this message was issued during execution of the CTMBLT utility, it is followed by message BLT895I and/or BLT896I, which identify the problematic job, keyword, and value.This message may also be issued by the CTMBUPD utility.

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

Corrective Action: For the syntax of the parameter for the report or utility, see either the INCONTROL for z/OS Administrator Guide or the INCONTROL for z/OS Utilities Guide, as appropriate.

Parent Topic

CTD messages