Reason codes for response: SYSTEM_ERROR

601
WS_GETMAIN_ERROR
Explanation:

During Initialize_User processing, a GETMAIN for working storage failed.

System action:

Processing cannot continue without working storage, so the request is terminated. At this point the external CICS® interface trace and dump services are not available to provide diagnostic information, therefore EXCI issues an MVS™ abend (U0408) to force a SYSMDUMP. The return code from the MVS GETMAIN request is returned in the return area.

User response:

Locate the GETMAIN return code in the dump, and use this and the rest of the dump to determine why the GETMAIN failed. A possible reason for this is that the region size specified for the job is too small. If this is the case, increase the region size and restart the client application program.

602
XCGLOBAL_GETMAIN_ERROR
Explanation:

During Initialize_User processing, a GETMAIN failed for a critical control block (XCGLOBAL).

System action:

Processing cannot continue without this control block, and the request is terminated. At this point the external CICS interface trace and dump services are not available to provide diagnostic information, therefore EXCI issues an MVS abend (U0403) to force a SYSMDUMP. The return code from the MVS GETMAIN request is returned in the return area.

User response:

Locate the GETMAIN return code in the dump, and use this and the rest of the dump to determine why the GETMAIN failed. A possible reason for this is that the region size specified for the job is too small. If this is the case, increase the region size and restart the client application program.

603
XCUSER_GETMAIN_ERROR
Explanation:

During Initialize_User processing, a GETMAIN request failed for the user control block (XCUSER).

System action:

Initialize_User processing is terminated. The return code from the GETMAIN is returned in subreason field-1 of the return area. The external CICS interface issues message DFHEX0003 and issues an MVS user abend (0410) to force a SYSMDUMP.

User response:

Use the return code from the GETMAIN, with the dump, to determine why the GETMAIN failed. A possible reason for this is that the region size of the job is too small. If this is the case, increase the region size and restart the client application program.

604
XCPIPE_GETMAIN_ERROR
Explanation:

During Allocate_Pipe processing, a GETMAIN request for the pipe control block (XCPIPE) failed.

System action:

Allocate_Pipe processing is terminated. The return code from the GETMAIN is returned in subreason field-1 of the EXCI return area. The external CICS interface issues message DFHEX0003, and takes a system dump.

User response:

Use the return code from the GETMAIN, and the dump, to determine why the GETMAIN failed. A possible reason for this is that the region size for the job is too small. If this is the case, increase the region size and restart the client application program.

605
VERIFY_BLOCK_GM_ERROR
Explanation:

During Initialize_User processing, a GETMAIN failed for an EXCI internal control block.

System action:

Initialize_User processing is terminated. The return code from the GETMAIN is returned in the subreason field-1 of the EXCI return area. This error occurs before EXCI dumping services are initialized, Therefore EXCI issues an MVS abend (U0409) to force a SYSMDUMP The return code from the MVS GETMAIN request is returned in the return area.

User response:

Locate the GETMAIN return code in the dump, and use this and the rest of the dump to determine why the GETMAIN failed. A possible reason for this is that the region size specified for the job is too small. If this is the case, increase the region size and restart the client application program.

606
SSI_VERIFY_FAILED
Explanation:

A VERIFY call to the MVS subsystem interface (SSI) to obtain the current CICS SVC number failed.

System action:

The Initialize_User request is terminated. The return code from the SSI call is returned in subreason field-1 of the return area. This error occurs before the external CICS interface dump services are initialized, therefore EXCI issues an MVS user abend (0405) to force a SYSMDUMP.

User response:

Locate the return code in the dump, and use this with the rest of the dump and SSI documentation to determine why the VERIFY request failed. When the problem is resolved, restart the client application program.

607
CICS_SVC_CALL_FAILURE
Explanation:

During Initialize_User processing, a call to the currently installed CICS SVC failed.

System action:

The return code from the CICS SVC is returned in the subreason field-1 of the EXCI return area. This error occurs before the external CICS interface dump services are initialized, therefore EXCI issues an MVS user abend (0406) to force a SYSMDUMP.

User response:

Contact your IBM® support center for assistance, with the return code and the dump available.

608
IRC_LOGON_FAILURE
Explanation:

During Allocate_Pipe processing, an attempt by the external CICS interface to LOGON to DFHIRP failed.

System action:

The Allocate_Pipe request fails. DFHIRP returns a R15 value to subreason field-1 and a R0 value (the reason code) to subreason field-2. The first two bytes of subreason field-1 are the return code qualifier and the last two bytes are the return code itself.

User response:

For an explanation of the IRP return codes, see the interregion control blocks in the CICS Data Areas manual. The IRP return codes are in the DFHIRSPS copybook, listed under the heading IRC. Use the return codes to determine why the logon failed, or contact your IBM support personal with details of the failure.

609
IRC_CONNECT_FAILURE
Explanation:

During Open_Pipe processing, an attempt to connect to the target CICS system failed.

System action:

The Open_Pipe request fails. DFHIRP returns a R15 value to subreason field-1 and a R0 value (the reason code) to subreason field-2. The first two bytes of subreason field-1 are the return code qualifier and the last two bytes are the return code itself.

User response:

For an explanation of the IRP return codes, see the interregion control blocks in the CICS Data Areas manual. The IRP return codes are in the DFHIRSPS copybook, listed under the heading IRC.

Use the return code to determine why the logon failed, and reissue the open pipe request.

Note:
This error is not caused by the target CICS being unavailable, which is returned as a RETRYABLE condition (NO_CICS).
610
IRC_DISCONNECT_FAILURE
Explanation:

During Close_Pipe processing, CICS issued a DFHIRP disconnect call to terminate the connection to CICS. This request has failed.

System action:

The call fails and the pipe is left open. DFHIRP returns a R15 value to subreason field-1 and a R0 value (the reason code) to subreason field-2. The first two bytes of subreason field-1 are the return code qualifier and the last two bytes are the return code itself.. The external CICS interface takes a system dump.

Although the disconnect failed, it is possible that the pipe is still connected to CICS. However, all connections are automatically disconnected at the end of the batch program.

User response:

For an explanation of the IRP return codes, see the interregion control blocks in the CICS Data Areas manual. The IRP return codes are in the DFHIRSPS copybook, listed under the heading IRC. Use the return code and the dump to determine the cause of the error.

611
IRC_LOGOFF_FAILURE
Explanation:

During Deallocate_Pipe processing, CICS issued a DFHIRP logoff call. This request failed.

System action:

The Deallocate_Pipe call fails and the pipe remains allocated. DFHIRP returns a R15 value to subreason field-1 and a R0 value (the reason code) to subreason field-2. The first two bytes of subreason field-1 are the return code qualifier and the last two bytes are the return code itself. The external CICS interface takes a system dump.

Note:
Because it remains allocated, the pipe is available for further calls. Any storage associated with the pipe is not freed. However, this storage is freed at the end of the client application program.
User response:

For an explanation of the IRP return codes, see the interregion control blocks in the CICS Data Areas manual. The IRP return codes are in the DFHIRSPS copybook, listed under the heading IRC. Use the return code and the dump to determine the cause of the error.

612
TRANSFORM_1_ERROR
Explanation:

During DPL processing, whilst processing the data in preparation for sending to CICS, an internal call to program DFHXFQ resulted in an error.

System action:

The DPL request is terminated.

User response:

The return code from the call is returned in the EXCI subreason field-1, and the external CICS interface takes a system dump.

This is an external CICS interface error. Contact your IBM support center with details of the return code and the dump.

613
TRANSFORM_4_ERROR
Explanation:

During DPL processing, whilst processing the data returned by the CICS server region, an internal call to module DFHXFQ resulted in an error.

System action:

The DPL request is terminated. Note that the server application program has executed. The return code from the call to DFHXFQ is returned in the EXCI subreason field-1. This return code corresponds to any EIBRCODE information that was available. The external CICS interface takes a system dump.

User response:

This is an external CICS interface error. Contact your IBM support center with details of the return code and the dump.

614
IRP_NULL_DATA_RECEIVED
Explanation:

During DPL processing, a request has been sent to the target CICS and this target CICS has replied without returning any data.

System action:

The DPL processing is terminated and the external CICS interface takes a system dump.

User response:

This is an internal protocol error. Contact your IBM support center with details of the dump.

615
IRP_NEGATIVE_RESPONSE
Explanation:

An internal protocol error has occurred whilst trying to communicate with the target CICS region.

System action:

The DPL request fails, the pipe is put into a "must close" state, and the external CICS interface takes a system dump.

User response:

This is an external CICS interface error. Keep the dump and contact your IBM support center.

Note:
The pipe is in a "must close" state. Before attempting further calls, the pipe must first be closed and reopened.
616
IRP_SWITCH_PULL_FAILURE
Explanation:

An internal protocol error has occurred whilst trying to communicate with the target CICS region.

System action:

The DPL request fails, the pipe is put into a "must close" state, and the external CICS interface takes a system dump. The IRP return code (R15) and reason code if any (R0) are returned in the EXCI subreason field-1 and subreason field-2.

User response:

This is an external CICS interface error. Keep the dump and contact your IBM support center.

Note:
The pipe is in a "must close" state, and before attempting further DPL calls, the pipe must first be closed and reopened.
617
IRP_IOAREA_GM_FAILURE
Explanation:

During DPL processing, an MVS GETMAIN request for an internal control block failed.

System action:

The DPL request is terminated. The return code from the GETMAIN is returned in the EXCI subreason field-1.

Note:
This error occurs whilst processing the data returned by CICS, after the server application program has completed execution. This error results in the pipe being put into a "must close" state.
User response:

Use the return code to determine why the GETMAIN failed. A possible reason for this is that the region size of the job is too small. If this is the case, increase the region size and restart the batch job.

619
IRP_BAD_IOAREA
Explanation:

During a DPL request, an I/O area has been supplied to DFHIRP that could not be used.

System action:

The DPL request is terminated, the pipe is forced into a "must close" state, and the external CICS interface takes a system dump.

User response:

This is an external CICS interface error. Contact the IBM support center with details of the return code and the dump.

Note:
The pipe is in a "must close" state after this error, and before attempting further calls must first be closed and reopened.
620
IRP_PROTOCOL_ERROR
Explanation:

An internal protocol error has occurred whilst trying to communicate with the target CICS system.

System action:

The DPL request is terminated, the pipe is forced into a "must close" state, and the external CICS interface takes a system dump.

User response:

This is an external CICS interface error. Keep the dump and contact your IBM support center.

Note:
The pipe is in a "must close" state after this error, and before attempting further calls must first be closed and reopened.
621
PIPE_RECOVERY_FAILURE
Explanation:

An error has occurred during an open pipe request. The external CICS interface attempts to recover by disconnecting the pipe again. During this disconnection, further errors have occurred.

System action:

The Open_Pipe call is terminated and the pipe is placed in a "must close" state. The return code from DFHIRP is returned in the EXCI subreason field-1, and a system dump is taken.

User response:

For an explanation of the IRP return codes, see the interregion control blocks in the CICS Data Areas manual. The IRP return codes are in the DFHIRSPS copybook, listed under the heading IRC. Use the dump and IRP return codes to determine why the disconnect failed. You may also want to use the EXCI trace to determine the earlier error that caused the open pipe recovery routine to be invoked.

Note:
The pipe is now in a "must close" state and if further calls are to be issued, the pipe must be closed and reopened again first.
622
ESTAE_SETUP_FAILURE
Explanation:

In order to protect itself from possible program checks the external CICS interface establishes an MVS ESTAE. In this case, the MVS ESTAE macro has failed.

System action:

The call terminated, and the return code from the MVS ESTAE command is returned in the EXCI subreason field-1. This error may occur before EXCI dump services are initialized, therefore an EXCI issues an MVS abend (U0402) to force a SYSMDUMP.

User response:

Use the return code and the dump to determine why the ESTAE command failed. This may be an internal EXCI error and if the problem persists, contact your IBM support center.

623
ESTAE_INVOKED
Explanation:

A program check is encountered during call processing, and the ESTAE is invoked.

System action:

The program check is handled by the EXCI ESTAE and an attempt is made to recover to a state that can support further EXCI calls. The MVS abend code is returned in the EXCI subreason field-1 of the return area. To aid further diagnosis, a SYSMDUMP is taken.

User response:

Use the return code and the dump to determine why a program check occurred in the external CICS interface. The most likely reason for this is that the EXCI code abended whilst trying to access the client program's parameters. Use the EXCI trace to determine if any of the parameters might have caused this error. If this is not the case, this may be an error in the external CICS interface. Keep the dump and contact your IBM support center.

624
SERVER_TIMEDOUT
Explanation:

A DPL request has been issued and the target server program has executed in the CICS server region. However, the server program has been executing for longer than the time-out value specified in the DFHXCOPT table.

System action:

The external CICS interface stops waiting for the server program to complete. Because the server program might complete some time after the time-out, and try to respond to the DPL call, the pipe is forced into a "must close" state.

User response:

Determine why the server application program timed out. Either there is a problem with the server program itself (for example, it might be in a loop), or the timeout value is too low.

625
STIMER_SETUP_FAILURE
Explanation:

In order to provide a TIMEOUT mechanism, the external CICS interface issues an MVS STIMERM macro call. This call has failed.

System action:

The return code from the call is returned in the subreason field-1 of the EXCI return area. The DPL request is terminated and the external CICS interface takes a system dump. The pipe is placed in a "must close" state.

User response:

Use the MVS return code and the dump to determine why the call failed. This could be an external CICS interface error. Contact your IBM support center with details of the dump.

Note:
The pipe is in a "must close" state after this error, and before attempting further calls must first be closed and reopened.
626
STIMER_CANCEL_FAILURE
Explanation:

On successful completion of a DPL request, the cancel of an STIMERM request issued to check the TIMEOUT value has failed with an error.

System action:

The return code from the STIMERM CANCEL is returned in the subreason field-1 of the EXCI return area. The pipe is placed in a "must close" state, and the external CICS interface takes a system dump.

User response:

Use the return code and the dump to determine why the MVS STIMERM CANCEL command failed. This could be an external CICS interface error. Contact your IBM support center with details of the dump.

Note:
The pipe is in a "must close" state after this error, and before attempting further calls must first be closed and reopened.
627
INCORRECT_SVC_LEVEL
Explanation:

The release level of the CICS SVC (DFHCSVC) is not the same (or higher) than the release level of the external CICS interface.

System action:

The Initialize_User request is terminated. This error occurs before the external CICS interface SDUMP facilities are initialized, therefore EXCI issues an MVS abend (U0407) to force a SYSMDUMP.

User response:

Determine the level of the CICS SVC being used and ensure it is the same release level as the external CICS interface, or higher. If the SVC number is allowed to default (CICSSVC=0 in DFHXCOPT), the SVC number being used is the SVC first used by a CICS region on the MVS image. That is, the SVC used by the first CICS region to open the CICS interregion communications (IRC). If the SVC number is specified on CICSSVC in DFHXCOPT, the SVC number specified is at an incorrect level. For more information, see the description of the CICSSVC parameter in Using the EXCI options table, DFHXCOPT.

628
IRP_LEVEL_CHECK_FAILURE
Explanation:

The release level of the module DFHIRP is not at the same, or higher, level than the release level of the external CICS interface.

System action:

The Allocate_pipe request is terminated. The IRP return code (R15) is returned in the EXCI subreason field-1, and the function level of DFHIRP being used is returned in the EXCI subreason field-2. Subreason field-2 is only meaningful if subreason field-1 is zero. The external CICS interface takes a system dump.

User response:

Check the level of the DFHIRP module installed in the LPA. Ensure that it is at least the same as the external CICS interface. The installed level of DFHIRP must be the highest level of CICS or external CICS interface in use in the MVS image. For more details about installing DFHIRP, see the CICS Transaction Server for z/OS® Installation Guide.

629
SERVER_PROTOCOL_ERROR
Explanation:

A response to a DPL request has been returned by CICS but the external CICS interface does not understand the response.

System action:

The DPL request is terminated and the external CICS interface takes a system dump.

User response:

Use the dump to determine why the response was in error. The most likely reason for this is that the CICS application server program was not running under the control of a CICS mirror task. This can happen if the transaction definition named by the transid parameter on the DPL call does not specify DFHMIRS as the program name. This would cause unidentified responses being sent from the CICS server region.

630
RRMS_ERROR
Explanation:

An unexpected return code was received from Recoverable Resource Management Services (RRMS) while processing a DPL_Request.

System action:

DPL_Request processing is terminated.

The value in subreason field-1 of the return area indicates which RRMS interface returned the unexpected return code:

1
CTXRCC
2
ATRRURD
3
CTXSDTA

The return code from the RRMS request is returned in subreason field-2.

The external CICS interface issues message DFHEX0002, and takes a system dump.

User response:

Use the return code from the RRMS request and the dump, to determine why the request failed. This may be an internal EXCI error or a problem with RRMS and you may need the assistance of your IBM support center.

631
RRMS_SEVERE_ERROR
Explanation:

During the processing of a DPL_Request, the EXCI code encountered an unexpected error while using its interface with Recoverable Resource Management Services (RRMS).

System action:

DPL_Request processing is terminated.

The external CICS interface issues message DFHEX0002, and takes a system dump.

User response:

Use the dump, to determine why the request failed. This may be an internal EXCI error and you may need the assistance of your IBM support center.

632
XCGUR_GETMAIN_ERROR
Explanation:

During DPL_Request processing, a GETMAIN request for working storage for module DFHXCGUR failed.

System action:

DPL_Request processing is terminated.

The return code from the GETMAIN is returned in subreason field-1 of the return area. The external CICS interface issues message DFHEX0003, and takes a system dump.

User response:

Use the return code from the GETMAIN, and the dump, to determine why the GETMAIN failed. A possible reason is that the region size of the job is too small. If this is the case, increase the region size and restart the client application program.

[[ Contents Previous Page | Next Page Index ]]