1 Oracle Access Manager for IMS TM Messages

This chapter describes the messages issued by Oracle Access Manager for IMS TM while running under z/OS.

Oracle Access Manager for IMS TM messages begin with the prefix "AMI-"

The following messages are described in this chapter:

Messages AMI-0001 to AMI-0055
Messages AMI-0107 to AMI-0197

1.1 Messages AMI-0001 to AMI-0055

Messages AMI-0001 to AMI-0055 are issued in American English only. They cannot be translated.

AMI-0001 THE RTT FOR THIS REGION AND SUBSYSTEM IS NOT AN AMI RTT: Cause: During Oracle Access Manager for IMS TM initialization processing, the RTT loaded into the region (specified in the SSM entry for the subsystem) was not generated with AMIRT and other macros, or has been damaged.; Action: Initialization processing for the region fails. If the failure occurs in the control region, then the subsystem is placed in a stopped state. When the RTT is replaced or repaired, the region can retry initialization. If the subsystem was stopped, then it can be restarted with the START SUBSYS command.

AMI-0002 AMI/RTT VERSIONS INCOMPATIBLE (RTT=version.version AT date_time, AMI=version.version): Cause: During Oracle Access Manager for IMS TM initialization processing, the RTT loaded into the region (specified in the SSM entry for the subsystem) contained an Oracle Access Manager for IMS TM version or release number higher than that of the Oracle Access Manager for IMS TM code.; Action: Initialization processing for the region fails. If the failure occurs in the control region, then the subsystem is placed in a stopped state. When the RTT is replaced or repaired, the region can retry initialization. If the subsystem was stopped, then it can be restarted with the START SUBSYS command.

AMI-0003 NO AMI RTT HAS BEEN SUPPLIED FOR THE CONTROL REGION: Cause: During Oracle Access Manager for IMS TM initialization processing for the control region, no RTT name had been specified in the SSM entry for the subsystem or the specified RTT could not be loaded.; Action: Initialization processing for the subsystem fails. If the SSM entry does not specify an RTT name, then one must be added. If a name is specified, then ensure the name is correct and that the load module is located in an authorized library that is part of the DFSESL DD statement concatenation.

AMI-0004 UNABLE TO ALLOCATE AMI GLOBAL STRUCTURE (number BYTES): Cause: During Oracle Access Manager for IMS TM initialization processing for the control region, an attempt to allocate the specified amount of memory in the z/OS extended common storage area (ECSA) failed.; Action: Initialization processing for the subsystem fails. The indicated amount of ECSA must be available in order for Oracle Access Manager for IMS TM to initialize. If ECSA can be made available, then the subsystem can be restarted with the START SUBSYS command.

AMI-0005 DEPENDENT REGION UNABLE TO LOCATE AMI GLOBAL STRUCTURE: Cause: During Oracle Access Manager for IMS TM initialization processing for a dependent region, the Oracle Access Manager for IMS TM global data area could not be located.; Action: Initialization processing for the region fails. You can report this error to Oracle Support Services for additional assistance.

AMI-0006 UNABLE TO ALLOCATE AMI LOCAL STRUCTURE (number BYTES): Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to allocate the specified amount of memory in the extended private area of the region failed.; Action: Initialization processing for the region fails. If the error occurs in the control region, then subsystem initialization fails. Refer to the Oracle Database System Administration Guide for IBM z/OS (OS/390) for a discussion of region memory requirements.

AMI-0007 AMI MESSAGE FACILITY INITIALIZATION FAILED: Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to initialize message localization facilities for the product failed. This message normally is preceded by one or more instances of message AMI-0010.; Action: Initialization processing for the region fails. If the error occurs in the control region, then the subsystem initialization fails. Ensure the required message modules are installed in an authorized library that is part of the region DFSESL DD statement concatenation.

AMI-0008 (AMI MESSAGE FETCH FAILURE FOR MSGNO msgid): Cause: An attempt to fetch the indicated Oracle Access Manager for IMS TM message has failed.; Action: You can report this message to Oracle Support Services for additional assistance. The original message can be looked up in this section by its number. If the message contains fill in items, however, then they cannot be determined.

AMI-0009 UNABLE TO ALLOCATE GVV STRUCTURE (number BYTES): Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to allocate the specified amount of memory in the extended private area of the region failed.; Action: Initialization processing for the region fails. If the error occurs in the control region, then the subsystem initialization fails. Refer to the Oracle Database System Administration Guide for IBM z/OS (OS/390) for a discussion of region memory requirements.

AMI-0010 AMI MESSAGE INITIALIZATION FOR LANGUAGE lang_id FAILED WITH ERROR number: Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to initialize message localization facilities for the indicated language string failed.; Action: Initialization retries message initialization using other language strings, if available. If all such attempts fail, then message AMI-0007 is issued and initialization of the region fails. Ensure the required message module has been placed in an authorized library that is part of the DFSESL DD statement concatenation for the region, and that the NLS_LANG environment variable has not been specified incorrectly in an AMIENV macro in the region's RTT.

AMI-0011 AMI LANGUAGE INITIALIZATION FOR LANGUAGE lang_id UNSUCCESSFUL: Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to initialize message localization facilities for the indicated language string failed.; Action: Initialization retries message initialization using other language strings if available. If all such attempts fail, then message AMI-0007 is issued and initialization of the region fails. Ensure the required message module has been placed in an authorized library that is part of the DFSESL DD statement concatenation for the region, and that the NLS_LANG environment variable has not been specified incorrectly in an AMIENV macro in the region's RTT.

AMI-0012 UNABLE TO ALLOCATE MEMORY FOR MESSAGE/MESSAGE PROCESSING: Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to allocate virtual memory in the extended private area of the region failed.; Action: Initialization processing for the region fails. If the error occurs in the control region, then the subsystem initialization fails. Refer to the Oracle Database System Administration Guide for IBM z/OS (OS/390) for a discussion of region memory requirements.

AMI-0013 UNABLE TO LOCATE AMI LOCAL DATA AREA: Cause: During Oracle Access Manager for IMS TM processing for a region, an attempt to locate a required data structure in the region failed.; Action: Application request processing, if any, fails with a U3044 abend. You can report this message to Oracle Support Services for additional assistance.

AMI-0014 UNABLE TO SET AMI GLOBAL STRUCTURE POINTER IN SSCT: Cause: During Oracle Access Manager for IMS TM initialization processing for the control region, an attempt to dynamically add a z/OS subsystem entry for the Oracle Access Manager for IMS TM has failed.; Action: Initialization processing for the subsystem fails. You can report this message to Oracle Support Services for additional assistance. A possible workaround for this problem is to add the subsystem entry to z/OS using the formal mechanism and re-IPL z/OS.

AMI-0015 ssn IMS MESSAGE SERVICE ROUTINE RETURNED ERROR CODE number: Cause: An attempt to issue an Oracle Access Manager for IMS TM message through the IMS message service routine has returned the indicated error.; Action: This message and the original message are displayed at the z/OS system console. You can report this to Oracle Support Services for additional assistance.

AMI-0016 LOADED CONTROL REGION RTT name AT ADDRESS address: Cause: During Oracle Access Manager for IMS TM initialization processing for the control region, Oracle Access Manager for IMS TM has loaded the RTT because IMS failed to do so.; Action: Processing continues; no action is required. This message is an expected occurrence in IMS TM release 4.1.

AMI-0050 AMI ANCHOR BLOCK NOT FOUND - ESMT ERROR: Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an Oracle Access Manager for IMS TM data structure was not found as expected.; Action: Initialization processing for the region fails. This data area is allocated by IMS through controls in the ESMT module ORAESMT. Ensure you are using the correct ESMT and it has not been altered.

AMI-0051 AMI UNABLE TO LOCATE IMS SCD: Cause: During Oracle Access Manager for IMS TM initialization processing for a region, the IMS SCD data area could not be located.; Action: Initialization processing for the region fails. Ensure the version and release level of your IMS TM are supported by the Oracle Access Manager for IMS TM release. If so, then you can report this message to Oracle Support Services for additional assistance.

AMI-0052 AMI DOES NOT SUPPORT THIS VERSION OF IMS: Cause: During Oracle Access Manager for IMS TM initialization processing for a region, the IMS SCD data area indicated an IMS TM version and release not supported by this release of Oracle Access Manager for IMS TM.; Action: Initialization processing for the region fails. Ensure the version and release level of your IMS TM are supported by the Oracle Access Manager for IMS TM release. If so, then you can report this message to Oracle Support Services for additional assistance.

AMI-0053 AMI UNABLE TO ALLOCATE SECONDARY STACK: Cause: During Oracle Access Manager for IMS TM deferred connection processing for a region, a request for region virtual storage could not be satisfied.; Action: Connection processing for the region fails. Refer to the Oracle Database System Administration Guide for IBM z/OS (OS/390) for a discussion of region memory requirements.

AMI-0054 AMI UNABLE TO ALLOCATE REQUIRED REGION MEMORY: Cause: During Oracle Access Manager for IMS TM deferred initialization processing for a region, a request for region virtual storage could not be satisfied.; Action: Initialization processing for the region fails. Refer to the Oracle Database System Administration Guide for IBM z/OS (OS/390) for a discussion of region memory requirements.

AMI-0055 AMILS UNABLE TO LOCATE IMS ECP: Cause: The Oracle Access Manager for IMS TM linking stub, AMILS, issues this message when the IMS ECP data area associated with the task cannot be found.; Action: Ensure the transaction is running in a valid IMSMPP, IFP, or BMP environment.

1.2 Messages AMI-0107 to AMI-0197

AMI-0107 ROLLBACK NON-EXISTING TRANSACTION (xxxx) IGNORED: Cause: During Oracle Access Manager for IMS TM resolve in-doubt processing, where IMS requested a rollback of the transaction, the transaction was not found in the Oracle system. This is a normal message after a certain type of application failure.; Action: None. Processing continues.

AMI-0108 INITIALIZATION SUCCESSFUL WITH RTT ASSEMBLED AT date_time: Cause: Oracle Access Manager for IMS TM initialization processing for the region has completed successfully. The RTT in effect for the region was assembled on the indicated date. This is the RTT specified in the region SSM entry for the subsystem, if any; otherwise it is the RTT loaded by the control region.; Action: Processing continues; this message is informational. Oracle Access Manager for IMS TM initialization consists primarily of allocation and setup of internal data areas. It does not include making a connection to the target Oracle database server, which might follow immediately or be deferred until an application request is issued.

AMI-0109 UNABLE TO LOCATE AMI GLOBAL DATA AREA: Cause: On entry to one of the Oracle Access Manager for IMS TM ESAF exit routines, the global data area for Oracle Access Manager for IMS TM was not found.; Action: The exit routine returns error code 32 (decimal) to IMS; the effect depends on which exit encountered the problem. If an application request is involved, then the program ends with user abend U3044. You can report this message to Oracle Support Services for additional assistance.

AMI-0110 CONNECT TO ORACLE FAILED WITH ERROR ORA-number: Cause: During Oracle Access Manager for IMS TM connection processing, the attempt to connect to the target Oracle database server failed with the indicated error.; Action: ESAF identify processing fails for the region; if this is the control region or a subsequent access of the Oracle database server from the control region fails, then the subsystem is placed in the stopped state. It can be restarted with the START SUBSYS command after the cause of the error is corrected.

AMI-0111 ORACLE VERSION QUERY FAILED WITH ERROR ORA-number: Cause: During initial connection (ESAF identify) or following an application abend, a test inquiry sent to the Oracle database server failed with the indicated error.; Action: In the identify case, identify processing ends with an error and the subsystem is placed in a logical stopped state. In the latter case, IMS assumes that the target Oracle database server is unavailable and stops the subsystem in the region in question. This is a normal occurrence if communications with the Oracle database server ended unexpectedly by hardware or software failure.

AMI-0112 TARGET ORACLE7 IS AN UNSUPPORTED VERSION (version): Cause: During connection processing, the version number returned by the target Oracle database server was one not supported by Oracle Access Manager for IMS TM.; Action: Connection processing fails and the subsystem is placed in the stopped state. Refer to the Oracle Database System Administration Guide for IBM z/OS (OS/390) for information about supported versions and releases of the Oracle database server.

AMI-0113 SUBSYSTEM ssn CONNECTED TO ORACLE VERSION version: Cause: Oracle Access Manager for IMS TM identify (connection) processing for the indicated subsystem id has completed in the region.; Action: Processing continues; this message is informational.

AMI-0114 UNABLE TO ALLOCATE HSTDEF EXTENSION OF SIZE number: Cause: During Oracle Access Manager for IMS TM identify (connection) processing, a request for the indicated amount of virtual memory failed.; Action: Connection processing ends and IMS ESAF identify ends with an error. The subsystem can be restarted with the IMS START SUBSYS command when more virtual storage is available in the affected region.

AMI-0117 SESSION POOL FULL BEFORE ALL POOLED SESSIONS WERE STARTED: Cause: During connection processing for a dependent region, the maximum number of session pool entries (RTT MAXSESS parameter) was reached before all pooled sessions (those having AMISESS START=YES) could be started.; Action: Processing continues; sessions beyond the MAXSESS number are not pooled. You might want to increase MAXSESS to allow for all START=YES sessions or reduce the number of START=YES sessions defined.

AMI-0118 RESOLVE IN-DOUBT PROCESSING COMPLETED: Cause: Following Oracle Access Manager for IMS TM identify (connection) processing in the control region or following an application abend, IMS resolve in-doubt processing has completed normally.; Action: Processing continues; this message is informational.

AMI-0119 RECOVERY SESSION CREATION FAILED WITH ERROR ORA-number: Cause: During connection (identify) processing in the control region, the attempt to create an Oracle session for recovery (using the RTT RECOID user id) failed with the indicated error.; Action: Connection processing fails and the subsystem is placed in the stopped state. Ensure RECOID is correctly specified in the RTT AMIRT macro and a suitable AMISESS entry is provided for that user id.

AMI-0120 UNABLE TO FIND RTT SESSION ENTRY FOR RECOVERY USERID: Cause: During connection (identify) processing in the control region, no RTT AMISESS entry could be found for the recovery user id (AMIRT RECOID) and no default session entry is provided.; Action: Connection processing fails and the subsystem is placed in the stopped state. Ensure RECOID is correctly specified in the RTT AMIRT macro and a suitable AMISESS entry is provided for that user id.

AMI-0121 RETRIEVE PENDING TRANSACTION COUNT FAILED WITH ERROR ORA-number: Cause: IMS has been cold-started and an attempt by the Oracle database server to obtain information about possible inconsistencies has failed with the indicated error.; Action: Resolve in-doubt processing fails and the subsystem is placed in the stopped state. The cause of the error must be corrected to restart the subsystem.

AMI-0122 IMS COLD-STARTED AND THERE ARE number PENDING TRANSACTIONS IN ORACLE: Cause: IMS has been cold-started and the target Oracle database server has the indicated number of in-doubt transaction entries. These create an inconsistency between IMS and the Oracle database server.; Action: Resolve in-doubt processing fails and the subsystem is placed in the stopped state. Manual (forced) commit or rollback of the Oracle transactions must be performed by an Oracle database administrator (DBA).

AMI-0123 UNKNOWN RECOVERY ACTION string FOR RECOVERY TOKEN token, IGNORED: Cause: During resolve in-doubt processing, IMS has called the RID exit for Oracle Access Manager for IMS TM with an action code other than CO (commit) or AB (abort).; Action: Resolve in-doubt processing fails. You can report this message to Oracle Support Services for additional assistance.

AMI-0124 RECOVERY action FOR TOKEN token FAILED WITH ERROR ORA-number: Cause: During resolve in-doubt processing, an attempt to take the indicated action (COMMIT or ROLLBACK) in the Oracle database server has failed with the indicated error.; Action: Resolve in-doubt processing fails. If the error is ORA-2058, indicating an unknown Oracle transaction id, then an inconsistency might exist between IMS and the Oracle database server.

AMI-0125 RECOVERY COMMITS=number, ABORTS=number, DEFERS=number: Cause: Resolve in-doubt processing has completed. The indicated number of transactions have been committed, ended (rolled back), or deferred for later recovery action.; Action: Processing continues; this message is informational.

AMI-0126 RETRIEVE PENDING TRANSACTION COUNT FAILED WITH ERROR ORA-number: Cause: Following resolve in-doubt processing, an attempt to check for irrecoverable Oracle transactions (which constitute an inconsistency between IMS and the Oracle database server) has failed with the indicated error.; Action: Resolve in-doubt processing fails. Manual recovery of in-doubt Oracle transactions might be required.

AMI-0127 ORACLE STILL HAS number PENDING TRANSACTIONS AFTER RECOVERY: Cause: IMS has signalled recovery has ended, but the Oracle database server still has in-doubt transactions associated with this IMS.; Action: Resolve in-doubt processing fails. Manual recovery of in-doubt Oracle transactions might be required.

AMI-0128 CLOSE OF RECOVERY CURSOR GOT ERROR ORA-number: Cause: The call to close a cursor using resolve in-doubt processing received the indicated error.; Action: Processing continues. Unless this message is associated with an obvious cause (such as an outage of the target database or Oracle Net), you can report this message to Oracle Support Services for additional assistance.

AMI-0129 ESAF CALL OCCURRED IN ILLOGICAL STATE OR UNEXPECTED SEQUENCE: Cause: A call to one of the Oracle Access Manager for IMS TM ESAF exits has occurred at an unexpected time.; Action: The exit routine returns error code 32 (decimal) to IMS; the effect depends on which exit encountered the problem. If an application request is involved, then the program ends with user abend U3044. You can report this message to Oracle Support Services for additional assistance.

AMI-0130 ORACLE DISCONNECT FAILED WITH ERROR ORA-number: Cause: Disconnect (end identify) processing encountered an error on the call to disconnect from the Oracle database server.; Action: Processing continues. Unless this message is associated with an obvious cause (such as an outage of the target database or Oracle Net), you can report this message to Oracle Support Services for additional assistance.

AMI-0131 action ACTION FOR RECOVERY TOKEN token SUCCESSFUL: Cause: During resolve in-doubt processing, the transaction associated with the indicated IMS recovery token was successfully forced through COMMIT or ROLLBACK processing in the Oracle database server.; Action: Processing continues; this message is informational.

AMI-0132 action ACTION FOR RECOVERY TOKEN token FAILED DUE TO INCONSISTENCY: Cause: During resolve in-doubt processing, an attempt to force a COMMIT or ROLLBACK of the transaction associated with the indicated IMS recovery token has failed because the transaction is not known to the Oracle database server. This indicates that an inconsistency exists between IMS and the Oracle database server.; Action: Resolve in-doubt processing fails. Manual commit or end of the transaction might be required in other resource managers.

AMI-0133 action ACTION FOR RECOVERY TOKEN token DEFERRED DUE TO ERROR: Cause: During resolve in-doubt processing, an attempt to force a COMMIT or ROLLBACK of the transaction associated with the indicated IMS recovery token has failed. A return code is passed to IMS indicating recovery for this transaction is to be deferred.; Action: The specific error should be displayed in another message; investigate the cause of the error.

AMI-0134 RECOVERY TOKEN CHANGED DURING MULTIPLE-MODE TRANSACTION: Cause: In ESAF signon processing for the second or later input message for a multiple-mode transaction, IMS indicated a change of recovery token.; Action: Oracle Access Manager for IMS TM causes the application to end with abend U3047.

AMI-0135 ILLEGAL ATTEMPT TO CHANGE USERID IN MULTIPLE-MODE TRANSACTION: Cause: In processing a multiple-mode transaction whose RTT AMITRANS macro specifies AUTH=IMSID, a new input message has a different MVS/IMS user id than the one under which the transaction was started.; Action: Oracle Access Manager for IMS TM causes the application to end with abend U3047.

AMI-0136 ESAF SIGNON CALL IN IMPROPER STATE number: Cause: IMS invoked the signon ESAF processing exit for Oracle Access Manager for IMS TM at an unexpected time.; Action: This indicates an internal IMS or Oracle Access Manager for IMS TM problem and you can report this message to Oracle Support Services for additional assistance.

AMI-0137 ESAF CREATE THREAD CALLED IN IMPROPER STATE number: Cause: IMS invoked the create thread ESAF processing exit for Oracle Access Manager for IMS TM at an unexpected time.; Action: This indicates an internal IMS or Oracle Access Manager for IMS TM problem and you can report this message to Oracle Support Services for additional assistance.

AMI-0139 UNABLE TO FIND RTT TRANSACTION ENTRY FOR PSB psb_name: Cause: At thread creation time, Oracle Access Manager for IMS TM was unable to locate an RTT transaction entry (AMITRANS macro) for the indicated PSB name and no default transaction entry is provided.; Action: Thread creation fails and the application is ended by IMS with abend U3047. To run this application, the region RTT must be changed to include an AMITRANS entry for the PSB name or a default AMITRANS (with a PSB name of *). Refer to the Oracle Database System Administration Guide for IBM z/OS for more details.

AMI-0140 UNABLE TO FIND RTT SESSION ENTRY FOR USERID id, PSB psb_name: Cause: At transaction start time, Oracle Access Manager for IMS TM was unable to locate an RTT session entry (AMISESS macro) for the indicated Oracle user id, and no default session entry is provided. The applicable PSB name, whose RTT AMITRANS entry determined the user id, is also indicated.; Action: Transaction start fails, and the application is ended by IMS with abend U3047. To run this application with the indicated user id, the region RTT must be changed to include an AMISESS entry for the user id or a default AMISESS (with a user id of *). Refer to the Oracle Database System Administration Guide for IBM z/OS for more details.

AMI-0143 DELETE SESSION sess_id FAILED (number); MAY STILL BE ACTIVE IN ORACLE: Cause: An Oracle Access Manager for IMS TM request to delete an Oracle session received an error.; Action: The session is logically discarded by Oracle Access Manager for IMS TM. If this message occurs with a failure of the Oracle connection, then it is normal and can be ignored. Otherwise, investigate the specific error to determine why the session was not deleted. Repeated occurrences of this message over time might signal a resource problem in the target Oracle instance.

AMI-0145 UNABLE TO MAKE ORACLE SESSION FOR USERID id (function ERROR number): Cause: An attempt to create or clone an Oracle session for the indicated Oracle user id failed; the internal interface routine and Oracle error code are shown in parentheses.; Action: If this occurs in the control region (with the recovery user id), then Oracle Access Manager for IMS TM identify processing ends; the problem indicated by the error code must be corrected and the Oracle Access Manager for IMS TM instance restarted. In a dependent region this message might indicate a problem with a specific Oracle user id (such as incorrect authentication information in the RTT session descriptor) or a more general problem that affects all sessions; accompanying messages tell you the problem. In the former case, only transactions running with the specific user id are affected and behavior depends on the region error option (REO) in effect for the transaction. In the latter case, IMS attempts to restart the Oracle Access Manager for IMS TM instance in the region before placing the instance in a stopped state.

AMI-0149 UNEXPECTED RESPONSE CODE (number) TO ORACLE COMMIT: Cause: During the last phase of two-phase commit processing for a transaction, the COMMIT command sent to the Oracle database server received an unexpected response code as shown.; Action: The transaction ends with abend U3044. This message indicates an Oracle Access Manager for IMS TM or the Oracle database server problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0150 UNEXPECTED RESPONSE (number) TO ORACLE COMMIT PREPARE: Cause: During the first phase of two-phase commit processing for a transaction, the commit prepare command sent to the Oracle database server received an unexpected response code as shown.; Action: The transaction ends with abend U3044. This message indicates an Oracle Access Manager for IMS TM or an Oracle database server problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0151 ESAF COMMIT PREPARE CALLED IN IMPROPER STATE number: Cause: IMS invoked the commit prepare ESAF processing exit for Oracle Access Manager for IMS TM at an unexpected time.; Action: The application ends with abend U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0157 ESAF PREPARE CALLED WITH UNEXPECTED RECOVERY TOKEN: Cause: The ESAF commit prepare exit was invoked with an IMS recovery token different from the one supplied when the transaction started.; Action: The transaction ends with abend U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0159 SETUP OF RECOVERY CURSOR(S) FAILED WITH ERROR ORA-number: Cause: During resolve in-doubt processing, parse, bind, or define processing for recovery SQL received the indicated error.; Action: Resolve in-doubt processing fails. Unless the error is associated with an obvious cause, such as an outage of the target database or Oracle Net, you can report this message to Oracle Support Services for additional assistance.

AMI-0160 ESAF START SUBSYSTEM REQUEST FAILED WITH RC number (DECIMAL): Cause: An attempt to start Oracle Access Manager for IMS TM in response to an application request has failed. The IMS ESAF subsystem startup service routine returned the indicated error code.; Action: Deferred connect processing fails. Unless the error is associated with an obvious cause, such as an outage of the target database or Oracle Net, you can report this message to Oracle Support Services for additional assistance.

AMI-0162 IDENTIFY FAILED - ORACLE CONNECTION LOST: Cause: During connection (identify) processing, an error was received indicating the connection has been lost.; Action: Connection processing fails. Unless the error is associated with an obvious cause, such as an outage of the target database or Oracle Net, you can report this message to Oracle Support Services for additional assistance.

AMI-0165 IMBEDDED SIGNON ATTEMPTED WITH MODE=SNGL PSB psb_name: Cause: An IMS transaction defined as MODE=SNGL caused a second ESAF signon call within a single transaction. This behavior is limited to MODE=MULTI transactions.; Action: Oracle Access Manager for IMS TM causes the transaction program to end with abend code U3045.

AMI-0169 INCORRECT STATE (number) AT TRANSACTION COMPLETION: Cause: IMS invoked the commit prepare or end thread processing exit for Oracle Access Manager for IMS TM at an unexpected time.; Action: The application ends with abend U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0170 ESAF COMMIT CALLED WITH UNEXPECTED RECOVERY TOKEN: Cause: The ESAF commit prepare or end thread exit was invoked with an IMS recovery token different from the one supplied when the transaction started.; Action: The transaction ends with abend U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0174 INCORRECT STATE (number) AT TRANSACTION ABORT: Cause: IMS invoked the abort continue or end thread processing exit for Oracle Access Manager for IMS TM at an unexpected time.; Action: The application ends with abend U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0175 ESAF ABORT CALLED WITH UNEXPECTED RECOVERY TOKEN: Cause: The ESAF abort continue or end thread exit was invoked with an IMS recovery token different from the one supplied when the transaction started.; Action: The transaction ends with abend U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0178 UNEXPECTED RESPONSE CODE (number) TO ORACLE ABORT: Cause: During ABORT processing for a transaction, the ABORT command sent to the Oracle database server received an unexpected response code as shown.; Action: The transaction ended with abend U3044. This message indicates an Oracle Access Manager for IMS TM or Oracle database server problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0179 ESAF TERMINATE THREAD 'DEALLOCATE' WITH IN-PROGRESS TRANSACTION: Cause: IMS has invoked the ESAF end thread exit with a deallocate request code while a transaction is still in progress.; Action: This message indicates an IMS or Oracle Access Manager for IMS TM logic problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0180 UNKNOWN ESAF TERMINATE THREAD COMMIT OPTION <opt>: Cause: IMS has invoked the ESAF end thread exit with an option code other than COMM, ABRT, or DEAL.; Action: The current transaction, if any, ends with an abend U3044. You can call Oracle Support Services for additional assistance.

AMI-0181 INCORRECT STATE (number) AT TERMINATE IDENTIFY: Cause: IMS invoked the end identify processing exit for Oracle Access Manager for IMS TM at an unexpected time.; Action: The application ends with abend U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0183 AMI REGION TERMINATION COMPLETED NORMALLY: Cause: End identify (disconnect) processing completed normally in the region.; Action: Processing continues; this message is informational.

AMI-0186 RECOVERY ACTION ON TRANSACTION token DEFERRED DUE TO DISCONNECT: Cause: During resolve in-doubt processing, a previous error caused connection to the Oracle database server to be lost.; Action: Processing continues; IMS retains the recovery token for later resolution. This message is normal for each recovery token processed after a disconnect.

AMI-0187 ABORT TRANSACTION FAILED AT TERMINATE IDENTIFY: Cause: An identify end has been called while there is still a transaction in progress, and the attempt to end the transaction in the Oracle database server has failed.; Action: You can report this message to Oracle Support Services for additional assistance.

AMI-0188 FAILED TO ALLOCATE MESSAGE BUFFER OF SIZE number: Cause: Initialize or identify was unable to allocate an Oracle error message buffer of the indicated size.; Action: Initialize or identify processing fails. Refer to the product documentation for a discussion of memory requirements.

AMI-0189 CONTROL REGION DBADDR DIFFERS FROM THIS DR DBADDR; net_type addr_string: Cause: The dependent region RTT contains a database address (DBADDR parameter of the AMIRT macro) or NET specification that differs from that specified in the control region RTT.; Action: Oracle Access Manager for IMS TM initialization for the region ends. The dependent region RTT must be regenerated or a different RTT used.

AMI-0190 function FOR SSN ssn FAILED, SUBSYSTEM UNAVAILABLE UNTIL RESTARTED: Cause: A failure in the indicated Oracle Access Manager for IMS TM function for the indicated subsystem has failed, causing IMS to place the subsystem in a logical stopped state. Details on the failure appeared in prior messages.; Action: Access to the affected target Oracle database server remains unavailable until the problem is corrected and the subsystem restarted using the IMS START SUBSYS command.

AMI-0191 UNABLE TO ALLOCATE SESSION ARRAY OF SIZE number: Cause: During Oracle Access Manager for IMS TM identify processing for the region, a request for session array memory of the indicated size failed.; Action: If this occurs in the control region, then Oracle Access Manager for IMS TM identify processing fails and the Oracle Access Manager for IMS TM instance is placed in a stopped state. Steps must be taken to ensure sufficient virtual memory is available in the region before Oracle Access Manager for IMS TM can be restarted. In a dependent region, Oracle Access Manager for IMS TM might attempt to allocate a smaller session array. If this is not possible or also fails, then identify processing for the region fails.

AMI-0193 TRACE COMMAND HAS SYNTAX ERROR - descr: Cause: A syntax error was found in the TRACE command.; Action: The tracing state is not changed. Change the command and reenter it.

AMI-0192 TRACE COMMAND PROCESSED SUCCESSFULLY: Cause: Trace command was processed successfully.; Action: Processing continues; this is a normal response to the Oracle Access Manager for IMS TM TRACE command.

AMI-0194 INVALID ACCESS MANAGER COMMAND - string: Cause: A command unknown to Oracle Access Manager for IMS TM has been entered through SSR.; Action: Issue the command correctly.

AMI-0195 ORACLE ERROR - INFORMATION FOLLOWS

userid=xxxx, PGM=xxxx, PSB=xxxx,Oracle userid=xxxx, lterm=xxxx, tran name=xxxx, REO option is x, oercid=xxxx, typ=xxx, fatal=xx, flg=xx, oerrcd=xx,opt=xx, par=xx, wflg=xx

Cause: This is an Oracle system error.

Action: Review the error information. You can contact Oracle Support Services for additional assistance. The following is a list of definitions of terms in the message:

userid: The IMS TM user id
PGM: The name of the IMS TM program
PSB: The PSB name
Oracle userid: The Oracle user ID
lterm: The IMS TM transaction name
tran name: The IMS TM transaction name
REO option is: The IMS TM region error option
oercid: The current cursor id (oercid)
typ: The SQL command type (oertyp)
fatal: The error action information (oeropt)
flg: The flags (oerflg)
oerrod: The return code (oerrod)
opt: The user-specified curser options (oeropt)
par: The UPI parameter that generates the error (oerpar)
wflg: The warning flag (oerwflg)

AMI-0197 ORACLE NOT RESPONDING. MANUAL INTERVENTION MIGHT BE REQUIRED.: Cause: Oracle Access Manager for IMS TM has determined that the target Oracle instance is not responding. The instance might have failed. If Oracle Net is being used, then the network connection to the target instance might not be operating normally.; Action: Check the status of the target Oracle instance. If Oracle Net is being used, then ensure it is operating properly and that the underlying network protocol is functioning normally