ADAM* -- ADAMPM System Messages

The z/VM version being used is not supported by the Entire Net-Work IUCV driver.

The IUCV line driver cannot be opened.

Upgrade the system to the required z/VM level.

z/VM systems only: An IUCV connection between two virtual machines could not be made because either the initiating (source) or target virtual machine exceeded the MAXCON value in the machine's CP directory. The type of machine (SOURCE or TARGE) that exceeded the MAXCON value is given in the message.

Increase the appropriate MAXCON value and update the machine's CP directory.

Entire Net-Work was not able to sign on to IUCV because the virtual machine was not IUCV-authorized in the CP directory.

The IUCV line driver cannot be opened.

Add the required IUCV statements to the CP directory for the virtual machine.

The Entire Net-Work IUCV line driver attempted to receive or reply to a message that was not found in any IUCV message queue.

The IUCV line terminates Entire Net-Work abnormally.

Make note of the link "link-name", any related messages and dump listings, and call your Software AG technical support for assistance.

The specified function detected error err-num on the specified link and path.

This message is followed by message ADAM007. The IUCV line terminates Entire Net-Work abnormally.

Note the error number (err-num), the link (link-name) and any related messages, and call your Software AG technical support for assistance.

The IUCV SEND function detected error err-num on the specified link and path.

The IUCV line terminates Entire Net-Work abnormally.

Note the error number (err-num), the link (link-name), any related messages, and call your Software AG technical support for assistance.

This message occurs after an ADAM005 error, and is followed by a hexadecimal display of the failing IUCV parameter block.

The IUCV line terminates Entire Net-Work abnormally.

Retain the displayed information plus any other related error or dump information and contact your Entire Net-Work technical support representative.

Incoming messages on link link-name are being delayed due to insufficient buffer space.

Entire Net-Work suspends incoming data traffic until the buffer shortage is resolved.

Increase the short-term buffer size for a virtual machine running a non-paging guest operating system, or increase the page-fixed buffer size for a paging guest system virtual machine. Both buffers are controlled by the NODE statement parameters for the link-name's node.

Communication with the specified link is impaired by insufficient buffer space on that node. Message ADAM008 occurs on that node, advising of the problem.

The adjacent Entire Net-Work node suspends incoming data traffic until the buffer shortage is resolved.

Increase the short-term buffer size for a virtual machine running a non-paging guest operating system on the specified node, or increase the page-fixed buffer size for a paging guest system virtual machine. Both buffers are controlled by the NODE statement parameters for the link-name's node.

z/VSE systems only : An ADAMAF abend occurred. The variable message information is as follows:

This node could not accept a connection due to inadequate buffer space.

The IUCV path which was initiated is not connected.

Increase the short-term buffer size for a virtual machine running a non-paging guest operating system, or increase the page-fixed buffer size for a paging guest system virtual machine. Both buffers are controlled by the NODE statement parameters for the specified node.

This informational message advises that the condition causing previous impaired communications has been corrected.

A buffer shortage indicated by a message ADAM008 or ADAM009 has been resolved.

No action required. This message is for your information only.

A program check occurred while accessing an IUCV buffer area.

Entire Net-Work terminates operation with a dump.

Note the link "link-name", any related error or dump listing information, and call your Software AG technical support for assistance.

This normal termination message specifies the total number of SEND/REPLY (SEND 2WAY) and SEND 1WAY messages, as well as the counts of each type of SEND.

Entire Net-Work proceeds to terminate normally.

No action required. This message is for your information only. An excessive number of SEND 1WAYs maybe an indicator that the MSGLIM parameter value is insufficient.

This normal termination message specifies the total number of IUCV replies as well as the counts of replies containing data (non-null) and those without data (null).

Entire Net-Work proceeds to terminate normally.

No action required. This message is for your information only. An excessive number of null replies indicates the SEND 1WAY protocol is more suitable.

An incoming IUCV message from the link link-name was too long for the available buffer.

Entire Net-Work terminates operation with a dump.

Increase the short-term buffer pool size (specified by the NODE statement for the specified node ID).

An outgoing IUCV message was too large for the allocated buffer space.

Entire Net-Work terminates operation on this node with a dump.

Increase the short-term buffer pool size (specified by the NODE statement for this node ID).

The values specified by this node's and the partner node user-id's LINK statement MAXBLK parameters are not the same.

The IUCV path that was initiated is not connected.

Correct one of the LINK statement's MAXBLK values to agree with the other.

The maximum number of outstanding IUCV messages allowed was exceeded.

The IUCV line terminates abnormally.

Correct either the IUCV LINK statement's MSGLIM parameter value, or the CP directory MSGLIMIT value.

Entire Net-Work found no MAXBLK value on the IUCV LINK statement in a paging system where a maximum block size is required.

Entire Net-Work sets the block length to the page size "length".

No action is required for this informational message.

Entire Net-Work was unable to initialize the IUCV line driver in the guest operating system. The driver is not opened.

If the IUCV driver is the only driver specified, Entire Net-Work terminates operation on this node.

Note the error number ("err-num") and guest operating system level, and call your Software AG technical support for assistance.

A connection could not be made to another virtual machine. The error code "err-code" is returned by the operating system's IUCV interface; the IUCV code "code" is returned in the IPRCODE field of the IUCV parameter block. The value "code" can be one of the following IUCV CONNECT error codes:

IUCV codes 11 and 12 are two of the most common codes that can occur.

Ensure that the virtual machine at the other end of the link is logged on, active, and authorized to use IUCV. Refer to the appropriate operating system information for the meaning of "err-code", and the corrective action. For detailed IUCV and related code information, see IBM's z/VM System Programmer's Guide and z/VM System Facilities for Programming manuals.

The Entire Net-Work IUCV support routine was not able to save the status of an incoming IUCV interruption due to a lack of interrupt queue elements.

The IUCV link is disconnected.

Increase the value of the QSIZE parameter for NETSIR and rerun NETSIP with the REPLACE parameter

The IUCV driver has been closed either by an operator command or by SHUTDOWN processing.

No action is required for this informational message.

This normal termination message specifies the total number of SEND/REPLY (SEND2WAY) and SEND1WAY messages, as well as the counts of each type of SEND.

This normal termination message specifies the total number of IUCV replies as well as the counts of replies containing data (non-null) and those without data (null).

An incoming IUCV message from the specified link exceeded the length of the available buffer.

Entire Net-Work terminates with a dump.

Use the message blocking and/or compression options for the link (specified by the IUCV LINK statement), or increase the short-term buffer pool size (specified by the NODE statement for the specified node ID).

An outgoing IUCV message was too large for the allocated buffer space.

Entire Net-Work terminates operation on this node with a dump.

Use the message blocking and/or compression options for the specified link (specified by the IUCV LINK statement), or increase the short-term buffer pool size (specified by the NODE statement for this node ID).

The values specified by this node's and the partner node "user-id's" LINK statement MAXBLK parameters are not the same.

Correct one of the LINK statement's MAXBLK values to agree with the other.

The maximum number of outstanding IUCV messages allowed was exceeded.

Correct either the IUCV LINK statement's MSGLIM parameter value, or the CP directory OPTION MAXCONN value.

Entire Net-Work found no MAXBLK value on the IUCV LINK statement, and therefore has set the block length to the page size length.

Entire Net-Work was unable to initialize the IUCV line driver in the guest operating system. The driver is not opened.

If the IUCV driver is the only driver specified, Entire Net-Work terminates operation on this node.

Note the error number ("err-num") and guest operating system level, and call your Software AG technical support for assistance.

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:

ADAM76  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:

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

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.

BS2000 systems only: The BS2000 macro or function function issued the unexpected return code ret-code. Depending on the specified macro or function, information contains more error-specific information:

For the ENAMP function, if ret-code is 08...00, a common memory pool is already present and a new pool is being required. An attempt was most likely made to bring up an active nucleus again. Do not bring up the same nucleus twice for the same task if the ENAMP function was indicated.

The MP2LEVEL indication occurs when an incompatible reentrant router was loaded by another Adabas nucleus. Refer to the related BS2000 information for return code meanings and actions.

BS2000 systems only: The Adabas nucleus was cancelled while waiting for an event.

The nucleus terminates without giving control to termination recovery to reset the the DIB block. The user abend code is 233.

BS2000 systems only: The message text is explained as follows:

New IDT created,name=idt-name,GROUPS={YES | NO}

The reporting task created a new ID table idt-name located above the 16-MB limit with the attribute GROUPS=NO (global to the machine) or GROUPS=YES (in the scope of the user logon).

Connected to IDT idt-name,GROUPS={YES | NO}

The reporting task participates in the existing ID table idt-name located above the 16-MB limit with the attribute GROUPS=NO (global to the machine) or GROUPS=YES (in the scope of the user logon).

CMDQ/AB pool enabled, LOC=loc

The location of the command queue (CMDQ) pool is location loc" which is either "above" or "below".

Disconnected from IDT idt-name

The nucleus closed out its use of ID table idt-name. Another nucleus or user task is holding the ID table.

Disconnected from CMDQ/AB pool

The nucleus stopped processing, but the command queue (CMDQ) pool is still being held by a user task.

IDT disabled, Name=idt-name

CMDQ/AB pool disabled

The nucleus stopped processing, and no user task is using the command queue, which is removed from the system.

BS2000 systems only: An error occurred during the initialization of the IDT. Depending on the message text, the explanations are as follows:

ADARER is no BS2000 router

The load library does not contain a consistent router module (ADARER).

Wrong ADARER version vv expected: ee

The load library contains a router module (ADARER) from an earlier Adabas version where vv is the version level encountered and ee is the version level required.

RERPROG NE "RERBS2"
NOT AN XS ROUTER
NOT AN SMP ROUTER
ROUTER NOT AT OFFSET 0

A module containing the Adabas router (ADARER) was loaded, but it is not an SSF router of the required version.

Check the contents of the load library(s). Check load library assignments.

BS2000 systems only: An error occurred during connection to an existing IDT. Depending on the message text, the explanations are as follows:

ADARER is no BS2000 router

The IDT does not contain a consistent router module (ADARER). IDTNAME= specifies a memory pool other than an Adabas IDT.

Wrong ADARER version

The IDT contains a router module (ADARER) from an earlier Adabas version.

Check IDTNAME= parameters. Note that the first target coming up and initializing the IDT must have the latest Adabas version.

BS2000 systems only: An error occurred when attempting to connect to the IDT. A memory pool named by IDTNAME was found, but did not contain the expected structure. The message text is explained as follows:

RERPROG NE "RERBS2"

The ADARER program encountered was not the required RERBS2.

Router ID was xxxx,expected yyyy

The router ID encountered (xxxx) was not the router ID required (yyyy).

RERAIDT = ZERO
IDIDTID = WRONG VALUE
NOT AN SMP ROUTER

This message can occur when an Adabas nucleus of version 6.1.3 or above attempts to connect to a non-SMP router; that is, one that contains modules from Adabas version 6.1.2 or below.

Determine whether:

• the IDTNAME specifies an IDT at the appropriate version level.

• another target is using a DBID reserved for internal SMP purposes.

BS2000 systems only. This is an information message which states how many processors (n) are available on the computer on which the database ddddd is started.

None required.

BS2000 systems only: The specified SSF function encountered an unrecoverable condition.

Contact your Software AG technical support representative.

BS2000 systems only: This informational message identifies which IDT version (vv) is being accessed by the database (dbid) when started, its date of assembly (yyyymmdd) and the SM level (ssss).

No action is required for this informational message.

BS2000 systems only: This informational message identifies which zaps (zzzz) have been applied to the IDT accessed by the database (dbid) when started.

No action is required for this informational message.

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

The subtask terminates with Adabas user abend 252.

BS2000 systems only.

This isn't informational message. It states that the Software AG internal product software (APS) posting module ADAAPSPE has been loaded into the router. This is an acknowledgment that access to APS applications is now enabled.

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

BS2000 systems only. This is an information message. This states that the Software AG internal product software (APS) posting module ADAAPSPE has been loaded into the router. This is an acknowledgement that access to APS applications is now enabled.

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 cancelled; Adabas frees the command queue element (CQE) and alternate buffers. If a user program eventually issues a router 16-CALL, a response code 254 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.

BS2000 systems only. This is an information message stating that the Software AG internal product software (APS) posting module ADAAPSPE has been loaded into the router. This is an acknowledgment that access to APS applications is now enabled.

No action required for this informational message.

This message specifies the mode under which Adabas is running:

ASIDs are defined by cross-memory services. For more information regarding the use of ASCB/ASIDs by Adabas, refer to the Adabas Installation documentation section Requirements for Cross-Memory Services.

Ask the system operator to start the initiator.

When a nucleus with an active cross-memory environment ends, the entire address space including any initiator is also terminated, whether termination is normal or not. Refer to the Adabas Installation documentation section Requirements for Cross-Memory Services .

None required. This information is for your information only.

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 abend code (code) format is specific to your operating system:

• z/OS: 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.

• z/VSE: 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. System abend codes are documented as cancel codes in z/VSE/AF Messages and Codes. Adabas nucleus abend codes are described elsewhere in this documentation.

• BS2000: The rightmost byte shows the STXIT interrupt code. They are documented in the Executive Macros manual, under Task and Program Execution Control, STXIT Procedure with Contingency Processing.

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.