Version 7.4.4
 —  Messages and Codes  —

AITMnn-VM/ESA Transaction Monitor Interface Messages

Overview of Messages

AITM01 | AITM02 | AITM03 | AITM04 | AITM05 | AITM06 | AITM07 | AITM08 | AITM09 | AITM10 | AITM11 | AITM12 | AITM13 | AITM14 | AITM15 | AITM16 | AITM17 | AITM18 | AITM19 | AITM20 | AITM21 | AITM22 | AITM23 | AITM24 | AITM25 | AITM26 | AITM27 | AITM28 | AITM29 | AITM30

AITM01 ADAITM ABNORMALLY TERMINATED
Explanation

The background Adabas communications manager program ADAITM was unable to continue operation, perhaps because of a program error.


AITM02 I/O ERROR err-num WRITING ADAITM RESTART FILE
Explanation

The error "err-num" occurred while VM/ESA was writing the error recovery program ADAITM on the A-disk, preventing automatic restart from continuing. This message usually follows the ADAM80 message; however, "err-num" is not the original cause of the failure.


AITM03 I/O ERROR err-num READING ADAITM RESTART FILE
Explanation

The error "err-num" occurred while VM/ESA was restarting the system using the ADAITM RESTART program. This message usually follows message ADAM80; however, "err-num" is not necessarily the cause of the original failure.


AITM04 IUCV CONNECT ERROR err-num DURING ADAITM RESTART
Explanation

ADAITM was unable to reconnect to an active nuclei or user because of the CP internal communications (IUCV) error "err-num". This message usually follows error message ADAM80; however, "err-num" is not necessarily the cause of the ADAM80 message.


AITM05 HX COMMAND ENTERED DURING ADAITM EXECUTION
Explanation

The VM/ESA console operator entered a halt execution (HX) command, abnormally terminating ADAITM.


AITM06 RECURSIVE ERROR CONDITION ENCOUNTERED
Explanation

An error causing abnormal termination of ADAITM reoccurred during restart.


AITM07 TARGET-ID dbid action IN VMID vm-id CQH-FLAGS flags AT time
Explanation:

An event related to a target with the database ID of "dbid" occurred in the virtual machine "vm-id". "action" can be STARTed, ENDed, or ABENDed. This message appears only during an ADAITM event trace.


AITM08 COMMUNICATOR dbid action IN VMID vm-id AT time
Explanation

An event related to a communicator with the database ID of "dbid" occurred in the virtual machine "vm-id". "action" can be STARTed, ENDed, or ABENDed. This message appears only during an ADAITM event trace.


AITM09 USER vm-id action AT time
Explanation

An event related to a user with the database ID of "dbid" occurred in the virtual machine "vm-id". "action" can be STARTed, ENDed, or ABENDed. This message appears only during an ADAITM event trace.


AITM10 USER vm-id REQUESTED type TARGET-ID dbid IN vm-id AT time
Explanation

ADALNK issued a request for a virtual machine ID for a physical or logical target id of "dbid". If the target was active, the virtual machine ID "vm-id" is displayed. This message appears only during an ADAITM event trace.


AITM11 COMMAND NOT RECOGNIZED
Explanation

An operator command entered at the VM/ESA console was not understood by ADAITM.


AITM12 NO ACTIVE entity FOUND
Explanation

The VM/ESA console operator entered a LISTxxxx command to list all active entities, and none were found.


AITM13 type TARGET dbid ( target) ACTIVE IN VMID vm-id CQH-FLAGS flags IN VMID ON NODE node-name ON LINK link-name
Explanation

The Adabas nucleus or other local or remote target is active. Communication is through the virtual machine "vm-id" for local VM/ESA targets, or over the link to an Entire Net-Work communicator for remote targets. This message is in response to the ADAITM LISTTARG operator command entered from the VM/ESA console. "(target)" refers to the target type:


AITM14 USER PROGRAM ACTIVE IN VMID vm-id
Explanation

A user program has requested Adabas communication information from the virtual machine "vm-id". The program is not necessarily still active. This message is in response to an ADAITM LISTUSER operator command entered from the VM/ESA console.


AITM15 NODE node-name (target-id) TARGETS: target-ids
Explanation

An Entire Net-work node "node-name" and the target ID of (target-id) is communicating with the ID table manager. The list of targets active on the node ( target-ids ) follows. This message appears in response to an ADAITM LISTNODE operator command entered from the VM/ESA console, and accompanies the message AITM21.


AITM16 LOGGING NOT ACTIVE
Explanation

A LISTLOG or RESET VM/ESA operator command was entered, but event logging was not active.


AITM17 COMMAND command ACCEPTED
Explanation

A DISPON, DISPOFF, LOGON, or LOGOFF VM/ESA operator console command was entered.


AITM18 LOG IS CURRENTLY EMPTY
Explanation

The operator entered a LISTLOG command from the VM/ESA console, but the logging area was empty.


AITM19 LOG AREA HAS BEEN RESET
Explanation

A RESET operator command was issued at the VM/ESA console. The logging area pointer has been reset.


AITM20 LINK link-name TO NODE node-name STAT=status
Explanation

This message is a response to the ID table manager LINKLIST operator command. The Entire Net-Work link "link-name" connected to the node "node-name" has the current status of "status". The name of the link is set by the ID table manager to the VMID of the virtual machine running the Entire Net-Work node. The status values and meanings are:


AITM21 NODE node-name DIST distance VIA LINK link-name
Explanation

This message is a response to an ADAITM LISTNODE operator command. An Entire Net-Work node is now active and can be reached over the link "link-name". The distance in links is specified by "distance", and is the sum of the weight parameters specified along the path.


AITM22 NODE vm-id action AT time
Explanation

An event related to a node occurred in the virtual machine "vm-id". "action" can be CONNECTed, ABORTed, or REJECTed. This message appears only during an ADAITM event trace.


AITM23 REMOTE TARGET dbid (target) function ON NODE node-name AT time
Explanation

The ID table manager received an Entire Net-Work message saying that the target database "dbid" and the type target "(target)" either started or ended on the designated node " node-name" at the specified time.


AITM24 PROBE type dbid RECEIVED ON LINK link-name FROM NODE node-id AT time
Explanation

The ID table manager received an Entire Net-Work probe message. The message was issued by the node "node-id", and was either a probe for a target or for the node "type" on "dbid".


AITM25 NODE ADDRESS CONSTANTS COULD NOT BE RESOLVED, INCOMPATIBLE VERSIONS
Explanation

The ID table manager (ADAITM) and Entire Net-Work component for VM/ESA (NETITM) versions are incompatible. The ID table manager terminated abnormally (abended).


AITM26 NODE NO RESTART OPTION SPECIFIED, ID-TABLE MACHINE LOGGED OFF
Explanation

The ID table manager received a program check, and the restart option was not specified. The ID table manager terminated abnormally (abended) and automatically also terminated all VM/ESA nuclei by logging itself off.


AITM27 LINK link-name SEVERED DUE TO MESSAGE LIMIT OVERFLOW
Explanation

An Entire Net-Work message intended for an adjacent node over the link "link-name" could not be transmitted because the maximum number of pending messages for the IUCV path was exceeded. The system breaks the link.


AITM28 NO ERROR MESSAGES AVAILABLE
Explanation

No Entire Net-Work messages are available to be displayed; the NETITM MSGS file is empty.


AITM29 FSREAD ERROR fs-code READING ERROR MESSAGE FILE
Explanation

The error code "fs-code" was returned by VM/ESA file services while attempting to read the NETITM MSGS file. The LISTMSG operator command is terminated.


AITM30 NODE node-name IN VMID vm-id DEACTIVATED PATH, TID target-id AT time
Explanation

An Adabas command to the remote node "node-name" was rerouted because the original path chosen by the ID table manager no longer led to the required target "target-id" .


Top of page