DFH51xx (DFHCSDUP) messages

DFH5100 S
SEVERE ERROR IN MODULE modname. ABEND CODE: abcode
Explanation:

An internal error has occurred in module modname, when invoked by a CSD utility command.

System action:

Processing terminates abnormally with an operating system dump and abend code abcode. The CSD utility attempts to:

  1. Close any files previously opened internally.
  2. Unload any extract exit routines that were dynamically loaded.
  3. Invoke the termination exit routine (if supplied).
  4. Return control to the invoker of the utility.
User response:

See the description of abend code abcode for guidance.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5101 I
command COMMAND EXECUTED SUCCESSFULLY.
Explanation:

The execution of a CSD utility command command completed successfully.

System action:

Normal processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5102 I
WARNING MESSAGES ISSUED WHILE PROCESSING command COMMAND.
Explanation:

The CSD utility issued messages during syntax-checking and execution of the command command.

System action:

Normal utility processing continues to the end of the job.

User response:

Review the warning messages to see how they have affected utility processing. Then decide whether you need to submit a further CSD utility job.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5103 I
ERROR(S) OCCURRED WHILE PROCESSING command COMMAND.
Explanation:

The CSD utility either found a syntax error in the utility command command, or the command command failed to execute correctly.

System action:

Utility command execution is terminated.

If commands are being read from a SYSIN data stream by the utility, then subsequent commands (except LIST) are checked for syntax only. (If the primary CSD file cannot be opened, LIST is not processed either.)

If commands are being read from a get-command exit, then DFHCSDUP attempts to process subsequent commands.

User response:

If the command failed because of syntax errors, correct the command.

If the command failed to execute correctly, this may have been caused by a previous error. In such a situation, an associated error message, such as DFH5275, should have been issued. Refer to these error messages for further guidance.

Correct all errors before trying to open the CSD file again.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5104 W
SUBSEQUENT COMMANDS (EXCEPT LIST) ARE NOT EXECUTED BECAUSE OF ERROR(S) ABOVE.
Explanation:

After the CSD utility program encounters an error, it ceases to execute any further commands read from a data stream (as opposed to supplied by a Put-Message exit routine). However, it continues to check the syntax of subsequent commands. The exception is the LIST command, which will still be executed if the primary CSD file can be opened.

System action:

Subsequent CSD utility commands (except LIST) are ignored.

User response:

Check for a syntax error in the commands used and correct it.

There should be associated error messages which identify the problem that caused DFHCSDUP to halt active processing. These messages should appear in DFHCSDUP output before. message DFH5104 is issued.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5105 W
command COMMAND NOT EXECUTED BECAUSE OF PREVIOUS ERROR(S).
Explanation:

If a syntax error (or an execution error) occurred in a command read from a data stream and processed earlier, no further commands (except for LIST commands) are executed. If the primary CSD file could not be opened, the LIST command is not executed either.

System action:

The CSD utility command is not executed.

User response:

Check for syntax errors or execution errors in commands processed earlier.

Correct the invalid commands.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5107 I
COMMANDS EXECUTED SUCCESSFULLY: nn COMMANDS GIVING WARNINGS: nn COMMANDS IN ERROR: nn
Explanation:

The CSD utility has completed input command processing.

Commands giving warnings may or may not have been executed successfully.

System action:

Normal processing continues to the end of the job.

User response:

If any CSD utility commands in error were executed, decide if the results are what you want.

If they are NOT what you want, correct them and resubmit them in another job.

If any commands were not executed, you must resubmit them. (See message DFH5108.)

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5108 I
COMMANDS NOT EXECUTED AFTER ERROR(S): nn
Explanation:

The CSD utility has completed input command processing. The number of commands not executed because of errors is indicated by nn.

System action:

Normal processing continues to the end of the job.

User response:

Correct the commands in error and resubmit them in another job.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5109 I
END OF DFHCSDUP UTILITY JOB. HIGHEST RETURN CODE WAS: retcode
Explanation:

The CSD utility job is complete.

System action:

Control returns to the invoker, that is, either the operating system or to an invoking program.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5110 W
ERROR FOUND IN 'PARM=' PARAMETER DATA ON EXEC JOB STEP. THIS DATA IS IGNORED.
Explanation:

The value of the PARM parameter on the EXEC job in the JCL to run the DFHCSDUP utility is incorrect.

System action:

The PARM parameter is ignored. The CSD is opened for read and write operations.

User response:

Correct the erroneous PARM value. The incorrect value can be found in the job step.

The CICS® Operations and Utilities Guide describes how to code the PARM parameter.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5114 S
THE {PRIMARY | SECONDARY} CSD HAS NOT BEEN INITIALIZED. COMMAND NOT EXECUTED.
Explanation:

The primary CSD file must be initialized before any CSD utility command (other than the INITIALIZE or SERVICE commands) can be processed. If a secondary CSD file is used, it must always be initialized before this command can be processed. CICS issues this message if you try to break either of these rules, or if an attempt to initialize a CSD file fails to complete successfully

System action:

The CSD utility ignores the command.

User response:

Initialize the CSD file. You may first have to determine why a previous initialization attempt failed.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5115 S
THE PRIMARY CSD IS ALREADY INITIALIZED. COMMAND NOT EXECUTED.
Explanation:

An INITIALIZE or a SERVICE command was encountered but the primary CSD file has already been initialized.

System action:

The INITIALIZE or SERVICE command is ignored.

User response:

Confirm that the correct CSD file was specified.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5116 S
THE PRIMARY CSD HAS BEEN DEFINED WITH AN INVALID KEY LENGTH. PROCESSING IS TERMINATED.
Explanation:

The CSD utility cannot initialize the CSD file because it has been defined to VSAM with an invalid key length.

System action:

The CSD file remains uninitialized, and no utility commands are processed.

User response:

Delete the CSD file, using VSAM Access Method Services (AMS). In the JCL defining the CSD cluster, change the AMS control statements to specify KEYS(22 0). Use this JCL to redefine the CSD file, and use the CSD utility to reinitialize it.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5117 S
THE PRIMARY CSD HAS BEEN DEFINED WITH AN INVALID RECORD SIZE. PROCESSING IS TERMINATED.
Explanation:

The CSD utility cannot initialize the CSD file, because it has been defined to VSAM with an invalid record length.

System action:

The CSD file remains uninitialized, and no utility commands are processed.

User response:

Delete the CSD file, using VSAM Access Method Services (AMS). In the JCL defining the CSD cluster, change the AMS control Start of changestatements to specify RECORDSIZE(200 2000). Use this JCL toEnd of change redefine the CSD file, and use the CSD utility to reinitialize it.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5120 I
{PRIMARY | SECONDARY} CSD OPENED; DDNAME: ddname
Explanation:

The VSAM data set specified in the JCL has been successfully opened, and is identified as the primary or secondary CSD file. (All utility commands processed will use the same primary CSD file. Different secondary CSD files may be accessed by different utility commands.)

System action:

Normal processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5121 S
I/O ERROR WHILE OPENING {PRIMARY | SECONDARY} CSD; DDNAME: ddname
Explanation:

An I/O error occurred when reading or writing control records of the VSAM data set identified in the JCL as the primary or secondary CSD file.

System action:

The utility command is not executed.

User response:

Retry the utility command that failed. If the problem persists, restore the CSD file from your own backup procedures.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5122 S
VSAM ERROR WHILE OPENING {PRIMARY | SECONDARY} CSD; DDNAME: ddname
Explanation:

A VSAM error occurred when opening the data set identified in the JCL as a primary or secondary CSD file.

System action:

The utility command is not executed.

User response:

Refer to the VSAM diagnostics output in message DFH5179 for further information and guidance.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5123 I
{PRIMARY | SECONDARY} CSD CLOSED; DDNAME: ddname
Explanation:

The VSAM data set used as the primary or secondary CSD file has been successfully closed, with control records updated if necessary. (The primary CSD file is closed after all the utility commands have been processed; the secondary CSD file is closed after the command for which it was opened.)

System action:

Normal processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5124 S
PROCESSING TERMINATED. CORRUPTED CSD CONTROL RECORD DETECTED WHILE CLOSING CSD; DDNAME: ddname
Explanation:

A storage corruption is preventing the CSD control records from being updated when the CSD file is being closed.

System action:

No further CSD utility commands are processed.

User response:

Obtain a dump from DFHCSDUP together with a listing of the DFHCSDUP run and its JCL. Also try to obtain a print out of the CSD, using either IDCAMS or the DFHCSDUP LIST ALL option. The LIST will indicate where the errors have occurred because they do not print and are therefore easily identifiable.

Using the information available, determine the cause of the errors and correct them.

Resubmit the CSD utility commands that failed.

If you cannot resolve the problem, or if the problem persists, you will need further help from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5125 S
ERROR OCCURRED WHILE CLOSING THE CSD. FILE IS FULL; DDNAME: ddname
Explanation:

After processing the CSD utility commands, the CSD control records are updated before closing the data set.

Updating failed because data set ddname was full.

System action:

Utility command processing is terminated.

User response:

Initialize a new primary CSD file with a larger data set size. Then use the IDCAMS IMPORT and EXPORT commands to restore the CSD file onto a larger data set.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5126 S
I/O ERROR WHILE CLOSING THE {PRIMARY | SECONDARY} CSD; DDNAME: ddname
Explanation:

An I/O error occurred when reading or writing the control records of the CSD file, before closing VSAM data set ddname.

System action:

No further utility commands are executed.

User response:

Resubmit the utility commands that failed. If the problem persists, restore the CSD file from your own backup procedures.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5127 S
VSAM ERROR WHILE CLOSING {PRIMARY | SECONDARY} CSD; DDNAME: ddname
Explanation:

A VSAM error occurred when closing the data set ddname in the JCL as the primary or secondary CSD file.

System action:

No further CSD utility commands are executed.

User response:

Refer to the VSAM diagnostics output in message DFH5179 for further information and guidance.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5128 S
PROCESSING TERMINATED. {PRIMARY | SECONDARY} CSD ACCESSED BY ANOTHER USER AND COULD NOT BE SHARED. DDNAME: ddname
Explanation:

An attempt to open the CSD has returned an error from VSAM because the data set is not available for the type of processing requested.

This usually means that:

System action:

The command is not executed.

User response:

You can change the access mode in which you are trying to open the CSD.

Note:
You must specify PARM=CSD(READONLY) if you wish to open a recoverable CSD in RLS access mode from the DFHCSDUP utility program.

Alternatively, wait until the CSD file is no longer being accessed in the conflicting access mode, or until it becomes available again in accordance with the SHAREOPTIONS rules defined for the cluster.

If the conflict is due to SHAREOPTIONS and LIST is the only command you want to execute, you can specify PARM=CSD(READONLY).

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5130 E
UNABLE TO LOCATE MODULE DFHCICS. PRIMARY CSD NOT INITIALIZED.
Explanation:

The DFHCICS module is missing from the library.

System action:

Processing of the INITIALIZE command is terminated.

User response:

Ensure that the DFHCICS module is present in the library.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5131 I
LIST listid CREATED.
Explanation:

The INITIALIZE command has created the header for an IBM-protected list.

System action:

Normal processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5132 S
UNABLE TO CREATE LIST listid
Explanation:

The INITIALIZE command has failed when calling the CSD manager routing program, DFHDMP, to create a new list listid on the CSD file for the IBM-protected groups. The CSD file may be full or corrupt.

System action:

Processing of the INITIALIZE command is terminated.

User response:

Check that the data set size for the CSD file is large enough. If it is not, allocate more space.

If there is ample space and you suspect that the CSD file is corrupt, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5133 S
CSD CONTAINS ONE OR MORE LISTS. NO LISTS MAY BE PRESENT ON THE CSD WHEN THE INITIALIZE COMMAND IS ISSUED.
Explanation:

The CEDA transaction was used to create a list while the INITIALIZE command was executing.

System action:

Processing of the INITIALIZE command is terminated.

User response:

Redefine the data set and re-run the INITIALIZE command. The CEDA transaction must not be used until the initialization of the CSD file has been successfully completed.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5134 S
ERROR OCCURRED WHILE ADDING GROUP grpname TO LIST listid
Explanation:

A call to the CSD manager routing program, DFHDMP, to write the definition of group grpname to the CSD file as a member of an IBM-protected list listid created an error. The CSD file may be full or corrupt.

System action:

Processing of the INITIALIZE command is terminated.

User response:

Increase the data set size for the CSD file and repeat the INITIALIZE request. If this fails, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5135 I
GROUP grpname ADDED TO LIST listid
Explanation:

A group definition grpname has been satisfactorily created on the CSD file in list listid.

System action:

Processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5136 W
GROUP grpname IS ALREADY A MEMBER OF LIST listid
Explanation:

Group grpname already exists in list listid. CICS does not create a duplicate entry.

System action:

Normal utility processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5139 W
CONSIDER IMPLICATIONS OF MIGRATING TYPE=SHARED ENTRIES.
Explanation:

The CSD utility detected a migrate of a TST TYPE=SHARED entry. A DFHTST TYPE=SHARED entry is not directly migrated. Only when a TYPE=REMOTE macro that specifies a SYSIDNT that matches a SYSID in the corresponding TYPE=SHARED macro is a TSMODEL created.

System action:

The CSD utility continues processing of the MIGRATE command.

User response:

If SYSID is explicitly specified on the EXEC CICS request, or added by a global user exit program, and the intent of the SYSID is to direct the request to a SHARED TS pool, you must use the migrated TST in order to satisfy the request to use the pool. See the CICS Resource Definition Guide for more information.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5140 I
TOTAL xxxxxxxx DEFINITIONS CREATED: nn
Explanation:

CICS issued this message after migrating a CICS table. nn definitions of type xxxxxxxx have been created on the CSD file.

System action:

Normal utility processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5141 S
UNABLE TO CREATE NEW GROUP grpname
Explanation:

The MIGRATE command failed when calling the CSD manager routing program, DFHDMP, to create a new group grpname on the CSD file for the data in the table being migrated. The CSD file may be full, corrupt, or not initialized. The group name may be invalid.

System action:

Processing of the MIGRATE command is terminated.

User response:

Check the group name in the TOGROUP parameter. Reinitialize the CSD file with the INITIALIZE command, providing a larger data set size if necessary.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5142 E
COMMAND NOT EXECUTED. lgname WAS NOT UPDATED BECAUSE OF A PREVIOUS UPDATE FAILURE.
Explanation:

The list or group lgname cannot be used because an operation to update it, using the DFHCSDUP offline utility, failed to execute to completion.

This has probably happened in a previous execution of DFHCSDUP.

System action:

The command is not executed, and the execution of subsequent DFHCSDUP commands in the job stream is suppressed.

User response:

Use the DFHCSDUP VERIFY command to remove the in-flight flag detected when this message is produced.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5143 I
GROUP grpname CREATED.
Explanation:

A new CSD group, grpname, has been created for the data in the table being migrated.

System action:

Migration continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5145 E
COMMAND NOT EXECUTED. lgname HAS BEEN LOCKED BY APPLID: applid, OPID:opid TO PREVENT UPDATING.
Explanation:

The list or group lgname cannot be used because a user of the CEDA or CEDB transaction has enforced a LOCK command to prevent updating by other users.

System action:

The command is not executed.

If commands are being read from a SYSIN data stream, then subsequent commands (except the LISTcommand) are checked for syntax only. (If the primary CSD file cannot be opened, the LIST command is not processed either.)

If commands are being read from a get-command exit, then the DFHCSDUP utility attempts to process subsequent commands.

User response:

Negotiate with the user with the specified OPID and APPLID, or create a new group or list by taking a copy of the definitions in the locked one.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5146 E
COMMAND NOT EXECUTED. lgname IS CURRENTLY BEING UPDATED BY APPLID:applid, OPID:opid
Explanation:

The list or group lgname cannot be used because:

System action:

The command is not executed.

If commands are being read from a SYSIN data stream, then subsequent commands (except the LIST command) are checked for syntax only. (If the primary CSD file cannot be opened, the LIST command is not processed either.)

If commands are being read from a get-command exit, then the DFHCSDUP utility attempts to process subsequent commands.

User response:

Resubmit the utility job to retry the command that failed. Perform the subsequent commands that were suppressed.

If this fails to resolve the problem, run the DFHCSDUP VERIFY command to remove the in-flight flag detected when this message is produced.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5147 E
COMMAND NOT EXECUTED. lgname ALREADY EXISTS AS A {GROUP | LIST}
Explanation:

The name chosen for the target group (or list) duplicates that of an existing group or list on the CSD file.

System action:

Processing of the utility command is terminated.

User response:

Choose a different name for the target group.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5148 E
UNABLE TO GET STORAGE FOR {FCT | RDT |LD} TABLE NAMED table
Explanation:

There is insufficient storage to satisfy a GETMAIN request for table table.

System action:

The system action depends on the table specified as follows:

LD (language definition table)
The CSD utility cannot process any commands, and terminates with a dump. The MVS user abend code is 0327.
FCT and RDT
The CSD utility cannot migrate the table, and terminates processing of the utility command.
User response:

Allocate additional storage. If your TCT assembly and link-editing is successful, the RDT should be in the library. The LD is in the load library of the supplied pregenerated CICS system.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5149 E
COMMAND NOT EXECUTED. xxxxxxxx IS IBM-PROTECTED.
Explanation:

A user attempted to add a definition to an IBM-supplied group or list (groups or lists beginning with DFH). This is not allowed.

System action:

The CSD utility does not create a definition.

User response:

Change the input command or TCT source data to name a target group or list whose name does not begin with DFH.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5150 W
xxxxxxx OPTION CONFLICTS WITH yyyyyyy OPTION AND IS IGNORED FOR restype resname
Explanation:

The options, xxxxxxx and yyyyyyy, specified for the resource type restype with name resname are mutually exclusive.

System action:

The utility ignores option xxxxxxx.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

Start of changeDFH5151 IEnd of change
Start of changeRESOURCE NOT ALTERED. xxxxxxxx IS IBM-PROTECTED.End of change
Start of change
Explanation:

During the execution of an ALTER command containing a generic group name, a matching group was found which is an IBM-supplied group and is protected.

End of change
Start of change
System action:

The CSD utility does not alter the definition in the specified group.

End of change
Start of change
User response:

None.

Note:
This message cannot be changed with the message editing utility.
End of change
Start of change
Destination:

SYSPRINT

End of change
Modules:

Start of changeDFHCSDUPEnd of change

DFH5155 W
{TDQUEUE} xxxxxxxx HAS SAME NAME AS AN IBM SUPPLIED DEFINITION IN GROUP grpname.
Explanation:

The name of the migrated table entry, xxxxxxxx, matches the name of an IBM-supplied resource in IBM-protected group grpname, created by the INITIALIZE command.

System action:

CICS migrates this entry normally.

User response:

If necessary, rename the resource, using the CEDA transaction.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5156 W
{TDQUEUE} DID NOT MIGRATE. ITS PROPERTIES MATCH AN IBM-SUPPLIED DEFINITION IN GROUP grpname.
Explanation:

The properties of the resource defined in the user’s table entry are the same as those of the IBM-supplied resource of the same name contained in IBM-protected group grpname.

System action:

The entry for the user’s resource is not migrated.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5159 I
resource object DEFINED IN GROUP grpname
Explanation:

The CSD utility has successfully added a resource definition to a group, where:

System action:

Normal utility processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5161 S
TABLE table MUST BE LINK-EDITED WITH AMODE(24) RMODE(24).
Explanation:

After loading the table table, Start of changethe migration routine checks that the table being processed has been link-edited with the correct AMODE and RMODE attributes. For migration purposes, DCTs, FCTs and TCTs must be link-edited with AMODE(24) RMODE(24). RCTs must be link-edited with RMODE(24).End of change

System action:

The MIGRATE command is not processed.

User response:

Relink the table with the correct attributes. Start of changeFor example, when migrating a DCT to your CSD include the following statement in your DCT: DFHDCT TYPE=(INITIAL,MIGRATE). For more information about migrating tables to your CSD, refer to the CICS Resource Definition Guide.End of change

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5164 W
NO DEFINITION OF resource object CREATED. THIS DUPLICATES AN EXISTING DEFINITION IN GROUP grpname
Explanation:

The CSD utility detected a CSD record with a matching key before adding the definition to the CSD file, where:

System action:

The CSD utility does not migrate the resource definition to the CSD file. (If it is a transaction, a generated profile is not created either.)

User response:

Use the CEDA transaction to define the resource with a unique name.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5165 S
PROCESSING IS TERMINATED. AN ERROR OCCURRED WHILE WRITING resource object TO THE CSD.
Explanation:

An error occurred when the CSD utility called DFHDMP to write the definition of the object object to the CSD file.

The CSD file may be full or corrupted.

resource is the type of resource.

System action:

If the CSD is full, the CSD utility issues message DFH5176, and then terminates with a return code of 12 in message DFH5109.

If the CSD is not full, the CSD utility terminates abnormally with message DFH5175, usually accompanied by one or more of the explanatory messages, DFH5177, DFH5178, and DFH5179.

User response:

Use the additional messages to determine the cause of the error and the appropriate user action required.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5166 E
DISALLOWED CHARACTER IN resource NAME object
Explanation:

The call to module DFHDMP has failed to construct a valid key for the record created on the CSD file because of an invalid character, or the resource name for the migrated table entry may be invalid. resource is the type of resource, and object is the name of the object.

System action:

A CSD record is not created for this definition. (If it is a transaction, a generated profile is not created either.)

User response:

Use the CEDA transaction to define the resource with a valid name.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5167 S
THE CSECTS IN TABLE table HAVE BEEN LINK-EDITED IN THE WRONG ORDER.
Explanation:

While processing a MIGRATE command, the CSD utility has detected that the CSECTs in table table are in the wrong order. Input to the linkage editor omitted a control statement to order the CSECTs.

System action:

The CSD utility does not process the MIGRATE command.

User response:

Use the IBM-supplied procedure, DFHAUPLK, to assemble and link-edit CICS tables. This procedure ensures the correct ordering of CSECTs within the tables.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5168 S
TABLE LOADED FROM LIBRARY MEMBER table IS NOT A VALID {FCT | RDT | TCT}.
Explanation:

After loading the table table, the migration routine checks the VMNAME field in the DFHVM expansion of the data area following the load point. This message is produced if VMNAME is not that of a valid table.

System action:

The MIGRATE command is not processed.

User response:

  1. Ensure that the correct table is present in the library, and that the TABLE parameter of the MIGRATE command is correct.
  2. Ensure that an ORDER statement was processed in the JCL of the link-editing of the table.
Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5169 S
PROCESSING IS TERMINATED. TABLE table WAS ASSEMBLED FOR CICS RELEASE rrr. REASSEMBLE FOR RELEASE sss.
Explanation:

After loading the table table, the migration routine checks the VMVERS field in the DFHVM expansion of the data area following the load point. This field indicates the CICS release (rrr) for which the table was assembled, and is invalid for the CICS system (release sss) that is running.

System action:

The MIGRATE command is not processed.

User response:

Reassemble the table for the correct release of CICS.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5174 W
PROCESSING IS TERMINATED. COMMAND CANNOT BE EXECUTED BECAUSE 'PARM=CSD(READONLY)' WAS SPECIFIED.
Explanation:

This command requires the CSD to be opened for read-write access. Your job step specified read-only access for the CSD in the DFHCSDUP utility job stream.

System action:

This command is not executed.

If commands are being read from a SYSIN data stream, subsequent commands (except LIST) are checked for syntax only. (If the primary CSD file cannot be opened, LIST is not processed either.)

If commands are being read from a get-command exit, DFHCSDUP attempts to process subsequent commands.

User response:

Amend the JCL to specify ‘PARM=CSD(READWRITE)’.

Note:
If the CSD is recoverable, and you are accessing it in RLS mode, you cannot specify READWRITE access. To perform the command, access the CSD in non-RLS mode.
Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5175 S
PROCESSING IS TERMINATED. UNEXPECTED RESPONSE FROM function IN CSD MANAGER.
Explanation:

An invocation of the CSD manager, DFHDMP, has resulted in an error. The name of the function that failed is function.

System action:

DFHCSDUP issues additional messages and then

User response:

Ensure that you have set up your CSD file correctly. If you have migrated your CSD file from a previous release, note that you should have increased your block size to 500. If necessary, use the diagnostics in the additional messages.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5176 S
PROCESSING IS TERMINATED. CSD IS FULL.
Explanation:

The VSAM data set containing the CSD file is full.

System action:

Execution of the CSD utility command is terminated.

If commands are being read from a SYSIN data stream, then subsequent commands (except LIST commands) are checked for syntax only. (If the primary CSD file cannot be opened, the LIST command is not processed either.)

If commands are being read from a get-command exit, then the DFHCSDUP utility attempts to process subsequent commands.

The DFHCSDUP utility leaves a system lock on the group being created at the time of failure. This lock prevents processing of the group by the CSD utility or the CEDA transaction.

User response:

First, use the DFHCSDUP VERIFY process to remove the system lock on the partly-created group. Normal RDO processing of the group should then be possible, enabling the group (or any unwanted definitions) to be deleted.

To recover the contents of the CSD file, define a larger data set and use the AMS REPRO command. Usually, you will be able to REPRO from the CSD file that became full. If you are unable to do this, use a backup copy. (You may be able to transfer definitions from the CSD file that filled up by using the DFHCSDUP COPY command with the FROMCSD option.)

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5177 S
PROCESSING IS TERMINATED. CSD I/O ERROR OCCURRED.
Explanation:

An I/O error occurred when executing a READ or WRITE of a CSD record on the primary or secondary CSD file.

System action:

DFHCSDUP issues additional messages and terminates abnormally.

User response:

Restore the CSD file to a new data set from your own backup, or create the new CSD file by using the INITIALIZE, COPY, and APPEND commands to restore existing definitions.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5178 S
PROCESSING IS TERMINATED. SEVERE CSD ERROR OCCURRED.
Explanation:

An error occurred during execution of the CSD manager, DFHDMP, to access the primary or secondary CSD file.

System action:

DFHCSDUP issues additional messages and terminates abnormally.

User response:

See the VSAM diagnostics given in message DFH5179.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5179 S
VSAM ERROR. RETURN CODE = nn ERROR CODE = ddd(yy) CONTROL BLOCK TYPE = {RPL | ACB}
Explanation:

VSAM returned the following diagnostics when an error occurred, where:

System action:

The CSD utility terminates command processing, and in some situations, produces an operating system dump.

User response:

For the meaning of the VSAM return and error codes, refer to the DFSMS/MVS V1R3 Macro Instructions for Data Sets manual.

When interpreting these diagnostics, ensure that the data set referenced in the JCL exists.

Check the following:

If DFHCSDUP specifies RLS access mode, a ‘record not found’ error could mean that the CSD has not been initialized.

Note:
You must use non-RLS access mode to initialize a recoverable CSD.
Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5180 S
PROCESSING IS TERMINATED. ERROR OCCURRED WHILE CSD WAS BEING READ BY {SETBROWSE | GETNEXT} {SCANSETS | SCANOBJS}
Explanation:

When the LIST command invoked DFHDMP to scan the objects on the CSD file, an error occurred during execution of the DFHDMP function.

System action:

The CSD utility terminates with an MVS abend 0325.

User response:

This error should be reported. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5181 W
NO MATCH FOUND FOR GENERIC {GROUP | LIST} IDENTIFIER xxxxxxxx
Explanation:

The LIST command was executed with a generic group or list name, but no qualifying group or list exists on the CSD file.

System action:

Normal processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5182 W
{GROUP | LIST} xxxxxxxx DOES NOT EXIST.
Explanation:

The LIST command or the DELETE command was executed using the name of a group or list that does not exist on the primary CSD file.

System action:

The LIST command or the DELETE command is not processed. Subsequent commands may still be processed.

User response:

Correct the LIST command or the DELETE command to use a valid group or list name.

If a CSD upgrade is being performed, no user action is required.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5183 W
{GROUP | LIST} xxxxxxxx EXISTS AS A {GROUP | LIST} NAME.
Explanation:

The LIST command or the DELETE command was executed using a group name that is already in use as a list name, or using a list name that is already in use as a group name.

System action:

The LIST command or the DELETE command is not processed. Subsequent commands may still be processed.

User response:

Correct the LIST command or the DELETE command to use a valid group or list name.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5184 S
PROCESSING IS TERMINATED. INVALID OUTPUT FROM DFHPUP. CANNOT FORMAT DATA FOR UTILITY LISTING.
Explanation:

There has been an internal logic error in the DFHCSDUP utility program. The data in the back-translated output buffer is invalid. The length code may be out of range or the data fields in the wrong sequence. One or more of the data fields may be invalid.

System action:

The CSD utility terminates with an MVS abend 0326.

User response:

This error must be reported.

Obtain a dump from DFHCSDUP together with a listing of the DFHCSDUP run and its JCL. Also try to obtain a print out of the CSD, using either IDCAMS or the DFHCSDUP LIST ALL option. The LIST will indicate where the error(s) have occurred because they will refuse to print and are therefore easily identifiable.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5186 W
NO RESOURCES DEFINED IN GROUP grpname OR NO GROUPS DEFINED IN LIST lstid
Explanation:

In executing a LIST command, the CSD utility has found a group or list header on the CSD file for which no corresponding group or list elements exist.

System action:

The utility continues to process the LIST command, but will not tabulate elements of the group or list named in the message.

User response:

Run the DFHCSDUP VERIFY utility.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5187 I
resource IS LOCKED, BUT IS NOT THE NAME OF A GROUP OR LIST.
Explanation:

The CSD utility detected a locked resource that is not a group or list. The reason is that an interrupt or failure occurred during a CEDA transaction or a previous utility job. A lock had been created but not the associated group or list.

System action:

The utility continues normal processing of the VERIFY command.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5188 I
{GROUP | LIST | RESERVED NAME} resource IS NOW AVAILABLE FOR USE.
Explanation:

The VERIFY command discovered that the resource was not available for the CEDA transaction or offline commands. The restriction on its availability, which was due to the failure of some previous command affecting it, has now been removed.

System action:

Normal processing of the VERIFY command continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5189 I
CSD VERIFY PROCESS COMPLETED SUCCESSFULLY.
Explanation:

The VERIFY command has been processed successfully, and any internal locks associated with groups and lists on the CSD file have been removed.

System action:

Normal processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5190 S
COMMAND IS NOT EXECUTED. UNABLE TO GET STORAGE FOR SERVICE MODULE progname
Explanation:

There is insufficient storage available to load the service module progname, that is to be loaded and executed by DFHCSDUP.

System action:

Utility command execution is terminated.

If commands are being read from a SYSIN data stream, then subsequent commands (except LIST commands) are checked for syntax only. (If the primary CSD file cannot be opened, the LIST command is not processed either.)

If commands are being read from a get-command exit, then DFHCSDUP attempts to process subsequent commands.

User response:

Ensure that there is sufficient storage allocated to load module progname.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5191 I
SERVICE PROGRAM progname IS RUNNING.
Explanation:

The service module progname has been loaded correctly. Execution of the module has started.

System action:

Normal processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5192 S
COMMAND IS NOT EXECUTED. CSD SERVICE LEVEL ttt IS INCOMPATIBLE WITH CURRENT SERVICE LEVEL sss
Explanation:

Either the LEVEL parameter specified in the SERVICE command is wrong, or an incorrect version of the CSD file is being used as the secondary (input) CSD file.

System action:

The SERVICE command is not executed.

If commands are being read from a SYSIN data stream, then subsequent commands (except LIST commands) are checked for syntax only. (If the primary CSD file cannot be opened, the LIST command is not processed either.)

If commands are being read from a get-command exit, then DFHCSDUP attempts to process subsequent commands.

User response:

The SERVICE command may upgrade the service level of the CSD file only in increments of one. Check that the input CSD file is the intended one, and that the LEVEL parameter takes the value one higher than the current service level of the CSD file.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5193 S
COMMAND IS NOT EXECUTED. SERVICE MODULE progname IS UNABLE TO UPGRADE CSD TO TARGET SERVICE LEVEL ttt
Explanation:

The LEVEL parameter specified in the SERVICE command is incompatible with the status of the service module progname being applied to the CSD file.

System action:

The SERVICE command is not executed.

If commands are being read from a SYSIN data stream, then subsequent commands (except LIST commands) are checked for syntax only. (If the primary CSD file cannot be opened, the LIST command is not processed either.)

If commands are being read from a get-command exit, then DFHCSDUP attempts to process subsequent commands.

User response:

Ensure that the service module progname being applied, is correctly updated with the service fix supplied by IBM. (It should have been amended so as to be able to process SERVICE commands at the target level ttt.)

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5194 I
UPGRADING SERVICE STATUS OF CSD FROM LEVEL sss TO LEVEL ttt
Explanation:

The loaded service module is performing the required upgrade of the CSD file from service level sss to service level ttt.

System action:

Normal processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5195 I
EXECUTION OF SERVICE PROGRAM progname COMPLETE.
Explanation:

The loaded service program progname has run to completion. Control is being transferred back to the CSD offline utility program, DFHCSDUP.

System action:

Normal processing continues.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5196 S
COMMAND IS TERMINATED. ERROR OCCURRED WHILE READING CONTROL SECONDARY CSD RECORD.
Explanation:

An I/O error has occurred on the specified CSD file.

System action:

The SERVICE command is terminated.

If commands are being read from a SYSIN data stream, then subsequent commands (except LIST) are checked for syntax only. (If the primary CSD file cannot be opened, LIST is not processed either.)

If commands are being read from a get-command exit, then DFHCSDUP attempts to process subsequent commands.

User response:

Retry the command, ensuring that a sufficiently large data set size is specified for the output (primary) CSD file.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5197 S
COMMAND IS TERMINATED. UNRECOGNIZED CONTROL RECORD ENCOUNTERED WHILE SECONDARY CSD WAS BEING READ.
Explanation:

The contents of a control record of the secondary input CSD are invalid.

System action:

The SERVICE command is terminated.

If commands are being read from a SYSIN data stream, then subsequent commands (except LIST) are checked for syntax only. (If the primary CSD file cannot be opened, LIST is not processed either.)

If commands are being read from a get-command exit, then DFHCSDUP attempts to process subsequent commands.

User response:

Check that the input and output data sets have been correctly defined, and that the DDNAME for the secondary CSD file in the JCL corresponds to the OLDCSD parameter in the SERVICE utility command.

If the problem persists, you will need further help from IBM. First, obtain a dump from DFHCSDUP together with a listing of the DFHCSDUP run and its JCL. Also try to obtain a print out of the CSD using either IDCAMS or the DFHCSDUP LIST ALL option. The LIST indicates where the errors have occurred because they do not print and are therefore easily identifiable. See CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5198 I
CSD RECORD MODIFIED FOR xxxxxxxx
Explanation:

The specified modification to a record on the CSD file has taken place.

The insert, xxxxxxxx, is the element type.

System action:

Normal processing continues. If the modified record is an element in a GROUP or LIST, its date-and-time field is updated when copied to the output (primary) CSD file.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

DFH5199 W
INVALID FIELD ENCOUNTERED IN EXISTING RECORD FOR xxxxxxxx
Explanation:

An unexpected value was found in one of the fields of a CSD record that was to be modified for element xxxxxxxx.

System action:

Normal processing continues, and the invalid record is left unchanged on the new (primary) CSD file.

User response:

None.

Note:
This message cannot be changed with the message editing utility.
Destination:

SYSPRINT

Modules:

DFHCSDUP

[[ Contents Previous Page | Next Page Index ]]