ADAI* - ADAIOR System Messages

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.

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

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

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.

Note:
This message is available in z/OS systems only.

This message is written at data set close following message ADAI03 when a direct access data set has used zHPF channel programs for reads or writes.

This message is only generated when the zHPF read and write counts differ from the read and write counts in the preceding ADAI03 message.

No action is required for this informational message.

Note:
This message is available in z/OS systems only.

This message is written at data set close following message ADAI03. If it was necessary to retry any zHPF I/O requests using an ECKD channel program (for instance because zHPF became unavailable on the operating system), the retry count is supplied.

No action is required for this informational message.

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 when a disk I/O error is reported back to ADAIOR by the operating system.

The first 3 lines of the message are sent to the console and DDPRINT. Subsequent lines are sent to DDPRINT only.

The message variables and their meanings are:

For more information on CCW, CSW and sense data, please refer to the relevant IBM publication.

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

If no hardware failure occurred, please contact your Software AG technical support representative.

The ADAIOR trace table has been activated and printed.

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

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.

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.

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.

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.

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.

Note:
This message is available in z/OS systems only.

An I/O error has been detected for a zHPF channel program. The zHPF I/O is retried as a non-zHPF I/O and no further zHPF I/O will be attempted on this file extent during the job step.

This message is followed by message ADAI41.

No action is required for this informational message.

An attempt to allocate storage using fixed one-megabyte or two-gigabyte large pages failed. One of three possible reasons is listed in the message:

When "{R15=nnnnnnnn R0=nnnnnnnnn}" is shown in the message, it indicates that an unexpected return code was received from the z/OS IARV64 service.

No immediate action is necessary, as a storage allocation not using large pages will be attempted instead.

Action may be required to prevent this warning message from appearing when the job is next run:

• If the message indicates that the job was not authorized, ensure when rerunning the job that it is APF-authorized.

• If your system does not support large pages, do not use the ADARUN parameter causing the attempt to allocate using large pages. Remove it from the startup JCL of the job.

• If your system does support large pages of the type requested, consider increasing the number of fixed large pages specified for your operating system using the LFAREA parameter in PARMLIB member IEASYSxx. Contact your system administrator for assistance. For more information, read your IBM MVS Initialization and Tuning documentation.

Note:
This message is available in z/OS systems only.

An I/O error has been detected for a zHPF channel program, because zHPF is no longer available. The zHPF I/O is retried as a non-zHPF I/O and no further zHPF I/O will be attempted on any file until after message ADAI42 is issued.

This message is followed by message ADAI41.

No action is required for this informational message.

Note:
This message is available in z/OS systems only.

This message occurs when a disk I/O error on a zHPF channel program is reported back to ADAIOR by the operating system. Message ADAI41 is issued immediately following ADAI35 or ADAI40.

If ADAI41 is issued following ADAI40, only the first three lines of message ADAI41 are generated. The first three lines of the message are sent to the console and DDPRINT. Subsequent lines are sent to DDPRINT only.

The message variables and their meanings are:

For more information on TCW, CSW and sense data, please refer to the relevant IBM publication.

When preceded by message ADAI40, no further action is required.

When preceded by message ADAI35, use the information provided by the message to locate a possible hardware failure. Keep the information and any dumps for later use.

If no hardware failure occurred, please contact your Software AG technical support representative for assistance.

Note:
This message is available in z/OS systems only.

zHPF has been enabled on the operating system. I/O to data sets opened in zHPF mode, on devices which support zHPF, will now use zHPF channel programs.

This message is only issued after a previous ADAI40 message.

No action is required for this informational message.

A 64-bit virtual storage area was allocated with the address and length indicated in the message.

Different message endings appear using this message ID, depending on the type of storage requested and the type of storage allocated. The following table lists the possible messages, their cause, and recommended actions you can take when they occur.

Refer to the specific message ending in the table above to determine what action, if any, is necessary.

BS2000 systems only: A PAM I/O error occurred on DASD file file-name.

• err-num is the DMS error code. The explanation for the error can be found out using the following online command:

  HELP-MESSAGE DMS<err-num>

• error-rabn is the RABN where the error occurred.

• 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, contact your Software AG technical support representative.

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

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.

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.

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 ret-code and subcode display the error code returned from the operating system.

Interpret the error code for your system and respond accordingly.

Note:
This message is available in z/VSE and BS2000 systems only.

The data set specified is being opened using dynamic allocation in the mode given in the message (CKD, ECKD, or FBA). The file resides on a storage control device that supports count key data (CKD), extended count key data (ECKD) or fixed block access (FBA) channel commands. Adabas generates channel programs accordingly.

Note:
This message is available in z/VSE and BS2000 systems only.

The file specified is being opened in the mode given in the message (CKD, ECKD or zHPF). The file resides on a storage control device that supports count key data (CKD), extended count key data (ECKD) or high performance FICON (zHPF) channel commands. Adabas generates channel programs accordingly.

Note:
This message is available in z/OS systems only.

The file (ddname) or dynamically allocated data set (dsn) is being opened in the mode given in the message (CKD or ECKD). The file resides on a storage control device that supports count key data (CKD) or extended count key data (ECKD) channel commands. Adabas generates channel programs accordingly.

The block size (blksize) of the data set is given in the message. It contains the blocks with numbers start-RABN through end-RABN.

No action is required for this informational message.

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

Contact your Software AG technical support representative.

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.

Note:
This message appears in BS2000 systems.

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.

If this message occurs because of regular disabling processing, such as through the use of the ADAEND command, no action is required.

If this message occurs because of an unexpected error, then either the additional message "SUBTASK POSTED RC: return-code" is printed or additional messages can be found in the subtask-specific protocol. In this case, contact your Software AG technical support representative for assistance.

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

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

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

BS2000 only: For ASSO or DATA containers, the declared size nnnnnnnnnn is larger than the physical size mmmmmmmmmm for the container on link name llllllll. This happened after running the ADADBS INCREASE utility function or a wrong declaration of the size when the container was defined with the ADADEF utility. This can lead to I/O errors and database maintenance problems.

It is no longer possible to start the nucleus or run Adabas utilities other than the ADADBS, ADAFRM or ADAREP utilities.

Either run the ADADBS DECREASE utility function with a size of nnnnnnnnnn - mmmmmmmmmm blocks or run the ADAFRM utility with FROMRABN=NEXT and a size of nnnnnnnnnn - mmmmmmmmmm.

An error has occurred processing a request to write a message to the console.

Contact your Software AG technical support representative for assistance.