ADAU* Utility Status Messages

This message confirms entry of the operator command command.

This message is a reply to a utilities operator command other than DSTAT, which is the only valid operator command at this time.

Enter the operator command DSTAT.

This message is the response to the ADASAV operator command DSTAT. The count value is the number of blocks already processed, and total is the total number of blocks to be saved.

This message is the response to the ADASAV operator command DSTAT. The count value is the number of blocks already restored, and total is the total number of blocks to be restored.

This message, a response to the ADASAV utility's operator command DSTAT, indicates that the second pass of the RESTONL function has begun. The file or database has been restored, and ADASAV is now processing the protection log.

This message is displayed by ADASAV when reading from or writing to a new tape. The "A" or "D" that might appear between "RABN" and the first RABN number (first-rabn#) stand for Asso or Data.

This message shows the session number assigned to the save tape created by the save operation.

The specified file was added or removed from the file list for the specified reason.

• Reasons for adding files: coupled or expanded file

• Reasons for removing files:

  • file not loaded

  • inconsistent expanded or coupled file

  • file in inconsistent state

  • not flagged "modified"

If the file is added to the file list, it is saved; if the file is removed from the file list, it is not saved at all.

None required. This is an informational message only. To restore a file that was removed from the file list, the appropriate previous SAVE data set must be used.

The output data set is not created because there is no change.

The previous SAVE tapes should be used to restore the file. To restore a removed file, the appropriate save data set must be used.

This message is the response to the ADASAV operator command DSTAT. ADASAV is currently creating a delta save data set by merging.

This message is a response to the ADASAV operator command DSTAT. ADASAV is currently creating a full save data set by merging. count blocks have already been written; total blocks are to be written.

This message is a response to the ADASAV operator command DSTAT. ADASAV is currently in the second phase of a delta restore operation. The full save data set has already been restored.

The ADADBS OPERCOM utility issued the specified operator command.

None required. This informational message informs you of any changes in file access, etc., that may result from ADADBS OPERCOM operation.

This message is a response to ADALOD operator command DSTAT, and indicates that ADALOD is sorting and loading the inverted list for the specified descriptor.

This message is a response to the ADALOD operator command DSTAT, and advises that ADALOD is now loading records into data storage. Thus far, the specified number of records have been loaded.

This message is a response to the ADALOD operator command DSTAT, and advises that ADALOD is now presorting data storage (DS) records by their ADAM keys. Thus far, the specified number of records have been sorted.

This message is a response to the ADALOD operator command DSTAT, and indicates that ADALOD is now computing index space requirements for the specified descriptor.

This message is a response to the ADAORD operator command DSTAT, and indicates that ADAORD is now unloading the Data Storage for the specified file to DDFILEA. Thus far, the number of records specified by "record-count" have been unloaded.

This message is a response to the ADAORD operator command DSTAT, and indicates that ADAORD is now unloading the inverted list for the specified file to DDFILEA for the file "file-number".

This message is a response to the ADAORD operator command DSTAT, and indicates that ADAORD is now unloading the Data Storage space table (DSST) for the specified file to DDFILEA.

This message is a response to the ADAORD operator command DSTAT, and indicates that ADAORD is now unloading the address converter (AC) for the specified file to DDFILEA.

This message is a response to the ADAORD operator command DSTAT, and indicates that ADAORD is now loading the Data Storage for the specified file from DDFILEA. Thus far, the number of records specified by "record-count" have been loaded.

This message is a response to the ADAORD operator command DSTAT, and indicates that ADAORD is now loading the inverted list for the specified file from DDFILEA.

This message is a response to the ADAORD operator command DSTAT, and indicates that ADAORD is now loading the Data Storage space table (DSST) for the specified file from DDFILEA.

This message is a response to the ADAORD operator command DSTAT, and indicates that ADAORD is now loading the address converter (AC) from DDFILEA.

The ADAULD utility displays this message to indicate that the file being loaded has the CLIENT option in effect.

The format SIZE parameter in the ADAFRM parameters for the specified file exceeds its maximum cylinder or block size. This returns a User Abend 35 from the ADAFRM utility.

To format the remaining blocks, create the file with a size that can match the SIZE requested and rerun the ADAFRM job for all files not reported as formatted.

The ADAULD utility displays this message to indicate that the file being loaded has the USERISN option in effect.

User exit 9 returned an indication to write a record to DDOUT2, which is not defined. All records are written to DDOUT1.

If the records are to be unloaded onto two output data sets under control of user exit 9, specify DDOUT2 and rerun the job.

The number of blocks to be formatted must be at least the number of blocks per track.

If the number of blocks to be formatted is more than the number of blocks per track, then "block-n" must be the last block of the track.

Block "block-n" is not the last block of a track, or the ADAFRM SIZE parameter is less than the number of blocks per track. The partial track was not formatted.

To format the remaining blocks, specify a block range that spans a complete track.

The file has been loaded, but for some reason could not be linked into the expanded file chain. The cause could be one of the following:

• another file in the chain is locked

• the chain was modified during the load operation

Link the file into the expanded file chain using Adabas Online System (AOS).

The nucleus is in read-only state. A checkpoint cannot be written.

The ADAORD utility has begun its second pass. Any abend after this point requires that the file or database be restored before being used.

ADAORD was started by the specified job. This message follows message ADAU40.

This message occurs in response to the ADAVAL DSTAT operator command, and indicates that ADAVAL is now validating descriptor "descriptor" in file "file-number".

The ADALOD NUMREC parameter restricts the number of records to be loaded. In this case, the input data set contains more records than requested.

No action is required. Processing continues normally, but returns a response code of 4 (ADARSP004) to the operating system.

All ISNs available in the address converter (AC) are already assigned to records in the input file, and new ISNs cannot be allocated because NOACEXTENSION is active.

Processing continues normally, but returns a response code of 4 (ADARSP004) to the operating system. If the file is part of an expanded file, you can load the remaining records into another part of the expanded file.

Warning: An abnormal termination (abend) occurred while ADALOD was updating the expanded file's chain information. The information could be inconsistent, and any further processing of the file will create incorrect results.

Perform ADAREP to create an expanded file report, and check the expanded file linkage. Any errors must be corrected before processing can continue.

An error occurred while ADALOD was processing the file. The file is now in load status, but cannot be accessed.

Correct the cause of the error, and then either

• restart the ADALOD job;

• delete the file and rerun the ADALOD job; or

• restore the SAVE file copy and rerun the ADALOD job.

The file processing has completed, but a problem occurred while writing either

• recovery log information; or

• the checkpoint.

If necessary, ensure that you can redo the ADALOD job when a RESTORE/REGENERATE is done.

The USERISN option was in effect when the file was created by ADACMP or ADAULD. The USERISN option has been suppressed by specifying USERISN=NO. All ISNs are assigned by ADALOD.

The file is loaded with the USERISN option in effect. All ISNs are taken from the input file.

This message is a response to the ADARES operator command, DSTAT:

This message is a response to the ADARES operator command, DSTAT. When the message is displayed, the REPAIR function has processed "count" blocks and "record-count" records from the protection log input data set.

This message is a response to the ADARES operator command, DSTAT. function is either PLCOPY or CLCOPY. count blocks have been copied from DDPLOGR1/2 or DDCLOGR1/2 to the output data set.

This message is a response to the DSTAT operator command during ADARES operation. count is the number of blocks copied by the COPY function.

The file to be loaded will be defined as a multiclient file.

The file to be loaded is a multiclient file but will be defined as normal; that is, as a non-multiclient file.

This message reports on the percentage of the LWP work pool used. You may want to use this information to tune the LWP parameter for your installation.

Proceeding with ZIIP=NO.

The specified password for the ADASCR INSERT function already exists. The related information (file numbers, access and update levels) has been overwritten.

The utility parameter test, as requested by specifying the TEST parameter, was completed successfully.

No checkpoint could be written for a MERGE function because either the Adabas nucleus was not available or the Associator job control was not specified.

None. The MERGE function continues.

If a checkpoint is required, start the nucleus or provide the Associator job control for the MERGE function.

This message is displayed on the ADASAV job protocol at the end of an ADASAV RESTORE execution. It indicates the protection log that should be used as input to a subsequent ADARES REGENERATE job.

"log-number" is the protection log number. If that session happens to be a database save operation, the session number of the next nucleus session following the save operation must be used.

If the ADASAV RESTORE execution is to be followed by an ADARES REGENERATE operation, use the protection log with the indicated nucleus session number as input for the REGENERATE function.

This message is displayed on the ADASAV job protocol at the end of an ADASAV RESTORE execution. It points out the protection log (log-n) that should be input to a possible subsequent ADARES REGENERATE job, and to the checkpoint ( chk-pnt ) where the REGENERATE function should begin. "blk-num" is the (pre-merge) protection log block number of the checkpoint. "nucid" identifies the particular cluster nucleus where the checkpoint originally (that is, before a PLOG merge) resided.

If the ADASAV RESTORE execution is to be followed by an ADARES REGENERATE operation, use the protection log with the indicated nucleus session number as input for the REGENERATE function, and specify the "chk-pnt" checkpoint and "blk-num" as parameters.

Adabas version "v" created the unload data set specified as input.

The save data set specified as input was created by Adabas version "v".

In response to ADAULD operator command DSTAT, ADAULD is currently unloading file "file-number". At this point in time, "rec-count" records have been unloaded.

The utility is processing a file with a compressed or uncompressed index, as indicated.

A nonempty Work data set was assigned to an ADASAV RESTOREDB job that belongs to another database.

The Work data set is not reset.

The ADADBS utility issued either an FEOFPL or an FEOFCL. If there is no free PLOG or CLOG, the nucleus may potentially wait for a free PLOG/CLOG.

No action is required for this informational message.

The utility's request to lock the RLOG data set for the Adabas nucleus failed. The nucleus could experience a short hard wait if it attempts to access the RLOG data set at the same time as the utility.

The utility's request to unlock the RLOG data set for the Adabas nucleus failed. An ADADBS or Adabas Online System function could experience a medium wait if it needs to be recorded in the RLOG data set.

For restoring the database, initialization of RLOG data set access failed (utility error 058). ADASAV deactivates the Recovery Aid and continues the restore. ADASAV will terminate with return code 4.

Reactivate the Recovery Aid by executing the ADARAI PREPARE function again.

For a utility function that does not change the database or files, initialization of RLOG data set access failed (utility error 058). The utility continues without recording its run in the recovery log and terminates with return code 4.

Determine why the utility error 058 occurred. Correct the error.

While converting from a version of Adabas that uses the parallel participant table (PPT) structure to a higher version of Adabas, the system determined that the specified protection log (PLOG) for the specified earlier version nucleus (NUCID=0 for a noncluster nucleus) remained uncopied/unmerged. The conversion fails.

You can bypass this check if necessary by using the ADACNV CONVERT IGNPPT parameter.

This message display statistics about the processing of the Event Replicator utility ADARPL.

No action is required for this informational message.

The ADAZAP utility is being used to change the DBID in the GCB (RABN 1 of the DDASSOR1 dataset). This message, which is written to the DDDRUCK output of ADAZAP, reports the old DBID (before the change) and new DBID (after the change).

Ensure that the ADARUN DBID parameter specifies the new DBID of the database after the change. If Adabas SAF Security is used to check the authorization of utility executions on function level, ensure that the user is authorized to run ADAZAP on both the old DBID and the new DBID.

ECS is the Entire Conversion Services, a subsystem of the Adabas universal encoding support (UES) system. This message is written after a function of the subsystem has failed. The following ECS functions may return errors:

Resolve the problem and try again.

The specified version / revision / system-maintenance level of Entire Conversion Services has been initialized.

The specified collation exit supporting a collation descriptor field has been initialized.

This message is issued during utility processing. The actual message text varies, depending on the utility, as described in the following table.

No action is required for this informational message.

The file (fnr) to be restored to a database with a different DBID or to a database where replication is turned off has a nonzero Event Replicator Server target DBID set in the FCB. The target DBID will be reset for this file.

No action is required for this informational message. The Event Replicator Server target DBID for the file is reset automatically.

While processing the file (fnr) listed in the message, which is part of a LOB file group, the utility detected that one file in the group is out-of-sync with the other file. The base file number (base-fnr) and the LOB file number (lob-fnr) are also given in the message. The utility detects this condition and ends with return code 4 or 8.

This problem can occur if, through a logically incorrect sequence of utility operations, either or both files were exported from and reimported into the database, but not put back to the same point in time. In other words, one file would contain the results of a LB field update that the other, associated, file does not contain.

Investigate the sequence of utility operations on the files involved and determine why they are not in sync. Take actions to bring them back in sync. Then, if necessary, run the following function to mark the two files as being in sync.

ADADBS MODFCB FILE=base-fnr,LOBFILE=lob-fnr

While processing the file (fnr) listed in the message, which is part of a LOB file group, the utility detected that utility operations had been performed on the file group that left Adabas unable to track the LOB-update-status of the files. The base file number (base-fnr) and LOB file number (lob-fnr) are also given in the message. The utility that detects this condition ends with return code 4.

The LOB-update-status values of the files in a LOB file group reflect the LOB values in a base or LOB file when the file is exported from or imported to the database. Most utility operations either preserve the LOB-update-status of a file or change it to a defined new value, but some do not. In this case, the unable-to-track flag is set to signal that Adabas has become unable to guarantee that utility operations have kept the LOB file group in sync.

If you know that no (logically incorrect) utility operations were performed that put the files in a LOB file group out of sync, you can use the following function to mark the two files as being in sync.

ADADBS MODFCB FILE=base-fnr,LOBFILE=lob-fnr

While processing the file (fnr) listed in the message, which is part of a LOB file group, the utility detected that the base file and LOB file are out-of-sync. The base file number (base-fnr) and LOB file number (lob-fnr) and their respective LOB-update-status values (stat-val1 and stat-val2) are also given in the message. The utility ends with return code 4 or 8.

The LOB-update-status values of the files in a LOB file group reflect the LOB values in a base or LOB file when the file is exported from or imported to the database. As LOB operations are performed on the LOB file group, the LOB-update-status value changes for both files at the same time, resulting in a status value that is different if either or both files are exported or imported again.

A mismatch condition can occur if a logically incorrect sequence of utility operations caused the files to contain the results of different LOB updates.

Investigate the sequence of utility operations on the files involved and determine why they are not in sync. Take actions to bring them back in sync. Then, if necessary, run the following function to make the two files as being in sync.

ADADBS MODFCB FILE=base-fnr,LOBFILE=lob-fnr

ADALOD could not establish the complete linkage between the base file and the LOB file because the file specified in the BASEFILE or LOBFILE parameter was either locked or not loaded.

ADALOD sets part of the file linkage only in the file just loaded and ends with return code 4.

If the other file does not exist, specify the correct BASEFILE or LOBFILE parameter when loading that file. This will establish the complete base-file-LOB file linkage.

If the other file is locked, wait until the utility function that locked the files has ended. Then, check whether the base file-LOB file linkage is in place (for example, using ADAREP). If necessary, you can use the following function to reestablish the base file-LOB file linkage:

ADADBS MODFCB FILE=base-fnr,LOBFILE=lob-fnr

The last formatted ISN or secondary ISN was not set for the file listed in the message (fn). When the utility completes, the last formatted ISN will be set to the value of MAXISN or the last formatted secondary ISN will be set to the value of MAXISN2.

No action is required for this informational message.

This message is a response to the utility DSTAT operator command, if the corresponding utility is still in its initialization phase.

No action is required for this informational message.

This message is returned when the DSTAT operator command is issued against a running ADACHK process. The file number (fn) and the ADACHK function name (fx-name) are given in the message. Possible function names are "ACCHECK", "DSCHECK", "ICHECK", or "VALIDATE".

No action is required for this informational message.

The ADALOD or ADAORD utilities were run, specifying the MAXRECL parameter, against files with spanned Data Storage records. The MAXRECL parameter is ignored and the utility ends with return code 4.

No action is required for this informational message.

The ADALOD utility was run, specifying the MIXDSDEV parameter, against files with spanned Data Storage records. The MIXDSDEV parameter is ignored and the utility ends with return code 4.

No action is required for this informational message.

The product license check works with the separate component Mainframe License Check (MLC). For a correct interaction with MLC a minimum version vvvv is required.

Update the MLC component and rerun the job.