ADAM* -- ADAMPM System Messages

A request to write an SVC dump has failed due to a busy condition. This indicatest that the system service is active processing another SVC dump request. If the busy condition is returned from the first attempt to write to SVCDUMP. the following message is issued:

ADAM75  SVCDUMP busy - retry ever 05 sec for 15 min

In this case, the SVC dump requrest will be retried as indicated in the message.

If the busy condition persists for the maximum time permitted, the following messages are issued and no further retries are attempted:

ADAM75  SVCDUMP busy - dump not written
ADAM78 SVCDUMP SDUMP FAILED RC rc/sc

Dump processing then continues as if the SVCDUMP DD statement had not been specified.

No action is required for this informational message.

This message usually follows message ADAM98. The Communicator or Entire Net-Work cannot receive the initialization feed call. This extra message warns the operator that there is something wrong with the communicator. The database will start normally. If the MPM node is a translator or communicator, this node will go down.

Do not restart the database until the problems in the Communicator or Entire Net-Work have been resolved.

The operator command NWCONNECT may be used to retry establishing the Entire Net-Work DBID target. This command is not available if Adabas Cluster Services or Adabas Parallel Services is being used.

An SVC dump (//SVCDUMP DD) was attempted, but the job is not running with APF authorization. APF authorization is required for an SVC dump.

Dump processing continues as if the SVCDUMP DD statement had not been specified.

No action is required for this information message.

The SVC dump failed. The return code (rc) and reason code (rsn) from the IBM SDUMP macro or IBM IEATDUMP macro are given in the message.

No action is required for this information message.

The SVC dump was written. The return code (rc) and reason code (rsn) from the IBM SDUMP macro or IBM IEATDUMP macro are given in the message or are suppressed if the return code is zero.

No action is required for this information message.

An Adabas subtask abend occurred. The abend code, password, and register information is in the same format as the ADAM99 message.

The subtask terminates with Adabas user abend 252.

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

The program was apparently canceled after issuing an Adabas command (router 04-CALL), perhaps due to a communication delay or timeout.

Avoid ending, abending, or cancelling the program, if possible.

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

The program was apparently canceled after issuing an Adabas command (router 04-CALL), perhaps due to a communication delay or timeout.

Avoid ending, abending, or cancelling the program, if possible.

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. If a user program eventually issues a router 16-CALL, a response code 254 (ADARSP254) also occurs.

Consider increasing the ADARUN CT time, or otherwise increase the resources for the user program. Avoid cancelling or ending the user program, if this was done.

The database identified in the message is terminating and no longer accepting commands.

No action is necessary for this informational message.

ADAMPM was unable to establish interregion communication for the reason specified in the message (cause), which is one of the following:

The nucleus ended abnormally. This is the result of an error detected by Adabas (user abend code) or by the operating system (system abend code). All abend code values are given in hexadecimal notation.

The first four bytes of the abend code are in the form xxsssuuu. The system abend code is specified by sss and the user abend code (the Adabas nucleus abend code) by uuu. Some system abend codes also provide a four-byte reason code. System abend and reason codes are documented in z/OS MVS System Codes. Adabas nucleus abend codes are described elsewhere in this documentation.

Additional error environment information follows the abend code in the message text, in the following order:

• PSW: The eight-byte program status word. The rightmost four bytes are the instruction address at the time of the abend.

• EC Info: Eight bytes of additional z/OS extended control mode information, such as the instruction length code, the interrupt code, and the virtual address causing a translation exception. Refer to the IBM documentation for SDWA fields SDWAAEC1 and SDWATRAN for more details.

• R0 - R15: Contents of the general purpose registers. Each register is either four or eight bytes, depending on whether the hardware and operating system support eight-byte registers.

• AR0 - AR15: Contents of the access registers.

• The load addresses of various nucleus modules and user exits.

The following is an example of an ADAM99 message produced when a z/OS nucleus was canceled:

ADAM99 00226 ADABAS   Abend code 40222000 00000000
078D1000 8001EC02 00020001 00000000 (PSW, EC Info)
00000000_00000001 00000000_FFFBC5F8 (R0-R1)       
00000000_00043A08 00000000_001651A0 (R2-R3)       
00000000_00000000 00000000_00009C9A (R4-R5)       
00000000_246FA940 00000000_0014D6EC (R6-R7)       
00000000_0014D6EC 00000000_0005A988 (R8-R9)       
00000000_0001EBA8 00000000_00056000 (R10-R11)     
00000000_800109E0 00000000_000129D0 (R12-R13)     
00000000_8001EBD4 00000000_808D6C68 (R14-R15)     
00000000 00000000 00000000 00000000 (AR0-AR3)     
00000000 00000000 00000000 00000000 (AR4-AR7)     
00000000 00000000 00000000 00000000 (AR8-AR11)    
00000000 00000000 00000000 00000000 (AR12-AR15)
                                                  
 ADARUN 00007A60 ADALNK 800456C0 ADAMOD 80044100 ADAMIM 80054000 
 ADARVU 8004CEB8 ADACLX 80051000 ADARMT 80053100 ADAMSG 8004A000 
 ADAIOR 800109E0 ADAIOS 80015A18 ADANC0 00055000 ADANC1 0005A800 
 ADANC2 00068000 ADANC3 0008C400 ADANC4 000A0800 ADANC5 000B4400 
 ADANC6 000C7800 ADANC7 000DBC00 ADANC8 000F4400 ADANC9 0010B000 
 ADANCA 00113400 ADANCB 00123000 ADANCC 00127D00 ADALOG 00135998 
 ADAMPM 8013C430 ADARAC 8013FF30 ADAMGR 801464F8 ADAMGI 8014AF00 

Refer to your Adabas documentation for a description of a nucleus user abend, or to the appropriate operating system documentation for a description of the system abend.

ADAML1 messages list statistics that are printed when a CL command is issued and the ADARUN PREFETCH and PREFSTDD parameters are set. The following table describes each message.

No action is required for these informational messages.