Messages and Codes

This section lists messages and abend codes for the external CICS® interface.

DFHEX0001
An abend (code aaa/bbbb) has occurred in module modname.
Explanation:

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.

System action:

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.

User response:

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 the CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Module:

DFHXCPRH, DFHXCEIP

DFHEX0002
A severe error (code X'code') has occurred in module modname.
Explanation:

An error has been detected in module modname. The code code is the exception trace point ID which uniquely identifies what the error is and where the error was detected.

System action:

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.

User response:

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.

Destination:

Console

Module:

DFHXCPRH, DFHXCEIP

DFHEX0003
A GETMAIN request in module modname (code X'code') has failed. Reason X'rc'.
Explanation:

An MVS GETMAIN was issued by module modname, but it failed with return code rc.

The code code is the exception trace point ID which uniquely identifies the place where the MVS GETMAIN was issued.

System action:

An exception entry is made in the EXCI internal trace table (code 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

User response:

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 the CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Module:

DFHXCPRH, DFHXCTRI

DFHEX0004
JOBNAME: jobname, STEPNAME: stepname, PROCNAME: procname, SYSID IN SMF: sysid, APPLID: applid.
Explanation:

This message accompanies message DFHEX0001 and provides the jobname, stepname, procname, Sysid in SMF and applid to which the EXCI job is connecting. If an insert value is unknown or not specified, then the message insert will show Unknown. For example, procname and stepname are not mandatory in an EXCI job. If they are omitted and DFHEX0004 is issued, then the inserts for procname and stepname show Unknown.

System action:

Follow system action for DFHEX0001.

User response:

Follow user response for DFHEX0001.

Destination:

Console

Module:

DFHXCPRH, DFHXCEIP

DFHEX0100
The installed level of CICS SVC does not support the EXCI call.
Explanation:

The external CICS interface module DFHXCPRH detected that the level of CICS SVC (DFHCSVC) in use does not support the external CICS interface.

System action:

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.

User response:

Check the level of DFHCSVC installed in the LPA, which 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.

Destination:

Console

Module:

DFHXCPRH

DFHEX0101
Unable to start interregion communication because DFHIRP services are down level.
Explanation:

The version of DFHIRP being used is at a lower level than that of the External CICS Interface (EXCI) module DFHXCPRH.

System action:

The EXCI allocate pipe request is rejected, and a return code passed back to the batch application.

User response:

Update the level of the DFHIRP module in the LPA such that it matches the level of the latest CICS version in use.

Destination:

Console

Module:

DFHXCPRH

DFHEX0110
EXCI SDUMP has been taken. Dumpcode: dumpcode, Dumpid: dumpid.
Explanation:

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.

System action:

The EXCI request is terminated.

User response:

See the EXCI message indicated by dumpcode for further guidance.

You may need further assistance from IBM to resolve this problem. See the CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Module:

DFHXCDMP.

DFHEX0111
EXCI SDUMP attempted but SDUMP is busy - will retry every five seconds for nnnn seconds.
Explanation:

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.

System action:

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.

User response:

None.

Destination:

Console

Module:

DFHXCDMP.

DFHEX0112
SDUMP request failed - reason X'nn'.
Explanation:

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:

ONLY PARTIAL DUMP
The SYS1.DUMP data set to which the dump is written is not large enough to contain all of the dumped storage.
SDUMP BUSY
At the time of the MVS SDUMP request issued by the EXCI, another address space in the same MVS system was in the process of taking an SDUMP. This causes MVS to reject the new request. If a nonzero value is specified for the dump retry parameter in DFHXOPTS table, the EXCI has retried the SDUMP request every five seconds for the specified period. This message is only issued if SDUMP is still busy after the final retry.
STIMERM FAILED
In order to delay for five seconds before retrying SDUMP after an SDUMP BUSY condition, the EXCI issues an MVS STIMERM macro request. MVS has indicated that the STIMERM request has failed.
NO DATA SET AVAILABLE
No SYS1.DUMP data sets were available at the time the SDUMP request was issued.
REJECTED BY MVS, REASON = X'nn'
MVS has rejected the SDUMP request because of user action (for example, specifying DUMP=NO in the MVS IPL) or because of an I/O error or terminating error in the SDUMP routine. X'nn' is the SDUMP reason code.
NOT AUTHORIZED FOR EXCI
SDUMP is not authorized for the external CICS interface.
INSUFFICIENT STORAGE
The EXCI issued an MVS GETMAIN for subpool 253 storage during the processing of the SDUMP request. The GETMAIN has been rejected by MVS.
System action:

The EXCI proceeds as if the dump had been successful.

User response:

The user response depends on the reasons, (reason), for the failure.

ONLY PARTIAL DUMP
Increase the size of the SYS1.DUMP data sets and cause the SDUMP request to be reissued.
SDUMP BUSY
Cause the SDUMP to be reissued after, if appropriate, increasing the dump retry time in DFHXCOPT.
STIMERM FAILED
Use MVS problem determination methods to fix the STIMERM failure and then cause the SDUMP request to be reissued.
NO DATA SET AVAILABLE
Clear a SYS1.DUMP data set and then cause the SDUMP request to be reissued.
REJECTED BY MVS, REASON = X'nn'
No action is required if the dump is suppressed deliberately. If the dump has failed because of an error in the MVS SDUMP routine, use MVS problem determination methods to fix the error and then cause the SDUMP request to be reissued. See the OS/390 MVS Programming: Assembler Services Reference, for an explanation of the SDUMP reason code X'nn'.
NOT AUTHORIZED FOR EXCI
This reason is unlikely because SDUMP is unconditionally authorized during EXCI initialization, and should be authorized throughout the EXCI run. If you do get this reason, the EXCI AFCB (authorized function control block) has probably been accidentally overwritten.
INSUFFICIENT STORAGE
Ensure sufficient storage is available to MVS for subpool 253 requests.
Destination:

Console

Module:

DFHXCDMP

DFHEX0113
EXCI trace Initialization has failed.
Explanation:

An attempt to initialize external CICS interface (EXCI) trace facilities during EXCI initialization has failed.

System action:

The EXCI request continues without trace facilities. An earlier message identifies the cause of the failure.

User response:

Refer to the earlier message to determine the cause of the failure.

Destination:

Console

Module:

DFHXCTRI

DFHEX0114
Incorrect data has been passed for EXCI tracing causing a program check in DFHXCTRP.
Explanation:

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.

System action:

The EXCI request is terminated and a SYSMDUMP is taken.

User response:

Examine the dump to determine the source of the incorrect data.

You may need further assistance from IBM to resolve this problem. See the CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Module:

DFHXCTRI

DFHEX0115
EXCI trace services have been disabled due to a previous error.
Explanation:

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.

System action:

The EXCI trace facilities are disabled to prevent further errors. A SYSMDUMP is taken.

User response:

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 the CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Module:

DFHXCTRI

DFHEX0116
Program check occurred within global trap exit - DFHXCTRA now marked unusable.
Explanation:

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.

System action:

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.

User response:

Use the dump to find the cause of the program check.

You may need further assistance from IBM to resolve this problem. See the 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.

Destination:

Console

Module:

DFHXCTRI

[[ Contents Previous Page | Next Page Index ]]