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 DFHDP1310).
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 and bring CICS down at a convenient time to resolve the problem.
If you cannot continue 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
DFHDP*
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
DFHDPFM, DFHDPLM, DFHDPUM.
XMEOUT Parameters:
applid,
X'
code',
modname
A call to CICS file control from a DP domain module has received an unexpected exception response from DFHFCFR. The reason code given in the message is the reason from the FCFR parameter list on return from file control.
The file given in the message is not usable.
The application debugging profiles manager will fail until the problem has been corrected. It the CICS supplied transaction, CADP, is being used to define debugging profiles it will fail with an ADPA abend.
The meaning of the reason code in the message is given below:
There has been an input/output(IO) error trying to access the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. Examine the console to find file control or VSAM messages that will indicate the reason for the error.
The data set for the debugging profiles file, DFHDPFMB, is currently unavailable because it is being copied. Retry when it becomes available.
The file definition for the debugging profiles base data set, DFHDPFMB, or path data set, DFHDPFMP, is disabled. Enable the disabled file and retry.
The file definition for the debugging profiles base data set, DFHDPFMB, or path data set, DFHDPFMP, cannot be opened. Examine the console to find file control or VSAM messages that will indicate the reason for the error.
A definition for the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP, could not be found. Sample definitions for these files are available and should be defined and installed before retrying.
The debugging profiles base file, DFHDPFMB, is full. Investigate whether there are degbugging profiles that can be deleted. Or, increase the storage allocation for the underlying VSAM data set, and recreate. Existing profiles could be backed up on another data set and then copied to the newly defined debugging profiles data set as part of the JCL to recreate it. To achieve this, replace REPRO INFILE with REPRO INDATASET in the JCL and replace SYS01 with the name of the data set containing the backed up profiles.
There has been an IO error trying to access the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. Examine the console to find file control or VSAM messages that will indicate the reason for the error.
An attempt has been made to ship a file control request but ISC=NO for the system. Determine if ISC should be YES or if the file definition should be changed so that shipping is not required and retry.
An attempt has been made to write a record to the debugging profiles base file, DFHDPFMB, but a retained lock exists against the key of the record being written.
There has been an IO error trying to access the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. Examine the console to find file control or VSAM messages that will indicate the reason for the error.
There has been an IO error trying to access the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. Examine the console to find file control or VSAM messages that will indicate the reason for the error.
The user is not authorized to use the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. If the user should have access to the files, allow access and retry.
The debugging profiles file, DFHDPFMB, has been defined as record level sharing(RLS) but RLS is currently unavailable due to a failure. Investigate the reason for the RLS failure by looking for messages from file control and VSAM on the console. Retry when RLS is available.
The external security manager would not allow the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP, to be accessed. If the user should have access to the files, allow access and retry. .
A journal referenced in the definition for the debugging profiles file, DFHDPFMB, is using an MVS which in turn, is using a coupling facility structure that has been defined with a MAXBUFSIZE parameter less than the recommended 64000. Redefine the coupling facility structure that the logstream is using with a MAXBUFSIZE parameter of 64000. The journal in error can be the forward recovery log or the journal used for auto-archiving.
The debugging profiles file, DFHDPFMB, has been defined as record level sharing(RLS) but RLS is currently disabled. Investigate why RLS is disabled by examining the console for file control and VSAM messages. Retry when RLS is available.
The debugging profiles file has been defined as record level sharing(RLS) but RLS is currently unavailable due to a failure. Investigate the reason for the failure by examining the console for file control and VSAM messages. Retry when RLS is available.
The definition for the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP, does not allow all types of file request to be issued. Alter the file definitions to allow all file requests and retry.
A user exit has suppressed the writing of records to the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. The exit should not be allowed to suppress records being written to these files. Correct the exit and retry.
The SYSID for the file definition for the debugging profile base file, DFHDPFMB, or path file, DFHDPFMP, specifies a name that is neither the local CICS region nor a remote system defined to CICS by a CONNECTION definition. SYSIDERR can also occur if the link to the remote system is closed. Correct the SYSID or reopen the link and retry.
The external security manager would not allow the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP, to be accessed. If the user should have access to the files, allow access and retry. .
There has been an IO error trying to access the debugging profiles base file, DFHDPFMB, or path file, DFHDPFMP. Examine the console to find file control or VSAM messages that will indicate the reason for the error.
Investigate and correct the error based on the reason given and retry.
Console
DFHDPFM, DFHDPLM, DFHDPUM.
XMEOUT Parameters:
applid,
X'
code',
modname,
filename
CICS is running with a level of Debug Tool which is older than Version 3.1.
The CADP transaction and the web interface can be used to define debugging profiles and they can be activated. However, Debug Tool will not be able to use these profiles.
If you do not intend to perform LE debugging on this system or you only want to use CADP and the web interface to define profiles for use on another CICS region which does have Debug Tool at least at the version 3.1 level, then no action is required. If the intention is to use LE debugging profiles on this CICS, then Debug Tool version 3.1 or later must be installed.
Console
DFHDPLU
XMEOUT Parameter:
applid
The transaction CIDP or the program DFHDPIN has been run to inactivate all currently active debugging profiles. num debugging profiles have been inactivated.
None.
None.
Console
DFHDPIN.
XMEOUT Parameters:
applid,
num
The transaction CIDP or the program DFHDPIN has been run to inactivate all currently active debugging profiles. It was not possible to inactivate the profiles as the CADP file DFHDPFMB was not available.
Inactivation is canceled.
Make the CADP file DFHDPFMB available and reissue the CIDP command.
Console
DFHDPIN.
XMEOUT Parameter:
applid