ADAMnnn System Messages

The VM/ESA 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 VM level.

VM/ESA 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. "Type" specifies the machine (SOURCE or TARGET) that exceeded the MAXCON value.

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.

This message is preceded by message ADAM005. 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 "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 "link-name's" node.

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

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

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 VM System Programmer's Guide and 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.

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 Adabas technical support representative.

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 Smarts(APS) posting module ADAAPSPE has been loaded into the router. This is an acknowledgment that access to Smarts 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 Smarts (APS) posting module ADAAPSPE has been loaded into the router. This is an acknowledgement that access to Smarts 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 Smarts(APS) posting module ADAAPSPE has been loaded into the router. This is an acknowledgment that access to Smarts applications is now enabled.

None.

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 by "cause", which is one of the following:

INTERNAL ERROR

Keep all dumps, messages, and other related information and contact your Software AG support representative.

NUMBER CQES (NC PARM)

Specify an NC parameter value in the range 1 - 32767.

INVALID ID (DA PARM)

Specify a TARGETID or DATABASE parameter value in the range 1 - 65535.

LENGTH IUB (LU PARM)

Specify an LU parameter value in the range 1 - 65535.

NO ID TABLE

The ID table was not correctly initialized by ADASIP and/or ADASIR. For VM/CMS, this cause means the ID table manager virtual machine is not active.

Rerun ADASIP and/or ADASIR to correctly initialize the ID table.

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.

Do not specify the FORCE=YES ADARUN parameter unless it is absolutely certain that the ID table entry now active was left behind by a target that is no longer valid. If this problem continues, retain all related information and contact the Software AG support representative.

ID TABLE FULL

The system already holds the maximum allowed number of ID table entities that can be simultaneously active: databases, Entire Net-Work nodes, Entire System Server (Natural Process) nuclei, etc. 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.

Only one communicator/translator can be active at any one time.

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.

DUP ID ON NODE node-id

In Entire Net-work, target (database) IDs must be unique across all connected systems. Duplicate target IDs cannot be active on systems connected with Entire Net-Work.

Determine the conflicting targets having the specified node ID, and choose which is to be active under the specified ID.

NUMBER ATTBUFS (NA-PARM)

The attached buffer count (NA 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=resp-code

An unexpected response code resulted from the sign-on call to the Entire Net-Work communicator. This message can also occur when Entire Net-Work installation has not completed for some reason.

Refer to the Entire Net-Work documentation for a description of the response code "resp-code".

Either a system or nucleus abend activated the STAE abend routine. In VSE systems, the rightmost three digits of 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 Adabas nucleus abend codes.

(VSE systems only) The system abend code is the VSE Advanced Functions cancel code (refer to the IBM's VSE/AF Messages and Codes manual for the code meaning).

The message also displays the active program status word "psw", the work register contents, and the Adabas nucleus modules' entry points at the time of the abend. "psw" is the 16-character program status word, and has the following format:

nnnnnnnn nnnnnnnn

where the rightmost six or eight (ESA systems) characters contain the instruction address at the time of the abend.

(BS2000 systems only) The rightmost two digits of the first word in the "code" field show the STXIT interrupt code (refer to the manual Executive Supervisor Calls for code meanings).

The 16 register values "reg0-reg15" are the work register contents at the time of failure. The "ADANC" section shows the addresses "...(addr)" of the Adabas nucleus modules. The letters before the address value are abbreviations of the module name.

Modules that are not loaded have addresses of zero. All abend code, register, and addresses are shown in hexadecimal.

Adabas user abend 253 occurs after this message.

Refer to chapter 4 for a description of a nucleus abend, or to the appropriate operating system documentation for a description of the system abend that occurred.