Messages NGTR600 through NGTR699

NGTR600

MORE THAN ONE PART RANGE WAS SPECIFIED. COPYLVL PART WILL BE USED FOR databaseName.tableSpaceName

Explanation: An BMC AMI Reorg job specifying +COPYLVL(FULL) or COPYLVL FULL was run on more than one contiguous range of partitions.  The COPYLVL FULL process supports only a single range of partitions.  BMC AMI Reorg forced COPYLVL PART for the referenced object and made individual copies for each partition.

User response: No action is required. The reorganization continues with the COPYLVL PART specification.

NGTR601

RID TRANSLATE TABLE WRITE COMPLETED

Explanation: The current task has just completed the process that was described by message NGTR600.

User response: No action is required.

NGTR602

LOADING RID TABLE FOR PART number-1,EXPECTED RECORDS= number-2

Explanation: This message indicates that the restart record header for part number number-1 has been read successfully. It also shows the number of restart records that have to be read for this partition.

User response: No action is required.

NGTR603

MISMATCH ON RIDS COUNT VS TABLE - INDEX indexName PT(number-1)

Explanation: The read of the named index retrieved a different number of rows than the table the index is on.

User response: Run CHECK INDEX on this index. If there are no errors, then contact BMC Support for further assistance.

NGTR604

MISMATCH ON RIDS COUNT VS NPI READ - INDEX indexName PT(number-1)

Explanation: The named index should be an NPI. The NPI read counted rows by part and compared them to the input counts from the table space read. The number of rows is different. The part number in the message identifies the failing logical part.

User response: Run CHECK INDEX on this index. If there are no errors, then contact BMC Support for further assistance.

NGTR605

ERROR UPDATING RTS TABLES

Explanation: The RTS tables could not be updated.

User response: Ensure that the RTS tables exist and are open. Then re run the job, if necessary.

NGTR606

INSUFFICIENT ROOM FOR PBG X1T

Explanation: There was not enough room for the X1T during the PBG processing.

User response: A logic error has occurred. Contact BMC Support, having available the SNAP dump from the Log PDS.

NGTR607

INSUFFICIENT MEMORY. TABLESPACE IS TOO LARGE TO PROCESS. 

Explanation: The table space size exceeds the maximum size BMC AMI Reorg can process.

User response: The maximum memory limit is reached for utility. Contact BMC Support.

NGTR608

T1 HAS number-1 TAGS

Explanation: This is the number of tags that exceeds the size for the T1 control area.

User response: A logic error has occurred. Contact BMC Support, having available the SNAP dump from the Log PDS.

NGTR609

WINDOW SIZE IS number-1

Explanation: This message shows the size of the paging window in use for restricted resource processing.

User response: No action is required.

NGTR610

SYSTEM RESOURCE SHORTAGE

Explanation: This message reports that a temporary shortage of Auxiliary Storage Manager (ASM) slots has occurred in a particular phase of processing a partitioned table space. BMC AMI Utilities waits for a short time and checks again.

User response: No action is required.

NGTR611

WAITING FOR SYSTEM RESOURCES, REQUIRED SLOTS= number-1

Explanation: This message reports that a temporary shortage of Auxilary Storage Manager (ASM) slots has occurred in a particular phase of reorganizing an index or a non-partitioned table space. Number-1 is the number of slots required. BMC AMI Reorg waits for a short time and checks again.

User response: No action is required.

NGTR612

UNAVAILABLE SYSTEM RESOURCE

Explanation: This message reports that the shortage of Auxiliary Storage Manager (ASM) slots previously reported by message NGTR611 has continued. BMC AMI Reorg immediately cleans up and terminates.

User response: Resubmit the utility when the system load is lighter.

NGTR613

DB2 MAX SIZE EXCEEDED

Explanation: This message reports that there is no more space available in Db2 for the resource. The job is terminated.

User response: This will occur if the data set capacity is exceeded. In which case, reduce the PCTFREE value, and/or increase the FREEPAGE value, so the rows fit within Db2 limits.

NGTR614

TASK STATISTICS: EVENTS=number-1 RWE=number-2 TWE=number-3

Explanation: This message reports some statistics about the degree of multitasking being performed. Number-1 is the number of concurrent tasks, number-2 is the number of object-partitions remaining to to be reorganized, and number-3 is the number of tasks not yet complete (that is, active or yet to start).

User response: No action is required.

NGTR615

SLOT STATISTICS: USABLE=number-1 TOTAL=number-2 AVAILABLE=number-3

Explanation: This message reports some Auxiliary Storage Manager (ASM) statistics. Number-1 is the maximum number of usable local slots, number-2 is the total number of slots defined, and number-3 is the total number of slots available.

User response: No action is required.

NGTR616

INSUFFICIENT SYSTEM RESOURCES FOR THIS UTILITY, ADD AN ADDITIONAL number-1 PAGES

Explanation: BMC AMI Utilities has determined that one of the objects to be processed is simply too large to be accommodated by the current paging configuration. That is, the number of Auxiliary Storage Manager (ASM) slots defined on this system is too low for that object to be processed, even using a minimum-resource strategy, while leaving adequate slots for other users. BMC AMI Utilities terminates.

User response: Unlike the temporary shortages of resources reported by other messages such as NGTR612, this situation is persistent in that it cannot be bypassed by resubmitting the utility at a time when the system load is lighter. Add a further paging volume containing at least number-1 pages.

NGTR617

PBG tableSpaceName CLIX string-3 - READ COMPLETE - RLST = #8, ATB = #8

Explanation: This message summarized resource use to read the clustering index of the named PBG.

User response: No action is required.

NGTR618

PBR tableSpaceName CLIX string-3 - READ COMPLETE - RLST = #8, ATB = #8

Explanation: This message summarized resource use to read the clustering index of the named PBR.

User response: No action is required.

NGTR619

THE COMPRESSION DICTIONARY REMAINS UNCHANGED FOR databaseName.tableSpaceName

Explanation: An attempt was made to rebuild the dictionary but the rebuild process failed to change the current dictionary. The current dictionary does not require an update.

User response: No action is required.

NGTR620

string-1.string-2 (number-1) FRPG=number-2, PCTF=number-3, MXRPP=number-4, USABLE/PG=number-5 BYTES

Explanation: This message is issued by the segmented table space processor when initializing.

User response: No action is required.

NGTR621

string-1.string-2 - SGSZ=number-1, SGNM=number-2, PGS/SPMP=number-3, MAX PGS/PT=number-4 (hexstring-1)

Explanation: This message is issued by the segmented table space processor when initializing.

User response: No action is required.

NGTR622

string-1.string-2 - FILLED ALL PARTS - REACHED MAXPARTS = number-1

Explanation: This message is issued by the segmented table space processor when performing logical reorg.

User response: Try a lower PCTFREE / FREEPAGE. Alternatively, discard some rows as part of the Reorg.

NGTR623

TS WRITE COMPLETE string-1 string-2 (number-1) - number-2 ROWS IN number-3 PAGES

Explanation: This message is issued by the segmented table space to PBG conversion writer when a new output partition is complete.

User response: No action is required.

NGTR624

TS WRITE IN PROGRESS string-1.string-2 (number-1) - number-2 ROWS IN number-3 PAGES

Explanation: This is a progress message issued by the segmented table space to PBG conversion writer.

User response: No action is required.

NGTR625

RESTART DATASET IS NOT COMPATIBLE WITH CURRENT OBJECT, SYMPTOM=hexstring-1, hexstring-2, hexstring-3

Explanation: This message indicates that there is a discrepancy between the data describing the current object on the restart file and in the Db2 catalog. X'hexstring-1' is the DBID. X'hexstring-2' is the OBID. X'hexstring-3' is the Partition number.

User response: Contact BMC Support for further assistance.

NGTR626

PROCESSING ENDED

Explanation: This message is issued by the segmented table space processor when a single table has completed processing.

User response: No action is required.

NGTR627

PROCESSING BEGINS

Explanation: This message is issued by the segmented table space processor when a single indexed table begins processing.

User response: No action is required.

NGTR628

IX indexName - RUNNING TOTAL - #8 RIDS, #8 DELETED RIDS

Explanation: This is a tracing message during NPI translate processing.

User response: No action is required.

NGTR629

UTILITY IS WAITING

Explanation: This message is issued by the segmented table space processor when a single indexed table begins processing, but is inhibited by other processors currently active.

User response: No action required--this is a trace message. If you see many of these, contact BMC Support.

NGTR630

TSRID1 LOAD FAILED, CURRENT PROCESS TERMINATED

Explanation: An error occurred reading the translate RIDs from file SYSUT1, which are needed in order to process the non-partitioning index of a partitioned table space.

User response: Rerun the job with either 'RESTART' or 'RECOVER' parameter option, and, if the problem persists, contact BMC Support.

NGTR631

REORGED PBG PART number-1 EXCEEDS PBG SIZE OF number-2 PAGES

Explanation: When reorganizing a PBG partition, the number of new pages exceeds the maximum size allowed for this type of object.

User response: Rerun the job with different PCTFREE or FREEPG or discard some rows from the input partition.

NGTR632

CALLING NXLM - number-1 RIDS, RSN string-1, number-2 RIDS READ, number-3 KEYS

Explanation: This is a tracing message during NPI translate processing.

User response: No action is required.

NGTR633

NPI ANALYSIS

Explanation: This is a tracing message during NPI translate processing.

User response: No action is required.

NGTR634

- VERY LOW REAL MEMORY AVAILABLE

Explanation: Real memory is not available to get adequate performance during NPI Rid translate. The run will continue.

User response: No action is required.

NGTR635

- EXPECT POOR PERFORMANCE DURING NPI XLATE

Explanation: Real memory is not available to get adequate performance during NPI Rid translate. The run will continue.

User response: No action is required.

NGTR636

WAITING FOR TS ROW FOR number-1 MINUTES

Explanation: The writer subtask is waiting for a row to come available from the read subtask.

User response: The job may need to be cancelled. Take an SVC dump.

NGTR637

TS tableSpaceName IS DEFINED 'NOT LOGGED'. UNSUPPORTED BY CDB

Explanation: NGT Reorg is not able to process 'not logged' table spaces. IBM Reorg must be used on this object.

User response: Remove this SYSIN statement.

NGTR638

REPART NOT SUPPORTED FOR INDEX indexName DUE TO INDEX ORDERING VALUE

Explanation: The repart function does not support table-based partitioned indexes that are not in the same order as the clustering index.

User response: Contact BMC Support.

NGTR639

SOME OBJECTS/PARTITIONS ARE IN REORG_PENDING. DATA IN THESE OBJECTS WILL BE RELOADED

Explanation: Objects can be in REORG pending status for several reasons. The LOAD utility corrects this in all cases. If limit keys have been altered, LOAD will put the rows in the correct partition.

User response: No action is required.

NGTR640

MASSDELETE IS IN PROGRESS FOR THIS OBJECT

Explanation: This message indicates that the current task's object rows will be deleted. This occurs in response to coding MASSDELETE on the REORG statement for a partitioned table space.

User response: No action is required.

NGTR641

INVALID CONDITION: TO BE DELETED ROWS CAN NOT BE UPDATED

Explanation: BMC AMI Reorg has detected an invalid condition where a row subject to discard processing or mass delete has been updated by the user via SQL. This is a terminating error. An S0C3 abend follows this message.

User response: Refrain from updating rows that are subject to discard or mass delete processing.

NGTR642

TS tableSpaceName IX string-3 BEING ALTERED TO PGSIZE number-1

Explanation: A pending Db2 ALTER was issued for this index, changing the pagesize to the specified size. This is based on the ALTER of the BUFFERPOOL.

User response: No action is required.

NGTR643

IX indexName, number-1 PASSES, #8 RIDS WRITTEN OF #8

Explanation: This message shows the progress status for this index writer.

User response: No action is required.

NGTR644

TS tableSpaceName REORG AUX WITH MOVEINLINE. NO RECLUSTERING IS DONE

Explanation: When reorganizing a table space with LOBs and data is to be moved from the LOB to the Base table (MOVEINLINE), no reclustering is performed.

User response: No action is required.

NGTR645

TS tableSpacename REORG AUX. MOVEINLINE IGNORED SINCE NO LOBS HAVE INLINE LENGTH

Explanation: The named table space has no LOB column defined with INLINE LENGTH so no data can be moved. MOVEINLINE is ignored.

User response: No action is required.

NGTR646

TS tableSpaceName COLUMN number-1, INLINE LENGTH DEFINED WITH number-2 BYTES

Explanation: The named table space has a LOB column defined with INLINE LENGTH. Data can be moved.

User response: No action is required.

NGTR647

READING EACH PART OF TS tableSpaceName TO DETERMINE DICTIONARY STATUS

Explanation: The table space is defined with COMPRESS NO, so BMC AMI Reorg must read each partition to determine it contains a compression dictionary.

User response: No action is required.

NGTR648

TS tableSpaceName (number-1) HDRPAGE --> DICTIONARY, BUT NOT THERE

Explanation: The table space is defined with COMPRESS NO and the specified partition has no compression dictionary.

User response: This table space is unusable. Recover the table space and rerun the reorganization.

NGTR649

TS tableSpaceName (number-1) HAS A DICTIONARY

Explanation: The table space is defined with COMPRESS NO. The named partition has a dictionary, so all rows will be decompressed.

User response: No action is required.

NGTR650

ALTER LIMITKEY MUST BE THE ONLY CHANGE PENDING ON TS tableSpaceName

Explanation: Pending changes specified for this table space include a limit key change as well as other pending changes. If a pending limit key change exists, BMC AMI Reorg terminates if other pending changes exist on the table space.

User response: Run a DROP PENDINGDDL SQL statement to remove all changes, then specify only the SQL ALTER statement to change the limit keys. Rerun the reorganization.

NGTR651

STATISTICS INSERT OF SYSIBM.SYSTABLEPART_HIST WAS SUCCESSFUL

Explanation: The Db2 catalog table SYSIBM.SYSTABLEPART_HIST was updated for the table space that message NGTR437 identifies.

User response: No action is required.

NGTR652

STATISTICS INSERT OF SYSIBM.SYSTABLES_HIST WAS SUCCESSFUL

Explanation: The Db2 Catalog table SYSIBM.SYSTABLES_HIST was updated for the table identified by the message NGTR438 which follows.

User response: No action is required.

NGTR653

STATISTICS INSERT OF SYSIBM.SYSTABSTATS_HIST WAS SUCCESSFUL

Explanation: The Db2 Catalog table SYSIBM.SYSTABSTATS_HIST was updated for the table identified by the message NGTR445 which follows.

User response: No action is required.

NGTR654

STATISTICS INSERT OF SYSIBM.SYSCOLDIST_HIST WAS SUCCESS FUL

Explanation: The Db2 Catalog table SYSIBM.SYSCOLDIST_HIST was updated for the table identified by the message NGTR450 which follows.

User response: No action is required.

NGTR655

STATISTICS INSERT OF SYSIBM.SYSINDEXES_HIST WAS SUCCESSFUL

Explanation: The Db2 Catalog table SYSIBM.SYSINDEXES_HIST was updated for the index identified by the message NGTR439 which follows.

User response: No action is required.

NGTR656

STATISTICS INSERT OF SYSIBM.SYSCOLUMNS_HIST WAS SUCCESS FUL

Explanation: The Db2 Catalog table SYSIBM.SYSCOLUMNS_HIST was updated for the table identified by the message NGTR446 which follows.

User response: No action is required.

NGTR657

STATISTICS INSERT OF SYSIBM.SYSINDEXPART_HIST WAS SUCCESSFUL

Explanation: The Db2 Catalog table SYSIBM.SYSINDEXPART_HIST was updated for the index identified by the message NGTR447 which follows.

User response: No action is required.

NGTR658

STATISTICS INSERT OF SYSIBM.SYSINDEXSTATS_HIST WAS SUCCESSFUL

Explanation: The Db2 Catalog table SYSIBM.SYSINDEXSTATS_HIST was updated for the index identified by the message NGTR448 which follows.

User response: No action is required.

NGTR659

number-1 ROWS INSERTED INTO string-1.string-2

Explanation: This message indicates that a number of rows were inserted into a Db2 statistics table.

User response: No action is required.

NGTR660

number-1 ROWS DELETED FROM string-1.string-2

Explanation: This message indicates that a number of rows were deleted from a Db2 statistics table.

User response: No action is required.

NGTR661

NO ROWS FOR TABLE ID hexstring-1

Explanation: There are no rows detected for this table. See the summary IDs report for the name matching the ID. This table has no index.

User response: No action is required.

NGTR662

+DBNAME(NAME) NOT SPECIFIED OR INVALID

Explanation: This reorganization is materializing a pending limit key change, but the +DBNAME parameter is not specified, or the name is invalid. To materialize a pending limit key change, BMC AMI Reorg requires that a work database be present and that you specify the name of this database in the +DBNAME parameter.

User response: Create the database and specify its name in the +DBNAME parameter. Rerun the job step.

NGTR663

DICTIONARY WILL BE string-1. NEW COMPRESSION IS string-2 FOR DB.TS databaseName.tableSpaceName (Part partitionNumber)

Explanation: A new compression type was detected for the indicated partition-by-range (PBR) table space partition. A new compression dictionary will be built or rebuilt as needed.

User response: No action is required.

NGTR665

INDEX CANNOT BE RECOVERED, BECAUSE OF ERROR DURING LOAD OF TSRID1

Explanation: The RIDs translation file could not be loaded due to an I/O error on the SYSUT1 file. This message is always followed by message NGTR666.

User response: Execute the Db2 RECOVER utility against all indexes of this table space. Contact BMC Support to try to determine the cause of the problem.

NGTR666

INDEX MUST BE RECOVERED BY MEANS OF DB2 RECOVER UTILITY

Explanation: This message should be preceded by another that indicates the nature of the problem. This message tells you that you must recover indexes. Other indexes of the current partitioned table space are in an inconsistent state.

User response: Execute the DB2 RECOVER utility against all indexes of this table space.

NGTR667

COMPRESSED INDEX (string-1.string-2) NOT SUPPORTED AT THIS TIME

Explanation: BMC AMI Reorg detected a compressed index and terminated processing.

User response: Contact BMC Support.

NGTR668

CLONED INDEX (indexName) NOT SUPPORTED AT THIS TIME

Explanation: The utility does not support cloned indexes.

User response: Contact BMC Support.

NGTR669

RANDOMIZED INDEX (indexName) NOT SUPPORTED AT THIS TIME

Explanation: The utility does not support randomized indexes.

User response: Contact BMC Support.

NGTR670

CLUSTERING NPI (indexName) NOT SUPPORTED AT THIS TIME

Explanation: The utility does not support clustering nonpartitioned indexes.

User response: Contact BMC Support.

NGTR671

RESTART PROCESSING MEMBER string-1 NOT FOUND, RUN ABORTED

Explanation: The restart processing member string-1 could not be found in the System PDS. Restart is aborted.

User response: If you have modified the System PDS, this is to be expected. If not, there may be some damage. Rerun the job with the option 'NORESTART'. If 'NORESTART' could damage your database, then BMC AMI Reorg will not allow it. (See also message NGTR171.)

NGTR672

RESTART MEMBER string-1 FAILED VALIDITY CHECK, RUN ABORTED

Explanation: The restart processing member string-1 in the System PDS contains invalid data. This problem may occur if the PDS was reblocked with a smaller block size.

User response: Check for any system messages that might help explain the problem. Contact BMC Support.

NGTR673

I/O ERROR PROCESSING MEMBER string-1 PROCESSING TERMINATED

Explanation: The restart processing member string-1 in the System PDS could not be read due to an I/O error.

User response: Check for any system messages that might help explain the problem. Contact BMC Support.

NGTR674

LEAF PAGE CHAIN ERROR - PAGE hexstring-1 - DB2X2LPV = hexstring-2, PRIOR PAGE READ WAS hexstring-3

Explanation: The index leaf page chain appears to be incorrect.

User response: Run Check Index or print the affected pages and contact BMC Support for further assistance.

NGTR675

LEAF PAGE CHAIN ERROR - PAGE hexstring-1 - DB2X2LNX = hexstring-2, PAGE READ WAS hexstring-3

Explanation: The index leaf page chain appears to be incorrect.

User response: Run Check Index or print the affected pages and contact BMC Support for further assistance.

NGTR676

COMPRESSED LOBS ARE NOT SUPPORTED AT THIS TIME FOR TS string-1.string-2.

Explanation: The indicated table space contains compressed LOB data, which the utility does not support.

User response: Contact BMC Support.

NGTR677

REORG ALTER LIMIT KEY ERROR ENCOUNTERED. PROCESSING SKIPPED FOR TS string-1.string-2

Explanation: BMC AMI Reorg detected an unspecified ALTER limit key error and is skipping processing for the specified table space.

User response: No action is required.

NGTR679

M = number-1, S = number-2, MAX = number-3

Explanation: This message shows the average row length of all non-discarded rows in the table space (M =) and the standard deviation of the row lengths (S =).

User response: No action is required.

NGTR680

TSRID1 RECORDER IS WAITING

Explanation: This message indicates that the current task is waiting to record the table space translation RIDs into file SYSUT1. The process currently holding this resource can be identified by a previous NGTR681 message.

User response: No action is required.

NGTR681

TSRID1 RECORDER STARTED

Explanation: The current task has just started recording the new table space translation RIDs into file SYSUT1. Other tasks requesting this resource will queue behind, and could be identified by message NGTR680.

User response: No action is required.

NGTR682

TSRID1 RECORDER ENDED

Explanation: This message marks the end of the table space translation RIDs write to SYSUT1. Exclusive control of the 'TSRID1 RECORDER' resource has been released. As a result, the first waiting task will be activated.

User response: No action is required.

NGTR683

RID TABLE FOR PART(number-1) IS READY, (number-2) ROWS, (number-3) DELETED

Explanation: This message is issued prior to the processing of other indexes of a partitioned table space. Number-1 is the part number which will participate in the translate process, and Number-2 is the number of RIDs or rows in that partition. Number-2 is the number of rows that will be deleted.

User response: No action is required.

NGTR684

OFLOW RID rowID ON PBG tableSpaceName TS WITH LOB PART (number-2) RESTRICTION FOUND 

Explanation: During BMC AMI Reorg with change apply process on LOB PBG tablespace, update occurred on overflow row that will cause the row to be moved to different partition, this is restricted state on BMC AMI Reorg .

User response: Rerun BMC AMI Reorg on that object.

NGTR685

+ALLO(REUSE) IS CHANGED TO +ALLO(USED) BECAUSE DATASET DOES NOT EXIST

Explanation: You specified +ALLO(REUSE) and TAPEDD, but the name of the space to be reused does not exist in the VSAM catalog. A new space will be defined with a PRIQTY equal to the number of pages in the TAPEDD dataset and on the list of volumes previously occupied.

User response: No action is required.

NGTR686

string-1 SPACE string-2.string-3 string-4, IS EMPTY, OBJECT MUST BE RECOVERED

Explanation: BMC AMI Reorg has detected that the object of type string-1 and under the space name of string-2 is empty (that is, its High Used RBA is zero). Reorg cannot proceed until the object is recovered.

User response: Execute the Db2 recover utility to recover the specified object, then rerun the JOB.

NGTR687

INSUFFICIENT DISK SPACE TO REORG-IN-PLACE string-1 SPACE string-2.string-3 string-4

Explanation: BMC AMI Reorg has detected that the object of type string-1 and under the space name of string-2 cannot be reorganized in place, because the current dataset is not large enough to accommodate the new copy.

User response: Consider either using the +TAPEDD parameter in order to perform a reorg-in-place, or running with +MODE(NO).

NGTR688

RESTART DATA IN FILE SYSUT1 IS MISSING

Explanation: A previous run with this utility id produced restart data in the dataset referenced by DDname SYSUT1. However, on restart, the data could not be found.

User response: If you have modified or deleted the dataset, this is to be expected; if not, there may be some damage. Rerun the utility with the restart option 'NORESTART'. If 'NORESTART' could damage your database, then you must RECOVER all the indexes of the table space.

NGTR689

REORG-IN-PLACE IS NOT RESTARTABLE

Explanation: A prior run of this utility failed while in a non-restartable mode due to the specification of +INPLACEBUF parameter. The status is unknown of either the table space, or of the indexes on the tables in it, or both.

User response: Examine the extent of damage from the prior job. Either correct the error and rerun the job with PARM=NORESTART or terminate the current utility id.

NGTR690

OBJECT hexstring-1.hexstring-2 IS MISSING FROM THE DB2 CATALOG

Explanation: The Db2 object whose DBID is X'hexstring-1' and OBID is X'hexstring-1' is no longer recorded in the Db2 Catalog.

User response: This object existed prior to the restart of the utility. If you have deleted the object, then do not restart the utility. If not, then this may indicate a problem with BMC AMI Reorg, so contact BMC Support.

NGTR692

UNABLE TO OBTAIN 'string-1' LOCK ON DBNAME string-2 SQLCODE number-1

Explanation: Several unsuccessful attempts were made to obtain the string-1 lock on the DBD whose name is string-2 number-3 is the SQLCODE generated by the lock request which explains why the lock could not be obtained.

User response: If the SQLCODE is -911, you may increase the +QRETRY interval before restarting the JOB.

NGTR693

TABLE CONTAINS VARIABLE LENGTH COLUMN. OBID=hexstring-1, OBDREFLD=hexstring-2

Explanation: A variable length column has been found in the table whose OBID is X'hexstring-1'. The table however is considered to have fixed row length. OBDREFLD is a 10 byte entry in the OBD representing this column.

User response: This is a terminating error. It is possible that the DBD does not match the catalog, in which case, the DBD must be repaired. Contact BMC Support for further assistance.

NGTR694

TABLE ROW CONVERSION IS ACTIVE

Explanation: Any number of different factors may contribute to the need to convert rows for this reorg. Compression change, ALTER TABLE commands, RRFMT change, for example.

User response: No action is required.

NGTR695

TABLE ALTER DONE DURING REORG CHANGED KEYLENGTH - REORG ABORTED

Explanation: Reorg has detected that some index being reorganized has been modified as a result of a recent 'ALTER TABLE ALTER COLUMN' command. This command invalidates the indexes constructed during REORG.

User response: The run is aborted - rerun the REORG.

NGTR696

MEMORY TRACE MESSAGE

Explanation: message issued to detect memory leaks

User response: No action is required.

NGTR697

REORG OF LOB tableSpaceName SKIPPED. SAVINGS OF number-1 PAGES IS LESS THAN number-2 %

Explanation: Analysis of the named LOB table space showed savings below the specified limit. The reorg is skipped.

User response: No action is required.

NGTR698

COPY OF string-1.string-2 SKIPPED AT USER REQUEST - NOCOPY SPECIFIED

Explanation: A user specification causes the COPY of the named table space to be skipped.

User response: No action is required.

NGTR699

REORG OF INDIVIDUAL PARTS OF A PBG IS DISABLED - USE REORG TABLESPACE tableSpaceName DSNUM ALL

Explanation: Reorg of individual parts of a PBG can cause discrepancies in the conversion status of a PBG. Use DSNUM ALL on the REORG statement.

User response: The run is aborted - rerun the REORG.