ADAInn System Messages

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

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 VSE) is the source of the memory (GETVIS, COMREG, ADABUF).

A direct access dataset is closed. 'physical-file-name' indicates that the file was opened using dynamic allocation.

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

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

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

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

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

The ADAIOR trace table has been activated and printed.

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

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

Enter a valid Adabas command.

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.

VSE/ESA 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.

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)

VSE/ESA 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.

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

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

OS/390, z/OS, VSE/ESA, 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.

ADAIOR has completed formatting for a direct-access file.

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

An internal error has occurred.

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

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

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

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

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

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.

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

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

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

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.

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

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.

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

Correct the DATADEF statement, then rerun the job.

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

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

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

Initialize the tape using the CMS TAPE WVOL1 command.

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

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

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.

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:

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

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.

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

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

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

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.

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

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 other abend codes, see chapter 4.

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

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

Interpret the error code for your system and respond accordingly.

The dataset specified is being opened using dynamic allocation in "mode"

The file specified is being opened in "mode"

z/OS, OS/390, z/VM, and VM/ESA 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.

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.

The "error-code" is the Siemens 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.

Contact your Software AG technical support representative.

The "error-code" is the Siemens macro return code. The "message" is one of the following produced while attempting to start a subtask in the subtask start-up 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.

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

DISABLING SUBROUTINE subtask-number subtask-startname

The subtask with the number and start-up name specified is being disabled.

SUBTASK POSTED RC: return-code

The subtask posted the specified return code.

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

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

EXTENTS NOT ON SAME DEVICE TYPE

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

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

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

Use for diagnosing errors.