Messages NGTR700 through NGTR799

For the Next Generation Technology products, this topic explains each message in the designated range.

NumberDescription
NGTR701

OPEN - ddName DD OPEN ERROR.


Explanation: An error occurred opening a QSAM DCB. NGT Reorg issues this message when you are rebalancing partitions and you do not allocate a PARTSDDL data set. The reorganization continues and NGT Reorg rebalances your partitions. However, NGT Reorg does not write to the PARTSDDL data set. For more information about this data set, see the BMC Next Generation Technology Reorg for DB2 for z/OS Reference Manual.

User response: If this message displays PARTSDDL as the DD name in error, no action is required. However, to avoid this message, ensure that you allocate this data set when rebalancing partitions during a reorganization. For other DDs, check for MVS Data Management (IEC) messages and correct any associated error. For example, a missing DD name is reported by message IEC130I. If you need assistance, contact BMC Customer Support, having available the dump from the Log PDS.

NGTR702

CLOSE - //string-1 DD CLOSE ERROR.


Explanation: An error occurred closing a QSAM DCB. String-1 is the DDname.

User response: Check for MVS Data Management (IEC) messages and correct any associated error. Otherwise, contact BMC Customer Support, having available the dump from the Log PDS.

NGTR703

string-1.string-2 'RBALRSN_CONVERSION BASIC' CONFLICTS WITH ZPARM 'NOBASIC'


Explanation: RBALRSN_CONVERSION BASIC specified in the SYSIN statement but the ZPARM option 'NOBASIC' is set, so this conversion is not allowed.

User response: You can specify any option other than BASIC. Modify the SYSIN and resubmit the job.

NGTR704

string-1.string-2 (number-1) 'RBALRSN_CONVERSION NONE' CONFLICTS WITH ZPARM 'NOBASIC'


Explanation: dbname.spacename (part #) is in BASIC format, but the ZPARM option 'NOBASIC' is set, so NONE is not allowed in this case.

User response: You cannot specify NONE. Modify the SYSIN and resubmit the job.

NGTR706

ALLOCATING NEW INDEX DATASET.


Explanation: A new index data set is being allocated.

User response: No action necessary--information only.

NGTR707

LOGIC ERROR - ERROR PROCESSING RID number-1 (hexstring-1) - PREFIX = hexstring-2.


Explanation: Number-1 is the RID as a number, X'hexstring-1' is the RID in hex, and X'hexstring-2' is the prefix of the row read at that RID. This message is issued if the row read is not the expected row (see byte 5 of X'hexstring-2'), or if the row is not an overflow row when one is expected, or if the row is not a pointer row when one is expected. This message could be due to a damaged Catalog, especially if the error is repeatable.

User response: Try the run again. If the error persists, contact BMC Customer Support.

NGTR708

LOGIC ERROR - ID MAP ERROR number-1, RID=hexstring-1, ID MAP ENTRY=hexstring-2.


Explanation: Number-1 is an error code:

Error code

Meaning

1

ID MAP value is 0

2

ID MAP value exceeds the max IDs in the page

3

ID MAP entry is for a deleted row

4

ID MAP entry contains an illegal offset

X'hexstring-1' is the RID in hex, and X'hexstring-2' is the ID MAP entry value that is invalid. This message indicates a damaged DB2 Catalog.


User response: The RID value gives the page number (in hex) in the first three bytes. Dump this page of the Catalog and contact BMC Customer Support. Run an analysis program (such as !DB/SMU) if you have one.

NGTR709

LOGIC ERROR - PAGE FLAGS ERROR, RID = hexstring-1, PAGE DATA=hexstring-2.


Explanation: This message indicates that the page read from the DB2 Catalog contains one of the following unexpected flags in the page header:

  • Page is broken

  • Page is an index page

  • Page is a spacemap or header page

  • Page is in a segmented table space


User response: The first three bytes of the RID value (X'hexstring-1') are the page number in hex. Dump this page of the Catalog and contact BMC Customer Support. Run an analysis program such as !DB/SMU if you have one.

NGTR710

LOGIC ERROR - UNEXPECTED EOF PROCESSING RID=number-1 (hexstring-1).


Explanation: The page indicated by the RID (X'hexstring-1') could not be read. An end-of-file condition was returned from the I/O routines.

User response: The RID value gives the page number (in hex) in the first three bytes. Dump this page of the Catalog and contact BMC Customer Support. Run an analysis program (such as !DB/SMU) if you have one.

NGTR711

ERROR OCCURRED DURING BLDMSG PROCESSING.


Explanation: This is an internal logic error

User response: A snap dump should exist in the Log PDS. Find the dump member for this error. Contact BMC Customer Support.

NGTR712

YOUR PASSWORD WILL EXPIRE TOMORROW.


Explanation: A default NGT utilities password is associated with each DB2 subsystem. This can be overridden at execution time via the value of the +PASSWORD keyword. The password associated with this execution expires tomorrow.

User response: This message warns you that if you use this password after today NGT utilities will not run. If you don't have another password with a later expiry, contact BMC Customer Support.

NGTR713

YOUR PASSWORD HAS EXPIRED, RUN CANNOT CONTINUE.


Explanation: For each of the NGT utilities, a default password is associated with each DB2 subsystem. This can be overridden at execution time via the value of the +PASSWORD keyword. The password associated with this execution was valid, but has expired.

User response: You can identify which product has the expired password from the first three characters of the module that issued the message. The run will continue unless you try to run the utility that requires the password.

NGTR714

PASSWORD IS INVALID, RUN CANNOT CONTINUE.


Explanation: For each of the NGT utilities, a default password is associated with each DB2 subsystem. This can be overridden at execution time via the value of the +PASSWORD keyword. The password associated with this execution is invalid.

User response: If you have a valid password, use it. Otherwise, contact BMC Customer Support.

NGTR715

OBJECT IS NOT IN AREO PENDING STATE, string-1.string-2 PART number-1 WILL BE SKIPPED.


Explanation: The object was sent to the Pre-process queue to determine if it was in an AREO Pending state. The object is not in AREO Pending, therefore the object will be skipped.

User response: No action necessary--information only.

NGTR716

ALL PARTS SKIPPED FOR OBJECT, string-1.string-2 WILL BE EXCLUDED.


Explanation: All the partitions being processed for the object have been skipped. The object will be placed on the Exclude queue.

User response: No action necessary--information only.

NGTR719

'AUX' USED BUT string-1.string-2 DOES NOT CONTAIN ANY TABLES WITH LOB COLUMNS. OBJECT SKIPPED.


Explanation: The 'AUX' keyword should only be used on table spaces that have tables with LOB columns.

User response: Remove the 'AUX' keyword on table spaces that does not contain any LOB columns.

NGTR720

LSPACE FAILED FOR VOLUME string-1. UTILITY ABORTED FOR THIS OBJECT.


Explanation: The +ALLOTYPE routine requested the 'SPAC' function. The MVS LSPACE failed for the volume named in string-1 .

User response: Consider using a different volume. Contact BMC Customer Support.

NGTR721

UCBSCAN FAILED FOR VOLUME string-1. UTILITY ABORTED FOR THIS OBJECT.


Explanation: The +ALLOTYPE routine requested the 'SPAC' function. The MVS UCB Scan routine failed for the volume named in string-1.

User response: Consider using a different volume. Contact BMC Customer Support.

NGTR722

VOLUME string-1 NOT FOUND IN SYSTEM. UTILITY ABORTED FOR THIS OBJECT.


Explanation: The volume named in string-1 was specified on a volumes list. It could not be located.

User response: Consider using a different volume. Contact BMC Customer Support.

NGTR725

DEFINE MODEL FROM string-1 LINE number-1


Explanation: The DEFINE statement about to be executed (via IDCAMS) was obtained from the User DEFINEs library. The member name (table space name) is string-1. The specific DEFINE starts as relative line number number-1 in this member.

User response: No action necessary--information only.

NGTR726

PRIQTY CHANGED FROM number-1 PAGES TO number-2 PAGES BECAUSE VOLUME string-1 IS FULL.


Explanation: +ALLO(MXIG) was specified. The data set requires number-1 pages, but this will not fit on the first volser, string-1. The PRIQTY value was changed to the largest contiguous space on the volume, number-2.

User response: No action necessary--information only.

NGTR727

INDEX DIRECTORY ERROR ON PAGE hexstring-1.


Explanation: The index header page indicates the existence of an index directory page. The page is either not a valid directory page (type 74) or some data in the page is inconsistent.

User response: The run fails. Run DSN1PRNT on the page. Contact BMC Customer Support.

NGTR728

DISCARDS NOT ALLOWED FOR REORG string-1.string-2. OBJECT IS IN REORG PENDING.


Explanation: This table space is in or has partitions that are in REORG PENDING. This cannot be corrected while discarding. Run with DISCARD after the Pending state has been cleared.

User response: Remove the DISCARD clause and rerun the REORG.

NGTR729

NO AUX TABLES DEFINED FOR TS tableSpaceName. AUX IS IGNORED.


Explanation: This table space does not have defined AUX tables (LOBs).

User response: No action necessary--information only.

NGTR730

NO TSTPRINT DD STATEMENT, SO NO REPORTS WILL BE PRODUCED.


Explanation: REORG TABLESPACE ... TESTONLY was specified, but no //TSTPRINT DD statement was included in the JCL. Reorganizations will be skipped, but no report will be produced.

User response: Supply a //TSTPRINT DD statement (SYSOUT=A)

NGTR731

LOAD FAILED FOR REXX MODULES, INTERFACE DISABLED


Explanation: One of the REXX interface modules could not be loaded, either IRXINIT or IRXTERM.

User response: Make these modules are available for loading via LINKLIST or STEPLIB.

NGTR732

UNABLE TO INITIALIZE REXX ENVIRONMENT, RC=number-1, INTERFACE DISABLED


Explanation: The initialization routine was unable to build a new LPE or find an old one to use. Module IRXINIT returned code number-1.

User response: The TSO/E REXX Reference manual lists the return codes for this module. If you are unable to correct the error, contact BMC Customer Support.

NGTR733

UNABLE TO LOAD REXX EXEC 'string-1'.


Explanation: The initialization routine was unable to load the REXX Exec string-1. This exec should be in the NGT SYSPDS library.

User response: Contact BMC Customer Support.

NGTR734

REXX EXIT 'string-1' INITIALIZATION COMPLETE.


Explanation: All tasks relating to initializing the REXX EXIT for exec string-1 are complete.

User response: No action necessary--information only.

NGTR735

REXX EXIT 'string-1' ERROR, RC=number-1, TEXT=string-2.


Explanation: When called to execute exec string-1, IRXEXEC returned a non-zero return code of number-1. Along with that, the error code returned was string-2.

User response: IRXEXEC return codes are listed in the TSO/E REXX Reference manual. The TEXT error, if present, may be associated with a REXX syntax error. See the TSO/E REXX Ref. manual for codes between 20003 and 20099.

NGTR736

UNABLE TO MODIFY THE HOST COMMAND TABLE FOR 'string-1', ROUTINE 'string-2', RC=number-1.


Explanation: The request to add the host command environment entry for string-1 in routine string-2 failed. The return code from IRXSUBCM was number-1.

User response: The TSO/E REXX Reference manual lists the return codes for this module. If you are unable to correct the error, contact BMC Customer Support.

NGTR737

BMC/REXX WILL NOT BE OPERATIONAL.


Explanation: The modules needed to run NGT/REXX could not be loaded. The REXX Exit will be operational, but command directed towards NGT/REXX will fail.

User response: The NGT/REXX load modules should be in the LINKLIST or STEPLIB. If you are unable to correct the error, contact BMC Customer Support.

NGTR738

IX SLAB NO. number-1 OF number-2 STARTED - STARTING PAGE hexstring-1


Explanation: Index SLAB read is operational due to the size of the Index.

User response: No action necessary--information only.

NGTR739

IX SLAB NO. number-1 OF number-2 ENDED - number-3 PAGES, number-4 FREE, number-5 TREE, number-6 LEAF


Explanation: Index SLAB read is completed.

User response: No action necessary--information only.

NGTR740

INDEX INTEGRITY ERROR - LEVEL 2 TREE PAGE DOES NOT POINT TO A LEAF PAGE


Explanation: An Index Tree page at level 2 should point to all Leaf pages. This one does not. Message NGTR743 should follow.

User response: See message NGTR743.

NGTR741

INDEX INTEGRITY ERROR - LEVEL >2 TREE PAGE DOES NOT POINT TO A TREE PAGE


Explanation: An Index Tree page above level 2 should point to all Tree pages. This one does not. Message NGTR744 should follow.

User response: See message NGTR744.

NGTR742

INDEX INTEGRITY ERROR - LEVEL >2 TREE PAGE DOES NOT POINT TO A TREE PAGE OF THE CORRECT LEVEL


Explanation: An Index Tree page above level 2 should point to all Tree pages of the next lower level. This one does not. Message NGTR744 should follow.

User response: See message NGTR744.

NGTR743

IX ERROR - TREE PAGE hexstring-1, LVL hexstring-2, number-1 PAGES INDEXED. ERROR AT PAGE hexstring-3


Explanation: The page indicated by X'hexstring-1' is at the IX level named. number is the number of pages at the next level of the Index. The one in error is indicated by X'hexstring-3'.

User response: Run DSN1PRNTs of the Index for the pages specified. Contact BMC Customer Support.

NGTR744

IX ERROR - TREE PAGE hexstring-1, LVL hexstring-2 REFERENCES PAGE hexstring-3, LVL hexstring-4


Explanation: The page indicated by X'hexstring-1' is at the named IX level. It points to the page indicated by X'hexstring-3'.

User response: Run DSN1PRNTs of the Index for the pages specified. Contact BMC Customer Support.

NGTR745

IX LEAFCHAIN ERROR - PAGE hexstring-1, CHAINED TO hexstring-2, EXPECTED hexstring-3.


Explanation: The page indicated by X'hexstring-1' is a leaf page. The forward leafpage chain references the page in X'hexstring-2'. X'hexstring-3' is the page expected from the tree page list.

User response: Run DSN1PRNTs of the Index for the pages specified. Contact BMC Customer Support.

NGTR746

IX STRUCTURE ERROR - PAGE hexstring-1 IS REFERENCED BY MULTIPLE TREE PAGES.


Explanation: The page indicated by X'hexstring-1' is a leaf page or a tree page that is pointed to by more than one tree page.

User response: Run DSN1PRNTs of the Index for the page specified. Contact BMC Customer Support.

NGTR747

FLAG - 80 (LEAF) 40 (TREE) 20 (NEXT OK) 10 (PRIOR OK) 08 (UNRESOLVED)


Explanation: This message follows NGTR746 and defines the values of the FLAG.

User response: See message NGTR746.

NGTR748

TREE PAGE hexstring-1 REFERENCES UNKNOWN TREE PAGE hexstring-2


Explanation: The page indicated by X'hexstring-1' is a non-leaf page that references the non-leaf page indicated by X'hexstring-2'. The latter page is not a tree (non-leaf) page.

User response: Run DSN1PRNTs of the Index for the pages specified. Contact BMC Customer Support.

NGTR749

TREE PAGE hexstring-1 REFERENCES TREE PAGE hexstring-2 - EXPECT LEVEL number-1, GOT number-2


Explanation: The page indicated by X'hexstring-1' is a non-leaf page that references the non-leaf page indicated by X'hexstring-2'. The latter page should be at tree level number-1 but was found at number-2.

User response: Run DSN1PRNTs of the Index for the pages specified. Contact BMC Customer Support.

NGTR750

MAX NUMBER STRUCTURAL ERRORS DETECTED - RUN ABORTING


Explanation: This Index Reorg is aborting because at least 50 structural errors were found.

User response: See messages NGTR748 and NGTR749.

NGTR751

STARTING INDEX TREE STRUCTURE ANALYSIS


Explanation: The process of analyzing the tree structure of the index begins. this includes validating the pages in each index non-leaf page.

User response: No action necessary--information only.

NGTR752

INDEX TREE STRUCTURE ANALYSIS COMPLETE


Explanation: The process of analyzing the tree structure of the index has completed with no errors.

User response: No action necessary--information only.

NGTR753

IX INTEGRITY ERR - PG hexstring-1 LEVEL ERROR - AT LVL number-1, INDEXED FROM LVL number-2


Explanation: The page indicated by X'hexstring-1' is referenced by a tree page but not at the correct index level. The page should be at tree level number-1 but was indexed from level number-2.

User response: Run DSN1PRNTs of the Index for the pages specified. Contact BMC Customer Support.

NGTR754

IX INTEGRITY ERR - PG hexstring-1 ERROR - EXPECT LVL number-1, NO MATCH FOUND.


Explanation: The page indicated by X'hexstring-1' is referenced by a tree page but was either not a leaf page or was previously referenced by another tree page.

User response: Run DSN1PRNTs of the Index for the pages specified. Contact BMC Customer Support.

NGTR755

INSUFFICIENT MEMORY TO PROCESS OBJECT - CODE hexstring-1 hexstring-2


Explanation: There was not enough memory to process an object of this size. Check the +INITWINDOW REORG parameter.

User response: If +INITWINDOW seems large enough for the size of the object, contact BMC Customer Support. Have the CDBPRINT output available.

NGTR756

OBJECT IS IN A RESTRICTED STATE state. objectName PART partitionNumber WILL BE SKIPPED.


Explanation: NGT Reorg could not reorganize the indicated object because it is in a restrictive state, for example, Recover Pending (RECP).

User response: If the object is an index that is in RBDP status, consider changing the REBUILDIX option to enable NGT Reorg to rebuild the index during the reorganization. Otherwise, use your standard method to remove the pending state of the object. Rerun the reorganization.

NGTR757

COPY FILE WRITTEN FOR string-1.string-2 (number-1) - number-2 TRACKS


Explanation: This message signals the close of the temporary COPY of the object being reorged. The final COPY happens after Change Apply.

User response: No action is required.

NGTR758

OVERLAY CONDITION - string-1.string-2 (number-1) -TS AVG RWLN = number-2 EA FOR #8 ROWS


Explanation: A terminating condition has occurred. Internal memory estimates are based on +INITWINSOW and the average row length in the TS as determined by the initial scan of the TS.

User response: Lower +INITWINDOW and retry.

NGTR759

OVERLAY CONDITION - SCAN AVG ROWLEN = number-1 BYTES EA FOR #8 ROWS


Explanation: The current TS scan has read the shown number of rows and they have an average row length specified in the message. When this average is significantly larger than the TS average, this condition can occur.

User response: Lower +INITWINDOW and retry.

NGTR760

OVERLAY CONDITION - TRY REDUCING +INITWINDOW BY AT LEAST number-1 PCT


Explanation: See Messages NGTR758 and NGTR759.

User response: Lower +INITWINDOW and retry.

NGTR761

LEAF PAGES COUNT MISMATCH - FROM TREE PAGES = #8, LEAFS READ = #8


Explanation: The first count is from traversing the tree pages. The second count is a count of leaf pages read from the index.

User response: There should be other messages describing the problem. The index is corrupted.

NGTR762

PBG TABLESPACE tableSpaceName WILL BE REORGED AS A SINGLE OBJECT


Explanation: DSNUM ALL was specified for a PBG REORG. No DB2 restrictions exist that prevent this object being reorged as a very large single table space.

User response: No action necessary--information only.

NGTR763

PBG TABLESPACE tableSpaceName ADDED PARTS BETWEEN PREPROC AND READ (number-1 TO number-2)


Explanation: DSNUM ALL was specified for a PBG REORG. The object grew into another partition between REORG setup and initial read.

User response: Resubmit the job when insert activity abates.

NGTR764

PBG TABLESPACE tableSpaceName PART 1 WAITING number-1 SECONDS FOR number-2 PARTS


Explanation: DSNUM ALL was specified for a PBG REORG. Part 1 has completed and is waiting for the other partitions to complete.

User response: No action is required.

NGTR765

COUNTS MISMATCH ON TS tableSpaceName - ROWTYPE=string-3, COUNT=#8, EXPECT=#8


Explanation: a PBG table space reorg has failed due to internal accounting errors.

User response: Contact BMC Customer Support.

NGTR766

TS tableSpaceName - WILL NOT FIT IN MAXPARTS (number-1) WITH SPECIFIED PCTFREE AND FREEPAGE VALUES.


Explanation: a PBG table space reorg cannot be done. The rows will not fit within the defined maxparts value.

User response: Reduce PCTFREE or raise FREEPAGE. Consider discarding rows as part of the REORG.

NGTR767

INDEX indexName HAS HAD COLUMNS ADDED - REBUILD INDEX IS REQUIRED.


Explanation: NGT Reorg could not reorganize the object because it is in a restrictive state, for example, recover pending (RECP).

User response: If the index is in rebuild pending (RBDP) status, consider changing the REBUILDIX option to enable NGT Reorg to rebuild the index during the reorganization. Otherwise, use your standard method to remove the pending state. Rerun the reorganization.

NGTR768

PBG tableSpaceName (number-1) WILL HAVE number-2 DATA (EXCL. CTL/EMPTY) PAGES AND number-3 ROWS


Explanation: Logical reorganization for this PBG has finished a partition. The number-2 variable refers only to the number of DATA pages, not CTL (control) or EMPTY pages. The number-3 variable refers to the number of rows.

User response: No action is required.

NGTR769

FASTSWITCH(NO) NOT ALLOWED WHEN APPLYING PENDING DEFINITION CHANGES


Explanation: When running the REORG to apply pending definition changes, +FASTSWITCH(NO) is not allowed.

User response: Change the Reorg Parms and rerun the utility

NGTR770

REORG INDEX WILL USE number-1 MEGS FOR I/O BUFFERS


Explanation: Due to size of index, a larger i/o buffer will be used.

User response: No action is required.

NGTR771

REORG RESET PROCESSING STARTED.


Explanation: The number of partitions in the PBG has increased while NGT/REORG is initiating. The Reorg will be restarted.

User response: No action necessary--information only.

NGTR772

BFAC PROCESSING HAS DETERMINED OBJECT hexstring-1 MUST START OVER.


Explanation: The number of partitions in the PBG has increased while NGT/REORG is initiating. The Reorg will be restarted.

User response: No action necessary--information only.

NGTR773

REMOTE PTR FLAG TURNED OFF IN ROW IN PAGE hexstring-1 ROW number-1


Explanation: A row flag is on indicating this row is an overflow from a pointer row in a different partition. The flag will be reset.

User response: No action necessary--information only.

NGTR774

TS tableSpaceName PART number-1 HAS NO DICTIONARY - WILL BE REBUILT.


Explanation: The table space is compressed, part 1 has a dictionary, but the named part has no dictionary. This forces a rebuild of all dictionaries and recompression of all rows in all parts.

User response: No action necessary--information only.

NGTR775

DICTIONARY IN TS tableSpaceName PART number-1 DIFFERS FROM THAT IN PART 1 - ALL WILL BE REBUILT


Explanation: The table space is compressed, part 1 has a dictionary, but the named part has a different dictionary. This forces a rebuild of all dictionaries and recompression of all rows in all parts.

User response: No action necessary--information only.

NGTR776

DICTIONARIES IN TS tableSpaceName WILL NOT BE REBUILT, ALL number-1 ARE THE SAME.


Explanation: The table space is compressed and all parts have the same dictionary. No rebuild or recompression is necessary.

User response: No action necessary--information only.

NGTR777

DICTIONARIES IN TS tableSpaceName WILL BE DELETED. NOT ALL ARE THE SAME AND RBLD FAILED.


Explanation: The table space is compressed but not all parts have the same dictionary. Rebuild already failed. The existing dictionaries must be deleted.

User response: No action necessary--information only.

NGTR778

BECAUSE DISCARD/SHORT ROWS, DCTNRY FROM TS tableSpaceName (1) WILL BE USED FOR ALL PARTS.


Explanation: The table space is compressed but all rows will be decompressed and recompressed because discarding is active or the table has 'short' rows. The dictionary from part 1 will be propagated to all parts.

User response: No action necessary--information only.

NGTR779

COMPRESS(NO) SET, DICTIONARY IN TS tableSpaceName WILL BE DELETED FOR ALL PARTS.


Explanation: The table space is compressed but it was altered to COMPRESS NO. All dictionaries will be deleted.

User response: No action necessary--information only.

NGTR780

PBG TS tableSpaceName - HAS A CLUSTERING INDEX string-3. CLIX READ STARTING.


Explanation: The PBG table space has a clustering index. This index will be read to determine the order of the rows in the table space.

User response: No action necessary--information only.

NGTR781

PBG TS tableSpaceName - PREPARING TRANSLATE TABLE FOR number-1 PAIRS


Explanation: The PBG table space has indexes that need to be Reorged and translated. The Translate table must be in original rid order.

User response: No action necessary--information only.

NGTR784

PBG TS tableSpaceName (number-1) - number-2 PAGES WRITTEN


Explanation: This is a progress message for the named PBG table space writer.

User response: No action necessary--information only.

NGTR785

DB2 ALTERS DONE DURING THE TIME OF INITIALIZATION. THE JOB MUST BE RERUN.


Explanation: DB2 ALTERs were applied to this table space between the time of REORG initialization and the start of processing.

User response: The job fails and must be restarted.

NGTR786

REORG STARTING FOR string-1.string-2 TO CONVERT TO UTS.


Explanation: DB2 ALTERs were applied to this table space to convert it to UTS.

User response: No action necessary--information only.

NGTR787

REORG COMPLETE FOR string-1.string-2 CONVERSION TO UTS.


Explanation: DB2 ALTERs were applied to this table space to convert it to UTS. The run is complete.

User response: No action necessary--information only.

NGTR788

DISCARDS NOT ALLOWED FOR A REORG THAT CONVERTS tableSpaceName TO A PBG.


Explanation: DB2 ALTERs were applied to this table space to convert it to a PBG. This cannot be done while discarding. Run with DISCARD after converted to a PBG.

User response: Remove the DISCARD clause and rerun the REORG.

NGTR789

MASSDELETE NOT ALLOWED FOR A REORG THAT IS PROCESSING PENDING ALTERS ON TS tableSpaceName


Explanation: DB2 ALTERs were applied to this table space. This cannot be done while doing mass deletes. Run with MASSDELETE after the special Reorg is complete.

User response: Remove the MASSDELETE clause and rerun the REORG.

NGTR790

NO PART SELECTION ALLOWED ON A REORG THAT IS PROCESSING PENDING ALTERS ON TS tableSpaceName


Explanation: DB2 ALTERs were applied to this table space. This must be done on all parts. Part selection is not allowed.

User response: Remove the PARTS/LPARTS clause and rerun the REORG.

NGTR791

PENDINGDDL Materialization starting on TS tableSpaceName


Explanation: The process to materialize all DB2 ALTERS on the above named TS and all of its indexes has started. Message NGTR793 will be issued at the completion of the process.

User response: No action necessary--information only.

NGTR792

PENDINGDDL MATERIALIZATION STARTING ON IXSPC indexSpaceName


Explanation: The process to materialize all DB2 ALTERS on the above named Index Space has started. Message NGTR793 will be issued at the completion of the process.

User response: No action necessary--information only.

NGTR793

PENDINGDDL MATERIALIZATION SUCCESSFUL ON string-1.string-2


Explanation: All DB2 ALTERs described by message NGTR791 or NGTR792 have been put into effect and removed from the PENDINGDDL table.

User response: No action necessary--information only.

NGTR794

SQL error and warning fields formatter


Explanation: Formats various SQLCA fields and their values.

User response: Refer to SQL reference for more details or contact BMC Customer Support.

NGTR795

PENDINGDDL MATERIALIZATION WARNING FOR string-1.string-2


Explanation: Pending DDL materialization is successful but with a warning.

User response: Refer to message NGTR794 for details or contact BMC Customer Support.

NGTR796

PENDINGDDL MATERIALIZATION ERROR ON string-1.string-2. REORG ABORTED.


Explanation: Pending DDL materialization has failed due to SQL error. REORG of the TS or Index will be aborted. Original TS or IX will be restored.

User response: Refer to message NGTR794 for details or contact BMC Customer Support.

NGTR797

PENDINGDDL MATERIALIZATION ABENDED ON string-1.string-2. REORG ABORTED.


Explanation: Pending DDL materialization has failed due to other ABENDs. REORG of the TS or Index will be aborted. Original TS or IX will be restored.

User response: Refer to prior error messages that caused the ABEND. Contact BMC Customer Support.

NGTR798

PBG TS tableSpaceName (number-1) WTRX ENDING BECAUSE READER FAILED.


Explanation: A PBG table space writer subtask failed - this message signals the termination of the main task.

User response: Contact BMC Customer Support.

NGTR799

PBG TS tableSpaceName (number-1) WTRX ENDING BECAUSE WRITER FAILED.


Explanation: A PBG table space writer subtask failed - this message signals the termination of the main task.

User response: Contact BMC Customer Support.

Was this page helpful? Yes No Submitting... Thank you

Comments