Abend codes ARxx

ARCB
Explanation:

CICS has attempted to enable a task-related user exit, or a global user exit during initialization, but failed because the exit program could not be found.

On all types of start, CICS attempts to enable DFHEDP, the EXEC DLI task-related user exit. On an emergency restart, CICS enables transaction backout exit programs as specified by the first two TBEXITS system initialization parameters.

On all types of start, CICS attempts to enable file control backout programs as specified by the third, fourth, fifth and sixth TBEXITS system initialization parameters.

System action:

CICS issues a message to the console indicating which exit program is involved. CICS initialization then terminates abnormally with a system dump.

User response:

If the associated message indicates that program DFHEDP could not be found, check that IBM-supplied group DFHEDP is included in the group list used at CICS cold or initial start time.

For transaction backout exit programs, including the file control backout programs, ensure the program has been defined and is in a library available to CICS.

If necessary, use the dump to find out why the exit program could not be enabled.

Modules:

DFHRCEX

ARHA
Explanation:

The SAA resource recovery interface has been invoked with an invalid first parameter. The first parameter should be the code of the function to be performed. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

A level 2 trace for ‘CP’ of the transaction shows the course of events before this error occurred (such as the modules called and their parameters) plus details of the error itself. You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPIR

ARHB
Explanation:

The SAA resource recovery interface has been invoked with an invalid number of parameters for the call.

System action:

the transaction is abnormally terminated with a CICS transaction dump.

User response:

The exception trace point produced with this abend contains the SAA resource recovery verb name that was issued incorrectly. Use this to determine where the application program was in error and amend application program accordingly. The SAA Resource Recovery Reference Manual, SC31-6821, provides a detailed description of the SAA resource recovery verbs and how they should be called.

Modules:

DFHCPIR

ARHC
Explanation:

The SAA resource recovery interface has detected an unexpected return code from the syncpoint program. This is a CICS internal logic error.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

A level 2 trace for ‘CP’ of the transaction shows the course of events before this error occurred (such as the modules called and their parameters) plus details of the error itself. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCPIR

ARM0
Explanation:

An attempt was made to attach a transaction specifying DFHRMXN3 as the program to be given control, but the transaction was not internally attached by CICS.

DFHRMXN3 is for use by CICS system transaction CSKP. This provides support for activity keypoints,

System action:

The transaction is abnormally terminated. CICS processing continues.

User response:

Establish why an attempt was made to attach CSKP incorrectly, or why a transaction definition specified DFHRMXN3 as the program to be given control.

Modules:

DFHRMXN3

ARPA
Explanation:

An unexpected response from DFHSUSN has occurred when trying to sign off a user of the CRTE transaction in the target system when processing a CANCEL request.

This abend can be caused by incorrect use of the VTAM VARY INACT command. Otherwise it indicates that there may be an error in CICS.

System action:

The CSSF transaction (CRTE cancel processor transaction) is terminated with an ARPA abend.

User response:

Ensure that the VTAM VARY inact command is used correctly. If this is not the cause of the abend, you need further assistance from IBM to correct this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHRTC

ARPF
Explanation:

The alias could not be initialized.

System action:

One of the following messages is issued: DFHRP0103, DFHRP0104, DFHRP0106, DFHRP0108, DFHRP0109.

User response:

See the user response for the message.

Modules:

DFHRPAS

ARPG
Explanation:

The alias was not able to link to the CICS program or the Encode function of the converter one of the following reasons:

System action:

One of the following messages is issued: DFHRP0121, DFHRP0131, DFHRP0138, DFHRP0139, DFHRP0141, DFHRP0156, DFHRP0157, DFHRP0159.

User response:

See the user response for the message.

Modules:

DFHRPAS

ARPH
Explanation:

The alias detected a global work area error.

System action:

The following message is issued: DFHRP0118.

User response:

See the user response for the message.

Modules:

DFHRPAS

ARPI
Explanation:

The alias detected a logic error.

System action:

One of the following messages is issued: DFHRP0107, DFHRP0133, DFHRP0135, DFHRP0137, DFHRP0143, DFHRP0144, DFHRP0148, DFHRP0149, DFHRP0155, DFHRP0164, DFHRP0168, DFHRP0170.

User response:

See the user response for the message.

Modules:

DFHRPAS

ARPJ
Explanation:

The alias ends for one of the following reasons:

System action:

One of the following messages is issued: DFHRP0105, DFHRP0132, DFHRP0136, DFHRP0140, DFHRP0145, DFHRP0146, DFHRP0147, DFHRP0150, DFHRP0165, DFHRP0166, DFHRP0167.

User response:

See the user response for the message.

Modules:

DFHRPAS

ARPK
Explanation:

The alias detected a CICS logic error.

System action:

One of the following messages is issued: DFHRP0102, DFHRP0122, DFHRP0142, DFHRP0160.

User response:

See the user response for the message.

Modules:

DFHRPAS

ARPL
Explanation:

The alias detected an authorization error.

System action:

One of the following messages is issued: DFHRP0119, DFHRP0120, DFHRP0132, DFHRP0134.

User response:

See the user response for the message.

Modules:

DFHRPAS

ARPM
Explanation:

The alias detected an error in user code.

System action:

One of the following messages is issued: DFHRP0161, DFHRP0162, DFHRP0163, DFHRP0169.

User response:

See the user response for the message.

Modules:

DFHRPAS

ARPN
Explanation:

The alias detected an error while trying to switch TCBs.

System action:

The following message is issued: DFHRP0151.

User response:

See the user response for the message.

Modules:

DFHRPAS

ARPO
Explanation:

The alias program detected an abend.

System action:

One of the following messages is issued: DFHRP0181, DFHRP0182, DFHRP0183.

User response:

See the user response for the message.

Modules:

DFHRPAS

ARPU
Explanation:

The connection manager could not access the CICS ONC RPC data set, and received an error response when it tried to send message DFHRP1512.

System action:

None.

User response:

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

Modules:

DFHRPC01

ARPV
Explanation:

The connection manager received an unexpected response from CICS following an EXEC CICS command.

System action:

One of the following messages is issued: DFHRP1540, DFHRP1651, DFHRP1954.

User response:

See the user response for the message.

Modules:

DFHRPC0E

ARPW
Explanation:

The connection manager received an unexpected response from CICS following an EXEC CICS command.

System action:

The following message is issued: DFHRP1969.

User response:

See the user response for the message.

Modules:

DFHRPC0E

ARPX
Explanation:

The connection manager was started against an invalid terminal.

System action:

The following message is issued: DFHRP1522.

User response:

See the user response for the message.

Modules:

DFHRPC01

ARPZ
Explanation:

The connection manager has insufficient authority.

System action:

The following message is issued: DFHRP1902.

User response:

See the user response for the message.

Modules:

DFHRPC0B

ARP2
Explanation:

The server controller detected an internal error during CICS ONC RPC enable processing.

System action:

One of the following messages is issued: DFHRP0508, DFHRP0509, DFHRP0528, DFHRP0529, DFHRP0590, DFHRP0591.

User response:

See the user response for the message.

Modules:

DFHRPMS

ARP4
Explanation:

The server controller has performed an exception disable because of an internal error.

System action:

One of the following messages is issued: DFHRP0503, DFHRP0559, DFHRP0697, DFHRP0726, DFHRP0728, DFHRP0730, DFHRP0741.

User response:

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

Modules:

DFHRPMS

ARP5
Explanation:

An invalid attempt was made to start the server controller.

System action:

The following message is issued: DFHRP0640.

User response:

See the user response for the message.

Modules:

DFHRPMS

ARP9
Explanation:

There was not enough storage for the connection manager.

System action:

None.

User response:

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

Modules:

DFHRPC01

ARTA
Explanation:

The task does not own a terminal as its principal facility.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Ensure that DFHRTE has not been specified as the program for a task other than CRTE. Ensure that CRTE has not been initiated by means other than terminal input.

Modules:

DFHRTE

ARTB
Explanation:

There is no input TIOA or the data length is zero.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Ensure that DFHRTE has not been specified as the program for a task other than CRTE. Ensure that CRTE has not been initiated by means other than terminal input.

Modules:

DFHRTE

ARTC
Explanation:

The link to the required system is not usable for an unknown reason.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

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

Modules:

DFHRTE

ARTD
Explanation:

An internal logic error has been detected.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

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

Modules:

DFHRTE

ARTE
Explanation:

An error was encountered when attempting to read from or write to temporary storage.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Determine the cause of the temporary storage problem and correct it.

Modules:

DFHRTE

ARTF
Explanation:

An attempt has been made to use the routing transaction (CRTE) from a terminal that has a permanent transaction code set.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Inform the system programmer.

Modules:

DFHRTE

ARTG
Explanation:

CICS could not find the profile specified for a transaction being routed.

System action:

CICS terminates the task abnormally with a dump.

User response:

Check your transaction and profile definitions.

Modules:

DFHRTE

ARTH
Explanation:

An error (INVALID, DISASTER or EXCEPTION response) has occurred on a call to schedule a remote terminal delete by DFHRTE during sign-off for a surrogate terminal session running CRTE. The domain that detected the original error provides an exception trace, a console message and, possibly, a system dump (depending on the options specified in the dump table).

System action:

CICS terminates the task abnormally with a dump.

User response:

See the related message produced by the domain that detected the original error.

Modules:

DFHRTE

Start of change
ARUA
Explanation:

An exception condition was returned on the ADD_LINK during the BIND phase of ATTACH for the transaction invoked by the RUN command.

System action:

CICS terminates the invoked transaction abnormally with a dump. The RUN SYNCHRONOUS command that was issued by the application returns with an error response of INVREQ (RESP2 28).

User response:

More details can be found in the trace.

Modules:

DFHXMRU

End of change
Start of change
ARUB
Explanation:

A RUN SYNCHRONOUS command caused an attempt to attach a transaction defined as remote. Only transactions defined as local may be run synchronously.

System action:

CICS terminates the invoked transaction abnormally with a dump. The RUN SYNCHRONOUS command that was issued by the application returns with an error response of ACTIVITYERR or PROCESSERR (RESP2 27).

User response:

More details can be found in the trace.

Modules:

DFHXMXM

End of change
Start of change
ARUC
Explanation:

A RUN SYNCHRONOUS command caused an attempt to attach a transaction with an invalid USERID.

System action:

CICS terminates the invoked transaction abnormally with a dump. The RUN SYNCHRONOUS command that was issued by the application returns with a resp2 value of 27.

User response:

More details can be found in the trace.

Modules:

DFHXMRU

End of change
Start of change
ARXA
Explanation:

A transactional EXCI request has been received from a batch region. CICS has encountered an error when attempting to express interest in an RRMS Unit of Recovery.

DFHRXUW provides an exception trace, console message DFHRX0002, and possibly a system dump (depending on the options in the dump table).

System action:

The transaction is terminated with a CICS transaction dump.

User response:

Resource Recovery Services (RRS) may have been shut down after the request was received by CICS. If this is the case, retry the EXCI request once RRS has been restarted.

If this is not the case, use the exception trace provided by the RX domain to determine the reason for the failure. You might need further assistance from IBM in this situation. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHRXUW

End of change
Start of change
ARXB
Explanation:

An error (EXCEPTION, DISASTER, INVALID, KERNERROR or PURGED) has occurred on an ADD_LINK call to the recovery manager (RM) domain. For errors other than EXCEPTION, the RM domain provides an exception trace, a console message, and possibly a system dump (depending on the options in the dump table).

For all errors, DFHRXUW provides an exception trace, console message DFHRX0002, and possibly a system dump (depending on the options in the dump table).

System action:

The transaction is terminated with a CICS transaction dump.

User response:

See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHRXUW

End of change
Start of change
ARXC
Explanation:

A transactional EXCI request has been received from a batch region when either:

System action:

The transaction is terminated with a CICS transaction dump.

User response:

If CICS was started with system initialization parameter RRMS=NO, restart CICS specifying RRMS=YES (or route transactional EXCI requests to another CICS system).

Otherwise, investigate why the RX domain did not initialize succesfully. A failure during initialization of the domain is accompanied by a console message and a system dump. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHRXUW

End of change
Start of changeARZEEnd of change
Start of change
Explanation:

A command has failed due to a serious failure in a CICS component (resource manager).

End of change
Start of change
System action:

The transaction is abnormally terminated with abend code ARZE. CICS takes a transaction dump, unless module DFHDUIO is not loaded.

End of change
Start of change
User response:

Use the transaction dump to determine the cause of the failure. For further assistance, or if module DFHDUIO is not loaded and no transaction dump is available, contact your system programmer.

End of change
Modules:

Start of changeDFHRZLN, DFHRZRM, DFHRZSO, DFHRZSO1, DFHRZTA, DFHRZXMEnd of change

Start of change
ARZF
Explanation:

A command has failed due to a serious failure in a CICS component (resource manager).

System action:

The transaction is abnormally terminated with abend code ARZF. CICS takes a transaction dump, unless module DFHDUIO is not loaded.

User response:

Use the transaction dump to determine the cause of the failure. For further assistance, or if module DFHDUIO is not loaded and no transaction dump is available, contact your system programmer.

Modules:

DFHRZLN, DFHRZRM, DFHRZSO, DFHRZSO1, DFHRZTA, DFHRZXM

End of change
Start of change
ARZI
Explanation:

A command has failed due to a serious failure in a CICS component (resource manager).

System action:

The transaction is abnormally terminated with abend code ARZI. CICS takes a transaction dump, unless module DFHDUIO is not loaded.

User response:

Use the transaction dump to determine the cause of the failure. For further assistance, or if module DFHDUIO is not loaded and no transaction dump is available, contact your system programmer.

Modules:

DFHRZLN, DFHRZRM, DFHRZSO, DFHRZSO1, DFHRZTA, DFHRZXM

End of change
Start of change
ARZJ
Explanation:

A command has failed due to a serious failure in a CICS component (resource manager).

System action:

The transaction is abnormally terminated with abend code ARZJ. CICS takes a transaction dump, unless module DFHDUIO is not loaded.

User response:

Use the transaction dump to determine the cause of the failure. For further assistance, or if module DFHDUIO is not loaded and no transaction dump is available, contact your system programmer.

Modules:

DFHRZLN, DFHRZRM, DFHRZSO, DFHRZSO1, DFHRZTA, DFHRZXM

End of changeStart of change
ARZ2
Explanation:

An attempt to service a GIOP request failed during task attach due to required resources being unobtainable, or missing information from request data.

System action:

The request fails and the task is abnormally terminated with abend code ARZ2. CICS takes a transaction dump, unless module DFHDUIO is not loaded.

User response:

Use the transaction dump to determine the cause of the failure. For further assistance, or if module DFHDUIO is not loaded and no transaction dump is available, contact your system programmer.

Modules:

DFHRZXM

End of change
Start of changeARZ3End of change
Start of change
Explanation:

An attempt to service a GIOP request failed during task attach due to required resources being unobtainable, or missing information from request data.

End of change
Start of change
System action:

The request fails and the task is abnormally terminated with abend code ARZ3. CICS takes a transaction dump, unless module DFHDUIO is not loaded.

End of change
Start of change
User response:

Use the transaction dump to determine the cause of the failure. For further assistance, or if module DFHDUIO is not loaded and no transaction dump is available, contact your system programmer.

End of change
Modules:

Start of changeDFHRZIX, DFHRZTCXEnd of change

Start of change
ARZ4
Explanation:

An attempt to service a GIOP request failed during task attach due to required resources being unobtainable, or missing information from request data.

System action:

The request fails and the task is abnormally terminated with abend code ARZ4. CICS takes a transaction dump, unless module DFHDUIO is not loaded.

User response:

Use the transaction dump to determine the cause of the failure. For further assistance, or if module DFHDUIO is not loaded and no transaction dump is available, contact your system programmer.

Modules:

DFHRZRM, DFHRZSO1

End of change
Start of change
ARZ5
Explanation:

The target request stream task detected that the source task was no longer active. The target task is unable to process the request it was attached for

System action:

The request fails and the task is abnormally terminated with abend code ARZ5. CICS takes a transaction dump, unless module DFHDUIO is not loaded.

User response:

Investigate why the source task has terminated before this target began initialization. There might be relevant messages in the CICS log. Otherwise a CICS trace or system dump will be required to identify the problem. One possible cause is that the source task was timed out and purged before the target task started.

Modules:

DFHRZRM

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