Messages NGTY000 through NGTY999

ADREC Prepare starting.

Explanation: This message indicates the ADREC PREPARE process is starting.

User response: No action is required.

ADREC Prepare already active.

Explanation: This message indicates that an ADREC PREPARE job is already active. Only one PREPARE job can be active at one time.

User response: No action is required.

No SYSCOPY records to process.

Explanation: This message indicates ADREC PREPARE did not find any records in the PREPARE IDB to process.

User response: No action is required.

SQL error processing string-1.

Explanation: This message indicates ADREC PREPARE encountered a SQL error while processing the specified table.

User response: Check the SQL code in the DB2 Messages and Codes. If the code does not seem appropriate, contact BMC Support.

Unable to obtain DBD lock for database string-1.

Explanation: This message indicates ADREC PREPARE was unable to obtain the DBD lock for the specified database (string-1).

User response: SYSCOPY records for this database will be skipped. Resubmit the PREPARE when the DBD lock can be obtained.

Unable to read DBD for database string-1.

Explanation: This message indicates ADREC PREPARE encountered an error while attempting to read the DBD for the specified database (string-1).

User response: SYSCOPY records for this database will be skipped. Contact BMC Support.

No archive entries found in the SYSPRINT file.

Explanation: This message indicates LPT STRIPLOG was unable to find Archive Logs to be processed.

User response: No logs will be processed. Verify that the correct BSDS was specified. Also ensure the correct MEMBER name, if specified, was requested.

INITRBA is invalid for previously processed member (string-1).

Explanation: This message indicates ADREC STRIPLOG GENERATE is being run against Member(x) with an INITRBA value. However, Member(x) has previously been processed.

User response: INITRBA is used to initialize the STRIPLOG process. It may only be used the first time a member is processed. Remove the INITRBA parameter and rerun the job. If you wish to reset the INITRBA value, a Striplog Reset must first be run.

DELETE DSN – string-1

Explanation: The indicated permanent work file will be deleted. This message is  used by BMC Support.

User response: No action is required.

ADREC Recover starting.

Explanation: This message indicates the ADREC RECOVER process is starting.

User response: No action is required.

number-1 SYSCOPY entries to be prepared.

Explanation: This message is issued after successful read of the NGT SYSCOPY table. number-1 is the number of rows read.

User response: No action is required.

Preparing SYSCOPY entry (COPY_NUM = number-1).

Explanation: This message indicates the ADREC PREPARE process is starting the prepare process for the PREPARE IDB row whose COPY_NUM is number-1.

User response: No action is required.

SYSCOPY entry (COPY_NUM = number-1) prepared.

Explanation: This message indicates the ADREC PREPARE process has completed the prepare process for the PREPARE IDB row whose COPY_NUM is number-1.

User response: No action is required.

Copy file entry already exists (COPY_NUM = number-1).

Explanation: This message indicates the ADREC PREPARE process has found that a COPY file entry already exists for the PREPARE IDB row whose COPY_NUM is number-1.

User response: No action is required.

Prepare file entry already exists (COPY_NUM = number-1).

Explanation: This message indicates the ADREC PREPARE process has found that a PREPARE file entry already exists for the PREPARE IDB row whose COPY_NUM is Number-1.

User response: No action is required.

Prepare file entry (COPY_NUM = number-1) not found.

Explanation: This message indicates the ADREC was unable to locate a PREPARE file entry for the copy record whose COPY_NUM is number-1.

User response: Contact BMC Support.

'ADREC DEFINE' is required before any other function.

Explanation: This message indicates the ADREC DEFINE procedure has not been performed. ADREC DEFINE must be performed before executing any other ADrec function.

User response: Run ADREC DEFINE.

ADREC control member is invalid.

Explanation: This message indicates the ADrec control member was found in the SYSPDS, but it does not contain valid information.

User response: If ADREC DEFINE has not been performed, the run a ADREC DEFINE. Otherwise, contact BMC Support.

ADREC control created hexstring-1/hexstring-2, hexstring-3:hexstring-4:hexstring-5:hexstring-6.

Explanation: This message indicates the date and time the ADrec control member was created.

User response: No action is required.

Job string-1 (string-2) submitted for log string-3.

Explanation: This message indicates that a batch Striplog job was submitted to the system via the Internal Reader.

User response: No action is required.

Log string-1 skipped due to MAXJOB exceeded.

Explanation: This implied MAXJOB value has been exceeded. No job was submitted to process the specified Log.

User response: MAXJOB is controlled via the use of job card symbolics (&N, &NN, &NNN, and &A). Change the symbolic or allow submitted jobs to complete. Then re-submit the Striplog Generate job.

APRPRFIL file error, device type is not supported.

Explanation: The //APRPRFIL DD statement must reference a data set on either tape or DASD. No other devices are supported for this file.

User response: Verify that the DD statement APRPRFIL is in your JCL. If it is on tape or DASD, contact BMC Support.

Error retrieving data set's volume entries.

Explanation: An error occurred while attempting to get a catalogued tape data set's volume entries.

User response: Check the message log for any other error messages. Contact BMC Support.

Incorrect header page in DSN (string-1).

Explanation: The first page in the above named data set is not a header page and therefore it does not describe a DB2 pageset.

User response: This is a terminating error. LOG apply processing will be terminated and the pageset must be restored prior to the LOG apply phase.

Catalog DBID.PSID.PART (hexstring-1.hexstring-2.hexstring-3) does not match space ID (hexstring-4.hexstring-5.hexstring-6).

Explanation: A discrepancy was detected between the DB2 catalog and the pageset header page. The source data set name of the header page will be printed in the next message.

User response: This is a terminating error. LOG apply processing will be terminated and the pageset must be restored prior to the LOG apply phase.

Saving pageset (hexstring-1.hexstring-2.hexstring-3) to DSN (string-1)

Explanation: This message indicates that the above named data set is in the process of being created for the pageset whose ID is (DBID.PSID.PART in hex). This data set will be used to restore the pageset in case of a failure during the log apply phase.

User response: No action is required.

Restoring pageset (hexstring-1.hexstring-2.hexstring-3) from DSN (string-1).

Explanation: This message indicates that the pageset whose ID is (DBID.PSID.PART in hex) is currently being restored from the above named data set. This usually occurs on a restart of a failed LOG APPLY JOB. After restoration, LOG APPLY will start its processing.

User response: No action is required.

number-1 4K pages written to DSN (string-1).

Explanation: This message indicates the number of 4K blocks written to the save page data set that was created earlier and posted by message NGTY029.

User response: No action is required.

number-1 4K pages read from DSN (string-1).

Explanation: This message indicates the number of 4K blocks read from the save page data set and ends the pageset restore process indicated by MSG NGTY030.

User response: No action is required.

LOG APPLY terminating for pageset (hexstring-1.hexstring-2.hexstring-3).

Explanation: The LOG apply process for the indicated table space Pageset ID has completed in a prior run. However this run will perform final cleanup.

User response: No action is required.

LOG APPLY restarting for pageset (hexstring-1.hexstring-2.hexstring-3).

Explanation: The LOG apply process for the indicated table space Pageset ID has failed in a prior run and is now restarting to perform the index change apply phase.

User response: No action is required.

LOG APPLY starting for pageset (hexstring-1.hexstring-2.hexstring-3).

Explanation: The LOG apply process for the indicated table space Pageset ID is starting from the beginning. Any prior changes for the same pageset will be restored prior to the log apply phase.

User response: No action is required.

Scheduling number-1 index processes in number-2 threads.

Explanation: This message shows the number of indexes that will undergo change apply as well as the degree of parallelism to achieve the work.

User response: No action is required.

LOG APPLY complete.

Explanation: This message indicates the end of the process that was started by message NGTY033, NGTY034 or NGTY035. All table space and index changes including non-partitioning indexes have completed successfully.

User response: No action is required.

Not all partitions or NPI's are complete.

Explanation: The log apply process for the current partitioned table space pageset and its partitioning index has completed successfully. The non-partitioning index changes will be performed whenever the last table space partition is complete.

User response: No action is required.

Pageset (hexstring-1.hexstring-2.hexstring-3) is at LevelID (hexstring-4).

Explanation: The table space/index space pageset whose ID is (DBID.PSID.PART) has a LEVELID/RBA or LRSN as indicated. This is the highest logrba that has been applied to the pageset.

User response: No action is required.

Applying index changes to pageset (hexstring-1.hexstring-2.hexstring-3).

Explanation: Index changes resulting from the table space log apply process will be applied to this index whose pageset ID is (DBID.PSID.PART).

User response: No action is required.

number-1 -way merge of key files for pageset (hexstring-1.hexstring-2.hexstring-3).

Explanation: number-1 shows the number of data sets containing keys to be inserted in and/or deleted from the index pageset whose ID is (DBID.PSID.PART). The data sets will be read simultaneously via a hi-speed merge process.

User response: No action is required.

Writing keys file for pageset (hexstring-1.hexstring-2.hexstring-3).

Explanation: Index keys resulting from table space log apply will be written to a sequential data set which will be used to update the index whose ID is (DBID.PSID.PART). For an NPI, the PART number will correspond to the TS partition from which the keys were extracted.

User response: No action is required.

number-1 keys written to DSN (string-1).

Explanation: number-1 shows the number of keys written to the above named data set for the index whose pageset ID is reported in a prior NGTY042 by the same task.

User response: No action is required.

LOG APPLY error in page (hexstring-1) at RBA (hexstring-2).

Explanation: A terminating error has occurred during the log apply process. X'hexstring-1' is the page number of the table space page. X'hexstring-2' is the log record RBA causing the error.

User response: The next set of messages will describe the error in detail. Moreover, a hex dump of the log record and the DB2 page will be provided for further analysis.

Error occurred during page compaction.

Explanation: Before a log record is applied, a TS page may have to be compacted. This message shows that there is a physical error with the DB2 page.

User response: This indicates that the TS page is erroneous rather than the LOG record. The next message will show the compaction error reason text.

Reason string-1.

Explanation: This is the error reason text for either NGTY045 or NGTY044 message.

User response: For a compaction error, you need to analyze the TS page. Otherwise analysis of the TS page and the LOGRECORD is required in order to resolve the error.

string-1 DDNAME is required for Prepare.

Explanation: The specified DDNAME (string-1) is required for PREPARE processing, but was not found.

User response: This is a terminating error. PREPARE processing will be terminated.

Error encountered extracting DBD information (number-1).

Explanation: This message indicates that an ADREC PREPARE was unable to extract DBD information for one of the records found in PREPARE IDB. number-1 is a reason code that identifies why the extract failed.

User response: The SYSCOPY record that received the error is ignored. Processing continues with the next record.

Prepare entry for string-1.string-2 skipped (number-1).

Explanation: This message indicates ADREC COPY has encountered an error with the SYSCOPY information for the object listed. ADrec is skipping the creation of a PREPARE entry for this row.

User response: No action is required.

No PREPARE file (APRPRPRP) records to process.

Explanation: This message indicates ADREC PREPARE did not find any records in the file pointed to by the APRPRPRP DD.

User response: No action is required.

Tablespace string-1.string-2 must already exist.

Explanation: This message indicates ADREC DEFINE did not find the NGT table space.

User response: Define the NGT Database, table space.

string-1 dataset created.

Explanation: This message indicates ADREC DEFINE has created the indicated data set.

User response: No action is required.

ADREC string-1 dataset name must contain a '.CDBDBX' qualifier.

Explanation: The CTL/LOG data set does not contain the required qualifier.

User response: Respecify the data set name using the required form.

Maximum number of JCL records (200) exceeded - number-1 supplied.

Explanation: This message indicates ADREC DEFINE has generated more than the supported number of JCL statements.

User response: Contact BMC Support for assistance.

number-1 JCL records saved.

Explanation: This message shows the number of JCL records saved.

User response: No action is required.

Delete failed for ADREC string-1 DATASET.

Explanation: The delete operation could not be performed for the indicated LOG/CTL data set.

User response: No action is required.

Open failed for file string-1.

Explanation: The indicated output file could not be opened.

User response: Check the message log for indications for the failure.

INITRBA may be specified only once - input value ignored.

Explanation: This message indicates that an init RBA already exists. Processing will continue.

User response: No action is required.

Null record type at LOGRBA hexstring-1.

Explanation: This informational message indicates that a null record was found at the specified logrba. Processing will continue.

User response: No action is required.

Cannot run SPLIT if CONSOLIDATE is running.

Explanation: Splitlog cannot run while consolidate is running.

User response: Wait until consolidate finishes to run split.

CONSOLIDATE not done before 'SPLIT'. Failure on DBID/PSID hexstring-1.

Explanation: Consolidate must be run before split. This message indicates that consolidate has not been run.

User response: Run consolidate first then, after it completes, run strip.

Only one ADREC PURGELOG/CONSOLIDATE can be running at a time.

Explanation: Another Purgelog/Consolidate is running. Only one of these processes can run at one time.

User response: Run this purgelog/consolidate after the current process completes.

In-flight files consolidated - number-1 tracks released.

Explanation: The in-flight file consolidation step of the purgelog/consolidate process has completed.

User response: No action is required.

- UNIT-OF-WORK Files consolidated - number-1 tracks released string-1.

Explanation: The unit of work file consolidation step of the purgelog/consolidate process has completed.

User response: No action is required.

DB2 OBJECT LOG files consolidated - number-1 tracks released.

Explanation: The DB2 object log file consolidation step of the purgelog/consolidate process has completed.

User response: No action is required.

Doing LOG STRIP for string-1.

Explanation: This informational message issued in conjunction with NGTY067, indicates that a log strip has started.

User response: No action is required.

Starting LOG RBA string-1, Ending LOG RBA string-2.

Explanation: This information refers to the log strip described in the previously issued NGTY066 message.

User response: No action is required.

Log read complete - number-1 pages.

Explanation: The ADrec log read has completed.

User response: No action is required.

Open failed for KEY file string-1.

Explanation: This message indicates ADrec Log Apply failed due to an open failure on the named key file.

User response: If the corrective action is not obvious from the diagnostic messages, contact BMC Support.

Open failed for LOG file string-1.

Explanation: This message indicates ADrec Log Apply failed due to an open failure on the named key file.

User response: If the corrective action is not obvious from the diagnostic messages, contact BMC Support.

Open failed for POF file string-1.

Explanation: This message indicates ADrec Log Apply failed due to an open failure on the named pointer/overflow file.

User response: If the corrective action is not obvious from the diagnostic messages, contact BMC Support.

Define failed for new DB2 dataset.

Explanation: This message indicates that ADREC DEFINE was not able to define the CTL or LOG data set.

User response: Check the message log for indications for the failure.

SYSTEM PDS error - string-1 string-2.

Explanation: Some error has occurred processing the PDS that contains the restart and control information. The text of the message should describe the nature the problem.

User response: If the corrective action is not obvious from the diagnostic messages, contact BMC Support.

Allocation failed for dataset.

Explanation: Dynamic allocation failed for a sequential data set. A second message describes the error.

User response: Check system messages on the job log or allocation log to determine the cause of the failure.

Unable to open SYSIN.

Explanation: An attempt to open the temporary data set previously allocated under the DDName 'SYSIN' has failed.

User response: Refer to the reason indicated in system message IEC161I. Attempt to correct the error, or contact BMC Support.

ADREC will not process this copy (SHRLEVEL CHANGE).

Explanation: The current release of ADrec only supports SHRLEVEL REFERENCE copies. Since this copy is not a SHRLEVEL REFERENCE copy, ADrec will not process the copy or attempt to use it for recovery.

User response: No action is required.

ADREC will not process this copy (INCREMENTAL).

Explanation: The current release of ADrec only supports FULL copies. Since this copy is not a FULL copy, ADrec will not process the copy or attempt to use it for recovery.

User response: No action is required.

number-1 copies purged, number-2 tracks released, from DBID hexstring-1 PSID hexstring-2.

Explanation: This is an informational message. It indicates the number of copies purged, tracks released, from a DBID PSID during the Purge Copy process of Striplog Consolidate.

User response: No action is required.

No prepared copies were found for the following objects, they can not be recovered.

Explanation: This indicates a problem. The object identified in the message can not be recovered because there are no copies for it.

User response: Submit a copy for the indicated object.

ADREC Application Definition (string-1) starting.

Explanation: This message indicates the ADREC RECOVER process is starting for application string-1 .

User response: No action is required.

ADREC Application definition already active.

Explanation: This message indicates the ADREC APPLICATION DEFINE process is currently active. Only one APPLICATION DEFINE job can be running at a time.

User response: Retry this job after the other APPLICATION DEFINE job has completed.

ADREC Application definition string-1.

Explanation: string-1 is either SAVED, UPDATED, or DELETED. This message indicates the ADrec definition has been defined, updated, or deleted.

User response: No action is required.

'ALL' or 'BYDATABASE' specified but definitions exist.

Explanation: An ADREC APPLICATION DEFINE statement contains the ALL or BYDATABASE keyword. However, ADrec applications have already been defined.

User response: If ALL or BYDATABASE is desired, add an APPLICATION DEFINE RESPECIFY statement before the APPLICATION DEFINE statement and re-run your job.

'THEREST' specified but definitions do not exist.

Explanation: An ADREC APPLICATION DEFINE statement contains the THEREST keyword, but no other ADrec applications have been defined. THEREST can only be used after other applications have been defined.

User response: Define other ADrec applications before defining the THEREST application.

'THEREST' has been previously defined.

Explanation: An ADREC APPLICATION DEFINE statement contains the THEREST keyword, but to the THEREST application has already been defined. The THEREST application can only be defined once.

User response: No action is required.

Define of an application not allowed after 'THEREST' defined.

Explanation: An ADREC APPLICATION DEFINE statement was encountered after the THEREST application has already been defined. The THEREST application must be the last application defined.

User response: Delete the current ADrec application definitions using the RESPECIFY keyword, then redefine your applications placing the THEREST application last.

Define of application not allowed after EXCLUDE list defined.

Explanation: An ADREC APPLICATION DEFINE statement was encountered after EXCLUDES have been defined. Once the EXCLUDES have been defined, no new applications can be created.

User response: Delete the current ADrec EXCLUDES using the UNEXCLUDE keyword, then redefine your application.

Application string-1 created (COPIES (number-1, number-2), PRIORITY number-3, EXPIRE number-4).

Explanation: ADrec application string-1 has been created with the displayed attributes.

User response: No action is required.

Application string-1 has the following databases defined:

Explanation: ADrec application string-1 includes the databases specified in the following messages.

User response: No action is required.

Database string-1 already defined to Application string-2 .

Explanation: The DB2 database string-1 has already been defined in ADrec recover application string-2. A DB2 database can only be defined to one ADrec recover application.

User response: Delete the current ADrec application definitions using the RESPECIFY keyword, then redefine your applications placing the DB2 database in the desired ADrec application.

'APPLICATION DEFINE' has not been performed.

Explanation: ADREC APPLICATION DEFINE has not been performed to define any ADrec recover applications.

User response: Define your ADrec application definitions using the DEFINE keyword.

'APPLICATION DEFINE' DBID table not found.

Explanation: ADREC APPLICATION DEFINE has been performed to define the ADrec recover applications. However, no active DB2 databases were found defined to any applications.

User response: Delete the current ADrec application definitions using the RESPECIFY keyword, then redefine your ADrec applications.

Application string-1's definition currently does not contain any objects.

Explanation: ADREC APPLICATION DEFINE has been performed to define the ADrec application string-1. However, DB2 currently does not have databases defined which match the application's specifications.

User response: No action is required.

'DISPLAY DB()' requires 'BYDATABASE' define.

Explanation: ADREC APPLICATION DISPLAY has been requested using the DB() keyword. However, the ADrec applications were not defined using the BYDATABASE keyword.

User response: No action is required.

Purge processing started for the copy file.

Explanation: The purge process has started for the ADrec Copy File.

User response: No action is required.

Purge processing completed for the copy file.

Explanation: The purge process has completed for the ADrec Copy File.

User response: No action is required.

A total of number-1 copies were purged freeing number-2 log file tracks.

Explanation: This is an informational message.

User response: No action is required.

Application string-1 not found.

Explanation: ADrec APPLICATION string-1 was not found in the current application definitions.

User response: Use APPLICATION DEFINE to define the ADrec application.

No usable copies found for application string-1.

Explanation: ADREC RECOVER was unable to find any usable copies to recover ADrec application string-1.

User response: Run COPY to copy the table spaces defined to the ADrec application.

DBID hexstring-1 is not defined to ADrec so its log data was not kept.

Explanation: No log data will be kept for and object within the specified DBID.

User response: No action is required.

DBID hexstring-1 PSID hexstring-2 is in the ADrec exclude list so its log data was not kept.

Explanation: No log data will be kept for and object within the specified DBID.

User response: No action is required.

DBID hexstring-1 PSID hexstring-2 is no longer defined to ADrec. Date forthis object will expire in number-1 days.

Explanation: The specified object is no longer defined to ADrec. All data for this object will be removed from ADrec in the # days specified.

User response: To avoid data loss, re-define the object to ADrec via the Define Application process, then run an ADrec Striplog Consolidate.

DBID hexstring-1 PSID hexstring-2 has been re-defined to ADrec, the expire flag has been reset.

Explanation: The specified object has been re-defined to ADrec. The expire in # days flag has been reset.

User response: No action is required.

Purge processing started for the Striplog File.

Explanation: The purge process has started for the ADrec Striplog File.

User response: No action is required.

Purge processing completed for the Striplog File.

Explanation: The purge process has completed for the ADrec Striplog File.

User response: No action is required.

Purge processing dropped number-1 Striplog File entries.

Explanation: The purge process has removed the specified number of entries from the Striplog File.

User response: No action is required.

No restores done for Application string-1 (all objects excluded).

Explanation: All objects defined to ADrec application string-1 were found in the list of excluded objects. No restores will be performed for this application.

User response: No action is required.

Gap found in Log data for member string-1, starting at hexstring-1 and ending at hexstring-2.

Explanation: A 'gap' in the saved log data has been identified for the specified member. ADrec is unable to recover beyond that point.

User response: Run a Striplog Generate to process the missing data.

DBID hexstring-1 PSID hexstring-2 Consolidated - number-1 tracks released.

Explanation: The DBID PSID file indicated has been consolidated and the specified number of tracks were released.

User response: No action is required.

Consolidation of the DBID PSID files complete, a total of number-1 tracks released.

Explanation: All DBID PSID files have been consolidated and a total of the specified number of tracks were released.

User response: No action is required.

ADREC Recover already active.

Explanation: An ADREC RECOVER job is already active for this application. Only one ADREC RECOVER job can be active at a time for a specific application.

User response: Resubmit the ADREC RECOVER after the other ADrec job finishes.

Database number-1 (hexstring-1)not defined in an application.

Explanation: A copy was found for an object in DB2 database number-1. However, this DB2 database is not currently defined to any ADrec application.

User response: No action is required.

Job string-1 (string-2) submitted for Striplog string-3.

Explanation: A STRIPLOG job (name string-1, job number string-2) has been submitted to perform a GENERATE or CONSOLIDATE (string-3).

User response: No action is required.

Waiting for Striplog string-1 job string-2 (string-3) to string-4.

Explanation: ADrec is waiting for STRIPLOG GENERATE or CONSOLIDATE (string-1) job (namestring-2, job number string-3) to START or COMPLETE (string-4).

User response: No action is required.

Waiting for number-1 Striplog jobs to complete (number-2 have started and number-3 have completed).

Explanation: ADrec is waiting for number-1 STRIPLOG jobs to complete. So far, number-2 STRIPLOG jobs have started and number-3 STRIPLOG jobs have completed.

User response: No action is required.

The DDNAME string-1 was not found in the JCL.

Explanation: The DDNAME was specified in one of the ADREC JCL parameters but was not found in the job's JCL.

User response: Add the specified DDNAME to the job's JCL and re-run the ADREC JCL job.

No ADREC PREPARE was processed since the last Consolidate, NOPURGE option forced.

Explanation: ADREC PREPARE should be run prior to an ADREC STRIPLOG CONSOLIDATE.

User response: Run an ADREC PREPARE and then an ADRREC STRIPLOG CONSOLIDATE.

Job string-1 (string-2) submitted for LOGSPLIT.

Explanation: A LOGSPLIT job (name string-1, job number string-2) has been submitted.

User response: No action is required.

Waiting for LOGSPLIT job string-1 (string-2) to string-3.

Explanation: ADrec is waiting for LOGSPLIT job (name string-1, job number string-2) to START or COMPLETE (string-3).

User response: No action is required.

Restart error for Recover. Parameter string-1

Explanation: ADREC RECOVER restart encountered an error with the current restart status file (string-1)

User response: Correct the error and resubmit the ADREC RECOVER. Contact BMC Support.

Passed FNC invalid, base section not ADREC.

Explanation: ADREC RECOVER has encountered an internal processing error.

User response: Contact BMC Support.

Passed FNC invalid, ADREC section not Recover.

Explanation: ADREC RECOVER has encountered an internal processing error.

User response: Contact BMC Support.

Waiting for number-1 Restores/ number-2 LogSplits/ number-3 LogApplys to complete (number-4 objects).

Explanation: ADrec is waiting for number-1 RESTORE jobs, number-2 LOGSPLIT jobs, and number-3 LOGAPPLY jobs to complete for number-4 DB2 objects.

User response: No action is required.

LogApply job failed to submit for copy number number-1.

Explanation: ADrec attempted to submit a LOGAPPLY job and the submit failed.

User response: Check SYSLOG for any error messages concerning JOB submission. Contact BMC Support.

Status Update failed for LogApply submit (copy number number-1).

Explanation: ADrec attempted to update the status table with information about a LOGAPPLY job. The status table update failed.

User response: Check SYSLOG and CDBPRINT for any error messages concerning status table updates. Contact BMC Support.

StripLog string-1 job failed to submit.

Explanation: ADrec attempted to submit a STRIPLOG GENERATE or CONSOLIDATE (string-1) job and the submit failed.

User response: Check SYSLOG for any error messages concerning JOB submission. Contact BMC Support.

Status insert failed for StripLog string-1.

Explanation: ADrec attempted to insert into the status table information about a STRIPLOG GENERATE or CONSOLIDATE job (String-1). The status table insert failed.

User response: Check SYSLOG and CDBPRINT for any error messages concerning status table inserts. Contact BMC Support.

Status update failed for StripLog string-1.

Explanation: ADrec attempted to update the status table with information about a STRIPLOG GENERATE or CONSOLIDATE job (String-1). The status table update failed.

User response: Check SYSLOG and CDBPRINT for any error messages concerning status table updates. Contact BMC Support.

Job not submitted - previous job string-1 (string-2) has not completed execution.

Explanation: ADrec was prepared to submit a batch job to perform a STRIPLOG. However, a STRIPLOG was previously submitted to perform this STRIPLOG and this job is still executing.

User response: No action is required.

Job string-1 (string-2) submitted for Validate.

Explanation: ADrec submitted to submitted a job (name string-1, job number string-2) to perform a VALIDATE.

User response: No action is required.

Validate job failed to submit.

Explanation: ADrec attempted to submit a VALIDATE job and the submit failed.

User response: Check SYSLOG for any error messages concerning JOB submission. Contact BMC Support.

Status insert failed for Validate.

Explanation: ADrec attempted to insert into the status table information about a VALIDATE. The status table insert failed.

User response: Check SYSLOG and CDBPRINT for any error messages concerning status table inserts. Contact BMC Support.

Status update failed for Validate.

Explanation: ADrec attempted to update the status table with information about a VALIDATE job. The status table update failed.

User response: Check SYSLOG and CDBPRINT for any error messages concerning status table updates. Contact BMC Support.

Waiting for Validate job string-1 (string-2) to string-3.

Explanation: ADrec is waiting for VALIDATE job (name string-1, job number string-2) to START or COMPLETE (string-3).

User response: No action is required.

Purge processing started for the DBID PSID files.

Explanation: ADREC STRIPLOG CONSOLIDATE has started the purge process for the DBID/PSID log data. Any log data older the oldest retained COPY will be purged.

User response: No action is required.

Purge processing completed for the DBID PSID files, a total of number-1 tracks were released.

Explanation: ADREC STRIPLOG CONSOLIDATE has completed the purge process for the DBID/PSID log data. A total of number-1 tracks were released and made available for reuse in the ADrec LOG file.

User response: No action is required.

Purge processing for DBID hexstring-1 PSID hexstring-2 - number-1 tracks released.

Explanation: ADREC STRIPLOG CONSOLIDATE has completed the purge process for the specific DBID/PSID log data. A total of number-1 tracks were released and made available for reuse in the ADrec LOG file.

User response: No action is required.

Striplog data for DBID hexstring-1 PSID hexstring-2 has been expired, number-1 tracks released.

Explanation: ADREC STRIPLOG CONSOLIDATE has found expired log data for the specific DBID/PSID. The log data was purged. A total of number-1 tracks were released and made available for reuse in the ADrec LOG file.

User response: No action is required.

No copies found for DBID hexstring-1 PSID hexstring-2, log data for this object will expire in number-1 days.

Explanation: ADREC STRIPLOG CONSOLIDATE has found log data for the specific DBID/PSID but an ADrec COPY record does not exist for the DBID/PSID. The log data will be purged in number-1 days.

User response: No action is required.

SQL statement exceeds maximum allowed (32k).

Explanation: ADrec attempted to build a dynamic SQL statement but exceeded the DB2 32K limited for a SQL statement.

User response: Check SYSLOG and CDBPRINT for any error messages concerning SQL statements. Contact BMC Support.

Exclude wildcard entry is invalid (excluding all).

Explanation: The EXCLUDE wildcard entry is invalid. It is attempting to exclude all databases and table spaces (i.e., %.%)

User response: Correct the EXCLUDE wildcard specification and retry the job.

Exclude list successfully updated.

Explanation: The EXCLUDE list was successfully updated with the new wildcard definitions.

User response: No action is required.

Exclude List contains the following tablespaces:

Explanation: The EXCLUDE list currently contains the following table spaces.

User response: No action is required.

Exclude List not currently defined.

Explanation: An ADREC UPDATE UNEXCLUDE was attempted, but the EXCLUDE list currently does not contain any entries.

User response: No action is required.

Unexclude entry string-1.string-2 not found in Exclude List.

Explanation: An ADREC UPDATE UNEXCLUDE was attempted, but the EXCLUDE list currently does not contain the specified entry.

User response: No action is required.

number-1 SYSTABLESPACE rows to be processed.

Explanation: ADREC PREPARE is building the database and table space name table and found number-1 rows in SYSIBM.SYSTABLESPACE.

User response: No action is required.

Database and tablespace name file already exists for copy number number-1.

Explanation: ADREC PREPARE is building the database and tablespace name table and found the name table already exists for COPY number number-1.

User response: No action is required.

SQL error or no rows returned from SYSIBM.SYSTABLESPACE.

Explanation: ADREC PREPARE is building the database and tablespace name table and encountered an error while processing SYSIBM.SYSTABLESPACE.

User response: Check SYSLOG and CDBPRINT for any error messages concerning SQL statements. Contact BMC Support.

Database and tablespace name table created with key number-1.

Explanation: ADREC PREPARE has built a database and tablespace name table with the specified key (number-1).

User response: No action is required.

Open in progress for ADREC string-1 dataset.

Explanation: The described data set is being opened.

User response: No action is required.

number-1 tracks in dataset

Explanation: The size of the LOG or CTL data set is described.

User response: No action is required.

Open failed for string-1 dataset

Explanation: The open failed for the described data set.

User response: The messages that immediately follow will give additional information about the failure. If these messages are not sufficient to diagnose the error, contact BMC Support.

No pages changed for hexstring-1 - hexstring-2.

Explanation: The split log step has found no changed pages for the dbid-psid in the message.

User response: No action is required.

LogSplit starting, Ending RBA = hexstring-1.

Explanation: This message gives the ending RBA for the logsplit that is starting.

User response: No action is required.

LogSplit must be run from Recovery.

Explanation: This message indicates that recovery has not been run.

User response: This message is issued after detecting that a recovery status table does not exist. Recovery must be run before splitlog.

LogSplit status entry does not exist.

Explanation: This message indicates that the ADrec status database does not contain a record for the current object.

User response: This message is issued after detecting that a the ADrec status database does not have a record for the current object. Check the message logs from previous jobs to determine the problem. If the problem cannot be determined, contact BMC Support.

Error retrieving LogSplit status.

Explanation: An error occurred while retrieving status for the current logsplit.

User response: An error occurred retrieving status for the current logsplit. Check the message log for information about the error. If the problem cannot be determined, contact BMC Support.

Beginning analysis of UOW trackset.

Explanation: The uow trackset analysis has begun.

User response: No action is required.

number-1 tracks in UOW trackset.

Explanation: The uow trackset analysis has determined the number of tracks in the uow trackset.

User response: No action is required.

ADREC Database/Tablespace name table not defined.

Explanation: ADrec attempted to retrieve the database and tablespace name table but the table does not exist.

User response: Run ADREC PREPARE to build the database and tablespace name table.

ADREC not found in system.

Explanation: The attempt to locate the ADrec member in the SYSPDS data set failed.

User response: This is an informational message. ADrec functions will fail.

No applications defined to ADREC.

Explanation: No application entries were found in the application table. The Copy by Application request will fail.

User response: Ensure that you have defined your applications to ADrec.

ADREC applications were not defined using string-1.

Explanation: The special keywords 'ALL' or 'BYDB' were not used when the applications were defined to ADrec.

User response: The COPY APPLICATION statement will fail.

ADREC Application string-1 not defined or contains invalid data.

Explanation: The specified application has not been defined to ADrec or database(s) contain invalid data, as identified by a prior message. The return code from APRAPCPY is 8.

User response: The COPY APPLICATION statement will fail.

Translate tables file already exists for copy number number-1.

Explanation: ADREC PREPARE is building the translate table and found the table already exists for COPY number number-1.

User response: No action is required.

SQL error or no rows returned from SYSIBM.SYSSTRINGS.

Explanation: ADREC PREPARE is building the translate table and encountered and error while processing SYSIBM.SYSSTRINGS.

User response: Check SYSLOG and CDBPRINT for any error messages concerning SQL statements. Contact BMC Support.

Translate tables entry created with key number-1.

Explanation: ADREC PREPARE has built a translate table with the specified key (number-1).

User response: No action is required.

DBD table entry created with key hexstring-1.

Explanation: ADREC COPY processing has created a DBD table entry with the specified key.

User response: No action is required.

DBD extract failed for DBID hexstring-1 PSID hexstring-2.

Explanation: ADREC COPY processing encountered an error while attempting to extract DBD information for the specific DBID/PSID combinations.

User response: Check SYSLOG and CDBPRINT for any error messages. Contact BMC Support.

DBD table entry already exists for key hexstring-1.

Explanation: A DBD table entry already exists with the specified key. A new entry will not be created.

User response: No action is required.

Prepare Table entry created with key number-1.

Explanation: ADREC PREPARE has created a prepare table entry for the COPY whose copy number is number-1.

User response: No action is required.

Storage group string-1 not found in Stogroup Table.

Explanation: The ADrec storage group table did not contain an entry for string-1.

User response: Check SYSLOG and CDBPRINT for any error messages. Contact BMC Support.

number-1 Name Table rows deleted using key number-2.

Explanation: ADREC PREPARE has deleted number-1 rows from the database and tablespace name table. Rows up to and including copy number number-2 have been deleted.

User response: No action is required.

number-1 Translate Table rows deleted using key number-2.

Explanation: ADREC PREPARE has deleted number-1 rows from the translate table. Rows up to and including copy number number-2 have been deleted.

User response: No action is required.

ADREC unload starting.

Explanation: ADREC UNLOAD function is starting.

User response: No action is required.

ADREC load starting.

Explanation: ADREC LOAD function is starting.

User response: No action is required.

Unload DDNAME (string-1) not found.

Explanation: ADREC UNLOAD DDNAME string-1 was not found.

User response: ADREC UNLOAD job terminates. Correct the DDNAME specification and resubmit the job.

Load DDNAME (string-1) not found.

Explanation: ADREC LOAD DDNAME string-1 was not found.

User response: ADREC LOAD job terminates. Correct the DDNAME specification and resubmit the job.

ADREC unload complete (number-1 records unloaded).

Explanation: ADREC UNLOAD has completed and has written number-1 records to the unload file.

User response: No action is required.

ADREC load complete (number-1 records loaded).

Explanation: ADREC LOAD has completed and has processed number-1 records from the unload file.

User response: No action is required.

string-1 tablespace is empty (0 rows unloaded).

Explanation: ADREC UNLOAD did not find any rows in the string-1 table.

User response: No action is required.

Copy file is empty (0 rows unloaded).

Explanation: ADREC UNLOAD did not find any rows in the COPY file.

User response: No action is required.

Action file is empty (0 rows unloaded).

Explanation: ADREC UNLOAD did not find any rows in the ACTION file.

User response: No action is required.

Application file is empty (0 rows unloaded).

Explanation: ADREC UNLOAD did not find any rows in the APPLICATION file.

User response: No action is required.

Additional volume needed for dataset (DSN). Specify VOLSER or * for SMS.

Explanation: One of the ADrec data sets is full and either needs to extend to another volume or allocate another data set. A DASD volume is needed to for this to complete.

User response: Reply to the outstanding WTOR with a DASD volume serial to which ADrec can expand. Contact BMC Support.

Specified object not found in catalog, DB=string-1, TS=string-2.

Explanation: One of the names in the INCLUDE list is not defined to DB2.

User response: The APPLICATION DEFINE will fail.

Prepared copy entry not found for string-1. string-2 part number-1 .

Explanation: ADREC DELTA did not find a prepared copy entry for the DB2 object (string-1.string-2).

User response: Run ADREC COPY (if needed) to copy the DB2 object and then run ADREC PREPARE to 'prepare' the copy entries.

ADREC DELTA Table string-1.string-2 created in string-3. string-4

Explanation: The ADREC DELTA table (string-1.string-2) has been created in DB2 database and tablespace identified by string-3.string-4.

User response: No action is required.

ADREC DELTA Index string-1.string-2 created on table string-3.string-4

Explanation: An Index (string-1.string-2) has been created on the ADREC DELTA table (string-3.string-4).

User response: No action is required.

ADREC DELTA Table string-1.string-2 dropped.

Explanation: The ADREC DELTA table (string-1.string-2) has been dropped.

User response: No action is required.

No DBID/PSID entries found, there is nothing to consolidate.

Explanation: ADREC STRIPLOG CONSOLDATE did not find any DBID/PSID entries in the LOG file.

User response: No action is required.

DELTA RBA not the same for all application objects (hexstring-1/hexstring-2).

Explanation: ADREC DELTA has found that the DELTARBA value for all objects defined in the DELTA application is not the same. For ADREC DELTA to work properly, all objects must have the same DELTARBA.

User response: Either delete the entries from the DELTA table or update the DELTARBA to be the same for all objects in the DELTA application. Contact BMC Support.

No log data available for use by ADREC Delta. Verify correct BSDS specified.

Explanation: ADREC DELTA did not find any log data in the log file.

User response: Verify the BSDS specified in the ADREC DELTA sysin is the correct BSDS. Contact BMC Support.

DELTA Table successfully updated: number-1 rows updated and number-2 rows inserted.

Explanation: ADREC DELTA successfully update the DELTA table (Number-1 rows were updated and number-2 rows were inserted).

User response: No action is required.

DELTA StripLog Validate failed. string-1 point hexstring-1 not found.

Explanation: ADREC DELTA striplog validation failed. The START or END (string-1) time specified not found in the LOG file.

User response: Verify the STARTTIME and ENDTIME specified is valid. Call BMC Support for assistance.

StripLog file is invalid, unable to continue.

Explanation: ADREC DELTA striplog validation failed. The STRIPLOG file is empty or contains invalid data.

User response: Contact BMC Support.

The initial size of the CNTL file must be at least 51 tracks. Unable to format the CNTL file.

Explanation: The ADrec CNTL file must be at least 51 tracks in size.

User response: Change the ADREC DEFINE statement to increase the allocation of the CNTL data set. Contact BMC Support.

ADREC Define JCL must be run before jobs may be submitted.

Explanation: ADrec attempted to customize the JCL needed for a batch job. However, the JCL for the job was not found in the ADrec database.

User response: Define the JCL needed by ADrec using the DEFINE JCL statement. Contact BMC Support.

PREPAREX Table entry created with key number-1.

Explanation: A row has been created in the PREPAREX table with a key of number-1.

User response: No action is required.

Directory/Catalog Prepare entry updated (copy num = number-1).

Explanation: A ADREC PREPARE table row (copy number = number-1) for a DB2 Directory or Catalog table has been updated with information from the DB2 log file.

User response: No action is required.

Copy file is empty. ADREC Prepare needs to be run.

Explanation: The ADrec COPY file is currently empty. An ADREC PREPARE needs to be run to create and fill in the COPY file.

User response: Run an ADREC PREPARE. Contact BMC Support.

Prepared COPY entry not found for string-1.string-2 (RBA= hexstring-1).

Explanation: ADREC DELTA did not find and copy information in the COPY file for the specified DB2 object (string-1.string-2).

User response: If recent copies have been made for the DB2 object, run an ADREC PREPARE. Contact BMC Support.

LogApply starting for Tablespace tableSpaceName part number-1 instance number-2.

Explanation: The current task has started the process to apply log records on behalf of the above named tablespace and part number. The instance number indicates the version of the log records bounded by different recovery points (such as REORG's).

User response: No action is required.

Image Copy opened DSN=string-1.

Explanation: The above named data set is an image copy of the space that will participate in the logapply process indicated by message NGTY210.

User response: No action is required.

Logread complete. total=number-1 applied=number-2 skipped=number-3

Explanation: All log records for the current logapply process has been processed. This message shows log records statistics. The skipped count will be non zero if the participating image copy is a SHRLEVEL CHANGE COPY

User response: No action is required.

LOGAPPLY PHASE complete. pages=number-1 rows=number-2

Explanation: The current task has completed the process that was started earlier and indicated by message NGTY210. This message shows the total number of affected data pages and the total number of changed rows.

User response: No action is required.

number-1 rows discarded from Table tableName part number-2 due to WHERE clause.

Explanation: This message is a response to the 'WHERE' clause specification on the ADREC DELTA statement for the above named table and part number. It shows the total number of rows discarded that did not satisfy the WHERE clause criteria.

User response: No action is required.

Unload phase starting for Table tableName part number-1.

Explanation: The final phase of the ADREC DELTA statement for the above named table and part number has just started by the current task. REXX EXEC 'XULDDYNM' will be driven to supply data set names for the UNLOAD phase.

User response: No action is required.

Error opening UNLOAD file DDNAME (string-1).

Explanation: The Unload phase of the current table has failed due to a file open error.

User response: Look for error message in the JOB's LOG relating to this DDname. Correct the error and rerun the job.

number-1 records written to DSN=string-1.

Explanation: The ADREC DELTA UNLOAD phase for the current table has completed. This message shows the number of records written to the above named data set. The data set could be an unload file or an SQL commands file.

User response: No action is required.

Scheduling number-1 DELTA processes in number-2 threads.

Explanation: This message shows the number of tablespace images that will undergo LogApply as well as the degree of parallelism to achieve the work.

User response: No action is required.

number-1 rows not selected from Table tableName part number-2 .

Explanation: The above named table and part number have had delta changes but none was processed because the table name was not selected via the SELECT clause of the ADREC DELTA command.

User response: No action is required.

MASS DELETE on Table tableName incompatible with any SQL output format.

Explanation: A mass delete event has been detected on the above named table. SQLUNDO and RBAUNDO processing can not undo a mass delete performed on a table not having the 'DATA CAPTURE CHANGES' attribute.

User response: In order to skip the above event, you must code a where clause that excludes this event from SQLUNDO or RBAUNDO processing. For example: 'WHERE G.EVENT <> 'M''

SQL STMTS=number-1 for 'string-1.string-2' update=number-2 delete=number-3 insert=number-4.

Explanation: This message shows the total number of SQL statements generated for the above named TABLE and the break down of the total by activity type. The total does not include internally generated 'COMMIT' statements.

User response: No action is required.

Log (string-1) - not yet processed.

Explanation: The specific DB2 LOG data set (string-1) has not yet been processed.

User response: No action is required.

Member (string-1) - INITRBA (hexstring-1) last consolidate point (hexstring-2).

Explanation: The INITRBA and last consolidate point for the specified member is shown.

User response: No action is required.

ADREC DELTA complete for Tablespace tableSpaceName part number-1.

Explanation: The current task has successfully completed the ADREC DELTA statement for the above named tablespace and part number.

User response: No action is required.

Unable to determine the INITRBA value. Run copies or specify an INITRBA value.

Explanation: ADREC STRIPLOG GENERATE was unable to determine a starting point (initial RBA) for STRIPLOG processing. Running an ADREC COPY will provide a starting point or specify one using INITRBA().

User response: Either run an ADREC COPY or specify an INITRBA() value. Contact BMC Support.

Log skipped (string-1) - string-2.

Explanation: The specific DB2 LOG data set (string-1) was not processed because of the reason (string-2) given.

User response: No action is required.

INITRBA (hexstring-1) established using the copy string-1.

Explanation: The starting point (initial RBA) for DB2 Log processing was established using either the COPY FILE or COPY TABLE (string-1).

User response: No action is required.

ADREC DELTA starting for Application string-1.

Explanation: ADREC DELTA has started for the specific ADrec application (string-1).

User response: No action is required.

DELTA Split 1 starting, Ending RBA = hexstring-1.

Explanation: ADREC DELTA has started to collect DB2 LOG records for SPLIT 1 processing. DB2 LOG records will be collect up to and including the ending RBA.

User response: No action is required.

DELTA Split 2 starting, Ending RBA = hexstring-1.

Explanation: ADREC DELTA has started to collect DB2 LOG records for SPLIT 2 processing. DB2 LOG records will be collect up to and including the ending RBA.

User response: No action is required.

DELTA Split 1 does not contain any changed rows.

Explanation: ADREC DELTA did not find any log records for SPLIT 1 processing.

User response: No action is required.

DELTA Split 2 does not contain any changed rows.

Explanation: ADREC DELTA did not find any log records for SPLIT 2 processing.

User response: No action is required.

Endtime is less than DELTA Time (hexstring-1) for string-1.string-2.

Explanation: The ENDTIME specified is less than the current DELTA TIME for the specific object (string-1.string-2).

User response: Correct the ENDTIME value and resubmit the job.

Copy not found for object (hexstring-1 hexstring-2 hexstring-3) but UOW record (hexstring-4) exists for object.

Explanation: A current COPY was not found for the specified object (DBID PSID PART), but changes for the object were found in the unit-of-work (UOW) file.

User response: COPY the object and run an ADREC PREPARE. Contact BMC Support.

Application string-1 already defined, record skipped.

Explanation: ADREC LOAD already found an application called string-1 defined in the Application file. The Application record found in the LOAD file will be skipped.

User response: No action is required..

Action record for copy number number-1 already defined, record skipped.

Explanation: ADREC LOAD already found an action record, for the Copy Number (number-1) specified, defined in the Action file. The Action record found in the LOAD file will be skipped.

User response: No action is required..

Copy record for copy number number-1 already defined, record skipped.

Explanation: ADREC LOAD already found a copy record, for the Copy Number (number-1) specified, defined in the Copy file. The Copy record found in the LOAD file will be skipped.

User response: No action is required..

Corresponding copy file record not found for action record (copy number number-1), record skipped.

Explanation: ADREC LOAD did not find the Copy File entry associated with the action record (Copy Number = number-1) specified. The Action record found in the LOAD file will be skipped.

User response: LOAD Copy file records before loading action file records. Contact BMC Support.

Corresponding prepare file record not found for copy record (copy number number-1), record skipped.

Explanation: ADREC LOAD did not find the Prepare File entry associated with the copy record (Copy Number = number-1) specified. The Copy record found in the LOAD file will be skipped.

User response: LOAD Prepare file records before loading copy file records. Contact BMC Support.

string-1 record (hexstring-1)already defined, record skipped.

Explanation: ADREC LOAD found a string-1 record already defined to ADrec. The hexstring-1 value is the first 16 bytes of the record. The record found in the LOAD file will be skipped.

User response: No action is required..

string-1 record with key hexstring-1 already defined, record skipped.

Explanation: ADREC LOAD found a string-1 record already defined to ADrec. The hexstring-1 value is the first 16 bytes of the record key. The record found in the LOAD file will be skipped.

User response: No action is required..

The specified Application (string-1) was not found.

Explanation: ADrec Start/Stop Application was unable to locate the specified Application name.

User response: Verify that the application exists by running ADrec Display and rerun the job.

Application string-1 is not valid for 'DEFINE ALL', record skipped.

Explanation: The current ADrec applications were created using 'DEFINE ALL' but LOAD found a record (string-1) which is not valid for 'DEFINE ALL'. The record found in the LOAD file will be skipped.

User response: No action is required..

Application string-1 is not valid for 'DEFINE BYDATABASE', record skipped.

Explanation: The current ADrec applications were created using 'DEFINE BYDB' but LOAD found a record (string-1) which is not valid for 'DEFINE BYDB'. The record found in the LOAD file will be skipped.

User response: No action is required..

There are no tablespaces or indexes to be started or stopped.

Explanation: The ADrec application definition does not contain any table spaces or indexes which are currently defined to DB2.

User response: No action is required..

No copies found for DATABASE number-1 (hexstring-1).

Explanation: No copies were found in the COPY table for this database.

User response: No action is required..

Usable copy (number-1) not found for tablespace tableSpaceName PART number-2.

Explanation: A copy was not found in the COPY table that could be used for this tablespace. Number-1 is the copy version requested (0 = latest, -1 next previous copy, ...).

User response: Either COPY the tablespace or use a more recent version. Contact BMC Support.

LOCATE failed for DSN - string-1.

Explanation: One of the data sets defined in the ADrec Control Member can not be found.

User response: Recover the specified data set or Run an ADREC DELETE followed by an ADREC DEFINE to recreate the data sets.

The dataset defined by DD string-1 must have a RECFM of V, VB, F, or FB.

Explanation: One of the data sets used to supply ADrec with JCL images has an invalid RECFM.

User response: Correct the data set and re-run the job.

The dataset defined by DD string-1 must have an LRECL of 80 bytes or less.

Explanation: One of the data sets used to supply ADrec with JCL images has an invalid LRECL.

User response: Correct the data set and re-run the job.

Error while attempting to find definition of ADREC Application string-1.

Explanation: ADrec encountered an unknown error while trying to locate the definition of Application string-1.

User response: Verify the Application has been defined and exists in the ADrec database. Contact BMC Support.

ADREC Recover Application requires DB2 to be active.

Explanation: ADrec determined that DB2 was not active or the process was running with 'NOCONNECT' specified.

User response: Verify that DB2 is active and that 'NOCONNECT' is not specified.

The DB2 catalog can not be recovered using ADREC Application Recover.

Explanation: ADrec Recover Application can not recover the DB2 Catalog. You must use ADrec Disaster Recovery to recover the Catalog.

User response: Run ADrec Disaster Recovery. Contact BMC Support.

Adding initial DBID-PSID-PART entries to STATUS Table.

Explanation: ADrec Recover Application has started adding entries to the Status Table based upon the Copy Tree.

User response: No action is required..

Waiting for Pre-Validation Queue, number-1 objects left to be processed.

Explanation: ADrec is waiting for number-1 Pre-Validation objects to complete.

User response: No action is required..

ADREC Application Recovery Update Check processing started.

Explanation: ADREC has started the application recovery update check process.

User response: No action is required..

Update Check Split starting, Starting RBA = hexstring-1.

Explanation: ADrec has started the update check split process for the listed Starting RBA.

User response: No action is required..

Changes found after specified End RBA for Tablespace number-1 - number-2 - number-3 (DBID-PSID-PART).

Explanation: ADREC has determined that the object identified by the specified DBID/PSID/PART contained updates after the End RBA. The status of this tablespace will now be set to RESTORE.

User response: No action is required..

Tablespace status changed to RESTORE for Tablespace number-1 - number-2 - number-3 (DBID-PSID-PART).

Explanation: ADREC has determined that the object identified by the specified DBID/PSID/PART contained updates after the End RBA. The status of this tablespace will now be set to RESTORE.

User response: No action is required..

Indexspace number-1 - number-2 (DBID-OBDI) set to REBUILD status.

Explanation: ADrec has set the status for the above referenced index space to REBUILD in the Status Table.

User response: No action is required..

Indexspace number-1 - number-2 - number-3 (DBID-OBID-PART) status entry deleted.

Explanation: ADREC has deleted the Status Table entry for the index space identified by the referenced DBID/OBID/PART value.

User response: No action is required..

ADREC Application Recovery Update Check processing completed.

Explanation: ADREC has completed the Recovery Update Check process.

User response: No action is required..

No copies of type string-1 found.

Explanation: ADrec found copies but none for the user requested type (LP, LB, RP, RB).

User response: Rerun the job requesting a different COPYTYPE.

ADREC Pre-Validation started for string-1.string-2 part number-1.

Explanation: ADrec Recovery pre-validation has started for the listed object.

User response: No action is required..

ADREC Pre-Validation completed for object.

Explanation: ADrec Recovery pre-validation has completed for an object.

User response: No action is required..

Waiting for Striplog Queue, number-1 objects left to be processed.

Explanation: ADrec has found DB2 archive logs which need to be stripped. ADrec is currently stripping these logs and is waiting for number-1 logs to be stripped before continuing.

User response: No action is required..

number-1 SYSINDEXES rows to be processed.

Explanation: ADREC PREPARE is has queried SYSINDEXES to get index names. ADrec has found number-1 rows in SYSINDEXES to be processed.

User response: No action is required..

Application string-1 is not defined as a DELTA Application.

Explanation: ADrec Application string-1 was not defined as a Delta application. Delta can only be run using applications defined as a Delta application (e.g., uses INCLUDE to define table spaces in the application).

User response: Rerun the job using a Delta application.

Waiting for work to complete, number-1 objects left to be processed.

Explanation: ADrec is waiting for number-1 objects to complete.

User response: No action is required..

STARTTIME/STARTRBA error. STARTTIME/STARTRBA must be less than ENDTIME/ENDRBA.

Explanation: The start time/start RBA (LRSN) specified is greater than or equal to the end time/end RBA (LRSN) specified. The start time/start RBA (LRSN) must be less than the end time/end RBA (LRSN).

User response: Rerun the job specifying a different start time/start RBA (LRSN).

ADREC Validation started for string-1.string-2 part number-1.

Explanation: ADrec Recovery validation has started for the listed object.

User response: No action is required..

ADREC Validation completed for string-1.string-2 part number-1.

Explanation: ADrec Recovery validation has completed for the listed object.

User response: No action is required..

ADREC Index Rebuild started for number-1.number-2.number-3 (DBID.OBID.PART).

Explanation: ADrec Index Rebuild has started for the listed object.

User response: No action is required..

ADREX Index Rebuild completed for number-1.number-2.number-3 (DBID.OBID.PART).

Explanation: ADrec Index Rebuild has completed for the listed object.

User response: No action is required..

ADREC Validation failed for string-1.string-2 part number-1 (error code number-2).

Explanation: ADrec Recovery validation failed for the listed object. The ADrec Recovery status table should give an indication of why the validation failed.

User response: Correct the error and rerun the job.

Server selected string-1.string-2 part number-1 for string-3 processing.

Explanation: The ADrec Recovery Server has selected the specified object for the indicated process.

User response: No action is required..

CDBPRINT output found in DDNAME string-1, SYSERROR output found in DDNAME string-2.

Explanation: The user should look in the specified DDNAMEs for output associated with the object. This message is related to message NGTY282.

User response: No action is required..

'ADREC DEFINE' cannot be used when control record exists.

Explanation: An 'ADREC DEFINE' is being attempted but an ADrec control records was found. This indicates that and 'ADREC DEFINE' has already been performed.

User response: To redefine the ADrec data sets, an 'ADREC DELETE' must be run before running the 'ADREC DEFINE'.

'ADREC DELETE' must name existing control datasets.

Explanation: A data set name in the 'ADREC DELETE' statement does not match the data set names found in the ADrec control record.

User response: Correct the data set name and resubmit the job.

'ADREC DEFINE' is required before any other function.

Explanation: An ADrec function is attempting to execute but an 'ADREC DEFINE' has not been performed. An 'ADREC DEFINE' must be performed before any other ADrec function.

User response: Run a 'ADREC DEFINE'

Application string-1 already defined.

Explanation: An ADrec application define is being attempted, but the application was already found in the ADrec database.

User response: Use a different application name or use RESPECIFY to reset the ADrec application definitions.

ADREC Recovery Status record not found for Application string-1.

Explanation: An ADrec Recover status record was not found for the specified application name.

User response: Verify the correct ADrec application was specified. Contact BMC Support.

ADREC Recovery Status Table not built for Application string-1.

Explanation: An ADrec Recover status record was found for the specified application name but the Status table does not exist.

User response: The status table was not created or has been deleted. If status table should exist, contact BMC Support.

Waiting for resource string-1.

Explanation: An ADrec task is waiting for the specified resource.

User response: No action is required..

ADREC Split Check Processing started.

Explanation: ADrec has started the Split Check processing.

User response: No action is required..

No copies found for Tablespace tableSpaceName (hexstring-1.hexstring-2).

Explanation: No copies were found in the COPY table for this tablespace.

User response: No action is required..

No copies found for Tablespace tableSpaceName (hexstring-1.hexstring-2) part number-3.

Explanation: No copies were found in the COPY table for this tablespace partition.

User response: No action is required..

Error opening Copy Report File 'CDBDLRPT'.

Explanation: An error occurred while attempting to open the data set point to by the CDBDLRPT ddname.

User response: Verify the data set pointed to by the CDBDLRPT is valid, contact BMC Support.

Prepare record not found for copy number number-1.

Explanation: The referenced copy does not have an associated entry in the Prepare Table.

User response: If recent copies have been made for the DB2 object, run an ADREC PREPARE. Contact BMC Support.

ADREC COPY started for string-1.string-2 part number-1.

Explanation: ADrec Copy process has started for the listed object.

User response: No action is required..

number-1 objects found in error. Processing halted.

Explanation: The master job has completed its work. Some of the objects processed are in error.

User response: Review the STATUS file and take the appropriate action for the indicated failure. Contact BMC Support.

The main task's UID (string-1) was not found in the SYSPDS.

Explanation: The UID passed to the server was not found in the SYSPDS.

User response: Verify that the SYSPDS used by the master and the server(s) are the same. If the same SYSPDS is referenced by all jobs, contact BMC Support.

THE PRIMARY TASK'S STATUS RECORD WAS NOT FOUND IN THE STATUS FILE.

Explanation: An ADrec Server was started by the Primary's status record could not be found in the ADrec Status file.

User response: Verify the Primary task has not completed and that the Primary's status record still exists. Contact BMC Support.

START ACC(RW) FAILED FOR TABLESPACE tableSpaceName

Explanation: ADrec has determined that a REPAIR LEVELID is needed for the object. However, ADrec's attempt to START the object RW in preparation for the REPAIR LEVELID has failed.

User response: Check CDBPRINT and SYSLOG for any messages explaining why the START failed. Contact BMC Support.

REPAIR LEVELID FAILED FOR TABLESPACE tableSpaceName.

Explanation: ADrec has determined that a REPAIR LEVELID is needed for the object. However, The REPAIR LEVELID has failed.

User response: Check CDBPRINT and SYSLOG for any messages explaining why the START failed. Contact BMC Support.

ERROR OCCURRED WHILE BUILDING COPY TREE.

Explanation: ADrec received an error while building the COPY tree. This can result if ENDRBA specified is lower than the earliest copy, no copies of COPYTYPE were found, etc..

User response: Check CDBPRINT and SYSLOG for any messages explaining why the COPY tree build failed. Contact BMC Support.

BMC TCP/IP SERVER USING HOST number-1. number-2. number-3. number-4 PORT number-5

Explanation: The TCP/IP server has connected to the specified TCP/IP host.

User response: No action is required.

THE NGT TCP/IP LISTENER IS NOW string-1

Explanation: This message shows the TCP/IP Listener status—STARTING or STOPPING.

User response: No action is required.

TCP/IP string-1 ERROR ( RETCODE = number-1 ERRNO = number-2)

Explanation: A TCP/IP call made by the NGT Listener received a non-zero return code. String-1 specifies the TCP/IP call that was being attempted (INITAPI, SOCKET, SOCKOPT, GETHOSTI, BIND, GETSOCKNAME, LISTEN, ACCEPT, READ, WRITE, CLOSE, or TERMAPI).  number-1 provides the return code, and number-2 provides the reason code from the TCP/IP call. 

User response: Contact BMC Support.

ERROR, string-1 VCAT IS string-2, ZPARM IS string-3.

Explanation: The VCAT name (string-2) found in the DSNZPARM (string-1) load module does not match the VCAT specified in the ZPARM keyword (string-3).

User response: Verify DSNZPARM and VCAT specified are correct. Contact BMC Support.

PLACING TABLESPACES ON VALIDATE QUEUE

Explanation: The table spaces are being placed on the VALIDATE queue so they can be validated again. This validation will be down with the DB2 subsystem active.

User response: No action is required..

ERROR, string-1 VCAT IS string-2, ZPARM IS string-3.

Explanation: All the table spaces were successfully placed on the validate queue.

User response: No action is required..

TCP/IP ERROR: DBMGR ENVIRONMENT NOT AVAILABLE.

Explanation: The ADrec TCP/IP server was unable to find an active DBMGR environment.

User response: Verify SYSPDS specified is correct. Contact BMC Support.

TCP/IP ERROR: ERROR READING STATUS FILE.

Explanation: An I/O or other error occurred when the ADrec TCP/IP server attempted to read the STATUS file.

User response: Contact BMC Support.

TCP/IP ERROR: STATUS FILE IS EMPTY.

Explanation: The ADrec TCP/IP server read the STATUS file, but the file is empty.

User response: No action is required..

TCP/IP ERROR: STATUS FILE HEADER IS CORRUPTED.

Explanation: The ADrec TCP/IP server read the STATUS file, but the STATUS file header was corrupted.

User response: Contact BMC Support.

TCP/IP ERROR: STATUS DOES NOT CONTAIN ANY ENTRIES.

Explanation: The ADrec TCP/IP server read the STATUS file, but the file does not currently contain any status information.

User response: No action is required..

TCP/IP RECEIVE BUFFER ERROR (string-1).

Explanation: The ADrec TCP/IP server received a buffer from a client but the data in the buffer was invalid (string-1).

User response: Contact BMC Support.

TCP/IP ERROR: OPEN OF STATUS TABLE FAILED

Explanation: An I/O error occurred when the TCP/IP server attempted to open the STATUS TABLE file.

User response: Contact BMC Support.

TCP/IP ERROR: READ OF STATUS TABLE FAILED

Explanation: An I/O error occurred when the TCP/IP server attempted to read the STATUS TABLE file.

User response: Contact BMC Support.

TCP/IP ERROR: SIZE OF STATUS TABLE IS NOT VALID

Explanation: The TCP/IP server read the STATUS TABLE file, but the size of the next entry was not calculated.

User response: Contact BMC Support.

TCP/IP ERROR: ROW KEY string-1 NOT FOUND IN IDB string-2

Explanation: The TCP/IP server read the STATUS TABLE file, but the locate row function failed or an unexpected end of file occurred.

User response: Contact BMC Support.

TCP/IP ERROR: ERROR READING APPLICATION FILE

Explanation: An I/O error occurred when the TCP/IP server attempted to read the application file.

User response: Contact BMC Support.

TCP/IP SERVER: string-1 COMMAND INVALID

Explanation: The TCP/IP server did not recognize the indicated command (STOP, FORCE, or TRACE) or its length. Processing continues.

User response: No action is required.

TCP/IP ERROR: ERROR BUILDING STATUS OPTIONS

Explanation: The Master Options for the STRIPLOG function failed to build the status option list. Processing terminates.

User response: Contact BMC Support.

SHUTDOWN REQUEST RECEIVED FROM CLIENT

Explanation: The TCP/IP server is closing the connection and terminating.

User response: No action is required.

BMC TCP/IP CLIENT REQUEST ACCEPTED (HOST number-1. number-2. number -3. number-4 PORT number-5 ) 

Explanation: The TCP/IP request for the connection has been accepted on the host system.

User response: No action is required.

SERVER WILL PROCESS WORKTYPE string-1.

Explanation: The ADrec server will process work from the specified work queue.

User response: No action is required.

TCP/IP ERROR: READING UTILTIY JOB INFORMATION

Explanation: The request to receive the master utility information failed. Processing terminates.

User response: Contact BMC Support.

string-1 FAILED FOR string-2 DATA SET

Explanation: The process referenced in string-1 (OPEN or ALLOCATE) failed for the SYSIN data set. string-2 indicates the SYSIN data set.

User response: Contact BMC Support.

TCP/IP ERROR: DB2 IS NOT ACTIVE - FUNCTION FAILED.

Explanation: The requested function requires DB2 services but DB2 is not active.

User response: Rerun the function after DB2 is started.

TCP/IP ERROR: DB2 SQL ERROR.

Explanation: The requested function uses DB2 services but failed.

User response: There should be additional error messages about the error.

TCP/IP ERROR: REQUESTED TABLE NOT FOUND.

Explanation: The requested function specified a table obid that does not exist.

User response: There should be additional error messages about the error.

Striplog File conversion has started.

Explanation: Conversion of the old format Striplog file into the new internal IDB format has begun.

User response: No action is required..

Striplog File conversion has completed.

Explanation: Conversion of the old format Striplog file into the new internal IDB format has completed.

User response: No action is required..

TCP/IP warning: table is empty.

Explanation: The table being processed by the TCP/IP server is empty.

User response: No action is required..

TCP/IP error: table insert error.

Explanation: An error was encountered by the TCP/IP server during the table insert process.

User response: Contact BMC Support.

Striplog Generate has not been run.

Explanation: The Striplog Generate/Striplog Consolidate processes have not been run.

User response: Run a Striplog Generate then re-submit your job.

The Striplog File is empty.

Explanation: The Striplog file is empty.

User response: Run a Striplog Generate then re-submit your job.

Setting split RBA for ActiveStandBy objects

Explanation: The ADREC process is establishing the starting point for the log apply process for each object.

User response: No action is required..

ActiveStandBy history table does not exist. SYNCPOINTRBA() required.

Explanation: The first time ActiveStandBy is executed, the user must provide the SYNCPOINT RBA to be used. Once that job is complete, as objects are updated, ADREC will track the changes to that object.

User response: Specify the SYNCPOINT RBA on the job command and resubmit the job.

string-1.string-2 part number-1'S split RBA set to hexstring-1.

Explanation: The specified object and its associated RBA are listed in this message.

User response: No action is required..

Syntax error - COPIES(0,0) is not supported.

Explanation: The value COPIES(0,0) is not valid and is flagged as a syntax error.

User response: Change one of the COPIES sub parameters to a value greater than zero and re-run the failing job.

Partitioned object(s) with NPI(s) must be manually recovered before ADREC may be run.

Explanation: A destructive function has been done in an individual partition. An NPI exists for this table. This NPI and other parts that were not touched by this destructive function can not be recovered by ADREC. The ADREC processing has terminated.

User response: Remove the object from the application being recovered. This object must be recovered manually. Exclude this object from the recovery process.

Pageset (hexstring-1.hexstring-2.hexstring-3) ActiveStandBy error: LevelID (hexstring-4) greater than SYNCPOINT (hexstring-5)

Explanation: The RBA in the header page is greater than the SYNCPOINT value.

User response: Contact BMC Support.

DBMGR work data set name change ignored (string-1).

Explanation: The data set name received from the DBMGR dynamic allocation routine was ignored.

User response: No action is required..

DBMGR work data set name set to string-1

Explanation: This message identifies the DBMGR work data set name.

User response: No action is required..

Error occurred allocating DBMGR work data set.

Explanation: The DBMGR work data set could not be allocated.

User response: Investigate the associated messages with this error. Attempt to correct the problem. If the problem persists, contact BMC Support.

ActiveStandBy requires DB2 started as a tracker site.

Explanation: ActiveStandBy requires that the target DB2 system be active and available for use in tracker site mode.

User response: Drop the DB2 system. Then start the DB2 system in tracker site mode. Resubmit the job.

Error in Log data for member string-1 ,ending RBA hexstring-1 is less than INITRBA hexstring-2 .

Explanation: A GAP has been detected in the log data for the specified member.

User response: Run a STRIPLOG RESET and then a STRIPLOG GENERATE. If the problem persists, Contact BMC Support.

Advanced DB2 Recovery Auto-Strip server starting.

Explanation: The ADREC Auto-Strip server is now starting.

User response: No action is required..

Auto-Strip server: string-1 command invalid.

Explanation: The indicated command was not recognized by the Auto-Strip server and is considered invalid. The only command recognized by the Auto-Strip server is the STOP command.

User response: No action is required..

Advanced DB2 Recovery Auto-Strip server stopping.

Explanation: The ADREC Auto-Strip server is now stopping.

User response: No action is required..

Auto-Strip Striplog process started.

Explanation: The ADREC Auto-Strip Striplog process is now starting.

User response: No action is required..

Auto-Strip Striplog process completed.

Explanation: The ADREC Auto-Strip Striplog process is now complete.

User response: No action is required..

Auto-Strip sleeping for number-1 minutes.

Explanation: The sleep cycle has started for the Auto-Strip process. The indicated duration is the time that this strip process will sleep.

User response: No action is required..

number-1 log pages processed.

Explanation: This count represents the log pages that are being currently processed.

User response: No action is required..

ADREC processing created or dropped objects.

Explanation: ADREC is processing SYSDBASE log records looking for recently created or dropped objects.

User response: No action is required..

Creating STATUS file entry for new tablespace tableSpaceName. Placing on RESTORE queue.

Explanation: The specified new table space will have an entry created on the STATUS file and it will also be put on the RESTORE queue.

User response: No action is required..

Tablespace tableSpaceName has been dropped. Placing on DELETE queue.

Explanation: The specified tablespace is dropped and is added to the DELETE queue.

User response: No action is required..

Creating STATUS file entry for new index indexName. Placing on REBUILD queue.

Explanation: The referenced new index will have an associated STATUS file entry and will be put on the REBUILD queue.

User response: No action is required..

Index indexName has been dropped. Placing on DELETE queue.

Explanation: The specified index has been dropped and will be put on the DELETE queue.

User response: No action is required..

No objects found for application string-1. Ensure an ADREC Prepare has been run.

Explanation: The specified ADREC application is empty.

User response: Run a PREPARE job then resubmit this failing job.

ADREC processing SYSDBASE log records for renames.

Explanation: The SYSDBASE log records are being processed for renames (i.e., FASTSWITCH(YES) reorganizations).

User response: No action is required..

Adding object string-1.string-2 part number-1 to string-3 list.

Explanation: The specified object has been marked to be drained or started by being put on either the DRAINED or STARTED list.

User response: No action is required..

string-1 objects in string-2 list.

Explanation: All the objects in the DRAIN or START list are being either drained or started.

User response: No action is required..

ADrec Audit TABLE tableName dropped.

Explanation: The specified DB2 table has been dropped.

User response: No action is required..

ADrec Audit TABLE tableName created in string-3.string-4.

Explanation: The specified DB2 table has been created.

User response: No action is required..

ADrec Audit INDEX indexName created on table tableName.

Explanation: The specified DB2 index has been created.

User response: No action is required..

All rows deleted from audit predicate table.

Explanation: The audit predicate table is now empty.

User response: No action is required..

SQL error occurred processing predicate table.

Explanation: An SQL error was encountered while processing the predicate table.

User response: Contact BMC Support.

ADREC Audit IDB table not defined or error.

Explanation: The ADREC Audit IDB table is not defined or an error was encountered while accessing it.

User response: Contact BMC Support.

Audit columns not found for string-1.string-2.

Explanation: ADREC can not find the column records for the specified object.

User response: Verify that the console has been run to create the audit and key columns defined for the referenced table. If the problem persists, contact BMC Support.

Audit key columns length error for string-1.string-2.

Explanation: The total length of all key columns combined can not be greater than 254 bytes in length.

User response: Redefine the key columns for the specified table to reduce the combined key length.

Error inserting predicate value for string-1.string-2 into AUDIT_PREDICATE table.

Explanation: The specified value could not be inserted into the AUDIT_PREDICATE table.

User response: Contact BMC Support.

Change data from string-1.string-2 inserted into string-3. AUDIT_DATA as number-1 rows.

Explanation: Change data from the specified DB2 table was inserted into the Audit Data table.

User response: No action is required..

ADREC string-1 requires DB2 to be active.

Explanation: An error occurred because DB2 is not active. DB2 must be active for ADREC to successfully complete its processing.

User response: Start DB2 and resubmit the failing job.

ADREC string-1 error (index not found or SQL error).

Explanation: An error occurred because an index could not be found or because of a related SQL error.

User response: Contact BMC Support.

UOW Track Index is empty.

Explanation: No entries were found in the UOW track Index.

User response: Run a STRIPLOG RESET job, a STRIPLOG GENERATE job. Once these two jobs have completed successfully, then resubmit this failing job. If the problem persists, contact BMC Support.

Error in UOW index - code (number-1), Index will be rebuilt.

Explanation: An error, identified by CODE, was found in the UOW Track Index during Consolidate processing. The Index will be rebuilt.

User response: No action is required..

ADREC rename started for string-1 string-2.string-3 part number-1.

Explanation: The rename process for the specified object has begun.

User response: No action is required..

ADREC rename completed for string-1 string-2.string-3 part number-1.

Explanation: The rename process for the specified object has completed.

User response: No action is required..

Member string-1 has number-1 saved JCL records:

Explanation: The JCL statements for the specified member are displayed.

User response: No action is required..

COPY LIST BUILD ERROR.

Explanation: An error has occurred while attempting to build the list of objects to be copied.

User response: Contact BMC Support.

DSNZPARM string-1 has tracker site enabled.

Explanation: ActiveStandBy has determined that tracker site flag is still on in the specified DSNZPARM. CRESTART requires a DSNZPARM without the tracker site flag.

User response: Stop DB2 and start it again with tracker site mode turned off. Then, resubmit the failing job.

UOW DBID PDID Index / UOW Track Index mismatch.

Explanation: This indicates that the 2 UOW indexes do not match one another.

User response: Run an ADrec Striplog Consolidate. Then re-run your job. If the problem persists, contact BMC Support.

Unable to gather split information for new object string-1.string-2 part number-1 (hexstring-1).

Explanation: During ActiveStandBy CRESTART processing, a new object was found to have been created. Since DB2 is down, we are unable to gather information need to perform a log apply.

User response: The object must be recovered after the ActiveStandBy CRESTART completes. Contact BMC Support.

Internal Reader (INTRDR) allocation failed.

Explanation: The allocation of the Internal Reader was not successful.

User response: Contact BMC Support.

JCL to be submitted not found (buffer is empty).

Explanation: AUTO-STRIP sent an empty JCL buffer to be submitted.

User response: Contact BMC Support.

AUTO-STRIP Server processing JCL in APRSYNC DD

Explanation: The Auto-Strip server has started processing the JCL in the DD APRSYNC.

User response: No action is required..

AUTO-STRIP Server sending number-1 JCL records to standby host system.

Explanation: The SYNC job is being sent to the TCP/IP server on the standby host system.

User response: No action is required..

AUTO-STRIP Server successfully sent JCL to standby host system.

Explanation: The transfer of the SYNC job to the standby host has been completed by the TCP/IP server.

User response: No action is required..

AUTO-STRIP bypassing sending JCL to standby host system (string-1).

Explanation: The transfer of the SYNC job to the standby host has been bypassed due to the reason indicated in the message.

User response: No action is required..

JCL record expected but not found in APRSYNC DDName.

Explanation: The DD APRSYNC did not contain any JCL records.

User response: Verify that the file referenced by the APRSYNC DD contains valid JCL records. Resubmit the job again. If the failure persists, contact BMC Support.

JCL records found in APRSYNC DDName exceeds maximum allowed records.

Explanation: The records found in the file referenced by the DDName APRSYNC must not exceed 64K in length.

User response: Update the contents in the file referenced by the DDName APRSYNC to contain records less than the maximum allowed (64K). Then resubmit the failing job.

Error occurred attempting to send APRSYNC JCL to standby host.

Explanation: An error has occurred while attempting to send the JCL found in the APRSYNC ddname to the standby system.

User response: Check error logs for TCP/IP or other error messages. Contact BMC Support.

AUTO-STRIP Server using host number-1.number-2.number-3.number-4

Explanation: The AUTO-STRIP server has connected to the specified local TCP/IP host.

User response: No action is required..

AUTO-STRIP connecting to host string-1 (number-1.number-2.number-3.number-4) number-5

Explanation: The AUTO-STRIP server has connected to the specified remote TCP/IP host.

User response: No action is required..

AUTO-STRIP Server submitted string-1 on standby host string-2 .

Explanation: The AUTO-STRIP server has submitted the JCL found in the APRSYNC ddname on the standby host system.

User response: No action is required..

WAITING FOR DB2 SUBSYSTEM string-1 TO STOP.

Explanation: The ADREC utility job is waiting for DB2 to STOP.

User response: No action is required..

BMC TCP/IP SERVER CONSOLE MODULE VERSION = string-1

Explanation: The TCP/IP server is using the specified version of the Console module.

User response: No action is required.

BMC TCP/IP SERVER AUDIT MODULE VERSION = string-1

Explanation: The TCP/IP server is using the specified version of the Audit module.

User response: No action is required.

BMC TCP/IP SERVER JCL MODULE VERSION = string-1

Explanation: The TCP/IP server is using the specified version of the JCL module.

User response: No action is required.

A DBMGR workfile is already defined, Create request failed.

Explanation: An attempt was made to create a DBMGR work file, however a work file is already in use. Only one work file may be in use at a time. The Create request will not be honored.

User response: No action is required.

STARTING SORT OF DELTA RBA RECORDS.

Explanation: FORMAT(RBAREDO) or FORMAT(RBAUNDO) has been specified and DELTA is starting the final SORT (in RBA order) of the records.

User response: No action is required.

SORT of DELTA RBA records completed with a return code of number-1 .

Explanation: The SORT (in RBA order) of the DELTA records has completed.

User response: No action is required.

DELTA RBA unload table is empty. No data to sort.

Explanation: Delta did not produce any change records for FORMAT(RBAREDO) or FORMAT(RBAUNDO) processing. RBA SORT not required.

User response: No action is required.

DELTA RBA encountered an error (Missing DD or OPEN error) with first unload work data set.

Explanation: Delta creates work data sets which are passed to SORT so they can be in RBA order. An error has occurred while trying to allocate or open one of these work data sets.

User response: Verify that the work files still exist and are available. if the failure persists, contact BMC Support.

Error occurred allocating the DELTA RBA data set.

Explanation: An error occurred while attempting to allocated the FORMAT(RBAREDO) or FORMAT(RBAUNDO) output data set.

User response: Verify that the XADRDYNM REXX exec specified correct data set name. If the failure persists, contact BMC Support.

Error occurred building SORT option SORTDD

Explanation: Delta allocates a new DD based on the current SYSOUT DD. The allocation of the new DD failed.

User response: Verify that the SYSOUT DD has been specified in the JCL. If the failure persists, contact BMC Support.

Error occurred sorting DELTA RBA records (hexstring-1).

Explanation: Some error has occurred while attempting to sort the Delta records in RBA order for FORMAT(RBAREDO) or FORMAT(RBAUNDO).

User response: Examine CDBPRINT or SYSERROR DDs for any other error messages. If the failure persists, contact BMC Support.

TCP/IP Error: Table delete error.

Explanation: An error occurred while attempting to delete a record from the AUDIT column information table.

User response: Contact BMC Support.

Workfile not opened, status record not found.

Explanation: An attempt was made to open a DBMGR work file. No such file was found.

User response: No action is required.

Workfile not deleted, status record not found.

Explanation: An attempt was made to delete a DBMGR work file. No such file was found.

User response: No action is required.

REXX EXEC 'XADRDYNM' NOT FOUND

Explanation: The above named REXX EXEC was not found in the CDBEXEC or NGTAUTO PDS library. This EXEC is required in order to dynamically allocate output files generated ADrec.

User response: Add the EXEC to the CDBEXEC or NGTAUTO PDS library and rerun your JOB. If further problems persist, contact BMC Support.

Variable 'string-1' set by Rexx exec 'XADRDYNM' is invalid.

Explanation: The above named REXX variable coded in the ADrec dynamic allocation exit named 'XADRDYNM' is incorrect or does not conform to specification standards.

User response: Correct the value for this variable and rerun your JOB. If further problems persist, contact BMC Support.

'DSNAME' value set by Rexx Exec 'XADRDYNM' is not unique.

Explanation: The REXX variable 'DSNAME' was incorrectly set by the REXX exit to a name that is currently in use by the JOB. It is possible that 'DISP' variable was not set correctly.

User response: Ensure that the DSNAME is unique or change the DISP to 'Keep'. Correct the REXX EXEC and rerun the JOB.

ADrec BSDS Update utility starting.

Explanation: The ADrec BSDS Update utility is starting.

User response: No action is required.

Archive entry already exists in BSDS for string-1 string-2 string-3.

Explanation: The ADrec BSDS Update utility has read the current BSDS and found an entry exists for START RBA/END RBA/START LRSN/END LRSN specified by X'hexstring-1'.

User response: Remove the archive log from the ADrec BSDS Update utility SYSIN or restore the BSDS to an earlier time.

ADrec BSDS Update completed with errors.

Explanation: The ADrec BSDS Update utility completed but detected errors during its execution.

User response: Check the JOB log and SYSLOG for any error messages. Contact BMC Support.

READLOG processing started.

Explanation: The READLOG server process has started and will read an archive log to gather information for the ADrec BSDS update utility.

User response: No action is required.

READLOG processing started.

Explanation: The READLOG server process has started and will read an archive log to gather information for the ADrec BSDS update utility.

User response: No action is required.

READLOG processing completed successfully (number-1 pages read).

Explanation: The READLOG server process has successfully read an archive log to gather information for the ADrec BSDS update utility (number-1 pages were read in the archive log).

User response: No action is required.

STRIPLOG Retrieve processing started.

Explanation: The STRIPLOG Retrieve server process has started and will read offloaded log data and place into the ADrec log repository.

User response: No action is required.

STRIPLOG Retrieve processing completed.

Explanation: The STRIPLOG Retrieve server process has completed. The offloaded log data has been read and placed into the ADrec log repository.

User response: No action is required.

Gap error detected (Missing Archive logs) at RBA hexstring-1 .

Explanation: The ADrec BSDS Update utility has detected that additional archive logs needed to update the BSDS correctly. X'hexstring-1' is the RBA where the gap occurs.

User response: Update the ADrec BSDS Update utilities SYSIN to include the missing archive logs. Contact BMC Support.

STRIPLOG RETRIEVE PROCESSING string-1.

Explanation: The STRIPLOG Retrieve server is processing the specified offload data set.

User response: No action is required.

ADrec PRE-VALIDATE PLACING string-1.string-2 PART number-1 ON RESTORE QUEUE (number-2).

Explanation: ADrec Pre-Validate has determined the object needs to be restored and is placing the object on the restore queue.

User response: No action is required.

COPY TREE IS EMPTY. THERE IS NOTHING TO DO.

Explanation: ADrec Copy has determined that there are no valid copies to be processed.

User response: Verify that copies exist and are defined to ADrec. Ensure there are no Point In Time records with an RBA greater than the most recent Full Image Copy record in SYSIBM.SYSCOPY.

NO LOG DATA FOUND FOR DBID (hexstring-1).

Explanation: Log data does not exist for the named DBID.

User response: No action is required.

NO LOG DATA FOUND FOR OBJECT (hexstring-1) (hexstring-2).

Explanation: Log data does not exist for the named Object/DBIDPSID.

User response: No action is required.

DIRECTORY OR CATALOG APPLICATION DOES NOT EXIST ('NODIRECTORY' OR 'NOCATALOG' SPECIFIED).

Explanation: The DIRECTORY or CATALOG application has not been defined because NODIRECTORY or NOCATALOG was specified on the ADrec DEFINE. This function requires the DIRECTORY and CATALOG applications.

User response: The ADrec job is terminated. Make sure DIRECTORY and CATALOG applications have been defined to the ADrec environment to use this function.

TAPE ANAL FAILED. PAGESET (hexstring-1.hexstring-2.hexstring-3) SHARES VOL string-1 FSN number-1 WITH PAGESET (hexstring-4.hexstring-5.hexstring-6).

Explanation: The same tape has been used multiple times creating different DBID/PSID/PART entries for the same VOLSER/FILESEQNUM indicating discrepancy in the actual tape content.

User response: The job is terminated. Ensure data integrity of all tape contents by not reusing tapes that are required to be analyzed by this function.

ADrec APPLICATION RECOVERY UPDATE WAITING FOR PRE-VALIDATE TO COMPLETE.

Explanation: The Update Check phase requires that all PRE-VALIDATE processing be complete. Some objects were found in PRE-VALIDATE so the Update Check phase is going to wait.

User response: No action is required.

UNEXPECTED RESULT FOR DBID (hexstring-1) PSID (hexstring-2) IN DBD (string-1) ERRCODE (string-2). PROCESSING string-3.

Explanation: The DBID/PSID in the DBD is invalid for the ERRCODE reason. The errors are caused by reuse of the OBID due to DBD changes. Reason: 01 - OBID offset <= 0; 02 - OBID not a PageSet; 03 - OBID not a Related File; 04 - DBD offset <= 0; 05 - OBID not a File.

User response: For +ONERROR(CONTINUE), the Object in error is ignored and processing continues with the next Object, otherwise processing is discontinued. Set +ONERROR accordingly.

UNEXPECTED RETURN CODE (hexstring-1) FROM STATUS DATABASE FUNCTION CODE (hexstring-2). UNABLE TO CONTINUE.

Explanation: The STATUS DATABASE is an integral part of ADrec processing. After attempting the requested access function, the server received the noted return code. As a result, the server is unable to continue processing the requested ADrec function.

User response: The ADrec job is terminated. Make sure that the ADrec environment has been defined correctly and is available and ready to support the requested function.

STATUS DATABASE KEY IS hexstring-1.

Explanation: The Key of the Status Database is placed into the CDBPRINT listing.

User response: No action is required.

INPUT FNC (CODE Xhexstring-1) IS NOT VALID FOR ADrec. UNABLE TO LIST PRIMARY OPTIONS FOR THIS SERVER.

Explanation: The FNC input to this module is not an ADrec type FNC. As a result, the ADrec Primary Options for this particular Server cannot be determined.

User response: Processing continues without determining the ADrec Primary Options for this Server. However be aware that this anomaly should be investigated thoroughly and corrected.

FNC (CODE Xhexstring-1) DOES NOT SPECIFY A VALID ADrec FUNCTION (CODE Xhexstring-2). UNABLE TO LIST PRIMARY OPTIONS.

Explanation: The ADrec FNC input to this module is not for a recognized ADrec function. As a result, the ADrec Primary Options for this particular Server cannot be determined.

User response: Processing continues without determining the ADrec Primary Options for this Server. However be aware that this anomaly should be investigated thoroughly and corrected.

NO PRIMARY OPTIONS ENTRIES FOUND IN IDB.

Explanation: There are no Primary Options available in the IDB. As a result, the ADrec Primary Options for this particular Server cannot be determined.

User response: Processing continues without determining the ADrec Primary Options for this Server. However be aware that this anomaly should be investigated thoroughly and corrected.

ADrec PRIMARY OPTION: --> string-1.

Explanation: This message is repeated to list the ADrec Primary Options specified for the function performed by this Server.

User response: No action is required.

RECOVER SYNCPOINT REQUIRES DB2 TO BE STOPPED. THE DB2 IMAGE IS NO LONGER CONSISTENT.

Explanation: This message is issued if the target DB2 subsystem is found to be active at the start of a Recover Syncpoint process.

User response: The job ends. Stop the target DB2 and restore the consistent image form backups. The re-run the Recover Job.

RBAUNDO HAS ENCOUNTERED A MASS DELETE LOG RECORD (number-1 - hexstring-1).

Explanation: DELTA, with FORMAT(RBAUNDO) specified, has encountered a Mass Delete log record. SQL cannot be generated to UNDO the Mass Delete. This record is ignored.

User response: No action is required.

DUMMY ENTRY ADDED TO THE STATUS FILE FOR DBID (hexstring-1) PSID (hexstring-2) PART (hexstring-3).

Explanation: Copies for a range of parts were requested and some were not found. A dummy copy entry was added for the identified DBID/PSID/PART.

User response: No action is required.

VCAT TRANSLATION NOT FOUND FOR DIRECTORY/CATALOG VCAT (string-1).

Explanation: A VCAT translate for the DB2 Directory and Catalog was not found. ADrec Clone requires a VCAT translate be specified for the VCAT of the DIRECTORY and CATALOG.

User response: The ADrec job is terminated. Specifiy a VCAT translate for the DB2 Directory and Catalog on the CLONE statement and re-submit the job.

EOF NOT FOUND FOR DDNAME string-1 DSNAME string-2.

Explanation: EOF NOT FOUND AFTER ATTEMPTING 256 (MAX) DATA VOLUMES.

User response: No action is required.

TRACING NOW ENABLED FOR TCP/IP SERVER INTERFACE.

Explanation: MODIFY TRACE ON COMMAND ENCOUNTERED.

User response: No action is required.

TRACING NOW DISABLED FOR TCP/IP SERVER INTERFACE.

Explanation: MODIFY TRACE OFF COMMAND ENCOUNTERED.

User response: No action is required.

THE UTILITY ID string-1 IS INVALID FOR TCP/IP.

Explanation: THE UTILITY ID FOR TCP/IP MUST BE TCP FOLLOWED BY 1-5 NUMERIC DIGITS.

User response: TCP/IP is terminated. Correct the Utility ID and then restart TCP/IP.

THE TCP/IP SERVER MAIN SUBTASK FAILED WITH RC= hexstring-1.

Explanation: THE TCP/IP SERVER MAIN SUBTASK ENCOUNTERED A NON-ZERO RETURN CODE.

User response: TCP/IP is terminated. Review all associated messages, correct the problem and then restart TCP/IP.

TCP/IP unable to access UTILITY File.

Explanation: The TCP/IP User Interface was unable to access the UTILITY File.

User response: The requested command requires a UTILITY File. Verify that the correct environment exists.

TCP/IP requested entries not found in UTILITY File.

Explanation: The TCP/IP User Interface was unable to find the requested data in the UTILITY File.

User response: Verify the command entered and that the correct environment exists.

TCP/IP unable to access STATUS File with KEY (string-1).

Explanation: The TCP/IP User Interface was unable to access the identified STATUS File.

User response: The requested command requires the correct STATUS File. Verify the command entered and the keyed file exists.

TCP/IP requested entries not found in STATUS File with KEY (string-1).

Explanation: The TCP/IP User Interface was unable to find the requested data in the identified STATUS File.

User response: The requested command requires the correct STATUS File. Verify the command entered and the keyed file exists.

TCP/IP INFORMATION File (string-1) does not exist.

Explanation: The TCP/IP User Interface was unable to locate the named INFORMATION File.

User response: The requested command requires the correct INFORM File. Verify the command entered and the named file exists.

TCP/IP unable to access INFORMATION File (string-1).

Explanation: The TCP/IP User Interface was unable to access the named INFORMATION File.

User response: The requested command requires the correct INFORM File. Verify the command entered and the named file exists.

TCP/IP requested entries not found in INFO File (string-1).

Explanation: The TCP/IP User Interface was unable to find the requested data in the named INFORMATION File.

User response: The requested command requires the correct INFORM File. Verify the command entered and the named file exists.

TCP/IP INFO File (string-1) has more than one PRIMARY Record.

Explanation: The TCP/IP User Interface expects only a single PRIMARY Record in every INFORMATION File.

User response: Verify the command entered and the named file is correct. Contact BMC Support.

TCP/IP OUTPUT File (string-1) does not exist.

Explanation: The TCP/IP User Interface was unable to locate the named OUTPUT File.

User response: The requested command requires the correct OUTPUT File. Verify the command entered and the named file exists.

TCP/IP unable to access OUTPUT File (string-1).

Explanation: The TCP/IP User Interface was unable to access the named OUTPUT File.

User response: The requested command requires the correct OUTPUT File. Verify the command entered and the named file exists.

TCP/IP requested entries not found in OUTPUT File (string-1).

Explanation: The TCP/IP User Interface was unable to find the requested data in the named OUTPUT File.

User response: The requested command requires the correct OUTPUT File. Verify the command entered and the named file exists.

Scheduling number-1 COLGROUP processes in number-2 threads.

Explanation: This message shows the number of COLGROUPS that will undergo sorting and processing as well as the degree of parallelism to achieve the work.

User response: No action is required.

TCP/IP INFO File (string-1) has invalid Sysin sequence number.

Explanation: The TCP/IP User Interface found an out of sequence Sysin statement in the named INFORMATION File.

User response: The requested command requires the Sysin statements to be in the correct sequence. Contact BMC Support.

number-1 UNRESOLVED POINTER RECORDS, number-2 UNRESOLVED OVERFLOWS

Explanation: DSTATS Tablespace reader found unresolved pointer-overflow records.

User response: This indicates a possibly corrupted tablespace. Diagnostic procedures should be instituted to examine the tablespace data.

UNRESOLVED string-1 ROW, OFLOW RID hexstring-1, PTR RID hexstring-2

Explanation: DSTATS Tablespace reader found unresolved pointer-overflow records. This message is a display of one of the unresolved record. If it is an OVERFLOW record, the PTR RID will be all zeros.

User response: This indicates a possibly corrupted tablespace. Diagnostic procedures should be instituted to examine the tablespace data.

TCP/IP is unable to access DB2 SSID (string-1) with PLAN NAME (string-2).

Explanation: The TCP/IP User Interface was unable to access the named SUBSYSTEM ID of DB2 with the stated PLAN NAME.

User response: The requested command requires a valid DB2 SSID, and PLAN NAME. Processing continues without the use of DB2. If DB2 data is required, correct the problem, and restart the TCP/IP task.

TCP/IP INFO File (string-1) has mismatching SERVER Records.

Explanation: The TCP/IP User Interface expects the correct number of matching SERVER Records in every INFORMATION File.

User response: Verify the command entered and the named file is correct. Contact BMC Support.

THE DBI FUNCTION MUST BE EXECUTED WHILE CONNECTED TO DB2.

Explanation: The DBI function requires DB2 access.

User response: Re-run the job without the 'NOCONNECT' option and when DB2 is active.

BMC TCP/IP SERVER AUTHORIZATION MODULE VERSION = string-1

Explanation: The TCP/IP server is using the specified version of the Authorization module.

User response: No action is required--information only.

TCP/IP unable to access SYSPDS ONES File.

Explanation: The TCP/IP User Interface was unable to access the SYSPDS ONES File.

User response: The requested command requires a SYSPDS ONES File. Verify that the correct environment exists.

THE IP ADDRESS IN THE //IPADDR DATA SET IS NOT VALID

Explanation: The IP address defined in the IPADDR option for the NGTTCPIP statement is incorrect.

User response: Correct the IPADDR specification, and rerun the job.

CDB TCP/IP SERVER CONNECTED HOST number-1. number-2. number-3. number-4 PORT number-5

Explanation: The TCP/IP server has connected to the specified remote TCP/IP host.

User response: No action is required.

diagnostic text

Explanation: This diagnostic/trace message is used by BMC Support.

User response: No action is required.

diagnostic text

Explanation: This diagnostic/trace message is used by BMC Support.

User response: No action is required.

diagnostic text

Explanation: This diagnostic/trace message is used by BMC Support.

User response: No action is required.

diagnostic text

Explanation: This diagnostic/trace message is used by BMC Support.

User response: No action is required.

TCP/IP requested entries not found in SYSPDS ONES File.

Explanation: The TCP/IP User Interface was unable to find the requested data in the SYSPDS ONES File.

User response: Verify the command entered and that the correct environment exists.

TCP/IP unable to access OBJECT REGISTRATION File.

Explanation: The TCP/IP User Interface was unable to access the OBJECT REGISTRATION File.

User response: The requested command requires an OBJECT REGISTRATION File. Verify that the correct environment exists.

TCP/IP requested entries not found in OBJECT REGISTRATION File.

Explanation: The TCP/IP User Interface was unable to find the requested data in the OBJECT REGISTRATION File.

User response: Verify the command entered and that the correct environment exists.

TCP/IP unable to access PRODUCT File.

Explanation: The TCP/IP User Interface was unable to access the PRODUCT File.

User response: The requested command requires a PRODUCT File. Verify that the correct environment exists.

TCP/IP requested entries not found in PRODUCT File.

Explanation: The TCP/IP User Interface was unable to find the requested data in the PRODUCT File.

User response: Verify the command entered and that the correct environment exists.

BMC TCP/IP SERVER CONSOLE UTILITIES INTERFACE VERSION NUMBER = string-1.

Explanation: The TCP/IP server is using the specified version number of the Console Interface.

User response: No action is required.

NON-ZERO RC FROM SQL QUERY. UNABLE TO CONTINUE.

Explanation: The DB2 QUERY to SYSTABLESPACES for the user specified DB.TS did not return any rows.

User response: Review the messages from the QUERY. If no messages are seen, re-run the JOB with +TRACE(255) set.

TCP/IP BUFFER TOO SMALL FOR RTS PRODUCT FILE.

Explanation: TCP/IP buffer is too small to receive the RTS Product file data.

User response: Contact BMC Support.

PARSE ERROR PROCESSING BMC RTS TCP/IP BUFFER.

Explanation: A parse error occurred while parsing the RTS data in the TCP/IP buffer.

User response: Contact BMC Support.

SQL ERROR OCCURRED WHILE DOING A string-1.

Explanation: A SQL error occurred while attempting to change (INSERT, UPDATE, or DELETE) one of the BMC RTS tables.

User response: Contact BMC Support.

TCP/IP BUFFER TOO SMALL FOR AMS PRODUCT DATA.

Explanation: TCP/IP buffer is too small to receive the AMS Product data.

User response: Contact BMC Support.

SCHEDULE TABLE KEY DATA MISSING FROM BUFFER.

Explanation: The Key data for a SCHEDULE Table update was missing from the buffer.

User response: Contact BMC Support.

diagnostic text.

Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages.

User response: No action is required.