Start of change

DFHDPxxxx messages

Start of changeDFHDP0001End 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 the CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.

The code aaa/bbbb is a 3-digit hexadecimal MVS code (if applicable), followed by a 4-digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; 1310 refers to message DFHDP1310).

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.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS could be terminated by the caller ( for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

Look up the MVS code, if there is one, in the relevant MVS codes manual.

Next, look up the CICS alphanumeric code. This tells you, for example, whether the error was a program check, an abend, or a runaway, and may give you some guidance concerning user response.

If module modname is not crucial to the running of your CICS system, you may decide to continue and bring CICS down at a convenient time to resolve the problem.

If you cannot continue without the full use of module modname you should bring CICS down in a controlled shutdown.

You 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 changeDFHDP*End 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 changeDFHDP0002End of change
Start of changeapplid A severe error (code X'code') has occurred in module modname.End of change
Start of change
Explanation:

An error has been detected in module modname. The code X'code' is the exception trace point id which uniquely identifies what the error is and where the error was detected.

End of change
Start of change
System action:

An exception entry (code X'code' in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

This indicates a possible error in CICS code. The severity of its impact depends on the importance of the function being executed at the time of the error.

CICS may not have been terminated. If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If the message recurs or if you cannot run without the full use of module modname, you should bring CICS down in a controlled shutdown.

You 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 changeDFHDPFM, DFHDPLM, DFHDPUM.End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changecode',End of changeStart of changemodnameEnd of change

Start of changeDFHDP0100End of change
Start of changeapplid An unexpected exception response with reason code X'code' has been returned by CICS file control to module modname. The debugging profiles file, filename, is not usable.End of change
Start of change
Explanation:

A call to CICS file control from a DP domain module has received an unexpected exception response from DFHFCFR. The reason code given in the message is the reason from the FCFR parameter list on return from file control.

End of change
Start of change
System action:

The file given in the message is not usable.

The application debugging profiles manager will fail until the problem has been corrected. It the CICS supplied transaction, CADP, is being used to define debugging profiles it will fail with an ADPA abend.

The meaning of the reason code in the message is given below:

End of change
Start of change
User response:

Investigate and correct the error based on the reason given and retry.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHDPFM, DFHDPLM, DFHDPUM.End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changecode',End of changeStart of changemodname, End of changeStart of changefilenameEnd of change

Start of changeDFHDP0200End of change
Start of changeapplid Debug Tool is back level. LE Debugging profiles may be defined but not used on this system.End of change
Start of change
Explanation:

CICS is running with a level of Debug Tool which is older than Version 3.1.

End of change
Start of change
System action:

The CADP transaction and the web interface can be used to define debugging profiles and they can be activated. However, Debug Tool will not be able to use these profiles.

End of change
Start of change
User response:

If you do not intend to perform LE debugging on this system or you only want to use CADP and the web interface to define profiles for use on another CICS region which does have Debug Tool at least at the version 3.1 level, then no action is required. If the intention is to use LE debugging profiles on this CICS, then Debug Tool version 3.1 or later must be installed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHDPLUEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHDP0300End of change
Start of changeapplid num debugging profile(s) have been inactivated.End of change
Start of change
Explanation:

The transaction CIDP or the program DFHDPIN has been run to inactivate all currently active debugging profiles. num debugging profiles have been inactivated.

End of change
Start of change
System action:

None.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHDPIN.End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changenumEnd of change

Start of changeDFHDP0301End of change
Start of changeapplid The file DFHDPFMB is not available. No debugging profiles have been inactivated.End of change
Start of change
Explanation:

The transaction CIDP or the program DFHDPIN has been run to inactivate all currently active debugging profiles. It was not possible to inactivate the profiles as the CADP file DFHDPFMB was not available.

End of change
Start of change
System action:

Inactivation is canceled.

End of change
Start of change
User response:

Make the CADP file DFHDPFMB available and reissue the CIDP command.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHDPIN.End of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

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