ADAM* -- ADAMPM System Messages

#### Search Results

Search

# ADAM* -- ADAMPM System Messages

### Overview of Messages

`ADAM001 | ADAM002 | ADAM003 | ADAM004 | ADAM005 | ADAM006 | ADAM007 | ADAM008 | ADAM009 | ADAM01 | ADAM010 | ADAM011 | ADAM012 | ADAM013 | ADAM014 | ADAM015 | ADAM016 | ADAM017 | ADAM018 | ADAM019 | ADAM020 | ADAM021 | ADAM022 | ADAM025I | ADAM13 | ADAM14 | ADAM15 | ADAM16 | ADAM17 | ADAM18 | ADAM19 | ADAM20 | ADAM75 | ADAM76 | ADAM77 | ADAM78 | ADAM79 | ADAM81 | ADAM82 | ADAM83 | ADAM86 | ADAM88 | ADAM8B | ADAM8C | ADAM90 | ADAM91 | ADAM92 | ADAM93 | ADAM94 | ADAM96 | ADAM97 | ADAM98 | ADAM99 | ADAML1`

ADAM001 | VM/System product release level under 3 - not supported
Explanation | The z/VM version being used is not supported by the Entire Net-Work IUCV driver. The IUCV line driver cannot be opened.
Action: | Upgrade the system to the required z/VM level.

ADAM002 | Line driver maximum number of connections exceeded on type machine
Explanation | 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 TARGET) that exceeded the MAXCON value is given in the message.
Action | Increase the appropriate MAXCON value and update the machine's CP directory.

ADAM003 | No IUCV authorization found
Explanation | 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.
Action: | Add the required IUCV statements to the CP directory for the virtual machine.

ADAM004 | No IUCV message found on link link-name
Explanation | 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.
Action: | Make note of the link "link-name", any related messages and dump listings, and call your Software AG technical support for assistance.

ADAM005 | IUCV function function error err-num on link link-name on path-ID path
Explanation | 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.
Action: | Note the error number (err-num), the link (link-name) and any related messages, and call your Software AG technical support for assistance.

ADAM006 | IUCV send completion error err-num onlink link-name path-ID path
Explanation | The IUCV SEND function detected error err-num on the specified link and path. The IUCV line terminates Entire Net-Work abnormally.
Action: | Note the error number (err-num), the link (link-name), any related messages, and call your Software AG technical support for assistance.

ADAM007 | IUCV parameter block at location location
Explanation | 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.
Action: | Retain the displayed information plus any other related error or dump information and contact your Entire Net-Work technical support representative.

ADAM008 | Incoming traffic impaired on link link-name due to buffer shortage
Explanation | 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.
Action: | 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.

ADAM009 | Communications impaired to link link-name
Explanation | 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.
Action: | 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.

ADAM01 | version job-name abend code code
Explanation | z/VSE systems only : An ADAMAF abend occurred. The variable message information is as follows:
version | Adabas version
job-name | the z/VSE job name
code | the abend code

ADAM010 | Pending connection rejected due to buffer shortage
Explanation | This node could not accept a connection due to inadequate buffer space. The IUCV path which was initiated is not connected.
Action: | 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.

ADAM011 | Normal communications resumed to link link-name
Explanation | 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.
Action: | No action required. This message is for your information only.

ADAM012 | Buffer program check on link link-name
Explanation | A program check occurred while accessing an IUCV buffer area. Entire Net-Work terminates operation with a dump.
Action: | Note the link "link-name", any related error or dump listing information, and call your Software AG technical support for assistance.

ADAM013 | number number of sends 2way count-a 1way count-b
Explanation | 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.
Action: | 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.

ADAM014 | number number of replies non-null count-a null count-b
Explanation | 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.
Action | No action required. This message is for your information only. An excessive number of null replies indicates the SEND 1WAY protocol is more suitable.

ADAM015 | Incoming message exceeds buffer length on link link-name
Explanation | An incoming IUCV message from the link link-name was too long for the available buffer. Entire Net-Work terminates operation with a dump.
Action: | Increase the short-term buffer pool size (specified by the NODE statement for the specified node ID).

ADAM016 | Outgoing message exceeds buffer length on link link-name
Explanation | An outgoing IUCV message was too large for the allocated buffer space. Entire Net-Work terminates operation on this node with a dump.
Action: | Increase the short-term buffer pool size (specified by the NODE statement for this node ID).

ADAM017 | Connection to user user-id denied due to block length conflict
Explanation | 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.
Action: | Correct one of the LINK statement's MAXBLK values to agree with the other.

ADAM018 | Message limit on path to VMID vm-id INSUFFICIENT
Explanation | The maximum number of outstanding IUCV messages allowed was exceeded. The IUCV line terminates abnormally.
Action: | Correct either the IUCV LINK statement's MSGLIM parameter value, or the CP directory MSGLIMIT value.

ADAM019 | Maximum block length set to length
Explanation | 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".
Action | No action is required for this informational message.

ADAM020 | Initialization error err-num for guest system IUCV support
Explanation | 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.
Action: | Note the error number ("err-num") and guest operating system level, and call your Software AG technical support for assistance.

ADAM021 | Link link-name not connected error err-code IUCV-code code
Explanation | 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:
11 | Target communicator not logged on.
12 | Target communicator has not invoked the DECLARE BUFFER function.
13 | The maximum number or connections for this virtual machine has been exceeded.
14 | The maximum number or connections for the target virtual machine has been exceeded.
IUCV codes 11 and 12 are two of the most common codes that can occur.
Action: | 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.

ADAM022 | Path to VMID vm-id disconnected due to interrupt queue shortage
Explanation | 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.
Action: | Increase the value of the QSIZE parameter for NETSIR and rerun NETSIP with the REPLACE parameter

ADAM025I | IUCV driver manually closed
Explanation | The IUCV driver has been closed either by an operator command or by SHUTDOWN processing.
Action | No action is required for this informational message.

ADAM13 | number number of sends 2way count-a 1way count-b
Explanation | 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.

ADAM14 | number number of replies non-null count-a null count-b
Explanation | 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).

ADAM15 | Incoming message exceeds buffer length on link link-id
Explanation | An incoming IUCV message from the specified link exceeded the length of the available buffer. Entire Net-Work terminates with a dump.
Action: | 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).

ADAM16 | Outgoing message exceeds buffer length on link link-id
Explanation | An outgoing IUCV message was too large for the allocated buffer space. Entire Net-Work terminates operation on this node with a dump.
Action: | 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).

ADAM17 | Connection to user user-id denied due to block length conflict
Explanation | The values specified by this node's and the partner node "user-id's" LINK statement MAXBLK parameters are not the same.
Action: | Correct one of the LINK statement's MAXBLK values to agree with the other.

ADAM18 | Message limit on path to VMID vm-id insufficient
Explanation | The maximum number of outstanding IUCV messages allowed was exceeded.
Action: | Correct either the IUCV LINK statement's MSGLIM parameter value, or the CP directory OPTION MAXCONN value.

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

ADAM20 | Initialization error err-num for guest system IUCV support
Explanation | 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.
Action: | Note the error number ("err-num") and guest operating system level, and call your Software AG technical support for assistance.

ADAM75 | SVCDUMP busy
Explanation | 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.
Action | No action is required for this informational message.

ADAM76 | Communicator unusable, remote access not possible
Explanation | 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.
Action | 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.

ADAM77 | SVCDUMP ignored - not authorized
Explanation | 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.
Action | No action is required for this information message.

ADAM78 | SVCDUMP {SDUMP|TDUMP} failed RC rc/rsn
Explanation | 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.
Action | No action is required for this information message.

ADAM79 | SVCDUMP {SDUMP|TDUMP} written RC rc/rsn
Explanation | 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.
Action | No action is required for this information message.

ADAM81 | dbid unexpected return code ret-code information in MACRNAME, macro-name
Explanation | BS2000 systems only: The BS2000 macro macro-name issued the unexpected return code ret-code. Depending on the specified macro, information contains more error-specific information:
Macro (macro-name) | Information (information)
--- | ---
ENAEI | task sequence number (tttt) of target hard post ID (ADAtttt) to enable
ENQAR | Identification table memory pool name (IDTNAME) used as lock ID
DISEI | task sequence number (tttt) of target hard post ID (ADAtttt) to disable
DISMP/CQ | task sequence number of command queue common memory to disable
POSSIG | task sequence number (tttt) of target hard post ID (ADAtttt)
ENAMP | command queue pool name. If the return code (ret-code) is "08...00", a common memory pool is already present, but it must be new
REQMP | command queue pool name where memory could not be obtained
STXIT | the nucleus except exit
Action: | For the ENAMP function, if ret-code is 08...00, a common memory pool is already present and a new pool is required. An attempt was 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. For the ENQAR/REQMP function, check the IDTNAME used in ADARUN, SSFB2C, or DDLNKPAR. For ENAEI, DISEI, DISMP/CQ, and POSSIG, the task sequence numbers are those of the command queue memory post to be accessed. Check the tasks and matching IDs in your system with SHOW-USER-STATUS or in the utility program IDTLOOK. The STXIT, contact your Software AG technical support representative. Note: <ret-code> is described in the BS2000 System Macros Manual for the macro mentioned.

ADAM82 | dbid Adabas canceled in bourse wait
Explanation | BS2000 systems only: The Adabas nucleus was canceled while waiting for an event. The nucleus terminates without giving control to termination recovery to reset the DIB block. The user abend code is 233.

ADAM83 | dbid text
Explanation | 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.

ADAM86 | dbid IDT CONN ERROR : text
Explanation | 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 possible message texts (text) are explained in the following table.
Message text | Explanation | Action
--- | --- | ---
wrong ADARER version nn expected mm | The router is an older version than the caller. | Bring the whole system down and start the first nucleus/server with the newest version to allocate and fill the ID table with its version.
SMPSVC (router extension) not loaded | An attempt to allocate a new identification table (IDT) memory pool failed to load the SMPSVC module. | Check that the executable SMPSVC is present in one of the libraries in the DDLIB/BLSLIB library load stack.
DBID already in use by SMP cluster | An attempt has been made to start a nucleus with a DBID that clashes with an Adabas Parallel Services cluster. | Use another DBID for the nucleus or start it on another IDTNAME.
IDIDTID = wrong value | The start of the identification table (IDT) does not have the expected eyecatcher (IDIDTID) of "ADABAS51". | Bring the whole system down and start the first nucleus/server again to make a clean IDT.
ADARER is not a BS2000 router | The start of the identification table (IDT) memory pool contains the BS2000 Adabas router. The eyecatcher for this (RERBS2) has not been detected. | Check the value of the IDTNAME parameter in ADARUN or in DDLNKPAR. Otherwise, bring the whole system down.

ADAM88 | ddddd Processor(s) = n
Explanation | 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.
Action: | None required.

ADAM8B | dbidIDT Version vv date yyyymmdd SP ssss
Explanation | 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 SP level (ssss).
Action: | No action is required for this informational message.

ADAM8C | dbid Router Zaps Applied: zzzz zzzz zzzz zzzz zzzz zzzz zzzz
Explanation | BS2000 systems only: This informational message identifies which zaps (zzzz) have been applied to the IDT accessed by the database (dbid) when started.
Action: | No action is required for this informational message.

ADAM90 | dbid Adabas subtask abend code code PSW password reg0 reg1 reg2 reg3 (R0-R3) reg4 reg5 reg6 reg7 (R4-R7) reg8 reg9 reg10 reg11 (R8-RB) reg12 reg13 reg14 reg15 (RC-RF)
Explanation | 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.

ADAM91 | dbid target user gone job job-name user ID hex-user-id
Explanation | 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.
Action: | Avoid ending, abending, or cancelling the program, if possible.

ADAM92 | dbid target user gone job job-name user ID hex-user-id
Explanation | 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.
Action: | Avoid ending, abending, or cancelling the program, if possible.

ADAM93 | dbid target User gone job job-name user ID hex-user-id
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. If a user program eventually issues a router 16-CALL, a response code 254 (ADARSP254) also occurs.
Action: | 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.

ADAM94 | dddd Post Module ADAASPE loaded
Explanation | 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.
Action | No action required for this informational message.

ADAM96 | dbid MPM running in XAE-mode-type mode under Vv dbid MPM running in ops - mode-type mode under level
Explanation | This message specifies the mode under which Adabas is running:
ops | z/VSE operating system type, either "370" or "ESA"
v | the z/VSE version
mode-type | SHARED NON-SHARED NON-SPECIFIED
level | the operating system level

ADAM97 | dbid Terminating, no longer accepting commands
Explanation | The database identified in the message is terminating and no longer accepting commands.
Action: | No action is necessary for this informational message.

ADAM98 | dbid Target initialization error: cause
Explanation | ADAMPM was unable to establish interregion communication for the reason specified in the message (cause), which is one of the following:
Cause | Action
--- | ---
Communicator response code rsp | 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 rsp.
CQ/AB incorrect key | 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.
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 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.
DUPL. COMMUNIC./TRANSL. | Only one communicator/translator can be active at any one time. Correct the problem and rerun the job.
Duplicate target ID (DBID) | 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).
Incompatible SVC version | ADASVC must be at the same or later release as ADAMPM. Verify that the SVC and the execution libraries are correct.
Internal error | Keep all dumps, messages, and other related information and contact your Software AG support representative.
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 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.
No ID table | The ID table was not correctly initialized by ADASIP and/or ADASIR. For z/VM, this cause means the ID table manager virtual machine is not active. Rerun ADASIP and/or ADASIR to correctly initialize the ID table.
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.
Number CQES (NC parm) | Specify an NC parameter value in the range 1 - 32767.

ADAM99 | dbid ADABAS ABEND CODE code error-environment-information
Explanation | 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 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
Action: | 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 | Percentage of PREFTBL used pct Number of calls to ADAMLF callcount Number of cmds to ADABAS cmdcount1 Number of cmds returned from ADAMLF cmdcount2 Number of over reads count
Explanation | 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.
Message | Description
--- | ---
Percentage of PREFTBL used pct | The percentage of the ADARUN parameter PREFSTBL used for this execution.
Number of calls to ADAMLF callcount | The number of times that ADAMLF was entered.
Number of cmds to ADABAS cmdcount1 | The total number of commands that were passed to Adabas for this execution.
Number of cmds returned from ADAMLF cmdcount2 | The number of commands that were returned from the ADAMLF buffers.
Number of over reads count | The number of records that were prefetched that were not passed back to the caller.
Action | No action is required for these informational messages.