DFHDMxxxx messages

DFHDM0001
applid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.
Explanation:

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

Alternatively,

The code aaa/bbbb is a three digit hexadecimal MVS code (if applicable), followed by a four 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 DFHTS1310).

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 CICS will continue unless you have specified in the dump table that CICS should terminate. This action will be taken by DFHDMIQ.

Or this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate. This action is taken by DFHDMDM, DFHDMDS and DFHDMWQ.

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

User response:

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

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

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

Destination:

Console

Modules:

Start of changeDFHDMDM, DFHDMEN, DFHDMENF, DFHDMIQ, DFHDMDS, DFHDMWQEnd of change

Start of changeXMEOUT Parameters: applid, aaa/bbbb, X'offset', modnameEnd of change

DFHDM0002
applid A severe error (code X'code') has occurred in module modname.
Explanation:

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

For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.

System action:

An exception entry (code 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.

Either CICS will continue unless you have specified in the dump table that CICS should terminate. This action will be taken by DFHDMIQ.

Or, this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate. This action is taken by DFHDMDM, DFHDMDS and DFHDMWQ.

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

User response:

This indicates a possible error in the CICS code. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

Start of changeDFHDMDM, DFHDMEN, DFHDMENF, DFHDMIQ, DFHDMDS, DFHDMWQEnd of change

Start of changeXMEOUT Parameters: applid, X'code',modnameEnd of change

DFHDM0003
applid Insufficient storage to satisfy GETMAIN (code X'code') in module modname.
Explanation:

A CICS GETMAIN was issued by module modname, but there was insufficient storage available to satisfy the request.

The code X'code' is the exception trace point id which uniquely identifies the place where the error was detected.

This error has occurred above the 16Mb line.

System action:

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

Either CICS continues unless you have specified in the dump table that CICS should terminate. This action is taken by DFHDMIQ.

Or this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate. This action is taken by DFHDMDM and DFHDMWQ.

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

User response:

Try increasing the size limits of the DSAs or EDSAs. See the CICS System Definition Guide or the CICS Performance Guide for further information on CICS storage.

Destination:

Console

Modules:

DFHDMDM, DFHDMIQ, DFHDMWQ

XMEOUT Parameters: applid, X'code',modname

DFHDM0004
applid A possible loop has been detected at offset X'offset' in module modname.
Explanation:

A CICS function is taking more time to process than CICS expects. A possible loop has been detected in module modname at X'offset'. This is the offset of the instruction which was executing at the time the error was detected.

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 CICS continues unless you have specified in the dump table that CICS should terminate. This action is taken by DFHDMIQ.

Or this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate. This action is taken by DFHDMDM, DFHDMDS and DFHDMWQ.

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

User response:

If CICS has not been terminated, it is necessary to decide whether the problem is serious enough to bring CICS down.

Since some CICS functions can use a lot of CPU time, this message may have been caused by a long-running function. So there may not be an error here. Usually, CICS purges a CICS function which exceeds the runaway task time interval which you have specified in the SIT (this is the ICVR which is measured in milliseconds). This means that the module modname is terminated and CICS continues.

But if you have declared ICVR=0 in the SIT and you consider that module modname has gone into a loop, you have to terminate CICS in order to terminate the runaway function.

If CICS has terminated module modname and you consider that it was not a runaway, you should increase the ICVR time interval in the SIT. You have to bring CICS down at a suitable time to do this permanently. But you can change the ICVR time interval temporarily online, using the CEMT transaction.

If raising the ICVR time does not solve the problem, you will need further assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

Start of changeDFHDMDM, DFHDMEN, DFHDMENF, DFHDMIQ, DFHDMDS, DFHDMWQEnd of change

Start of changeXMEOUT Parameters: applid, X'offset', modnameEnd of change

DFHDM0005
applid A hardware error has occurred (module modname, code X'code'). The Time-of-Day clock is invalid.
Explanation:

A hardware error has occurred during the running of module modname. The MVS Store Clock facility is the timing mechanism for the operating system.

The code code is the exception trace point id which uniquely identifies the place where the error was detected.

System action:

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

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

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

User response:

This is in all probability a hardware error and you should in the first instance investigate the MVS Store Clock and find out whether it is working properly. If this is the cause, you should take the appropriate action to have it repaired or replaced.

In the unlikely event that this is not a hardware problem, you need further assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHDMDM, DFHDMWQ, DFHDMDS

XMEOUT Parameters: applid, modname,X'code'

DFHDM0101I
applid CICS is initializing.
Explanation:

This message is for information only.

CICS initialization has started. The domain (DM) manager is about to attach an initialization task for each domain defined in the local CICS catalog, DFHLCD.

System action:

Processing continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHDMDM

XMEOUT Parameter: applid

DFHDM0102I
applid CICS is quiescing.
Explanation:

This message is for information only.

The controlled shutdown of CICS has started. The domain (DM) manager is about to attach a quiesce task for each CICS component.

System action:

Processing continues.

User response:

None. You can suppress this message with the SIT parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHDMDM

XMEOUT Parameter: applid

DFHDM0103
applid Unsuccessful quiesce of domain domain. CICS will terminate.
Explanation:

A domain has failed to quiesce.

System action:

CICS terminates. An exception trace and a dump are issued by the domain in error.

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

User response:

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

Destination:

Console

Modules:

DFHDMDS

XMEOUT Parameters: applid, domain

DFHDM0104
applid Unsuccessful load of program domain. CICS will terminate.
Explanation:

The domain (DM) manager has called the loader to load a program for an initialization task but the load has failed. The module is missing from the DFHRPL concatenation, possibly because the SDFHLOAD is missing. Alternatively, if the module name given in the message is not a legitimate CICS module, the CICS catalog could be corrupted.

System action:

Start of changeCICS terminates. A system dump with dump code DM0006 is taken unless you have suppressed dumps in the dump table.End of change

An exception trace is issued by the domain manager. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

Console

Modules:

DFHDMDM

XMEOUT Parameters: applid, domain

DFHDM0105
applid Unsuccessful initialization of domain domain. CICS will terminate.
Explanation:

A domain has failed to initialize.

System action:

CICS terminates.

Start of changeDiagnostics are issued by the domain in error. Message DFHME0116 is normally produced containing the symptom string for this problem.End of change

User response:

Start of changeReview the diagnostics and take remedial action for any installation-related problems.End of change See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHDMDS

XMEOUT Parameters: applid, domain

DFHDM0106
applid The Domain Manager records on the CICS Catalog may have been corrupted.
Explanation:

A problem was detected when calling the CICS catalog to browse the domain (DM) manager records. For example, the domain manager records may not be present.

This message may follow message DFHDM0002.

System action:

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

A system dump is taken, unless you have specifically suppressed dumps in the dump table.

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

User response:

Try reinitializing the local CICS catalog, DFHLCD, using DFHCCUTL, and perform an initial start of CICS.

If this does not solve the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHDMDM

XMEOUT Parameter: applid

[[ Contents Previous Page | Next Page Index ]]