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
DFHSMAD, DFHSMAR, DFHSMCK, DFHSMDM, DFHSMGF, DFHSMMCI, DFHSMMC2, DFHSMMF, DFHSMMG, DFHSMPQ, DFHSMPP, DFHSMSR, DFHSMST, DFHSMSU, DFHSMSY
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.
See the CICS Trace Entries for
a description of the exception trace point ID,
X'code' and the data it contains.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHSMAD, DFHSMAR, DFHSMCK, DFHSMGF, DFHSMMC2, DFHSMMF, DFHSMMG, DFHSMPQ, DFHSMPP DFHSMSCP, DFHSMSR, DFHSMST, DFHSMSU, DFHSMSY
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. 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 need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHSMMCI, DFHSMST
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 suggested 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.
See the CICS Trace Entries for
a description of the exception trace point ID,
X'code' and the data it contains.
You can get diagnostic information about the MVS return code by consulting the relevant MVS codes manual.
Try decreasing the limits of the CICS dynamic storage areas (DSAs), or increasing the MVS region size. You can vary the CICS DSAs dynamically using the DSALIM and EDSALIM parameters on the CEMT master terminal command. To increase the MVS region size you must bring CICS down and change the MVS JCL REGION parameter.
Console
DFHSMDM
XMEOUT Parameters: applid, X'code',modname, mvscode
A storage violation has been detected by module modname. The code X'code' is the exception trace point ID which uniquely identifies the type of storage violation.
An exception entry (X'code' in the message)
is made in the trace table.
Use the exception trace point ID,
X'code',
to investigate the cause of the storage violation.
A description of the exception trace point ID, and the data
it contains, is in the
CICS Trace Entries.
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 you have enabled storage recovery (by specifying the system initialization parameter STGRCVY=YES), CICS attempts to repair the storage violation. Otherwise, the storage is left unchanged.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Use the exception trace point ID, X'code',
to investigate the cause of the storage violation.
See the CICS Trace Entries for
a description of the exception trace point ID
and the data it contains.
Console
DFHSMAR, DFHSMCK, DFHSMGF, DFHSMMC2, DFHSMMF
XMEOUT Parameters: applid, X'code',modname
A storage violation has been detected by the storage violation trap, which may be enabled via the CHKSTSK or the CHKSTRM system initialization parameters or via the CSFE transaction. The code X'code' is the exception trace point ID which uniquely identifies the type of storage violation detected.
CICS disables the storage violation trap. An exception entry (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 you have enabled storage recovery (by specifying the system initialization parameter STGRCVY=YES), CICS attempts to repair the storage violation. Otherwise, the storage is left unchanged.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Use the exception trace point ID,
X'code', to investigate
the cause of the storage violation.
See the CICS Trace Entries for
a description of the exception trace point ID
and the data it contains.
Console
DFHSMCK
XMEOUT Parameters: applid, X'code'
This is an informatory message stating that storage protection has not been requested (STGPROT=NO) and is not in effect for this execution of CICS.
CICS continues.
None. You can suppress this message with the system initialization parameter, MSGLVL=0. Storage protection can be enabled by specifying the system initialization parameter STGPROT=YES.
Console
DFHSMDM
XMEOUT Parameter: applid
This is an informatory message stating that although storage protection was requested, it is not in effect for this execution of CICS because the necessary hardware and/or operating system support is not available.
CICS continues.
None.
Console
DFHSMDM
XMEOUT Parameter: applid
This is an informatory message stating that storage protection is requested (STGPROT=YES) and is in effect for this execution of CICS.
CICS continues.
None. You can suppress this message with the system initialization parameter, MSGLVL=0.
Console
DFHSMDM
XMEOUT Parameter: applid
This is an informatory message stating that read-only programs will not be loaded into read-only storage for this execution of CICS. This is because RENTPGM=NOPROTECT was specified as a system initialization parameter.
CICS continues.
None.
You should not specify RENTPGM=NOPROTECT unless you wish to deliberately overwrite programs (to set breakpoints while testing, for example).
Console
DFHSMDM
XMEOUT Parameter: applid
This message gives the limit dsalimit of the dynamic storage area (DSA) below 16MB.
CICS continues.
None. You can suppress this message with the message level system initialization parameter, MSGLVL=0.
Console
DFHSMDM
XMEOUT Parameters: applid, dsalimit
This message gives the limit edsalimit of the dynamic storage area (DSA) above 16MB.
CICS continues.
None. You can suppress this message with the message level system initialization parameter, MSGLVL=0.
Console
DFHSMDM
XMEOUT Parameters: applid, edsalimit
The combination of system initialization parameters STGPROT(NO) and TRANISO(YES) is invalid. During a warm or emergency start of CICS, the catalogued system initialization parameters are incompatible with a SIT override. Although transaction isolation was requested, it is not in effect for this execution of CICS because the necessary hardware and/or operating system support is not available, and/or storage protection is not active.
CICS continues.
None.
Console
DFHSMDM
XMEOUT Parameter: applid
Transaction isolation is requested (TRANISO=YES) and is in effect for this execution of CICS.
CICS continues.
None. You can suppress this message with the system initialization parameter, MSGLVL=0.
Console
DFHSMDM
XMEOUT Parameter: applid
Transaction isolation has not been requested (TRANISO=NO) and is not in effect for this execution of CICS.
CICS continues.
None. You can suppress this message with the system initialization parameter, MSGLVL=0. Transaction isolation can be enabled by specifying TRANISO=YES as a system initialization parameter.
Console
DFHSMDM
XMEOUT Parameter: applid
CICS has issued an MVS GETMAIN for the requested limit dsalimit of DSA storage below 16MB, but the GETMAIN request failed.
If the requested size is greater than the default, CICS reissues the MVS GETMAIN request using the default size for the DSALIM parameter.
If the requested size is not greater than the default, the storage manager makes an exception entry in the trace table. An error return code is sent to the domain manager DFHDMDM (the caller of the storage manager). The domain manager might then terminate CICS, in which case a message to this effect is issued.
Ensure that the DSALIM system initialization parameter is specified correctly.
Ensure that the REGION parameter for the CICS job is large enough.
See the OS/390 MVS JCL Reference for further information about specifying storage on the REGION parameter.
Console
DFHSMDM
XMEOUT Parameters: applid, dsalimit
CICS has issued an MVS GETMAIN for the requested limit dsalimit of DSA storage above 16MB, but the GETMAIN request failed.
If the requested size is greater than the default, CICS reissues the MVS GETMAIN request using the default size for the EDSALIM parameter.
If the requested size is not greater than the default, the storage manager makes an exception entry in the trace table. An error return code is sent to the domain manager DFHDMDM (the caller of the storage manager). The domain manager might then terminate CICS, in which case a message to this effect is issued.
Ensure that the EDSALIM parameter is specified correctly.
Ensure that the REGION parameter for the CICS job is large enough.
See the OS/390 MVS JCL Reference for more information about specifying storage on the REGION parameter.
Console
DFHSMDM
XMEOUT Parameters: applid, dsalimit
Following message DFHSM0127, CICS has reduced the MVS GETMAIN request to the default size for the DSALIM system initialization parameter but the GETMAIN request has still failed.
The storage manager makes an exception entry in the trace table.
An error return code is sent to the domain manager, DFHDMDM, (the caller of storage manager). The domain manager might then terminate CICS, in which case a message to this effect is issued.
See DFHSM0127 for further information.
Ensure that the REGION parameter for the CICS job is large enough.
See the OS/390 MVS JCL Reference for more information about specifying storage on the REGION parameter.
Console
DFHSMDM
XMEOUT Parameters: applid, dsalimit
Following message DFHSM0128, CICS has reduced the MVS GETMAIN request to the default size for the EDSALIM system initialization parameter but the GETMAIN request has still failed.
The storage manager makes an exception entry in the trace table.
An error return code is sent to the domain manager, DFHDMDM, (the caller of storage manager). The domain manager might then terminate CICS, in which case a message to this effect is issued.
See DFHSM0128 for further information.
Ensure that the REGION parameter for the CICS job is large enough.
See the OS/390 MVS JCL Reference for more information about specifying storage on the REGION parameter.
Console
DFHSMDM
XMEOUT Parameters: applid, dsalimit
This message is produced when there is a shortage of storage in any of the dynamic storage areas (DSAs) below 16MB. Either the largest free area in one of the DSAs is less than the size of the internally defined cushion for that DSA, or there is at least one transaction suspended due to insufficient contiguous free storage.
An exception entry is made in the trace table to record the event.
CICS continues to operate but takes steps to alleviate the situation by, for example, slowing down the rate at which new tasks are started and by releasing storage occupied by programs which are not currently in use.
No immediate action is required. However, if the problem persists you could increase the value of the DSALIMIT parameter, if possible, or reduce the storage requirements below 16MB of your CICS system. For more information about how to do this, see the CICS Performance Guide.
Console
DFHSMSY
XMEOUT Parameter: applid
The short on storage condition reported by message DFHSM0131 has ceased.
CICS continues.
None.
Console
DFHSMSY
XMEOUT Parameter: applid
There is a shortage of storage in one of the dynamic storage areas (DSAs) above 16MB. Either the largest free area in one of the DSAs is less than the size of the internally defined cushion for that DSA, or there is at least one transaction suspended due to insufficient contiguous free storage.
An exception entry is made in the trace table to record the event.
CICS continues to operate but takes steps to alleviate the situation by, for example, slowing down the rate at which new tasks are started and by releasing storage occupied by programs which are not currently in use.
No immediate action is required. However, if the problem persists you could, if possible, increase the value of the EDSALIMIT parameter, or reduce the storage requirements of your CICS system above 16MB. For guidance on how to do this, see the CICS Performance Guide.
Console
DFHSMSY
XMEOUT Parameter: applid
The short on storage condition reported by message DFHSM0133 has ceased.
CICS continues.
None.
Console
DFHSMSY
XMEOUT Parameter: applid
CICS has attempted to allocate the requested size of dsasize for the dynamic storage area dsaname but there is insufficient storage to satisfy the request.
An error return code is sent to the domain manager, DFHDMDM (the caller of storage manager). The domain manager might then terminate CICS, in which case a message to this effect is issued.
Either reduce the value specified in the DSASZE parameter, or increase the value specified in the DSALIM parameter.
Console
DFHSMDM
XMEOUT Parameters:
applid,
dsasize,
dsaname
This is an informatory message giving the size dsasize of the dynamic storage area (DSA) dsaname.
CICS continues.
None. You can suppress this message with the message level system initialization parameter, MSGLVL=0.
Console
DFHSMDM
XMEOUT Parameters:
applid,
dsaname,
dsasize
When MVS storage is requested by a JVM from Language Environment, CICS intercepts the request. This message is produced when the size of the largest contiguous unallocated block of storage above 16MB that is available for use by MVS has fallen below a system-defined threshold.
An exception entry is made in the trace table to record the event.
CICS continues to operate but takes steps to alleviate the situation by deleting any JVMs that are currently inactive. This will have the effect of freeing any MVS storage that the inactive JVMs are holding.
No immediate action is required. However, if the problem persists and if you are a user of Java transactions you could reduce the value of the MAXJVMTCBs parameter. This would reduce the number of JVMs which exist concurrently within CICS. For more information about how to do this, see the CICS Performance Guide.
Console
DFHSMVN
XMEOUT Parameter:
applid
The MVS storage shortage reported by message DFHSM0137 has ceased.
CICS continues.
None.
Console
DFHSMVN
XMEOUT Parameter:
applid
This message is produced when there is no unallocated block of storage large enough to satisfy an MVS request for storage. When MVS storage is requested by a JVM from Language Environment, CICS will intercept these requests. The message means that insufficient contiguous storage was available to satisfy the MVS storage request. Either CICS has been forced to attempt to satisfy the request by releasing storage from an MVS storage cushion that it keeps in reserve or there is at least one transaction suspended due to insufficient contiguous free storage.
An exception entry is made in the trace table to record the event.
CICS continues to operate but takes steps to alleviate the situation by deleting JVMs as the programs that own them complete and not starting new JVMs until the storage shortage is relieved.
No immediate action is required. However, if the problem persists and if you run Java transactions you could decrease the MAXJVMTCBS parameter. For more information about how to do this, see the CICS Performance Guide.
Console
DFHSMVN
XMEOUT Parameter:
applid
The MVS storage shortage reported by message DFHSM0139 has ceased.
CICS continues.
None.
Console
DFHSMVN
XMEOUT Parameter:
applid
This is the report from the local catalog storage manager domain
subpool record manipulation program, DFHSMUTL. A number of lines
may be written to the report:
DFHSM0300 DFHSMUTL REPORT
Report header.
ADD SUBPOOL=xxxxxxxx PROCESSED SUCCESSFULLY
ADD SUBPOOL=xxxxxxxx has been processed successfully.
DEL SUBPOOL=xxxxxxxx PROCESSED SUCCESSFULLY
DEL SUBPOOL=xxxxxxxx has been processed successfully.
FOUND DFHLCD RECORD SMSUBPOL=xxxxxxxx
Subpool record found by the LST command.
ERROR OPENING DFHLCD
An error has occurred opening the local catalog data set.
The program is terminated.
UNRECOGNISED VERB xxx IN INPUT
Only ADD, DEL and LST are allowed. The statement is
ignored.
UNRECOGNISED OPERAND xxxxxxxx IN INPUT
Only ADD SUBPOOL=xxxxxxxx or DEL SUBPOOL=xxxxxxxx are
allowed. The statement is ignored.
ERROR PROCESSING 'ADD SUBPOOL=xxxxxxxx'. R15 = X'yy'. RPL
FEEDBACK CODE = X'zz'. SEE DFSMS/MVS MACRO INSTRUCTIONS FOR
DATA SETS
A VSAM error has occurred whilst processing an
ADD SUBPOOL=xxxxxxxx command. For the meaning of the VSAM
codes, refer to DFSMS/MVS Macro Instructions for Data Sets, SC26-4913. The program is terminated.
ERROR PROCESSING 'DEL SUBPOOL=xxxxxxxx'. R15 = X'yy'. RPL
FEEDBACK CODE = X'zz'. SEE DFSMS/MVS MACRO INSTRUCTIONS FOR
DATA SETS
A VSAM error has occurred whilst processing a
DEL SUBPOOL=xxxxxxxx command. For the meaning of the VSAM
codes, refer to DFSMS/MVS Macro Instructions for Data Sets, SC26-4913. The program is terminated.
END OF DFHSMUTL REPORT
Report trailer.
See Explanation.
If an error is reported, correct the cause and retry.
SYSPRINT
DFHSMUTL