Abend codes ASxx

ASCA
Explanation:

A DFHSC TYPE=GETMAIN request has resulted in a call to the storage manager (SM) domain which has returned an INVALID or DISASTER response.

System action:

The transaction is terminated with a CICS transaction dump.

User response:

There has been an earlier failure which led to the response from the storage manager domain. Investigate the earlier failure (which is accompanied by a console message and a system dump).

Module(s):

DFHSMSCP

ASCB
Explanation:

A DFHSC TYPE=FREEMAIN request has resulted in a call to the storage manager (SM) domain which has returned an INVALID or DISASTER response.

System action:

The transaction is terminated with a CICS transaction dump.

User response:

There has been an earlier failure which led to the response from the storage manager domain. Investigate the earlier failure (which is accompanied by a console message and a system dump).

Modules:

DFHSMSCP

ASCP
Explanation:

A task which has issued an unconditional DFHSC TYPE=GETMAIN request has been purged while waiting for sufficient contiguous main storage to become free.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate why the task was purged. This will either have been 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 task was purged by the master terminal operator then 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 then 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 then the number of tasks in the system should be reduced to avoid short-on-storage situations. Another possibility would be to increase the value of the DTIMOUT option for the transaction.

Modules:

DFHSMSCP

ASCR
Explanation:

A DFHSC macro request has been issued with an invalid request type.

System action:

The transaction is terminated with a CICS transaction dump.

Detection of the invalid request by DFHSMSCP causes a console message and a system dump to be produced.

User response:

Use the associated console message and system dump to investigate the problem.

Modules:

DFHSMSCP

ASDA
Explanation:

The default shutdown transaction (CESD) has been started directly from a terminal. This is not permitted. This transaction can only be started internally by CICS.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

None.

Modules:

DFHCESD

ASFA
Explanation:

An internal logic error occurred in DFHSFP because of an unexpected response from EXEC CICS. This abend code is usually accompanied by message DFHCE3598 which contains the associated return codes.

System action:

The transaction 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:

DFHSFP

ASFB
Explanation:

An attempt was made to execute the CICS signoff program without an associated terminal.

System action:

CICS terminates the transaction with a dump. This abend code is usually accompanied by message DFHCE3598.

User response:

Only use the signoff program when there is a related terminal.

Modules:

DFHSFP

ASFC
Explanation:

An attempt was made to execute the CICS signoff program against an APPC session.

System action:

CICS terminates the transaction with a dump. This abend code is usually accompanied by message DFHCE3598.

User response:

Only use the signoff program when there is a related terminal.

Modules:

DFHSFP

Start of change
ASHA
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 ASHA. 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:

DFHSHDM

End of change
Start of change
ASHB
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 ASHB. 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:

DFHSHDM

End of change
Start of change
ASHR
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 ASHR. 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:

DFHSHRSP

End of change
Start of change
ASHU
Explanation:

In the process of transferring the request from one region to another an abend occurred due to a routing failure. The Request cannot be routed to a suitable region. The request is unserviceable.

System action:

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

User response:

Check the links between regions are available. Check the Distributed Routing Program name is correct and the program is usable. 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:

DFHSHRSP

End of change
Start of change
ASH2
Explanation:

An attempt to service a Scheduler Services request failed due to required resources being unobtainable. This may result in a request being unserviceable or an Activity being marked abended depending on the nature of the failure.

System action:

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

User response:

Check that any required links between regions are available. Check the Distributed Routing Program name is correct and the program is usable. 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:

DFHSHXM

End of change
Start of change
ASH3
Explanation:

A transaction bound to a Scheduler Services request has backed out. No other abend code has been set. The SH abend request uses this abend code by default.

System action:

The transaction continues backing out. A subsequent task will process the SH abend request.

User response:

None.

Modules:

DFHSHRM

End of change
Start of change
ASH4
Explanation:

A Scheduler Services request attempted to attach a transaction that is currently disabled.

System action:

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

User response:

Check the status of the transaction. For further assistance, or if module DFHDUIO is not loaded and no transaction dump is available, contact your system programmer.

Modules:

DFHSHXM

End of change
ASIA
Explanation:

An error has occurred on a call to the storage manager (SM) domain. The domain that detected the original error will have provided 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. CICS then terminates abnormally.

User response:

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

Modules:

DFHSII1

ASIB
Explanation:

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

System action:

CICS terminates the task with a transaction dump.

User response:

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

Modules:

DFHSIPLT

Start of change
ASJD
Explanation:

An attempt to load a DLL by SJ Domain has failed.

System action:

CICS terminates the task with a transaction dump.

User response:

See message DFHSJ0503 to determine the DLL name and the reason why the load failed.

Modules:

DFHSJCS

End of change
Start of change
ASJE
Explanation:

An attempt to locate the Wrapper class has failed.

System action:

CICS terminates the task with a transaction dump.

User response:

Verify the location and attributes of the CICS Wrapper class particularly the HFS permissions. If Java 2 security is active ensure the necessary permissions have been granted in the policy file. See message DFHSJ0501 for further information.

Modules:

DFHSJCS

End of change
Start of change
ASJF
Explanation:

An attempt to change the HFS working directory has failed.

System action:

CICS terminates the task with a transaction dump.

User response:

See message DFHSJ0502 to determine the directory name and the reason why the attempt failed.

Modules:

DFHSJCS

End of change
Start of change
ASJG
Explanation:

An attempt by SJ domain to fetch the user-replaceable module DFHJVMAT has failed.

System action:

CICS terminates the task with a transaction dump.

User response:

Verify that module DFHJVMAT is contained in a dataset referenced by ddname SDFHAUTH and that it is executable.

Modules:

DFHSJIN

End of change
Start of change
ASJJ
Explanation:

A JVM was started which does not meet the minimum version requirements for this release of CICS.

System action:

CICS terminates the task with a transaction dump.

User response:

Update the version of Java specified in the JVM profile.

Modules:

DFHSJIN

End of change
Start of change
ASJ1
Explanation:

CICS attempted to initialize the Java environment for a task by issuing a JNI_CreateJavaVM call to the Java Native Interface. The call was not successful.

System action:

Exception trace SJ 050C is created. The task is abnormally terminated with a CICS transaction dump.

User response:

This abend usually implies that there is an error in the JVM Profile. Check that the LIBPATH and JAVA_HOME entries in the JVM Profile are correct. Also check that the CICS_DIRECTORY has been set correctly.

Ensure that CICS is using the correct JVM Profile and that the correct version of Java is being used. Check that the CICS region id has read permission to the Java HFS files and that you have the latest Java maintenance applied.

Examine the HFS files used for stdout and stderr (as named by the environment variables STDOUT and STDERR, whose default names are dfhjvmout and dfhjvmerr) for error messages output by the JVM. Also examine destination CEEMSG for error messages output by Language Environment and the Java Native Interface (JNI). The trace table from the transaction dump contains the exception trace mentioned above.

If the suggestions above do not help you should ensure that the JVM has not abended. To do this look in the WORK_DIR directory specified in the JVM Profile for any JAVADUMP files.

Modules:

DFHSJCS

End of change
Start of change
ASJ3
Explanation:

The CICS JVM interface invoked the JVM to find the main method of the CICS Wrapper class used to set up the operating environment before executing the user Java class. The JVM failed to find the main method of the CICS Wrapper class.

System action:

DFHSJCS provides an exception trace, console message DFHSJ0002, and possibly a system dump (depending on the options in the dump table). The task is abnormally terminated with a CICS transaction dump.

User response:

Examine the HFS files used for stdout and stderr (as named by the environment variables STDOUT and STDERR, whose default names are dfhjvmout and dfhjvmerr) for error messages output by the JVM. Also examine destination CEEMSG for error messages output by Language Environment and the Java Native Interface (JNI).

Ensure that the CICS_DIRECTORY entry in the JVM Profile is correct and that the CICS region id has permission to read the CICS_DIRECTORY HFS structure.

Modules:

DFHSJCS

End of change
Start of change
ASJ4
Explanation:

The SJ domain failed to build the argument list required to invoke the CICS Wrapper class used to set up the operating environment before executing the user Java class. This is possibly due to lack of free storage.

System action:

DFHSJCS provides an exception trace, console message DFHSJ0002, and possibly a system dump (depending on the options in the dump table). The task is abnormally terminated with a CICS transaction dump.

User response:

Examine the HFS files used for stdout and stderr (as named by the environment variables STDOUT and STDERR, whose default names are dfhjvmout and dfhjvmerr) for error messages output by the JVM. Also examine destination CEEMSG for error messages output by Language Environment and the Java Native Interface (JNI).

Modules:

DFHSJCS

End of change
Start of change
ASJ5
Explanation:

The CICS JVM interface invoked the CICS Wrapper class used to set up the operating environment before executing the user Java class. The Wrapper returned an exception.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Examine the HFS files used for stdout and stderr (as named by the environment variables STDOUT and STDERR, whose default names are dfhjvmout and dfhjvmerr) for error messages output by the JVM. Also examine destination CEEMSG for error messages output by Language Environment and the Java Native Interface (JNI).

Modules:

DFHSJCS

End of change
Start of change
ASJ6
Explanation:

The SJ domain issued a call to the kernel to ensure that CICS's ESTAE is the current ESTAE. This is required before calling CICS services from a native C environment which is running with Language Environment's ESTAE in effect. The call failed.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Examine the CICS Kernel or MVS messages and diagnostics that should be present as a result of the failure.

Modules:

DFHSJCS

End of change
ASNA
Explanation:

An internal logic error occurred in DFHSNP because of an unexpected response from EXEC CICS.

System action:

CICS terminates the transaction with a dump. This abend code is usually accompanied by message DFHCE3548.

User response:

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

Modules:

DFHSNP

ASNB
Explanation:

An attempt was made execute the CICS sign on program without an associated terminal. This abend code is usually accompanied by message DFHCE3548.

System action:

CICS terminates the transaction with a dump.

User response:

Only use the sign on program when there is a related terminal.

Modules:

DFHSNP

ASNC
Explanation:

The signon program attempted to send a request to the user but failed to do so.

System action:

CICS terminates the transaction with a dump. This abend code is usually accompanied by message DFHCE3548.

User response:

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

Modules:

DFHSNP

Start of change
ASND
Explanation:

A request from DFHSNTU to ENQ on the address of the SNEX has failed during signoff terminal user.

System action:

A transaction dump is taken and the task which issued the signoff is abended.

User response:

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

Modules:

DFHSNTU

End of change
Start of change
ASOA
Explanation:

The TCP/IP listener task CSOL has been incorrectly started from a terminal. It can only be enabled by the Sockets Domain at CICS system initialization or by using CEMT SET TCPIP OPEN or the equivalent SPI function.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

None.

Modules:

DFHSOL

End of change
Start of change
ASOB
Explanation:

The TCP/IP listener task CSOL has encountered a locking error while attempting to issue a lock.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

The exception trace prior to this abend gives more information as to why this abend was issued.

Modules:

DFHSOL

End of change
Start of change
ASOC
Explanation:

The TCP/IP listener task CSOL has encountered an unlocking error while attempting to issue an unlock.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

The exception trace prior to this abend gives more information as to why this abend was issued.

Modules:

DFHSOL

End of change
Start of change
ASOD
Explanation:

The TCP/IP transaction attach module DFHSOXM encountered an error during the bind stage of transaction attach processing for a new task.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

The exception trace prior to this abend gives more information as to why this abend was issued.

Modules:

DFHSOXM

End of change
Start of change
ASOL
Explanation:

The TCP/IP listener task CSOL has abended.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Investigate why the transaction was abended. The exception trace prior to this abend gives more information as to why this abend was issued.

Modules:

DFHSOL

End of change
ASPA
Explanation:

The task was purged before a request to recovery manager (RM) domain 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. If processing is at a point where data integrity might not be maintained, CICS is abnormally terminated.

User response:

Investigate why the task was purged. This is 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.

If CICS is abnormally terminated, it should be emergency restarted to ensure that data integrity is maintained.

Modules:

DFHAPAC

ASPB
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the recovery manager (RM) domain. The domain that detected the original error will have provided 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. If processing is at a point where data integrity might not be maintained, CICS is abnormally terminated.

User response:

See the related message from the domain that detected the original error. If CICS was abnormally terminated, it should be emergency restarted to ensure that data integrity is maintained.

Modules:

DFHAPAC

ASPC
Explanation:

An error (INVALID or DISASTER) has occurred on a call to the bridge syncpoint routine (DFHBRSP). The domain that detected the original error will have provided an exception trace, 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 from the domain that detected the original error.

Modules:

DFHSPP

Start of change
ASPD
Explanation:

The transaction requested syncpoint via EXEC CICS SYNCPOINT, or rollback via EXEC CICS SYNCPOINT ROLLBACK, but this is not allowed in a transaction that is associated with an OTS transaction.

System action:

CICS terminates the transaction abnormally. EXEC CICS HANDLE ABEND command cannot handle this abend.

User response:

The error indicates an invalid attempt to syncpoint the transaction.

If DB2 is being accessed in the transaction, check that the DB2ENTRY or DB2CONN pool definition used by the transaction does not specify DROLLBACK(YES).

Modules:

DFHEISP

End of change
ASPF
Explanation:

CICS issued an internal syncpoint request resulting in a syncpoint with an intersystem session which has returned ROLLEDBACK to recovery manager (RM) domain. As a result, the transaction is abnormally terminated because the unit of work which was being syncpointed has been backed out.

This could result from shutting down IRC or from the failure of a connected CICS region.

System action:

The transaction is abnormally terminated. Recoverable resources updated by the unit of work are backed out and locks released. The EXEC CICS HANDLE ABEND command cannot handle this abend.

Message DFHAC2215 is sent to the terminal end user if possible, and message DFHAC2245 is sent to transient data destination CSMT.

User response:

Determine why the remote intersystem session returned a ROLLEDBACK response to the syncpoint request. Once this has been corrected retry the transaction.

To avoid ASPF abends in future, ensure that no in-flight units of work exist before shutting down IRC.

Modules:

DFHAPAC

ASPI
Explanation:

During CICS synchronization level 1 (synclevel 1) commit, an unexpected FMH or no data has been received from the partner system. Local resources and synclevel 2 partners have been committed, but synclevel 1 function-shipped resource updates may have been backed out.

System action:

The transaction does not abend. CICS synclevel 1 commit processing continues, with the aim of committing as many synclevel 1 resources as possible.

User response:

Examine the transaction dump to determine why the FMH was invalid or missing, It is likely that the error is in the remote system.

See the CICS Family: Communicating from CICS on System/390® for more information about syncpointing.

Modules:

DFHCR2U

ASPJ
Explanation:

During CICS synchronization level 1 (synclevel 1) commit, unexpected syncpoint message data has been received from the partner system. Local resources and synclevel 2 partners have been committed, but synclevel 1 function-shipped resource updates may have been backed out.

System action:

The transaction does not abend. CICS synclevel 1 commit processing continues, with the aim of committing as many synclevel 1 resources as possible.

User response:

Examine the transaction dump to determine why the message data was invalid. It is likely that the error is in the remote system.

See the CICS Family: Communicating from CICS on System/390 for more information about syncpointing.

Modules:

DFHCR2U

ASPN
Explanation:

A transaction has issued an EXEC CICS RETURN in backout required program state. The backout required program state is set when an application receives or issues an abend, or receives a backout request on a protected conversation.

System action:

The transaction is abnormally terminated. Recoverable resources updated by the unit of work are backed out and locks released. The EXEC CICS HANDLE ABEND command cannot handle this abend.

Message DFHAC2216 is sent to the terminal end user if possible, and message DFHAC2246 is sent to transient data destination CSMT.

User response:

To avoid the transaction abend, the application should code an EXEC CICS SYNCPOINT command before the EXEC CICS RETURN. A syncpoint issued in 'backout required' program state results in a backout being performed, and the ROLLEDBACK condition returned on the EXEC CICS SYNCPOINT command. If this condition is then handled, a subsequent EXEC CICS RETURN will complete successfully. For LU61 conversations the application should issue an EXEC CICS FREE followed by an EXEC CICS SYNCPOINT ROLLBACK, in order to avoid a subsequent ASP8 abend.

Modules:

DFHAPAC

ASPO
Explanation:

An intersystem session failed while a syncpoint was being taken. The intersystem session that failed was the link to the coordinator system. The failure occurred during the indoubt period of syncpoint processing. As a result this CICS system is in doubt as to the outcome of the unit of work for the transaction.

The unit of work is not shunted to await the return of the coordinator system, but is instead unilaterally committed. The unit of work is not shunted for one of the following reasons:

The unit of work is committed, rather than backed out, because the transaction definition specifies ACTION(COMMIT).

The fact that the unit of work is committed is remembered by the recovery manager (RM) domain until the unit of work is resynchronized with the coordinator system. At this time, according to whether the coordinator system committed or backed out, the recovery manager domain issues resynchronization messages reporting whether or not the resolution of the unit of work in the subordinate system was consistent with the coordinator system.

System action:

The transaction is abnormally terminated. Recoverable resources updated by the unit of work are committed and locks released. The EXEC CICS HANDLE ABEND command cannot handle this abend.

Message DFHAC2202 is sent to the terminal end user if possible, and message DFHAC2232 is sent to transient data destination CSMT.

User response:

Any updates performed by the unit of work are committed. There is a danger that recoverable resources will be inconsistent with the coordinator system if the coordinator system has backed out. If the reason for the failure is the first of those listed above and if you wish CICS to ensure that data integrity is maintained, change the indoubt transaction definition to specify WAIT(YES) so that CICS automatically handles indoubt failures and resynchronizes the unit of work when the link to the coordinator system is reestablished.

Modules:

DFHAPAC

ASPP
Explanation:

An intersystem session failed while a syncpoint was being taken. The intersystem session that failed was the link to the coordinator system, and the failure occurred during the critical indoubt period of syncpoint processing. As a result this CICS system is in doubt as to the outcome of the unit of work for the transaction.

The unit of work is not shunted to await the return of the coordinator system. Instead it is unilaterally backed out. The unit of work is not shunted for one of the following reasons:

The unit of work is backed out, rather than committed, because the transaction definition specifies ACTION(BACKOUT).

The fact that the unit of work is backed out is remembered by recovery manager (RM) domain until the unit of work is resynchronized with the coordinator system. At this time, according to whether the coordinator system backed out or committed, the recovery manager domain issues resynchronization messages reporting whether or not the resolution of the unit of work in the subordinate system was consistent with the coordinator system.

System action:

The transaction is abnormally terminated. Recoverable resources updated by the unit of work are backed out and locks released. The EXEC CICS HANDLE ABEND command cannot handle this abend.

Message DFHAC2203 is sent to the terminal end user if possible, and message DFHAC2233 is sent to transient data destination CSMT.

User response:

Any updates performed by the unit of work are backed out. There is a danger that recoverable resources will be inconsistent with the coordinator system if the coordinator system has committed. If the reason for the failure is the first of those listed above and if you wish CICS to ensure that data integrity is maintained, change the indoubt transaction definition to specify WAIT(YES) so that CICS automatically handles indoubt failures and resynchronizes the unit of work when the link to the coordinator system is reestablished.

Modules:

DFHAPAC

ASPQ
Explanation:

During phase 2 of the two phase syncpoint protocol an error occurred while communicating with a remote system. The error occurred after the recoverable resources were committed or backed out, so data integrity is not in danger.

System action:

The transaction is abnormally terminated. Recoverable resources updated by the unit of work will have backed out or committed depending on the decision taken by the recovery manager (RM) domain, which was not influenced by this later problem. The EXEC CICS HANDLE ABEND command cannot handle this abend.

Message DFHAC2221 is sent to the terminal end user if possible, and message DFHAC2251 is sent to transient data destination CSMT.

User response:

Refer to earlier messages issued by the communication or remote resource management components of CICS to determine the cause of the intersystem communication problem.

Modules:

DFHAPAC

ASPR
Explanation:

Intersystem communication failed while a syncpoint was being taken. Communication with the coordinator system has been interrupted, and the failure occurred during the critical indoubt period of syncpoint processing. As a result this CICS system is in doubt as to the outcome of the unit of work for the transaction.

However, this CICS system has not updated any recoverable resources in the unit of work and hence does not require the unit of work to be shunted to await resynchronization of its resources later. The coordinator system commits or backs out its resources. No resources on this system need to be kept in step.

This error can occur with external resource managers connected to CICS via the resource manager interface (RMI) as well as CICS systems connected via LU 6.2, and MRO. If an external resource manager such as DB2 is the only recoverable resource updated in the transaction, the recovery manager (RM) domain can optimize the syncpoint protocol. In this instance, the external resource manager becomes the syncpoint coordinator. If the link to the external resource manager is lost during this time, CICS will be indoubt as to whether the external resource manager updates were committed or backed out.

System action:

The transaction is abnormally terminated. There are no recoverable resources affected in this CICS system. The EXEC CICS HANDLE ABEND command cannot handle this abend.

Message DFHAC2222 is sent to the terminal end user if possible, and message DFHAC2252 is sent to transient data destination CSMT.

User response:

Refer to messages on the remote system to determine if the remote resources were backed out or committed.

Modules:

DFHAPAC

ASP1
Explanation:

Intersystem communication failed while a syncpoint was being taken. Communication with the coordinator system has been interrupted, and the failure occurred during the critical indoubt period of syncpoint processing. As a result this CICS system is in doubt about the outcome of the unit of work for the transaction.

Start of changeAlternatively, a transaction may have timed out while waiting for Recoverable Resource Management Services (RRMS) to provide the outcome of the unit of work, or RRMS may have failed during the critical indoubt period.End of change

The transaction definition specifies WAIT(YES) as an indoubt attribute. Therefore the unit of work is not completed but is shunted and allowed to wait for resynchronization with the coordinator system. If the WAITTIME attribute is specified on the transaction definition, the unit of work waits for the specified time. If after that time the coordinator system has not resynchronized, a unilateral decision is made about the unit of work as specified by the ACTION keyword on the transaction definition. A WAITTIME of zero, the default, means an indefinite wait. The unit of work can also be forced to take a unilateral decision by means of a CEMT SET UOW command.

System action:

The transaction is abnormally terminated. The EXEC CICS HANDLE ABEND command cannot handle this abend.

The associated unit of work is shunted awaiting the return of the coordinator system. Recoverable resources updated by the unit of work remain locked. The locks are released when the unit of work is backed out or committed at resynchronization time, or when a unilateral decision is made by this system.

Message DFHAC2201 is sent to the terminal end user if possible, and message DFHAC2231 is sent to transient data destination CSMT.

User response:

None. Any updates performed by the unit of work are resolved automatically when resynchronization with the coordinator system takes place.

Alternatively, the user can force resolution of the updates independently of the coordinator system by making a CEMT request to commit or back out the unit of work.

Modules:

DFHAPAC o*---------- ABCODE ASP2 ALTERED BY APAR PQ47569 ----------------

ASP2
Explanation:

A syncpoint has been attempted when an intersystem conversation is in a state in which the EXEC CICS SYNCPOINT command is not allowed. If CICS is connected to a system which must act as LAST AGENT, such as IMS, then this ABEND will be issued from SYNCPOINT processing if a PREPARE has been received on a link to another system. In order to support syncpointing CICS must act as COORDINATOR when it is directly connected to the LAST AGENT, the COORDINATOR system may send PREPARE syncpoint commands but never receives them.

System action:

The task is abnormally terminated with a CICS transaction dump which includes terminal control information. In particular, the dump contains state information for the links used by this transaction. The EXEC CICS HANDLE ABEND command cannot handle this abend.

User response:

Ensure that the application issues an EXEC CICS SYNCPOINT command only when its sync level 2 conversations are in the correct state. The EXEC CICS SYNCPOINT command may be issued only when each conversation is in one of the following states:

Modules:

DFHAPAC

ASP3
Explanation:

An application has requested syncpoint, either via EXEC CICS SYNCPOINT or implicitly via EXEC CICS RETURN. The coordinator of the syncpoint is not this CICS system but is remote. During the syncpoint protocol the remote coordinator has decided that the unit of work cannot be committed and must be backed out.

This error can occur with external resource managers connected to CICS via the resource manager interface (RMI) as well as CICS systems connected via LU 6.2, and MRO. If an external resource manager such as DB2 is the only recoverable resource updated in the transaction, the recovery manager (RM) domain can optimize the syncpoint protocol. In this instance, the external resource manager becomes the syncpoint coordinator. In this instance if the external resource manager returns with a backed out response, an ASP3 abend results.

System action:

The transaction is abnormally terminated and recoverable resources updated by the unit of work are backed out. The EXEC CICS HANDLE ABEND command cannot handle this abend.

Message DFHAC2220 is sent to the terminal end user if possible, and message DFHAC2250 is sent to transient data destination CSMT.

User response:

Refer to the remote coordinator system to determine why the unit of work was backed out.

Modules:

DFHAPAC

ASP7
Explanation:

A resource manager involved in syncpoint protocols has replied ‘No’ to a request to ‘Prepare’. The resource manager may be local to this CICS system, or may be a remote resource manager on another CICS system, or an external resource manager communicating through the resource manager interface (RMI).

System action:

CICS terminates the transaction abnormally. Recoverable resources updated by the unit of work are backed out. The EXEC CICS HANDLE ABEND command cannot handle this abend.

If it is a local resource manager that has voted no, message DFHAC2218 is sent to the terminal end user if possible, and message DFHAC2248 is sent to transient data destination CSMT.

If it is a remote resource manager that has voted no, message DFHAC2219 is sent to the terminal end user if possible, and message DFHAC2249 is sent to transient data destination CSMT.

User response:

This abend is caused by a prior problem. For example, the resource manager cannot flush its buffers because of an I/O error, or it cannot communicate with CICS because of a TP failure. Correct the earlier problem. Start of changeAn ASP7 can also occur during terminal or connection install if CICS is short on storage. For instance if message DFHAC2248 shows the transaction as CATA then look for earlier short on storage messages.End of change

Modules:

DFHAPAC

ASP8
Explanation:

The transaction requested syncpoint rollback, but was using a type of processing for which syncpoint rollback is not supported.

System action:

CICS terminates the transaction abnormally. The EXEC CICS HANDLE ABEND command cannot handle this abend.

Message DFHAC2217 is sent to the terminal end user if possible, and message DFHAC2247 is sent to transient data destination CSMT.

User response:

This error may be an application error or a configuration error. Some communication sessions, (for example, LU6.1) do not support syncpoint rollback, and if CICS detects such a session during rollback processing, the task is abended. This restriction is described in the CICS Intercommunication Guide. To resolve the problem, either:

Alternatively, following a session failure during a previous syncpoint, CICS may have decided to rollback this unit-of-work in order to preserve data integrity. Since the unit-of-work contains a session which does not support syncpoint rollback, this abend ensues. In this case, no action is required in response to this abend, although action may be required to deal with the original failure.

Modules:

DFHAPAC

Start of change
ASP9
Explanation:

The transaction requested syncpoint via EXEC CICS SYNCPOINT, but this is not allowed in a transaction that is acting on behalf of an Activity.

System action:

CICS terminates the transaction abnormally. EXEC CICS HANDLE ABEND command cannot handle this abend.

User response:

The error indicates an invalid attempt to syncpoint the transaction.

Modules:

DFHEISP

End of change
ASQA
Explanation:

The CLS2 transaction was processing resynchronization work but the communications session which it was using has failed.

System action:

The work is reexecuted on a new session. If reexecution has has already been attempted, the transaction terminates.

User response:

The error may be caused by the failure of several sessions between communicating systems during the resynchronization process. To confirm this, examine the CSMT transient data queue for the relevant period.

Another cause could be logic errors within the resynchronization program, either on this system or on the partner system, which caused the session to be terminated. In this case, CSMT transient data messages indicate the nature of the error.

Modules:

DFHCRRSY

ASQB
Explanation:

The CLS2 transaction was executing exchange log names or resynchronization with a remote system when a logic error occurred.

System action:

The transaction is abnormally terminated with a transaction dump.

Message DFHRS2158 may also be issued.

User response:

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

Modules:

DFHCRRSY

ASQC
Explanation:

The CLS2 transaction was attached with an unexpected start code. The transaction can be attached due to terminal input (on a communications session), or via a system attach. Neither of these methods was used.

System action:

The transaction is abnormally terminated.

User response:

The error indicates an invalid attempt to start the transaction.

Modules:

DFHCRRSY

ASQD
Explanation:

The CLS2 transaction was attached but could not use the transaction manager interface to obtain input parameters.

System action:

The transaction is abnormally terminated.

User response:

The error indicates a failure in the transaction manager. See the exception trace entries produced by the transaction managed to determine the reason for the error.

Modules:

DFHCRRSY

ASQE
Explanation:

The CLS2 transaction was executing exchange log names with a remote system and 3 retry attempts have failed to solicit a warm exchange log names reply, in response to a warm exchange log names request sent by CICS.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

This abend indicates an error in the remote system. It should have saved the log name sent by CICS and, on receiving a later exchange lognames request, should then respond with a warm reply.

Modules:

DFHCRRSY

ASQG
Explanation:

The CLS2 transaction was executing resynchronization work and has failed during the receipt of data from remote system via an MRO session. The data was longer than expected.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

The abend indicates a CICS logic error, possibly in the remote system. The transaction storage in the dump shows the data received. The transaction trace shows the preceding flows between the systems, which should match those documented in the SNA LU6.2 Reference: Peer Protocols manual, SC30-6808.

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

Modules:

DFHCRRSY

ASQH
Explanation:

The CLS2 transaction was executing resynchronization work and has failed during the receipt of data from remote system via an MRO session. The data was shorter than the minimum length expected.

System action:

The transaction is anormally terminated with a transaction dump.

User response:

This indicates a CICS logic error, possibly in the remote system. The transaction storage in the dump shows the data received. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRRSY

ASQI
Explanation:

The CLS2 transaction was executing the exchange lognames process as part of the initialization sequence for an APPC connection. An attempt to invoke the CICS recovery manager to save a logname failed.

System action:

The transaction is abnormally terminated with a transaction dump.

Message DFHRS2157 may also be issued.

User response:

This indicates an error in the CICS recovery manager which has produced its own exception trace records. Look at the trace records and the CSMT message log for further information about the error.

Modules:

DFHCRRSY

ASQK
Explanation:

The CLS2 transaction was processing exchange lognames or resynchronization for a connected partner identified by a netname. The connection entry associated with the netname was located and locked, but could not be unlocked in subsequent processing. This indicates a CICS internal logic error.

System action:

The transaction is abnomally terminated with a transaction dump.

Message DFHRS2156 may also issued.

User response:

This indicates an error either in the CICS table manager, (which may have produced its own exception trace records) or in the resynchronization program itself. Look at the trace records and the CSMT message log for further information which might have indicated an error in the table manager program or in the table entry for the connection. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRRSY

ASQL
Explanation:

The CLS2 transaction was executing the resynchronization of a unit of work with a connected partner, and has locked the associated data managed by the CICS recovery manager. The invocation of the TERMINATE_RECOVERY command to unlock the data failed.

System action:

The transaction is abnormally terminated with a transaction dump.

Message DFHRS2154 is also issued.

User response:

This indicates an error either in the CICS recovery manager (which may have produced its own exception trace records) or in the resynchronization program itself. Look at the trace records and the CSMT message log for further information. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRRSY

ASQM
Explanation:

A CICS internal logic error has occurred in the management of dynamic storage for the resynchronization program.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

This indicates that the resynchronization program has exhausted the available space for recording storage areas. The symptoms may indicate that the program was looping without executing the error recovery process. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRRSY

ASRA
Explanation:

The task has terminated abnormally because of a program check.

System action:

The task is abnormally terminated and CICS issues either message DFHAP0001 or DFHSR0001. Message DFHSR0622 may also be issued.

User response:

Refer to the description of the associated message or messages to determine and correct the cause of the program check.

Modules:

DFHSRP

ASRB
Explanation:

An operating system abend has occurred and CICS has been able to abend the current transaction.

System action:

The task is abnormally terminated and CICS issues either message DFHAP0001 or DFHSR0001

User response:

Refer to the description of the associated message to determine the cause of the original operating system abend, and take the necessary corrective action.

Modules:

DFHSRP

ASRD
Explanation:

The task has been abnormally terminated for one of these reasons:

This error appears as a program check.

System action:

The task is abnormally terminated and CICS issues message DFHSR0618, followed by either DFHAP0001 or DFHSR0001.

User response:

Refer to the description of the associated messages to determine and correct the error.

It is likely that either R12 which usually addresses the TCA or R13 which usually addresses the CSA is pointing to an area of storage that you are not allowed to access.

Modules:

DFHSRP

ASRE
Explanation:

The task has been abnormally terminated because an attempt has been made to access a CICS-DB2 RCT load module.

Start of changeThe RCT nolonger exists as a load module and cannot be accessed directly.End of change

To access information held in the RCT use the CICS SPI commands EXEC CICS INQUIRE/SET DB2CONN, EXEC CICS INQUIRE/SET DB2ENTRY and EXEC CICS INQUIRE/SET DB2TRAN.

This error appears as a program check.

System action:

The task is abnormally terminated and CICS issues message DFHSR0619, followed by either DFHAP0001 or DFHSR0001.

User response:

Change the application to use the CICS SPI commands to retrieve data from, or set fields in, the RCT.

Modules:

DFHSRP

ASRK
Explanation:

The AP domain recovery stub, DFHSR1, has been invoked to deal with a program check, operating system abend, or another error within a transaction environment. However, DFHSR1 has been unable to call the system recovery program, DFHSRP, because register 12, which should be pointing to the task control area (TCA), is null. This indicates that the caller of DFHSR1, has not set the address of the TCA..

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:

DFHSR1

[[ Contents Previous Page | Next Page Index ]]