These Entire Net-Work system messages are identical to the corresponding ADAMnn messages documented in Adabas Messages and Codes documentation.
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 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:
|
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. |