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).
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.
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.
Console
DFHDHDH, DFHDHDM, DFHDHSL
XMEOUT Parameters:
applid,
aaa/bbbb,
X'
offset',
modname
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.
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.
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.
Console
DFHDHDH, DFHDHDM, DFHDHSL
XMEOUT Parameters:
applid,
X'
code',
modname
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.
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.
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.
Console
DFHDMTM
XMEOUT Parameters:
applid,
X'offset',
modname
This is an informational message indicating that document domain initialization has started.
System initialization continues.
None. The message can be suppressed with the system initialization parameter MSGLVL=0.
Console
DFHDHDM
XMEOUT Parameter:
applid
This is an informational message indicating that document domain initialization has completed successfully.
System initialization continues.
None. The message can be suppressed with the system initialization parameter MSGLVL=0.
Console
DFHDHDM
XMEOUT Parameter:
applid
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:
The document template is assigned a template name of templatename.
The definition is written to the CICS global catalog and will be restored on a CICS warm start.
Application programs can now use the template using the name templatename.
CSDH
DFHDHTM
XMEOUT Parameters:
date,
time,
applid,
doctemplate,
{1=PDS-MEMBER,
2=FILE,
3=PROGRAM,
4=TSQUEUE,
5=TDQUEUE,
6=EXITPGM,
7=HFSFILE},
resourcename,
templatename
The document template definition doctemplate has been successfully deleted from the Document Handler domain.
The definition is removed from the CICS global catalog and will not be restored on a CICS warm start.
Application programs can no longer use the template using the name templatename.
CSDH
DFHDHTM
XMEOUT Parameters:
date,
time,
applid,
doctemplate
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.
The document template doctemplate is not installed.
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.
Console
DFHDHRP
XMEOUT Parameters:
date,
time,
applid,
ddname,
doctemplate
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.
The document template doctemplate is not installed.
Add the specified member member to the data set named dsname. Then reinstall the document template.
Console
DFHDHRP
XMEOUT Parameters:
date,
time,
applid,
member,
dsname,
doctemplate