Messages CTDU00 through CTDUxx

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

CTDU10E fileType USER FILE ERROR error

Explanation: An error occurred while accessing a User Reports List file. This message is written to the IOA Log file by the user file interface routine.

The variables in this message are:

fileType - the type of User Reports List file component.Valid values for the data component are:
- ACT
- PRM
- HST
- MIG
- MG n, where n is the migrated partition number

Valid values for the index component are composed of the index component letter, followed the data component values.

error - the error description

Control returns to the calling routine which usually issues the CTD908S message.

Corrective Action: Do one of the following, depending on the value of error:

If the value of error is INCORRECT FORMAT OF DATA / INDEX FILE, use the IOADBF utility to reformat the problematic file.
If the value of error is RECORD NOT FOUND IN THE DATA FILE or INDEX RECORD DOES NOT MATCH DATA RECORD, use the CTDDIB utility to rebuild the index file.
If the value of error is FILE IS NOT CONVERTED ACCORDING TO WD1164, use the CTDDIB utility to rebuild the index file.
If the value of err is DATA FILE OVERFLOW or INDEX FILE OVERFLOW, enlarge the problematic file by running the IOADBF utility with the EXTEND function.
Note:

You can prevent this problem in the future by defining a secondary space allocation and automatic extension in the corresponding Space Calculation Step. You can find this using ICE:
1. In the IOA Installation Menu, select Customization.
2. Select the environment to customize.
3. In the Customization screen, set Product ID to CTD and select Product Customization.
4. Select Major Step 5, Customize Control-D User Files.
If the value of error is ALTERNATIVE INDEX DEFINITION MISMATCHES LRECL, check and correct the alternative index definition in the DEF xxxi or DEFALTI members or both, and rerun the CTDUFDBF, CTDUFANX, and CTDDIB utilities to recreate the alternative index component.

CTDU11I opn OPERATION FOR fileName FILE FROM pgm PROGRAM IN modeType MODE

Explanation: This information message indicates that accesses to user files were traced as requested by optional wish WD2370.

Corrective Action: No action is required.

CTDU99E fileType FILE RC=rc FUNC func PGM pgmCsect ID=xx /yyy LAST KEY=lastKey

Explanation: An error occurred while accessing a User Report List file.

This message accompanies the CTD908S message, and provides additional information.

The variables in this message are:

fileType - the type of User Report List file component.Valid values for the data component are:
- ACT
- PRM
- HST
- MIG
- MG n, where n is the migrated partition number

Valid values for the index component are composed of the index component letter, followed by the data component values.

rc - return code
func - the operation that caused the error
pgmCsect - the program CSECT that received the error
xx/ yyy - an identifier for localizing the erroneous call
lastKey - the key in the data or index file

Return codes may range from 004 through 399. The return codes from 300 through 399 relate to index components. Their explanations are the same as the corresponding return codes in the range from 100 through 199, which relate to data components.

The following table lists and explains the possible values for the return code (rc):

rc	Explanation
004	Read operation: EOF. Add index operation: Duplicate Key. Update operation: Record was changed. 0i
008	Duplicate key.
012	Incorrect record for update.
016	The record was not found (probably deleted), or an invalid record was read, or the function is not correct.
020	Insufficient memory to open an IOA Access Method file.
024	Not enough space in data file.
028	Not enough space in index file.
032	The current call terminates because the previous open failed.
036	Incorrect record length.
040	Internal error.
044	Internal error.
052	Invalid key fields.
056	Key is too long.
058	For future use.
060	Index record does not match data record.
064	Wish WD1164 setting does not match file contents.
068	Incorrect parameter for Interface routine.
072	Incorrect file type.
106	Record not found.
108	Record not found. Invalid extent number.
109	Record not found. Invalid block number.
110	Internal error. Record not found. Invalid extent number.
111	Internal error. Record not found. Invalid block number.
112	Insufficient memory for internal buffers.
113	Open failed for database file.
114	RDJFCB failed for database file.
116	Corrupted free list.
118	Corrupted record.
119	Record not found.
120	Invalid QNAME.
121	Bad record in free list.
122	Invalid data set name in control record.
124	Invalid function.
128	IOAPARM load failed.
132	Add failed. Record too long.
136	I/O error.
144	EXCP init error.
146	For future use.
148	Invalid data set name or DD name is too long.
150	Locate failed.
152	SVC 99 allocate failed.
154	SVC 99 unallocate failed.
156	Dual database not up to date - aborting.
158	For future use.
160	Link of IOADBF failed.
164	A dynamic allocation error occurred (for example, out of space condition, security problems). See dynamic allocation error messages in job log.
166	Control record cannot be updated because it is not enqueued.
168	Update failed. Record too long. No room in block.
170	IOADBSB# load failed.
172	READQ failed. Another block is already enqueued.
174	Function OPEN0 (exclusively) failed.
176	Function UPDATE0 failed. Data corrupted.
178	Function UPDATE0 failed. No appropriate enq.
180	Buffering not initialized. Internal error.
182	ENQ error.
184	Error during record compression / decompression.
186	Attempted to write the wrong extent of a multi-extent data set.
204	Record not found.
208	Error accessing the file.
212	Insufficient memory for internal buffers.
216	Internal error.
218	The structure of the index tree is corrupted. A key on a higher level of the tree does not match the last key on a lower level.
219	The structure of the index tree is corrupted. The indicated key value, or a higher value, was not found in the block.
220	Invalid function.
224	Invalid timestamp
284	Invalid chain of index elements - rebuild index and rerun process.

The system action depends on which component was accessing the user file. Usually, the current routine terminates. Additional messages clarifying the source of the error are written to the IOA Log file before this message.

Corrective Action: Do the following:

For return codes 200 and higher,

rebuild the index component
rerun the process

For all other return codes,

search the IOA Log file and the relevant job log for messages clarifying the source of the error
correct the error
rerun the job

If the error persists, contact BMC Customer Support.

CTDUF0I CTDUFPRT STARTED

Explanation: This information message indicates that CTDUFPRT, the user records printing utility, started.

Corrective Action: No action is required.

CTDUF1E INVALID PARAMETER: parm

Explanation: The parm input parameter specified for the CTDUFPRT utility is not valid.

The utility stops.

Corrective Action: Correct the invalid input parameter and rerun the job.

CTDUF2E REDUNDANT PARAMETER: parm

Explanation: The parm input parameter for the CTDUFPRT utility has already been specified. The same parameter is specified twice.

The utility stops.

Corrective Action: Delete the extra JCL input parameter and rerun the job.

CTDUF3E THE PARAMETER parm MUST BE SPECIFIED

Explanation: The parm input parameter for the CTDUFPRT utility is missing. The CTVUFPRT utility requires the parm parameter.

The CTDUFPRT utility stops.

Corrective Action: Insert the missing JCL parameter and rerun the job.

CTDUF4E THE PARAMETER parm CANNOT BE SPECIFIED FOR RECORD TYPE x

Explanation: The parm input parameter for the CTDUFPRT utility cannot be specified for record type x which is specified in the RECORD parameter.

The CTDUFPRT utility stops.

Corrective Action: Delete the problematic JCL input parameter and rerun the job.

CTDUF5I INPUT PARAMETER: parm

Explanation: This information message identifies that the parm input parameter for the CTDUFPRT utility is specified.

Corrective Action: No action is required.

CTDUF6I NUMBER OF SELECTED RECORDS: num

Explanation: This information message issues total number of records selected by the CTDUFPRT utility.

Corrective Action: No action is required.

CTDUF9I recordType RECORDS: num

Explanation: This information message follows the CTDUF6I message if the RECORD parameter is not specified for the CTDUFPRT utility.

Each such message issues the number of selected records of the specified record type.

Corrective Action: No action is required.

CTDUFEI CTDUFPRT ENDED WITH ERRORS

Explanation: This information message indicates that the CTDUFPRT utility finished with errors.

Corrective Action: Examine other messages relating to the CTDUFPRT utility to identify and fix the problem, then rerun the utility.

CTDUFFI CTDUFPRT ENDED OK

Explanation: This information message indicates that the CTDUFPRT utility finished successfully.

Corrective Action: No action is required.

CTDUFGI CONTROL-V UTILITY CTVSCTT STARTED

Explanation: This information message indicates that the CTVSCTT utility was started.

Corrective Action: No action is required.

CTDUFHI CONTROL-V UTILITY CTVSCTT STOPPED BECAUSE OF ERRORS

Explanation: This information message indicates that the CTVSCTT utility stopped working because of severe errors detected during the utility run.

The CTVSCTT utility ends with a return code of 08.

Corrective Action: Examine the accompanying messages for the cause of the problem and take action accordingly.

CTDUFII CONTROL-V UTILITY CTVSCTT ENDED

Explanation: This information message indicates that the CTVSCTT utility ended and the output file was created that contains information about the data sets that were migrated to tape.

Corrective Action: No action is required.

CTDUFKE MEDIA NAME media NOT FOUND IN IOASPRM

Explanation: The CTVSCTT utility read a SYSDATA or Index record from the Migrated User file with a media name that does not exist in the IOASPRM parameters member.

The problematic record is skipped and the CTVSCTT utility continues processing.

Corrective Action: Check the media name issued in the message. If there were reports that were migrated to this media, add this media to the IOASPRM member and rerun the utility.

CTDUFLE THE PARAMETER 'FIELD' CAN BE SPECIFIED AFTER PRINTFORM=REPORT ONLY

Explanation: This error message is issued when the FIELD parameter was encountered, in the input stream for the CTDUFPRT utility, before the PRINTFORM=REPORT parameter was specified.

The utility stops.

Corrective Action: Correct the input parameters and rerun the job.

CTDUFME FIELD= fieldName CANNOT BE SPECIFIED FOR RECORD TYPE type

Explanation: This error message is issued when the CTDUFPRT utility has been submitted and the following conditions are true:

PRINTFORM parameter is set to REPORT (PRINTFORM=REPORT)
FIELD parameter set to a field name that is not permitted for the record type (type) specified

The utility stops.

Corrective Action: Use the following procedure to correct this issue:

Check the list of field names allowed for the printed records type. For more information, see the INCONTROL for z/OS Utilities Guide.
Correct the input parameters
Rerun the job

Parent Topic

CTD messages