ADAI* - ADAIOR System Messages

A sequential data set is closed.

The read count is shown when a sequential input data set is closed. The write count is shown 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, (desc) is the Getmain descriptor, stor-req is the amount of memory requested, stor-avail is the amount of memory available, and address is the Getmain address.

A direct access data set is closed.

The physical-file-name indicates that the file was opened using dynamic allocation.

The read count countr and write count countw are shown.

The write count countw is the count of update writes only. If any format writes were issued, the format write count is shown in countf.

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.

This message is written at data set close following message ADAI03 when a direct access data set 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.

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

The ADAIOR trace table has been activated and printed.

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.

An operator command has been entered. The text of the operator command is shown in command.

No action is required for this informational message.

ADAIOR has completed formatting for a direct-access file.

An internal error has occurred.

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

A write to operator (WTO) request has returned a non-zero response code nnnnnnnn.

Following the ADAI34 message, the message which caused the WTO failure is written to DDPRINT as normal, and processing continues.

No action is required for this warning message. However, the user is advised to check the system console log for error messages issued by z/OS relating to WTO problems.

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.

This message may be issued by ADAFRM when a new dataset is being formatted.

There is no available space on the volume selected by z/OS for allocating the first secondary extent.

Following this message, the job will be terminated with user abend 692.

Specify non-zero primary allocations for the new datasets being formatted and rerun the job.

An attempt to allocate a buffer for encryption services has failed because there is no available space in the encryption buffer pool.

The job will continue to run but performance may be severely degraded.

Contact your our support representative for information on how to tailor the encryption buffer pool size for your installation.

An attempt to allocate storage using fixed or pageable 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.

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.

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

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.

Refer to the table below for description and action:

See table above.

Either the encryption service has returned an error indicated by the return code and reason code, or the encryption parameter list could not be built.

Contact your our support representative.

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.

The file (ddname) or dynamically allocated data set (dsn) is being opened in the mode (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.

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

If the dataset is encrypted, an additional message line is generated to indicate this.

No action is required for this informational message.

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.

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.

During a request to open DDCARD or DDDRUCK, an invalid record format or record length has been detected. DDCARD and DDDRUCK are required to be in fixed record format (RECFM=F), with a record length of 80 bytes (LRECL=80).

Correct the error and rerun the job.

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

Contact your technical support representative for assistance.

The file or data set listed in the message (ddname or dsn) has been dynamically allocated and added to ASSO or DATA during this nucleus session. All subsequent jobs for this database need the added DD name (ddname) in the JCL.

This message is displayed at nucleus termination.

Verify that the added data set has been included in the JCL for all nucleus and utility jobs for this database. If it has not, add appropriate JCL statements for the new data set to the jobs.

This message appears when either of the following situations has occurred:

• The Adabas nucleus issued a request to add a new ASSO or DATA data set comprising the listed number of cylinders (nnnnn) or to increase the size of the final ASSO or DATA data set by the listed number of cylinders or blocks.

• An Adabas utility detected that a new ASSO or DATA data set comprising the listed number of cylinders (nnnnn) has been added or the size of the final ASSO or DATA data set has been increased by the listed number of cylinders or blocks.

• The Adabas nucleus issued a request to decrease the size of ASSO or DATA by the listed number of cylinders or blocks.

For an add request, the data set name requested is also listed in the message (dsn).

No action is required for this informational message.

A previous request has been activated to add a new ASSO or DATA data set, increase the size of the final ASSO or DATA data set, or decrease the size of the ASSO or DATA data set. For an add or increase, the database is now ready to make use of the additional space. For a decrease, the areas of ASSO or DATA affected are no longer available to the database.

The DD name (ddname) associated with the data set is given in the message.

No action is required for this informational message.

A request has failed to add a new ASSO or DATA data set, increase the size of the final ASSO or DATA data set, decrease the size of ASSO or DATA, or to revoke or activate a previous request. The DD name (ddname) of the data set, the return code (cc) and the reason code (rsn) are given in the message.

If an add, increase or decrease request fails, the nucleus will continue running with the existing ASSO and DATA data sets and data set sizes. If a revoke or activate request fails, the nucleus will terminate abnormally (internal error).

A previous request has been revoked to add a new ASSO or DATA data set, increase the size of the final ASSO or DATA data set. or decrease the size of ASSO or DATA. An add, increase. or decrease request may be revoked if an error occurs after the request has been issued. The DD name (ddname) associated with the data set is given in the message.

The nucleus will continue running with the existing ASSO and DATA data sets and data set sizes.

No action is required for this informational message.

This message appears during initialization of a request to extend the ASSO or DATA data set by the listed size (nnnnn). The space requested is provided either in cylinders or in blocks.

The DD name (ddname) associated with the final data set comprising the ASSO or DATA database component (containers) is given in the message.

No action is required for this informational message.

When Adabas Cluster Services or Adabas Parallel Services is being used, a request to increase the size of ASSO or DATA in a peer nucleus has not been able to process the new extent information correctly.

This might occur if, for example, additional volumes have been added to the dataset since the nuclei were started.

If new volumes have been added to the dataset since the nuclei were started, the increase will not complete until all participating nuclei are recycled.

If the problem persists, contact your our support representative.

An ENQ or DEQ failure occurred when writing a print line to DDPRINT or DDDRUCK.

Contact your technical support representative for assistance.

A read, write, open, or close error has occurred during sequential dataset prtocessing.

If an attempt to write to DDPRINT or DDDRUCK has failed, the job will continue processing normally, but no further writes to DDPRINT or DDDRUCK will be attempted. A warning is given via a second message in this case:

All further writes to {DDPRINT | DDDRUCK} will be ignored

Note that if the Adabas nucleus issues this message for DDPRINT, Adabas shutdown statistics on DDPRINT will be lost.

Investigate the cause of the error using the diagnostic information supplied in the message.

If the error resulted from a file full condition, consider increasing the size of the file for future Adabas nucleus or utility jobs.

If the cause of the error cannot be determined, contact your technical support representative.

A Resource Manager invoked during termination has successfully page-freed areas of page-fixed storage.

This message may appear at termination following an abnormal end or cancel request.

No action is required for this informational message.

A Resource Manager invoked during termination has unsuccessfully attempted to page-free areas of page-fixed storage.

This message may appear at termination following an abnormal end or cancel request.

Contact your technical support representative.

If a system abend occurred, ensure that the dump is available for problem diagnosis

A Resource Manager invoked during termination was unable to attempt to page-free areas of page-fixed storage.

This message may appear at termination following an abnormal end or cancel request.

Contact your technical support representative.

If a system abend occurred, ensure that the dump is available for problem diagnosis

Event management using z/OS Pause Elements has been successfully initialized. This message is issued only when Adabas is running with ADARUN parameter ZIIP=YES.

No action is required for this informational message.

Event management using z/OS Pause Elements has been successfully terminated. This message is only issued when Adabas is running with ADARUN parameter ZIIP=YES.

This message may appear at termination following an abnormal end or cancel request.

No action is required for this informational message.

Event management using z/OS Pause Elements has returned an error. The unexpected return code (ret code) and reason (rsn code) are shown. This message is only issued when Adabas is running with ADARUN parameter ZIIP=YES.

This message may appear at termination following an abnormal end or cancel request.

If this message appears at termination following an abnormal end or cancel request, no action is required.

In any other circumstances, save the JES log, DDPRINT output and any dump of the Adabas nucleus and Contact your technical support representative for assistance.

A storage allocation request which might result in storage fragmentation has been detected. For example, a small amount of storage is being allocated on a page boundary.

Additional information on the length and type of storage being allocated is supplied on DDPRINT.

This is an informational message only, but, if it appears, users are requested to pass details of the message to their technical support representative for further assistance.

A storage allocation request has failed with reason code nnnnnnnn.

Additional information on the length and type of storage being allocated is supplied on DDPRINT.

Further error messages may appear or an abnormal end might occur as a consequence of the storage allocation failure.

Users should review the message text and attempt to correct the condition, for example by providing more virtual storage for the job.

If the message persists, users should contact their technical support representative for further assistance.