Start of change

DFHADxxxx (DFHADP) messages

Start of changeDFHAD0001End of change
Start of changeapplid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.End of change
Start of change
Explanation:

An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in CICS code.

Alternatively:

The code aaa is, if applicable, a 3-digit hexadecimal MVS system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The 4-digit code bbbb, which follows aaa, is a user abend code produced either by CICS or by another product on the user’s system.

If X'offset' contains the value X'FFFF', module modname was in control at the time of the abend, but the program status word (PSW) was not addressing this module.

End of change
Start of change
System action:

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

Either this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.

Or CICS will continue unless you have specified in the dump table that CICS should terminate. Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

Notify the system programmer.

Look up the MVS code aaa, if there is one, in the relevant MVS codes manual which is detailed in the book list in the front of this manual.

If the modname insert contains the value ????, CICS was unable to determine which module has abnormally terminated. In this case, examine the system dump to determine which area of code has caused the program check.

The user should examine other messages to determine what the module which issued this message was doing at the time the abend occurred. From these messages they can deduce which product has produced the abend code bbbb. If bbbb is identified as a CICS code, it may be either alphameric or numeric.

If the user abend code is from another product (for example, IMS), refer to the appropriate messages and codes manual to determine the cause of the abend.

The entries in the appropriate manuals will give the user guidance regarding the nature of the error, and may also give some guidance concerning the appropriate user response.

Note:
The program check may have occurred in a user program. If this is the case, the program check is usually followed by an ASRA or an ASRB transaction abend and a transaction dump.

If you want to suppress system dumps that precede ASRA and ASRB abends, you must specify this on an entry in the dump table, using either CEMT or an EXEC CICS command. Further guidance on suppressing system dumps can be found in the CICS® System Definition Guide.

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

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHADxxEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeaaa/bbbb,End of changeStart of changeX'End of changeStart of changeoffset', End of changeStart of changemodnameEnd of change

Start of changeDFHAD0201End of change
Start of changeSpecified DJAR could not be found.End of change
Start of change
Explanation:

A CICS DJAR resource with the specified name could not be found.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter the name of an INSERVICE DJAR installed in the local CICS region.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0202End of change
Start of changeSpecified DJAR is in the DISCARDING state and cannot be used.End of change
Start of change
Explanation:

The specified DJAR resource is in the DISCARDING state and cannot be used.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter the name of an INSERVICE DJAR installed in the local CICS region.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0203End of change
Start of changeSpecified DJAR is in the INITING state. Please wait and retry.End of change
Start of change
Explanation:

The specified DJAR resource is in the INITING state and cannot be used.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter the name of an INSERVICE DJAR installed in the local CICS region, or retry your request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0204End of change
Start of changeSpecified DJAR is in the PENDINIT state. Please wait and retry.End of change
Start of change
Explanation:

The specified DJAR resource is in the PENDINIT state and cannot be used.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter the name of an INSERVICE DJAR installed in the local CICS region, or retry your request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0205End of change
Start of changeSpecified DJAR is in the PENDRESOLVE state. Please wait and retry.End of change
Start of change
Explanation:

The specified DJAR resource is in the PENDRESOLVE state and cannot be used.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter the name of an INSERVICE DJAR installed in the local CICS region, or retry your request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0206End of change
Start of changeSpecified DJAR is in the RESOLVING state. Please wait and retry.End of change
Start of change
Explanation:

The specified DJAR resource is in the RESOLVING state and cannot be used.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter the name of an INSERVICE DJAR installed in the local CICS region, or retry your request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0207End of change
Start of changeSpecified DJAR is in the UNRESOLVED state and cannot be used.End of change
Start of change
Explanation:

The specified DJAR resource is in the UNRESOLVED state and cannot be used.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter the name of an INSERVICE DJAR installed in the local CICS region.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0208End of change
Start of changeSpecified DJAR is in the UNUSABLE state and cannot be used.End of change
Start of change
Explanation:

The specified DJAR resource is in the UNUSABLE state and cannot be used.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter the name of an INSERVICE DJAR installed in the local CICS region.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0209End of change
Start of changeFatal error occurred whilst reading shelf copy of specified DJAR.End of change
Start of change
Explanation:

An unknown error occurred when DFHADJR attempted to read the shelf copy of the JAR file for the specified DJAR resource. As a result of this error the specified DJAR resource cannot be used by CREA/CREC.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter the name of an INSERVICE DJAR installed in the local CICS region, or retry your request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0210End of change
Start of changeSpecified DJAR could not be found on the shelf.End of change
Start of change
Explanation:

DFHADJR could not find the shelf copy of the JAR file for the specified DJAR resource. As a result of this error the specified DJAR resource cannot be used by CREA/CREC.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter the name of an INSERVICE DJAR installed in the local CICS region, or retry your request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0211End of change
Start of changeShelf file for specified DJAR was not a valid JAR file.End of change
Start of change
Explanation:

DFHADJR could not read the shelf copy of the JAR file for the specified DJAR resource, since it is not a valid JAR file. As a result of this error the specified DJAR resource cannot be used by CREA/CREC.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Check that the JAR file for the specified DJAR is a valid JAR file and that it contains a valid deployment descriptor. Alternatively enter the name of an INSERVICE DJAR installed in the local CICS region.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0212End of change
Start of changeNo JNDI name was supplied for bean lookup.End of change
Start of change
Explanation:

DFHADJR could not find the name of JNDI server to use for performing bean lookups. As a result of this error the specified DJAR resource cannot be used by CREA/CREC.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Check that a JNDI naming provider is supplied in the JVM system properties file. Retry your request or enter another DJAR name.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0213End of change
Start of changeTSQueue full error when retrieving information from specifed DJAR.End of change
Start of change
Explanation:

DFHADJR could not return information about the contents of the JAR file for the specified DJAR resource since the TS queue used to pass the information became full. As a result of this error the specified DJAR resource cannot be used by CREA/CREC.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Retry your request when CICS has more available storage. You could also reduce the number of methods defined in the deployment descriptor, or split the beans within the JAR file into two or more JAR files.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0214End of change
Start of changeThe specified DJAR contains no session beans.End of change
Start of change
Explanation:

DFHADJR could not find any session beans in the deployment descriptor of the JAR file related to the specified DJAR resource. As a result of this error the DJAR resource cannot be used by CREA/CREC.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Modify the deployment descriptor for the specified DJAR so that it contains references to one or more session beans and reinstall it into CICS.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0215End of change
Start of changeThe specified DJAR contains session beans with invalid lengths.End of change
Start of change
Explanation:

DFHADJR found one or more session beans listed in the deployment descriptor of the JAR file related to the specified DJAR resource that had names exceeding the 240 character limit. As a result of this error the DJAR resource cannot be used by CREA/CREC.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Modify the names of the session beans listed in the deployment descriptor so that no name exceeds the 240 character limit and reinstall the JAR file into CICS.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0216End of change
Start of changeAn error occurred with the Java classloader when reading the DJAR.End of change
Start of change
Explanation:

An error occurred when DFHADJR attempted to generate the IDL names for methods listed in the JAR file related to the specified DJAR resource. An attempt to use the Java classloader failed as classes that were needed could not be found on the classpath. As a result the DJAR resource cannot be used by CREA/CREC.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Ensure that all classes required by the beans in the JAR file related to the specified DJAR resource are available on the classpath.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0231End of change
Start of changePress Enter to confirm the change of DJAR or another key to revert.End of change
Start of change
Explanation:

The name of the DJAR on the transaction ID association screen has been changed, indicating that the user wishes to work with a different DJAR resource.

End of change
Start of change
System action:

The transaction waits for the user to press the Enter key to confirm that they wish to work with a different DJAR.

End of change
Start of change
User response:

Press Enter to work with a different DJAR, or any other key to continue working with the current DJAR. If the DJAR name is changed again whilst this message is displayed, then the DJAR name will revert back to the original DJAR name.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0232End of change
Start of changeError generating REQUESTMODELs - IDL errors for indicated methods.End of change
Start of change
Explanation:

One or more IDL strings generated for the operation field of a REQUESTMODEL are longer than the 255 character maximum. The methods with the IDL mangled names that are causing the problems are highlighted with an asterisk ('*') character.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Alter the transaction IDs assigned to the problematic methods such that those methods do not require their own REQUESTMODELs, but can instead be handled by a more generic REQUESTMODEL. An example of a more generic REQUESTMODEL is the REQUESTMODEL that is created for all methods on a given bean, and would therefore have '*' in the operation field.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0261End of change
Start of changeRequestModel rmName was successfully created.End of change
Start of change
Explanation:

The REQUESTMODEL was successfully created, being installed into CICS and/or written to the CSD as specified.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0262End of change
Start of changeREQUESTMODEL could not be created.End of change
Start of change
Explanation:

The REQUESTMODEL could not be created for some unknown reason.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Skip the REQUESTMODEL or alter the name value and try again.

If the problem persists check the trace data sets for more information. You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0263End of change
Start of changeNo action was selected. Please select an action.End of change
Start of change
Explanation:

The REQUESTMODEL can be installed into CICS and/or defined to the CSD, but no action was selected.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Adjust the 'Define to CSD' and/or 'Install into CICS' fields by overtyping the 'N' with a 'Y'. Alternatively skip creating the REQUESTMODEL.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0264End of change
Start of changeREQUESTMODEL could not be written to the CSD.End of change
Start of change
Explanation:

The specified REQUESTMODEL could not be written to the CSD for some unknown reason.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Ensure that the CSD is available for write access and that there are no locks held on the group that you are attempting to write to. You can then either skip the REQUESTMODEL, or alter the name and/or group value and try again.

If the problem persists check the trace data sets for more information. You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0265End of change
Start of changeREQUESTMODEL could not be installed.End of change
Start of change
Explanation:

The specified REQUESTMODEL could not be installed into CICS for some unknown reason. If you have selected to define the REQUESTMODEL to the CSD, then this operation will not have been performed.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Skip the REQUESTMODEL or alter the name value and try again.

If the problem persists check the trace data sets for more information. You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0266End of change
Start of changePlease specify a valid CSD group name.End of change
Start of change
Explanation:

The user attempted to write the REQUESTMODEL to the CSD, but did not provide a valid name for the group the REQUESTMODEL should be written into.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter a valid name for the CSD group into which this REQUESTMODEL is to be written, or deselect the option for writing it to the CSD.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0267End of change
Start of changeA duplicate REQUESTMODEL is already installed.End of change
Start of change
Explanation:

A duplicate copy of the specified REQUESTMODEL has already been installed into CICS. Since the option for replacing duplicate REQUESTMODELs ('Replace Dups') was not selected, this REQUESTMODEL has not been installed. If you have selected to define the REQUESTMODEL to the CSD, then this operation will not have been performed.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Either select the option for replacing duplicate REQUESTMODELs, or press PF9 (as prompted) to replace the duplicate for this REQUESTMODEL only. You can alternatively choose to skip the REQUESTMODEL or rename it and retry your request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0268End of change
Start of changeA duplicate REQUESTMODEL already exists in the CSD.End of change
Start of change
Explanation:

A duplicate copy of the specified REQUESTMODEL has already been written to the CSD. Since the option for replacing duplicate REQUESTMODELs ('Replace Dups') was not selected, this REQUESTMODEL has not been written to the CSD. If you have selected to install the REQUESTMODEL into CICS, then this operation will be backed out.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Either select the option for replacing duplicate REQUESTMODELs, or press PF9 (as prompted) to replace the duplicate for this REQUESTMODEL only. You can alternatively choose to skip the REQUESTMODEL or alter the name and/or group and retry your request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0269End of change
Start of changeAn error occurred whilst discarding a duplicate REQUESTMODEL.End of change
Start of change
Explanation:

Whilst attempting to discard a REQUESTMODEL from CICS (as the result of a request to replace a REQUESTMODEL), an unknown error occurred. The REQUESTMODEL has not been installed into CICS. If you have selected to define the REQUESTMODEL to the CSD, then this operation will not have been performed.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Skip the REQUESTMODEL or alter the name and/or group value and try again.

If the problem persists check the trace data sets for more information. You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0270End of change
Start of changeAn error occurred whilst replacing a duplicate REQUESTMODEL.End of change
Start of change
Explanation:

Whilst attempting to replace an existing REQUESTMODEL an unknown error occurred. The REQUESTMODEL has not been installed into CICS.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Skip the REQUESTMODEL or alter the name and/or group value and try again.

If the problem persists check the trace data sets for more information. You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0271End of change
Start of changeError trying to delete a duplicate REQUESTMODEL from the CSD.End of change
Start of change
Explanation:

Whilst attempting to delete a REQUESTMODEL from the CSD (as the result of a request to replace a duplicate REQUESTMODEL), an unknown error occurred. The new REQUESTMODEL has not been written to the CSD. If you have selected to install the REQUESTMODEL into CICS, then this operation will be backed out.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Ensure that the CSD is available for write access and that there are no locks held on the group that you are attempting to delete from. You can then either skip the REQUESTMODEL, or alter the name and/or group value and try again.

If the problem persists check the trace data sets for more information. You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0272End of change
Start of changeNo name could be generated for this REQUESTMODEL. Range exceeded.End of change
Start of change
Explanation:

No name could be generated for this REQUESTMODEL since the name for the REQUESTMODEL created previously was the maximum size allowed for a REQUESTMODEL name and had reached the upper numerical limit.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter a new REQUESTMODEL name that has not already been used. You may attempt to create a REQUESTMODEL with the name shown, but if a REQUESTMODEL with the same name already exists this will not work. Alternatively you may choose to skip this REQUESTMODEL.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

Start of changeDFHAD0273End of change
Start of changePlease specify a valid name for this REQUESTMODEL.End of change
Start of change
Explanation:

No valid name was given for the REQUESTMODEL. Without a valid name the REQUESTMODEL cannot be created.

End of change
Start of change
System action:

The transaction continues.

End of change
Start of change
User response:

Enter a valid REQUESTMODEL name that has not already been used. Alternatively you may choose to skip this REQUESTMODEL.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHADDRMEnd of change

End of change [[ Contents Previous Page | Next Page Index ]]