An unexpected program check or abend aaa/bbbb has occurred in module modname. This implies that there may be an error in external CICS interface code.
Alternatively, unexpected data has been passed on an external CICS interface call or storage has been overwritten.
The code aaa/bbbb is, if applicable, a 3-digit hexadecimal MVS system completion code aaa (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The 4-digit code bbbb, which follows aaa is, if applicable, a user abend code produced by the external CICS interface. If the user abend code is not applicable, this field is filled with four hyphens.
An exception entry is made in the external CICS interface internal trace table, and to the GTF trace dataset (if GTF is active), and a SYSMDUMP is taken.
The external CICS interface terminates the current request, and attempts to recover to a consistent state so that further EXCI requests can be serviced. For an application using the EXCI CALL API, a response of EXCI_SYSTEM_ERROR with a REASON of ESTAE_INVOKED is returned to the application. For an application using the EXCI EXEC API, an EXEC_RESP of LINKERR is returned to the application, together with an EXEC_RESP2 of ESTAE_INVOKED or EXEC_ESTAE_INVOKED, depending on whether the call level ESTAE routine, or the EXEC level ESTAE routine was invoked.
Look up the MVS code aaa, if there is one, in the relevant MVS codes manual which is detailed in the book list in the front of this manual.
If applicable, see the description of abend code bbbb for further guidance.
You may need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.
Console
DFHXCPRH, DFHXCEIP
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 is made in the EXCI internal trace table and to GTF if it is active, (X'code' in the message). A system dump is taken.
This is a critical error and the EXCI request is terminated. The external CICS interface attempts to recover to a consistent state so that further EXCI requests can be issued. For applications using the EXCI CALL API, the EXCI_REASON returned to the application indicates the reason for the error. For applications using the EXCI EXEC API, the reason is returned in the EXEC_RESP2 field of the RETCODE area.
This failure indicates a serious error in the external CICS interface code. For further information about the EXCI exception trace entries, refer to the CICS Problem Determination Guide.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHXCPRH, DFHXCEIP
An MVS GETMAIN was issued by module modname, but it failed with return code rc.
The code X'code' is the exception trace point ID which uniquely identifies the place where the MVS GETMAIN was issued.
An exception entry is made in the EXCI internal trace table (code X'code' in the message). This is a critical error and the EXCI request is terminated. The external CICS interface attempts to recover to a consistent state so that further EXCI requests can be issued.
For applications using the EXCI CALL API, the EXCI_REASON returned to the application indicates the point of failure.
For applications using the EXCI EXEC API, the point of failure is returned in the EXEC_RESP2 field of the RETCODE area.
For EXCI_REASON and EXCI_RESP of 603, the EXCI module DFHXCPRH also issues abend 0410 which drives the ESTAE exit. Message DFHEX0001 is issued and a SYSMDUMP is taken
Look up the MVS GETMAIN return code rc in the relevant MVS codes manual.
If the reason is insufficient storage, try increasing the size of the region for the batch EXCI job.
You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHXCPRH, DFHXCTRI
This message accompanies message DFHEX0001 and will provide the jobname, stepname, procname, Sysid in SMF and applid to which the EXCI job is connecting to. If an insert value is unknown or not specified then the message insert will read Unknown. For example, procname and stepname are not mandatory in an EXCI job, if they were omitted and DFHEX0004 was issued then the inserts for procname and stepname will read Unknown.
Follow system action for DFHEX0001.
Follow user response for DFHEX0001.
Console
DFHXCPRH, DFHXCEIP
The external CICS interface module DFHXCPRH detected that the level of CICS SVC (DFHCSVC) in use does not support the external CICS interface.
The EXCI request is terminated. An exception trace is made in the EXCI internal trace table, and if GTF is active, in the GTF trace data set. The external CICS interface module DFHXCPRH issues abend 0407 which drives the ESTAE exit. Message DFHEX0001 is issued, and a SYSMDUMP is taken.
Check the level of DFHCSVC installed in the LPA. A CICS/ESA 4.1 level of DFHCSVC is required for the external CICS interface. Generally, the latest level of DFHCSVC must be used when running CICS and the external CICS interface. For more information about installing DFHCSVC see the CICS Transaction Server for z/OS® Installation Guide.
Console
DFHXCPRH
The call to DFHIRP to check DFHIRP's service level has failed.
This is probably because the version of DFHIRP being used is at a lower level than that of the External CICS Interface (EXCI) module DFHXCPRH. A less likely reason is that a failure occurred before DFHIRP could make the level check.
The EXCI allocate pipe request is rejected. A return code is passed back to the batch application.
Ensure that the correct level of DFHIRP exists in the LPA such that
it matches the level of the latest CICS version in use.
Console
DFHXCPRH
This message is issued on successful completion of a MVS SDUMP issued by external CICS interface module DFHXCDMP. An error, signalled by a previous message, caused a call to be made to DFHXCDMP to take a system dump.
The dump code dumpcode is an 8-character system dump code identifying the external CICS interface problem. A system dump code is the EXCI message number with the DFH prefix removed.
dumpid is the unique 9-character string identifying this dump.
The EXCI request is terminated.
See the EXCI message indicated by dumpcode for further guidance.
You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHXCDMP.
At the time of the MVS SDUMP request issued by DFHXCDMP another address space in the same MVS system was in the process of taking an SDUMP. This causes MVS to reject the new request. A nonzero value for the dump retry parameter in the DFHXCOPT table means that the external CICS interface waits five seconds before retrying the SDUMP request. If necessary, the external CICS interface retries every five seconds for the total time specified on the retry parameter.
The external CICS interface issues an MVS STIMERM macro which causes it to wait for five seconds. The request is reissued when the delay interval has expired.
None.
Console
DFHXCDMP.
An MVS SDUMP request issued from the external CICS interface has failed to complete successfully. The possible reasons, (reason) for the failure are as follows:
The EXCI proceeds as if the dump had been successful.
The user response depends on the reasons, (reason), for the failure.
Console
DFHXCDMP
An attempt to initialize external CICS interface (EXCI) trace facilities during EXCI initialization has failed.
The EXCI request continues without trace facilities. An earlier message identifies the cause of the failure.
Refer to the earlier message to determine the cause of the failure.
Console
DFHXCTRI
Some data passed to the external CICS interface (EXCI) trace module DFHXCTRP for addition to the EXCI internal trace table, or GTF trace, caused a program check to occur when an attempt was made to access it.
The most likely cause of this error is incorrect data passed on an EXCI CALL API request that the trace program DFHXCTRP is attempting to access.
The EXCI request is terminated and a SYSMDUMP is taken.
Examine the dump to determine the source of the incorrect data.
You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHXCTRI
An error occurred in the external CICS interface (EXCI) trace module DFHXCTRP indicated by message DFHEX0001. In trying to recover from the error, module DFHXCTRI determined that the error was not caused by accessing incorrect data passed to DFHXCTRP, but was due to a program check in DFHXCTRP.
The EXCI trace facilities are disabled to prevent further errors. A SYSMDUMP is taken.
See the DFHEX0001 message and the SYSMDUMP to determine the cause of the error.
You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHXCTRI
After making a trace entry, the external CICS interface (EXCI) trace program DFHXCTRP called the EXCI field engineering global trap program DFHXCTRA. A program check occurred during execution of DFHXCTRA.
The EXCI marks the currently active version of DFHXCTRA as unusable and ignores it on subsequent calls to DFHXCTRP for all subsequent calls made under this TCB. The EXCI request is terminated, and a SYSMDUMP is taken.
Use the dump to find the cause of the program check.
You may need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
You should use the global trap exit only in consultation with an IBM support representative.
Console
DFHXCTRI