dfhe5_codes_deleted.html |
Last updated: Saturday, 15 June 2019These abend codes are discontinued in CICS® Transaction Server for z/OS®, Version 5 Release 2.
No abend codes were deleted in CICS Transaction Server for z/OS, Version 5 Release 2.
The following abend codes were deleted in earlier releases:
| Abend code | Abend text |
|---|---|
| ABX9 | A next BMS BRMQ vector in the input message passed to the formatter does not contain the mapname requested to answer a RECEIVE MAP request. |
| AECY | The task was purged before a request to the storage manager (SM) domain was able to complete successfully. The domain that first detected the purged condition will have provided an exception trace. |
| AECZ | An error (INVALID, DISASTER or unexpected EXCEPTION response) has occurred on a call to the storage manager (SM) domain. The domain that detected the original error will have provided an exception trace, a console message and, possibly, a system dump (depending on the options specified in the dump table). |
| AII1 | An IIOP Request Receiver transaction (default CIRR) was started invalidly. This transaction can only be initiated internally by CICS. |
| AII2 | The IIOP Request Receiver program DFHIIRR returned an exception which may have been caused by data received from the client. |
| AII3 | An IIOP Request Receiver task has been purged. |
| AII4 | The IIOP Request Receiver program DFHIIRR has returned a disaster response due to a call to another CICS program failing. |
| AII5 | The IIOP Request Receiver stub program was invoked from the sockets domain. However the TCPIPSERVICE defined in RDO did not specify a PROTOCOL of IIOP. |
| AIIA | An error occurred in the IIOP Request Processor which prevented it from sending a reply to the Request Receiver. |
| AIID | The IIOP Request Processor attempted to use a CorbaServer that has been disabled or failed to initialize. |
| AIIP | An EJB was running in an OTS transaction and the timeout for this transaction was exceeded. |
| AIIT | The IIOP Request Processor timed out waiting for a request from a Request Receiver. It received a timed out notification from the RZ domain in response to a listen on the RequestStream of which it is the target. |
| AJAA | The CREA/CREC transaction could not allocate the shared memory it required. The transaction will free all allocated memory and issue this abend. |
| AJAB | The CREA/CREC transaction could not free the shared memory it allocated. |
| AJAC | The CREA/CREC transaction browses the installed REQUESTMODELs. An attempt to start or continue the browse of the REQUESTMODELs failed with an unexpected return code. |
| AJAD | The CREA/CREC transaction received an unexpected return code from an EXEC CICS call and could not continue. |
| AJAE | The CREA/CREC transaction used the EXEC CICS SEND MAP call to display a BMS map. This call returned an expected return code. |
| AJAF | The CREA/CREC transaction used the EXEC CICS RECEIVE MAP call to receive data from a BMS map. This call returned an expected return code. |
| AJAG | The CREA/CREC transaction must be invoked using the transaction ID of 'CREA' or 'CREC'. You are not able to use another transaction ID to invoke DFHADDRM (the program invoked for the CREA/CREC transaction). |
| ASJC | The CICS_HOME directory is inaccessible, does not exist, or contains a version of CICS Java support which is not the same as this release of CICS. |
| ASJD | An attempt to load a DLL by SJ Domain has failed. |
| ASJE | An attempt to locate the Wrapper class has failed. |
| ASJF | An attempt to change the HFS working directory has failed. |
| ASJG | An attempt by SJ domain to fetch the user-replaceable module DFHJVMAT has failed. |
| ASJJ | The JAVA_HOME directory is inaccessible, does not exist, or contains a JVM which does not match the Java version requirements for this release of CICS. |
| ASJK | An attempt was made to attach transaction CJGC, but the transaction was not attached internally by CICS. |
| ASJL | An attempt was made to attach a transaction specifying DFHSJGC as the program to be given control, but the transaction id was not CJGC. |
| ASJM | An attempt was made to attach transaction CJPI, but the transaction was not attached internally by CICS. The CICS system transaction CJPI provides support for initializing new JVMs.It can only be attached internally by CICS. |
| ASJN | An attempt was made to attach a transaction specifying DFHSJPI as the program to be given control, but the transaction id was not CJPI. DFHSJPI is for use by CICS system transaction CJPI, which provides support for initializing new JVMs. |
| ASJR | An attempt was made to start a JVM in resettable mode by specifying [-]Xresettable=YES or REUSE=RESET. |
| ASJ1 | CICS attempted to initialize the Java environment for a task by issuing a JNI_CreateJavaVM call to the Java Native Interface. The call was not successful. |
| ASJ3 | The CICS JVM interface invoked the JVM to find the main method of the CICS Wrapper class used to set up the operating environment before executing the user Java class. The JVM failed to find the main method of the CICS Wrapper class. |
| ASJ4 | The SJ domain failed to build the argument list required to invoke the CICS Wrapper class used to set up the operating environment before executing the user Java class. This is possibly due to lack of free storage. |
| ASJ5 | The CICS JVM interface invoked the CICS Wrapper class used to set up the operating environment before executing the user Java class. The Wrapper returned an exception. |
| ASJ6 | The SJ domain issued a call to the kernel to ensure that CICS's ESTAE is the current ESTAE. This is required before calling CICS services from a native C environment which is running with Language Environment's ESTAE in effect. The call failed. |
| ASJ8 | The SJ domain issued a call to the kernel to ensure that CICS's ESTAE is not the current ESTAE. This is required before calling the JVM as Language Environment's ESTAE is required to be in effect inside the JVM. The call failed. |
| ASRK | The AP domain recovery stub, DFHSR1, has been invoked to deal with a program check, operating system abend, or another error within a transaction environment. However, DFHSR1 has been unable to call the system recovery program, DFHSRP, because register 12, which should be pointing to the task control area (TCA), is null. This indicates that the caller of DFHSR1, has not set the address of the TCA.. |
Last updated: Saturday, 15 June 2019