DFHDHxxxx messages

Start of changeDFHDH0001End 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 DFHTS1310).

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 to run and bring CICS down at a convenient time to resolve the problem.
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 changeDFHDHDH, DFHDHDM, DFHDHSLEnd 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 changeDFHDH0002End 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 changeDFHDHDH, DFHDHDM, DFHDHSLEnd 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 changeDFHDH0004End of change
Start of changeapplid A possible loop has been detected at offset X'offset' in module modname.End of change
Start of change
Explanation:

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

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 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 processor 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 ICVR system initialization parameter, which is measured in milliseconds. This means that module modname in the message is terminated and CICS continues.

But if you have specified ICVR=0 you consider that module modname is looping, you must 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 system initialization parameter. You can change the RUNAWAY time interval temporarily using the CEMT transaction.

If raising the ICVR time does not solve the problem, you will need further assistance from IBM. 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 changeDFHDMTMEnd of change

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

Start of changeDFHDH0100IEnd of change
Start of changeapplid Document domain initialization has started.End of change
Start of change
Explanation:

This is an informational message indicating that document domain initialization has started.

End of change
Start of change
System action:

System initialization continues.

End of change
Start of change
User response:

None. The message can be suppressed with the system initialization parameter MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHDHDMEnd of change

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

Start of changeDFHDH0101IEnd of change
Start of changeapplid Document domain initialization has ended.End of change
Start of change
Explanation:

This is an informational message indicating that document domain initialization has completed successfully.

End of change
Start of change
System action:

System initialization continues.

End of change
Start of change
User response:

None. The message can be suppressed with the system initialization parameter MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHDHDMEnd of change

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

Start of changeDFHDH0105End of change
Start of changedate time applid Document template definition doctemplate has been added as {PDS-MEMBER |FILE | PROGRAM | TSQUEUE | TDQUEUE | EXITPGM | HFSFILE}(resourcename) with template name templatename.End of change
Start of change
Explanation:

The document template definition doctemplate has been successfully added to the Document Handler domain. The template definition maps on to one of the following resources named resourcename:

PDS-MEMBER
A member of a partitioned dataset
FILE
A CICS file
PROGRAM
A CICS program
TSQUEUE
A CICS Temporary Storage queue
TDQUEUE
A CICS Transient Data queue
EXITPGM
A User-replaceable program that reads in a template of its own specification
HFSFILE
A file in the z/OS UNIX System Services Hierarchical File Sytem (HFS).

The document template is assigned a template name of templatename.

End of change
Start of change
System action:

The definition is written to the CICS global catalog and will be restored on a CICS warm start.

End of change
Start of change
User response:

Application programs can now use the template using the name templatename.

End of change
Start of change
Destination:

CSDH

End of change
Modules:

Start of changeDFHDHTMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedoctemplate, End of changeStart of change{1=PDS-MEMBER, End of changeStart of change2=FILE, End of changeStart of change3=PROGRAM, End of changeStart of change4=TSQUEUE, End of changeStart of change5=TDQUEUE, End of changeStart of change6=EXITPGM, End of change Start of change7=HFSFILE}, End of changeStart of changeresourcename, End of changeStart of changetemplatenameEnd of change

Start of changeDFHDH0106End of change
Start of changedate time applid Document template definition doctemplate has been deleted.End of change
Start of change
Explanation:

The document template definition doctemplate has been successfully deleted from the Document Handler domain.

End of change
Start of change
System action:

The definition is removed from the CICS global catalog and will not be restored on a CICS warm start.

End of change
Start of change
User response:

Application programs can no longer use the template using the name templatename.

End of change
Start of change
Destination:

CSDH

End of change
Modules:

Start of changeDFHDHTMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedoctemplateEnd of change

Start of changeDFHDH0107IEnd of change
Start of changedate time applid DD statement ddname not found. DOCTEMPLATE doctemplate is not installed.End of change
Start of change
Explanation:

A document template definition specified a DDNAME value ddname, but a DD statement with that name was not present in the CICS JCL. The corresponding template data set cannot be opened.

End of change
Start of change
System action:

The document template doctemplate is not installed.

End of change
Start of change
User response:

Either restart CICS with a suitable template library allocated to DD name ddname, or use the ADYN transaction to allocate the library dynamically. The ADYN transaction is described in the CICS Customization Guide.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHDHRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeddname, End of changeStart of changedoctemplateEnd of change

Start of changeDFHDH0108IEnd of change
Start of changedate time applid Member member not found in dsname. DOCTEMPLATE doctemplate is not installed.End of change
Start of change
Explanation:

A document template definition specified a MEMBER name of member, but the data set dsname allocated to the specified DDNAME does not contain that member.

End of change
Start of change
System action:

The document template doctemplate is not installed.

End of change
Start of change
User response:

Add the specified member member to the data set named dsname. Then reinstall the document template.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHDHRPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changemember, End of changeStart of changedsname, End of changeStart of changedoctemplateEnd of change

[[ Contents Previous Page | Next Page Index ]]