Version 8.1.4
 —  Messages and Codes  —

ADAI* - ADAIOR System Messages

Note:
Although not considered console messages, those preceded by an asterisk (*) are also displayed on the system console.

Overview of Messages

ADAI01 | ADAI02 | ADAI03 | ADAI04 | ADAI20 | ADAI21 | ADAI22 | ADAI23 | ADAI24 | ADAI26 | ADAI27 | ADAI29 | ADAI30 | ADAI31 | ADAI32 | ADAI40 | ADAI41 | ADAI42 | ADAI43 | ADAI44 | ADAI45 | ADAI46 | ADAI47 | ADAI48 | ADAI49 | ADAI50 | ADAI51 | ADAI53 | ADAI54 | ADAI55 | ADAI56 | ADAI57 | ADAI59 | ADAI60 | ADAI62 | ADAI63 | ADAI64 | ADAI65 | ADAI66 | ADAI67 | ADAI68 | ADAI69

ADAI01 data set count {READS | WRITES}
Explanation

The first form of the message is written when a sequential input data set is closed; the second form is written when a sequential output data set is closed.


ADAI02 GETMAIN stor-req (source)
GETMAIN stor-req stor-avail (source)
Explanation

The first form of the message is written whenever memory is dynamically acquired and the requested memory is available.

The second form of the message is written whenever memory is dynamically acquired and less than the requested memory is available.

In the messages, stor-req is the amount of memory requested, stor-avail is the amount of memory available, and source (printed only under z/VSE) is the source of the memory (GETVIS, COMREG, ADABUF).


ADAI03 { data set | physical-file-name } countr reads countw writes
Explanation

A direct access data set is closed. The physical-file-name indicates that the file was opened using dynamic allocation.


ADAI04 count errs count errs
Explanation

The message is written immediately following message ADAI03 when a direct access data set for which there had been read and/or write errors is closed.


ADAI20 dbid dataset physical-file-name DD: link-name
Explanation

An I/O error occurred on a file opened using dynamic allocation. This message appears immediately after the ADAI21 message.


ADAI21 dbid IO error RABN bad-rabn(start-rabn) OP oper CC ccbs CSW csw SNS dlu
Explanation

IBM platforms only. This message occurs on SYSLOG when ADAIOR finds a disk I/O error. The message variables and their meanings are:

Variable Description
dbid database ID (not provided in z/VSE environments)
bad-rabn the actual failing RABN
start-rabn the starting RABN of the failing I/O operation
oper
the type of operation being performed when the failure occurred as follows (in hex):
x'80' read
x'40' write
x'20' format
x'10' read/write to end of track
x'08' no write if read-only nucleus
ccbs communications bytes from the communications control block
csw channel status from the channel status word (CSW). If zero (0, the error was a physical check
dlu the z/VSE logical unit where the failure occurred

On z/OS systems, if an I/O error occurs on a VSAM data set, the CSW and SNS data is replaced by RPL feedback information.

This message is followed immediately by message ADAI20.

Action

Use the information provided by the message to locate a possible hardware failure. Keep the information and any dumps for later use.


ADAI22 ADAIOR Trace table: --> is current entry
Explanation

The ADAIOR trace table has been activated and printed.


ADAI23 dbid job-name abend code code
Explanation

z/VSE and BS2000 systems only. ADAIOR is asked to abend a job. A dump is normally also provided. The message values are:

dbid database ID
code the abend code (refer to the abend code descriptions in chapter 4).
job-name the z/VSE job name or BS2000 program name.

ADAI24 dbid Ready for operator communication
Explanation

SYSLOG displays this message once operator communications has been requested by the operator with the z/VSE MSG command. The value dbid is the database ID.

Action

Enter a valid Adabas command.


ADAI26 dbid job-name completion code code
Explanation

BS2000 systems: This message displays the normal termination return code. If a nonzero abend code is displayed, the BS2000 program task switch 10 is set on.

z/VSE systems: The end-of-job (EOJ) "RC=(RX)" sets the return code for the operating system. The message provides the database ID (dbid), job name, and return code.

Action

BS2000 systems: If job variables are installed, the abend code is passed to the controlling job variable. A job variable assigned with link "*ADA" is set with the following information:

program name (8 bytes) completion code (4 bytes) error number (5 bytes) Adabas response code (5 bytes)

z/VSE systems: For a nonzero abend code, refer to the description in chapter 4. If the DUMP option was specified, refer to the resulting dump, if needed, to determine the cause of the abend. The job step is terminated.


ADAI27 dbid Timer interval exceeds maximum allowed
dbid Reset to maximum
Explanation

A timer request was issued that exceeds the maximum allowed by the operating system.

Action

Reset the interval to the maximum allowed by your operating system.


ADAI29 Oper cmd: command
Explanation

z/OS, z/VSE, and BS2000 systems only: This message occurs in SYSLST as part of the session statistics during Adabas session termination. The value command is the operator command last entered from SYSLOG.


ADAI30 file-name number tracks formatted
Explanation

ADAIOR has completed formatting for a direct-access file.


ADAI31 dbid Opening tape file file-name SYSnnn=cuu
Explanation

This SYSLOG message means that a tape file was opened. Meanings of the message fields are:

dbid Adabas database
file-name filename of the input/output file opened
nnn z/VSE logical unit ID
cuu physical address of the selected drive

ADAI32 dbid Internal error - function func-name error error
Explanation

An internal error has occurred.

Action

Make a note of all recent messages, and contact your Adabas support representative.


ADAI40 dbid CP-operator was requested to mount volume vol-number on virt. unit unit-number
Explanation

z/VM systems: The virtual machine running Adabas database dbid has issued a request to mount tape vol-number on your virtual machine's unit unit-number.


ADAI41 dbid Mount required for volume vol-number on unit cuu and attach to VADDR address
Explanation

z/VM systems: The virtual machine running an Adabas database or utility has issued a request to mount tape vol-number on physical unit cuu and ATTACH the unit at address address. This message is sent to the CP operator.

Action

ATTACH the tape unit, if necessary, then mount the requested tape volume.


ADAI42 dbid volume vol-number for file file-name mounted on virt. unit addr compression
Explanation

z/VM systems: The requested tape mount of vol-number and file file-name on the virtual tape unit addr has been completed. If "(IDRC") appears at the end of the message instead of compression, the file is on a tape cassette with the IDRC feature active.

Action

None required. This message is for your information only. If the IDRC ending appears and the IDRC feature is not supported by the cassette unit, a later I/O error will occur.


ADAI43 dbid Requested DSN for file file-name not on volume vol-number
Explanation

z/VM systems: The data set name (DSN) for file file-name could not be found on the tape volume vol-number. The DSN is specified on the DATADEF statement.

Action

Verify and correct the DATADEF statement, ensure that the correct tape volume was mounted.


ADAI44 dbid Block count on EOV or EOF for file file-name NOT EQUAL TO I/O COUNT
Explanation

z/VM systems: The number of blocks read from tape does not match the block count in the end-of-file record. This is an internal error.

Action

Make a note of all related error information (message number and contents, plus any other related information), and advise your system support personnel. If necessary, contact your Software AG support representative.


ADAI45 dbid I/O error during dape handling for file file-name volume vol-number
Explanation

z/VM systems: A recurring I/O error occurred during the mount or label processing for tape file file-name on volume vol-number.

Action

Make a note of all related error information (message number and contents, plus any other related information), and advise your system support personnel. If necessary, contact your Software AG support representative.


ADAI46 dbid No virtual console
Explanation

z/VM systems: The DATADEF statement specified a virtual console as UNIT, but no virtual console exists.

Action

Correct the DATADEF statement, then rerun the job.


ADAI47 dbid Output tape file protected for file file-name volume vol-number
Explanation

z/VM systems: The tape mounted as an output tape has no file protect/write ring.

Action

Remove the mounted tape, install the file protect ring, then remount the tape.


ADAI48 dbid NO VALID VOLUME RECORD FOUND ON TAPE FOR FILE file-name
Explanation

z/VM systems: The requested tape mounted for file "file-name" has not been initialized properly. Either there were no records found on the tape, or the first record was not a VOL1 record. The tape will be unloaded and the operator prompted to mount a another tape.

Action

Initialize the tape using the CMS TAPE WVOL1 command.


ADAI49 dbid io-count Diagnose I/Os performed for file file-name
Explanation

z/VM systems: Temporary I/O errors for the direct access file file-name occurred. The value io-count is the number of successful retries.


ADAI50 dbid Sequential buffer allocation failed for file file-name
Explanation

z/VM systems: I/O buffers for the sequential file file-name could not be allocated because of a shortage of virtual storage in the virtual machine. The utility stops operation and issues a sequential open error.

Action

Increase the storage size of the virtual machine in the CP directory, and then log the machine on again. If a BUFNO parameter was specified in a DATADEF statement, increase that value.


ADAI51 dbid Adabas PAM BS2000 I/O error err-num in file file-name
RABN=error-rabn (start-rabn) OP=op-code ST=fecb
Explanation

BS2000 systems only: A PAM I/O error occurred on DASD file file-name. err-num is the ID1ECB contents from the BS2000 FCB. error-rabn is the RABN where the error occurred, and start-rabn the RABN where the operation began. op-code comprises one or more of the following operation code values:

X'80' READ read operation
X'40' WRITE write operation
X'20' FORMAT format operation
X'10' ENDOFTRK read or write to track end
X'08' RENOWRT no write if read-only nucleus

fecb is the FECB block status used for the I/O error, and comprises the SENSE, GERAETE (device), ABM and NPA fields. For more information, refer to the publication BS2000 DVS Disk Preparation .


ADAI53 dbid Adabas BS2000 I/O error err-num in file file-name
Explanation

BS2000 systems only: This is the first part of an I/O error message. The message is followed by message ADAI54. The err-num is a BS2000 error code. The file-name shows the link name for the failed data set.

Action

Use the "err-num" as an argument for the HELP command to get information about the failing function.


ADAI54 dbid Exit=value, status=fcb-status
Explanation

BS2000 systems only: The value is the error exit byte of the BS2000 FCB.

fcb-status is a six-byte status containing the following:

byte 0: device byte
bytes 1-3: sense bytes 1-3
byte 4: executive flag byte
byte 5: count of processed PAM pages

ADAI55 dbid SOLSIG error R15=ret-code, post-code=post-code
Explanation

BS2000 systems only: The system received an invalid return ret-code or post-code when issuing a SOLSIG "WAIT" supervisor call (SVC). dbid is the database ID.


ADAI56 dbid Unexpected RC ret-code from macro
Explanation

BS2000 systems only: The data set assigned to SYSDTA is either a non-SAM/V data set, or it contains records longer than 80 bytes. The value macro is RDATA.


ADAI57 dbid Unable to load ADAIOS
Explanation

An attempt to load ADAIOS failed. Check your LOADLIB and your partition sizes; either the partition is too small or the ADAIOS member is missing from the LOADLIB.


ADAI59 dbid Terminated with condiction code code
Explanation

This is a termination message issued by ADAIOR when a controlled end is reached. The code specifies a weighted termination condition. Return code "0" indicates a normal end. For more information about abend codes, review your other Adabas abend code documentation.


ADAI60 dbid PLOGMIR parameter ignored
dbid PLOG mirroring no longer supported
Explanation

The ADARUN parameter PLOGMIR is set to YES or RAP. This parameter setting is ignored as PLOG mirroring is no longer supported.


ADAI62 dbid Allocation error - type x retcode ret-code
dbid subcode subcode dataset physical-file-name
Explanation

An attempt to allocate a file dynamically failed. x indicates the request type: A (allocation); D (deallocation); or I (information retrieval). The ret-code and subcode display the error code returned from the operating system.

Action

Interpret the error code for your system and respond accordingly.


ADAI63 dbid Dataset physical-file-name is being opened
dbid In mode mode - RABN size rabn-size
Explanation

The data set specified is being opened using dynamic allocation in mode:

CKD ECKD the file resides on a storage control device that supports count key data (CKD) or extended count key data (ECKD) channel commands. ADAIOR generates channel programs accordingly.
VSAM PAGE (z/OS systems) the file is a VSAM relative record (RRDS) or linear (PAGE) data set.

ADAI64 dbid File file-name is being opened in mode mode - RABN size rabn-size
Explanation

The file specified is being opened in mode:

CKD ECKD the file resides on a storage control device that supports count key data (CKD) or extended count key data (ECKD) channel commands. ADAIOR generates channel programs accordingly.
VSAM PAGE (z/OS systems) the file is a VSAM relative record (RRDS) or linear (PAGE) data set.

ADAI65 dbid EXCPVR is [NOT] being used for this run [in ESA64 mode ]
Explanation

z/OS and z/VM systems only: If ADAIOR is loaded from an APF-authorized library concatenation, and ADARUN is linked with the SETCODE AC(1) statement, ADAIOR then performs the channel program translation/page fixing. If "NOT" appears in the message, ADAIOR will not perform channel program translation and page-fixing to improve the performance of I/O operations.

If EXCPVR is in use, and the operating system and processor support the allocation of real storage above the 2 gigabyte line, "in ESA64 mode" appears in the message.

Action

None required. This message is for your information only. If the message says that EXCPVR is not being used, but you have set up ADAIOR in an APF-authorized library and linked ADARUN with SETCODE AC(1) to use EXCPVR, refer to the Adabas Installation documentation for more information.


ADAI66 dbid ADAIO2 error-code message
Explanation

The error-code is the Fujitsu Technology Solutions macro return code. The message is one of the following produced by the database main task while attempting to start a subtask:

 
        ENABLING SUBTASK COM MEMORY
        ENABLING CONTINGENCY
        ENABLING WAIT
        ENTERING JOB
        GET PARAMETER MEMORY
        GET SUBMIT FILE
        OPENING SUBMIT FILE
        SET FILE LINK
        STXIT CALL ERROR
      

All errors are caused by system resource problems.

Action

Contact your Software AG technical support representative.


ADAI67 dbid ADAI2S error-code message
Explanation

The error-code is the Fujitsu Technology Solutions macro return code. The message is one of the following produced while attempting to start a subtask in the subtask startup module:

NO MOTHER TASK COMMON MEMORY

The memory pool containing data from the mother task is not accessible. The mother task has timed out or terminated.

NO ENABLE TO MOTHER'S EVENT

Mother task-to-subtask communication cannot be established. The mother task has probably terminated.

CANNOT SHARE MOTHER'S LOW MEMORY

The subtask parameter address area cannot be accessed.

CANNOT LOAD SUBTASK subtask-name

An error occurred while loading the subtask. Check the DDLIB and BLSLIBnn link names for libraries containing "subtask-name".

CANNOT POST MOTHER PROGRAM

Communication with the mother task is no longer possible. The mother task has probably terminated.

STXIT DEFINITION ERROR

A system error occurred while establishing the ESTAE(STXIT) exit for the subtask. Check the system resources.


ADAI68 dbid ADAIO2 message
Explanation

The message providing information about BS2000 subtasks is one of the following:

DISABLING SUBROUTINE subtask-number subtask-startname

The subtask with the number and startup name specified is being disabled.

SUBTASK POSTED RC: return-code

The subtask posted the specified return code.


ADAI68 dbid file-number VSAM file error - reason
Explanation

z/OS only: An error occurred attempting to open the VSAM file identified by file-number.

Action

All of the following reasons terminate the job with user abend 619.

UNABLE TO LOAD INFO ROUTINE
ERROR RETURNED FROM INFO ROUTINE
INVALID INPUT TO SUBROUTINE

Contact your Software AG technical support representative.

INVALID FILE TYPE (NOT RRDS OR LINEAR)

Redefine the VSAM file as either a relative record or linear data set.

EXTENTS NOT ON SAME DEVICE TYPE

Redefine all extents of the file on the same device type.


ADAI69 ADALNK is running in mode mode
Explanation

BS2000 only: ADALNK writes this message to tell you the mode it thinks it is running in where mode is one of the following:

BATCH/TIAM batch or Fujitsu Technology Solutions as carrier
UTM/3GL/AMS on UTM with an Assembler or 3rd generation language such as COBOL, C, FORTRAN, etc.
UTM/NATURAL on UTM running Natural

Note:
To suppress this message, set the B2CONFIG parameter in SSFB2C: LNKMSG=NO

Action:

No action is required for this informational message, although you can use this message for diagnosing errors.


Top of page