NETM* - ADAMPM Messages

These Entire Net-Work system messages are identical to the corresponding ADAMnn messages documented in Adabas Messages and Codes documentation.

Overview of Messages

NETM91 | NETM92 | NETM93 | NETM98 | NETM99
NETM91 nodeid target USER GONE JOB jobname USER ID hexuserid
Explanation

Entire Net-Work tried to process a user call, but the addressed data area was not addressable, or no longer contained recognizable data. This message occurred while Entire Net-Work was receiving the command (Router 08-CALL processing).

Action

The program was apparently canceled after issuing an Entire Net-Work command (Router- 04-CALL), perhaps due to a communication delay or timeout. Ending, abending, or canceling of the program should be avoided, if possible.

NETM92 nodeid target USER GONE JOB jobname USER ID hexuserid
Explanation

Entire Net-Work tried to process a user call, but the addressed data area was not addressable, or no longer contained recognizable data. This message occurred while Entire Net-Work was posting the user after command completion (Router 12-CALL processing).

Action

The program was apparently canceled after issuing an Entire Net-Work command (Router 04-CALL), perhaps due to a communication delay or timeout. Ending, abending, or canceling of the program should be avoided, if possible.

NETM93 nodeid target USER GONE JOB jobname USER ID hexuserid
Explanation

The user's program exceeded the ADARUN CT time allowed without receiving the results of an Adabas Call (performing Router 16-CALL processing). This could be caused by processing delays caused by an overloaded system or network, low priority, or teleprocessing delays. Adabas assumes that the user program has been canceled; Adabas frees the Command Queue Element (CQE) and alternate buffers.

Action

Consider increasing the ADARUN CT time, or otherwise increase the resources for the user program. Avoid canceling or ending the user program, if this was done. If a user program eventually issues a Router 16-CALL, a response code 254 (ADARSP254) also occurs.

NETM98 nodeid TARGET INITIALIZATION ERROR: cause
Explanation

ADAMPM was unable to establish interregion communication for the reason specified by cause, which is one of the following:

Cause User Action
INTERNAL ERROR Keep all dumps, messages, and other related information and contact your Software AG technical support representative.
NUMBER CQES (NC PARM) Specify an NC parameter value between 1 and 32767.
INVALID ID (DA PARM) Specify a TARGETID or DATABASE parameter value ranging 1 through 65535.
LENGTH IUB (LU PARM) Specify an LU parameter value ranging 1 through 65535.
NO ID TABLE The ID Table was not correctly initialized by ADASIP and/or ADASIR, which must be rerun.
DUPLICATE ID (LOCAL) The ID Table already contains an active entry for the target ID (database ID) specified. Multiple targets with the same ID are not allowed. Choose which of the two targets should be active and if necessary, end the currently active target and restart the job for the other target.
ID TABLE FULL The system already holds the maximum allowed number of ID Table entries (databases, Entire Net-Work nodes, Natural PROCESS nuclei, and so on) that can be simultaneously active. This maximum is set during ID Table initialization; the default is 10. Either terminate one of the active targets and restart the job, or end all active targets and reinitialize the ID Table with a larger size (using ADASIP or by re-IPLing the system).
DUPL. COMMUNIC./TRANSL. No more than one communicator and no more than one translator can be active simultaneously. Correct the problem and rerun the job.
NO COMMON MEMORY CQ/AB The necessary common storage space for the Command Queue (CQ) and/or the Attached Buffer pool is not available. Either specify a smaller buffer requirement if possible, or re-IPL the system to free lost common storage.
CQ/AB KEYS INCOMPATIBLE The service's CQ and AB pool were not acquired with the correct attributes. Verify that the execution libraries are correct. If you are unable to resolve the error, contact your Software AG support representative.
DUP ID ON NODE nodeid In Entire Net-Work, target (database) IDs must be unique across all connected systems. Determine the conflicting targets having the specified node ID, and choose which is to be active under the specified ID. Duplicate target IDs cannot be active on systems connected with Entire Net-Work.
NUMBER ATTBUFS (NA-PARM) The Attached Buffer count ('NAB' parameter in ADARUN) was either not specified or specified as zero, or the requested space is unavailable. Either correct the parameter or increase the region size. Restart the job.
COMMUNICATOR RSP=code An unexpected response code resulted from the sign-on call to the Entire Net-Work communicator. Refer to the Adabas documentation for a description of the response code. This message can also occur when the Adabas installation has not been completed for some reason.

NETM99 nodeid Entire Net-Work ABEND CODE code PSW psw xxxxxxxx . . . . xxxxxxxx (R0-7) xxxxxxxx . . . . xxxxxxxx (R8-F)
Explanation

Either a system or Entire Net-Work abend activated the abnormal termination routine. In MVS systems, the rightmost three digits of operating system abend codes are zeros. The system abend code is then quoted as the value formed by the next three digits to the left (00ccc000). Abend codes contained in the rightmost three digits (00000ccc) are Entire Net-Work abend codes. Note that system abend codes are usually quoted in hexadecimal; user abend codes (Entire Net-Work), although displayed here in hexadecimal, are usually quoted in decimal (this is also true for the 'abend code' section of this manual).

The message also displays the active program status word (psw) and the work register contents at the time of the abend. psw is the 16-character program status word and has the following format: 

xxxxxxxx xxxxxxxx

where the rightmost six, or eight (XA systems) characters contain the instruction address at the time of the abend. The 16 register values (reg0 - regF) are the work register contents at the time of failure.