Abend codes ACxx

ACAA
Explanation:

This explanation applies to the two transaction abend codes, ACAA and ACAD. CICS cannot find a match for a function code in the language definition table because the parameterized resource definition contains an unrecognized resource type code. The abend code issued depends on the DFHCAP operation that was invoked before the error occurred:

Abend
DFHCAP operation
ACAA
ANALYZE
ACAD
DEFAULTS

The cause of the abend is either:

System action:

User response:

Ensure that the DFHEITCU module is in the library and is valid for this release of CICS.

If a valid version of DFHEITCU is already in the library, a CICS logic error has occurred. See CICS® Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCAP

ACAD
Explanation:

See ACAA.

Modules:

DFHCAP

ACAI
Explanation:

An internal error has occurred when module DFHCAP was invoked. There was an invalid function code for a domain call to DFHCAP.

System action:

User response:

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

Modules:

DFHCAP

ACAJ
Explanation:

An internal error has occurred when module DFHCAP was invoked while processing an EXEC CICS CREATE command. The preallocated dynamic storage area was too small.

System action:

The transaction executing the EXEC CICS CREATE command 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:

DFHCAP

Start of change
ACAM
Explanation:

An internal error has occurred when module DFHECBAM was invoked while processing a CBAM transaction.

System action:

CBAM 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:

DFHECBAM

End of change
ACCx
Explanation:

Abend codes with ‘ACC’ as the first three characters are issued by the C/370 compiler running under CICS. These are documented in the C/370 User’s Guide.

Start of change
ACFA
Explanation:

During the loading of a Coupling Facility Data Table by the CFCL transaction, an abend was detected or a domain call returned a response (such as DISASTER) after which normal processing could not continue.

System action:

A message is issued (one of DFHFC7100, DFHFC7101, DFHFC7103 or DFHFC7104). Loading of the data table is terminated and CFCL abends.

User response:

If this abend is produced as a result of an abend during loading, message DFHFC7103 is issued. If it is a result of a domain call failure, depending on which domain the failure was returned by, one of the messages DFHFC7100, DFHFC7101 or DFHFC7104 is issued. Refer to the description of the message for further information and guidance.

Modules:

DFHFCDL

End of change
Start of change
ACFB
Explanation:

A transaction has issued a request to a coupling facility data table for which it holds an active lock, but after the lock was acquired, the coupling facility data table server for the pool in which this coupling facility data table resides failed and was restarted. This request is of a type which cannot continue against a new instance of the server, because it is reliant on the lock which was acquired before the server failed.

System action:

The requesting transaction abends with a transaction dump.

CICS continues normally.

User response:

Retry the failed transaction.

Modules:

DFHEIFC

End of change
Start of change
ACFC
Explanation:

A transaction has issued a request to a coupling facility data table which was last accessed using a previous instance of the coupling facility data table server (that is, the server for the pool in which this coupling facility data table resides has failed and been restarted one or more times since the last access). We therefore need to reopen the access between this CICS file and the coupling facility data table, but the attempt to reopen access has failed.

System action:

The requesting transaction abends with a transaction dump.

CICS continues normally.

User response:

Retry the failed transaction. If the error continues to occur, issue an explicit close request for the file, followed by an explicit open request.

Modules:

DFHEIFC

End of change
Start of change
ACFD
Explanation:

During the loading of a Coupling Facility Data Table by the CFCL transaction, a call to the CICS Transaction Manager has returned a response (such as DISASTER) after which normal processing could not continue.

System action:

Message DFHFC7121 is issued. Loading of the data table is terminated and CFCL abends.

User response:

Refer to the description of the message for further information and guidance.

Modules:

DFHFCDL

End of change
Start of change
ACFE
Explanation:

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

DFHFCDL is for use by CICS system transaction CFCL. This loads a Coupling Facility Data Table.

System action:

The transaction is abnormally terminated. CICS processing continues.

User response:

Establish why an attempt was made to attach CFCL illegally, or why a transaction definition specified DFHFCDL as the program to be given control.

Modules:

DFHFCDL

End of change
ACHA
Explanation:

The remote server transaction, CEHS, is not at a compatible level to operate with the CICS/CMS system. This usually indicates that the service levels of CICS/CMS and the remote server are different.

Problem determination:

To diagnose a problem with the remote server, it is generally helpful to obtain a trace of the remote server’s activity up to the point of failure.

A remote server trace is obtained by invoking the remote server with the TRACE option, (type CEHS TRACE). The remote server operates as normal but causes entries to be written to a trace log in temporary storage. Note that main storage, not auxiliary, is used for this queue hence large amounts of memory can be used up if this trace is left on for long.

The trace is found in a queue whose name is ‘CEHSxxxx’, where ‘xxxx’ is the four-character terminal identifier. The queue can be browsed in text form or in hexadecimal form using CEBR. To find the terminal identifier, invoke CEBR on the terminal that has run CEHS, without giving a queue name. The queue name will default to ‘CEBRxxxx’, where ‘xxxx’ is the terminal identifier.

Note: CEBR requires the queue name to be in UPPER CASE.

For a description of the remote server and its trace entries and abend codes, see the CICS/VS Remote Server Diagnosis Manual (LC33-0438).

System action:

CICS terminates the remote server transaction abnormally with a 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:

DFHCHS

ACHB
Explanation:

The remote server has received a data frame from CICS/CMS that is out of sequence. A frame may have been lost in transmission.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further information, see the ‘Problem Determination’ section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCHS

ACHC
Explanation:

The remote server did not receive the expected acknowledgement type data frame from CICS/CMS.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further information, see the ‘Problem Determination’ section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCHS

ACHD
Explanation:

The remote server did not receive the expected response type data frame from CICS/CMS.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further information, see the ‘Problem Determination’ section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCHS

ACHE
Explanation:

The remote server received an unexpected data frame from CICS/CMS. This indicates a logic error in the remote server.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further information, see the ‘Problem Determination’ section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCHS

ACHF
Explanation:

The remote server attempted to send one of a series of data frames to CICS/CMS when, at this time, only a single frame is allowed. This indicates a logic error in the remote server.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further information, see the ‘Problem Determination’ section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCHS

ACHG
Explanation:

The remote server attempted to send data to CICS/CMS. However, it was not set to the correct mode to do so. This indicates a logic error in the remote server.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further information, see the ‘Problem Determination’ section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCHS

ACHH
Explanation:

A TIOA has not been created from the data received by the remote server from CICS/CMS.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further information, see the ‘Problem Determination’ section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCHS

ACHI
Explanation:

The remote server has received an unexpected return code from the Transformer 2 program.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

For further information, see the ‘Problem Determination’ section for abend code ACHA.

Modules:

DFHCHS

ACHJ
Explanation:

An error has occurred processing a request from CICS/CMS which had the ‘No-Reply’ option. The remote server cannot, therefore, return the error condition to CICS/CMS.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the remote server and diagnose the problem by executing the same command from CECI under CICS/CMS without the NOCHECK option. For further information, see the ‘Problem Determination’ section for abend code ACHA.

Modules:

DFHCHS

ACHK
Explanation:

The transformer program has requested neither EIP nor DLI to execute the request received from CICS/CMS. This indicates a logic error because the request has to be destined for either EIP or DLI.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

For further information, see the ‘Problem Determination’ section for abend code ACHA.

Modules:

DFHCHS

ACHL
Explanation:

CICS/CMS has supplied a buffer to the remote server which is not large enough to hold the reply that the remote server has to return.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further information, see the ‘Problem Determination’ section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCHS

ACHM
Explanation:

The remote server has tried to receive a response from CICS/CMS which failed repeatedly until the retry limit was exceeded.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further information, see the ‘Problem Determination’ section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCHS

ACHN
Explanation:

The remote server has tried to receive a request from CICS/CMS which failed repeatedly until the retry limit was exceeded.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further information, see the ‘Problem Determination’ section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCHS

ACHO
Explanation:

The remote server has tried to receive a reply from CICS/CMS which failed repeatedly until the retry limit was exceeded.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

Reestablish the connection between CICS/CMS and the remote CICS system and try to use the remote server again. For further information, see the ‘Problem Determination’ section for abend code ACHA.

If the problem persists, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCHS

ACHP
Explanation:

CICS/CMS has made a request to the remote server for which the reply would need more than the maximum storage allowed (32660 bytes). This indicates that a logic error has occurred.

System action:

CICS terminates the remote server abnormally with a dump.

User response:

For further information, see the ‘Problem Determination’ section for abend code ACHA.

Modules:

DFHCHS

ACHR
Explanation:

The CICS/CMS remote server transaction (CEHS) has been initiated and either the task is not terminal-oriented, or the associated terminal is a console.

System action:

CICS abnormally terminates the remote server with a dump.

User response:

Ensure the transaction is initiated with an associated terminal and that the terminal is not defined as a console. For further information, see the ‘Problem Determination’ section for abend code ACHA.

Modules:

DFHCHS

ACHS
Explanation:

The CICS/OS2 remote server transaction (CEHP) has been initiated and either the task is not terminal-oriented, or the associated terminal is a console.

System action:

CICS abnormally terminates the remote server with a dump.

User response:

Ensure the transaction is initiated with an associated terminal and that the terminal is not defined as a console. For further information, see the ‘Problem Determination’ section for abend code ACHA.

Modules:

DFHCHS

Start of change
ACL0
Explanation:

The new operator failed to allocate storage whilst creating an object. This problem will occur if there is insufficient storage available to the CICS region to satisfy the request.

System action:

CICS abnormally terminates the transaction.

User response:

This abend may occur if you are in a loop creating objects and not deleting them. Alternatively CICS might be short on storage and you should try resubmitting the transaction.

Modules:

ICCGLBIC

End of change
Start of change
ACL1
Explanation:

The CICS Foundation Classes have thrown an exception which the application programmer failed to catch.

System action:

CICS abnormally terminates the transaction.

User response:

Check that you have coded your application to catch exceptions. Interrogate the message object contained within the exception object to establish the cause of the exception being thrown.

Another possible cause of this abend is that you are running a Foundation Classes program on a machine that does not have the C++ runtime installed. Check that your machine has the C++ runtime installed.

Modules:

ICCGLBIC

End of change
Start of change
ACL2
Explanation:

The CICS Foundation Classes invoked the default handleEvent method (defined in class IccResource) in order to handle a CICS condition because the application programmer did not implement his own handleEvent method.

System action:

CICS abnormally terminates the transaction.

User response:

Implement your own handleEvent method or customize your resource objects so they do not call the handleEvent method for any of the possible CICS conditions.

Modules:

ICCRESEC

End of change
Start of change
ACL3
Explanation:

The CICS Foundation Classes responded to an application programmer's request to abend a CICS task.

System action:

CICS abnormally terminates the transaction.

User response:

The application programmer requested that the CICS Foundation Classes abend the transaction using the appropriate return enumeration from the handleEvent method (see IccResource class).

Modules:

ICCRESIC

End of change
Start of change
ACL4
Explanation:

The CICS Foundation Classes detected an internal error.

System action:

CICS abnormally terminates the transaction.

User response:

This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Modules:

ICCGLIBC

End of change
Start of change
ACL5
Explanation:

The CICS Foundation Classes received an error from a CICS storage request (GETMAIN). In response to a new operator request the CICS Foundation Classes issued a CICS GETMAIN request to allocate storage which CICS was unable to satisfy.

System action:

CICS abnormally terminates the transaction.

User response:

This abend may occur if you are in a loop creating objects and not deleting them. Alternatively CICS might be short on storage and you should try resubmitting the transaction.

Modules:

ICCBASEC

End of change
Start of change
ACL6
Explanation:

The CICS Foundation Classes detected an error while processing a storage release request.

System action:

CICS abnormally terminates the transaction.

User response:

This abend can occur if you try to delete an object that does not exist (that is, it has already been deleted). It may also indicate a CICS memory management problem, or a storage corruption problem. If the error persists, please contact your support organization.

Modules:

ICCBASEC

End of change
Start of change
ACL7
Explanation:

The CICS Foundation Classes have thrown an exception which the application programmer failed to catch.

System action:

CICS abnormally terminates the transaction.

User response:

Check that you have coded your application to catch exceptions. Interrogate the message object contained within the exception object to establish the cause of the exception being thrown.

Another possible cause of this abend is that you are running a Foundation Classes program on a machine that does not have the C++ runtime installed. Check that your machine has the C++ runtime installed.

Modules:

ICCGLBIC

End of change
Start of change
ACL8
Explanation:

The CICS Foundation Classes have thrown an exception which the application programmer failed to catch.

System action:

CICS abnormally terminates the transaction.

User response:

Check that you have coded your application to catch exceptions. Interrogate the message object contained within the exception object to establish the cause of the exception being thrown.

Another possible cause of this abend is that you are running a Foundation Classes program on a machine that does not have the C++ runtime installed. Check that your machine has the C++ runtime installed.

Modules:

ICCGLBIC

End of change
Start of change
ACL9
Explanation:

The CICS Foundation Classes responded to an application programmer's request to abend a CICS task.

System action:

CICS abnormally terminates the transaction.

User response:

A resource object was customized to cause a transaction abend if a particular CICS condition was raised, and this condition was subsequently raised by CICS.

Modules:

ICCRESIC

End of change
Start of change
ACLA
Explanation:

The CICS Foundation Classes detected an internal error.

System action:

CICS abnormally terminates the transaction.

User response:

This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Modules:

ICCGLIBC

End of change
Start of change
ACLB
Explanation:

The CICS Foundation Classes detected an internal error.

System action:

CICS abnormally terminates the transaction.

User response:

This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Modules:

ICCGLIBC

End of change
Start of change
ACLC
Explanation:

The CICS Foundation Classes detected an internal error.

System action:

CICS abnormally terminates the transaction.

User response:

This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Modules:

ICCGLIBC

End of change
Start of change
ACLD
Explanation:

The CICS Foundation Classes detected an internal error.

System action:

CICS abnormally terminates the transaction.

User response:

This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Modules:

ICCGLIBC

End of change
Start of change
ACLE
Explanation:

The CICS Foundation Classes detected an internal error.

System action:

CICS abnormally terminates the transaction.

User response:

This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Modules:

ICCGLIBC

End of change
Start of change
ACLF
Explanation:

The CICS Foundation Classes detected an internal error.

System action:

CICS abnormally terminates the transaction.

User response:

This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Modules:

ICCGLIBC

End of change
Start of change
ACLG
Explanation:

The CICS Foundation Classes detected an internal error.

System action:

CICS abnormally terminates the transaction.

User response:

This abend indicates a CICS Foundation Classes internal problem. Please contact your support organization.

Modules:

ICCGLIBC

End of change
Start of change
ACLH
Explanation:

The CICS Foundation Classes detected an error while processing a storage release request.

System action:

CICS abnormally terminates the transaction.

User response:

This abend can occur if you try to delete an object that does not exist (that is, it has already been deleted). It may also indicate a CICS memory management problem, or a storage corruption problem. If the error persists, please contact your support organization.

Modules:

ICCBASEC

End of change
ACNA
Explanation:

The table DFHCNV cannot be loaded. This is a general purpose abend code indicating that the LOAD request for the conversion table, DFHCNV, has failed.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Examine the transaction dump to determine the exact condition returned from LOAD request.

Modules:

DFHCCNV

ACNB
Explanation:

The program DFHUCNV cannot be linked This is a general purpose abend code indicating that the LINK request for the conversion program DFHUCNV, has failed.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Examine the transaction dump to determine the exact condition returned from LINK request.

Modules:

DFHCCNV

ACN1
Explanation:

The table DFHCNV cannot be loaded. This is probably because a table has not been pregenerated. It could also occur if the table DFHCNV has been linked above 16MB but DFHCCNV has been linked below 16MB.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Check that the DFHCNV module is in the library and is valid for this release of CICS. Check the linkage of DFHCNV and relink it with the correct AMODE if necessary.

Modules:

DFHCCNV

ACN2
Explanation:

The table DFHCNV has been loaded but the first record is in the wrong format. This is probably due to an error during assembly or linkedit, but could also be the result of a storage overwrite.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

The table should be reassembled and linked. Check the assemble and linkedit output. Check for any messages issued from CICS indicating that storage overwrites have occurred.

Modules:

DFHCCNV

ACN3
Explanation:

The program DFHUCNV cannot be linked. A user conversion program must be available (even if it only returns).

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Check that the DFHUCNV module is in the library and is valid for this release of CICS. Check the linkage of DFHUCNV and relink it with the correct AMODE if necessary.

Modules:

DFHCCNV

ACN4
Explanation:

An unrecognized format of a DFHCNV table has been encountered.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Re-assemble and re-link edit the DFHCNV macro.

Modules:

DFHCCNV

ACN5
Explanation:

An override for the default client code page has been received; however the value is not recognized.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Check that the client system is using one of the client code pages supported by CICS/390.

Modules:

DFHCCNV

ACN6
Explanation:

The client sent data in unicode but the client and server code pages are not the same. Unicode data is only tolerated provided that conversion is not required.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Ensure that the Client codepage and the Server codepage are the same.

Modules:

DFHCCNV

Start of change
ACNC
Explanation:

The client code page which has been requested by the client is not one which CICS can support.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Ensure that the Client codepage is valid.

Modules:

DFHCCNV

End of change
Start of change
ACND
Explanation:

The conversion between client code page and server code page is not supported by CICS/390; for example conversion has been requested between Japanese code page 932 and Latin-1 code page 500.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Ensure that the Client codepage, both default and overrides are in the same group as the Server codepage. for example client code page 852 from Latin-2 group, is only supported to server code page 870.

Modules:

DFHCCNV

End of change
Start of change
ACNE
Explanation:

The conversion between client code page and server code page is not supported by CICS/390. Although the code pages are in the same group, CICS does not have a conversion table to match the requested server code page for the client code page specified.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Ensure that the Client codepage and the server codepage are correct. If they are as intended, then CICS can not support the requested conversion.

Modules:

DFHCCNV

End of change
ACN7
Explanation:

An override for the default binary format has been received; however the value is not recognized.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Data formats should be either S/370 or INTEL, anything else is unsupported by CICS/390.

Modules:

DFHCCNV

ACN8
Explanation:

CICS data conversion is processing a FIELD defined as containing GRAPHIC characters (which are only DBCS): that is DFHCNV TYPE=FIELD,DATATYP=GRAPHIC,... However the client code page (defined in the CLINTCP operand), and the server code page (defined in the SRVERCP operand) imply that the FIELD contains only SBCS characters, for example DFHCNV TYPE=ENTRY,CLINTCP=437,SRVERCP=037

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Correct the FIELD definition.

Modules:

DFHCCNV

ACN9
Explanation:

The table DFHCNV cannot be loaded. This abend code is issued following a NOTAUTH condition being raised during loading of the DFHCNV table.

System action:

The transaction is abnormally terminated with a transaction dump.

User response:

Ensure the resource security definitions are correct.

Modules:

DFHCCNV

ACP1
Explanation:

DFHIC TYPE=GET response code is other than the normal response during print key processing.

System action:

The transaction is abnormally terminated with a CICS transaction dump. The keyboard of the terminal on which the print key was depressed remains locked to indicate the failure of the operation.

User response:

Analyze the dump. The response code is in the low order byte of register 0.

Modules:

DFHCPY

ACP2
Explanation:

DFHIC TYPE=INITIATE response code is other than the normal response during print key processing.

System action:

The transaction is abnormally terminated with a CICS transaction dump. The keyboard of the terminal on which the print key was depressed remains locked to indicate the failure of the operation.

User response:

Analyze the dump. The response code is in low-order byte of register 0.

Modules:

DFHCPY

Start of change
ACQA
Explanation:

The Connection Quiesce Protocol transaction has been initiated by user action, such as a START command or by typing the transaction identifier at a terminal. The transaction is not intended to be initiated in this way.

System action:

  1. If the transaction was not initiated by terminal input, message DFHZC4951 is written to destination CSNE.
  2. An exception trace record is written to all active trace destinations.
  3. The transaction is abnormally terminated with a CICS transaction dump.
User response:

Determine what caused the transaction to be initiated. The exception trace record contains information which will help you.

Modules:

DFHCLS5

End of change
Start of change
ACQB
Explanation:

The Connection Quiesce Protocol transaction has encountered an error when communicating with another system on an APPC session.

System action:

  1. Message DFHZC4951 is written to destination CSNE.
  2. An exception trace record is written to all active trace destinations.
  3. The transaction is abnormally terminated with a CICS transaction dump.
User response:

Determine what caused the failure. A likely cause is a failure of the session with the partner system.

Modules:

DFHCLS5

End of change
Start of change
ACQC
Explanation:

The Connection Quiesce Protocol transaction has encountered an unexpected error.

System action:

  1. Message DFHZC4951 is written to destination CSNE.
  2. An exception trace record is written to all active trace destinations.
  3. 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:

DFHCLS5

End of change
ACRA
Explanation:

The relay program has been invoked without a terminal as its principal facility.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Ensure that DFHAPRT has not been specified as the initial program of a task that is not terminal-related.

Modules:

DFHAPRT

ACRB
Explanation:

The relay program has been invoked by a transaction that is not defined as remote.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check that the relay program is defined correctly. Determine why DFHAPRT was invoked if the transaction is not a remote transaction.

Modules:

DFHAPRT

ACRC
Explanation:

The relay program received an invalid response from DFHZCX.

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:

DFHAPRT

ACRD
Explanation:

The system entry for the system to which routing is to be performed could not be found.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check the installed transaction definition to confirm that the system was correctly specified. Check that the system entry is defined in the TCT.

Modules:

DFHAPRT

ACRE
Explanation:

A transaction invoked from an APPC terminal and specified in the installed transaction definition as remote has abnormally terminated because the link is out of service.

System action:

The task is abnormally terminated.

User response:

Wait until the link is available. The CICS supplied transaction CEMT INQUIRE CONNECTION can be used to check the states of the links.

Modules:

DFHAPRT

ACRF
Explanation:

The relay program received a nonzero return code from the dynamic router following its first invocation.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the dump to determine why the dynamic routing program has failed by checking the contents of the passed COMMAREA DFHDYE for correctness. The COMMAREA address can be found from field TCACOMM in the system TCA for the task. The COMMAREA fields are mapped via the DFHDYPDS DSECT.

Modules:

DFHAPRT

ACRG
Explanation:

An ATI initiated remote transaction defined with DYNAMIC(YES) has failed because there is no matching entry in the AID chain.

Each AID in the chain has been checked and none has been found where

System action:

The task is abnormally terminated with a CICS system dump.

User response:

The dump can be used to help ascertain the mismatch. Check the transactions listed in the TCTTE and PCT fields of the system dump against the AID chain.

Modules:

DFHAPRT

ACRH
Explanation:

The profile for the session that will carry intersystem flows during transaction routing could not be found.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Check the installed transaction definition to confirm that TRPROF is correctly specified.

Modules:

DFHAPRT

ACRI
Explanation:

Start of changeAn error occurred when attempting to link to the dynamic routing program.End of change

System action:

The transaction is abnormally terminated with a CICS transaction dump.

A message in the range DFHRT4417 to DFHRT4420 is written to the CSMT log.

User response:

Refer to the message sent to the CSMT log. It identifies the cause of the link failure and provides further user guidance.

Start of change
Modules:

DFHAPRT, DFHEPC

End of change
ACRJ
Explanation:

Start of changeAn abend has occurred in the dynamic routing program after a link has been executed from DFHAPRT or DFHEPC.End of change

System action:

The transaction is abnormally terminated with a CICS transaction dump. Message DFHRT4416 is written to the CSMT log.

User response:

Refer to message DFHRT4416. Start of changeIt identifies the abend in the dynamic routing program and provides further user guidance.End of change

Start of change
Modules:

DFHAPRT, DFHEPC

End of change
ACRK
Explanation:

The relay program has been invoked with no address for the principal facility.

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:

DFHAPRT

ACRL
Explanation:

The task does not own the facility.

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:

DFHAPRT

ACRM
Explanation:

In response to a request from the dynamic routing program, DFHAPRT has attempted an INITIAL_LINK to a program that is not the initial program of the transaction for which the dynamic router has been invoked. The attempt has failed.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Examine the following possibilities:

Modules:

DFHAPRT

Start of change
ACRN
Explanation:

The dynamic routing program has indicated that the transaction should not be routed, but execute in the local system. Prior to invoking the application program, a security check is performed. This check has failed.

System action:

The transaction is abnormally terminated with a CICS transaction dump.

User response:

Ensure that the transaction security definition is correct.

Modules:

DFHAPRT

End of change
ACRO
Explanation:

An attempt has been made to invoke the CRSQ transaction from a terminal. CRSQ is an internal CICS transaction and cannot be invoked in this way.

System action:

The task is abnormally terminated.

User response:

None. You can use CEMT and EXEC CICS commands to cancel AIDs.

Modules:

DFHCRQ

ACRP
Start of change
Explanation:

The dynamic router has supplied a sysid whose supported functions are unknown. This may be due to either a backlevel release, or APPC is used for communication and no work has flowed across this connection.

End of change
Start of change
System action:

The task is abnormally terminated with a CICS transaction dump.

End of change
Start of change
User response:

Give an alternative sysid, or revert to the old style START, or flow some routed work across the connection.

End of change
Start of change
Modules:

DFHAPRT

End of change
ACSA
Explanation:

The remote scheduler task (CRSR) does not own an intersystem link TCTTE as its principal facility.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Ensure that DFHCRS is not specified as the initial program of a task other than CRSR. Check that the terminal operator did not enter CRSR.

Modules:

DFHCRS

ACSB
Explanation:

An unexpected reply was received from a remote system in response to a request to schedule a task on that 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:

DFHCRS

ACSC
Explanation:

An unexpected request was received from a remote system when expecting a request to schedule a task.

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:

DFHCRS

ACSD
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:

DFHCRS

ACSE
Explanation:

Module DFHCRS has been attached in an unsupported manner.

System action:

CICS abnormally terminates the transaction with a transaction dump.

User response:

Module DFHCRS should be executed only by transaction CRSR, which executes with an MRO session, an LU6.1 session or an LU type 6.2 conversation as its principal facility. Ensure that the transaction is being attached by a CRSR transaction in the connected system, and not by a user transaction.

If the transaction is being attached by a CRSR transaction, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRS

ACSF
Explanation:

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

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Investigate the reason why the task was purged. It was purged either by the master terminal operator or as a result of a deadlock timeout.

Modules:

DFHCRS

ACSG
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 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.

User response:

Please see the related error message produced by the domain that detected the original error.

Modules:

DFHCRS

ACSH
Explanation:

The processing of APPC mapped data requires the generation of an LU6.2 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:

DFHCRS

ACSI
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:

DFHCRS

ACSJ
Explanation:

An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the recovery manager (RM) domain. The domain provides an exit trace, and possibly a console message and a system dump (depending on the options specified in the dump table). This failure is either the result of a task purge, or a CICS logic error.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

See the related diagnostic material produced by the recovery manager domain and determine the reason for the failure.

In the case of a CICS logic error, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHCRS

ACSK
Explanation:

The transaction wait was purged while waiting for a VTAM INQUIRE macro to complete.

CICS issued a VTAM INQUIRE OPTCD=NQN or INQUIRE OPTCD=SESSNAME request then waited for VTAM to post the ECB, but the wait was terminated either as a result of an explicit FORCEPURGE request, or due to a 3 minute time out.

System action:

A transaction dump is taken together with CICS issuing message DFHZC0001.

User response:

Investigate the reason why the wait was terminated.

In the case of a time out, you may need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Modules:

DFHZGIN

ACSL
Explanation:

CICS has been unable to attach a transaction to perform a mass flag (CFTS) or mass remote delete (CDTS) 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:

DFHCRS

ACSM
Explanation:

Transaction CFTS has abended. The mass flagging of terminals for deletion 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:

DFHCRS

ACSN
Explanation:

Transaction CFTS has stalled. The mass flagging of terminals for deletion has exceeded the expected time and is therefore assumed to have failed.

System action:

The task is abnormally terminated with a CICS transaction dump. A flag is set in the remote work element (RWE) to indicate that the mainline transaction has assumed that CFTS has failed.

User response:

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

Modules:

DFHCRS

ACTA
Explanation:

The relay program running in the terminal-owning region has received an unexpected request from the application owning region. The request received is in violation of CICS transaction routing protocols.

The request will be in the DFHLUCDS DSECT in DFHZTSP’s LIFO - field LUCOPN0

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:

DFHZTSP

ACTB
Explanation:

The relay program running in the terminal-owning region issued a terminal control WRITE,LAST request to the application-owning system, and received a nonzero return code from terminal control.

This is the usual return code from terminal control in TCATPAPR.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine why terminal control was unable to process the request.

Modules:

DFHZTSP

ACTC
Explanation:

The relay program running in the terminal-owning region issued a terminal control request to free its session to the application-owning system, and received a nonzero return code from terminal control.

This is the usual return code from terminal control in TCATPAPR.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine why terminal control was unable to process the request.

Modules:

DFHZTSP

ACTD
Explanation:

The relay program running in the terminal-owning region issued a terminal control WRITE,WAIT,READ request to the application-owning system, and received a nonzero return code from terminal control.

This is the usual return code from terminal control in TCATPAPR.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine why terminal control was unable to process the request.

Modules:

DFHZTSP

ACTE
Explanation:

The relay program running in the terminal-owning region attempted to free its session with the APPC terminal, and received a nonzero return code from terminal control.

The return code will be in the DFHLUCDS DSECT in DFHZTSP’s LIFO field, LUCRCODE.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. The terminal session may have failed.

Modules:

DFHZTSP

ACTF
Explanation:

The relay program running in the terminal-owning region issued a terminal control request to free its session to the application-owning system, and received a nonzero return code from terminal control.

This return code can be found in the TCA field, TCATPAPR.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. The transaction on the application-owning region may have abnormally terminated or the session may have failed.

Modules:

DFHZTSP

ACTG
Explanation:

The relay program running in the terminal-owning region issued a request to attach a transaction in the application-owning region, but the response received from that region was invalid.

The return code in the TCA (field TCATPAPR) will be nonzero, and either there will be no TIOA (field TCTTEDA in the TCTTE is zero) or there will be no FMH7 at the start of the TIOA.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. The transaction on the application-owning region may have abnormally terminated or the session may have failed.

Modules:

DFHZTSP

ACTH
Explanation:

A privileged allocate was issued against a remote LU 6.2 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:

DFHZISP

ACTI
Explanation:

The relay transaction has an ISC or MRO session as its principal facility. However the TCTTE for that session is not owned by the task.

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:

DFHCRT

ACTJ
Explanation:

The principal facility of the relay transaction is not a TCTTE.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Task CXRT should only be started in a terminal-owning region by an ALLOCATE request issued in an application-owning region against a remote APPC device. The principal facility of the task should be an ISC or MRO link. Check that your CICS system is defined in such a way that this will always be the case. Also ensure that program DFHCRT is started only by task CXRT.

Modules:

DFHCRT

ACTK
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 the reason why the task was purged. It was either purged by the master terminal operator or as a result of a deadlock timeout.

Modules:

DFHZISP

ACTL
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 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.

User response:

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

Modules:

DFHZISP

ACUA
Explanation:

DFHZXRL was called with a request which is not supported for transaction routing.

The request is located in the DFHLUC parameter list which is printed in the exception trace. DFHZXRL is called from DFHZARL, which will put details of the request in its trace entry.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACUB
Explanation:

The parameter list passed to DFHZXRL for an ALLOCATE request does not contain the TCTSE address of a remote APPC terminal.

The TCTSE address is located in the DFHLUC parameter list which is printed in the exception trace. DFHZXRL is called from DFHZARL, which will put details of the request in its trace entry.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACUC
Explanation:

The TCTSE address passed to DFHZXRL is not that of a remote LU 6.2 terminal.

The TCTSE address is located in the DFHLUC parameter list which is printed in the exception trace. DFHZXRL is called from DFHZARL, which will put details of the request in its trace entry.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACUD
Explanation:

The profile DFHCICSR could not be located as an installed profile definition.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Check that the IBM-supplied profile DFHCICSR is correctly defined and installed to CICS.

Modules:

DFHZXRL

ACUE
Explanation:

A request to DFHZTSP to build a surrogate TCTTE was not satisfied.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACUF
Explanation:

A session between the application-owning region and the terminal-owning region was not allocated because the request was incorrectly specified.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACUG
Explanation:

A request to allocate a session between the application-owning region and the terminal-owning region failed. The return code from the ALLOCATE request indicated that the profile could not be located as an installed transaction definition, although an earlier attempt to locate it was successful.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACUH
Explanation:

A request to allocate a session between the application-owning region and the terminal-owning region failed. The return code from the ALLOCATE request indicated that the requested session is already owned by the TCA.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACUI
Explanation:

An ISC session between the application-owning region and the terminal-owning region was not allocated because the MODENAME named in the profile could not be found. The profile DFHCICSR as supplied by IBM does not specify a MODENAME. Therefore, this error will occur when a MODENAME has been added to the IBM-supplied profile, but that MODENAME is not defined in the SESSIONS definition for the terminal-owning region.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Ensure that the MODENAME specified in profile DFHCICSR was also specified when defining the SESSIONS to the terminal-owning region.

Modules:

DFHZXRL

ACUJ
Explanation:

A session between the application-owning region and the terminal-owning region was not allocated because the maximum session count for the mode group specified in profile DFHCICSR is zero.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the CEMT transaction to set sessions in the required mode group available for use.

Modules:

DFHZXRL

ACUK
Explanation:

No TCT entry was found for the terminal-owning region specified in the TCTSE for the remote terminal.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Ensure that the terminal-owning region defined in the remote system entry is also defined with a system entry in the TCT.

Modules:

DFHZXRL

ACUL
Note:

The description of this abend also applies to ACUX and ACUZ.

Explanation:

The transaction routing program in the application-owning region issued a terminal control WRITE,WAIT,READ request to the terminal-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRL

ACUM
Explanation:

A request to DFHZTSP to free a surrogate TCTTE was not satisfied.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACUO
Note:

The description of this abend also applies to ACUQ, ACUS and ACU1.

Explanation:

A terminal control READ request has failed. The transaction routing program in the application-owning region attempted to receive data from the terminal-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRL

ACUP
Note:

The description of this abend also applies to ACUR.

Explanation:

The transaction routing program in the application-owning region did not receive a rollback from the terminal-owning region. This violates CICS transaction routing protocols.

The trace from the terminal-owning region will show its response to the application-owning region.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACUQ
Explanation:

Refer to the description of abend ACUO.

Modules:

DFHZXRL

ACUR
Explanation:

Refer to the description of abend ACUP.

Modules:

DFHZXRL

ACUS
Explanation:

Refer to the description of abend ACUO.

Modules:

DFHZXRL

ACUT
Explanation:

The transaction routing program in the application-owning region did not receive either a syncpoint or a rollback from the terminal-owning region. This violates CICS transaction routing protocols.

The trace from the terminal-owning region will show its response to the application-owning region.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACUV
Explanation:

The transaction routing program in the application-owning region issued a terminal control ISSUE ABEND request on an MRO link to the terminal-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZIS1.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRL

ACUW
Explanation:

The transaction routing program in the application-owning region issued a terminal control ISSUE ERROR request on an MRO link to the terminal-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZIS1.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRL

ACUX
Explanation:

Refer to the description of abend ACUL.

Modules:

DFHZXRL

ACUY
Explanation:

The transaction routing program in the application-owning region issued a terminal control WRITE,WAIT request to the terminal-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRL

ACUZ
Explanation:

Refer to the description of abend ACUL.

Modules:

DFHZXRL

ACU0
Explanation:

The transaction routing program in the application-owning region issued a terminal control WRITE,LAST,WAIT request to the terminal-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRL

ACU1
Explanation:

Refer to the description of abend ACUO.

Modules:

DFHZXRL

ACU2
Explanation:

The transaction routing program in the application-owning region received a response from the terminal-owning region which violates CICS transaction routing protocols.

The trace from the terminal-owning region will show its response to the application-owning region.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACU3
Explanation:

The transaction routing program in the application-owning region attempted to set the conversation state machine to a state which violates CICS transaction routing protocols.

The register containing the state can be determined from the assembler listing.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACU4
Explanation:

The transaction routing program in the application-owning region issued a SET request to the conversation state machine and received a nonzero return code. This violates CICS transaction routing protocols.

The trace entry on return from DFHZUSR will show the request type and current state.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACU5
Explanation:

An program running in an application-owning region has issued an ALLOCATE against an APPC device attached to a terminal owning region, but the connection between the two systems is not installed.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Install the connection between the two regions.

Modules:

DFHZXRL

ACU6
Explanation:

A request to DFHRTSU to prepare the surrogate TCTTE for syncpoint gave an unexpected response and reason code. The response and reason code are included in DFHRTSU's parameter list which is printed in the exception trace.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACU7
Explanation:

A request to allocate a session between the application-owning region and the terminal-owning region was issued, but the connection with the remote system is not an APPC or MRO connection.

System action:

The task is abnormally terminated with a CICS transaction dump.

User response:

Redefine the connection as APPC or MRO, or avoid using transaction routing on this connection.

Modules:

DFHZXRL

ACU8
Explanation:

A request to DFHRTSU to get the recovery status of a surrogate TCTTE gave an unexpected response and reason code. The response and reason code are included in DFHRTSU's parameter list which is printed in the exception trace.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACU9
Explanation:

A request to recovery manager to set the recovery status of a link gave an unexpected response and reason code. The response and reason code are included in DFHRMLN's parameter list which is printed in the exception trace.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRL

ACVA
Explanation:

The transaction routing program in the terminal-owning region issued a terminal control WRITE,WAIT,READ request to the application-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRT

ACVB
Explanation:

The transaction routing program in the terminal-owning region attempted to issue an ISSUE SIGNAL request on an MRO link to the application-owning region. This violates CICS transaction routing protocols.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRT

ACVC
Explanation:

The transaction routing program in the terminal-owning region issued an ISSUE SIGNAL request on an LU 6.2 link to the application-owning region, and received a nonzero return code from terminal control.

The return code is located in the DFHLUC parameter list which is printed in the exception trace.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRT

ACVD
Explanation:

The transaction routing program in the terminal-owning region issued a READ,WAIT request to the application-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRT

ACVE
Explanation:

The transaction routing program in the terminal-owning region issued a WRITE request to the application-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRT

ACVF
Explanation:

The transaction routing program in the terminal-owning region issued a WRITE,LAST,WAIT request to the application-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRT

ACVG
Explanation:

The transaction routing program in the terminal-owning region issued a FREE request to free the session with the LU 6.2 terminal, and received a nonzero return code from terminal control.

The return code is located in the DFHLUC parameter list which is printed in the exception trace.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. The terminal session may have failed.

Modules:

DFHZXRT

ACVH
Explanation:

The transaction routing program in the terminal-owning region issued a FREE request to free the session with the application-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZARQ.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRT

ACVK
Explanation:

The transaction routing program in the terminal-owning region issued an ISSUE ABEND request on an LU 6.2 link, and received a nonzero return code from terminal control.

The return code is located in the DFHLUC parameter list which is printed in the exception trace.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRT

ACVL
Explanation:

The transaction routing program in the terminal-owning region issued an ISSUE ABEND request on an MRO link to the application-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZIS1.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRT

ACVM
Explanation:

The transaction routing program in the terminal-owning region issued an ISSUE ERROR request on an LU 6.2 link, and received a nonzero return code from terminal control.

The return code is located in the DFHLUC parameter list which is printed in the exception trace.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRT

ACVN
Explanation:

The transaction routing program in the terminal-owning region issued an ISSUE ERROR request on an MRO link to the application-owning region, and received a nonzero return code from terminal control.

The return code is located both in TCATPAPR and in the trace entry on return from DFHZIS1.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. This abend code may result when:

Modules:

DFHZXRT

ACVO
Explanation:

The transaction routing program in the terminal-owning region issued an ISSUE PREPARE request and received either a nonzero return code or a response which violates CICS transaction routing protocols.

The return code is located in TCASPRC and the response is located in TCASPSN1.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine whether the problem is caused by the return code or the response. If terminal control was unable to process the request, the abend may occur when:

Otherwise the distributed application programs may have violated APPC conversation protocols.

Modules:

DFHZXRT

ACVP
Explanation:

The transaction routing program in the terminal-owning region did not receive an FMH43 from the application-owning region. This violates CICS transaction routing protocols.

The trace from the application-owning region will show its response to the terminal-owning region.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

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

Modules:

DFHZXRT

ACVQ
Explanation:

The transaction routing program in the terminal-owning region issued a request to the APPC terminal, and received a nonzero return code from terminal control.

Both the request and the return code are located in the DFHLUC parameter list which is printed in the exception trace.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. The terminal session may have failed or be in the wrong state, for example, as the result of both the terminal and application issuing SYNCPOINT ROLLBACK at the same time.

Modules:

DFHZXRT

ACVR
Explanation:

The transaction routing program in the terminal-owning region issued a SEND,LAST,WAIT request to the LU 6.2 terminal, and received a nonzero return code from terminal control.

The return code is located in the DFHLUC parameter list which is printed in the exception trace.

System action:

The task is abnormally terminated with a transaction dump and an exception trace entry.

User response:

Use the transaction dump to determine why terminal control was unable to process the request. The terminal session may have failed.

Modules:

DFHZXRT

ACWA
Explanation:

CICS CWTO transaction has failed because the task does not own a terminal (TCTTE) as its principal facility. This has probably happened because CWTO has been started as an EXEC CICS START transid without a terminal ID.

System action:

The transaction is abnormally terminated without a transaction dump.

User response:

Retry with a terminal ID value or enter CWTO from a terminal.

Modules:

DFHCWTO

ACXA
Explanation:

The catch-up transaction, CXCU, has failed. CXCU runs either in response to a transaction request from an end-user, or is run automatically by an active CICS system in response to the appearance of an alternative CICS system. Its purpose is to inform the alternate system of the active system’s state regarding terminals and DBCTL connection.

System action:

The catch-up transaction, CXCU, is abnormally terminated with a CICS transaction dump. Both active and alternate CICS systems continue, but the alternate CICS system is less effective in the event of a takeover. For example, terminal back-up sessions may not be established. This abend is accompanied by DFHDX8313.

User response:

Retry by entering ‘CXCU’ from a terminal. If the error persists, diagnose the problem from the dump.

Modules:

DFHCXCU

[[ Contents Previous Page | Next Page Index ]]