ATM* - Adabas Transaction Manager Messages

#### Search Results

Search

# ATM* - Adabas Transaction Manager Messages

### Overview of Messages

`ATM000_FF | ATM001_20 | ATM002_20 | ATM003_20 | ATM005_20 | ATM007_20 | ATM010_20 | ATM012_20 | ATM013_20 | ATM014_20 | ATM015_10 | ATM016_20 | ATM017_20 | ATM018_20 | ATM019_20 | ATM020_04 | ATM021_08 | ATM023_04 | ATM024_10 | ATM025_10 | ATM026_10 | ATM027_10 | ATM028_10 | ATM029_10 | ATM030_10 | ATM031_10 | ATM032_10 | ATM033_10 | ATM034_10 | ATM036_08 | ATM037_08 | ATM038_00 | ATM039_04 | ATM040_00 | ATM041_00 | ATM042_10 | ATM043_04 | ATM044_04 | ATM045_04 | ATM046_04 | ATM047_20 | ATM048_08 | ATM049_04 | ATM050_20 | ATM051_20 | ATM052_20 | ATM054_20 | ATM055_20 | ATM057_10 | ATM058_10 | ATM059_10 | ATM060_10 | ATM061_10 | ATM062_10 | ATM063_10 | ATM064_10 | ATM067_10 | ATM068_04 | ATM069_10 | ATM070_10 | ATM071_10 | ATM072_10 | ATM073_10 | ATM074_10 | ATM075_10 | ATM076_10 | ATM077_10 | ATM078_10 | ATM080_08 | ATM081_08 | ATM082_08 | ATM083_08 | ATM084_10 | ATM085_10 | ATM086_10 | ATM087_10 | ATM088_10 | ATM089_10 | ATM090_04 | ATM091_04 | ATM092_10 | ATM095_08 | ATM099_08 | ATM100_08 | ATM101_08 | ATM102_10 | ATM103_08 | ATM104_10 | ATM105_08 | ATM106_04 | ATM110_04 | ATM119_04 | ATM120_04 | ATM121_10 | ATM122_20 | ATM124_04 | ATM125_10 | ATM126_04 | ATM127_04 | ATM128_04 | ATM129_04 | ATM130_20 | ATM131_10 | ATM132_10 | ATM133_10 | ATM134_10 | ATM135_10 | ATM136_10 | ATM137_10 | ATM138_10 | ATM139_10 | ATM140_10 | ATM141_04 | ATM144_08 | ATM160_10 | ATM163_04 | ATM164_04 | ATM167_10 | ATM168_10 | ATM169_10 | ATM171_08 | ATM172_10 | ATM173_08 | ATM174_10 | ATM177_08 | ATM178_08 | ATM179_08 | ATM180_20 | ATM181_08 | ATM182_20 | ATM184_10 | ATM185_04 | ATM186_04 | ATM187_04 | ATM188_04 | ATM189_04 | ATM190_04 | ATM191_04 | ATM192_04`

ATM000_FF | NO TEXT
Explanation | One of the following occurred: an unexpected error an error created intentionally by zap.
Action | If the error was unexpected, contact your Software AG support representative.

ATM001_20 | ADABAS VERSION NOT SUPPORTED BY ATM
Explanation | The Adabas Transaction Manager cannot be used with this version of Adabas.
Action | Use a version of Adabas that ATM supports.

ATM002_20 | ATM DATABASE OP FAILED, RSP/SUBCODE rsp/subcode
Explanation | The ATM recovery database failed to open for the reason indicated.
Action | Correct the cause of the response code and restart the ATM transaction manager.

ATM003_20 | UNABLE TO LOAD module-name
Explanation | The named module could not be loaded.
Action | Ensure that the module is in a library from which it can be loaded dynamically.

ATM005_20 | Error reading TM controls; RSP/SUB: rsp/sub
Explanation | An unexpected response code was encountered during reading of the TM controls from the configuration file.
Action | If the cause of the error is not clear from the description of the response code, report the details to your Software AG support representative.

ATM007_20 | COR GROUP ALREADY HAS MANAGER: manager
Explanation | The ATM manager indicated in the message is already active locally in the local COR group. It is not possible to have more than one ATM transaction manager associated with the same COR group and executing in the same location (that is, under the same Adabas ID table, or Adabas SVC).
Action | Do not attempt to run more than one ATM transaction manager under the same ID table and associated with the same COR group.

ATM010_20 | GENERAL GETMAIN FAILED
Explanation | ATM was unable to acquire enough storage to initialize.
Action | Increase the amount of memory available to the job and restart it.

ATM012_20 | UNABLE TO ACQUIRE STORAGE FOR area-name
Explanation | ATM was unable to acquire enough storage for the area named.
Action | Increase the amount of memory available to the job and restart it.

ATM013_20 | INITIALIZATION ERROR. FUNCTION/RF: function/rf
Explanation | An error occurred during the initialization of an interface to an external transaction coordinator.
Action | Check the documentation for the external transaction coordinator being used to determine the meaning of the return code (value rf). If the cause of the problem is still not apparent, contact your Software AG support representative, noting the values of function and rf.

ATM014_20 | RRMS LOGNAME CHECK FAILED
Explanation | This message relates to the initialization of the ATM interface with RRMS. The ATM node ID has changed since ATM was last used with this RRMS system.
Action | The node ID of the Adabas System Coordinator daemon within which the ATM transaction manager is running as a service must not be changed while there are global transactions in progress. If you have changed the Node ID and are sure that there were no incomplete global transactions, you can override this initialization error using the parameter `TMRESTART=FORCE`.

ATM015_10 | RRMS LOGNAME INCONSISTENCY OVERRIDDEN
Explanation | This message relates to the initialization of the ATM interface with RRMS. The node ID of the Adabas System Coordinator daemon within which the ATM transaction manager is running as a service has changed since ATM was last used with this RRMS system. However, the inconsistency was ignored because of the setting of the parameter `TMRESTART`.
Action | None. This message is for information only.

ATM016_20 | RRMS HAS LOST HARDENED RESTART DATA
Explanation | This message relates to the initialization of the ATM interface with RRMS. Because RRMS has lost some restart data, integrity cannot be guaranteed for incomplete transactions that were under the control of RRMS.
Action | If it is not possible to recover the RRMS restart data, you can use the parameter `TMRESTART` to force the ATM transaction manager to initialize. Details of any incomplete transactions are then transferred to the STJ file and can be examined using the SYSATM application.

ATM017_20 | FAILED TO OPEN ATMLOG. RC/RF:rc/rf
Explanation | The ATM transaction manager was unable to open the ATMLOG1 or ATMLOG2 dataset.
Action | Check the definition of the ATMLOG1/2 datasets. If the cause of the error is not apparent, report the problem to your Software AG support representative, noting the values of rc and rf.

ATM018_20 | Unexpected behavior for node dbid
Explanation | The node (dbid) is expected to be an Adabas System Coordinator daemon within which an ATM transaction manager is running as a service, but its behavior is not consistent with this.
Action | Check the indicated node.

ATM019_20 | RRS IS NOT ACTIVE; ATM WILL WAIT AND RETRY
Explanation | This message relates to the initialization of the ATM interface with RRMS. Initialization cannot complete because the RRS component of RRMS is not available.
Action | Report the problem to your systems programming staff. The ATM transaction manager cannot initialize until RRS is active again.

ATM020_04 | RRS EXITS HAVE BEEN SET
Explanation | If the ATM transaction manager is started with the parameter `TMSYNCMGR=RRMS`, this message is issued when the ATM RRMS interface has been initialized.

ATM021_08 | RRS RESTART FINISHED
Explanation | If the ATM transaction manager is started with the parameter `TMSYNCMGR=RRMS`, this message is issued when ATM transaction manager finishes telling RRS how to handle any transactions that previously failed to complete.

ATM023_04 | ISN: isn
Explanation | This message is preceded by message ATM025 or ATM033. It indicates the ISN associated with the error.
Action | Refer to the explanation of the previously issued message.

ATM024_10 | ERROR DURING DB RESTART; ID/ERR: dbid/error-code
Explanation | The error (error-code) occurred during restart processing for the database (dbid).
Action | Refer to the descriptions of the possible error codes. If the cause of the error is not clear, report the details to your Software AG support representative, noting the values of the variables.

ATM025_10 | ERROR IN ATM RESTART; ID/RSP/SUB/CMD: dbid/rsp/sub/cmd
Explanation | An unexpected response code (rsp) was encountered during restart processing for the ATM transaction manager (dbid). The response code, subcode (sub), and command code (cmd) are provided. An ATM023 message may follow, providing an associated ISN.
Action | If the cause of the error is not clear from the description of the response code, report the details to your Software AG support representative, noting the values of the variables.

ATM026_10 | ERROR DURING ATM RESTART; ID/ERR: dbid/error-code
Explanation | The error (error-code) occurred during restart processing for the partner ATM transaction manager (dbid).
Action | Refer to the descriptions of the possible error codes. If the cause of the error is not clear, report the details to your Software AG support representative, noting the values for the variables.

ATM027_10 | ATM RESTART. MAX PARTNERS EXCEEDED. USER userid
Explanation | The maximum number of partner ATM transaction managers indicated by the parameter `TMNODES` is not sufficient to perform restart processing for incomplete transactions. The error occurred while ATM was attempting restart processing for the user whose Client ID is userid. This message is followed by an ATM087 message providing the user’s 28-byte Communication ID. The transaction manager continues to execute, but cannot complete restart processing for transactions affected by the error.
Action | Set the `TMNODES` parameter and restart the ATM transaction manager.

ATM028_10 | DB RESTART. MAX TARGETS EXCEEDED. USER userid
Explanation | ATM is unable to perform restart processing for an incomplete transaction because the number of databases involved in the transaction exceeds the maximum possible. The error was detected while ATM was attempting restart processing for the user whose Client ID is userid. This message is followed by an ATM087 message providing the user’s 28-byte Communication ID. The transaction manager continues to execute, but cannot complete restart processing for transactions affected by the error.
Action | Contact your Software AG support representative.

ATM029_10 | PARTNER/DB RESTART ABORTED; ID/ERR: dbid/error-code
Explanation | The error indicated occurred during restart processing associated with the database or ATM identified by dbid. The transaction manager continues to execute, but cannot complete restart processing for transactions affected by this error.
Action | Refer to the descriptions of the possible error codes. If the cause of the error is not apparent, report the details to your Software AG support representative, noting the error code.

ATM030_10 | ERROR DURING TRAN RESTART; ID/ERR//COMMID: dbid/error-code
Explanation | The error indicated occurred during restart processing for an incomplete transaction. The database associated with the error is identified by dbid. The message is followed by an ATM032 message giving the Client ID of the transaction’s owner, and an ATM087 message giving the user’s 28-byte Communication ID.
Action | Refer to the descriptions of the possible error codes. If the cause of the error is not apparent, report the details to your Software AG support representative, noting the error code.

ATM031_10 | ERROR DURING BRANCH RESYNC; ID/ERR//COMMID: dbid/error-code
Explanation | The error indicated occurred while ATM was attempting to synchronize restart for an incomplete transaction branch with a partner ATM transaction manager. The partner transaction manager associated with the error is identified by dbid. The message will be followed by an ATM032 message giving the Client ID of the transaction’s owner, and an ATM087 message giving the user’s 28-byte Communication ID.
Action | Refer to the descriptions of the possible error codes. If the cause of the error is not apparent, report the details to your Software AG support representative, noting the error code.

ATM032_10 | RESTART ERROR FOR USER userid
Explanation | This message refers to a previous error message and gives the Client ID of the user associated with the previous error.
Action | Refer to details for the preceding message.

ATM033_10 | ERROR DURING DB RESTART; ID/RSP/SUB/CMD: dbid/rsp/sub/cmd
Explanation | An unexpected response code was encountered during restart processing for database dbid. The response code, subcode, and command code are provided. An ATM023 message may follow, providing an associated ISN.
Action | If the cause of the error is not clear from the description of the response code, report the details to your Software AG support representative, noting the value of the variables.

ATM034_10 | Register failure for xxxxx: DB/rsp/sub/RC: dbid/rsp/sub/cmd
Explanation | An unexpected condition was encountered when the transaction manager attempted to register an event with the SYSCO daemon. The type of event is identified by xxxxx.
Action | Please contact your Software AG support representative, noting the values of the variables given in the message.

ATM036_08 | Transaction Manager initialization started
Explanation | This message appears during the initialization of an ATM transaction manager, and indicates that initialization of the transaction manager’s environment has started.
Action | None. This message is for information only.

ATM037_08 | COR GROUP/DAEMON: group/jobname
Explanation | This message is issued by an ATM transaction manager at the end of its initialization process. It identifies the Adabas System Coordinator group that the transaction manager is associated with, and the job name of it’s COR daemon.
Action | None. This message is for information only.

ATM038_00 | FURTHER RESTART ERROR MESSAGES WILL BE SUPPRESSED
Explanation | This message is issued during ATM restart when the transaction manager has issued 100 error messages. It indicates that any further errors encountered during the restart process will be suppressed.
Action | None. This message is for information only.

ATM039_04 | TRANSACTION RESTART NOT POSSIBLE FOR DB dbid
Explanation | This message is preceded by message ATM025. It indicates that serious errors prevent the transaction manager from restarting affected transactions.
Action | Correct the error reported in the ATM025 message; then restart the database indicated in the message.

ATM040_00 | TRANSACTION RESTART DEFERRED FOR INACTIVE DB dbid
Explanation | This message might be issued during an transaction manager's restart processing. Incomplete transactions exist that involve the database indicated. It is not possible for the transaction manager to resolve them because the database is not available.
Action | This message is for information only. Restart processing for such transactions occurs when the indicated database is restarted.

ATM041_00 | TRANSACTION RESTART DEFERRED FOR INACTIVE NODE dbid
Explanation | This message might be issued during an transaction manager's restart processing. Incomplete transactions exist that involve the partner transaction manager indicated by dbid. It is not possible for the TM to resolve them because the partner TM is not active.
Action | This message is for information only. Restart processing for such transactions occurs when the indicated TM is restarted.

ATM042_10 | NUMBER OF WARNING MESSAGES SUPPRESSED: count
Explanation | This message is issued by an ATM transaction manager at the end of restart processing if the number of error messages during restart processing exceeded 100.
Action | This message is for information only.

ATM043_04 | TRANSACTIONS COMPLETED DURING RESTART: count
Explanation | This message is issued by an ATM transaction manager at the end of restart processing. It indicates the number of previously incomplete transactions that were completed (by completing the commit process) during ATM restart processing.
Action | This message is for information only.

ATM044_04 | TRANSACTIONS BACKED OUT DURING RESTART: count
Explanation | This message is issued by an ATM transaction manager at the end of restart processing. It indicates the number of previously incomplete transactions that were backed out during ATM restart processing.
Action | This message is for information only.

ATM045_04 | TRANS/BRANCHES PENDING AFTER RESTART: count
Explanation | This message is issued by an ATM transaction manager at the end of restart processing. It indicates the number of incomplete transactions or transaction branches that could not be completed or backed out during ATM restart processing, and so remain incomplete. These transactions remain incomplete until they can be completed or fully backed out. Note: This message is issued before the transaction manager attempts to resynchronize incomplete transactions that are controlled by the CICS syncpoint manager or by RRS.
Action | This message is for information only.

ATM046_04 | TRANS/BRANCHES TRANSFERRED TO STJ: count
Explanation | This message is issued by an ATM transaction manager at the end of restart processing. It indicates the number of incomplete transactions or transaction branches that could not be completed or backed out during the daemon recovery restart processing, and that were removed and recorded in the suspect transaction journal file in the transaction manager's recovery file. The number indicated should be zero unless the `TMRESTART` parameter indicates a forced restart.
Action | This message is for information only.

ATM047_20 | ATM INITIALIZATION FAILED, error description
Explanation | A serious error prevented the transaction manager from initializing. Where possible an error description is provided to identify the cause of the error, otherwise "RC/RF" error codes are displayed.
Action | If the reason for the failure is not clear please contact your Software AG support representative.

ATM048_08 | INITIALIZED, Vvers, SESSION sess
Explanation | This message marks the successful completion of an ATM transaction manager's initialization processing. The version, release, and maintenance level of ATM are displayed, followed by the session number (sess) for this execution of the transaction manager.
Action | This message is for information only.

ATM049_04 | ERRORS READING RECOVERY RECORDS: count
Explanation | This message appears at the end of the transaction manager's initialization processing if any errors were encountered reading recovery records.
Action | The message is for information only. For information about the errors encountered, refer to the error messages that precede this message.

ATM050_20 | ‘SIGN-OFF’ FAILED, RESPONSE CODE rsp
Explanation | This message can appear during the closedown process of a nucleus that was running with `DTP=RM`. It indicates that the nucleus called the local ATM transaction manager to notify it of the closedown, but the command failed with response code rsp.
Action | Nucleus termination will continue. Any incomplete global transactions will be resynchronized when the nucleus next communicates with the ATM transaction manager.

ATM051_20 | ‘SIGN-OFF’ FAILED, ERROR CODE error-code
Explanation | This message can appear during the closedown process of a nucleus that was running with `DTP=RM`. It indicates that the nucleus called the local ATM transaction manager to notify it of the closedown, but ATM returned the error-code error-code.
Action | Check the meaning of the given error code, to see if ATM needs any corrective action. Nucleus termination will continue. Any incomplete global transactions will be resynchronized when the nucleus next communicates with the transaction manager.

ATM052_20 | PROTOCOL ERROR. ATM NOT INITIALIZED.
Explanation | This message is issued if an ATM transaction manager receives an operator command before it has completed its initialization processing.
Action | Wait, and re-issue the command later.

ATM054_20 | HANDSHAKE ERROR; ID/RSP/SUB/CMD: dbid/rsp/sub/cmd
Explanation | An error occurred while the transaction manager was trying to handshake with the partner transaction manager identified by dbid. The error was an unexpected Adabas response code (rsp). The subcode (sub) and command code (cmd) are provided.
Action | If the cause of the error is not clear from the description of the response code, report the details to your Software AG support representative, noting the values of the variables.

ATM055_20 | HANDSHAKE ERROR; ERR/QERR: error-code/queue-error
Explanation | An error occurred while the transaction manager was attempting to handshake with a partner transaction manager. The error code and, if applicable, a queue management error are provided.
Action | Refer to the descriptions of the possible error codes. If the cause of the error is not apparent, report the details to your Software AG support representative, noting the error code.

ATM057_10 | NO FREE SLOTS IN queue-area
Explanation | The indicated queue area is full.
Action | Increase the relevant parameter and restart the Transaction Manager. If the indicated queue area has no associated runtime parameter, the error was most likely caused by shortage of memory. In this case, increase the amount of memory available to the Transaction Manager and restart it.

ATM058_10 | MIXED TRANSACTION STATUS/RESULT REPORTED BY ATM dbid
Explanation | The transaction manager was attempting restart processing for incomplete transactions involving the partner transaction manager dbid, which was restarting. The partner transaction manager reported an inconsistent transaction status (partly committed, partly backed out). Subsequent messages identify the owner of the transaction. Likely causes include the following: Some Adabas nucleus heuristically terminated its part of a global transaction. Some ATM transaction manager was started with `TMRESTART={FORCE | FORCEALL}`. A transaction branch was forcibly terminated on request from an online services user or operator. Some database was restored to a status that is inconsistent with the status of other databases in the network. Pending restart information in some database was discarded (for example, by formatting Work or by starting with `ADARUN IGNDTP=YES`).
Action | In some of the above cases, details of the transaction (branch) might be found in an ATM transaction manager's suspect transaction journal (STJ) file. Otherwise, use Online Services or application-specific checks to determine the status of the transaction.

ATM059_10 | MIXED TRANSACTION STATUS/RESULT; DBID dbid
Explanation | ATM was attempting restart processing for incomplete transactions involving the indicated database dbid, which was restarting. The transaction manager detected an inconsistent transaction status (partly committed, partly backed out). Refer to message ATM058 for likely causes.
Action | Use Online Services or application-specific checks to determine the status of the transaction.

ATM060_10 | CONFLICTING TRANSACTION STATUS REPORTED BY ATM/DB dbid
Explanation | ATM was attempting restart processing for incomplete transactions involving the partner ATM transaction manager or database indicated by dbid, which was restarting. The ATM transaction manager detected an inconsistent or unknown transaction identifier (XID). Subsequent messages provide further information.
Action | Use Online Services or application-specific checks to determine the status of the transaction.

ATM061_10 | MIXED TRANSACTION STATUS FOR USER userid
Explanation | This message indicates the Client ID of the owner of the transaction associated with a previous ATM058 or ATM059 message.
Action | Refer to the explanation of the preceding message.

ATM062_10 | CONFLICTING TRANSACTION STATUS FOR USER userid
Explanation | This message indicates the Client ID of the owner of the transaction associated with a previous ATM060 message.
Action | Refer to the explanation of the preceding message.

ATM063_10 | ERROR UPDATING PRR; RSP/SUB/CMD: rsp/sub/cmd
Explanation | The ATM transaction manager received an unexpected response code while attempting to update a recovery record in its recovery file. The message gives the response code (rsp), subcode (sub), and command code (cmd).
Action | If the cause of the error is not clear from the description of the response code, report the details to your Software AG support representative, noting the values of the variables.

ATM064_10 | ERROR UPDATING PRR; ERR: error-code
Explanation | The ATM transaction manager encountered the indicated error code while attempting to update a recovery record in its recovery file.
Action | Refer to the descriptions of the possible error codes. If the cause of the error is not apparent, report the details to your Software AG support representative, noting the error code.

ATM067_10 | UNSUPPORTED FUNCTION
Explanation | The transaction manager received a function call that is not valid.
Action | Contact your Software AG support representative.

ATM068_04 | QUIESCING TRANSACTIONS FOR DB dbid
Explanation | The transaction manager is attempting to complete (commit or back out) all active global transactions that involve the indicated database in response to a request from an Online Services user; or an `ADAEND` command issued to the indicated database.
Action | This message is for information only.

ATM069_10 | TRANSACTIONS CANNOT BE QUIESCED. DB/ERR: dbid/err
Explanation | The indicated error occurred while the transaction manager was trying to quiesce transactions involving database dbid. As a result, ATM was unable to complete one or more transactions.
Action | Refer to the descriptions of the possible error codes. If the appropriate action is not clear, contact your Software AG support representative.

ATM070_10 | LOCAL TRAN(S) STILL IN DOUBT ON DB dbid
Explanation | ATM attempted to complete (commit or back out) all active global transactions that involve the indicated database, but at the end of the process, at least one transaction or transaction branch involving the database remained active.
Action | This message may be preceded or followed by messages requiring action. If so, refer to the explanations of those messages.

ATM071_10 | FOLLOWING TMS IN ERROR: id-list
Explanation | While the ATM transaction manager was attempting to quiesce transactions on a database, it asked one or more partner managers to do the same, but one or more of them returned an unexpected error. The message lists up to four partner transaction managers that failed to carry out its request.
Action | Use Online Services to check the status of the indicated ATM nodes and, if necessary, to quiesce each transaction manager’s transactions for the required database.

ATM072_10 | HEURISTIC TERMINATIONS MAY RESULT
Explanation | This message is preceded by message ATM068 and one or more of the messages ATM069, ATM070, and ATM071. The database indicated in message ATM068 received an `ADAEND` command and asked ATM to quiesce its global transactions. At the end of the process, at least one transaction or transaction branch involving the database remained active. Any such transaction or transaction branch is heuristically terminated when its `TT` time limit expires, which could result in mixed completion of the related global transactions.
Action | This message warns of the impending loss of global transaction integrity for those global transactions that are still active. Use Online Services to identify the transactions that could not be quiesced. Any transaction that remains active when its `TT` time limit expires is heuristically committed. To prevent this, if appropriate, use Online Services to forcibly back out any such transaction.

ATM073_10 | DB ACTIVITY NOT QUIESCED. CHECK ATM MANAGER nodeid
Explanation | A `DTP=RM` nucleus that received an `ADAEND` command requested the transaction manager with the indicated Node ID to quiesce its global transactions. The request failed.
Action | Check that the indicated transaction manager is active, and check for error messages issued by it. Use Online Services to ask the transaction manager to quiesce transactions on the database.

ATM074_10 | RRMS REPORTED ERROR. FNC/RF/COMMID: fnc/rf/comm-id
Explanation | A problem was encountered with a transaction that is (or should be) under the control of RRMS. The RRMS function in error and its return code (values fnc and rf) are provided, together with the 28-byte Communications ID of the user who owns the transaction.
Action | Check the RRMS documentation to determine the meaning of the return code (value “rf”). If the cause of the problem is still not apparent, contact your Software AG support representative, noting the values of “fnc” and “rf”.

ATM075_10 | RRMS REPORTED EXIT MANAGER UNAVAILABLE
Explanation | ATM is interfacing to RRMS and has been notified that one of the RRMS exit managers has become unavailable. ATM continues to interface to RRMS once the exit manager has restarted.
Action | Report the problem to your systems programming staff.

ATM076_10 | RRMS REPORTED EXITS UNSET. REASON: rrrr
Explanation | ATM is interfacing to RRMS and has been notified that its exits have become unavailable.
Action | Check the console log for other messages that may indicate the cause of the problem. Check the RRMS documentation to determine the meaning of the reason code (value rrrr). If possible, correct the problem and restart ATM. If the cause of the problem is not apparent, contact your Software AG support representative, noting the value of rrrr.

ATM077_10 | RRS EXIT FAILED. X: xx R: rr AB: aaaaaaaa ABR: nnnnnnnn
Explanation | ATM is interfacing to RRMS and an error has occurred in one of its exit routines. The message details the exit number (xx), failure reason (rr), ABEND code (aaaaaaaa) and reason code (nnnnnnnn).
Action | If the cause of the problem is not apparent from the details of the message, contact your Software AG support representative, noting all the values given in the message.

ATM078_10 | EXTERNALLY-OWNED TRANSACTION INCOMPLETE. DB/TC: ddddd/cccc
Explanation | A database is trying to shut down in response to an `ADAEND` command; the ATM transaction manager has been asked to quiesce any transactions that involve the database, but has been unable to complete the process because at least one of those incomplete transactions is under the control of an external transaction coordinator. The database will not shut down until all global transactions are completed or backed out. The message identifies the database that is being shut down (value ddddd) and the external transaction coordinator (value cccc).
Action | Use the facilities of the external transaction coordinator to force the completion or removal of the incomplete transactions. The transactions can be identified by the Online Services application.

ATM080_08 | ‘STOP ALL USERS’ REQUESTED BY USER userid
Explanation | An Online Services user issued a "stop all transactions" request. The userid is the last 8 bytes of the user’s Communication ID.
Action | This message is for information and audit purposes only.

ATM081_08 | ‘FORCE STOP ALL USERS’ REQUESTED BY USER userid
Explanation | An Online Services user issued a "force stop all transactions" request. The userid is the last 8 bytes of the client session’s Communication ID.
Action | This message is for information and audit purposes only.

ATM082_08 | SELECTIVE MASS STOP USERS REQUESTED BY USER userid
Explanation | An Online Services user issued a selective mass “stop transactions” request. The userid is the last 8 bytes of the user’s Communication ID.
Action | This message is for information and audit purposes only.

ATM083_08 | FORCED SELECTIVE MASS STOP USERS REQUESTED BY USER userid
Explanation | An Online Services user issued a "forced selective mass stop transactions" request. The userid is the last 8 bytes of the user’s Communication ID.
Action | This message is for information and audit purposes only.

ATM084_10 | TRANSACTION BRANCH FORCIBLY COMPLETED. COMMID: commid
Explanation | In response to a "forced stop transactions" request from an Online Services user, ATM forced completion of the local branch of the transaction belonging to the client whose ID appears in the following ATM087 message. If the transaction had previously been prepared, ATM committed the branch; otherwise, ATM backed out the branch.
Action | This message is for information and audit purposes only.

ATM085_10 | TRANSACTION DETAILS TRANSFERRED TO JOURNAL. COMMID: commid
Explanation | In response to a "forced stop transactions" request from an Online Services user, the ATM transaction manager purged the transaction (branch) belonging to the client whose ID appears in the following ATM087 message. Details of the transaction (branch) can be found in the ATM suspect transaction journal file.
Action | This message is for information and audit purposes only.

ATM086_10 | RECOVERY RECORD DELETED FOR COMMID: commid
Explanation | In response to a request from an Online Services user, the ATM transaction manager purged from its recovery file, recovery information relating to the client whose ID appears in the following ATM087 message.
Action | This message is for information and audit purposes only.

ATM087_10 | commid
Explanation | This message relates to the message(s) immediately preceding it, and gives the 28-byte Communication ID (commid) of the client session associated with the earlier message(s).
Action | Refer to the explanation of preceding message(s).

ATM088_10 | ERROR TRANSFERRING TO STJ
Explanation | This message might be issued during forced restart of an ATM transaction manager, and indicates that a transaction that could not be completed could not be moved to the suspect transaction journal file. Subsequent messages provide more details of the error.
Action | Refer to explanation of following message(s).

ATM089_10 | DATA TRANSFERRED TO STJ FOR USER userid
Explanation | This message might be issued during forced restart of an ATM transaction manager, and indicates that a transaction that could not be completed has been moved to the suspect transaction journal file. The userid is the Client ID of the transaction’s owner.
Action | This message is for information and audit purposes only.

ATM090_04 | FORCED PRR DELETION REQUESTED BY USER userid
Explanation | The specified user forcibly deleted a recovery record from the ATM transaction manager's recovery file using the Online Services application. The userid is the last 8 bytes of the user’s Communication ID.
Action | The message is for information and audit purposes only.

ATM091_04 | PRR DELETION FOR COMMID:
Explanation | A recovery record was deleted from the ATM transaction manager's recovery file using the Online Services application. The Communication ID of the associated user is reported in an ATM087 message immediately after the ATM091 message.
Action | The message is for information only.

ATM092_10 | URID: urid
Explanation | This messages relates to the ATM136 message that immediately precedes it. It identifies the URID of the CICS unit of work that the ATM136 message relates to.
Action | Refer to the explanation of the ATM136 message.

ATM095_08 | COMMAND NOT RECOGNIZED
Explanation | An invalid operator command was entered.
Action | Issue the command correctly.

ATM099_08 | ATM CLOSEDOWN REQUESTED
Explanation | The operator entered the command `ATM END`.
Action | This message is for information only.

ATM100_08 | ATM IMMEDIATE CLOSEDOWN REQUESTED
Explanation | The operator entered the command `ATM HALT`.
Action | This message is for information only.

ATM101_08 | ATM CLOSEDOWN PROCESS STARTED
Explanation | The transaction manager is in the process of closing down.
Action | This message is for information only.

ATM102_10 | DB CLOSEDOWN ERROR; ID/RSP/SUB/RC: dbid/rsp/subcode/rc
Explanation | An `ADAEND` command was entered for the database dbid, but the transaction manager encountered an unexpected condition during the close-down sequence. Either a response code and subcode will be given (rsp/subcode), or an ATM error code (rc).
Action | Refer to the description of the Adabas response code or the ATM error code. If the appropriate action is not clear, contact your Software AG support representative.

ATM103_08 | TM END PENDING, INCOMPLETE TRANSACTIONS REMAIN
Explanation | An `ATM END` operator command was issued but the transaction manager is unable to close down immediately because of incomplete global transactions. Under these circumstances, ATM103 messages are issued for the first five of these incomplete transactions, each message displaying the client’s job-name, job-number and last 8 bytes of the communication ID. These messages are repeated at 60 second intervals until the transactions are completed and close down occurs.
Action | Wait for the incomplete transactions to be resolved, or use the `ATM HALT` command to cause the transaction manager to terminate immediately, leaving the incomplete transactions to be resolved the next time it is activated.

ATM104_10 | MEMORY SHORTAGE; ADAEND PROTOCOL MIGHT BE AFFECTED
Explanation | This messages can appear when a `DTP=RM` database is started. It indicates that certain memory areas could not be acquired. Database processing should not be affected by this condition. However, there is a possibility that the closedown protocol that happens when `ADAEND` is issued to the database will not proceed as normal; this could increase the risk of heuristically terminated transactions.
Action | Make more memory available to the database job and restart it.

ATM105_08 | ATM closedown process ended
Explanation | The transaction manager has finished its closedown process.
Action | This message is for information only.

ATM106_04 | Adabas RM dbid connection, type Peer TM nodeid connection
Explanation | This message is issued by a transaction manager approximately five minutes after start-up and hourly thereafter. It displays a list of known databases (dbid) and peer transaction managers (nodeid). A DTP=RM database is identified by the characters "RM" and the connection type may be one of the following: Local – the database is within the scope of the System Coordinator group name and is local to this transaction manager. Remote – the database is within the scope of the System Coordinator group name and is remote to this transaction manager External - the database is not within the scope of the System Coordinator group name.
Action | This message is for information only.

ATM110_04 | SESSION STATISTICS:
Explanation | This message is issued during transaction manager termination. Statistical messages follow.
Action | This message is for information only.

ATM119_04 | STATISTICS HAVE BEEN RESET
Explanation | This message is issued when the transaction manager's statistics are reset to zero, in response to an `ATM RSTAT` operator command or an equivalent request from an Online Services user.
Action | This message is for information only.

ATM120_04 | DB dbid waiting for Transaction Manager connection
Explanation | This message is issued by a `DTP=RM` database that is initializing. The nucleus is required to connect to the local Transaction Manager for distributed transaction processing which has not yet occurred, initialization continues but participation in distributed transactions is not yet possible. Note: In the case of a `DTP=RM` nucleus which is part of an Adabas Parallel Services cluster or an Adabas Cluster Services cluster, the message gives the ID of the nucleus, not the database number of the cluster, and begins, `NC dbid waiting for …`.
Action | This message is for information only, connection will occur automatically when the TM is ready.

ATM121_10 | DB dbid ATM82 (and above) - TM now runs in COR Daemon, DB dbid Normal termination of this node is scheduled
Explanation | This message is issued when a database is started with `ADARUN DTP=TM`. This method of identifying a Transaction Manager is no longer applicable, it is only required for previous releases of ATM. The database will terminate normally.
Action | Review the installation procedure for the correct way to install the Transaction Manager so that is runs in the Adabas System Coordinator daemon.

ATM122_20 | DTP operation FAILED, DB/TM/RSP/SUB/RC: dbid/tmid/rsp/sub/rc
Explanation | This message can be issued by a database for which the ADARUN parameter `DTP=RM` was specified, or by the ATM transaction manager. It can appear during an attempt to sign a database on to a transaction manager for distributed transaction processing, or to sign the database off, as indicated by operation. “Sign-on” can happen during initialization of a transaction manager or when the database is started. “Sign-off” happens when the database is terminated. The message indicates that an unexpected condition was detected. It includes the dbid of the database, the node ID (tmid) of the transaction manager, and might also contain a response code (rsp), subcode (sub) and return code (rc) for the error.
Action | If this message indicates sign-on and is followed by an ATM124 message from the database identified in the message detail, this indicates that the error condition was transient, and that the DTP sign-on has now taken place. If there is no ATM124 message, and if the cause of the error is not clear from the description of the response code, subcode and return code, report the details to your Software AG support representative, noting the values of the variables in the message. If the message indicates sign-off, it is given for information only.

ATM124_04 | DB dbid connected with Transaction Manager node nodeid
Explanation | This message is issued by a `DTP=RM` database or, a `DTP=RM` nucleus which is part of an Adabas Cluster Services or Adabas Parallel Services cluster, when it has connected with a Transaction Manager (nodeid). Under normal circumstances this message will be preceded by an ATM129 message. Note: In the case of a `DTP=RM` nucleus which is part of an Adabas Cluster Services or Adabas Parallel Services cluster, the message gives the ID of the nucleus, not the database number of the cluster, and begins, `Nc dbid connected with …`.
Action | This message is for information only.

ATM125_10 | ATM NOT ACTIVE. ADAEND CANNOT COMPLETE.
Explanation | An `ADAEND` command was entered for database dbid, but the normal process of quiescing open transactions could not occur because the transaction manager was not active. The database does not close down.
Action | Activate the transaction manager and use the Online Services application to quiesce any open transactions on the database. When you are sure that all global transactions involving the database have been completed or backed out, you can close down the database with a `HALT` command. Caution: If you issue a `HALT` command while there are incomplete global transactions, the integrity of those transactions can no longer be guaranteed.

ATM126_04 | RM disconnected — no unresolved transactions: dbid
Explanation | The ATM transaction manager issues this message when a `DTP=RM` database identified by dbid terminates with no outstanding transactions involving the database. If the terminating database is part of an Adabas Parallel Services or Adabas Cluster Services cluster, the value dbid might have the form `Nuc nnnnn`, where nnnnn is the ID of the terminating nucleus.
Action | This message is for information only.

ATM127_04 | RM disconnected — unprepared transactions remaining: dbid
Explanation | The ATM transaction manager issues this message when a `DTP=RM` database identified by dbid terminates with outstanding unprepared transactions involving the database. If the terminating database is part of an Adabas Parallel Services or Adabas Cluster Services cluster, the value dbid might have the form `Nuc nnnnn`, where nnnnn is the ID of the terminating nucleus.
Action | This message is for information only.

ATM128_04 | RM disconnected — prepared transactions remaining: dbid
Explanation | The ATM transaction manager issues this message when a `DTP=RM` database (dbid) terminates with outstanding prepared transactions involving the database. If the terminating database is part of an Adabas Parallel Services or Adabas Cluster Services cluster, the value dbid might have the form `Nuc nnnnn`, where nnnnn is the ID of the terminating nucleus.
Action | In the case of a normal database, restart the database with `DTP=RM`. If the message identifies a nucleus within an Adabas Parallel Services or Adabas Cluster Services cluster, and there is another nucleus in the cluster which is still executing, no action is necessary; otherwise, restart a member of the cluster, with `DTP=RM`. Caution: If the database is started with `DTP=NO`, data integrity cannot be guaranteed.

ATM129_04 | DB dbid connecting with Transaction Manager node nodeid
Explanation | This message is issued by a `DTP=RM` database or, a `DTP=RM` nucleus which is part of an Adabas Cluster Services or Adabas Parallel Services cluster, when it is connecting with a Transaction Manager (nodeid). Under normal circumstances this message will be followed by an ATM124 message. Note: In the case of a `DTP=RM` nucleus which is part of an Adabas Cluster Services or Adabas Parallel Services cluster, the message gives the ID of the nucleus, not the database number of the cluster, and begins, `Nc dbid connecting with …`.
Action | This message is for information only.

ATM130_20 | ATM PROXY INITIALIZATION FAILED
Explanation | This message can be issued by a job or TP system for which the client runtime control `ATM=ON` has been specified. It indicates a fatal error which prevented the ATM client proxy from initializing.
Action | Check for earlier messages which might indicate the reason for the failure. If the cause of the error is not clear, contact your Software AG support representative.

ATM131_10 | RMI RESYNC ERROR. SYS/RC/RC2 sys/rc/rc2
Explanation | An error occurred during the synchronization process that takes place during ATM or CICS restart when the CICS Resource Manager Interface is in use. The message provides the System ID of the CICS system (value sys), a CICS or ATM error code (value rc), and possibly a secondary return code or Adabas response code (value rc2).
Action | Refer to the descriptions of the possible error codes. If possible, correct the error and restart the ATM transaction manager; otherwise report the details to your Software AG support representative.

ATM132_10 | RMI RESYNC ERROR. SYS/CD/RSP sys/cd/rsp
Explanation | An error occurred during the synchronization process that takes place during ATM or CICS restart when the CICS Resource Manager Interface is in use. The message provides the System ID of the CICS system (value sys), a CICS command or function name (value cd), and CICS response code (value rsp).
Action | Refer to the CICS documentation for an explanation of the error condition. If possible, correct the error and restart CICS; otherwise report the details to your Software AG support representative.

ATM133_10 | RMI SYNCPOINT ERROR. URID urid
Explanation | An error occurred during syncpoint processing of a transaction that was under the control of the CICS syncpoint manager. The CICS Unit-of-Recovery ID (value urid) belonging to the transaction is displayed.
Action | This message is followed by message ATM134, which gives more information about the error.

ATM134_10 | RMI SYNCPOINT ERROR. SYS/RC/RSP sys/rc/rsp
Explanation | This message follows message ATM133 and provides details of an error that occurred during syncpoint processing under the control of the CICS syncpoint manager. The message provides the System ID of the CICS system (value sys), an ATM error code (value rc), and, depending on the ATM error code, a CICS or Adabas response code (value rsp).
Action | Refer to the relevant documentation for an explanation of the error condition. If the cause is not then apparent, report the details to your Software AG support representative.

ATM135_10 | RMI RESYNC ERROR. APP/CD/RSP app/cd/rsp
Explanation | An error occurred during the synchronization process that takes place during ATM or CICS restart when the CICS Resource Manager Interface is in use. The message provides the Application ID of the CICS system (value app), a CICS command or function name (value cd), and an error code (value rsp). If the error code begins with the character “R”, the remaining digits are an ATM error code; otherwise the value of rsp is a CICS response code.
Action | Refer to ATM error codes or to the CICS documentation, as appropriate, for an explanation of the error condition. If possible, correct the error and restart CICS and, if necessary, the ATM transaction manager; otherwise report the details to your Software AG support representative.

ATM136_10 | RMI RESYNC ERROR. APP/RC app/rc
Explanation | An error occurred during the synchronization process that takes place during ATM or CICS restart when the CICS Resource Manager Interface is in use. The message provides the Application ID of the CICS system (value app) and an ATM error code (value rc). This message may be followed by an ATM092 message indicating the URID of the CICS unit of work for which the error occurred.
Action | Refer to the descriptions of the possible error codes. If possible, correct the error and restart the ATM transaction manager; otherwise report the details to your Software AG support representative.

ATM137_10 | EXCI COMMAREA COULD NOT BE ADDRESSED
Explanation | An internal error occurred during the synchronization process that takes place during ATM restart when the CICS Resource Manager Interface is in use.
Action | Report the error to your Software AG support representative. You may bypass the problem by restarting your CICS systems after the ATM transaction manager has initialized.

ATM138_10 | RMI RESYNC ISSUED. SYS sys
Explanation | This message can appear during restart of an ATM transaction manager or a CICS system in an environment in which some transactions are controlled by the CICS Syncpoint Manager. It indicates that resynchronization processing will be carried out for incomplete transactions controlled by the CICS system with the System ID sys.
Action | This message is for information only.

ATM139_10 | RMI resync complete. Sys sys
Explanation | This message appears in an environment in which some transactions are controlled by the CICS Syncpoint Manager. The message follows restart of an ATM transaction manager or a CICS system and indicates that the synchronization process has executed for incomplete transactions controlled by the CICS system with the System ID sys.
Action | This message does not necessarily indicate that every incomplete transaction was resolved satisfactorily. Check the console log for other messages which might indicate a problem.

ATM140_10 | ATM PROXY DETECTED cmd DB dbid RSP rsp AD2 Xadditions-2
Explanation | This message is issued by the ATM client proxy for the first ATM-related error incurred by each client session. The message can include a command code, Database ID, response code and Additions-2 data, providing further information about the error. This message is followed by ATM087 messages which give the 28-byte Communication ID of the client session, first in character form, and then in hexadecimal.
Action | Check the meaning of the indicated response code and Additions-2 data. If the cause of the error is not apparent, contact your Software AG support representative, noting all the values given in the message.

ATM141_04 | DTP DISABLED FOR THIS JOB BY RUNTIME CONTROL
Explanation | This message is issued by the ATM client proxy. It indicates that client sessions executing within this job have been exempted from distributed transaction processing by the setting of a client runtime control.
Action | This message is for information only.

ATM144_08 | SYSTEM COORDINATOR GROUP NAME NOT SPECIFIED
Explanation | This message can be issued by a client job. It indicates that the ATM client runtime controls in effect for this job do not include the name of an Adabas System Coordinator Group. ATM processing will not be activated for the job.
Action | Use the Online Services application to specify the name of the System Coordinator Group in which the job will execute.

ATM160_10 | SYSCO DAEMON ERROR; ID/RSP/SUB/FNC/SBF/ERR: id/rsp/sub/fnc/sbf/err
Explanation | This message can appear during restart of an ATM transaction manager. It indicates that a call to an Adabas System Coordinator daemon returned an unexpected result. The message will include at least some of the following: the Node ID (id) of the Adabas System Coordinator daemon, the response code (rsp) and subcode (sub) returned by the Adabas System Coordinator daemon, the function and subfunction codes of the call (fnc and sbf), and an error code (err).
Action | If the cause of the error is not apparent from the description and content of the message, contact your Software AG support representative.

ATM163_04 | ERROR DELETING PER; RSP/SUB/CMD: rsp/sub/cmd
Explanation | This message indicates that an error occurred while deleting a Persistent Error Record. The message contains the following diagnostic information: a response code and subcode (rsp and sub) and a command code (cmd).
Action | If the cause of the error is not apparent from the description and content of the message, contact your Software AG support representative.

ATM164_04 | ERROR DELETING PER; ERR: err
Explanation | This message indicates that an error occurred while deleting a Persistent Error Record. The message contains an ATM error code (err).
Action | If the cause of the error is not apparent from the description and content of the message, contact your Software AG support representative.

ATM167_10 | MTR PROCESSING ERROR; ID/ERR/RSP/SUB/CMD: id/err/rsp/sub/cmd
Explanation | This message indicates that an error occurred while processing a migrated transaction record in an Adabas Cluster Services or Parallel Services environment. The message will contain at least some of the following diagnostic information: a database or Node ID (id), an error code (err), a response code and subcode (rsp and sub) and a command code (cmd). The user’s transaction is backed out, and a pending response code 9 (ADARSP009), subcode 77 is set.
Action | If the cause of the error is not apparent from the description and content of the message, contact your Software AG support representative.

ATM168_10 | CLIENT MIGRATED, BUT NO MTR FILE DEFINED
Explanation | This message indicates that a client session that had an open transaction has been migrated from one node to another within a cluster (for example, CICSplex), but ATM cannot handle this session’s transaction safely because no Migrated Transaction Record (MTR) file has been defined. The transaction is backed out, and a pending response code 9 (ADARSP009), subcode 77 is set.
Action | Define and create an MTR file, and restart the ATM transaction managers and clustered application environments in the COR group.

ATM169_10 | MTR FILE IS NOT DEFINED
Explanation | This is a warning message, and it can appear during initialization of an ATM transaction manager. It indicates that no Migrated Transaction Record (MTR) file definition was found. An MTR file is required if you use application environments in which a client session that is not at global transaction status can be migrated around a cluster (for example, CICSplex, with ATM client runtime control `TransactionModel` set to DYNAMIC).
Action | If your application environments are such that no MTR file is needed, you can ignore this message, or suppress it by making a dummy MTR file definition using SYSCOR. Otherwise, define and create an MTR file, and restart the ATM transaction managers and clustered application environments in the COR group.

ATM171_08 | TM tmid STARTING TRANSACTION FLUSH
Explanation | This message can be issued by a `DTP=RM` database when the database has received an `ADAEND` command. It indicates that the Transaction Manager with the given ID (tmid) is attempting to terminate any incomplete global transactions that have changed the database, so that the database can terminate cleanly. This message should be followed by either an ATM172 or an ATM173 message, indicating whether or not all relevant transactions were terminated.
Action | This message is for information only.

ATM172_10 | TM tmid DID NOT COMPLETE TRANSACTION FLUSH
Explanation | This message might be issued by a `DTP=RM` database after message ATM171. It indicates that the Transaction Manager with the given ID (tmid) was not able to terminate all global transactions that have changed the database. This might mean that a superior TM or external transaction co-ordinator has not indicated what the outcome of a transaction should be.
Action | Use the Online Services application to identify the offending transactions. If possible, resolve any such transaction through the co-ordinator that controls the root of the transaction. If this is not possible, you might choose to use SYSATM’s “stop” facility to force resolution of a transaction, if you are sure that this will not result in loss of transactional integrity.

ATM173_08 | TM tmid COMPLETED TRANSACTION FLUSH
Explanation | This message might be issued by a `DTP=RM` database after message ATM171. It indicates that the Transaction Manager with the given ID (tmid) successfully terminated all incomplete global transactions that had changed the database.
Action | This message is for information only.

ATM174_10 | NO TM ACTIVE
Explanation | This message can be issued by a `DTP=RM` database when the database has received an `ADAEND` command. It indicates that there are incomplete, prepared transactions in the database, but the Transaction Manager that owns these transactions is not currently active. The ADAEND process cannot complete until the incomplete transactions have been resolved.
Action | Restart the inactive Transaction Manager.

ATM177_08 | Transaction Manager waiting for TM agent node: nodeid
Explanation | This message is issued when a transaction manager has restarted following a previous abnormal termination after which a peer transaction manager was established as its agent. This transaction manager has notified the agent (nodeid) of its restart but must wait for the agent to relinquish its agent role.
Action | This message is for information only.

ATM178_08 | Agent processing relinquished for node: nodeid
Explanation | This message is issued when a transaction manager has relinquished its agent role at the request of a peer transaction manager (nodeid) which is restarting.
Action | This message is for information only.

ATM179_08 | Agent initialization successful for node: nodeid
Explanation | This message is issued when a transaction manager successfully initializes as an agent for a peer transaction manager (nodeid) which has terminated abnormally.
Action | This message is for information only.

ATM180_20 | Error during the opening of the recovery file: error-code
Explanation | This message is issued when a transaction manager is started and there is a problem opening the recovery file.
Action | Check the recovery file has been correctly defined according to the installation documentation. If the cause of the error is not apparent, report the details to your Software AG representative.

ATM181_08 | Agent initialization started for node: nodeid
Explanation | This message is issued when a transaction manager begins initializing as an agent for a peer transaction manager (nodeid) which has terminated abnormally.
Action | This message is for information only.

ATM182_20 | Agent initialization unsuccessful for node: nodeid
Explanation | This message is issued when a transaction manager unsuccessfully initializes as an agent for a peer transaction manager (nodeid) which has terminated abnormally. Preceding messages provide further information.
Action | This message is for information only. Other active peer transaction managers may also attempt agent initialization but, if none are successful, normal recovery processing will occur when the abnormally terminated transaction manager restarts.

ATM184_10 | TMRFI allocation failed: entity /error_code
Explanation | This message is issued if a failure occurred when the Transaction Manager attempted to allocate an additional number of blocks from the TMRFI file. If the failure is due to the TMRFI file being full, the error_code is replaced by the text "File full". Refer to ATM186 for an explanation of the entity name.
Action | In the event that a "File full" condition is reported, use the entity name in the message to identify which type of record was being processed at the time and use SYSATM Recovery File Functions to browse the corresponding records currently stored in the TMRFI file and, where possible, purge those that are no longer applicable. For any other error condition please contact your Software AG support representative providing the job log of the ATM transaction manager and a copy of the TMRFI file as close to the time of failure as possible.

ATM185_04 | TMRFI allocation successful: entity /blocks_allocated
Explanation | This message is issued when the Transaction Manager successfully allocates an additional number of blocks (blocks_allocated) from the TMRFI file. Refer to ATM186 for an explanation of the entity name. This message is always accompanied by message ATM187.
Action | This message is for information only.

ATM186_04 | TMRFI statistics / Text
Explanation | These messages are displayed at Transaction Manager start-up, shut-down or when an ATM DSTAT operator command is issued, and show general information about the size and usage of the TMRFI file. The TMRFI file manages different record types. These record types are also referred to as entities and consist of the following types: Recovery records (PRR) Suspect transaction records (STJ) System migration records (MTR) Pending response records (PER) ET data records (EDR) These messages display the number of blocks currently reserved for use by these entities. No parameters are required to be set or maintained in relation to these entities and any additional blocks required will be allocated automatically on demand, accompanied by an ATM185 message acknowledging successful allocation, and an ATM187 message reporting the remaining number of free blocks. The number of free blocks reported by the ATM186 and ATM187 messages can provide an early indication of the TMRFI file becoming full. All the other information provided is relevant only to Software AG in the event of problems associated with the use of the TMRFI file.
Action | This message is for information only.

ATM187_04 | TMRFI remaining free blocks: nnnnnnnn
Explanation | This message displays the number of free blocks remaining in the TMRFI file. It accompanies message ATM185 when the Transaction Manager successfully allocates an additional number of blocks from the TMRFI.
Action | This message is for information only. The number of free blocks in the TMRFI file is also displayed in message ATM186 at Transaction Manager start-up, shut-down or when an ATM DSTAT operator command is issued. The number of free blocks displayed can provide an early indication of the TMRFI becoming full.

ATM188_04 | RM connection pending: dbid Nuc nucid
Explanation | This message is issued by the Transaction Manager as a result of one of the following events: a local `DTP=RM` database is active a local `DTP=RM` nucleus which is part of an Adabas Parallel Services cluster is active a local or remote `DTP=RM` nucleus which is part of an Adabas Cluster Services cluster is active This can occur (a) if the Transaction Manager is already active and such a database or nucleus is started, or (b) such a database or nucleus is already active and the Transaction Manager is started. Under normal circumstances this message will be followed by an ATM190 message indicating successful connection. Note: The message gives the database number (dbid) and, in the case of a `DTP=RM` nucleus which is part of an Adabas Cluster Services or an Adabas Parallel Services cluster, the ID of the nucleus (nucid).
Action | This message is for information only.

ATM189_04 | RM disconnection pending: dbid Nuc nucid
Explanation | This message is issued by the Transaction Manager as a result of one of the following events: a local `DTP=RM` database is no longer active a local `DTP=RM` nucleus which is part of an Adabas Parallel Services cluster is no longer active a local or remote `DTP=RM` nucleus which is part of an Adabas Parallel Services cluster is no longer active This occurs when the Transaction Manager is active and such a database or nucleus is stopped. Under normal circumstances this message will be followed by an ATM126, ATM127, or ATM128 message indicating successful disconnection. Note: The message gives the database number (dbid) and, in the case of a `DTP=RM` nucleus which is part of an Adabas Cluster Services or an Adabas Parallel Services cluster, the ID of the nucleus (nucid).
Action | This message is for information only.

ATM190_04 | RM connected: dbid Nuc nucid
Explanation | This message is issued by the Transaction Manager as a result of successfully connecting to one of the following: a local `DTP=RM` database a local `DTP=RM` nucleus which is part of an Adabas Parallel Services cluster a local or remote `DTP=RM` nucleus which is part of an Adabas Cluster Services cluster This can occur (a) if the Transaction Manager is already active and such a database or nucleus is started, or (b) such a database or nucleus is already active and the Transaction Manager is started. Under normal circumstances this message will be preceded by an ATM188 message indicating pending connection. Note: The message gives the database number (dbid) and, in the case of a `DTP=RM` nucleus which is part of an Adabas Cluster Services or an Adabas Parallel Services cluster, the ID of the nucleus (nucid).
Action | This message is for information only.

ATM191_04 | DB dbid 2PC enabled with Transaction Manager node nodeid(L)
Explanation | This message is issued by a `DTP=RM` database or, a `DTP=RM` nucleus which is part of an Adabas Cluster Services or Adabas Parallel Services cluster, when it has connected with its local (L) Transaction Manager (nodeid). Under normal circumstances this message will be preceded by ATM129 and ATM124 messages. Note: In the case of a `DTP=RM` nucleus which is part of an Adabas Cluster Services or Adabas Parallel Services cluster, the message gives the ID of the nucleus, not the database number of the cluster, and begins, `Nc nucid 2PC enabled …`.
Action | This message is for information only.

ATM192_04 | DB dbid 2PC enabled with Transaction Manager node nodeid(R)
Explanation | This message is issued by a `DTP=RM` database or, a `DTP=RM` nucleus which is part of an Adabas Cluster Services or Adabas Parallel Services cluster, when it has connected with a remote (R) Transaction Manager (nodeid). Under normal circumstances this message will be preceded by ATM129 and ATM124 messages. Note: In the case of a `DTP=RM` nucleus which is part of an Adabas Cluster Services or Adabas Parallel Services cluster, the message gives the ID of the nucleus, not the database number of the cluster, and begins, `Nc nucid 2PC enabled …`.
Action | This message is for information only.