CICS Messages and Codes ________________________________________ Abnormal Termination Codes CICS abnormal termination codes This topic describes the abnormal termination codes used by your operating system. Overview of CICS abnormal termination codes Overview of CICS abnormal termination codes If an abnormal condition occurs when CICS is running a transaction, CICS writes a message to the terminal and to the CSMT transient data destination. The message is in the format: TRANSACTION transId PROGRAM programName ABEND abendCode AT termId where transId is the four-byte transaction identifier. programName is the name of the program that caused the abend abendCode is the abnormal termination code termId is the identifier of the terminal on which the transaction was running. Abnormal termination codes All the CICS transaction abnormal termination codes are four-byte or five-byte alphanumeric codes in the form Amma or Ummnn where A indicates a transaction termination that does not cause the CICS region to be terminated. U indicates a transaction termination that also causes the whole CICS region to be termianted. mm is a two-byte alphanumeric code (A-Z, 0-9), assigned by CICS, to identify the type of abnormal termination code. a is an alphanumeric code assigned by CICS. This code makes a particular abcode unique. nn is a two-digit code assigned by CICS to identify the abnormal termination uniquely within the module. Format of information The information provided for each CICS family abnormal termination code is: • • The abnormal termination code • An explanation of events leading to, or following, the production of the message • The system action that CICS has taken, or is about to take • User response - the suggested action that you should take. Note: Many of these messages state that CICS produces a transaction or system dump on abnormal termination. Actually this only occurs when the relevant attributes in the Region Definitions (RD) and in the Transaction Definitions (TD) are set to enable a dump. For more information, see the CICS Administration Reference and the CICS Administration Guide. AA4A Explanation: The debugging support runtime code encountered an error while trying to send some text output to the screen. This may be due to your cicsterm session being unavailable to CICS. Further information may be available in one of the CICS message files. System Action: CDCN terminates abnormally. User Response: Check that the cicsterm session in which CDCN is running is still active. Check that the screen is properly connected and configured. Refer to any associated messages in the CICS symptom records and console.msg files for further guidance on resolving the problem. AA41 Explanation: CDCN has encountered a problem trying to read BMS input from the screen. This may be due to your cicsterm session being unavailable to CICS. Further information may be available in one of the CICS message files. System Action: CDCN terminates abnormally. User Response: Check that the cicsterm session in which CDCN is running is still active. Check that the screen is properly connected and configured. Refer to any associated messages in the CICS symptom records and console.msg files for further guidance on resolving the problem. AA42 Explanation: CDCN has encountered an error while trying to send some BMS output to the screen. This may be due to your cicsterm session being unavailable to CICS. Further information may be available in one of the CICS message files. System Action: CDCN terminates abnormally. User Response: Check that the cicsterm session in which CDCN is running is still active. Check that the screen is properly connected and configured. Refer to any associated messages in the CICS symptom records and console.msg files for further guidance on resolving the problem. AA43 Explanation: CDCN tried unsuccessfully to receive any options specified when CDCN was invoked. This may be due to your cicsterm session being unavailable to CICS. Further information may be available in one of the CICS message files. System Action: CDCN terminates abnormally. User Response: Check that the cicsterm session in which CDCN is running is still active. Check that the screen is properly connected and configured. Refer to any associated messages in the CICS symptom records and console.msg files for further guidance on resolving the problem. AA44 Explanation: CDCN encountered an error while trying to obtain information about the current terminal from the region database. Further information may be available in one of the CICS message files. System Action: CDCN terminates abnormally. User Response: Ensure that the terminal definition is installed correctly in the region database. Refer to any associated messages in the CICS symptom records and console.msg files for further guidance on resolving the problem. AA45 Explanation: CDCN tried unsuccessfully to obtain a message from the message catalog. This might happen if your NLSPATH does not point where it should, or if your locale is wrong. System Action: CDCN terminates abnormally. User Response: Verify that CICS has been installed correctly for the locale which you have chosen. AA46 Explanation: An undetermined error has occurred at the start of CDCN execution. Further information may be available in one of the CICS message files. System Action: CDCN terminates abnormally. User Response: Refer to any associated messages in the CICS symptom records and console.msg files for further guidance on resolving the problem. AA47 Explanation: An attempt has been made to start CDCN other than directly from a local terminal, but CDCN can only be invoked directly from a terminal that is local to the CICS region. System Action: CDCN terminates abnormally. User Response: Invoke CDCN directly from a cicsterm that is on the same system as the CICS region. AA48 Explanation: CDCN has encountered an error while trying to send some text output to the screen. This may be due to your cicsterm session being unavailable to CICS. Further information may be available in one of the CICS message files. System Action: CDCN terminates abnormally. User Response: Check that the cicsterm session in which CDCN is running is still active. Check that the screen is properly connected and configured. Refer to any associated messages in the CICS symptom records and console.msg files for further guidance on resolving the problem. AA49 Explanation: The debugging support runtime code tried unsuccessfully to obtain a message from the message catalog. This might happen if your NLSPATH does not point where it should, or if your locale is wrong. System Action: The CDCN transaction terminates abnormally. User Response: Verify that CICS has been installed correctly for the locale which you have chosen. ABMB Explanation: The user has specified a cursor position in the BMS output request. It is larger than the current screen size for the 3270 for which output is being built. System Action: The transaction is abnormally terminated with a CICS transaction dump. User Response: Correct the program that specified the incorrect cursor location. Use trace to identify the statement issuing the request. Check that the cursor position is being correctly set. The program may have been designed to run in alternate screen size mode but is being run in default screen size mode, or it may have been designed to run on a 3270 model different from the one in use. If the program is routing a message, the route list should be checked. If the program is to run with various 3270 models, the cursor position should be within the size of the smallest screen. ABMI Explanation: The map specified for a BMS input mapping request was not an input map. System Action: The transaction is abnormally terminated with a CICS transaction dump. User Response: Either define another input map or redefine the existing map. ABMM Explanation: The program specified an invalid map. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: Verify that the mapset has been compiled with a version of cicsmap compatible with the CICS region. Also, check that the pathname in the program definitions (PD) points to a valid mapset. ABMO Explanation: The program specified a map that was not an output map, for a Basic Mapping Support (BMS) output mapping request. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: Either define another output map or redefine the existing map. ABM0 Explanation: The program specified a map that CICS could not locate, for a Basic Mapping Support (BMS) request. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: Check whether the program specified the map correctly, and that the map is defined. ABM3 Explanation: A non terminal-oriented transaction issued a Basic Mapping Support (BMS) input or output request. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: The task issuing a BMS input or output request must be attached to a terminal. ADPL Explanation: A server program has issued a command which is restricted in the distributed program link (DPL) environment. Certain API and CPI-RR requests, and the DL/I terminate request are not allowed in the list of these restricted commands. See the CICS Intercommunication Guide. System Action: CICS abends the transaction with a transaction dump. User Response: Remove the restricted commands from the server program, or run the server program locally. AEIA to AEY3 Explanation: CICS detected an exceptional condition for which no EXEC CICS HANDLE CONDITION command is active and the RESP or NOHANDLE option is not included in the associated command. Because of their similar characteristics, these abnormal termination codes for the EXEC interface program are described as a group. The codes and their corresponding exceptional conditions are as follows: Code Condition Code Condition AEIA ERROR AEID EOF AEIE EODS AEIG INBFMH AEIH ENDINPT AEII NONVAL AEIJ NOSTART AEIK TERMIDERR AEIL FILENOTFOUND AEIM NOTFND AEIN DUPREC AEIO DUPKEY AEIP INVREQ AEIQ IOERR AEIR NOSPACE AEIS NOTOPEN AEIT ENDFILE AEIU ILLOGIC AEIV LENGERR AEIW QZERO AEIZ ITEMERR AEI0 PGMIDERR AEI1 TRANSIDERR AEI2 ENDDATA AEI3 INVTSREQ AEI8 TSIOERR AEI9 MAPFAIL AEXL DISABLED AEYA INVERRTERM AEYB INVMPSZ AEYC IGREQID AEYE INVLDC AEYG JIDERR AEYH QIDERR AEYJ DSSTAT AEYK SELNERR AEYL FUNCERR AEYM UNEXPIN AEYN NOPASSBKRD AEYO NOPASSBKWR AEYP SEGIDERR AEYQ SYSIDERR AEYR ISCINVREQ AEYT ENVDEFERR AEYU IGREQCD AEYV SESSIONERR AEYX USERIDERROR AEYY NOTALLOC AEYZ CBIDERR AEY0 INVEXITREQ AEY1 INVPARTNSET AEY2 INVPARTN AEY3 PARTNFAIL System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: Change the application program either to prevent the condition recurring, to check the condition using the RESP option, or to handle the condition when it does occur (by using the EXEC CICS HANDLE CONDITION command). You can use the EIBRESP2 and EIBRCODE fields in the EXEC Interface Block (EIB) to help you determine the cause of the exceptional condition. AEY7 Explanation: A resource security check has failed. A transaction's Transaction Definition (TD) entry has requested resource security checking but this has been unsuccessful for one of the following reasons: • • The transaction is not a terminal transaction • The resource security specified in the relevant resource definitions entry is not matched by the resource security authorization for your user identifier. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: If you require access to this resource, ensure that you remove the reason why access was unsuccessful. RSLCheck=internal(CICS to perform resource security checks) is the default for the CICS-supplied transactions; CECI, CEDF, CEBR, CSMI, CSM1, CSM2, CSM3, and CSM5. If you wish to remove resource security checking for these or any other transactions, you should define the transaction in the TD, specifying RSLCheck=none. In the case of CEDF, the resource security checking is applied to the transaction under test (not to CEDF itself). Specifying RSLCheck=none for the CEDF transaction prevents the checks being applied to the transaction under test, unless you specify RSLCheck=internalor RSLCheck=external, explicitly for that transaction. AEY9 Explanation: You have named the local region in the SYSID option of a command and the underlying resource is marked as being remote. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: Correct the transaction so that it does not use the SYSID option, or correct the resource definition so that it does not point to a remote system. AICA Explanation: A task has been executing for longer thatn the MaxTaskCPU time. This abend indicates a possible loop in the application. See the accompanying ERZ014039E messages for further information. System Action: The task is terminated with a transaction dump. User Response: Identify the failing task and investigate the possible causes for the excessive CPU usage. AIS9 Explanation: The mirror program has detected that a DPL server program has returned in an invalid state following the completion of the LINK command. The server program or a program it linked to has initiated a synclevel 2 conversation with another program which in turn has issued a syncpoint. The server program has not responded to the syncpoint request which is still outstanding when control returns to the mirror program. The mirror program only issues this abend code if the LINK request did not specify SYNCONRETURN TURN. System Action: The task is abnormally terminated with a transaction dump User Response: Correct the design of the DTP application or applications initiated by the server program. If the SYNCONRETURN option is not specified on the LINK request, only the client program should initiate the syncpoint. If it is necessary to issue syncpoint requests from the DTP applications, consider using the SYNCONRETURN option on the LINK request. AKCS Explanation: CICS detected a deadlock timeout condition. This condition may occur within any transaction defined with a non-zero DeadLockTimeout attribute in the Transaction Definitions (TD). Deadlock timeout occurs when a transaction waits for longer than the time specified in DeadLockTimeout. (Note: the DeadLockTimeout attribute is specified in seconds.) System Action: CICS abnormally terminates the transaction, but does not produce a transaction dump. User Response: You should re-run the transaction because the situation causing the transaction to wait, may well clear itself. If this does not solve the problem, try increasing the value of the DeadlockTimeout attribute to the maximum acceptable value. If this does not solve the problem, please read Problem Determination. AKCT Explanation: CICS has detected a terminal read-time-out condition. The transaction has been waiting for a terminal input message for an interval longer than that specified in Timeout in the Transaction Definitions. (Note: The Timeout attribute is specified in minutes.) System Action: CICS abnormally terminates the transaction, but does not produce a transaction dump. User Response: Check if the Timeout limit was set to be too short. APCN Explanation: An attempt has been made to release an object that is not correctly loaded. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: Determine in your application why more deletes for a program, table or map set than loads were issued. APCT Explanation: A requested program entry in the Program Definitions (PD) is disabled, or the program has zero length, or an I/O error has occurred while loading the program. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: Determine why the PD entry is disabled, or incorrect, or why the program has zero length. If an I/O error occurred previous error messages may indicate the source of the error ASRA Explanation: The task has terminated abnormally because of a signal or exception. System Action: CICS abnormally terminates the transaction, and produces a transaction and possibly a system dump. User Response: Determine and correct the cause of the signal or exception. ASRB Explanation: The task has terminated abnormally because of an incorrect system call. System Action: CICS abnormally terminates the transaction and produces a transaction and possibly a system dump User Response: Determine and correct the cause of the incorrect system call. ATCV Explanation: An application attempted an operation with an LU6.2 system, but was not in a valid state to attempt this operation, for one of the following reasons: • • The application is communicating with an LU6.2 system, and is not in the correct state to perform the attempted operation. • The application is using function shipping and a SYNCPOINT ROLLBACK was required but not performed. This abnormal termination also occurs when CICS cannot communicate with a terminal. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: Investigate the problem, using either the transaction dump or a debugging aid. Possible debugging aids include CEDF, Trace, ANIMATOR, and dbx. For information about transaction dumps, please read Problem Determination. Correct the transaction and submit it again. However, if the abnormal termination is due either to the user deliberately closing his terminal or to some component such as rpcs timing out then check console.msg. If console.msg indicates the cause, when it is necessary, you should correct the problem. ATDD Explanation: The transaction attempted to access a Transient Data (TD) queue that is disabled. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: Check why the queue is disabled. For information about transaction dumps, please read Problem Determination. ATNI Explanation: CICS decides to abnormally terminate the transaction. This abend code occurs if the TERMERR condition is not handled. This abend occurs when a conversation is abnormally terminated. Conversations being abnormally terminated may be due to both software and hardware causes. It is impossible for CICS to know why a conversation was abnormally terminated. In the case of a tty or cicsteld terminal, this abend is the result of the physical terminal (or window) losing contact with CICS. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: For investigation of the failure you should first look for logged messages on the local and the remote systems. Further investigation may be required using the facilities offered by the other communication components involved (such as AIX SNA Services/6000). AZI4 Explanation: An IRC data transmission request has been issued, but cannot be completed because the other system has become unavailable for interregion communication. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: Rerun the transaction when interregion communication is available. AZI6 Explanation: The transaction was connected to another transaction in another CICS system via an IRC link. This other transaction has abnormally terminated. System Action: CICS abnormally terminates the transaction, and produces a CICS transaction dump. User Response: Correct the cause of the abend in the connected transaction. A011 Explanation: An error in a COBOL transaction program caused a COBOL runtime system error to occur during the execution of the program. System Action: The transaction terminates abnormally. User Response: Look in console.msg for the COBOL runtime system error message. For further information about the error, look up the error number in the Micro Focus COBOL Error Messages manual. If the error number is 187 (Runtime system not found on $COBDIR path) check that COBOL is properly installed and that the $COBDIR environment variable is properly set up for the region. Otherwise correct the error in your COBOL program. A012 Explanation: An error in an IBM COBOL transaction program caused an IBM COBOL runtime system error to occur during the execution of the program. System Action: The transaction terminates abnormally. User Response: Look in console.msg for the IBM COBOL runtime system error message. For further information about the error, look up the error number in the relevant IBM COBOL documentation. A013 Explanation: An error in an IBM PL/I transaction program caused an IBM PL/I runtime system error to occur during the execution of the program. System Action: The transaction terminates abnormally. User Response: Look in console.msg for the IBM PL/I runtime system error message. For further information about the error, look up the error number in the relevant IBM PL/I documentation. A014 Explanation: An unexpected error occurred during initialisation of a CICS Java task. This may be a system problem such as a shortage of memory, or an internal error. System Action: The transaction terminates abnormally. User Response: Look in console.msg for a Java exception message. A015 Explanation: An unexpected exception was generated by a CICS Java program. System Action: The transaction terminates abnormally. User Response: There will be additional CICS messages in CSMT and a Java exception message in console.msg. Examine these to determine the cause of the problem and rectify if possible. A031 Explanation: The CICS Command Level Interpreter (CECI) tried unsuccessfully to read user input from the screen. System Action: CECI terminates abnormally. User Response: Check that the cicsterm session in which CECI is running is still active. Check that the screen is properly connected and configured. Check the symptom records for any related information. A032 Explanation: The CICS Command Level Interpreter (CECI) tried unsuccessfully to obtain Task Private storage. CECI breached the CICS task private pool storage threshold. System Action: CECI terminates abnormally. User Response: Shut down the CICS region and reconfigure the task private storage pool size (MaxTaskPrivatePool) attribute in the Region Definitions or by overriding the Region Definitions on the CICS command line. A033 Explanation: An undetermined error has occurred during execution of the CICS Command Level Interpreter (CECI or CECS). Further information may be available in one of the CICS message files. System Action: CECI/CECS terminates abnormally. User Response: Refer to any associated messages in the CICS message files for further guidance on resolving the problem. A07A Explanation: A START command is invalid. This may be because there was an attempt to START a CICS-private transaction, or because a transaction was started at an inappropriate phase of region operation, or on an invalid terminal. User Response: Check that the value of the InvocationMode attribute in the Transaction Definitions of the transaction you want to START is appropriate. A07B Explanation: There is insufficient memory available in the Region Pool to perform an Interval Control operation A07C Explanation: The definitions for a transaction that has been specified as the trigger transaction for a temporary data queue indicate that the transaction is to be routed to another system. This is invalid. User Response: Consider changing the transaction definitions (TD) so the transaction has a blank RemoteSysId. Alternatively, you could change the transient data definitions (TDD) so that the TriggeredTransId contains the name of a transaction that is run locally. A101 Explanation: CICS has detected an exceptional condition while executing in CICS code. System Action: CICS abnormally terminates the transaction and the application server where the exception was detected. User Response: This abend indicates a CICS internal problem. You should save any dump file produced and contact your support organization. A10A Explanation: CICS was unable to set up the message catalog. Messages will have been logged to indicate the nature of the problem. System Action: The transaction abnormally terminates. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. A10C Explanation: CICS was unable to register as an Application Server. Messages will have been logged to indicate the nature of the problem. System Action: The transaction abnormally terminates. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. A10D Explanation: CICS was unable to initialize a process. System Action: The transaction abnormally terminates. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. A10E Explanation: An operation failed during an RPC call. System Action: The transaction abnormally terminates. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. A11A Explanation: The terminal autoinstall was unsuccessful. System Action: Terminal installation terminates abnormally. User Response: Examine the CSMT message log for possible causes. A11B Explanation: The terminal installation was unsuccessful because another terminal is already installed using the same netname. System Action: Terminal installation terminates abnormally. User Response: Install using a different netname, or alternatively autoinstall the terminal by omitting the netname. A11D Explanation: There is a problem with CICS Task Private storage. System Action: Autoinstall or uninstall terminates abnormally. User Response: Retry the operation. If still unsuccessful, stop CICS and try again. Contact your support organization if the problem persists. A11F Explanation: The terminal installation was unsuccessful because there is no entry in the Terminal Definitions (WD) for the specified netname. System Action: Terminal installation terminates abnormally. User Response: Install using a different netname, or add a WD entry for this netname, or alternatively autoinstall the terminal by omitting the netname. A11M Explanation: CICS is short of Task Private storage and a storage allocation request for a terminal operation could not be satisfied. System Action: The transaction terminates abnormally. User Response: Retry the transaction. If it is still unsuccessful, check that this transaction is not using a lot of storage. If it is not, check for any other transactions using a lot of storage. A11N Explanation: Your attempt to autoinstall a terminal has been unsuccessful because there are no terminal models defined in the Terminal Definitions (WD) with DevType matching the model you requested. The model may be requested by setting either the $CICSTERM or the $TERM variable, or by specifying the -m option on the cicsterm command. System Action: Terminal installation terminates abnormally. User Response: Either add an entry to the WD with DevType matching your requested model, or set $CICSTERM to match an existing DevType entry in the WD, or specify -m using an existing DevType entry in the WD. A11P Explanation: The terminal installation was unsuccessful because the Terminal Definition (WD) for this netname is not consistent with the installation type. This occurs when you try to install a printer using a non-printer definition, or when you try to install a terminal using a printer definition. System Action: Terminal installation terminates abnormally. User Response: Check the netname used is correct. Check the definition for this netname to ensure that it defines a printer or a terminal as required. A11T Explanation: The terminal installation was unsuccessful. System Action: Terminal installation terminates abnormally. User Response: Examine the CSMT message log for possible causes. A11U Explanation: The autoinstall user-exit program could not be run or rejected the autoinstall request. System Action: Autoinstall or uninstall terminates abnormally. User Response: Check that the autoinstall user-exit program exists. It is specified in the Program Definitions (PD) for the program associated with the CICS private CHAT transaction in the Transaction Definitions (TD). If you have replaced the autoinstall user-exit program, investigate why the program rejected the request. A11W Explanation: The terminal uninstall was unsuccessful because the Terminal Definitions (WD) entry for this netname could not be updated. System Action: The terminal uninstall terminates abnormally. User Response: Examine the CSMT message log for possible causes. A121 Explanation: An unexpected error has occurred during CESN execution. System Action: CESN terminates abnormally. User Response: Check the symptom records and console.msg for any related information. A122 Explanation: CESN has encountered an error while trying to send some information to, or read your input from, the screen. Your terminal session may be unavailable to CICS. Further information may be available in one of the CICS message files. System Action: CESN terminates abnormally. User Response: Check that the terminal session in which CESN is running is still active. Check that your screen is properly connected and configured. Refer to any associated messages in the CICS message files for further guidance on resolving the problem. A124 Explanation: CESN tried unsuccessfully to obtain a message from the message catalog. System Action: CESN terminates abnormally. User Response: Verify that CICS has been installed correctly for the locale which you have chosen. A125 Explanation: CESN tried to do some work on the terminal on which it was running, but received an error. System Action: CESN terminates abnormally. User Response: Verify that CICS has been installed correctly on your machine. Ensure that the the terminal on which CESN is running has been autoinstalled correctly. A126 Explanation: You tried to change your DCE password using CESN, but there was an error on one of the DCE calls. System Action: CESN terminates abnormally. User Response: See the previous message in the console.msg file for more A141 Explanation: CICS detected an unrecoverable error during transaction initialization. System Action: CICS does not start the transaction User Response: This abend indicates a problem during the initialization of the transaction. You should examine the messages written to CSMT and console.msg to determine the actual problem. Refer to the documentation associated with the messages for further guidance on resolving the problem and subsequent action. A142 Explanation: CICS detected an exceptional condition while executing in CICS code. System Action: CICS abnormally terminates the transaction and the application server where the exception was detected. User Response: This abend indicates a CICS internal problem. You should save any dump file produced and contact your support organization. A143 Explanation: CICS was unable to satisfy the task private storage allocation requirements during transaction initialization. System Action: CICS does not start the transaction User Response: This abend indicates that CICS was unable to allocate sufficient task private storage to start the transaction. You should examine the messages written to CSMT and console.msg to determine the actual problem. Refer to the documentation associated with the messages for further guidance on resolving the problem and subsequent action. A144 Explanation: No initial program has been defined for the transaction. System Action: CICS does not start the transaction User Response: The transaction is not executable either because there is no initial program specified in the ProgName attribute in the transaction definition, or because the ProgName attribute refers to a program for which there is no corresponding program definition, or the program is disabled, or because the dynamic transaction routing program has returned a null program name. Either correct the transaction definition to specify the name of the initial program, or create a program definition entry matching the program specified by the ProgName attribute, or ensure that the dynamic transaction routing program returns a program name. Re-submit the transaction request. A145 Explanation: CICS detected an unrecoverable error during transaction initialization within a CRTE session. System Action: CICS abnormally terminates the transaction. User Response: This abend indicates a CICS internal problem during the initialization of a new transaction to run within the environment created by CRTE. You should examine the messages written to CSMT and console.msg to determine the actual problem. Refer to the documentation associated with the messages for further guidance on resolving the problem and subsequent action. A146 Explanation: One of the authorization checks made at transaction initialization was unsuccessful. System Action: CICS does not start the transaction User Response: This abend indicates a problem detected by the authorization checks made during the initialization of the transaction. Examine the messages written to CSMT and console.msg to determine the actual problem. Refer to the documentation associated with the messages for further guidance on resolving the problem and subsequent action. A147 Explanation: The transaction has been purged. System Action: CICS abnormally terminates the transaction. User Response: This abend indicates the transaction has been purged, either via CEMT, or as the result of an immediate region shutdown, or because an exceptional condition has been detected. Re-submit the transaction. A148 Explanation: CICS is terminating a transaction and has found that a Logical Unit of Work needs committing. However, the attempt to commit has resulted in a Syncpoint Rollback because some other participant cannot commit due to a fatal problem. System Action: CICS abnormally terminates the transaction with code A148. User Response: You should examine the messages written to CSMT and console.msg to determine the actual problem. Check that the file server is still running, correct any other errors and retry the transaction. Refer to the documentation associated with the messages for further guidance on resolving the problem and subsequent action. A149 Explanation: The dynamic transaction routing user exit (UE014025) returned a return code of UE_Term_Abend. System Action: CICS does not start the transaction User Response: This abend indicates that your dynamic transaction routing user exit returned a code of UE_Term_Abend. If the abend was not expected check your dynamic transaction routing program to discover why this return code has been set. A150 Explanation: The dynamic transaction routing user exit (UE014025) was not active when a dynamic transaction was started. System Action: CICS does not start the transaction User Response: A dynamic transaction should not be started while the dynamic transaction routing program is not active. Refer to the documentation associated with the messages for further guidance on resolving the problem and subsequent action. A151 Explanation: CICS is unable to allocate storage for a COMMAREA from the Task-Private Pool, to be passed to a program during an EXEC CICS XCTL. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: Resubmission of the transaction may work. If not, determine if the transaction is using excessive amounts of Task-Private Pool (Getmain) storage and correct this. A152 Explanation: CICS is unable to release some Task-Private Pool storage allocated for Program Control data structures. These data structures hold information about programs running at each logical level. System Action: CICS abnormally terminates the transaction and the application server in which it was running. User Response: This problem is unlikely to be caused by application code. If the problem reoccurs, save any dump file produced and contact your support organization. A153 Explanation: CICS is unable to run a program due to lack of space in the Region Pool or Task-Private Pool for Program Control data structures. These data structures hold information about programs running at each logical level. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: The message logged earlier can be used to determine which storage Pool was empty (ERZ15005 or ERZ1534). If the Region Pool is empty, then because memory in the Region Pool is continually being acquired and freed by CICS on behalf of running transactions, resubmission of this transaction may be successful. If this problem persists when you resubmit the transaction, check whether it is looping in some way that causes CICS to acquire substantial amounts of Region Pool memory on its behalf; for example check the depth of EXEC CICS LINKs in the program, as Region Pool memory is required for each logical level. Finally, consider increasing the size of the Region Pool by restarting the region with an override for the value of the MaxRegionPool attribute in the Region Definition (RD). If the Task-Private Pool is empty, resubmission of the transaction may work. If not, determine if the transaction is using excessive amounts of Task-Private Pool (Getmain) storage and correct this. A154 Explanation: CICS is unable to lock a database entry for the definition of a program being run. This was due to lack of space in the Region Pool. System Action: CICS abnormally terminates the transaction and the application server running the transaction. User Response: Because memory in the Region Pool is continually being acquired and freed by CICS on behalf of running transactions, resubmission of this transaction may be successful. If this problem persists when you resubmit the transaction, check whether it is looping in some way that causes CICS to acquire substantial amounts of Region Pool memory on its behalf; for example check the depth of EXEC CICS LINKs in the program, as Region Pool memory is required for each logical level. Finally, consider increasing the size of the Region Pool by restarting the region with an override for the value of the MaxRegionPool attribute in the Region Definition (RD). A155 Explanation: CICS is unable to unload a program, previously loaded by an application server. System Action: CICS abnormally terminates the transaction and the application server in which it was running. User Response: Check the symptom record file for any operating system specific failure. The problem could also be caused by incorrect application code, so check for this in the transaction that failed. A156 Explanation: CICS is unable to allocate storage for a COMMAREA from the Task-Shared Pool, to be passed to another transaction via an EXEC CICS RETURN. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: Because memory in the Task-Shared Pool is continually being acquired and freed by running transactions, resubmission of this transaction may be successful. If this problem persists when you resubmit the transaction, check whether any transaction is using large amounts of Task-Shared storage. Finally, consider increasing the size of the Task-Shared Pool by restarting the region with an override for the value of the MaxTSHPool attribute in the Region Definition (RD). A158 Explanation: An exception is caught while running in CICS code. Possible causes of the exception are an invalid argument on an EXEC CICS command or a CICS internal problem. System Action: The transaction and application server running the transaction are abnormally terminated. User Response: Inspect the symptom record file for symptom records that indicate why the exception occurred. Investigate the abend using appropriate debugging tools (for example: CEDF, ANIMATOR). If the exception appears to occur on a particular EXEC CICS command, and some form of address exception is indicated, carefully check all arguments specified on the EXEC CICS command and correct the program if necessary. Otherwise, this is probably a CICS internal problem. Any dump file produced should be saved. If the problem persists, contact your support organization. A159 Explanation: CICS is unable to redirect the debugger IO to the specified terminal. The given terminal could not be opened as a file. System Action: The transaction is abnormally terminated. User Response: Look up the error number in errno.h and investigate the cause. A15A Explanation: CICS is unable to load the Micro Focus COBOL for UNIX language support program cicsprCOBOL. cicsprCOBOL is used to load and run COBOL application programs. System Action: CICS abnormally terminates the transaction. User Response: Investigate the cause of the load failure using the ERZ015035E error message logged earlier and the symptom records. Check that the full pathname of cicsprCOBOL recorded in error message ERZ015035E refers to a valid executable file which is accessible. If this file does not exist contact your system administrator, because Micro Focus COBOL for UNIX support may not be installed on CICS, or the CICS installation may have become corrupted. In this last case the system administrator can consider reinstalling CICS and Micro Focus COBOL for UNIX support for CICS. If the problem cannot be solved and persists, contact your support organization. A15F Explanation: CICS is unable to find the database record for the principal facility, during an EXEC CICS RETURN TRANSID COMMAREA command. System Action: CICS abnormally terminates the transaction and the application server in which it was running with abend code A15F. User Response: Save any dump file produced. This error is likely to be caused by a CICS inconsistency, rather than incorrect applications. If the problem reoccurs, contact your support organization. A15Z Explanation: CICS has caught a processing exception for a user exit System Action: CICS abnormally terminates the transaction and the application server in which it was running with abend code A15Z. User Response: Save any dump file produced. Examine the console for any associated messages indicating changes in the status of the associated user exit program. Refer to message ERZ015037E for further actions. A161 Explanation: The CICS Transaction Manager component (TRAN) has decided to terminate and backout a logical unit of work immediately, without waiting for a syncpoint. This frequently means that some other participant, such as a Structured File Server (SFS), involved in the transaction has had a fatal problem and so there is no point in continuing the transaction any further. System Action: CICS abnormally terminates the transaction with code A161. User Response: Check that all Structured File Servers are still running normally, and all Distributed Transaction Processing (DTP) clients. Restart any components which have failed and retry the transaction. A162 Explanation: CICS is unable to start a new logical unit of work in a particular application server. A new logical unit of work was obtained from the Transaction Manager, but it had already been abnormally ended before CICS had made it ready for use. System Action: See ERZ016049E. User Response: See ERZ016049E. A163 Explanation: CICS is unable to acquire Region Pool storage for the data structures needed to process an active logical unit of work. System Action: See ERZ016009E. User Response: See ERZ016009E. A164 Explanation: CICS is unable to start a new logical unit of work. This message is preceded by another message indicating the reason. System Action: See ERZ016004E. User Response: See ERZ016004E. A165 Explanation: CICS has detected an internal error which has prevented a logical unit of work from starting or continuing. System Action: See ERZ016005E. User Response: See ERZ016005E. A166 Explanation: CICS is attempting to syncpoint, but cannot complete successfully. This means either that heuristic damage has been detected by the Program to Program Communication (PPC) component of CICS, or that a CICS internal error has occurred. In either case additional error messages are produced. System Action: The affected transaction is abnormally terminated with code A166. User Response: See the additional error messages produced for further information. Retry the transaction and call your support organization. if the problem persists. A16E Explanation: CICS is unable to allocate Region Pool storage for the registration of an External Resource Manager. System Action: See ERZ016048E. User Response: See ERZ016048E. A16H Explanation: CICS has detected heuristic damage affecting the transaction being abnormally terminated. System Action: See ERZ016056W. User Response: See ERZ016056W. A16Z Explanation: CICS is unable to complete the initialization of an application server. This message may be preceded by a warning message describing the problem in more detail. System Action: See ERZ016026E. User Response: See ERZ016026E. A171 Explanation: The table holding information about active ABEND, Attention IDentifier (AID), and condition handlers, in the Region Pool, contains invalid data. System Action: The transaction and the application server in which it is running are both abnormally terminated, but the CICS region continues. User Response: Because the Action Table is held in the Region Pool it is unlikely that the invalid data has been produced by application code. It is possible that there are further inconsistencies in the Region Pool; you may find that the CICS self-consistency checking transaction detects this. If the transaction produces a dump file, you should save it for possible use by your support organization. If the problem persists, contact your support organization. A175 Explanation: CICS could not acquire storage to create a new Action Table from the Region Pool. This table holds information about active ABEND, Attention IDentifier (AID), and condition handlers. System Action: The transaction and the application server in which it is running are both abnormally terminated, but the CICS region continues. User Response: Because memory in the Region Pool is continually being acquired and freed by CICS on behalf of running transactions, resubmission of this transaction may be successful. If this problem persists when you resubmit the transaction, check whether it is looping in some way that causes CICS to acquire substantial amounts of Region Pool memory on its behalf; for example check the depth of EXEC CICS LINKs in the program, as an Action Table is built for each logical level. Finally, consider increasing the size of the Region Pool by restarting the region with an override for the value of the MaxRegionPool attribute in the Region Definition (RD). A177 Explanation: The stack of tables holding information regarding active ABEND, Attention IDentifier (AID), or condition handlers for the program at each logical level contains invalid data. System Action: The transaction and the application server in which it is running are both abnormally terminated, but the CICS region continues. User Response: Because the Action Tables are held in the Region Pool it is unlikely that the invalid data has been produced by application code. It is possible that there are further inconsistencies in the Region Pool; you may find that the CICS self-consistency checking transaction detects this. If the transaction produces a dump file, you should save it for possible use by your support organization. If the problem persists, contact your support organization. A178 Explanation: During an EXEC CICS HANDLE ABEND PROGRAM command, CICS could not lock a handle abend program database entry due to lack of space in the Region Pool. System Action: The transaction and the application server in which it is running are both abnormally terminated, but the CICS region continues. User Response: Because memory in the Region Pool is continually being acquired and freed by CICS on behalf of running transactions, resubmission of this transaction may be successful. If this problem persists when you resubmit the transaction, check whether it is looping in some way that causes CICS to acquire substantial amounts of Region Pool memory on its behalf; for example check the depth of EXEC CICS LINKs in the program, as storage is required for for each logical level. Finally, consider increasing the size of the Region Pool by restarting the region with an override for the value of the MaxRegionPool attribute in the Region Definition (RD). A179 Explanation: CICS could not acquire storage to create a new table for storing AIDs handlers from the Region Pool. This occurred during an EXEC CICS HANDLE AID command. System Action: The transaction and the application server in which it is running are both abnormally terminated, but the CICS region continues. User Response: Because memory in the Region Pool is continually being acquired and freed by CICS on behalf of running transactions, resubmission of this transaction may be successful. If this problem persists when you resubmit the transaction, check whether it is looping in some way that causes CICS to acquire substantial amounts of Region Pool memory on its behalf; for example check the depth of EXEC CICS LINKs in the program, as Region Pool storage is required for each logical level. Finally, consider increasing the size of the Region Pool by restarting the region with an override for the value of the MaxRegionPool attribute in the Region Definition (RD). A17A Explanation: CICS could not acquire storage to create a new table for storing condition handlers from the Region Pool. This occurred during either an EXEC CICS HANDLE CONDITION or EXEC CICS IGNORE CONDITION command. System Action: The transaction and the application server in which it is running are both abnormally terminated, but the CICS region continues. User Response: Because memory in the Region Pool is continually being acquired and freed by CICS on behalf of running transactions, resubmission of this transaction may be successful. If this problem persists when you resubmit the transaction, check whether it is looping in some way that causes CICS to acquire substantial amounts of Region Pool memory on its behalf; for example check the depth of EXEC CICS LINKs in the program, as Region Pool storage is required for each logical level. Finally, consider increasing the size of the Region Pool by restarting the region with an override for the value of the MaxRegionPool:ehp2. attribute in the Region Definition (RD). A17G Explanation: This is the abend code used if one of the conditions: QBUSY, NOSTG, NOJBUFSP, ENQBUSY, SYSBUSY, when raised results in an abnormal termination of a program. System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17H Explanation: This is the abend code used if the condition WRONGSTAT, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17I Explanation: This is the abend code used if the condition NAMEERROR, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17J Explanation: This is the abend code used if the condition CCERROR, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17K Explanation: This is the abend code used if the condition MAPERROR, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17L Explanation: This is the abend code used if the condition NOSPOOL, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17M Explanation: This is the abend code used if the condition ROLLEDBACK, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17N Explanation: This is the abend code used if the condition END, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17O Explanation: This is the abend code used if the condition ALLOCERR, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17P Explanation: This is the abend code used if the condition STRELERR, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17Q Explanation: This is the abend code used if the condition SPOLBUSY, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17R Explanation: This is the abend code used if the condition SPOLERR, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17S Explanation: This is the abend code used if the condition NODEIDERR, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17T Explanation: This is the abend code used if the condition TCIDERR, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A17U Explanation: This is the abend code used if the condition TASKIDERR, when raised results in an abnormal termination of a program (the default action for the condition). System Action: If there is no abend handler at any active logical level which clears the abend, then the transaction is abnormally terminated with this abend code. Otherwise the abend handler is executed and the transaction continues. User Response: Find which EXEC CICS command raised the condition. Then investigate why the condition is raised. Either stop the condition being raised, or change the program to handle or ignore the condition. A194 Explanation: An attempt to allocate storage from the Region Pool to contain EDF control information was unsuccessful. System Action: CICS abnormally terminates the application server and issues message ERZ019004E. The CICS region continues. User Response: As memory in the Region Pool is continually being acquired and freed by CICS on behalf of running transactions, this may be a transient problem that could occur when CICS is heavily loaded. Try turning EDF on and then running the transaction again. If this problem persists when you resubmit the transaction, check whether it is looping in some way that causes CICS to acquire substantial amounts of Region Pool memory on its behalf; for example check the depth of EXEC CICS LINKs in the program, as Region Pool memory is required for each logical level. Finally, consider increasing the size of the Region Pool by restarting the region with an override for the value of the MaxRegionPool attribute in the Region Definition (RD). A195 Explanation: An attempt to read an EDF message from the CICS message catalogue was unsuccessful. System Action: CICS abnormally terminates the application server. The CICS region continues. User Response: Check that the CICS catalog file for the region is accessible and has the required permissions. Refer to the operating system documentation for further information about the use of catalogs. A19D Explanation: EDF attempted to alter EDF control information in the database entry for the named terminal but was unable to access the Terminal Definition in the runtime database. System Action: CICS abnormally terminates the application server. The CICS region continues. User Response: Examine the CICS message logs as CICS may have logged other messages which indicate why the attempt to access the runtime database was unsuccessful. A19E Explanation: EDF attempted to alter EDF control information in the database entry for the named system but was unable to access the System Definition in the runtime database. System Action: CICS abnormally terminates the application server. The CICS region continues. User Response: Examine the CICS message logs as CICS may have logged other messages which indicate why the attempt to access the runtime database A21M Explanation: CICS was attempting to obtain memory for file control information. Insufficient memory was available. System Action: The transaction terminates abnormally. User Response: This may be a transient problem that could occur when CICS is heavily loaded. Resubmit the transaction. If the problem persists, you may need to reconfigure the size of an appropriate memory pool and restart CICS. Check the message files for a message regarding which memory pool was full. A21R Explanation: CICS was unable to restore a File Definitions (FD) entry to the region database. System Action: The transaction terminates abnormally. User Response: This is an internal CICS error. Contact your support organization. A21S Explanation: CICS was unable to find a File Definitions (FD) entry in the region database that should exist. System Action: The transaction terminates abnormally. User Response: This is an internal CICS error. A221 Explanation: CICS could not obtain access to a Transient Data (TD) queue prior to performing a read, write, or delete operation on it. CICS could not record the fact that the queue has been accessed. This probably indicates an unsuccessful allocation request from the Region Pool. You can confirm this by searching for other error messages preceding this one. System Action: CICS terminates the transaction with abend code A221. User Response: Check preceding messages for the cause of the error. If it was caused by an unsuccessful allocation request from the Region Pool, the size of the Region Pool may be increased by overriding the MaxRegionPool attribute, on the command line, and restarting the region. A222 Explanation: Logging of recoverable data queue operations requires allocation of storage from the Region Pool. This attempt was unsuccessful. System Action: CICS terminates the transaction with abend code A222. User Response: This indicates a memory allocation failure. You may need to increase the size of the region pool and restart CICS. A223 Explanation: This may occur when the SET option is used in an EXEC CICS READQ TD call or when performing a write to an intrapartition TD queue. In the case of a READQ operation, CICS could not allocate a buffer for return of the queue data. When performing a WRITEQ operation, CICS could not allocate a buffer for formatting the data before passing it to the file server. System Action: CICS terminates the transaction with abend code A223. User Response: This indicates a memory allocation failure. You may need increase the size of the Task-Shared pool and restart CICS. A226 Explanation: During transaction syncpoint, CICS was unable to store recovery information about a Transient Data queue operation in the filesystem. System Action: CICS terminates the transaction with abend code A226. User Response: Check preceding messages for the cause of the error. There may be a problem writing data to the file which contains Transient Data queue records. A227 Explanation: For files used to store intrapartition TD queue data, CICS must obtain file handles when a transaction first operates on a queue. This error arises if CICS cannot obtain a file handle. See previous messages for details of the file server error. System Action: CICS terminates the transaction with abend code A227. User Response: This may indicate an unsuccessful attempt to aquire Region Pool m emory. You may need to increase the size of the Region Pool and restart CICS. A228 Explanation: CICS must log all operations on physically recoverable TD queues as they are performed. CICS generates this error if CICS could not write the log data. CICS may not have performed the queue operation correctly, and may not be able to recover the queue. System Action: CICS disables the queue, and terminates the transaction with abend code A228. User Response: Other messages may indicate the nature of the log service error. You should check the error logs and possibly the log server to ensure that its data is correctly formatted. A229 Explanation: Invalid attempt to delete an extrapartition Transient Data (TD) queue. System Action: CICS terminates the transaction with abend code A229. User Response: Check the program or the queue definition to ensure that the queue name is correctly identified, and that the queue type should be extrapartition. A22A Explanation: CICS was unsuccessful when deleting records from a Transient Data (TD) queue. System Action: CICS terminates the transation with abend code A22A. A22B Explanation: CICS was unsuccessful when opening a file server file storing either logical, physical or non-recoverable Transient Data. System Action: CICS terminates the transaction with abend code A22B. User Response: Look at previous messages to see if there is a problem with the file server. If the file server seems to be working correctly, then you can use file server administration commands to interrogate the status of the file, and its index. Until the file is available again you will not be able to run any transaction using non-recoverable TDQs. A23A Explanation: During transaction syncpoint, CICS was unable to store recovery information about Temporary Storage queue operations in the filesystem. System Action: CICS abnormally terminates the transaction with code A23A. User Response: Check preceding messages for the cause of the error. There may be a problem writing data to the file which contains Recoverable Temporary Storage queue records. A23E Explanation: CICS detected an unexpected return code from CICS file support and was unable to open a file for auxiliary Temporary Storage queues. System Action: CICS abnormally terminates the transaction. User Response: Refer to any file support messages that preceded this message. A23F Explanation: CICS detected an unexpected return code from CICS file support and could not write to an auxiliary queue. System Action: CICS abnormally terminates the transaction. User Response: We recommend that you delete the queue, identified by a preceding ERZ023046E message, from CICS and abnormally terminate any transactions using the queue. Refer to any file support messages that preceded this abnormal termination. A23G Explanation: CICS detected an unexpected return code from CICS file support and could not read from an auxiliary queue. System Action: CICS abnormally terminates the transaction. User Response: We recommend that you delete the queue, identified by a preceding ERZ023047E message, from CICS and abnormally terminate any transactions using the queue. Refer to any file support messages that preceded this message. A23L Explanation: Temporary Storage (TS) was unable to register a Logical Unit of Work for your transaction System Action: CICS abnormally terminates your transaction. User Response: Refer to any previous message detailing why the registration failed and re-run the transaction. A23S Explanation: CICS is unable to allocate enough memory from either the Region Pool, Task-Shared Pool or Task-Private memory. This abend is always preceded by either an ERZ023090E, ERZ023091E or ERZ023092E message that details the type of memory that CICS has been unsuccessful in obtaining. System Action: CICS abnormally terminates the transaction. User Response: As for the preceding ERZ023090E, ERZ023091E or ERZ023092E message. A23T Explanation: CICS detected an unexpected return code from CICS file support and could not delete an auxiliary queue. System Action: CICS abnormally terminates the transaction. User Response: We recommend that you abnormally terminate any transactions using the queue, identified by a preceding ERZ023051E or ERZ023049E message. Refer to any file support messages that preceded this message. A241 Explanation: CICS is unable to create the specified log file. System Action: See ERZ024001E. User Response: See ERZ024001E. A242 Explanation: CICS is unable to configure the specified log file. System Action: See ERZ024002E. User Response: See ERZ024002E. A243 Explanation: CICS is attempting to obtain exclusive access to a user journal's run-time database record, but is unable to do so because of insufficient memory. System Action: See ERZ024074E. User Response: See ERZ024074E. A245 Explanation: CICS cannot open the specified log file. System Action: See ERZ024005E. User Response: See ERZ024005E. A248 Explanation: CICS is attempting to write to a non-crucial user journal but is unable to do so. Possible causes include deadlock timeout, insufficient space on the relevant filesystem and bad destination path specified in the journal definition (JD). System Action: See ERZ024076E. User Response: See ERZ024076E. A24F Explanation: CICS is attempting to save changes made to the specified journal's run-time database record, but is unable to do so. System Action: See ERZ024074E. User Response: See ERZ024074E. A24M Explanation: CICS failed to obtain memory whilst attempting to open a user journal. CICS is unable to create and insert a TDQ runtime database entry corresponding to the user journal because there is insufficient memory in the Region Pool. System Action: See ERZ024072E. User Response: See ERZ024072E. A24S Explanation: CICS failed to obtain memory for a log record because there is insufficient memory in the Region Pool. This means that CICS is unable to make the log record permanent. System Action: See ERZ024062E. A25A Explanation: CICS and the Structured File Server (SFS) are cooperating in processing the current transaction. SFS has reported that it has detected a problem which requires that the transaction be terminated. A25E Explanation: CICS has encountered a problem when attempting to obtain the RBA of a record that it is inserting to a Structured File Server (SFS) file. A25F Explanation: CICS could not perform an operation on the structured file system, as the transaction that was being used has been asynchronously terminated. System Action: CICS writes a message to CSMT and terminates the transaction. A25L Explanation: CICS was unsuccessful when attempting to retain a transactional lock on a record. A25M Explanation: CICS was attempting to obtain memory for file control information from the Region Pool. Insufficient memory was available. A261 Explanation: CEBR tried unsuccessfully to obtain a message from the message catalog. System Action: CEBR terminates abnormally. User Response: Verify that CICS has been installed correctly for the locale which you have chosen. A262 Explanation: CEBR tried unsuccessfully to write to the screen. System Action: CEBR terminates abnormally. User Response: Check that the cicsterm session in which CEBR is running is still active. Check that the screen is properly connected and configured. Check the symptom records and console.msg for any related information. A263 Explanation: CEBR tried unsuccessfully to read user input from the screen. System Action: CEBR terminates abnormally. User Response: Check that the cicsterm session in which CEBR is running is still active. Check that the screen is properly connected and configured. Check the symptom records and console.msg for any related information. A264 Explanation: CEBR tried unsuccessfully to retrieve data passed from the EXEC CICS START command. System Action: CEBR terminates abnormally. User Response: Check the symptom records and console.msg for any related information. A265 Explanation: CEBR attempted to read a record from a queue and received an unexpected error returned from the EXEC CICS READQ TS command. System Action: CEBR terminates abnormally. User Response: Check the symptom records and console.msg for any related information. A266 Explanation: An undetermined error has occurred during CEBR execution. System Action: CEBR terminates abnormally. User Response: Check the symptom records and console.msg for any related A27A Explanation: A message to be sent to a remote system could not be encoded. System Action: The transaction abnormally terminates. User Response: Examine the CICS message files for further information on the reason for this error. If sufficient storage could not be allocated for the encoded message, retry the transaction when the system is more lightly loaded, or simplify your transactions such that they use less task private storage. If data could not be converted between different code pages, ensure that an operating system conversion is available between the two code pages. If the conversion is available, and the problem persists, contact your support organization. A27B Explanation: A message received from a remote system could not be decoded. System Action: The transaction abnormally terminates. User Response: Examine the CICS message files for further information on the reason for this error. If sufficient storage could not be allocated for the encoded message, retry the transaction at a later time, when the system is more lightly loaded, or simplify your transactions such that they use less task private storage. If data could not be converted between different code pages, ensure that an operating system conversion is available between the two code pages. If the conversion is available, and the problem persists, contact your support organization. A27C Explanation: The function shipping mirror transaction could not access a resource. System Action: The transaction abnormally terminates. User Response: Examine the CICS message files for further information on the reason for this error. Consider re-running the transaction at a later time when the system is more lightly loaded. If the problem persists, contact your support organization. A27D Explanation: A message has been received which cannot be understood, or an unexpected communications verb has been received. System Action: The transaction abnormally terminates. User Response: Ensure that the remote system is not executing a Distributed Transaction Processing (DTP) transaction. If it is, modify the transaction and/or its resource definitions, such that it does not execute as the function shipping mirror transaction, or does not allocate conversations to the function shipping mirror transaction. If this is not the case, verify that the remote system, and the connection to it are functioning normally by performing other intersystem communication functions (such as transaction routing) to the remote system. If the problem persists, prepare a communications trace showing the data received from the remote system and contact your support organization. A27E Explanation: The function shipping mirror transaction has received a DL/I request which cannot be serviced. System Action: The transaction abnormally terminates. User Response: Use the procedures appropriate to the remote system to ensure that it does not attempt to function ship DL/I requests to CICS. This may including modifying the remote transaction and/or the remote system's resource definitions. A27F Explanation: Task private storage could not be allocated. System Action: The transaction abnormally terminates. User Response: Consider simplifying your transactions, such that they use less task private storage or enlarge the task private storage pool. A27G Explanation: The function shipping mirror transaction has received an error, while executing a START NOCHECK request. System Action: The mirror transaction abnormally terminates. User Response: Examine the CICS message files which may provide further information regarding the nature of the error response code. A27K Explanation: Your transaction has been using synclevel 1 to process remote function shipped resources. As a result of the transaction taking a syncpoint, either implicitly or explicitly, all local resources and synclevel 2 partner systems were committed. However, an error was detected when the commit message was sent to a synclevel 1 system. System Action: The transaction abnormally terminates. User Response: Examine the CICS message files for additional information which may help to determine why the transaction was rolled back. Use the procedures appropriate to any remote systems with which the transaction has performed intersystem communication with to obtain any additional information. A27L Explanation: A remote system issued an EXEC CICS LINK to run a user program local to this system. A COMMAREA was specified. The function shipping mirror transaction ran the user program on this system and the program completed. CICS then detected that the user program had overwritten memory beyond the end of the user programs COMMAREA. System Action: CICS abnormally terminates the function shipping mirror transaction. User Response: Identify the user program being run using CICS product trace and correct the programming error that caused the COMMAREA memory overwrite. A28A Explanation: A communications error was detected while communicating with a transaction on the remote system. System Action: CICS abnormally terminates the transaction. The region continues. User Response: Ensure that the remote system and the connection to it are available. Further information on the reason for the error can be obtained by examining the CICS message logs and referring to the CICS Intercommunication Guide. A28B Explanation: The remote transaction has abnormally terminated. System Action: CICS abnormally terminates the local transaction. The region continues. User Response: Use the procedures that are appropriate for the remote system to determine the reason for the abnormal termination of the remote transaction. A28C Explanation: The relay transaction was started without a terminal as its principal facility. :p. The relay transaction is a CICS-private transaction that provides the communication mechanism between the terminal on the terminal owning region and the transaction on the application owning region. System Action: CICS abnormally terminates the transaction. The region continues. User Response: Ensure that the transaction is being started from a terminal and not by another transaction executing ATI commands to start the transaction. A28D Explanation: CICS could not encode or decode a message that is to be sent to, or has been received from, a remote system. System Action: CICS abnormally terminates the transaction. The region continues. User Response: Examine the CICS message logs to determine why a message could not be encoded or decoded. If sufficient storage could not be allocated, retry the transaction when the system is more lightly loaded, or simplify your transactions so that they use less task private storage. Ensure that the remote system is not trying to start a Distributed Transaction Processing (DTP) transaction. A28E Explanation: A transaction has nominated a next transaction to run against a terminal as part of a pseudo-conversation sequence of transactions, but CICS could not start it. System Action: CICS abnormally terminates the transaction. The region continues. User Response: Examine the CICS message logs to determine which transaction could not be started. Then verify that the nominated transaction is defined in the terminal owning region by examining the transaction's Transaction Definition (TD). A28F Explanation: CICS could not perform an input or output operation on a terminal. System Action: CICS abnormally terminates the transaction. The region continues. User Response: Examine the CICS message logs and consult the CICS Problem Determination Guide to determine why the terminal could not be read from or written to. A28G Explanation: A Terminal Definition (WD) does not exist on the local system, and cannot be requested from the remote system because it is defined as not shippable. System Action: CICS abnormally terminates the transaction. The region continues. User Response: Confirm that it is desirable for the remote system to ship terminal definitions. If it is, then set the Terminal Definition in the remote system as shippable. If the remote system is a version of CICS on Open Systems, you can achieve this by setting the IsShippable attribute of the WD to yes. If the remote system is not a version of CICS on Open Systems, consult the appropriate documentation for the system to determine how to set the Terminal Definition as shippable. :p. If it is not desirable to ship terminal definitions from the remote system, add a WD for the remote terminal on the local system. A28H Explanation: A Terminal Definition (WD) could not be requested from the terminal owning region, or could not be installed in the transaction owning region. System Action: CICS abnormally terminates the transaction. The region continues. User Response: Examine the CICS message logs to determine why the WD entry could not be installed. If the WD could not be installed because CICS is short on storage, retry the transaction later, or increase the size of the task shared and region pools. If the WD entry could not be installed because the WD entry in the terminal owning region is defined as not shippable, consider defining it as shippable, or consider installing a WD entry in the transaction owning region. A28I Explanation: The Terminal Definition (WD) entry on the transaction owning region is in use by another terminal, on another remote system. System Action: CICS abnormally terminates the transaction. The region continues. User Response: Retry the transaction at a later time. If the problem persists, consider trying to make the terminal name unique within your network of connected systems. This can be achieved by modifying the user exit program that provides the terminal name. If the terminal owning region is a version of CICS on Open Systems, this is the DFHCHATX transaction. Also consider specifying a local WD entry for the remote terminal, specifying the RemoteName and RemoteSysId attributes. A28J Explanation: The TCTUA cannot be installed in the Terminal Definition (WD). System Action: CICS abnormally terminates the transaction. The region continues. User Response: Consider altering the TCTUALen attribute of the local system's WD for the terminal and the TCTUA length of the remote terminal definition such that they match. If this message is displayed in the transaction owning region, also consider deleting the local terminal definition and allowing the remote region to ship terminal definitions. A28K Explanation: Transaction is part of a transaction routing loop. System Action: CICS abnormally terminates the transaction. The region continues. User Response: If you are using CRTE, avoid routing back to the local system from the remote system. If the remote transaction has itself been defined as remote, verify that the remote system for the transaction is correctly specified. If the remote system is a version of CICS on Open Systems, you can achieve this by examining the RemoteSysId attribute of the Transaction Definition (TD) entry. If the remote system is not a version of CICS on Open Systems, consult the appropriate documentation for that system. A28M Explanation: An unexpected or unknown communications error has occurred. System Action: CICS abnormally terminates the transaction. The region continues. User Response: Look for the message ERZ028038E in CSMT and follow the instructions associated with it. A28N Explanation: A dynamic transaction cannot be started on an intermediate system. System Action: CICS abnormally terminates the transaction. The region continues. User Response: Ensure that the local transaction definition does not specify that the transaction is dynamic. Dynamic transaction should only be started in terminal owning systems. A28O Explanation: CICS is unable to link to the DFHTRUC program. DFHTRUC is required in order to convert data in a COMMAREA or TCTUA for a transaction routing request. Further information on the function of DFHTRUC can be found in the CICS Intercommunication Guide. System Action: CICS abnormally terminates the transaction. User Response: Examine the messages written to the console.msg file and CSMT log to determine why CICS can not link to the DFHTRUC program. Follow the instructions for these messages. A29A Explanation: CICS has detected a communications error that requires the currently running transaction to be terminated abnormally. For example, if a Distributed Transaction Processing (DTP) command is force-purged, this code will be used. System Action: CICS abnormally terminates the transaction. User Response: Check the additional messages logged to identify which error occurred and follow the instructions for these messages. If the transaction has been force-purged, this abend is expected. Retry the command. A29B Explanation: A request to allocate storage from the Task Private Pool to complete a Distributed Transaction Processing (DTP) command was unsuccessful. System Action: CICS abnormally terminates the transaction. User Response: Retry the command. If this problem persists find out where your program is making large demands for Task Private memory. Either rewrite it to use less or increase the size of the Task Private Pool by changing the value of the MaxTaskPrivatePool attribute in the Region Definition and cold starting CICS. A29C Explanation: CICS has detected an unexpected synclevel on an incoming intersystem request. System Action: CICS abnormally terminates the transaction. User Response: Look for additional messages, which will give details of the remote system, and follow the instructions for these messages. Ensure that the versions of software used by your CICS region are compatible. Also check that the software running on the remote system is compatible with your local CICS region. If the remote system is connected to your CICS region via a PPC Gateway and a Systems Network Architecture (SNA) network, check that the version of the PPC gateway is compatible with the versions of the software products used by your local region. If you find that the software used by the communicating systems is incompatible, install the correct versions. Retry the transaction. If the problem persists, contact your support organization. A29D Explanation: CICS received transaction routing or function shipping data from a remote system on a Distributed Transaction Processing (DTP) conversation. This indicates there is a mismatch between the local transaction and the remote program. The local transaction could be a DTP program that has requested a program on the remote system and the remote system has mistakenly interpreted this as a transaction routing or a function shipping request. Alternatively, the remote system could have issued a transaction routing or function shipping request which the local region has mistakenly interpreted as a request to start a backend DTP program. System Action: CICS abnormally terminates the transaction. User Response: Look for additional messages, which will give details of the remote system, and follow the instructions for these messages. Look at the function of the transaction. If it is not a DTP program, ensure that the IsBackEndDTP attribute of its Transaction Definition (TD) entry is set to no. If the transaction is a DTP program that starts the conversation with the remote system, check that the program requested on the PROCNAME parameter of the CONNECT PROCESS command is set up on the remote system as a DTP backend program. Finally, if the transaction was invoked by an intersystem request from the remote system, determine how it was started. It is possible that it is defined in the remote system as a remote transaction and it has been invoked from a terminal connected to the remote system. If this is the case, request that the definition for the transaction is either removed from the remote system, or altered so that transaction routing requests for the transaction are not sent to the local region. A30A Explanation: Your transaction has executed a syncpoint or syncpoint rollback which was unsuccessful, either because one or more of your transaction's synclevel syncpoint APPC conversations is in the wrong state, or because heuristic damage was reported on one of your transaction's APPC conversations. System Action: The transaction is abnormally terminated. User Response: Examine the CICS message files for additional information indicating why your transaction was abnormally terminated. If a state error is reported on one of your transaction's APPC conversations, examine your transaction to ensure that all of its synclevel syncpoint conversations are in the appropriate state to execute a syncpoint or syncpoint rollback. If heuristic damage is reported, use the procedures appropriate to the remote system to determine why heuristic damage was reported. The local and remote systems may require manual intervention to synchronise resources that have been either rolled back or committed. A30B Explanation: CICS attempted to allocate task private storage for a message received on an Intersystems Communication (ISC) link, but was unsuccessful. System Action: The transaction is abended. User Response: Consider re-running the transaction at a later time when the system is more lightly loaded. Also consider simplifying your transactions, such that they use less task private storage. A30C Explanation: CICS is unable to execute a CICS-supplied program because the Program Definition (PD) entry for this program does not exist. System Action: The transaction is abnormally terminated. User Response: Examine the CICS message files to determine which PD entry cannot be found. Ensure that a suitable PD entry for the program exists. Then resubmit the transaction. A30D Explanation: CICS is unable to execute a CICS-supplied program because this program is defined to be remote. CICS requires that this program is local. For a program to be local, the RemoteSysId attribute of its Program Definition (PD) entry must either be set to null ("") or the local SYSID. The local SYSID is configured in the LocalSysId attribute of the Region Definition (RD) entry. System Action: CICS abnormally terminates the transaction. User Response: Examine the CICS message files to determine which PD entry is defined as remote. Modify the RemoteSysId attribute of the PD entry for the program such that it either specifies a null string ("") or the local SYSID. Then resubmit the transaction. A30E Explanation: The transaction has terminated leaving an outstanding conversation to one or more remote systems. In order to end the transaction CICS has abnormally terminated the outstanding conversation(s). System Action: CICS abnormally terminates both the conversation(s) and the transaction. User Response: If this is a distributed transaction processing (DTP) program, alter the program logic so that all conversations are terminated prior to the program issuing an EXEC CICS RETURN. The CICS Intercommunication Guide provides more information on DTP conversations. If the transaction is not using DTP, refer to any associated messages that may have been logged for further guidance in resolving this problem. A30F Explanation: CICS is unable to complete a send or a receive of data for an intersystem request because of an error in the length fields within the data. System Action: CICS creates a symptom record (symrec) describing the failing command and abnormally terminates the transaction. User Response: Examine the console.msg file and the CSMT log as these may contain messages which describe the cause of the problem. If you can not solve this problem yourself, save the message files and the symrec file and contact your support organization. A30G Explanation: CICS is unable to complete a send or a receive of Process Initialization Parameter (PIP) data for an intersystem request because of an error in the length fields within the PIP data. System Action: CICS creates a symptom record (symrec) describing the failing command and abnormally terminates the transaction. User Response: Examine the console.msg file and the CSMT log as these may contain messages which describe the cause of the problem. If you can not solve this problem yourself, save the message files and the symrec file and contact your support organization. A31A Explanation: The CRTE transaction was started without a terminal as its principal facility. System Action: The transaction abnormally terminates. User Response: You should ensure that the transaction is being started from a terminal, and not by another transaction executing ATI commands that start the transaction. A31B Explanation: CICS could not perform an input or output operation on a terminal. System Action: The transaction abnormally terminates. User Response: You should examine the CICS message logs and consult the CICS Problem Determination Guide to determine why the terminal could not be read from or written to. A32A Explanation: A CICS-private transaction was unable to attach to a remote system. System Action: The transaction is abnormally terminated. Any ATIs which were to be transmitted to the remote system and terminal are deleted. User Response: Look for messages ERZ3201E and ERZ3202E on CSMTLOG and follow the instructions associated with them. A32B Explanation: A CICS-private transaction attempted to send a request to a remote system which is in the process of quiescing. System Action: The transaction is abnormally terminated. Any ATIs which were to be transmitted to the remote system and terminal are deleted. User Response: Look for message ERZ3210E on CSMTLOG and follow the instructions associated with it. A32C Explanation: A conversation between CICS-private transactions has been abnormally terminated. This may be caused by a network failure or an abnormal termination of the CICS-private transaction on the remote system. System Action: The transaction is abnormally terminated. Any ATIs which were to be transmitted to the remote system and terminal are deleted. User Response: Look for message ERZ3204E on CSMTLOG and follow the instructions associated with it. A32D Explanation: There is an inconsistency with a remote system definition or a terminal definition. System Action: The CICS-private transaction is abnormally terminated. Any ATIs which were to be transmitted to the remote system and terminal are deleted. User Response: Look for messages ERZ3205E, ERZ3214E, ERZ3215E and ERZ3220E on CSMTLOG and follow the instructions associated with them. A32E Explanation: An invalid, unknown or corrupt message has been given to the CICS-private transaction which schedules tasks to a remote system. There are many potential causes of this problem such as someone attempting to transaction route the CICS-private transaction or issuing EXEC CICS CONNECT PROCESS for it. These are the symptoms to be expected if the remote system is incompatible with CICS on Open Systems. System Action: The transaction is abnormally terminated. Any ATIs which were to be transmitted to the remote system and terminal are deleted. User Response: Look for message ERZ3206E on CSMTLOG and follow the instructions associated with it. A32F Explanation: A request was made to schedule a task on a remote terminal; the terminal was not available on the remote system. System Action: The CICS-private transaction is abnormally terminated. Any ATIs which were to be transmitted to the remote system and terminal are deleted. User Response: Look for message ERZ3207E on CSMTLOG and follow the instructions associated with it. A32G Explanation: A request was made to schedule a transaction on a remote terminal; the transaction was not available on the remote system. System Action: The CICS-private transaction is abnormally terminated. Any ATIs which were to be transmitted to the remote system and terminal are deleted. User Response: Look for message ERZ3221E on CSMTLOG and follow the instructions associated with it. A32H Explanation: A request was made to schedule a transaction on a remote system, but the schedule failed on the remote system. System Action: The CICS-private transaction is abnormally terminated. Any ATIs which were to be transmitted to the remote system and terminal are deleted. User Response: Investigate the message logs on the remote system, there should be messages indicating the problem on the remote system, follow the actions documented for the messages on the remote system. Look for message ERZ3203E on CSMTLOG and follow the instructions associated with it. A32J Explanation: ASCII to EBCDIC translation failed, there is a problem with the national language support (NLS) environment. System Action: The CICS-private transaction is abnormally terminated. Any ATIs which were to be transmitted to the remote system and terminal are deleted. User Response: Look for message ERZ3213E on CSMTLOG and follow the instructions associated with it. A32K Explanation: A request to allocate storage has failed. System Action: The CICS-private transaction is abnormally terminated. Other storage-associated problems may also occur in this CICS region. User Response: Investigate why there is not sufficient storage. Look for message ERZ3006E on the logs and follow the instructions associated with it. A32L Explanation: The CICS-private transaction CRSR, which schedules tasks for remote terminals, has been invoked by an invalid method. CICS-private transactions should only ever be started by CICS. System Action: The CICS-private transaction CRSR is abnormally terminated. User Response: Investigate how the transaction was invoked and ensure that the transaction is not invoked in this way again. Refer to the error message ERZ3231E (on the CSMT.log) for more information regarding this error. A32M Explanation: A request to ship an unsupported message type to the partner system has been received. System Action: The request is abnormally terminated. User Response: No user action is required. A331 Explanation: Although the CICS_EpiStartTran call returned CICS_EPI_NORMAL, the attempt to schedule the transaction was unsuccessful. System Action: CICS does not run the transaction. The EPI is ready to schedule another transaction. User Response: Examine the data buffer of the preceding CICS_EPI_EVENT_SEND event. Calling CICS_EpiGetSysError specifying the TermIndex for the associated terminal will return further information about the cause of A341 Explanation: An attempt was made to run the CICS-private transaction CURD from a terminal. System Action: The transaction is abnormally terminated. User Response: Do not run CURD from a terminal. A342 Explanation: The CICS-private transaction CURD, used in CICS region to Resource Definition Online (RDO) communications, made an unsuccessful attempt to converse with RDO. System Action: CICS abnormally terminates the CURD transaction. User Response: As for message ERZ034068E. A371 Explanation: An undetermined error has occurred during CALF execution. Further information may be available in one of the CICS message files. System Action: CALF terminates abnormally. User Response: Refer to any associated messages in the CICS message files for further guidance on resolving the problem. A372 Explanation: CALF has determined that the source and destination files that you specified do not have the same format. Specifically, the record length of the source file is greater than the record length of the destination file. System Action: CALF terminates abnormally. User Response: Check to see that the source and destination filenames were entered correctly. Also ensure that they are defined to be the same format and that the destination record length, is sufficient to hold the longest source record. If the filenames were wrong you should re-invoke CALF, specifying the correct files. If the definitions for the files were incorrect you may need to redefine the source file to the file server before you can re-invoke CALF to copy them. A373 Explanation: CALF has determined that the length of the records in the source file is less than the length of the records in the destination file, that you have requested that no records should be padded with nulls and that the destination is of fixed length. System Action: CALF terminates abnormally. User Response: You have requested CALF does not pad records with NULLs. You should determine whether you really need PAD set to NO. If not then use the default setting. If you need PAD set to NO change the record length of the destination file to be the same of that of the source file. A374 Explanation: CALF has detected an invalid request response (INVREQ) while it was writing to the destination file. This could be due to insufficient authority on the file or inconsistencies of key length and key position between the source and destination files. It could also be due to an inconsistent conversion template for a remote copy. Further information may be held in one of the CICS message files. System Action: CALF terminates abnormally. User Response: Check that the key of the source file is of the same length and in the same position as that of the destination file (in the case of a KSDS file). Check also that the user has add authority to write to the destination file. In the case of a remote source file, ensure that the conversion template performs consistent conversion of the key and the key section of the record. A375 Explanation: CALF detected a duplicate record response (DUPREC) while it was writing to the destination file, but you have specified that duplicate records are not allowed. System Action: CALF terminates abnormally. User Response: The default setting for duplicate records is that they should be allowed (DUPREC=YES). You have set this value to NO. You should determine whether you really need DUPREC set to NO. If not then use the default setting. If you need DUPREC set to NO then ensure the destination file is empty before using the import function. A376 Explanation: CALF has encountered an error while trying to read a record from the source file. Further information may be available in one of the CICS message files. System Action: CALF terminates abnormally. User Response: If the source file is remote check that there is a connection to the remote system where the source file resides. Refer to the CICS message files for more information. A377 Explanation: CALF has encountered an error while trying to write to the destination file. This may be due to a lack of file space or perhaps the destination file has been closed since you opened it. Further information may be available in one of the CICS message files. System Action: CALF terminates abnormally. User Response: Check that the destination file is open/enabled and that there is enough space in the file system to write to it. Check also that you have the necessary permissions to write to the file. Refer to any associated messages in the CICS message files for further guidance on resolving the problem. A378 Explanation: CALF has encountered an error while trying to send some information to the screen. This may be due to your cicsterm session crashing. Further information may be available in one of the CICS message files. System Action: CALF terminates abnormally. User Response: Check that the cicsterm session in which CALF is running is still active. Check that your screen is properly connected and configured. Refer to any associated messages in the CICS message files for further guidance on resolving the problem. A379 Explanation: CALF has encountered a problem trying to read your input from the screen. This may be due to your cicsterm session being unavailable to CICS. Further information may be available in one of the CICS message files. System Action: CALF terminates abnormally. User Response: Check that the cicsterm session in which CALF is running is still active. Check that the screen is properly connected and configured. Refer to any associated messages in the CICS message files for further guidance on resolving the problem. A37A Explanation: CALF tried unsuccessfully to obtain a message from the message catalog. This might happen if your NLSPATH does not point where it should, or if your locale is wrong. System Action: CALF terminates abnormally. User Response: Verify that CICS has been installed correctly for the locale which you have chosen. A37B Explanation: CALF encountered a problem while trying to inquire on either the source or the destination file. This may be because the file is not present in the CICS runtime database, or because you are not authorized to read the file. Further information may be available in one of the CICS message files. System Action: CALF terminates abnormally. User Response: Verify that both the source and the destination files are present and defined in the FD.stanza. Check also that you are authorized to read the file. Refer to any associated messages in the CICS message files for further guidance on resolving the problem. A37C Explanation: CALF tried unsuccessfully to request a SYNCPOINT while it wrote to the destination file. Further information may be available in one of the CICS message files. System Action: CALF terminates abnormally. User Response: The system which you are running CALF on is unable to commit the syncpoint. Refer to any associated messages in the CICS message files for further guidance on resolving the problem. A37D Explanation: CALF tried to schedule the use of the destination file (using ENQ) but encountered an error. This might be because the destination file was in use at the time CALF issued its request. Further information may be available in one of the CICS message files. System Action: CALF terminates abnormally. User Response: It is possible that the source file was being written to at the time CALF tried to schedule its use. Make sure nobody else is using your source file, then try the operation again. If the problem persists refer to any associated messages A41A Explanation: CICS has detected an unexpected fatal exception. System Action: See ERZ041014E. User Response: See ERZ041014E. A42A Explanation: A request to allocate storage from the Task Private Pool was unsuccessful. System Action: CICS abnormally terminates the transaction. User Response: Retry the operation. If it is still unsuccessful, this may be because another transaction is using a large amount of Task-Private (GETMAIN) storage. Refer to any previous messages in the CSMT log and console.msg files which may indicate why Task-Private storage could not be allocated. If the problem persists, increase the size of the Task Private Pool by changing the value of the MaxTaskPrivatePool attribute in your region's Region Definition (RD) entry and restart CICS. A42B Explanation: The CTIN transaction was invoked incorrectly or the data received from the CICS Client was invalid. The CTIN transaction should only be issued by an CICS Client to install or uninstall a client terminal. It is not a general purpose transaction. System Action: CICS abnormally terminates the CTIN transaction. The install or uninstall request is not performed. User Response: If this abend continues to occur when issued by an CICS Client, contact your support organization. A42C Explanation: A request to uninstall (delete) a Terminal Definitions (WD) entry for an CICS Client terminal was unsuccessful. The uninstall request may have been scheduled by CICS because the network went down or it may have been scheduled by an CICS Client when closing down the terminal session. The reason why the uninstall request was unsucessful will have been logged in a CSMT message. System Action: CICS abnormally terminates the CTIN transaction. The uninstall request is not performed. User Response: Check the CSMT log to see why the uninstall abnormally terminated. If this occurs repeatedly, ask the System Administrator to delete the WD entry from the region database. If unwanted WD entries remain installed, further installs take longer to perform and degrade performance. A42D Explanation: The CTIN transaction was invoked correctly but the network connection was lost before the CICS Client terminal request completed. System Action: CICS abnormally terminates the CTIN transaction. The install or uninstall request is not performed. User Response: Retry the CICS Client terminal operation. Refer to any previous messages in the console.msg file and CSMT log which indicate why the network connection went down. A42E Explanation: A Communications Definition (CD) entry autoinstall request abnormally terminated. This may be because: • • The autoinstall program, DFHCCINX, vetoed the autoinstall request. • DFHCCINX requested a SYSID that matches an existing entry in either the Communications Definition (CD) or Terminal Definitions (WD). • CICS could not interpret the autoinstall data received from the remote system. System Action: CICS logs error messages to CSMT and abnormally terminates the CCIN transaction. User Response: Check the CSMT log and console.msg file for further messages which explain why the autoinstall request was unsuccessful, and follow the instructions for these messages. A42F Explanation: A Communications Definition (CD) entry uninstall (delete) request was unsuccessful. System Action: CICS logs error messages to the CSMT log and abnormally terminates the CCIN transaction. User Response: Check the CSMT log and console.msg file for further messages which explain why the uninstall request was unsuccessful and follow the instructions for these messages. A42G Explanation: The Communications Definition (CD) entry install or uninstall (delete) request was unsuccessful due to a communication error on the connection with the remote system. System Action: CICS logs a message indicating the type of communications error, creates a symptom record (symrec) and abnormally terminates the CCIN transaction. User Response: Retry the operation. If the problem persists, although the remote system remains running, check that the communications protocol being used is set up correctly for the two systems. A42H Explanation: The CCIN transaction has been invoked incorrectly. This transaction should only be started by a remote CICS system or an CICS Client to autoinstall or delete Communications Definitions (CD) entries. It is not a general purpose transaction. System Action: CICS creates a symptom record (symrec) and abnormally terminates the CCIN transaction. User Response: No further action is required. A42I Explanation: The CCIN transaction can not interpret the data received from a remote system. This could be because: • • The remote system is not compatible with the local region. • The remote system is not a CICS region or an CICS Client. • A user-written application running in the remote system has requested a Distributed Transaction Processing (DTP) conversation with CCIN. A symptom record (symrec) is created which contains the SYSID that CCIN was scheduled against. If this is the local SYSID configured in Region Definition (RD) attribute LocalSysId, the request was received from a remote system that is not recognized by CICS. In this case the remote system is either an CICS Client or it is a CICS region connecting over a CICS family TCP/IP connection. If the SYSID is not the local SYSID, it is the name of the Communications Definition (CD) entry for the remote system. System Action: CICS creates a symptom record and abnormally terminates the CCIN transaction. User Response: Identify the remote system using the SYSID from the symptom record or error messages logged in connecting systems. If the remote system is an CICS Client, alter the software or configuration used in the CICS Client so it is compatible with your region. If the remote system is a CICS region, look for applications in this remote system that are requesting a DTP conversation with CCIN. A42J Explanation: CICS is unable to interpret the data received from a remote system because there is a problem with the data conversion routines for conversion between the United States (US) ASCII and EBCDIC code pages. System Action: CICS creates a symptom record (symrec) and abnormally terminates the CCIN transaction. User Response: Examine the symptom record to determine the exact nature of the problem. Then use the information on National Language Support (NLS) supplied with the operating system to correct the problem. A42K Explanation: The CCIN transaction is unable to complete an install or an uninstall (delete) of a Communications Definition (CD) entry because of an error in the region database. System Action: CICS creates a symptom record (symrec) describing the failing command and abnormally terminates the CCIN transaction. User Response: Examine the console.msg file and the CSMT log as these may contain messages which describe the cause of the problem. If you can not solve this problem yourself, save the message files and the symrec file and contact your support organization. A43A Explanation: CICS tried to allocate Task Private storage for intersystems communication, but was unsuccessful. System Action: CICS abnormally terminates the transaction. User Response: Retry the transaction at a later time when the system is more lightly loaded, or change your transactions so that they use less task private storage, or increase the size of the Task Private storage and warm start the region. A43B Explanation: An error was detected during communications that requires the currently running transaction to be terminated abnormally. System Action: CICS abnormally terminates the transaction. Message ERZ043004E will be logged. User Response: Check the error message for the error reported by the communications protocol and take appropriate action. A43C Explanation: An inconsistency has been detected in an internal CICS operation. System Action: CICS abnormally terminates the transaction. User Response: Retry the failed operation. If the condition persists, use CEMT PERFORM SNAP to produce a system dump and contact your support organization. A43D Explanation: An error was detected during communications that requires the currently running transaction to be terminated abnormally. System Action: CICS abnormally terminates the transaction. Message ERZ043007E will be logged. User Response: Check the error message for the nature of the problem and take appropriate action. A43E Explanation: An asynchronous backout occurred during intersystems communication that requires the currently running transaction to be terminated abnormally. System Action: CICS abnormally terminates the transaction. Message ERZ043008W will be logged. User Response: Check the error message and any previous messages for the cause of the asynchronous backout and take appropriate action. A451 Explanation: The user defined External Security Manager (ESM) raised an unexpected error condition when executing a Transaction Security Level (TSL) check on a transaction. System Action: CICS abnormally terminates the application server. User Response: You should check the documentation and source code of the ESM to ascertain why an unexpected error code was raised. A452 Explanation: The user defined External Security Manager (ESM) raised an unexpected error condition when executing a Resource Security Level (RSL) check in a transaction. System Action: CICS abnormally terminates the application server. User Response: You should check the documentation and source code of the ESM to ascertain why an unexpected error code was raised. A453 Explanation: An update to a resource definition could not be completed. System Action: CICS abnormally terminates the application server. User Response: This is an indication of a software problem in CICS. Contact your support organization. A460 Explanation: CEMT has detected an error with your CICS region. Further information may be available in one of the CICS message files. System Action: CEMT terminates abnormally. User Response: Refer to any associated messages in the CICS message files for further guidance on resolving the problem. A461 Explanation: CEMT tried unsuccessfully to obtain a message from the message catalog. System Action: CEMT terminates abnormally. User Response: Verify that CICS has been installed correctly for the locale which you have chosen. A462 Explanation: CEMT is unable to create a panel for display on the screen. System Action: CEMT terminates abnormally. User Response: Verify that CICS has been installed correctly. Check the symptom records and console.msg for any related information. A463 Explanation: CEMT is unable to create a map for display on the screen. System Action: CEMT terminates abnormally. User Response: Verify that CICS has been installed correctly. Check the symptom records and console.msg for any related information. A464 Explanation: CEMT is unable to create a field for display on the screen System Action: CEMT terminates abnormally. User Response: Verify that CICS has been installed correctly. Check the symptom records and console.msg for any related information. A465 Explanation: CEMT is unable to write to a field for display on the screen System Action: CEMT terminates abnormally. User Response: Verify that CICS has been installed correctly. Check the symptom records and console.msg for any related information. A466 Explanation: CEMT is unable to display a panel on the screen System Action: CEMT terminates abnormally. User Response: Check that the cicsterm session in which CEMT is running is still active. Check that the screen is properly connected and configured. Check the symptom records and console.msg for any related information. A467 Explanation: CEMT is unable to read from a field displayed on the screen System Action: CEMT terminates abnormally. User Response: Verify that CICS has been installed correctly. Check the symptom records and console.msg for any related information. A468 Explanation: CEMT is unable to allocate a task table from region memory System Action: CEMT terminates abnormally. User Response: Ensure that the region is configured correctly and that enough memory is made available. CEMT uses memory from a task private pool. Check the value of MaxTaskPrivatePool in the region definitions; you can increase the size of task private pool given to transactions by adjusting this attribute. Check the symptom records and console.msg for related information. A469 Explanation: CEMT is unable to access its private error Temporary Storage Queue (TSQ) System Action: CEMT terminates abnormally. User Response: Verify that the file server is configured correctly and is active for the region to which CEMT was connected.Check the symptom records and console.msg for related information. Re-start CEMT. If the file server is in-operative, CEMT will revert to using main TSQs instead of auxiliary TSQs. A46A Explanation: CEMT is unable to read its private screen Temporary Storage Queue (TSQ) System Action: CEMT terminates abnormally. User Response: Verify that the file server is configured correctly and is active for the region to which CEMT was connected. Check the symptom records and console.msg for related information. Ensure that you have security access to CEMT TSQs - adjust resource definitions as necessary. Re-start CEMT. If the file server is in-operative, CEMT will revert to using main TSQs instead of auxiliary TSQs. A46B Explanation: CEMT is unable to write to its private screen Temporary Storage Queue (TSQ) System Action: CEMT terminates abnormally. User Response: Verify that the file server is configured correctly and is active for the region to which CEMT was connected. Check the symptom records and console.msg for related information. Re-start CEMT. If the file server is in-operative, CEMT will revert to using main TSQs instead of auxiliary TSQs. A46C Explanation: CEMT is unable to initialize the CICS internal command analyzer. System Action: CEMT terminates abnormally. User Response: Verify that CICS has been installed correctly and that the region to which CEMT was attached is still active. Check the symptom records and console.msg for any related information. A46D Explanation: CICS is unable to syncpoint the CEMT transaction. System Action: CEMT terminates abnormally. User Response: Check that the region to which CEMT was connected is still active. Check the symptom records and console.msg for any related information. A46E Explanation: CEMT is unable to write to its private screen Temporary Storage Queue (TSQ), as there is insufficient Task Shared Pool Storage. System Action: CEMT is restarted using Auxiliary Temporary Storage. User Response: Ensure that the region is configured correctly and that enough memory is made available. Check the value of MaxTSHPool in the region definitions; you can increase the size of task shared pool by adjusting this attribute. Check the symptom records and console.msg for related information. A46F Explanation: CEMT is unable to write to Auxiliary Temporary Storage as the file which contains the queues has no space available. System Action: CEMT terminates abnormally. User Response: There may be associated messages in the console.log or CSMT.out detailing the file server error. CEMT will only be using Auxiliary Temporary Storage if there is insufficient Task Shared Pool Storage in the region for it to use Main Temporary Storage. Check that the region is A47A Explanation: A transaction calls GETMAIN with a LENGTH or FLENGTH value of 0. System Action: A user abnormal termination handler is invoked if defined by the transaction program. If no abnormal termination handler is defined then CICS abnormally terminates the transaction. User Response: Check the programs associated with the transaction for the use of the GETMAIN call. Ensure that the values passed in the LENGTH or FLENGTH options are greater than zero. A47B Explanation: A transaction calls FREEMAIN with the DATA option set to an invalid address. System Action: A user abnormal termination handler is invoked if defined by the transaction program. If no abnormal termination handler is defined then CICS abnormally terminates the transaction. User Response: You should check the programs associated with the transaction for the use of the FREEMAIN call. Ensure that the address value passed in the DATA option is one that has been previously returned from a GETMAIN call and that the value has not already been processed by a previous FREEMAIN call. A transaction dump should be taken and can be used to investigate this problem. Check CSMT and console.msg for any messages which can be used to investigate the problem along with the transaction dump. A47C Explanation: CICS detects a storage inconsistency. CICS uses a 'signature string' placed at the end of an allocated block of task-private storage. If this 'signature string' is not in place when the storage area is passed to a FREEMAIN call this indicates that the storage area was overrun during the transaction's execution. System Action: A user abnormal termination handler is invoked if defined by the transaction program. If no abnormal termination handler is defined then CICS abnormally terminates the transaction. A transaction dump is taken if this is indicated by the transaction's definition. User Response: A transaction dump should be taken and can be used to investigate this problem. Check CSMT and console.msg for any messages which can be used to investigate the problem along with the transaction dump. A47D Explanation: CICS returns an unexpected error while allocating or deallocating a control block associated with a task-private storage call (GETMAIN or FREEMAIN). This abnormal condition indicates a software problem in CICS. System Action: A user abnormal termination handler is invoked if defined by the transaction program. If no abnormal termination handler is defined then CICS abnormally terminates the transaction. User Response: Retry transaction to see if the condition has cleared. If the condition persists contact your support organization. A48A Explanation: A transaction has been timed out waiting for task shared storage to become available. System Action: A user abnormal termination handler is invoked if defined by the transaction program. If no abnormal termination handler is defined then CICS abnormally terminates the transaction. User Response: Retry the transaction. If this is a persistent problem you should check the size of the task shared pool defined in the Region Definitions. If it is not large enough for the needs of your region then reconfigure the size of the task shared pool in the Region Definitions or by CICS command line parameters at start up. A48B Explanation: An unexpected error is returned from storage control. System Action: A user abnormal termination handler is invoked if defined by the transaction program. If no abnormal termination handler is defined then CICS abnormally terminates the transaction. User Response: This is indicative of a software problem in CICS. Contact your support organization. A48C Explanation: CICS did not complete a LOAD PROGRAM or SEND MAP or RECEIVE MAP call because it was unable to load the map or table image into shared storage. This occurred because of an input output error reading the map or table image from disk storage. System Action: A user abnormal termination handler is invoked if defined by the transaction program. If no abnormal termination handler is defined then CICS abnormally terminates the transaction. A transaction dump is taken if this is indicated by the transaction's definition. User Response: Retry the transaction. Check that the map or table to be loaded exists at in the disk directory indicated in the Program Definitions. If this error persists there may be some problem with a disk drive; contact your support organization. A49B Explanation: CICS has detected an inconsistency in its internal data structures whilst processing a command to either start or stop user trace. System Action: The transaction is abnormally terminated. User Response: It is possible that CICS internal data structures have been overwritten by a defective application program. Retry the transaction. If the problem A50B Explanation: CICS is unable to release monitoring record storage during initialization of the Task Control Area (TCA) due to a data inconsistency in the Task-Private Pool. Further messages may be found in the message log and give more information about the problem. System Action: CICS abnormally terminates the task. User Response: It is likely that the transaction has caused a data inconsistency in the Task-Private Pool storage. Check the User Event Monitoring Point (EMP) and, if necessary, correct the User Event Monitoring Point (EMP) function. In order to use the replacement ULM, you will need to restart the region. A50C Explanation: CICS is unable to release monitoring record storage during task termination due to data inconsistency. Further messages may be found in the message log and give more information about the problem. System Action: CICS abnormally terminates the task. User Response: It is likely that the transaction has caused a data inconsistency in the Task-Private Pool storage. Check the User Event Monitoring Point (EMP) and, if necessary, correct the User Event Monitoring Point (EMP) function. In order to use the replacement ULM, you will need to restart the region. A53A Explanation: CICS was unable to process your request to collect statistics, due to an error while collecting the statistics. Messages will have been logged to indicate the nature of the problem. System Action: The transaction abnormally terminates. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. A561 Explanation: CICS was unable to allocate storage to perform a wait on a condition. System Action: CICS abnormally terminates the process. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. A57A Explanation: CICS detected an unsuccessful condition. System Action: If the condition is detected in an Application Server process, then CICS abnormally terminates the process and any transaction running in that process. If the process is not an Application Server then the region will terminate. If you are running a CICS utility program, then the utility is halted. User Response: Investigate the circumstances in which the error occurred. Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. A583 Explanation: A program has exited with the Micro Focus COBOL run-time system (RTS) in an unknown state, and possibly also with an incomplete logical unit of work. This can happen when using the Micro Focus COBOL ANIMATOR debugger, for example, or when the Micro Focus COBOL RTS returns an error. System Action: CICS abnormally terminates the application server to back out any incomplete logical unit of work, and to terminate the Micro Focus COBOL RTS for that application server. Further messages will be logged if a logical unit of work is backed out. This avoids leaving the Micro Focus COBOL RTS in an unknown state as this could prevent successful execution of subsequent COBOL programs. User Response: Depending on the transaction involved it may be acceptable to do nothing, such as when using ANIMATOR, or it may be necessary to correct and resubmit the transaction. A61A Explanation: CICS is unable to register a function to be called at a syncpoint. System Action: CICS terminates the transaction abnormally. User Response: Examine surrounding messages for further help in the reasons for A62C Explanation: CICS attempted to perform a Basic Mapping Support (BMS) operation on a terminal that does not support BMS operations. System Action: CICS abnormally terminates the transaction. User Response: Run the transaction on a terminal that does support BMS operations. A62F Explanation: CICS cannot allocate memory for a terminal operation in one of the Task Private or the Task Shared Pools. System Action: CICS abnormally terminates the transaction. User Response: Retry the transaction. If the condition occurs again, it may be due to heavy load on CICS or because some transaction uses a large amount of memory. A62G Explanation: CICS cannot update the Terminal Definitions (WD). System Action: CICS abnormally terminates the transaction. User Response: Any CICS internal data structure inconsistencies are unlikely to be caused by application code, since they are held in the Region Pool. Save any dump file and contact your support organization. A62H Explanation: CICS is unable to register a function to be called at a syncpoint System Action: CICS abnormally terminates the transaction. User Response: Examine surrounding messages for further information about this problem. A62J Explanation: CICS cannot convert a data in Case=Mixed field in a BMS map to uppercase. System Action: CICS abnormally terminates the transaction. A64A Explanation: Either the ECI mirror transaction definition or the model terminal definition used for the autoinstalled ECI terminal session has the UCTranFlag attribute set to yes. System Action: The ECI mirror transaction is abnormally terminated. User Response: Use RDO to redefine the offending transaction or model terminal definition to have the UCTranflag attribute set to no. Upper case translation must not be set as the ECI protocols send data encoded within the 3270 data stream. If upper case translation is set on, the ECI data will be corrupted and interpreted incorrectly. A64B Explanation: The ECI mirror transaction received an error when reading or writing data to an ECI application. System Action: The ECI mirror transaction is abnormally terminated. User Response: This abend may occur if the ECI application is prematurely terminated, e.g. the ECI request timed out or the interrupt key is entered at a terminal executing the ECI application, or if the ECI mirror transaction is invoked directly at a CICS terminal. A64C Explanation: The ECI mirror transaction was invoked incorrectly or the data received from the ECI application was invalid. System Action: The ECI mirror transaction is abnormally terminated. User Response: This abend may occur if the ECI mirror transaction is invoked directly at a CICS terminal. If the is abend occurs when running an ECI application, contact your support organization. A64D Explanation: CICS is short of Task-Private storage and a storage allocation request for a ECI operation could not be satisfied. System Action: The ECI mirror transaction is abnormally terminated. User Response: Retry the operation. If it is still unsuccessful, this may be because another transaction is using a lot of Task-Private Pool (GETMAIN) storage. Refer to any previous messages in the CSMT and console.msg files which indicate why Task-Private storage could not be allocated. A64E Explanation: An ECI application requested a syncpoint operation, but the syncpoint was unsuccessful. System Action: Any recoverable resources used by the ECI mirror transaction are rolled back and the transaction is abnormally terminated. User Response: Check the CSMT and console.msg files to see why the syncpoint operation failed. An example may be that the ECI program was requesting resources on a remote CICS system, or using DTP, and the communications link to the remote system failed. Ensure that the resources are available before retrying the ECI request. A661 Explanation: CICS was unable to release Region Pool memory, used during an attempt to access the runtime database, while performing a SET command. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: There is a serious problem with your region. A691 Explanation: CICS was unable to release Region Pool memory, used during an attempt to access the runtime database, while performing a SET command. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: There is a serious problem with your region. A701 Explanation: CICS was unable to release Region Pool memory, used during an attempt to access the runtime database, while performing a SET command. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: There is a serious problem with your region. A711 Explanation: CICS was unable to release Region Pool memory, used during an attempt to access the runtime database, while performing a SET command. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: There is a serious problem with your region. A731 Explanation: CICS was unable to release Region Pool memory, used during an attempt to access the runtime database, while performing a SET command. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: There is a serious problem with your region. A741 Explanation: It was not possible to read the region record from the runtime database during an INQUIRE SYSTEM command. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: There is a serious problem with your region. A751 Explanation: CICS was unable to release Region Pool memory, used during an attempt to access the runtime database, while performing a SET command. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: There is a serious problem with your region. The region should be restarted at the earliest opportunity. A752 Explanation: CICS was unable to allocate Region Pool memory for the runtime database while performing a SET or INQUIRE command. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: You can increase the size of the Region Pool available by restarting the region and overriding the MaxRegionPool attribute, A761 Explanation: CICS was unable to release Region Pool memory, used during an attempt to access the runtime database, while performing a SET command. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: There is a serious problem with your region. A771 Explanation: CICS was unable to release Region Pool memory, used during an attempt to access the runtime database, while performing a SET command. System Action: CICS abnormally terminates the transaction, but the region continues. User Response: There is a serious problem with your region. A82C Explanation: CICS was attempting to start a new browse or perform a new read-update but Application Server SQL resources are exhausted. A82E Explanation: CICS has encountered a problem when attempting to obtain the maximum current RBA of an ESDS file. A82L Explanation: CICS was unsuccessful when attempting to retain a lock on a record. A82M Explanation: CICS was attempting to obtain memory for file control information from the Region Pool. Insufficient memory was available. AB31 Explanation: An exception was raised in a CICS Java Application that was caught by the application and was incorrectly not rethrown. The exception indicates an internal error that cannot be handled by the application. Further information is unavailable while the application does not rethrow the exception. System Action: The transaction terminates abnormally. User Response: Examine your application and correct it to rethrown all CicsError exceptions. Then rerun the transaction to obtain further information on the internal error. This should now result in a different abend with additional information. AB40 Explanation: IIOP request abended System Action: IIOP request terminates. User Response: Check console.msg for further messages and correct the error before rerunning the IIOP request. AB41 Explanation: Internal class table corrupted System Action: See ERZ114008E. User Response: See ERZ114008E. AB42 Explanation: Java generic factory missing System Action: See ERZ114009E. User Response: See ERZ114009E. AB43 Explanation: IIOP support abended System Action: See ERZ114030E. User Response: See ERZ114030E. AB44 Explanation: An assert has been detected in the IOM component of the ORB System Action: See ERZ114033E. User Response: See ERZ114033E. AB45 Explanation: Error in class update transaction. System Action: Class update transaction terminates. User Response: Check console.msg for further messages and correct the error before rerunning the class update transaction. AB52 Explanation: CICS has detected an invalid region configuration. System Action: See ERZ115033E or ERZ115034E as appropriate. User Response: See ERZ115033E or ERZ115034E as appropriate. AB53 Explanation: CICS has detected that this is a terminal attached mirror transaction. System Action: See ERZ115023E. User Response: See ERZ115023E. AB54 Explanation: CICS mirror failed to read request data. System Action: See ERZ115024E. User Response: See ERZ115024E. AB55 Explanation: CICS mirror failed to register COMMIT/ABORT callback functions. System Action: See ERZ115025E. User Response: See ERZ115025E. AB56 Explanation: CICS mirror failed to allocate storage for commarea. System Action: See ERZ115026E. User Response: See ERZ115026E. AB57 Explanation: CICS mirror failed to send response data. System Action: See ERZ115027E. User Response: See ERZ115027E. AB58 Explanation: CICS has detected a corrupted commarea signature detected during free. System Action: See ERZ115028E. User Response: See ERZ115028E. U0101 Explanation: CICS was unable to attach the Region Pool shared memory. System Action: CICS abnormally terminates the region. User Response: Ask the system administrator to check for inconsistencies in the CICS shared memory segments using the ipcs command; these segments must have read and write permissions for user 'cics' and group 'cics'. If the problem cannot be identified, call your support organization. U0701 Explanation: CICS self-consistency checking: inconsistent ICE queue detected U0702 Explanation: CICS self-consistency checking: mismatched expiry time/next start time U0703 Explanation: CICS self-consistency checking: inconsistent ICE links U0704 Explanation: CICS self-consistency checking: inconsistent ICE links U0705 Explanation: CICS self-consistency checking: inconsistent ICQ Reqid hash values U0706 Explanation: CICS self-consistency checking: inconsistent ICQ Reqid hash values U0707 Explanation: Couldn't schedule the blocked Interval Control Element (ICE) recovery transaction User Response: During auto start, CICS has attempted to recover Interval Control Elements (ICEs), but is unable to do so because Temporary Storage is unavailable. Therefore, it attempts to schedule a transaction that will recover the blocked requests. This attempt to schedule the transaction has failed. Check that the region pool size is sufficiently large, if it is not, increase it and restart the region. Check that the attribute CUBSDelayMinutes in the Region Definitions has a reasonable value, between 1 and 5999. This symptom may be avoided by performing a cold start of the region. U0708 Explanation: The data in a Temporary Storage Queue is shorter than expected User Response: During auto start, CICS has attempted to recover Interval Control Elements (ICEs), but the Temporary Storage queue contains a record that is shorter than expected. This may be because there is a problem with Temporary Storage. Examine previous messages for an indication of the cause of the problem. This symptom may be avoided by performing a cold start of the region. U0709 Explanation: CICS was unable to free a locked resource User Response: During an attempt to delete a free a locked resource, CICS detected an inconsistency in internal data structures. If you want to investigate this problem, Check that the previous CICS self-consistency check did not detect any errors. Set the IntrospectInterval in the Region Definitions to 1 minute and restart the region. Attempt to reproduce the problem by running that same sequence of transactions again. If you can reproduce the problem, take note of the transactions that were running or were terminating when this error occurred, and contact your support organization. U0710 Explanation: Timed wait failed in Interval Control process U0711 Explanation: Failed to access terminal details User Response: While preparing to run a transaction, CICS was unable to access the details of the terminal on which the transaction attempted to run. CICS may have run out of memory. This may be due to a transaction that is looping in some way that causes CICS to acquire substantial amounts of Region Pool memory on its behalf. Check that the Region Definition value MaxRegionPool is sufficiently large. Increase this value, and restart the region. U0712 Explanation: Failed to schedule internal transaction User Response: While preparing to run an internal transaction, CICS was unable to find the transaction, the transaction name is identified in the message which accompanies this abend. The transaction definition may have been deleted or disabled in the Trsanction Definitions for the region. Check the definition for the missing transaction and correct the problem. If the definition is missing copy the definition for the transaction from another region. U0713 Explanation: Couldn't schedule the Interval Control Element (ICE) Cancel transaction User Response: CICS has attempted to cancel Interval Control Elements (ICEs), but the attempt to schedule the transaction CICE has failed. Check that the region pool size is sufficiently large, if it is not, increase it and restart the region. U0714 Explanation: CICS received an unexpected exception while processing hand posts. U1001 Explanation: CICS detected an unexpected exceptional condition. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1002 Explanation: CICS failed to attach region shared memory or task shared memory segments. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1003 Explanation: CICS failed to create TS configuration file. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1004 Explanation: CICS failed to setlocale and/or open message catalogue. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1005 Explanation: Failed to save locale. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1006 Explanation: Failed to obtain locale. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1007 Explanation: CICS failed to obtain pointer to Region record. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1008 Explanation: CICS failed to detach pointer from Region record. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1009 Explanation: CICS failed to schedule the CLAM transaction. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1010 Explanation: CICS failed to cancel the CLAM transaction. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1011 Explanation: CICS could not get CWA. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1012 Explanation: bde_ThreadCreate failure. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1013 Explanation: CICS failed to initialize task private memory. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1014 Explanation: CICS failed to create heartbeat process. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1015 Explanation: System process ended unexpectedly or in error. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1016 Explanation: CICS failed to initialize process. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1017 Explanation: CICS failed to register as an Application Manager. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1018 Explanation: CICS self consistency checking failed. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1019 Explanation: CICS failed to create the Log Daemon. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1020 Explanation: CICS failed to create the Recovery Manager. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1021 Explanation: CICS failed to create the Application Manager. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1022 Explanation: CICS failed to initialize TCA. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1024 Explanation: CICS failed to create the Transaction Server. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1025 Explanation: CICS failed to run the startup program. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1027 Explanation: CICS failed to allocate id hash table entry. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1028 Explanation: CICS failed to enable the Application Server group. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1029 Explanation: CICS failed to execute the CAIN transaction. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1030 Explanation: CICS failed to enable the Application Server class. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1031 Explanation: CICS failed to execute the CRAB transaction. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1032 Explanation: Unable to access listener definition record or unable to create CICS listener process. Messages will have been logged to indicate the nature of the problem. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U1033 Explanation: This copy of CICS is not licensed to run. The CICS License Manager was not able to locate a valid license. Additional messages indicate the reason for the licensing failure. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If you require assistance in licensing your copy of CICS, contact your support organization. U1034 Explanation: The CICS region was configured to use DB2 for its file and queue management but CICS was unable to determine which DB2 instance to use. This was because the DB2INSTANCE environment variable and the RDBMSInstance entry in the RD stanze were both empty. System Action: CICS abnormally terminates the region. User Response: Determine which DB2 instance is to be used for the CICS file and queue management and set this value in the RDBMSInstance field of the RD stanza or in the DB2INSTANCE environment variable. If the problem persists, contact your support organization. U1035 Explanation: The CICS region was configured to use Oracle for its file and queue management but CICS was unable to determine which Oracle instance to use. This was because the ORACLE_SID environment variable and the RDBMSInstance entry in the RD stanze were both empty. System Action: CICS abnormally terminates the region. User Response: Determine which Oracle instance is to be used for the CICS file and queue management and set this value in the RDBMSInstance field of the RD stanza or in the ORACLE_SID environment variable. If the problem persists, contact your support organization. U1036 Explanation: The CICS region was configured to use Oracle for its file and queue management but CICS was unable to determine the value for ORACLE_HOME. System Action: CICS abnormally terminates the region. User Response: Determine the correct setting for ORACLE_HOME and export the ORACLE_HOME environment variable or define it in the CICS region's environment file. If the problem persists, contact your support organization. U1037 Explanation: An IIOP listener definition must be defined if an IIOP SSL listener definition is defined. System Action: CICS abnormally terminates the region. User Response: Define both an IIOP and an IIOP SSL listener definition if you require IIOP SSL support. U1038 Explanation: An IIOP SSL listener definition is defined but the IIOP version for generated object references is set to 1.0. System Action: CICS abnormally terminates the region. User Response: Define the IIOP version for generated object references to 1.1 if you require an IIOP SSL Listener. U1039 Explanation: An IIOP workload-managed SSL port is defined but no IIOP SSL Listener hsa been defined for this region. System Action: CICS abnormally terminates the region. User Response: Define an IIOP SSL Listener if you intend to support an IIOP workload-managed SSL configuration. U1101 Explanation: CICS could not initialize the CICS terminal component. System Action: CICS terminates the region abnormally. User Response: Examine previous messages to see if the region was short of storage. U1401 Explanation: One of the CICS control processes has detected an exceptional condition. System Action: CICS abnormally terminates the region. User Response: This abend indicates an internal problem in one of the CICS control processes. If the region definition SysDump attribute is set to 'yes' a region dump file is produced. This file should be saved. Restart the region (ensuring the region is configured to take a dump if the problem recurs). Contact your support organization. U1403 Explanation: CICS made an unsuccessful attempt to attach to the shared memory segment of the region. System Action: CICS abnormally terminates the region. User Response: This abend indicates an internal CICS problem. If the region definition SysDump attribute is set to 'yes' a region dump file is produced. This file should be saved. Restart the region (ensuring the region is configured to take a dump if the problem recurs). Contact your support organization. U1404 Explanation: CICS made an unsuccessful attempt to browse the transaction definition database. System Action: CICS abnormally terminates the region. User Response: This abend indicates an internal CICS problem. If the region definition SysDump attribute is set to 'yes' a region dump file is produced. This file should be saved. Restart the region (ensuring the region is configured to take a dump if the problem recurs). Contact your support organization. U1501 Explanation: The periodic consistency check performed by CICS on the Program Control structures detects an error that CICS could not correct. These data structures hold information about programs running at each logical level. System Action: The CICS region is abnormally terminated. User Response: Because the Program Control data structures are held in the Region Pool it is unlikely that the invalid data has been produced by application code. Any dump file produced should be saved for use by your support organization. If the problem persists contact your support organization. U1507 Explanation: CICS is unable to free Region Pool storage allocated for Program Control data structures. These data structures hold information about programs running at each logical level. System Action: CICS abnormally terminates the region. User Response: Because the Program Control data structures are held in the Region Pool, the problem encountered freeing the data structures is unlikely to be caused by application code. It is more likely to be caused by an inconsistency in the CICS internal data structures. If the problem reoccurs, save any dump file produced and contact your support organization. U1512 Explanation: CICS is unable to delta a Program Definition database record after locking it. This is likely to be caused by an inconsistency in the CICS internal data structures. System Action: CICS abnormally terminates the region. User Response: Any CICS internal data structure inconsistencies are unlikely to be caused by application code, since they are held in the Region Pool. Save any dump file produced and contact your support organization. U1513 Explanation: CICS is unable to get exclusive access to a Program Definition database entry. CICS encountered an error freeing Region Pool storage during this operation. This is likely to be caused by an inconsistency in the CICS internal data structures. System Action: CICS abnormally terminates the region. User Response: Any CICS internal data structure inconsistencies are unlikely to be caused by application code, since they are held in the Region Pool. Save any dump file produced and contact your support organization. U1514 Explanation: CICS is unable to attach shared memory used for the Region Pool after returning from application code. Region Pool memory is protected while running application code, by detaching it. System Action: CICS abnormally terminates the region. User Response: This error could occur if shared memory segments have been removed accidentally. Otherwise, it could be caused by a CICS internal problem. In this case, save any dump file produced and contact your support organization. U1516 Explanation: CICS is unable to update the database record for the principal facility, during an EXEC CICS RETURN TRANSID COMMAREA command. This is likely to be caused by an inconsistency in the CICS internal data structures. System Action: CICS abnormally terminates the region. User Response: Any CICS internal data structure inconsistencies are unlikely to be caused by application code, since they are held in the Region Pool. Save any dump file produced and contact your support organization. U1517 Explanation: CICS is unable to load the C language support program cicsprC. cicsprC is used to load and run C application programs. System Action: CICS abnormally terminates the region. User Response: Investigate the cause of the load failure using the ERZ015035E error message logged earlier and the symptom records. Check that the full pathname of cicsprC recorded in error message ERZ015035E refers to a valid executable file which is accessible. If this file does not exist, or is inaccessible, contact your system administrator, because CICS may not be installed properly, or it may have become corrupted. In this case the system administrator can consider reinstalling CICS. If the problem cannot be solved and persists, then save any dump file produced and contact your support organization. U1518 Explanation: CICS is unable to allocate enough memory, from the Region Pool, to initialize the quickcell pools. System Action: CICS abnormally terminates the region. User Response: As for message ERZ015036E. U1601 Explanation: The data structures used to drive syncpoint processing are inconsistent. System Action: See ERZ016026E. User Response: See ERZ016026E. U1605 Explanation: CICS has detected an internal error which has prevented a logical unit of work from starting or continuing. System Action: See ERZ016005E. User Response: See ERZ016005E. U1606 Explanation: CICS has obtained invalid information from the system log and is unable to complete recovery processing. System Action: See ERZ016006E. User Response: See ERZ016006E. U1610 Explanation: During system startup, CICS is unable to acquire sufficient Region Pool storage for the data structures needed to process logical units of work. System Action: See ERZ016010E. User Response: See ERZ016010E. U1611 Explanation: CICS is unable to recover CICS resources to the correct state. This message is preceded by another message indicating the reason, which may have been sent to destination CSMT. System Action: See ERZ016011E. User Response: See ERZ016011E. U1612 Explanation: During recovery processing at system startup, the effects of a committed transaction could not be re-applied. This message is preceded by another message indicating the reason, which may have been sent to destination CSMT. System Action: See ERZ016012E. User Response: See ERZ016012E. U1614 Explanation: CICS is attempting to release a block of Region Pool storage but is unsuccessful. System Action: See ERZ016014E. User Response: See ERZ016104E. U1616 Explanation: CICS has detected an error in the Region Control Area (RCA) which cannot be corrected. System Action: See ERZ016016E. User Response: See ERZ016016E. U1625 Explanation: CICS is unable to start because the Remote Procedure Call (RPC) runtime system has rejected a request from CICS to use the named protocol. System Action: See ERZ016025E. User Response: See ERZ016025E. U1627 Explanation: CICS is attempting to create a Recovery Server process but is unsuccessful. This message is preceded by other messages describing the condition in more detail. System Action: See ERZ016027E. User Response: See ERZ016027E. U1631 Explanation: CICS is unable to complete the initialization of a Recovery Server. System Action: See ERZ016031E. User Response: See ERZ016031E. U1633 Explanation: CICS has encountered an internal problem whilst attempting to reprepare a logical unit of work. Recovery processing cannot continue. System Action: See ERZ016033E. User Response: See ERZ016033E. U1637 Explanation: CICS is unable to complete the initialization of a recovery server or the recovery manager. System Action: See ERZ016037E. User Response: See ERZ016037E. U1639 Explanation: CICS is unable to initialise the Transactional Remote Procedure Call (TRPC) service in a CICS server process. System Action: See ERZ016039E. User Response: See ERZ016039E. U1644 Explanation: CICS is unable to register an XA-compliant resource manager with the Transaction Manager XA Service because of an internal problem in the Transaction Manager XA Service code. System Action: See ERZ016044E. User Response: See ERZ016044E. U1645 Explanation: CICS is unable to initialize the Transaction Manager XA Service due to an internal problem in the Transaction Manager Service code. System Action: See ERZ016045E. User Response: See ERZ016045E. U1646 Explanation: CICS can not locate, or does not have sufficient permissions to access, an XA Support module for an External Resource Manager. System Action: See ERZ016046E. User Response: See ERZ016046E. U1647 Explanation: CICS is unable to load an External Resource Managers XA Support file into the application server. This message indicates an error from the operating system load function or an error from the operating system loadbind function. System Action: See ERZ016047E. User Response: See ERZ016047E. U1651 Explanation: CICS has detected an unexpected fatal exception. System Action: See ERZ016051E. User Response: See ERZ016051E. U1655 Explanation: CICS is unable to terminate a logical unit of work. System Action: See ERZ016055E. User Response: See ERZ016055E. U1671 Explanation: CICS was unable to release a storage buffer during Transactional Remote Procedure Call (TRPC) initialization. System Action: See ERZ016071E. User Response: See ERZ016071E. U1672 Explanation: CICS detected the unexpected termination of an application server processing unfinished recoverable work. System Action: See ERZ016072E. User Response: See ERZ016072E. U1675 Explanation: CICS is unable to attach shared memory to the finished function registered with the tran service. System Action: See ERZ016075E. User Response: See ERZ016075E. U1678 Explanation: CICS attempted to load the Product Definitions but was unsuccessful. This message is preceded by other messages describing the cause of the failure in more detail. System Action: See ERZ016078E. User Response: See ERZ016078E. U1681 Explanation: Filesystem switch for DB2 could not be loaded. System Action: See ERZ016081E. User Response: See ERZ016081E. U1682 Explanation: Filesystem switch for SFS could not be loaded. System Action: See ERZ016082E. User Response: See ERZ016082E. U1683 Explanation: Filesystem switch file for DB2 could not be found. System Action: See ERZ016083E. User Response: See ERZ016083E. U1684 Explanation: Filesystem switch file for SFS could not be found. System Action: See ERZ016084E. User Response: See ERZ016084E. U1701 Explanation: During system startup, CICS could not allocate Region Pool storage for its internal data structures. System Action: CICS shuts down the region. User Response: Increase the size of the Region Pool by restarting the region with an override for the value of the MaxRegionPool attribute in the Region Definition (RD). If the problem persists, contact your support organization. U2203 Explanation: See message ERZ022003E. U2224 Explanation: CICS was unable to complete recovery processing for Transient Data queues. System Action: The region is abnormally terminated. User Response: Check preceding messages for the cause of the error. The recovery data is stored in the filesystem, so this may be caused if CICS is unable to access that data. U2231 Explanation: See message ERZ022031E. System Action: See message ERZ022031E. User Response: See message ERZ022031E. U2238 Explanation: See message ERZ022038E. System Action: See message ERZ022038E. User Response: See message ERZ022038E. U2239 Explanation: See message ERZ022039E. System Action: See message ERZ022039E. User Response: See message ERZ022039E. U2242 Explanation: See message ERZ022402E. System Action: See message ER0Z22042E. User Response: See message ERZ022042E. U2243 Explanation: See message ERZ022043E. System Action: See message ER0Z22043E. User Response: See message ERZ022043E. U2251 Explanation: See message ERZ022051E. System Action: See message ERZ022051E. User Response: See message ERZ022051E. U2264 Explanation: See message ERZ022064E. System Action: See message ERZ022064E. User Response: See message ERZ022064E. U2265 Explanation: See message ERZ022065E. System Action: See message ERZ022065E. User Response: See message ERZ022065E. U2269 Explanation: See message ERZ022069E. System Action: See message ERZ022069E. User Response: See message ERZ022069E. U2270 Explanation: See message ERZ022070E. System Action: See message ERZ022070E. User Response: See message ERZ022070E. U2274 Explanation: See message ERZ022074E. System Action: See message ERZ022074E. User Response: See message ERZ022074E. U2287 Explanation: See message ERZ022087E. System Action: See message ERZ022087E. User Response: See message ERZ022087E. U2288 Explanation: See message ERZ022088E. System Action: See message ERZ022088E. User Response: See message ERZ022088E. U2289 Explanation: See message ERZ022089E. System Action: See message ERZ022089E. User Response: See message ERZ022089E. U2312 Explanation: CICS is unable to allocate enough memory, from the Region Pool, to initialize Temporary Storage (TS). System Action: CICS abnormally terminates the region. User Response: You can increase the size of the Region Pool available by restarting the region and overriding the MaxRegionPool attribute, with a larger value, on the command line. U2313 Explanation: CICS is unable to save information for unprotected asynchronous start requests in the filesystem. System Action: CICS abnormally terminates the region. User Response: Determine the cause of the error from associated messages and resolve. Restart the region and resubmit the start requests. U2314 Explanation: CICS is unable to restore information for unprotected asynchronous start requests from the filesystem as the file server is unavailable. System Action: CICS abnormally terminates the region. User Response: Make the file server available and restart the region. U2315 Explanation: CICS self-consistency checking has detected that the chain of queues involved in the current LUW for the transaction has been overwritten by invalid data. System Action: CICS abnormally terminates the region. User Response: Restart the CICS region. U2319 Explanation: CICS could not rewrite a runtime database TS entry. System Action: CICS abnormally terminates the region. User Response: Refer to any previous messages indicating why the runtime database entry could not be updated. U2329 Explanation: CICS cannot insert a runtime database entry during Temporary Storage (TS) restoration of queues from the system journal. System Action: CICS abnormally terminates the region. User Response: Restart the region, if the error continues to occur then Cold start the region. U2334 Explanation: The size of the Temporary Storage (TS) checkpoint buffer, read from the system journal, has been overwritten. It is the wrong size. System Action: CICS abnormally terminates the region. User Response: Cold Start the region. U2342 Explanation: CICS Temporary Storage (TS) self consistency checking has found a TS queue runtime database entry with an invalid Status attribute value. System Action: CICS abnormally terminates the region. User Response: Restart the CICS region. U2348 Explanation: CICS self-consistency checking has found an Auxiliary Temporary Storage (TS) queue containing Main TS queue data. System Action: CICS abnormally terminates the region. User Response: Restart the CICS region. U2353 Explanation: CICS self-consistency checking has found a mismatch between maintained count of LUWs and actual number of LUWs. System Action: CICS abnormally terminates the region. User Response: Restart the CICS region. MVS_EQUIVALENT: None. U2354 Explanation: CICS self-consistency checking has found an invalid address to the Temporary Storage (TS) private management data for a queue. System Action: CICS abnormally terminates the region. User Response: Restart the CICS region. U2356 Explanation: CICS self-consistency checking has found an unknown Temporary Storage (TS) queue type in its internal management data. System Action: CICS abnormally terminates the region. User Response: Restart the region, if CICS self-consistency checking continues to detect inconsistencies contact your support organization. U2358 Explanation: CICS self-consistency checking has found an unknown Temporary Storage (TS) queue Action in its internal management data. System Action: CICS abnormally terminates the region. User Response: Restart the CICS region. U2362 Explanation: CICS could not provide access to Auxiliary Temporary Storage (TS) queues. System Action: CICS abnormally terminates the region. User Response: Refer to the preceding message(s) that detail why CICS was unable to access Auxiliary TS queues. Restarting the Auxiliary TS File Server(s) should enable access to TS queues. If the problem persists it is likely that the configuration of the TS File Server(s) is suspect. U2372 Explanation: CICS was unable to complete recovery processing for Recoverable Temporary Storage queues. System Action: The region is abnormally terminated. User Response: Check preceding messages for the cause of the error. The recovery data is stored in the filesystem, so this may be caused if CICS U2404 Explanation: CICS is unable to attach shared memory to the callback function registered with the Log Service. System Action: See ERZ024004E. User Response: See ERZ024004E. U2406 Explanation: CICS is unable to write a restart record to a log file. If the region were allowed to continue this problem could prevent CICS recovery algorithms from working correctly. System Action: See ERZ024006E. User Response: See ERZ024006E. U2407 Explanation: This abend may be caused by any of the following: • • CICS has been auto-started after the log service was cold started. • CICS is unable to determine the position in a log file at which to begin recovery processing. A restart position is always set by CICS when it creates a log file so this problem suggests a malfunction in either CICS or the Log Service. • CICS is unable to read a log record at the restart position in a log. This error suggests that the restart position for the log file has been overwritten with invalid data. • CICS has read a record at the restart position in the log file but it contained invalid data. System Action: See ERZ024007E. User Response: See ERZ024007E. U2409 Explanation: An attempt to read from a log file was unsuccessful. System Action: See ERZ024009E. User Response: See ERZ024009E. U2411 Explanation: An unexpected record type was read from a log file. System Action: See ERZ024011E. User Response: See ERZ024011E. U2413 Explanation: This abend may be caused by any of the following: • • CICS is unable to open a Log Service cursor in a log file. This operation attempts to establish a context for subsequent reads by selecting a subset of the log records to be retrieved, a position in the log and a direction (See the Encina Log Service documentation for more information). This problem prevents the retrieval from the log of records required to recover CICS resources correctly. • CICS is unable to change the position of a Log Service cursor in a log. This problem prevents the retrieval from the log of records required to recover CICS resources correctly. System Action: See ERZ024013E. User Response: See ERZ024013E. U2416 Explanation: The Log Service has an internal problem from which it is unable to continue. It has requested an action from CICS to terminate the region immediately. System Action: See ERZ024016E. User Response: See ERZ024016E. U2419 Explanation: CICS has recovered the last successful checkpoint written to the Log Service, but is unable to find data for all the modules required. System Action: See ERZ024019E. User Response: See ERZ024019E. U2425 Explanation: CICS has detected a mismatch between a counter and the actual number of objects existing. As these objects are allocated out of the region pool, it is not likely that this problem is caused by user action or user transactions. System Action: See ERZ024025E. User Response: See ERZ024025E. U2430 Explanation: CICS is unable to find a log for a recovery server that it has started. The set of logs available for use in recovery processing is maintained in memory allocated from the region pool and is retrieved from the CICS master log (identified by the CLogName attribute in RD) during initial recovery processing. This message is produced when the CICS recovery manager (cicsrm process) attempts to read from a log not present in the available list. This should not happen unless an internal problem exists or unless region pool memory has been overwritten. System Action: See ERZ024030E. User Response: See ERZ024030E. U2450 Explanation: Failed opening the master system journal System Action: See ERZ024050E. User Response: See ERZ024050E. U2451 Explanation: CICS is unable to write to the specified log file. System Action: See ERZ024051E. User Response: See ERZ024051E. U2454 Explanation: CICS is attempting to obtain memory from the Region Pool for reading the system log. Insufficient memory is available. System Action: See ERZ024054E. User Response: See ERZ024054E. U2455 Explanation: CICS is attempting to obtain memory for log archive control information from the Region Pool. Insufficient memory is available. System Action: See ERZ024055E. User Response: See ERZ024055E. U2456 Explanation: CICS is attempting to obtain Task Shared Pool memory for a start of checkpoint buffer to contain log management data. Insufficient memory is available. System Action: See ERZ024056E. User Response: See ERZ024056E. U2457 Explanation: CICS writes some log data into buffered storage to improve performance. It also attempts to write log data direct to permanent storage (storage which survives a system crash or a restart of the Log Service), forcing all earlier buffered data to become permanent too. This message is produced when the Log Service is unable to make data permanent when requested to do so by CICS. System Action: See ERZ024057E. User Response: See ERZ024057E. U2460 Explanation: CICS is unable to open an Application Server log file during recovery processing. The CICS recovery manager obtains the list of Application Server log files needing recovery from the CICS master log, and stores this list in memory obtained from the Region Pool. Possible causes of this problem therefore include: • • Region Pool memory has been overwritten with invalid data (either before the list is written to the Log Service, or after the list has been retrieved from the Log Service) • Log Service data has been overwritten with invalid data • Other users of the Log Service have deleted the log file • The Log Service has been cold started since your region was started • Another process has the log file opened already. It is unlikely that misbehaving user transactions could cause this problem. System Action: See ERZ024060E. User Response: See ERZ024060E. U2463 Explanation: CICS is attempting to obtain memory from the Region Pool for a log control list element. Insufficient memory is available. System Action: See ERZ024063E. User Response: See ERZ024063E. U2467 Explanation: CICS could not initialize the log service client whilst attempting to start a CICS process. This is usually because the logserver process has died or because of RPC communication problems. System Action: See ERZ024067E. User Response: See ERZ024067E. U2470 Explanation: CICS is attempting to open a user journal defined with InitialOpenFlag=yes in the Journal Definitions (JD). It is unable to create and insert a TDQ runtime database entry corresponding to the user journal being opened because there is insufficient memory in the Region Pool. System Action: See ERZ024070E. User Response: See ERZ024070E. U2475 Explanation: CICS is attempting to write to a user journal which is designated as a "crucial" journal. CICS is unable to write to this journal. Possible causes include deadlock timeout, insufficient space on the relevant filesystem and bad destination path specified in the journal definition (JD). System Action: See ERZ024075E. User Response: See ERZ024075E. U2497 Explanation: CICS detected an unexpected fatal exception. System Action: See ERZ024097E. User Response: See ERZ024097E. U2498 Explanation: CICS detected an unrecoverable error whilst attempting to write to the system log. System Action: See ERZ024066E. User Response: See ERZ024066E. U2499 Explanation: CICS was unable to introspect Reg data System Action: See ERZ24113E. User Response: See ERZ24113E. U2501 Explanation: CICS failed to initialize server side transaction support System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. U3405 Explanation: CICS is unable to allocate enough memory, from the Region Pool, to initialize the runtime databaze. System Action: CICS abnormally terminates the region. User Response: As for message ERZ034005E. U3406 Explanation: The value in RD stanza ClassTableSize attribute for the class is invalid. System Action: CICS abnormally terminates the region. User Response: As for message ERZ034004E. U3408 Explanation: The CICS-private transaction CURD, used in CICS region to Resource Definition Online (RDO) communications, made an unsuccessful attempt to send data to RDO. System Action: CICS abnormally terminates the region. User Response: As for message ERZ034068E. U3410 Explanation: CICS is unable to initialize the runtime database recovery image during region startup. System Action: CICS abnormally terminates the region. User Response: As indicated by the messages detailing the errors encountered during runtime database recovery image initialization. U3411 Explanation: CICS detected error(s) during initialization of the runtime database. System Action: CICS abnormally terminates the region. User Response: As indicated by the message(s) detailing the errors during database initialization. U3466 Explanation: CICS could not cleanup the runtime database data for the task that is terminating. This is probably due to internal data corruption. System Action: CICS abnormally terminates the region. User Response: As for message ERZ034066E. U3469 Explanation: CICS self-consistency checking has detected that a runtime database internal control structure is inconsistent. System Action: CICS abnormally terminates the region. User Response: As for message ERZ034069E. U3470 Explanation: CICS self-consistency checking has detected that a runtime database internal control structure contains no table entries. This is inconsistent with the expected minimum of one. System Action: CICS abnormally terminates the region. User Response: As for message ERZ034070E. U3901 Explanation: Insufficient storage to initialise the transaction scheduler System Action: Refer to message ERZ039004E User Response: Refer to message ERZ039004E U4419 Explanation: CICS has detected an unexpected fatal exception. System Action: See ERZ044019E. User Response: See ERZ044019E. U4511 Explanation: CICS could not load a user defined External Security Manager (ESM) into the region at region start up. System Action: CICS abnormally terminates the region during start up. User Response: Check console.msg for messages from CICS that concern problems with the External Security Manager (ESM). U4512 Explanation: CICS could not initialize the user defined External Security Manager (ESM). The ESM initialization module returned an error. System Action: CICS abnormally terminates the region during start up. User Response: You should check the documentation and source code of the ESM to ascertain in what circumstances errors can be raised during ESM initilization. U4514 Explanation: CICS could not support the supplied cell name. System Action: CICS abnormally terminates the region during start up. User Response: You should ask the System Administrator to reduce the length of the name of the DCE Cell. U4530 Explanation: CICS requires DCE network credentials to authenticate itself within a networked environment. For security reasons these credentials have a limited lifetime and must be periodically refreshed if CICS is to operate. To perform a credentials refresh CICS needs to obtain information regarding its DCE network credentials. This has failed because the credentials are invalid or have been overwritten. System Action: CICS abnormally terminates the region during start up. User Response: Check console.msg for messages from CICS that concern problems with the network credentials. U4531 Explanation: CICS requires DCE network credentials to authenticate itself within a networked environment. For security reasons these credentials have a limited lifetime and must be periodically refreshed if CICS is to operate. CICS could not refresh its network credentials and cannot continue. System Action: CICS abnormally terminates the region. User Response: Check console.msg for messages from CICS that concern problems with the network credentials. U4533 Explanation: CICS requires DCE network credentials to authenticate itself within a networked environment. CICS could not establish DCE network credentials and so the region cannot start. System Action: CICS abnormally terminates the region during start up. User Response: Check console.msg for messages from CICS that concern problems with the network credentials. U4534 Explanation: You have tried to change your DCE password, but CICS was unable to obtain or release a valid DCE context in order to do this for your application server. System Action: CICS abnormally terminates the application server. User Response: Check console.msg for further messages from CICS that may indicate what went wrong. U4535 Explanation: CICS requires DCE network credentials to authenticate itself within a networked environment. For security reasons these credentials have a limited lifetime and must be periodically refreshed if CICS is to operate. CICS could not refresh its network credentials and cannot continue because of a software problem within CICS. System Action: CICS abnormally terminates the region. User Response: This abend indicates a problem in CICS. Contact your support organization. U4536 Explanation: CICS could not allocate storage from the region pool. System Action: CICS abnormally terminates the region. User Response: Check the value of your MaxRegionPool, MaxTaskPrivatePool and MaxTSHPool region database attributes. Increase these values and try again. U4537 Explanation: You have tried to change your DCE password, but there has been an unexpected DCE error. System Action: CICS abnormally terminates the application server. User Response: Check console.msg for further messages from CICS that may indicate what went wrong. U4538 Explanation: During CICS process initialization, a failure occurred while attempting to retrieve the DCE context for the process. System Action: CICS abnormally terminates the process. User Response: Check console.msg for further messages from CICS that may indicate what went wrong. U4539 Explanation: CICS attempted to change the password for its DCE principal but failed. System Action: CICS abnormally terminates. User Response: Check console.msg for further messages from CICS that may indicate what went wrong. U4801 Explanation: CICS self-consistency checking detected some unrecoverable problems in the region or task shared pools. System Action: CICS abnormally terminates the region. User Response: This abend is accompanied by messages in console.msg. Use these messages and the information associated with them to determine what action to take. U4802 Explanation: CICS attempted to free region pool storage which was not allocated. This abend usually indicates a software problem in CICS. System Action: CICS abnormally terminates the region. User Response: This abend is accompanied by messages in console.msg. Use these messages and the information associated with them to determine what action to take. Contact your support organization. U4803 Explanation: CICS did not complete initialization of the region or task shared pools. System Action: CICS abnormally terminates the region at start up. User Response: There may be invalid parameters in the Region Definition defining the configuration of the region or task shared pools. See CICS Administration Guide for information on configuring these attributes. The system limits on numbers or sizes of shared memory segments may have been exceeded, or else there may be insufficient memory to fulfill the request. Restart the region with new values in the Region Definitions or using CICS command line parameters at start up. U4911 Explanation: CICS was unable to process your request to either start or stop the auxiliary trace facility, because it was unable to contact the CICS main process. More details may have been provided in an earlier messages. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for guidance on resolving the problem. If the problem persists, contact your support organization. U4916 Explanation: CICS was unable to save the product trace restart configuration in the region_restart file. More details may have been provided by an earlier message. System Action: CICS abnormally terminates the region. User Response: Remove the CICS restart file and restart the region, specifying a cold start. Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U5001 Explanation: CICS is unable to re-attach shared memory. Further messages may be found in the message log and give more information about the problem. System Action: CICS abnormally terminates the region. User Response: Restart the region. U5104 Explanation: CICS was unable to intialise the statistics file, because it couldn't be opened. System Action: CICS abnormally terminates the region. User Response: Ensure that the directory, in which the statistics file is situated, exists. Also ensure that CICS has permission to write to the statistics file. U5201 Explanation: CICS was unable to allocate storage to perform a wait during a system dump. System Action: CICS abnormally terminates the process. User Response: Increase the Region Definition value MaxRegionPool and restart the region. U5310 Explanation: CICS was unable to save the statistics restart configuration to the region restart file. System Action: CICS abnormally terminates the region. User Response: Remove the CICS restart file and restart the region, specifying a COLD start. Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U5655 Explanation: A crucial mutual exclusion lock is held by a terminated process. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U5701 Explanation: CICS detected an unsuccessful condition. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U5702 Explanation: CICS message processing facility has overwritten a buffer. System Action: CICS abnormally terminates the current execution environment: in the runtime, the whole region is terminated; elsewhere, the current process is terminated. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U5733 Explanation: CICS is unable to attach shared memory. Further messages may be found in the message log and give more information about the problem. System Action: CICS abnormally terminates the region. User Response: Restart the region. U5801 Explanation: CICS failed to handle a synchronous terminating signal. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U5802 Explanation: CICS failed to attach the Region Pool shared memory. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U5804 Explanation: Server side transaction support was requested but is not supported on this platform System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. U5805 Explanation: An attempt was made to acquire a CICS license; however, this was unsuccessful. Either a license does not exist, an expiry date has passed or the license information has been tampered with. System Action: CICS abnormally terminates the region. User Response: The trial period has expired. Contact your support organization to buy a copy of CICS. U5806 Explanation: CICS is configured to use Local SNA but the SunLink SNA shared library sunlu62.so could not be loaded. This probably means that you have not installed SunLink SNA correctly. There is either a Listener Definition (LD) entry or a Communications Definition (CD) entry that references Local SNA. System Action: CICS abnormally terminates the region. User Response: If you would like to use Local SNA then install SunLink SNA correctly. If you do not want to use SNA then remove or change the definitions that reference Local SNA. CICS expects to find the SunLink SNA shared library in /opt/SUNWlu62 or in /opt/SUNWappc or in a directory in your LD_LIBRARY_PATH. U5807 Explanation: CICS could not find a necessary SNA function in the SNA shared library sunlu62.so. System Action: CICS abnormally terminates the region. User Response: Install SunLink SNA correctly since it appears to be corrupted. U5808 Explanation: CICS failed to load SNA support System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. U5810 Explanation: CICS is configured to use Local SNA but the APPC library for your SNA product could not be found. System Action: CICS abnormally terminates the region. User Response: If you would like to use Local SNA then ensure your SNA product is installed correctly and set the CICS_SNA_APPC_LIBRARY environment variable to the full path name of the SNA APPC library. If you do not wish to use local SNA, then remove all Listener Definition (LD) entries that have Protocol=SNA from your region. U5811 Explanation: CICS is configured to use Local SNA but the Attach Manager library for your SNA product could not be found. System Action: CICS abnormally terminates the region. User Response: If you would like to use Local SNA then ensure your SNA product is installed correctly and set the CICS_SNA_ATTACH_LIBRARY environment variable to the full path name of the SNA attach manager library. If you do not wish to use local SNA, then remove all Listener Definition (LD) entries that have Protocol=SNA from your region. U58400 Explanation: A crucial mutual exclusion lock is held by a terminated process. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U58401 Explanation: The iconv-emulation code could not initialize correctly. System Action: CICS abnormally terminates the region. User Response: Refer to the associated messages for further guidance on resolving the problem. If the problem persists, contact your support organization. U6201 Explanation: CICS cannot free the memory allocated for the terminal i/o area in the Task Shared Pool. System Action: CICS abnormally terminates the region. User Response: Check your program to see that it is not incorrectly writing to, or freeing memory in the Task Shared Pool. Retry the transaction. U6301 Explanation: CICS has detected an unexpected fatal exception. System Action: See ERZ063008E. User Response: See ERZ063008E. U8005 Explanation: See message ERZ080005E System Action: CICS abnormally terminates the region User Response: See message ERZ080005E for appropriate responses to this problem. U8008 Explanation: See message ERZ080008E System Action: CICS abnormally terminates the region User Response: See message ERZ080008E for appropriate responses to this problem. U8022 Explanation: See message ERZ080022E System Action: CICS abnormally terminates the region User Response: See message ERZ080022E for appropriate responses to this problem. U8023 Explanation: See message ERZ080023E System Action: CICS abnormally terminates the region User Response: See message ERZ080023E for appropriate responses to this problem. U8025 Explanation: See message ERZ080025E System Action: CICS abnormally terminates the region User Response: See message ERZ080025E for appropriate responses to this problem. U8030 Explanation: See message ERZ080030E System Action: CICS abnormally terminates the region User Response: See message ERZ080030E for appropriate responses to this problem. U8032 Explanation: See message ERZ080032E System Action: CICS abnormally terminates the region User Response: See message ERZ080032E for appropriate responses to this problem. U8033 Explanation: See message ERZ080033E System Action: CICS abnormally terminates the region User Response: See message ERZ080033E for appropriate responses to this problem. U8034 Explanation: See message ERZ080034E System Action: CICS abnormally terminates the region User Response: See message ERZ080034E for appropriate responses to this problem. U8035 Explanation: See message ERZ080035E System Action: CICS abnormally terminates the region User Response: See message ERZ080035E for appropriate responses to this problem. U8036 Explanation: See message ERZ080036E System Action: CICS abnormally terminates the region User Response: See message ERZ080036E for appropriate responses to this problem. U8038 Explanation: See message ERZ080038E System Action: CICS abnormally terminates the region User Response: See message ERZ080038E for appropriate responses to this problem. U8039 Explanation: See message ERZ080039E System Action: CICS abnormally terminates the region User Response: See message ERZ080039E for appropriate responses to this problem. U8041 Explanation: See message ERZ080041E System Action: CICS abnormally terminates the region User Response: See message ERZ080041E for appropriate responses to this problem. U8045 Explanation: See message ERZ080045E System Action: CICS abnormally terminates the region User Response: See message ERZ080045E for appropriate responses to this problem. U8046 Explanation: See message ERZ080046E System Action: CICS abnormally terminates the region User Response: See message ERZ080046E for appropriate responses to this problem. U8047 Explanation: See message ERZ080047E System Action: CICS abnormally terminates the region User Response: See message ERZ080047E for appropriate responses to this problem. U8048 Explanation: See message ERZ080048E System Action: CICS abnormally terminates the region User Response: See message ERZ080048E for appropriate responses to this problem. U8049 Explanation: See message ERZ080049E System Action: CICS abnormally terminates the region User Response: See message ERZ080049E for appropriate responses to this problem. U8087 Explanation: See message ERZ080087E System Action: CICS abnormally terminates the region UA401 Explanation: Insufficient storage to initialise CICS Open Listener component. System Action: See ERZ106001E. UB401 Explanation: Unable to attach shared memory System Action: See ERZ114003E. User Response: See ERZ114003E. UB402 Explanation: Unable to create .odbc.ini file System Action: See ERZ114011E. User Response: See ERZ114011E. UB404 Explanation: No entry in class update table System Action: See ERZ114027E and ERZ114028E as appropriate. User Response: See ERZ114027E and ERZ114028E as appropriate. UB406 Explanation: Unable to start java virtual machine within a CICS application server process System Action: See ERZ114036E. User Response: See ERZ114036E. UB407 Explanation: Unable to allocate region storage System Action: See ERZ114041E. User Response: See ERZ114041E. UB408 Explanation: Invalid IIOP configuration data System Action: See ERZ114042E, ERZ114043E, ERZ114044E, ERZ114049E and ERZ114050E as appropriate. User Response: See ERZ114042E, ERZ114043E, ERZ114044E, ERZ114049E and ERZ114050E as appropriate. UB519 Explanation: CICS has detected an unexpected fatal exception. System Action: See ERZ115019E. User Response: See ERZ115019E. UB520 Explanation: CICS has detected an unexpected fatal exception. System Action: See ERZ115020E. User Response: See ERZ115020E. ________________________________________ ________________________________________ [ (C) and (TM) ] Copyright IBM Corporation 1999. All Rights Reserved