Abend codes AXxx

AXFA
Explanation:

The key length for a file control request that is to be sent to a remote system has to be obtained from the file control table, and has proved to be zero.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Ensure that the key length has been defined either in the remote file definition that is being used, or as a length option from the application program that is using it.

Modules:

DFHXFP

AXFB
Explanation:

An unacceptable function management header (FMH) type has been found. It must be type 05, type 06, or type 43.

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:

DFHXFP

AXFC
Explanation:

The request passed to the data transformation program is unknown to CICS. This abend can also occur in an MRO/IRC system as a result of an invalid EXEC CICS START request issued from the user’s node error program (DFHZNEP).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the CICS Customization Guide for restrictions on the use of EXEC CICS commands from within an NEP. If this is not the cause of the abend, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHXFP

AXFD
Explanation:

The request that is passed to the data transformation program cannot be sent to a remote system; for example, a storage control request.

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:

DFHXFP

AXFE
Explanation:

The transformation requested does not exist; for example, a DL/I schedule reply is not recognized by the outbound request processor in the data transformation program.

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:

DFHXFP

AXFF
Explanation:

An unacceptable queue organization has been found in a queue model function management header (FMH).

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:

DFHXFP

AXFG
Explanation:

An unacceptable argument number has been found in the data following a function management header (FMH) of type 43.

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:

DFHXFP

AXFH
Explanation:

The argument number in the data following a function management header (FMH) of type 43 is acceptable, however, the argument itself is not expected.

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:

DFHXFP

AXFI
Explanation:

The data length for a WRITEQ TD or READQ TD, which is determined from the destination control table, is zero. The abend can also occur when determining the length for file control requests from the file control table.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Notify the system programmer.

Modules:

DFHXFP

AXFJ
Explanation:

The error code held in UIBFCTR and UIBDLTR cannot be converted to an equivalent SNA error code.

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:

DFHXFP

AXFL
Explanation:

Transformers 2 and 4 expect to receive a function management header (FMH), possibly followed by user data. A null chain of data has been received.

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:

DFHXFP

AXFM
Explanation:

The ISCINVREQ condition has been raised. This can happen when the resource proves to be on yet another remote system, that is, when daisy-chaining is active.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check that daisy-chaining of requests is intended and that all relevant intersystem links are in service.

Modules:

DFHXFP

AXFO
Explanation:

The check on the DS and DBA parameters in an attach function management header (FMH) has failed. This abend represents a user error resulting from a mismatch in the system definitions for both ends of an intersystem link.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Notify the system programmer.

Modules:

DFHXFP

AXFP
Explanation:

CICS requires a second function management header (FMH) to follow an attach FMH. No second FMH was received.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Notify the system programmer.

Modules:

DFHXFP

AXFQ
Explanation:

Either the function management header (FMH) just received is too short or too long to be a valid FMH, or an expected FMH is not present.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check that the transaction profile parameter, INBFMH, is set to ALL. If communicating across a distributed program link, ensure that the requested function is supported on the partner system.

Modules:

DFHXFP

AXFR
Explanation:

The CICS command level interface imposes a maximum length of 32 767 for data. The length of the data just received exceeds this limit.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Notify the system programmer.

Modules:

DFHXFP

AXFS
Explanation:

A PSB has been scheduled successfully. However, the maximum possible length of an I/O area exceeded 65 535. This abend is likely to occur if path calls are used to retrieve large segments, and/or if FLS causes excessive expansion of segments.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Notify the system programmer.

Modules:

DFHXFP

AXFT
Explanation:

An estimate of the size of the output I/O area has been made, and it exceeds the maximum possible size of 65 535.

Note:
While the estimated size may exceed the actual size, the difference will only be a few bytes.

This abend is likely to occur if a database calls, inserts, or replaces multiple segments, and many qualified segment search arguments are specified.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Notify the system programmer.

Modules:

DFHXFP

AXFU
Explanation:

A two-level cursor is present in a function management header (FMH) relating to a linear (temporary storage) queue. However, these cursors are valid only for hierarchical queues that are not supported by CICS.

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:

DFHXFP

AXFW
Explanation:

An invalid length specification has been given in a CICS command-level request corresponding to one of the data variables.

The CICS-architected FMH is followed by zero or more self-describing data variables for each parameter specified.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check for an invalid or zero length specified in a CICS command-level request, or for data truncation in a user-written node error program (NEP).

Modules:

DFHXFP

AXFX
Explanation:

A function shipping request by an APPC link failed because

System action:

CICS terminates the task abnormally.

User response:

Check that the request was directed to the correct remote system, and that the remote system is set up to support full syncpoint protocols (synclevel 2).

Modules:

DFHXFP

AXFY
Explanation:

An APPC conversation failure has occurred when an attach between CICS systems was issued.

System action:

The task is abnormally terminated with a transaction dump.

User response:

Check the connection to the remote CICS system and try to reestablish it.

Modules:

DFHXFP

AXF0
Explanation:

A task has been purged due to lack of storage in a dynamic storage area (DSA).

System action:

The task is abnormally terminated with a transaction dump.

User response:

Try the transaction again later.

If the short-on-storage condition persists, consider increasing the size limit of the CICS DSAs. You can vary the DSAs dynamically using the DSALIM and EDSALIM parameters on the CEMT master terminal command.

Modules:

DFHXFP

AXF1
Explanation:

The storage manager module, DFHSMGF, has returned a condition not expected by DFHXFP.

System action:

The task is abnormally terminated with a transaction dump.

User response:

Look for any related CICS messages and abends to determine if there has been a prior failure in CICS storage.

Modules:

DFHXFP

AXF2
Explanation:

A task has been purged due to lack of storage in the DSA.

System action:

The task is abnormally terminated with a transaction dump.

User response:

Try the transaction again later.

If the short-on-storage condition persists, increase the size of the dynamic storage area using the DFHSIT DSA parameter.

Modules:

DFHXFP

AXF3
Explanation:

The storage manager module DFHSMMC has returned a condition not expected by DFHXFP.

System action:

The task is abnormally terminated with a transaction dump.

User response:

Look for any related CICS messages and abends to determine if there has been a prior failure in CICS storage.

Modules:

DFHXFP

AXF4
Explanation:

The task was purged before a GET_BUFFER request to the EXEC interface service routines module (DFHEISR), was able to complete successfully. The domain that first detected the purged condition provides an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate why the task was purged. It was purged either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHXFX

AXF5
Explanation:

An error (INVALID, DISASTER, or unexpected EXCEPTION response) has occurred on a call to the EXEC interface service routines module(DFHEISR). The domain that detected the original error provides an exception trace, a console message, and possibly, a system dump (depending on the options specified the dump table).

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the related message from the domain that detected the original error.

Modules:

DFHXFX

AXF8
Explanation:

A keyword such as TOKEN, CONSISTENT, REPEATABLE, UNCOMMITTED, or NOSUSPEND has been specified on a file control command for shipping to a system which does not support these functions.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Ensure that CICS in the file-owning region is at the correct level.

Modules:

DFHXFX

AXGA
Explanation:

Program DFHAPCR has returned an unexpected response. DFHAPCR performs the following functions:-

DFHAPCR has either detected an error in inbound data or has received an unexpected response whilst extracting or recreating channel data.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Look for any related CICS messages and abends to determine if there has been a prior failure in Program Manager, which manages containers. Look for exception trace entries from Program Manager or DFHAPCR to determine the cause of the error.

Modules:

DFHXFX,DFHXFP

AXMA
Explanation:

An error has occurred obtaining a lock within the transaction manager domain.

System action:

The recovery routine of the module in control is invoked which issues message DFHXM0002 with a system dump. DFHXM0002 reports the module in control at the time of the error.

User response:

See the description of message DFHXM0002 for further guidance.

Modules:

DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD, DFHXMFD, DFHXMLD, DFHXMQD, DFHXMST, DFHXMTA, DFHXMXD, DFHXMXE

AXMB
Explanation:

An error has occurred releasing a lock within the transaction manager domain.

System action:

The recovery routine of the module in control is invoked. This routine issues message DFHXM0002 with a system dump. DFHXM0002 reports the module in control at the time of the error.

User response:

See the description of message DFHXM0002 for further guidance.

Modules:

DFHXMAT, DFHXMBD, DFHXMCL, DFHXMDD, DFHXMFD, DFHXMLD, DFHXMQD, DFHXMST, DFHXMTA, DFHXMXD, DFHXMXE

AXMC
Explanation:

An severe error has occurred allocating a unique transaction number to a new transaction.

System action:

The recovery routine of the module in control is invoked. This routine issues message DFHXM0002 with a system dump. DFHXM0002 reports the module in control at the time of the error.

User response:

See the description of message DFHXM0002 for further guidance.

Modules:

DFHXMAT, DFHXMXE

AXMD
Explanation:

An attempt has been made to run the CICS internal task CSXM as a user transaction.

System action:

CICS terminates the task with a transaction dump.

User response:

Investigate why the attempt was made to run CSXM as a user transaction.

Modules:

DFHXMAB

Start of change
AXMU
Explanation:

During transaction attach the userid that had been assigned to the transaction was found to be invalid.

System action:

CICS terminates the task with a transaction dump.

User response:

Determine how the invalid userid had been assigned to the transaction. It might have been output by a user-replaceable module.

Modules:

DFHXMAT

End of change
AXMY
Explanation:

During transaction attach an unexpected error occurred obtaining transaction class membership.

System action:

The transaction is no longer considered for class membership. It is then abnormally terminated with a CICS transaction dump.

User response:

Use the dump to determine why the transaction failed to obtain membership of its transaction class.

Modules:

DFHXMAT

AXMZ
Explanation:

A serious failure in another component has been detected by the transaction manager domain.

System action:

The task in control is abnormally terminated with a transaction dump. Further diagnostics should have been taken by the failing component.

User response:

Look for earlier messages identifying the source of the problem. Refer to the descriptions of these messages for further guidance.

Modules:

DFHXMTA

AXSA
Explanation:

The CICS security control task could not complete because a necessary step failed. The task has done some essential recovery operations and abnormally terminated itself with code AXSA.

System action:

CICS writes a transaction dump for the security control restart task.

CICS sends messages to the console, one to identify the error detected by the security control task, and, if the error occurred during initialization, one to say that security initialization or CEMT PERFORM SECURITY REBUILD has failed. A third message follows either to say that CICS has terminated abnormally with a dump, or to ask you to reply GO or CANCEL. Depending on the nature of the original error, you may see messages from some other system component (for example, an access method).

User response:

First, if CICS has requested a response, you must reply. If you reply ‘GO’, CICS continues processing, but without support for the external security manager. CICS security still operates. If you reply ‘CANCEL’, CICS terminates abnormally with a dump.

Use the messages and dumps to find out the cause of the failure.

Modules:

DFHXSMN

AXSC
Explanation:

The task was purged before a GETMAIN request to the storage manager (SM) domain was able to complete successfully. The task that first detected the purged condition will have provided an exception trace.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate why the task was purged. It was purged either as a result of a purge from the master terminal operator via the CEMT transaction, or by the task being timed out after waiting for longer than the DTIMOUT (deadlock timeout) value specified for the transaction.

If the master terminal operator purged the task, this may have been in an attempt to clear the system which appeared to be deadlocked for some reason.

If the task was timed out automatically as a result of the DTIMOUT value being exceeded, this may be due to insufficient main storage being available for the number of tasks in the system. If the amount of main storage cannot be increased, reduce the number of tasks in the system to avoid short-on-storage situations. Another possibility is to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHXSMN

AXSD
Explanation:

An error (INVALID, DISASTER, or unexpected EXCEPTION response) has occurred on a call to the storage manager (SM) domain. 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:

The task is abnormally terminated with a CICS transaction dump.

User response:

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

Modules:

DFHTCRP

AXTA
Explanation:

The calculation of the length of data to be shipped has failed.

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:

DFHXTP

AXTB
Explanation:

An attempt to obtain a TIOA to ship data has failed.

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:

DFHXTP

AXTC
Explanation:

An attempt to transform data ready for shipment has failed.

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:

DFHXTP

AXTD
Explanation:

No TIOA received message was received from a remote system.

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:

DFHXTP

AXTE
Explanation:

Incorrect data was received from a remote system. The data was not long enough.

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:

DFHXTP

AXTF
Explanation:

No relay process function management header (FMH) was received from the remote system.

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:

DFHXTP

AXTG
Explanation:

Transformation of data received from remote system failed.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check that the reason for failure of the transformation process was not incorrect definition of the remote terminal. In particular check that the user area length specified for the terminal is the same in both local and remote systems. If the terminal definitions are correct, you need further assistance to resolve this problem. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHXTP

AXTH
Explanation:

An attempt to locate terminal identifier failed.

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:

DFHXTP

AXTI
Explanation:

The major request byte LUCOPN0 of the DFHLUC parameter list specified to the transaction-routing transformer is invalid, or corresponds to a request that is not shipped to a remote system. The parameter list will be found in the dynamic storage of XTP’s caller and may be located using the output from auxiliary trace.

System action:

The task is abnormally terminated with a 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:

DFHXTP

AXTJ
Explanation:

An unexpected combination of bit settings in the fields XTSSTAT and XTSTCOPC in the parameter list of the transaction-routing transformer was made.

System action:

The task is abnormally terminated with a 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:

DFHXTP

AXTK
Explanation:

An APPC conversation failure occurred when an attach between CICS systems was issued.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check the connection to the remote CICS system and try to reestablish it.

Modules:

DFHXTP

AXTL
Explanation:

The processing of APPC mapped data requires the generation of an APPC attach FMH with default values. In particular, the sync level requested is defaulted to 2. However, the session that is to be used has been bound with a sync level of 1.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check that:

Modules:

DFHXTP

AXTM
Explanation:

An attempt has been made to route a message-protected transaction over an APPC link bound at sync level 1. The attempt has failed because such transactions can be routed only over an APPC link that has been bound at sync level 2.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

If the transaction is to be routed to CICS OS/2 (which is bound at synclevel 1), remove the message protection option. If the transaction is to be routed to another host system and message protection is required, the link must be redefined so that it can be bound at synclevel 2.

Modules:

DFHXTP

AXTN
Explanation:

Module DFHXTP detected that the application buffer chained off a TCTTE at offset TCTERCSA has a corrupted header. This is caused either by a CICS logic error or by a storage overwrite.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

This is a CICS internal logic error. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHETL

AXTO
Explanation:

An exception response has been returned to the DFHXTP module from the CICS security manager. Prior to the call to the CICS security manager, the DFHXTP module detected that a shipped terminal definition had preset security. DFHXTP then invoked the CICS security manager in order to perform a preset security signon for the userid sent with the shipped terminal information. It is this preset security signon attempt which failed.

System action:

The transaction routing request is terminated and a message is sent to the terminal owning region (TOR) to indicate that the transaction routing request has failed. The CICS security manager issues a DFHSNxxxx message to the transient data queue, CSCS.

User response:

The most likely cause of this abend is that the terminal being shipped to the application owning region (AOR) has preset security with a userid which is not valid in the AOR. To confirm this, check the associated DFHSNxxxx message on the CSCS transient data queue in the AOR which gives the precise reason for the failure of the preset security signon request. This could be the result of an unauthorized transaction routing request.

Modules:

DFHXTP

AXTP
Explanation:

An exception response has been returned to the DFHXTP module from DFHCCNV FUNCTION(CONVERT_DS3270_FOR_SBCS). The module was called for a CICS client virtual terminal which requested conversion from ASCII to EBCDIC for data coming from the client. However, the conversion failed.

System action:

The transaction routing request is terminated and a message is sent to the terminal owning region (TOR) to indicate that the transaction routing request has failed. The CICS security manager issues a DFHSNnnnn message to the transient data queue, CSCS.

User response:

Examine the response and reason returned in the DFHCCNV commarea DFHC32. The client and server codepages will have already been validated so this may be a CICS error. You may need to contact IBM for further assistance. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHXTP

AXTQ
Explanation:

An exception response has been returned to the DFHXTP module from DFHCCNV FUNCTION(CONVERT_DS3270_FOR_SBCS). The module was called for a CICS client virtual terminal which requested conversion from EBCDIC to ASCII for data to be sent to the client. However the conversion failed.

System action:

The transaction routing request is terminated and a message is sent to the terminal owning region (TOR) to indicate that the transaction routing request has failed. The CICS security manager issues a DFHSNnnnn message to the transient data queue, CSCS.

User response:

Examine the response and reason returned in the DFHCCNV commarea DFHC32. The client and server codepages will have already been validated so this may be a CICS error. You may need to contact IBM for further assistance. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHXTP

AXTR
Explanation:

An exception response has been returned to the DFHXTP module from DFHPGLE FUNCTION(LOAD_EXEC) whilst trying to load EXEC program DFHCCNV.

System action:

The transaction routing request is terminated and a message is sent to the terminal owning region (TOR) to indicate that the transaction routing request has failed. The CICS security manager issues a DFHSNnnnn message to the transient data queue, CSCS.

User response:

Examine the response and reason returned from DFHPGLE to determine why CICS was unable to call DFHCCNV.

Modules:

DFHXTP

AXTS
Explanation:

One of the following conditions has occured.

System action:

The transaction routing request is terminated and a message is sent to the terminal owning region (TOR) to indicate that the transaction routing request has failed.

User response:

If channels are passed between transactions in a pseudo-conversation, you must ensure that all TOR and AOR systems involved in passing the channel are at a high enough CICS level to support channels.

Modules:

DFHXTP

AXTU
Explanation:

Program DFHAPCR has returned an unexpected response. DFHAPCR performs the following functions:-

DFHAPCR has either detected an error in inbound data or has received an unexpected response whilst extracting or recreating channel data.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Look for any related CICS messages and abends to determine if there has been a prior failure in Program Manager, which manages containers. Look for exception trace entries from Program Manager or DFHAPCR to determine the cause of the error.

Modules:

DFHXTP

[[ Contents Previous Page | Next Page Index ]]