Messages NGTR800 through NGTR899

This topic contains messages for the Next Generation Technology products.
NumberDescription
NGTR800

PBGA WRITER SUBTASK subtaskName PROCESSING OUTPUT PART partitionNumber


Explanation: Internal documentation message that indicates the assignment of a subtask for writing a specific PBG DSNUM ALL table space partition.

User response: No action is required.

NGTR801

TASK S string-1 WAITING FOR WORK


Explanation: This message identifies a Change Apply subtask. String-1 is the task id and will appear on all messages issued from this task.

User response: No action is required.

NGTR802

CHANGE APPLY STARTING FOR PART number-1 number-2 CHANGES


Explanation: Change Apply processing is starting. Number-1 is the partition. number (0 if non-partitioned.) Number-2 is the number of different rows changed.

User response: No action is required.

NGTR803

CHANGE APPLY COMPLETE FOR PART number-1


Explanation: Change Apply processing has completed for this task. Number-1 is the partition number (0 if non-partitioned).

User response: No action is required.

NGTR804

SUBTASK S string-1 ENDED PREMATURELY WITH CODE hexstring-1


Explanation: A Change Apply subtask has terminated abnormally with code X'hexstring-1'.

User response: Check for prior messages that might indicate the cause of the problem. Call BMC Customer Support.

NGTR805

UPDATE PHASE FOR number-1 CHGS - number-2 ISRTS, number-3 DLETS number-4 UPDTS


Explanation: This indicates the number of changes as the object existed at the first drain with the object as it existed at the second drain. number-1 = #CHANGES (#Inserts+#Deletes+#Updates) number-2 = #INSERTS (New rows added) number-3 = #DELETES (Old rows deleted) number-4 = #UPDATES (#Orignal rows differs from final rows)

User response: No action is required.

NGTR806

string-1 CLOSE - DSN=string-2


Explanation: String-1 is the DB2 Pageset type and String-2 names the VSAM data set that is being closed. This message is displayed after the data set has been successfully closed. Subsequent messages will show page I/O statistics.

User response: No action is required.

NGTR807

UNEXPECTED LRSN hexstring-1 IN PAGE hexstring-2. EXPECTED LRSN hexstring-3


Explanation: The buffer manager has detected a page having a LOGRBA/LRSN that exceeds the levelid RBA/LRSN for the pageset. X'hexstring-2' is the page number in error. A dump of the entire page as well as the pageset data set name follows this message.

User response: This is a terminating error. You may need to restore the pageset from a recent shrlevel reference image copy, then rerun the log apply process again.

NGTR808

'DB2 UTILITY/COMMAND MESSAGE'


Explanation: This is a line of output from DB2 commands and utilities. It is a compacted form of message NGTC029. To view the uncompacted format, specify +DSCRL(000999,9) in UTLPARMS. Refer to IBM DB2 message DSNT397I for an explanation of the information.

User response: No action is required.

NGTR809

BROKEN PAGE hexstring-1


Explanation: A page that has been modified by DB2 is being processing by the RWREORG Change Manager, but the page has the 'broken page' flag on. Reorg will terminate. X'hexstring-1' is the page number.

User response: Check for DB2 error messages on the System Console. Consider running DB2 CHECK INDEX. If no error is apparent, contact BMC Customer Support.

NGTR810

POF ERROR - hexstring-1 hexstring-2 hexstring-3


Explanation: The PTR_OFLOW resolution processor has detected unresolved pointers. X'hexstring-1' is the Overflow Rid, X'hexstring-2' is the Pointer Rid, and X'hexstring-3' are type flags.

User response: Contact BMC Customer Support. Have the CDBPRINT ready for analysis.

NGTR811

UNMATCHED PTR-OVERFLOW RECORD


Explanation: The PTR_OFLOW resolution processor has detected unresolved pointers.

User response: Contact BMC Customer Support. Have the CDBPRINT ready for analysis.

NGTR812

MISMATCHED OVERFLOW UPDATE


Explanation: The PTR_OFLOW resolution processor has detected unresolved pointers.

User response: Contact BMC Customer Support. Have the CDBPRINT ready for analysis.

NGTR813

MISMATCHED PTR-OVERFLOW PAIR


Explanation: The PTR_OFLOW resolution processor has detected unresolved pointers.

User response: Contact BMC Customer Support. Have the CDBPRINT ready for analysis.

NGTR814

TABLE MASS DELETE DETECTED


Explanation: Mass Deletes from a segmented table space will force the Reorg to terminate. This message will include a dump of the Spacemap page segment and the table name.

User response: Rerun the Reorg.

NGTR815

DB2 LOG APPLY PROCESS INITIATED


Explanation: This message signals the beginning of the Change Apply phase of the RE-Reorg.

User response: No action is required.

NGTR816

MAKING DB2 LEVELID UPDATES IN HEADER PAGES


Explanation: This message signals the beginning of the process to update the header pages of each data set with the proper data sharing levelid LRSN.

User response: No action is required.

NGTR817

string-1.string-2 (number-1) WILL BE CONVERTED TO EXTENDED_LRSN


Explanation: The above named object data and control pages will be converted from basic lrsn format to extended lrsn format

User response: No action is required.

NGTR818

string-1.string-2 (number-1) WILL BE CONVERTED TO BASIC_LRSN


Explanation: The above named object data and control pages will be converted from extended lrsn format to basic lrsn format

User response: No action is required.

NGTR819

string-1.string-2 'RBALRSN_CONVERSION BASIC' CONFLICTS WITH LARGE LOG RBA VALUE


Explanation: RBALRSN_CONVERSION BASIC specified in the SYSIN statement is not allowed because the current LOG has already surpassed the basic RBA value

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

NGTR820

TABLE OBID CHANGED - UNSUPPORTED CONDITION


Explanation: This situation should never occur except in simple multi-table table spaces. These are not supported in this release.

User response: You cannot run NGT Reorg on this table space.

NGTR821

A TABLE WITH OBID hexstring-1 WAS CREATED DURING THE REORG


Explanation: A new table was created during the NGT Reorg run. This situation is not supported in this release. The utility can be rerun.

User response: Rerun the utility.

NGTR822

number-1 4K CHANGES WRITTEN TO string-1


Explanation: number-1 is the number of 4K records written to the above named data set. These records will be merged with the base image copy files to produce a final image copy data set of the current table space.

User response: No action is required.

NGTR823

MAXMEM LIMIT EXCEEDED - number-1 KB USED, LIMIT number-2 MEG


Explanation: The MAXMEM parameter specified a limit for Change Apply memory. This value has been exceeded.

User response: Run the RW-Reorg during a period of lower activity or raise the MAXMEM limit.

NGTR824

THE INDEX IS NOT A TYPE 2 INDEX. RUN ABORTED


Explanation: REORG INDEX CONCURRENT can only be run on Type 2 Indexes. You must convert the index to Type 2 before doing the Index RW-REORG.

User response: Run the NGT/SuperReorg with the 'TOTYPE2' keyword to convert the index to a Type 2 Index.

NGTR825

INDIVIDUAL PARTITIONS NOT SUPPORTED IF NON-PARTITIONING INDEXES EXIST


Explanation: REORG TABLESPACE CONCURRENT PART n can only be run if there are no non-partitioning indexes. This is a restriction in the current release of RW-Reorg.

User response: If non-partitioning indexes exist, you must Reorg all partitions.

NGTR826

REORG OF A CATALOG OBJECT string-1.string-2 IS NOT ALLOWED


Explanation: Reorg has detected that the above named index is on a DB2 Catalog table. Currently, Reorg does not support this type of object.

User response: The object will be skipped. Maximum return code will be set to 4

NGTR827

INDEX MASS DELETE DETECTED, DSN=string-1


Explanation: Mass delete of data in a table will force the Reorg to terminate. This message is issued during RW-REORG of above named indexspace.

User response: Rerun the Reorg.

NGTR828

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


Explanation: This is for a non-PBG. A PBR or non-UTS partitioned TS has a non-partitioned clustering index.

User response: No action is required.

NGTR829

TS tableSpaceName - WAITING FOR TS PART READS. number-1 OF number-2 COMPLETE


Explanation: This is for a PBR with a NPI clustering index. TS part reads are in progress. All must complete before writes can start.

User response: No action is required.

NGTR830

QUIESCE UNDER BMC CONTROL - DRAIN TIMEOUT = number-1 SECONDS, number-2 RETRIES


Explanation: This message indicates that all QUIESCEs will be done under NGT control. The Timeout value for each QUIESCE is Number-1. Number-2 is the number of times the QUIESCE will be retried if it is unsuccessful.

User response: No action is required.

NGTR831

QUIESCE NOT EXECUTED BECAUSE DRAIN TIMEOUT IS 0


Explanation: This message indicates that no QUIESCEs will be done because there is no Timeout value.

User response: Either specify the DRAINTIMEOUT keyword with a value in seconds or use the +QRETRY utility parameter with a non-zero seconds value.

NGTR832

NO MATCHES FOUND IN CATALOG FOR QUIESCE WILDCARD REQUEST - string-1.string-2


Explanation: DB2 wildcards were used in the QUIESCE statement, but no catalog matches were found.

User response: Correct the statement and rerun the job.

NGTR833

TOO MANY OBJECTS TO QUIESCE


Explanation: There are too many objects in the QUIESCE request to fit in a 32K buffer. Each object requires between 25 to 40 characters.

User response: Use a more restrictive wildcard specification.

NGTR834

QUIESCE FAILED ON SOME OBJECT IN THE SET


Explanation: QUIESCE failed to obtain the DRAIN. Which object caused the failure is unknown.

User response: Processing continues based on the setting of +ONERROR .

NGTR835

QUIESCE FAILED ON string-1.string-2


Explanation: QUIESCE failed to obtain the DRAIN for this object.

User response: Processing continues based on the setting of +ONERROR .

NGTR836

ALL OBJECTS EXCLUDED


Explanation: The EXCLUDEs removed all named entries.

User response: No action is required.

NGTR837

MODIFY FAILED ON string-1.string-2


Explanation: MODIFY failed for a specific object.

User response: Processing continues based on the setting of +ONERROR .

NGTR838

QUIESCE SKIPPED FOR string-1.string-2 PART number-1 BECAUSE OBJECT IS STOPPED


Explanation: The named object is stopped. QUIESCE cannot be done on stopped objects.

User response: No action is required.

NGTR839

QUIESCE SKIPPED FOR string-1.string-2 PART number-1 BECAUSE OBJECT IS RESTRICTED


Explanation: The named object is in a restricted state. QUIESCE cannot be done on such objects.

User response: No action is required.

NGTR840

NO MATCHES FOUND IN CATALOG FOR MODIFY WILDCARD REQUEST - string-1.string-2


Explanation: DB2 wildcards were used in the MODIFY statement, but no catalog matches were found.

User response: Correct the statement and rerun the job.

NGTR841

QUIESCE SKIPPED FOR string-1.string-2 PART number-1 BECAUSE OBJECT IS INCOMPLETE


Explanation: The named object is in an incomplete state. QUIESCE cannot be done on such objects.

User response: No action is required.

NGTR842

string-1 COMMAND SYNTAX ERROR


Explanation: A syntax error related to the use of wild cards has been detected on the above named command. Following message will give more details on this specific error.

User response: See following message printed in the error file for further info.

NGTR843

string-1 KEYWORD RANGE (:) INCORRECTLY SPECIFIED


Explanation: The above named keyword specified on the command described by prior message NGTR842 does not adhere to restrictions. A range can not have wild cards.

User response: Remove wild cards '*' from the range of values separated by a colon ':' for the above named keyword then rerun your job.

NGTR844

ACCESS(FORCE) IS ONLY ALLOWED WITH EXPLICIT TABLESPACE OR INDEXSPACE


Explanation: ACCESS(FORCE) on the -START command does not allow the specification of wild cards in either the DB() or the SPace() keywords.

User response: Remove wild cards '*' from the names specified in the DB()/SP() keywords then rerun your job.

NGTR845

SYSADM AUTHORITY IS REQUIRED TO EXECUTE -STOP/-START COMMAND


Explanation: The current user id associated with this job does not have the proper authority to execute NGT's -STOP or -START command. SYSADM AUTHORITY is required.

User response: Rerun the job with a userid having the DB2 sysadm authority privilege

NGTR846

NO OBJECTS FOUND TO SATISFY THE DB()/SP() ON string-1 COMMAND


Explanation: The database objects specified by the DB()/SP() keywords on the above named command either did not exists in the DB2 catalog or was excluded by the criteria of XDB()/XSP() keywords. The return code will be 4

User response: Check for mis-spelled names. Correct names if necessary and rerun your job.

NGTR847

BEGIN EXECUTION OF COMMAND string-1 IN STATEMENT NO. number-1


Explanation: The current NGTUTIL task has started the execution of the above named command specified in the assigned statement number.

User response: No action is required.

NGTR848

QAFTER VALUE CHANGED TO QAFTER(NO)


Explanation: The current QAFTER value is not compatible with the function that is being executed. The QAFTER value has been changed to NO.

User response: No action is required.

NGTR849

BMC/STOP PASSWORD IS INVALID


Explanation: The +STOPPSWD() entered is invalid.

User response: Correct +STOPPSWD() and rerun job.

NGTR850

SYSADM AUTHORITY IS REQUIRED TO EXECUTE SQL


Explanation: The DB2 privilege level SYSADM was needed to run SQL processing and was not found.

User response: Either change the privilege level for the user running this job to SYSADM or run the job under a user that has the SYSADM privilege level.

NGTR851

DEFINE FAILED FOR NEW DB2 DATASET. RETRY number-1 OF number-2 IS IN PROGRESS


Explanation: The AMS DEFINE failed however the DEFINE process will be retried after invoking REXX EXEC 'XSUTALLO' to manipulate primary allocation values. number-1 is the current retry number number-2 is the final retry number.

User response: No action is required.

NGTR852

WORKFILE OBJECT string-1.string-2 HAS BEEN SKIPPED


Explanation: The named workfile object will not be processed.

User response: Information message - no action required.

NGTR853

TSPAGS=number-1 MXMP=number-2 FRAMES=number-3 E-FRAMES=number-4


Explanation: Shows total number of table space pages, maxrows per page MXMP found in the clustering index if any, the total number of available frames in the system and the total available Expanded frames.

User response: No action is required.

NGTR854

DSP hexstring-1 MEMORY USED=number-1 MMAX=number-2 MTOTAL(number-3 PAGES, #9 INSERTS, #9 DELETES)


Explanation: This message indicates a memory threshold of 32M increments at the current data space level

User response: No action is required.

NGTR855

MEMORY LIMIT EXCEEDED. USED=number-1 MAX=number-2


Explanation: The change apply data collection manager for the current utility has reached its collection limit within a single unit of work. This is a terminating condition.

User response: Run the RW-Reorg during a period of lower activity or increase the dispatching priority for the job.

NGTR857

SCHEDULING number-1 CHANGE APPLY PROCESSES IN number-2 THREADS


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

User response: No action is required.

NGTR858

DISPATCHING CHANGE APPLY WORK number-1 AT LRSN hexstring-1, INS=number-2 DEL=number-3


Explanation: This message shows the change apply work number at the specified sync point in the DB2 LOG.

User response: No action is required.

NGTR859

CHANGE APPLY DEADLINE LIMIT OF number-1 MINUTES REACHED


Explanation: This message shows that the change apply phase took longer than desired based on the specified +deadline parameter. Current job will terminate.

User response: Either specify +DEADLINE(0) or rerun the job when system activity is light.

NGTR860

QUEUEING CHANGE APPLY DSP number-1 AT LRSN hexstring-1 SIZE number-2


Explanation: The change apply queue manager has queued the above numbered DSP for DISK write processing due to increased change apply data capture activity.

User response: No action is required.

NGTR861

number-1 TRANSACTIONS PENDING CHANGE APPLY databaseName.objectName

Explanation: This message shows the number of transactions pending the change apply process.

User response: No action is required.

NGTR862

+QRETRY LIMIT REACHED BEFORE OBTAINING A DRAIN. PROCESS TERMINATED FOR databaseName.objectName


Explanation: The change apply process failed because drains could not be obtained in a timely manner as dictated by the +QRETRY parameter.

In this message:

  • databaseName is the database name or creator name of the object.
  • objectName depends on the command, as shown in the following table:

    CommandObject name
    REORG TABLESPACEtableSpaceName
    REORG INDEXindexSpaceName
    LOADtableName
User response: Rerun the job with increased limits for the +QRETRY parameter.
NGTR863

#8 ROWS PROCESSED BY LR


Explanation: Logical Reorg is processing a very large table space. A message is written to show progress.

User response: No action is required.

NGTR864

STARTING DICTIONARY ANALYSIS - NEW VS EXISTING FOR TS tableSpaceName


Explanation: Reorg of a Compressed PBG DSNUM ALL requires rebuild of the dictionary. This process will determine if the existing dictionary for the first part will be better or worse than a new dictionary.

User response: No action is required.

NGTR865

#8 ROWS READ FOR DICTIONARY ANALYSIS OF tableSpaceName


Explanation: Dictionary analysis is complete. The message indicates the number of table space rows read, decompressed and recompressed.

User response: No action is required.

NGTR866

string-1 DICTIONARY GIVES number-1 PCT COMPRESSION


Explanation: Dictionary analysis is complete. The message shows the percent reduction in the size of the rows using the specified dictionary.

User response: No action is required.

NGTR867

EXISTING DICTIONARY WILL BE USED FOR REORG databaseName.tableSpaceName


Explanation: The existing dictionary is used.

User response: No action is required.

NGTR868

OK RETURN FROM LR - CONV hexstring-1


Explanation: Internal documentation message—the CONV value indicates compression dictionary action for this PBG DSNUM ALL.

User response: No action is required.

NGTR869

REAL FRAMES = number-1, AUX FRAMES = number-2


Explanation: This is an internal documentation message showing memory available at the time the PBG DSNUM ALL Reorg begins. These values will affect the number of subtasks running in parallel.

User response: No action is required.

NGTR870

number-1 PARTS TO WRITE, number-2 EMPTY PARTS TO FORMAT databaseName.tableSpaceName


Explanation: This is an internal documentation message showing the results of the read of all the parts of the PBG.

User response: No action is required.

NGTR871

number-1 FRAMES PER TASK, number-2 TASKS


Explanation: For a PBG Reorg DSNUM ALL, this message indicates the number of parallel tasks that will be used to write the table space.

User response: No action is required.

NGTR872

WAITING FOR ALL WRITERS TO END


Explanation: For a PBG Reorg DSNUM ALL, this message indicates the start of the table space writer process.

User response: No action is required.

NGTR873

WAITING FOR PBG TASK MONITOR TO END


Explanation: For a PBG Reorg DSNUM ALL, a task is running that monitors the progress of the table space writers. This task should end within 10-15 seconds of this message. If not, there is a problem - use the DUMP operator command to get an SVC dump and contact BMC Customer Support.

User response: No action is required.

NGTR874

PBG TABLESPACE WRITER PROCESSING COMPLETE databaseName.tableSpaceName


Explanation: For a PBG Reorg DSNUM ALL, all table space data sets are written before beginning the Reorg of the NPIs (if any). This message marks the completion of the table space Write phase.

User response: No action is required.

NGTR875

PBGA WRITER SUBTASK string-1 STARTING


Explanation: Internal documentation message that indicates the initiation of a subtask for the writing of a PBG DSNUM ALL table space partition.

User response: No action is required.

NGTR876

PBGA WRITER SUBTASK string-1 ENDING


Explanation: Internal documentation message that indicates the termination of a subtask for the writing of a PBG DSNUM ALL table space partition.

User response: No action is required.

NGTR877

INSUFF AUX STG TO RUN DSNUM ALL ON databaseName.tableSpaceName


Explanation: Internal documentation message that indicates the assignment of a subtask for writing a specific PBG DSNUM ALL table space partition.

User response: No action is required.

NGTR878

PBGA WRITER SUBTASK string-1, PART string-2, COMPLETED RC=number-1


Explanation: This message marks the completion of the writing of a specific PBG DSNUM ALL table space partition.

User response: No action is required.

NGTR879

X1T WRITE COMPLETE FOR string-1. string-2 PART number-1


Explanation: This message documents the completion of the translate table write for the named partition.

User response: No action is required.

NGTR880

INPUT PART number-1, number-2 ROWS


Explanation: This is an internal tracing message—the count printed should match the prior report.

User response: No action is required.

NGTR881

X1T WRITTEN FOR PART number-1, #8 ROWS


Explanation: This is an internal tracing message—the count printed should match the count from the table space read.

User response: No action is required.

NGTR882

BEGINNING LR FOR string-1.string-2, number-1 PARTS


Explanation: The process of assigning rows to the new output parts is beginning.

User response: No action is required.

NGTR883

BEGINNING LR FOR string-1.string-2, PART number-1


Explanation: The process of assigning rows to the new output parts is beginning for the specified input partition.

User response: No action is required.

NGTR884

BEGINNING LR FOR string-1.string-2, INPUT PART number-1, number-2 ROWS


Explanation: The process of translating rows is beginning for the specified input partition.

User response: No action is required.

NGTR885

PART number-1, number-2 MEGS, number-3 ROWS, number-4 ROWS/SECTION, number-5 SECTIONS databaseName.tableSpaceName


Explanation: The new table space will be written using sectional reads of the input table space. This message indicates how many sections will be required based on the amount of memory allotted to the table space reader.

User response: No action is required.

NGTR886

DISORGANIZATION FACTOR = number-1 PCT, MAXDISORG=number-2 databaseName.tableSpaceName


Explanation: Disorganization level, as shown in the message, indicates the level of clustering index randomness in the table space. High values will cause the REORG to run a very long time.

User response: No action required.

NGTR887

number-1 TRANACTIONS HAVE BEEN APPLIED TO DB2 SPACES GOVERNED BY CONN ID number-2


Explanation: number-1 is the cumulative sum of all transactions that have been applied to the shadow copy of all spaces governed by utility statement number number-2

User response: No action is required.

NGTR889

STORAGE CLASS MEMORY (SCM) TOTAL = xM, USED = yM, AVAILABLE = zM


Explanation: This message displays the amount of Storage Class Memory available on the system at the time this task started. The three values shown are total SCM, used SCM, and available SCM.

User response: No action is required.

NGTR892

ALLOCATE - REPBLDAL DD ALLOCATION ERROR


Explanation: You are rebalancing partitions, but the REPBLDAL DD is not allocated. The reorganization continues and NGT Reorg rebalances your partitions. However, NGT Reorg does not write to the REPBLDAL 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: No action is required. However, to avoid this message, ensure that you allocate this data set when rebalancing partitions during a reorganization.

NGTR893

REQUIRED DRAIN PROCESSING FOR REORG WITH REPORTONLY IS DISABLED – REORG ABORTED


Explanation: The REPORTONLY option specified after any of the following on the REORG command requires drain processing:

- INDEX
- INDEXES
- INDEXSPACE
- AUX YES

However, +REPORT_DRAIN(NO) specifies that no drain processing is allowed.

User response: Change the +REPORT_DRAIN parameter to YES or avoid processing with any of the options listed in the explanation.

NGTR895

PBGA tableSpaceName HAS PARTS WITH DIFFERING CONVERSION STATUS - NOCLIX FORCED


Explanation: Varying conversion status between parts of the PBG force NOCLIX. Not all parts have dictionaries or the same RRFMT status.

User response: To re-establish CLIX order, this PBG will need to be reorganized again after all parts have the conversion status.

NGTR896

PBGA STATUS REPORT


Explanation: This is a repetitive report summarizing the status of the Reorg.

User response: No action is required.

NGTR897

reportHeading


Explanation: This message provides the heading for a report from NGT Reorg or NGT LOBMaster.

User response: No action is required.

NGTR898

PBGA OUTPUT REPORT


Explanation: This message reports the number of rows per output partition for a REORG DSNUM ALL.

User response: No action is required.

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

Comments