Start of change

04xx (external CICS interface) abend codes

0401
Explanation:

An external CICS interface (EXCI) request was issued using the CALL API or the EXEC API, and the EXCI stub DFHXCSTB link-edited with the application detected that it was running in AMODE 24. The external CICS interface only supports calls made in AMODE 31.

System action:

The application terminates abnormally.

User response:

Change the application so that EXCI calls are made in AMODE 31, or relink-edit the application AMODE 31.

Modules:

DFHXCSTB.

0402
Explanation:

The external CICS interface module DFHXCPRH issued an MVS ESTAE macro to establish a recovery environment, but a nonzero return code was returned from MVS.

System action:

The application terminates abnormally with a dump.

User response:

Examine the dump and any associated MVS messages produced to determine why the MVS ESTAE request failed.

If the error occurred while processing an INITIALIZE_USER request on behalf of the application, an attempt to format the dump using the CICS IPCS dump formatter does not produce any formatted output. This is because the error occurred too early in EXCI initialization for there to be any control blocks.

Modules:

DFHXCPRH

0403
Explanation:

The external CICS interface module DFHXCPRH issued an MVS GETMAIN request to obtain storage for its XCGLOBAL block, but a nonzero return code was returned from MVS.

System action:

Module DFHXCPRH issues an MVS abend with abend code 0403 which invokes its ESTAE routine to clear up its environment. A SYSMDUMP is taken before returning control to the application. An application using the EXCI CALL API receives RESPONSE(SYSTEM_ERROR) REASON(XCGLOBAL_GETMAIN_ERROR) in its return area. The subreason1 field of the return area contains the R15 return code from MVS indicating why the GETMAIN failed. An application using the EXCI EXEC API receives RESP(LINKERR) RESP2(602).

User response:

Use the MVS R15 return code obtained from the application or from the dump to determine why the MVS GETMAIN request failed. If the reason is insufficient storage, increase the region size of the batch application.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter does not produce any formatted output for the job because the error occurred too early in EXCI initialization for there to be any control blocks.

Modules:

DFHXCPRH

0404
Explanation:

The external CICS interface module DFHXCPRH needed to take an MVS SDUMP for an earlier reported problem. However the error has occurred too early in EXCI initialization for EXCI dump services to be available.

System action:

Module DFHXCPRH issues an MVS abend with abend code 0404 which invokes its ESTAE routine from which a SYSMDUMP is taken instead of an SDUMP to capture the earlier reported problem.

User response:

Examine the SYSMDUMP to determine the cause of the earlier reported problem.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter does not produce any formatted output for the job because the error occurred too early in EXCI initialization for there to be any control blocks.

Modules:

DFHXCPRH

0405
Explanation:

The external CICS interface module DFHXCPRH issued an IEFSSREQ SSI verify request to MVS to determine the number of the CICS SVC type 3 SVC to use. The SSI VERIFY request failed.

System action:

Module DFHXCPRH issues an MVS abend with abend code 0405 which invokes its ESTAE routine to clear up its environment. A SYSMDUMP is taken before returning control to the application. An application using the EXCI CALL API receives RESPONSE(SYSTEM_ERROR) REASON(SSI_VERIFY_FAILED) in its return area. The subreason1 field of the return area contains the R15 return code from MVS indicating why the SSI verify failed. An application using the EXCI EXEC API receives RESP(LINKERR) RESP2(606).

User response:

Use the MVS R15 return code obtained from the application or from the dump to determine why the SSI VERIFY request failed.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter does not produce any formatted output for the job because the error occurred too early in EXCI initialization for there to be any control blocks.

Modules:

DFHXCPRH

0406
Explanation:

The external CICS interface module DFHXCPRH called the CICS SVC to initialize the EXCI environment. The CICS SVC call failed.

System action:

Module DFHXCPRH issues an MVS abend with abend code 0406 which invokes its ESTAE routine to clear up its environment. A SYSMDUMP is taken before returning control to the application. An application using the EXCI CALL API receives RESPONSE(SYSTEM_ERROR) REASON(CICS_SVC_CALL_FAILURE) in its return area. The subreason1 field of the return area contains the R15 return code from the CICS SVC indicating why it failed. An application using the EXCI EXEC API receives RESP(LINKERR) RESP2(607).

User response:

Use the MVS R15 return code obtained from the application or from the dump to determine why the CICS SVC call failed.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter does not produce any formatted output for the job because the error occurred too early in EXCI initialization for there to be any control blocks.

Modules:

DFHXCPRH

0407
Explanation:

The external CICS interface module DFHXCPRH issued a call to the CICS SVC to check whether the SVC in use is at the correct level to be used with the external CICS interface. The check failed indicating that the CICS SVC is not at the correct level.

System action:

Message DFHEX0100 is output, and module DFHXCPRH issues an MVS abend with abend code 0407 which invokes its ESTAE routine to clear up its environment. A SYSMDUMP is taken before returning control to the application. An application using the EXCI CALL API receives RESPONSE(SYSTEM_ERROR) REASON(INCORRECT_SVC_LEVEL) in its return area. An application using the EXCI EXEC API receives RESP(LINKERR) RESP2(627).

User response:

See the explanation of message DFHEX0100 for guidance.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter does not produce any formatted output for the job because the error occurred too early in EXCI initialization for there to be any control blocks.

Modules:

DFHXCPRH

0408
Explanation:

The external CICS interface module DFHXCPRH issued an MVS GETMAIN request for its working storage but a nonzero return code was returned from MVS.

System action:

Module DFHXCPRH issues an MVS abend with abend code 0408 which invokes its ESTAE routine to clear up its environment. A SYSMDUMP is taken before returning control to the application. An application using the EXCI CALL API receives RESPONSE(SYSTEM_ERROR) REASON(WS_GETMAIN_ERROR) in its return area. The subreason1 field of the return area contains the R15 return code from MVS indicating why the GETMAIN failed. An application using the EXCI EXEC API receives RESP(LINKERR) RESP2(601).

User response:

Use the MVS R15 return code obtained from the application or from the dump to determine why the MVS GETMAIN request failed. If the reason is insufficient storage, increase the region size of the batch application.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter does not produce any formatted output for the job because the error occurred too early in EXCI initialization for there to be any control blocks.

Modules:

DFHXCPRH

0409
Explanation:

The external CICS interface module DFHXCPRH issued an MVS GETMAIN request for storage required for its SSI VERIFY request, but a nonzero return code was returned from MVS.

System action:

Module DFHXCPRH issues an MVS abend with abend code 0409 which invokes its ESTAE routine to clear up its environment. A SYSMDUMP is taken before returning control to the application. An application using the EXCI CALL API receives RESPONSE(SYSTEM_ERROR) REASON(VERIFY_BLOCK_GM_ERROR) in its return area. The subreason1 field of the return area contains the R15 return code from MVS indicating why the GETMAIN failed. An application using the EXCI EXEC API receives RESP(LINKERR) RESP2(605).

User response:

Use the MVS R15 return code obtained from the application or from the dump to determine why the MVS GETMAIN request failed. If the reason is insufficient storage, increase the region size of the batch application.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter does not produce any formatted output for the job because the error occurred too early in EXCI initialization for there to be any control blocks.

Modules:

DFHXCPRH

0410
Explanation:

The external CICS interface module DFHXCPRH issued an MVS GETMAIN request for an XCUSER block but a nonzero return code was returned from MVS.

System action:

Module DFHXCPRH issues an MVS abend with abend code 0410 which invokes its ESTAE routine to clear up its environment. A SYSMDUMP is taken before returning control to the application. An application using the EXCI CALL API receives RESPONSE(SYSTEM_ERROR) REASON(XCUSER_GETMAIN_ERROR) in its return area. The subreason1 field of the return area contains the R15 return code from MVS indicating why the GETMAIN failed. An application using the EXCI EXEC API receives RESP(LINKERR) RESP2(603).

User response:

Use the MVS R15 return code obtained from the application or from the dump to determine why the MVS GETMAIN request failed. If the reason is insufficient storage, increase the region size of the batch application.

Modules:

DFHXCPRH

0411
Explanation:

The external CICS interface dump module DFHXCDMP was attempting to call the CICS SVC in order for an MVS SDUMP to be taken to capture an earlier problem. DFHXCDMP was unable to call the SVC as no SVC number was available. DFHXCDMP issued an 0411 abend in order that the callers ESTAE routine is invoked which takes a SYSMDUMP instead.

System action:

A SYSMDUMP is taken instead of an SDUMP for an earlier reported problem.

User response:

Use the SYSMDUMP produced to diagnose the earlier reported problem.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter does not produce any formatted output for the job because the error occurred too early in EXCI initialization for there to be any control blocks.

Modules:

DFHXCDMP

0412
Explanation:

The external CICS interface dump module DFHXCEIP was processing an EXCI EXEC API request and detected that the EXEC parameter list passed to it contained a function that is not supported by the external CICS interface.

System action:

The application is abnormally terminated with a dump.

User response:

This error indicates the parameter list being passed to the EXCI has not been generated by the CICS translator. The translator should always be used. Correct the application to specify the correct EXCI EXEC API command.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter may not produce any formatted output for the job if this was the first EXCI request for this TCB.

Modules:

DFHXCEIP

0413
Explanation:

The external CICS interface dump module DFHXCEIP was processing an EXCI EXEC API request and detected that the EXEC parameter list passed to it did not require the mandatory RETCODE parameter in which return codes are returned to the application.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter may not produce any formatted output for the job if this was the first EXCI request for this TCB.

System action:

The application is abnormally terminated with a dump.

User response:

This error indicates the parameter list being passed to the EXCI has not been generated by the CICS translator. The translator should always be used. Correct the application to specify RETCODE.

Modules:

DFHXCEIP

0414
Explanation:

The external CICS interface module DFHXCEIP issued an MVS ESTAE macro to establish a recovery environment but a nonzero return code was returned from MVS.

System action:

The application terminates abnormally with a dump.

User response:

Examine the dump and any associated MVS messages to determine why the MVS ESTAE request failed.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter may not produce any formatted output for the job if this was the first EXCI request for this TCB.

Modules:

DFHXCEIP

0415
Explanation:

The external CICS interface module DFHXCEIP detected an error early in EXCI initialization before EXCI dump services were available. DFHXCEIP issues abend 0415 so that its ESTAE routine is invoked from where an SYSMDUMP is taken instead to capture the error.

System action:

The application terminates abnormally with a dump.

User response:

Examine the SYSMDUMP to determine the cause of the earlier reported error.

An attempt to format the SYSMDUMP produced with the CICS IPCS dump formatter does not produce any formatted output for the job because the error occurred too early in EXCI initialization for there to be any control blocks.

Modules:

DFHXCEIP

End of change [[ Contents Previous Page | Next Page Index ]]