ATM Messages

One of the following occurred:

• an unexpected error

• an error created intentionally by ZAP

If the error was unexpected, contact your Software AG support representative.

The Adabas Transaction Manager cannot be used with this version of Adabas.

Use a version of Adabas that ATM supports.

The ATM recovery database failed to open for the reason indicated.

Correct the cause of the response code and restart the ATM transaction manager.

The named module could not be loaded.

Ensure that the module is in a library from which it can be loaded dynamically.

The ATM transaction manager could not open the DDCARD dataset.

Check the DDCARD dataset.

An error occurred when the ATM transaction manager attempted to read a record from DDCARD.

Check the DDCARD dataset.

A parameter is incorrectly specified in the DDCARD input. The first ATM006 message is followed by two additional messages, each prefixed with ATM006, displaying the parameter statement in error and indicating the position at which the error was detected.

Correct the parameter specification and restart the ATM transaction manager.

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

Do not attempt to run more than one ATM transaction manager under the same ID table and associated with the same COR group.

The ATM transaction manager cannot complete its initialization process until the associated Adabas System Coordinator daemon provides it with essential operational information.

Check that there is an Adabas System Coordinator daemon running under the same ID table (Adabas SVC) as the ATM transaction manager.

The ATM transaction manager attempted to register with the local SYSCO daemon, for notification of certain events (“event-type”), but the attempt failed. A summary reason might be given.

Check the availability of the local SYSCO daemon. If the SYSCO daemon is available, and the reason for the error is not apparent from the details in the error message, contact your Software AG support representative, noting the value of “reason”.

ATM was unable to acquire enough storage to initialize.

Increase the amount of memory available to the job and restart it.

ATM was unable to acquire enough storage to initialize the queue area indicated.

Increase the amount of memory available to the job and restart it.

ATM was unable to acquire enough storage for the area named.

Increase the amount of memory available to the job and restart it.

An error occurred during the initialization of an interface to an external transaction coordinator.

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

This message relates to the initialization of the ATM interface with RRMS. The ATM Database ID has changed since ATM was last used with this RRMS system.

The ATM Database ID must not be changed while there are global transactions in progress. If you have changed the Database ID and are sure that there were no incomplete global transactions, you can override this initialization error using the ADARUN parameter TMRESTART=FORCE.

This message relates to the initialization of the ATM interface with RRMS. The ATM Database ID has changed since ATM was last used with this RRMS system, but the inconsistency was ignored because of the setting of the ADARUN parameter TMRESTART.

None. This message is for information only.

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.

If it is not possible to recover the RRMS restart data, you can use the ADARUN 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.

The ATM transaction manager was unable to open the ATMLOG1 or ATMLOG2 dataset.

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

The database (dbid) is expected to be an ATM transaction manager, but it behaves as if it is not executing as an ATM transaction manager.

Check that DTP=TM is specified in the ADARUN parameters of the indicated database.

This message relates to the initialization of the ATM interface with RRMS. Initialization cannot complete because the RRS component of RRMS is not available.

Report the problem to your systems programming staff. The ATM transaction manager cannot initialize until RRS is active again.

If the ATM transaction manager is started with the parameter TMSYNCMGR=RRMS, this message is issued when the ATM RRMS interface has been initialized.

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.

This message is issued by a SYSCO daemon when it tries, and fails to supply parameters to an ATM transaction manager that is initializing. The transaction manager’s job name (“job”) is given, if this is known; otherwise the transaction manager’s Database ID is given. A response code (“rsp”), subcode (“sub”) and return code (“rc”) might also be given.

Check that the transaction manager identified in the message is active. If the cause of the error is not apparent, contact your Software AG support representative, noting the values of the variables in the message.

This message is preceded by message ATM025 or ATM033. It indicates the ISN associated with the error.

Refer to the explanation of the previously issued message.

The error (error-code) occurred during restart processing for the database (dbid).

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.

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.

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.

The error (error-code) occurred during restart processing for the partner ATM transaction manager (dbid).

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.

The maximum number of partner ATM transaction managers indicated by the ADARUN 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.

Set the TMNODES parameter to 191 and restart ATM.

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.

Contact your Software AG support representative.

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.

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.

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.

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.

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.

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.

This message refers to a previous error message and gives the Client ID of the user associated with the previous error.

Refer to details for the preceding message.

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.

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.

An unexpected condition was encountered when the transaction manager attempted to register a database job for notification, by the SYSCO daemon, of certain events. This can happen during initialization of an ATM manager, or when a database is started.

Check the availability of the local SYSCO daemon. If the SYSCO daemon is available, and the cause of the error is not clear from the details in the message, contact your Software AG support representative, noting the values of the variables given in the message.

This message can be issued by an Adabas System Coordinator daemon. It indicates that an error occurred while the SYSCO daemon was trying to notify its local ATM transaction manager that another ATM manager had started in the same COR group, elsewhere in the network. The message identifies the local ATM daemon (value “id”) and the remote ATM that is starting (value “peer”), and gives details of the error, which can include an Adabas response code and subcode (values “rsp” and “subcode”), or an ATM error code (value “rc”).

If the cause of the error is not clear from the description of the response code or error code, report the details to your Software AG support representative, noting the values of the variables in the message.

This message appears during the initialization of an ATM transaction manager, and indicates that initialization of the transaction manager’s environment has started.

None. This message is for information only.

This message is issued by an ATM transaction manager at the end of its initialization process. It identifies the Ababas System Coordinator group that the transaction manager is associated with, and the job name of the local COR daemon.

None. This message is for information only.

This message is issued during ATM restart when the transaction manager has issued 100 error messages. It indicates that any additional errors encountered during the restart process will be written to the DDPRINT dataset only, and not to the console.

None. This message is for information only.

This message is preceded by message ATM025. It indicates that serious errors prevent the transaction manager from restarting affected transactions.

Correct the error reported in the ATM025 message; then restart the database indicated in the message.

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.

This message is for information only. Restart processing for such transactions occurs when the indicated database is restarted.

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.

This message is for information only. Restart processing for such transactions occurs when the indicated TM is restarted.

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.

This message is for information only. The suppressed messages can be found in the DDPRINT dataset.

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.

This message is for information only.

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.

This message is for information only.

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.

This message is for information only.

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 database. The number indicated should be zero unless the TMRESTART parameter indicates a forced restart.

This message is for information only.

A serious error prevented the transaction manager from initializing. Previous messages should indicate the reason.

Refer to the explanations of preceding error messages.

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.

This message is for information only.

This message appears at the end of the transaction manager's initialization processing if any errors were encountered reading recovery records.

The message is for information only. For information about the errors encountered, refer to the error messages that precede this message.

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

Nucleus termination will continue. Any incomplete global transactions will be resynchronized when the nucleus next communicates with the ATM transaction manager.

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

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.

This message is issued if an ATM transaction manager receives an operator command before it has completed its initialization processing.

Wait, and re-issue the command later.

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.

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.

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.

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.

When a certain pool in storage reaches 85% full (rounded down, minimum value 1), this message is issued as a warning.

Check the high-water mark for the indicated parameter, and if necessary increase the appropriate parameter value and restart the ATM transaction manager.

The indicated queue area is full.

Increase the relevant parameter and restart the ATM transaction manager. If the indicated queue area has no associated ADARUN 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.

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

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.

ATM was attempting restart processing for incomplete transactions involving the indicated database, which was restarting. The transaction manager detected an inconsistent transaction status (partly committed, partly backed out). Refer to message ATM058 for likely causes.

Use Online Services or application-specific checks to determine the status of the transaction.

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.

Use Online Services or application-specific checks to determine the status of the transaction.

This message indicates the Client ID of the owner of the transaction associated with a previous ATM058 or ATM059 message.

Refer to the explanation of the preceding message.

This message indicates the Client ID of the owner of the transaction associated with a previous ATM060 message.

Refer to the explanation of the preceding message.

The ATM transaction manager received an unexpected response code while attempting to update a recovery record in its database. The message gives the response code (rsp), subcode (sub), and command code (cmd).

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.

The ATM transaction manager encountered the indicated error code while attempting to update a recovery record in its database.

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.

The ATM transaction manager encountered an error while tyring to write to one of its dual ATMLOG datasets. Logging is disabled.

Check for operating system messages that might indicate the cause of the error.

Either the log file previously in use was full or the operator command TM FEOFLOG was used.

This message is for information only.

The transaction manager received a function call that is not valid.

Contact your Software AG support representative.

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.

This message is for information only.

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.

Refer to the descriptions of the possible error codes. If the appropriate action is not clear, contact your Software AG support representative.

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.

This message may be preceded or followed by messages requiring action. If so, refer to the explanations of those messages.

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.

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.

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.

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.

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.

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.

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.

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

Note:
This message appears on the console, but not in the DDPRINT report.

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.

Report the problem to your systems programming staff.

Note:
This message appears on the console, but not in the DDPRINT report.

ATM is interfacing to RRMS and has been notified that its exits have become unavailable.

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

Note:
This message appears on the console, but not in the DDPRINT report.

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”).

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.

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”).

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.

An Online Services user issued a "stop all transactions" request. “Userid” is the last 8 bytes of the user’s Communication ID.

This message is for information and audit purposes only.

An Online Services user issued a "force stop all transactions" request. “Userid” is the last 8 bytes of the client session’s Communication ID.

This message is for information and audit purposes only.

An Online Services user issued a selective mass “stop transactions” request. “Userid” is the last 8 bytes of the user’s Communication ID.

This message is for information and audit purposes only.

An Online Services user issued a "forced selective mass stop transactions" request. “Userid” is the last 8 bytes of the user’s Communication ID.

This message is for information and audit purposes only.

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.

This message is for information and audit purposes only.

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.

This message is for information and audit purposes only.

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.

This message is for information and audit purposes only.

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

Refer to the explanation of preceding message(s).

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.

Refer to explanation of following message(s).

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. “Userid” is the Client ID of the transaction’s owner.

This message is for information and audit purposes only.

The specified user forcibly deleted a recovery record from the ATM transaction manager's database using the Online Services application. “userid” is the last 8 bytes of the user’s Communication ID.

The message is for information and audit purposes only.

A recovery record was deleted from the ATM transaction manager's database using the Online Services application. The Communication ID of the associated user is reported in an ATM087 message immediately after the ATM091 message.

The message is for information only.

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.

Refer to the explanation of the ATM136 message.

An invalid operator command was entered.

Issue the command correctly.

This message is issued during initialization of an ATM transaction manager when TMLOG=YES is specified or in response to a TM LOG command from the operator. Events will be logged in the ATMLOG1/2 datasets.

This message is for information only.

This message is issued in response to a TM NOLOG command from the operator. Events will not be logged in the ATMLOG1/2 datasets.

This message is for information only.

This message is issued in response to a TM LOG command from the operator. The transaction manager was started with TMLOG=NEVER, which means that logging to the ATMLOG1/2 datasets is not permitted.

If you need to run with logging active, specify a suitable TMLOG parameter and restart the transaction manager.

The operator entered the command TM END.

This message is for information only.

The operator entered the command TM HALT.

This message is for information only.

The transaction manager is in the process of closing down.

This message is for information only.

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”).

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.

ATM END operator command was issued, but the transaction manager could not close down because one or more global transactions were incomplete. The transaction manager will terminate as soon as the remaining incomplete transactions are resolved. In the meantime, this message will be re-issued at intervals of approximately 60 seconds.

Wait for the incomplete transactions to be resolved, or use the TM HALT command to cause the transaction manager to terminate immediately, leaving the incomplete transactions to be resolved the next time it is activated.

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.

Make more memory available to the database job and restart it.

This message is issued during transaction manager termination. Statistical messages follow.

This message is for information only.

This message is issued during transaction manager termination, or in response to a TM DSTAT operator command. Additional statistical messages (ATM114) follow.

This message is for information only.

This message is issued several times during transaction manager termination, or in response to a TM DSTAT operator command, once for each of several resources in the ATM nucleus. For each resource:

• item: identifies the ATM resource

• max-value (where shown): the maximum value permitted in this execution of the transaction manager

• high-water-mark: the highest value recorded

• hit-count: the number of times the high-water mark value has been reached

• time-of-first-hit: the date and time at which the current high-water mark was first reached, in the format YY/MM HH:MM

This message is for information only.

This message is issued during transaction manager termination, or in response to a TM DSTAT operator command. Additional statistical messages (ATM117) follow.

This message is for information only.

This message is issued several times during transaction manager termination, or in response to a TM DSTAT operator command, once for each statistical time range maintained by the transaction manager. These messages together present a table which is equivalent to the Transaction Times statistical display that is available in the Online Services application. Refer to the description of this display for further details.

This message is for information only.

This message is issued when the transaction manager's statistics are reset to zero, in response to a TM RSTAT operator command or an equivalent request from an Online Services user.

This message is for information only.

This message can be issued by a database for which the ADARUN parameter DTP=RM was specified, or by a SYSCO daemon. 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 a SYSCO daemon, 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.

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.

This message might be issued by a DTP=RM database that is initializing. The nucleus has signed on for distributed transaction processing with the local ATM transaction manager, the ID of which is “nodeid”. 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 DBID of the cluster, and begins, “NC dbid SIGNED ON …”.

This message is for information only.

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.

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.

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.

This message is for information only.

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.

This message is for information only.

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.

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.

This message is issued by a DTP=RM database that is initializing. The ATM Transaction Manager identified by “nodeid” is about to begin the process of signing the database nucleus on for distributed transaction processing. 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 DBID of the cluster, and begins, “NC dbid SIGNING ON …”.

This message is for information only.

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.

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.

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”).

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.

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”).

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.

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.

This message is followed by message ATM134, which gives more information about the error.

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”).

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.

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.

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.

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.

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.

An internal error occurred during the synchronization process that takes place during ATM restart when the CICS Resource Manager Interface is in use.

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.

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

This message is for information only.

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

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.

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.

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.

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.

This message is for information only.

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.

Use the Online Services application to specify the name of the System Coordinator Group in which the job will execute.

This message can be issued by ATM’s ET data migration utility, ATMPETD. It indicates failure of the utility, and the cause of failure.

The error message should be self-explanatory. For a more detailed explanation, note the condition code that was given when ATMPETD terminated, and refer to the Return Codes section of the description of the ET data migration utility.

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

If the cause of the error is not apparent from the description and content of the message, contact your Software AG support representative.

This message can appear during restart of an ATM transaction manager. It indicates that a transient error has occurred, such as the unavailability of the local Adabas System Coordinator daemon. The transaction manager will try to initialize again after a short period, during which time the cause of the failure might be rectified. The transaction manager will retry repeatedly, until it initializes successfully, or until it is terminated by operator command.

A previous message should indicate why the transaction manager could not initialize. Check for such a message and respond accordingly.

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

If the cause of the error is not apparent from the description and content of the message, contact your Software AG support representative.

This message indicates that an error occurred while deleting a Persistent Error Record. The message contains an ATM error code (err).

If the cause of the error is not apparent from the description and content of the message, contact your Software AG support representative.

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, subcode 77 is set.

If the cause of the error is not apparent from the description and content of the message, contact your Software AG support representative.

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, subcode 77 is set.

Define and create an MTR file, and restart the ATM transaction managers and clustered application environments in the COR group.

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

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.

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.

This message is for information only.

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.

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.

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.

This message is for information only.

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.

Restart the inactive Transaction Manager.