DFH56xx (DFHCSDUP) messages

DFH5600 E
UNABLE TO GET STORAGE FOR MODULE DFHCICS. PRIMARY CSD HAS NOT BEEN INITIALIZED.
Explanation:

There is insufficient storage to load module DFHCICS.

System action:

Processing of the INITIALIZE command is terminated.

User response:

Ensure that there is sufficient storage to load the DFHCICS module.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5601 E
UNABLE TO LOAD THE {FCT | RDT | LD} TABLE NAMED table.
Explanation:

Table table cannot be loaded.

System action:

The system action depends on the type of table.

LD
DFHCSDUP cannot process the command. The 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.
FCT or RDT
The CSD utility cannot load the table, and terminates the processing of the utility command.
User response:

Refer to the preceding MVS message which should specify the reason for the failure.

If your FCT or TCT assembly and link-editing is successful, the FCT or 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

DFH5602 E
UNABLE TO UNLOAD THE {FCT | RDT |LD} TABLE NAMED table.
Explanation:

Table table cannot be unloaded.

System action:

The system action depends on the type of table.

LD
DFHCSDUP cannot process the command. The 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.
FCT or RDT
The CSD utility cannot unload the table, and terminates the processing of the utility command.
User response:

Refer to the preceding MVS message which should specify the reason for the failure.

If your FCT or TCT assembly and link-editing is successful, the FCT or 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

DFH5603 E
UNABLE TO LOCATE THE {FCT | RDT |LD | DCT} TABLE NAMED table.
Explanation:

Table table cannot be located.

System action:

The system action depends on the type of table specified.

LD
DFHCSDUP cannot process the command. The 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.
FCT, RDT or DCT
The CSD utility cannot locate the table, and terminates the processing of the utility command.
User response:

Determine the reason for the failure.

If your FCT, TCT or DCT assembly and link-editing is successful, the FCT, RDT or DCT 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

DFH5604 E
UNABLE TO OBTAIN STORAGE FOR THE CROSS-REFERENCE TABLE NAMED table.
Explanation:

DFHCSDUP was unable to obtain storage for table table.

System action:

DFHCSDUP cannot process the command.

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:

Increase the region size and retry the command.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5605 E
DISALLOWED CHARACTER IN GROUP OR LIST NAME object.
Explanation:

The call to module DFHDMP has failed to construct a valid key for the record created on the CSD file. This is because the group or list name contains an invalid character.

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

DFH5606 S
COMMAND IS NOT EXECUTED. UNABLE TO LOAD THE SERVICE MODULE progname.
Explanation:

The service module, progname, cannot be loaded due to insufficient storage.

System action:

Utility command execution is terminated. If commands are being read from a SYSIN data stream by the utility, then subsequent commands are checked for syntax only.

User response:

Retry the utility command with an increased region size.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5607 S
COMMAND IS TERMINATED. AN ERROR OCCURRED WHILE READING THE FIRST SECONDARY CSD RECORD.
Explanation:

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

System action:

The SERVICE command is terminated. If commands are being read from a SYSIN data stream by the utility, then subsequent commands are checked for syntax only.

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 FROMCSD parameter in the SERVICE utility command.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5608 S
COMMAND IS TERMINATED. AN ERROR OCCURRED WHILE READING A SECONDARY CSD RECORD.
Explanation:

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

System action:

The SERVICE command is terminated. If commands are being read from a SYSIN data stream by the utility, then subsequent commands are checked for syntax only.

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 FROMCSD parameter in the SERVICE utility command.

If the problem persists, try to obtain a print out of the CSD, using either IDCAMS or the DFHCSDUP LIST ALL option. The LIST will indicate where errors have occurred because they will not print and are therefore easily identifiable.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5609 S
COMMAND IS TERMINATED. AN ERROR OCCURRED WHILE WRITING A PRIMARY CSD RECORD.
Explanation:

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

System action:

The SERVICE command is terminated. If commands are being read from a SYSIN data stream by the utility, then subsequent commands are checked for syntax only.

User response:

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

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

SYSPRINT

Modules:

DFHCSDUP

DFH5611 E
COMMAND NOT EXECUTED. parameter PARAMETER MUST BEGIN WITH 'DFH'.
Explanation:

In a CSD utility MIGRATE command, the specified parameter contained an invalid table name or group name.

System action:

The utility does not process the command.

User response:

Resubmit the MIGRATE command with a valid table name or group name.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5612 I
resource object IN GROUP grpname IS UNCHANGED.
Explanation:

A resource definition existed in both source and target groups. Based on the CSD utility commands submitted, the utility has replaced the resource definition in the target group.

System action:

Normal utility processing continues.

User response:

None.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5613 E
UNABLE TO LOCATE THE LIBRARY MEMBER member.
Explanation:

The member is not in the libraries named in the JCL.

System action:

The utility terminates processing of the command that required access to library member member.

User response:

Ensure that the member is correctly link-edited into the library and resubmit the job.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5614 E
UNABLE TO LOAD THE LIBRARY MEMBER member.
Explanation:

DFHCSDUP could not load library member member.

System action:

The utility terminates processing of the command that required access to the library member.

User response:

Ensure that the member is correctly link-edited into the library and resubmit the job.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5617 S
COMMAND IS TERMINATED. AN UNRECOGNIZED TYPE OF RECORD WAS ENCOUNTERED WHILE SECONDARY CSD WAS BEING READ.
Explanation:

The record-type field of an input CSD record is invalid.

System action:

The SERVICE command is terminated. If commands are being read from a SYSIN data stream by the utility, then subsequent commands are checked for syntax only.

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 FROMCSD parameter in the SERVICE utility command.

If the problem persists, try to obtain a print out of the CSD, using either IDCAMS or the DFHCSDUP LIST ALL option. The LIST will indicate where errors have occurred because they will not print and are therefore easily identifiable.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5618 I
AN ATTENTION INTERRUPT WAS REQUESTED DURING DFHCSDUP EXECUTION.
Explanation:

An attention interrupt has been requested while DFHCSDUP is executing in a TSO environment.

System action:

Normal utility processing continues.

Control is passed to a put-message exit if one has been specified on the extended entry linkage. Refer to the CICS® Customization Guide for more information about put-message exits.

User response:

None.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5619 W
AN INVALID VALUE OF THE PAGESIZE PARAMETER HAS BEEN SPECIFIED. THE DEFAULT VALUE OF 60 LINES PER PAGE WILL BE USED.
Explanation:

A value of the PAGESIZE parameter outside the allowed range (4-9999) has been specified.

System action:

The default value of 60 lines per page is taken.

User response:

Ensure that a valid PAGESIZE value is specified in future.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5620 E
AN ILLEGAL RETURN CODE (RC= ret-code) HAS BEEN RETURNED FROM THE {INITIALIZATION | GET-COMMAND |TERMINATION} EXIT.
Explanation:

The specified user-exit routine has returned a disallowed return code.

System action:

Processing of the utility command is terminated. The exit is not disabled.

User response:

Investigate the specified exit routine for the cause of the illegal return code.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5621 E
A NON-ZERO RETURN CODE HAS BEEN RETURNED FROM THE PUT-MESSAGE EXIT.
Explanation:

The put-message exit routine has returned a disallowed return code.

System action:

Processing of the utility command is terminated and the put-message exit is disabled.

User response:

Investigate the put-message exit routine for the cause of the illegal return code.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5622 S
THE SECONDARY CSD HAS BEEN CLOSED DURING CLEAN-UP PROCESSING FOLLOWING THE INTERCEPTION OF AN ABEND.
Explanation:

An Abend has occurred during DFHCSDUP processing. The secondary CSD has been closed during post ABEND clean up processing.

System action:

Processing of the utility command is terminated.

User response:

Refer to prior messages for further information regarding this problem.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5623 S
THE PRIMARY CSD HAS BEEN CLOSED DURING CLEAN-UP PROCESSING FOLLOWING THE INTERCEPTION OF AN ABEND.
Explanation:

An abend has occurred during DFHCSDUP processing. The primary CSD has been closed during post ABEND clean up processing.

System action:

Processing of the utility command is terminated.

User response:

Refer to prior messages for further information regarding this problem.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5624 S
THE EXTRACT EXIT PROGRAM HAS BEEN UNLOADED DURING CLEAN-UP PROCESSING FOLLOWING THE INTERCEPTION OF AN ABEND.
Explanation:

An abend has occurred during the processing of an EXTRACT command. The extract exit program specified on the USERPROGRAM keyword of the EXTRACT utility command has been unloaded during post-abend clean-up processing.

System action:

The EXTRACT command is terminated.

User response:

Refer to prior messages for further information regarding the problem.

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

SYSPRINT

Modules:

DFHCSDUP

DFH5625
THE USER PROGRAM HAS PASSED AN INVALID DDNAME PARAMETER FOR ddname TO DFHCSDUP.
Explanation:

The user program has supplied an alternative ddname as a parameter for either DFHCSD, SYSIN or SYSPRINT. The alternative ddname is invalid because it begins with a blank.

System action:

The default DDNAME is used instead.

User response:

Correct the invalid DDNAME parameter.

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

Console

Modules:

DFHCSDUP

Start of changeDFH5630 WEnd of change
Start of changeNO IBM SUPPLIED DEFINITION FOUND FOR resourcetype resourcename.End of change
Start of change
Explanation:

While performing a SCAN command, the named resource type was not found in the CSD file on any of the IBM supplied groups. Note that compatibility groups are not used for the SCAN command.

End of change
Start of change
System action:

The utility continues.

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:

Console

End of change
Modules:

Start of changeDFHCSDUPEnd of change

Start of changeDFH5631 IEnd of change
Start of changeresourcetype resourcename IN GROUP groupname1 MATCHES THE IBM SUPPLIED DEFINITION IN GROUP groupname2.End of change
Start of change
Explanation:

While performing a SCAN command, the resource resourcetype name resourcename was found in group groupname1 and it matches the IBM supplied definition in group groupname2

End of change
Start of change
System action:

The utility continues.

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:

Console

End of change
Modules:

Start of changeDFHCSDUPEnd of change

Start of changeDFH5632 IEnd of change
Start of changeresourcetype resourcename IN GROUP groupname1 DOES NOT MATCH THE IBM SUPPLIED DEFINITION IN GROUP groupname2.End of change
Start of change
Explanation:

While performing a SCAN command, the resource resourcetype name resourcename was found in group groupname1 and it does not match the IBM supplied definition in group groupname2

End of change
Start of change
System action:

The utility continues.

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:

Console

End of change
Modules:

Start of changeDFHCSDUPEnd of change

Start of changeDFH5633 IEnd of change
Start of changeresourcetype resourcename FOUND IN GROUP groupname.End of change
Start of change
Explanation:

While performing a SCAN command, the resource resourcetype name resourcename was found in group groupname. No IBM supplied definition was found to perform a compare against.

End of change
Start of change
System action:

The utility continues.

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:

Console

End of change
Modules:

Start of changeDFHCSDUPEnd of change

Start of changeDFH5634 WEnd of change
Start of changeresourcetype resourcename NOT FOUND IN USER GROUPS.End of change
Start of change
Explanation:

While performing a SCAN command, the resource resourcetype name resourcename was not found in any user groups.

End of change
Start of change
System action:

The utility continues.

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:

Console

End of change
Modules:

Start of changeDFHCSDUPEnd of change

[[ Contents Previous Page | Next Page Index ]]