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 which is detailed in the book list in the front of this 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
DFHUSAD, DFHUSDM, DFHUSFL, DFHUSIS, DFHUSST, DFHUSXM
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 it 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
DFHUSAD, DFHUSDM, DFHUSFL, DFHUSIS, DFHUSST, DFHUSXM
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 SIT (this is the ICVR which is measured in milliseconds). This means that module modname in the message 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. However 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. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHUSAD, DFHUSDM, DFHUSFL, DFHUSIS, DFHUSST, DFHUSXM
XMEOUT Parameters: applid, X'offset', modname
An MVS 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.
The code mvscode is the MVS GETMAIN return code.
An exception entry is made in the trace table (code X'code'). 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.
If CICS has been terminated by another module, look out for the relevant termination messages (from, for example, the domain manager), and look up the User Response for these messages.
If CICS is still running, the problem may be a temporary one which rights itself if more storage becomes available. If you can manage without module modname, you may decide to continue 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 all CICS modules, you should bring CICS down in a controlled shutdown.
You can get diagnostic information about the MVS return code by consulting the relevant MVS codes manual.
Try decreasing the size limits of the DSAs or EDSAs. Or, try increasing the size of the whole region, if it is not already at maximum size. See the CICS System Definition Guide or the CICS Performance Guide for more information on CICS storage.
Console
DFHUSDM, DFHUSAD
XMEOUT Parameters: applid, X'code',modname, mvscode
The default userid specified in the system initialization parameter DFLTUSER cannot be used by this CICS job.
The region userid for this CICS job is not authorized to use the userid specified in the DFLTUSER system initialization parameter.
Consult the CICS RACF® Security Guide for
more information.
CICS initialization terminates.
Ensure the default userid and the userid for the CICS region are correct.
If the two userids are correct, obtain the necessary authorization for the default userid to be used by the CICS region userid. This may require the assistance of a security administrator.
Previous messages may have been produced by the job giving additional information.
Console
DFHUSDM
XMEOUT Parameters:
applid,
userid1,
userid2
An attempt was made to establish security for the CICS region userid but this was rejected by the external security manager (ESM).
CICS initialization terminates.
The response and reason codes (safresp and safreas) returned by the system authorization facility (SAF), and the response and reason codes (esmresp and esmreas) returned by the external security manager (ESM) are those issued by the RACROUTE REQUEST=VERIFY or RACROUTE REQUEST=EXTRACT macros. For the meaning of the response and reason codes in the message see z/OS MVS Programming: Authorized Assembler Services Guide (SA22-7608) and z/OS Security Server Racroute Macro Reference (SA22-7692).
There may be further messages produced by CICS or the external security manager (ESM) which provide more information.
If the ESM and SAF codes are not sufficient to explain the problem, then the USAD response code can be analyzed by IBM support. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHUSDM
XMEOUT Parameters: applid, userid,X'safresp', X'safreas', X'esmresp',X'esmreas', reason
The MVS ENQ issued as part of SNSCOPE checking has failed. The return code indicates that the CICS job has reached the limit of concurrent resource requests.
A system dump is suppressed, unless you have specifically enabled dumps for this dumpcode in the dump table. The request to signon is rejected.
See the OS/390 MVS Programming Authorized Assembler Services Guide for guidance on increasing the MVS ENQ limit. The MVS ENQ is issued by CICS in an unauthorized state.
Console
DFHUSAD, DFHUSFL
XMEOUT Parameter:
applid
An attempt was made to establish security for userid userid in group groupid with access to resources allowed for the terminal or console portname and the application applid. The attempt was rejected by the external security manager (ESM).
The transaction tranid cannot be initialized.
Security has not been established for the userid. The attempt to initialize the transaction has failed.
The response and reason codes (safresp and safreas) returned by the system authorization facility (SAF), and the response and reason codes (esmresp and esmreas) returned by the external security manager (ESM) are those issued by the RACROUTE REQUEST=VERIFY or RACROUTE REQUEST=EXTRACT macros. These return codes are described in the OS/390 MVS Programming: Authorized Assembler Services Guide and in External Security Interface (RACROUTE) Macro Reference for MVS and VM (SC28-1366). See these manuals for an explanation of the codes.
There may be further messages produced by CICS or the external security manager (ESM) which provide more information.
Console
DFHUSXM
XMEOUT Parameters: applid, userid,groupid, {99=no terminal, , 1=netname , 2=console }, portname, applid, tranid, X'safresp', X'safreas', X'esmresp', X'esmreas'
User userid in group groupid (at terminal portname if appropriate) has been removed from this CICS system because the userid has been unused for a period longer than that specified in the USRDELAY system initialization parameter.
Processing continues.
See the CICS System Definition Guide for more information about USRDELAY.
CSCS
DFHUSDM
XMEOUT Parameters: date, time,applid, userid, groupid, {1= at netname , 2= at console }, portname