Messages NGTR300 through NGTR399

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

NGT HAS NOT BEEN CONFIGURED FOR DB2 SUBSYSTEM string-1.


Explanation: The DB2 subsystem named in the PARM field of the EXEC statement is unknown to NGT utilities.

User response: Correct the name of the DB2 subsystem if necessary. Otherwise, configure NGT utilities for the subsystem. You can do this either by executing the program SUTISTRT, or via NGT utilities Interactive.

NGTR301

ERROR OCCURRED DELETING MODULE string-1, (hexstring-1).


Explanation: The installation parameter module is loaded, copied, then deleted from storage. The delete failed. The module is string-1 (X'hexstring-1').

User response: Check for any system error messages on the system messages file. Contact BMC Customer Support.

NGTR302

//string-1 DD IS NOT A PDS.


Explanation: The system PDS named in the //SYSPDS DD statement and the LOG PDS named in the //LOGPDS DD statement must both be Partitioned Data Sets. Other organizations (for example, SAM, VSAM or PDSE) are not supported. String-1 is the DDname for the data set.

User response: Review your installation procedure. Allocate PDSes for the SYSPDS and LOGPDS.

NGTR303

UTILITY COMPLETE, COMPLETION CODE=number-1.


Explanation: All the utility functions have completed. The completion code number-1 indicates the degree of success.

User response: If the completion code is zero, then this message is issued for information only and no action is necessary. If the completion code is non-zero, then other messages will appear reporting on errors encountered; follow the directions for those messages.

NGTR304

CONFIGURATION COMPLETE, COMPLETION CODE=number-1.


Explanation: The configuration of NGT Reorg for one DB2 subsystem is complete. The completion code number-1 indicates the degree of success.

User response: If the completion code is zero, then this message is issued for information only and no action is necessary. If the completion code is non-zero, then other messages will appear reporting on errors encountered; follow the directions for those messages.

NGTR305

configurationSet CONFIGURATION SET USED FOR DEFAULT PARAMETERS.


Explanation: The utility will use the indicated configuration set of load modules (RX10xxxx/RX11xxxx) for the default configuration parameters.

User response: No action is required.

NGTR306

NGTCKPT DD NOT FOUND AND +NGTCKPT PARAMETER IS NOT CONFIGURED


Explanation: The utility did not find an NGTCKPT DD statement and the +NGTCKPT parameter is not specified in the product configuration module. NGT utilities require a checkpoint data set and terminates when it does not find one.

User response: Either add an NGTCKPT DD statement to your JCL, or update the NGT configuration module with the +NGTCKPT parameter. Rerun the job.

NGTR307

SIZE OF numberOfPages PAGES EXCEEDS THE MAX ALLOWED BY DB2 FOR TABLESPACE databaseName.tableSpaceName


Explanation:
The number of pages in the new table space partition exceeded the maximum allowed by DB2 for the referenced database, table space, or partition. See also message NGTR308.

User response: Adjust the values specified in the NGT Reorg RRGPARMS +PCTFREE or +FREEPAGE to ensure that the new rows are within the limits allowed by DB2, and rerun the reorganization job.

NGTR308

CONSIDER ADJUSTING EITHER PCTFREE OR FREEPAGE OR BOTH SO THE ROWS FIT WITHIN THE DB2 LIMITS


Explanation:
The maximum number of pages allowed for an individual partition was exceeded during the reorganization of the object identified in message NGTR307. This might be directly related to the values specified in the NGT Reorg RRGPARMS values +PCTFREE or +FREEPAGE. You can adjust these values individually or collectively to affect the outcome of the reorganization.

User response: Adjust the NGT Reorg RRGPARMS +PCTFREE or +FREEPAGE to ensure that the new rows are within the limits allowed by DB2, and rerun the reorganization job.

NGTR309

DEFERRED INDEX FOUND WITH +IGNDEFNO(Y) USAGE. PROCESSING SKIPPED FOR: databaseName.indexName.


Explanation:
During processing, NGT Reorg found an index defined with the DEFINE NO attribute. NGT Reorg skipped the index due to the +IGNDEFNO(YES) specification in the RRGPARMS DD.

User response: To complete the reorganization job by skipping the index defined with the DEFINE NO attribute, in the NGT RRGPARMS DD, specify +IGNDEFNO(YES). If you specify IGNDEFNO(NO), NGT Reorg places DEFINE NO objects that it encounters on the error queue.

NGTR310

DEFERRED NPI CLIX FOUND: databaseName.indexName.


Explanation:
During processing, NGT Reorg found an NPI clustering index defined with the DEFINE NO attribute. NGT Reorg does not support NPI clustering indexes defined with the DEFINE NO attribute.

User response: NGT Reorg, version 11.2.00, puts the DEFINE NO objects on the error queue and excludes them from the NGT processing. NGT Reorg, version 12.1.00, forwards the failing object to DSNUTILB for processing.

NGTR311

SPECIFIC PARTS SPECIFIED FOR PBG tableSpaceName.databaseName.


Explanation:
NGT Reorg has encountered a partition-by-growth (PBG) table space with specified partitions. NGT Reorg will send the specified PBG partitions to DSNUTILB for processing.

User response: No action is required.

NGTR312

PBG databaseName.spaceName DOES NOT HAVE A CLUSTERING INDEX.


Explanation: The utility has detected that the specified object does not have a clustering index. The utility will send the object to DSNUTILB for processing.

User response: No action is required.

NGTR313

'DB2 COMMAND'


Explanation: This message lists the db2 command about to be issued.

User response: No action is required.

NGTR314

ERROR PROCESSING DB2 COMMAND - R15=hexstring-1.


Explanation: The DB2 command displayed in message NGTR313 failed. DB2 returned the code shown in X'hexstring-1'. The command was not processed by DB2.

User response: Check the status of DB2. There should not be an error trying to issue a command.

NGTR315

NO OUTPUT FROM DB2 COMMAND. R15=hexstring-1, R0=hexstring-2.


Explanation: The DB2 command displayed in message NGTR313 failed. DB2 returned the code shown in X'hexstring-1'. The value in R0 is shown in X'hexstring-2'.

User response: Check the status of DB2. Contact BMC Customer Support.

NGTR316

NO OUTPUT FROM DB2 COMMAND.


Explanation: The DB2 command displayed in message NGTR313 either returned no output or contains a DB2 error message (DSN9nn).

User response: Any output received from DB2 will be printed. Look up the DSN9nnn message in the DB2 Messages and Codes manual. If you do not understand why there is a problem, contact BMC Customer Support.

NGTR317

DISPLAY COMMAND OUTPUT ERROR.


Explanation: The DB2 command displayed in message NGTR313 returned output that was not of the format expected.

User response: Any output received from DB2 will be printed. Contact BMC Customer Support.

NGTR318

DISPLAY COMMAND FORMAT ERROR.


Explanation: The format of the output from the -DISPLAY command has changed.

User response: Any output received from DB2 will be printed. Contact BMC Customer Support.

NGTR319

PROCESSING ON THIS SPACE IS IMPOSSIBLE BECAUSE ITS STATUS IS RESTRICTED BY DB2.


Explanation: Table spaces (all partitions) and all indexes on any table in that table space must not be in a state that prohibits execution of the utility. For example, REORG cannot be done if any space has:

  • CHKP—Check pending

  • RECP—Recovery pending

  • REST—Restarting

  • INDBT—In doubt

  • STOP—Stopped

User response: The appropriate DB2 utility must be used to correct the space status before rerunning NGT utilities on this space.

NGTR320

ERROR PROCESSING DB2 COMMAND - R15=hexstring-1.


Explanation: The DB2 command displayed in message NGTR313 failed. DB2 returned the code shown in X'hexstring-1'. The command was not processed by DB2.

User response: Check the status of DB2. There should not be an error trying to issue a command.

NGTR321

NO OUTPUT FROM DB2 COMMAND. R15=hexstring-1,R0=hexstring-2.


Explanation: The DB2 command displayed in message NGTR313 failed. DB2 returned the code X'hexstring-1'. The value in R0 is X'hexstring-2'.

User response: Check the status of DB2. Contact BMC Customer Support.

NGTR322

-STOP DID NOT TAKE EFFECT FOR SOME SPACES WITHIN RETRY LIMIT - RUN ABORTED.


Explanation: A -STOP was issued for the spaces to be processed. -DISPLAY commands were issued at intervals as specified in the +DSCRL parameter. After repeating the command the specified number of times, the space was still not in a stopped state.

User response: Determine why the space(s) cannot be stopped. An application may be processing against them. Rerun the utility when the space(s) can be stopped.

NGTR323

VSAM READ ERROR OCCURRED FOR SPACE DSNDB06. string-1 PAGE=number-1 (hexstring-1) - R15=hexstring-2.


Explanation: VSAM returned a non-zero code attempting to read a DB2 Catalog data set. Number-1 is the page number in decimal, and X'hexstring-1' is the page number in hex. X'hexstring-2' is the return code in hex.

User response: Verify that there is no physical error on the Catalog. Contact BMC Customer Support.

NGTR324

LOGIC ERROR - SPACE DSNDB06. string-1 PAGE=number-1 (hexstring-1 :DB2PFLAG=hexstring-2 INSTEAD OF hexstring-3.


Explanation: A page in this DB2 Catalog index appears to be structurally unsound. Number-1 is the page number in decimal, and X'hexstring-1' is the page number in hex. X'hexstring-2' is the page flag value found, while X'hexstring-3' is the value expected.

User response: Verify that there is no physical error on the Catalog. Contact BMC Customer Support.

NGTR325

LOGIC ERROR - SPACE DSNDB06. string-1 PAGE=number-1 (hexstring-1) LAST KEY PAST END OF PAGE.


Explanation: A page in this DB2 Catalog index appears to be structurally unsound. Number-1 is the page number in decimal, and X'hexstring-1' is the page number in hex. The DB2 'last key' offset is out of range.

User response: Verify that there is no physical error on the Catalog. Contact BMC Customer Support.

NGTR326

LOGIC ERROR - SPACE DSNDB06. string-1 PAGE=number-1 (hexstring-1) HAS KEY LENGTH ZERO.


Explanation: A page in this DB2 Catalog index appears to be structurally unsound. Number-1 is the page number in decimal, and X'hexstring-1' is the page number in hex. The DB2 key length in the page cannot be zero.

User response: Verify that there is no physical error on the Catalog. Contact BMC Customer Support.

NGTR327

LOGIC ERROR - SPACE DSNDB06. string-1 PAGE=number-1 (hexstring-1) LEAF PAGE IS EMPTY.


Explanation: A page in this DB2 Catalog index appears to be structurally unsound. Number-1 is the page number in decimal, and X'hexstring-1' is the page number in hex. A leaf page was expected but the page is empty.

User response: Verify that there is no physical error on the Catalog. Contact BMC Customer Support.

NGTR328

TABLESPACE tableSpaceName WAS NOT FOUND IN THE DB2 CATALOG, (STMT number-1).


Explanation: Utility control statement number number-1 named table space tableSpaceName. This table space is not defined to the DB2 subsystem named in the EXEC PARM.

User response: Check for typographical errors and for compatibility the names of the DB2 subsystem and the table space. Consider qualifying an unqualified table space name.

NGTR329

objectName IGNORED DUE TO +AUTOLOCK(YES). PLEASE SEE INSTALLER FOR ASSISTANCE.


Explanation: The utility has ignored the specified object because you specified +AUTOLOCK(YES).

User response: See the installer.

NGTR330

SCAN COMPLETE - number-1 PAGES READ, number-2 ROWS


Explanation: A sequential scan of a section of the table space is complete. This message summarizes the result of the scan.

User response: No action is required.

NGTR331

SYSIBM.SYSCOLUMNS_HIST INSERTED FOR string-1.string-2 (number-1)


Explanation: This message names the table space and part number updated in the DB2 Catalog.

User response: No action is required.

NGTR332

SYSIBM.SYSTABLES_HIST INSERTED FOR string-1.string-2


Explanation: This message names the table space and part number updated in the DB2 Catalog.

User response: No action is required.

NGTR333

SYSIBM.SYSCOLUMNS UPDATED FOR string-1.string-2 (number-1)


Explanation: This message names the table space and part number updated in the DB2 Catalog.

User response: No action is required.

NGTR334

string-1 - string-2.string-3 WAS NOT FOUND IN THE DB2 CATALOG.


Explanation: A utility control statement named a table space, index or table (string-1) string-2.string-3. This object is not defined to the DB2 subsystem named in the EXEC statement PARM field.

User response: Check for typographical errors and for compatibility the names of the DB2 subsystem and the index or table.

NGTR335

SYSIBM.SYSTABLEPART UPDATED FOR string-1.string-2 (number-1)


Explanation: This message names the table space and part number updated in the DB2 Catalog.

User response: No action is required.

NGTR336

SYSIBM.SYSTABLEPART_HIST INSERTED FOR string-1.string-2 (number-1)


Explanation: This message names the table space and part number updated in the History Statistics tables.

User response: No action is required.

NGTR337

SYSIBM.SYSTABLESPACE UPDATED FOR string-1.string-2


Explanation: This message names the table space updated in the DB2 Catalog.

User response: No action is required.

NGTR338

SYSIBM.SYSTABLESPACESTATS UPDATED FOR string-1.string-2 (number-1)


Explanation: This message names the table space and part number updated in the RTS tables.

User response: No action is required.

NGTR339

SYSIBM.SYSCOLSTATS UPDATED FOR string-1.string-2 (number-1)


Explanation: This message names the table space and part number updated in the DB2 Catalog.

User response: No action is required.

NGTR340

SYSIBM.SYSINDEXSTATS_HIST INSERTED FOR string-1 . string-2 (number-1).


Explanation: This message names the index name and part number updated in the DB2 Catalog.

User response: No action is required.

NGTR341

-START DID NOT TAKE EFFECT FOR SOME SPACES WITHIN RETRY LIMIT - RUN ABORTED.


Explanation: A -START command was issued for the spaces to be processed. -DISPLAY commands were issued at intervals as specified in the +DSCRL parameter. After repeating the command the specified number of times, the space was still not in a readable state.

User response: Determine why the space(s) cannot be started for read processing. An application may be processing against them. Rerun the utility when the space(s) can be read.

NGTR342

FUNCTION NOT SUPPORTED FOR CATALOG TABLESPACE tableSpaceName (STMT number-1).


Explanation: Utility control statement number number-1 named table space tableSpaceName. This is a Catalog or Directory table space, so the only supported function is COPY.

User response: You cannot REORG or LOAD a Catalog Table with NGT products. Contact BMC Customer Support.

NGTR343

string-1.string-2 (number-1) NOT FOUND IN SYSIBM.SYSTABLESPACESTATS, INSERTING ROW


Explanation: An update of the named RTS table failed because the row does not exist. An insert will be done for the named table space and part number.

User response: No action is required.

NGTR344

string-1.string-2 (number-1) NOT FOUND IN SYSIBM.SYSINDEXSPACESTATS, INSERTING ROW


Explanation: An update of the named RTS table failed because the row does not exist. An insert will be done for the named indexspace and part number.

User response: No action is required.

NGTR345

string-1.string-2 (number-1) NOT FOUND IN SYSIBM.SYSCOLSTATS, INSERTING ROW


Explanation: An update of the named SYSIBM table failed because the row does not exist. An insert will be done for the named object.

User response: No action is required.

NGTR346

UPDATE OR INSERT OF SYSIBM.SYSCOLSTATS FAILED FOR string-1.string-2 (number-1)


Explanation: An update or insert of the SYSIBM table SYSCOLSTATS failed for the named object.

User response: No action is required.

NGTR347

THE TABLE WAS NOT FOUND IN THE DB2 CATALOG: OBID(hexstring), SYSIBM.tableSpaceName


Explanation: In this message:

  • hexstring is the 2-byte OBID hexadecimal value of the indicated catalog table.
  • tableSpaceName is the DB2 catalog table name.

The indicated DB2 catalog table with the indicated OBID value was not found. The job will abend.

User response: Specify a valid DB2 catalog table in the SYSIN statement. If the problem persists, contact BMC Support.

NGTR348

STOGROUP string-1 WAS NOT FOUND IN THE DB2 CATALOG.


Explanation: The +ALLOTYPE routine requested retrieval of volumes for a Storage Group, string-1. This STOGROUP is not defined to the DB2 subsystem named in the EXEC PARM.

User response: No list of volumes is returned to the exit. Correct the exit routine.

NGTR349

DBD AND CATALOG INCONSISTENT FOR DB.TS string-1.string-2, STMT number-1.


Explanation: The number of partitions in SYSIBM.SYSTABLESPACE does not match the corresponding value in the DBD from the Directory.

User response: The run is aborted. Contact BMC Customer Support.

NGTR350

RUN CONTINUES - MISSING TABLESPACES IGNORED SINCE +ONERROR(CONTINUE).


Explanation: +ONERROR(CONTINUE) was specified. Statements referencing missing table spaces are ignored. If such statements are for copies to tape data sets, an empty file will be written to the tape.

User response: The run continues.

NGTR351

PART NUMBER EXCEEDS MAX PARTITION FOR DB.TS string-1.string-2, STMT number-1.


Explanation: The partition number specified in input control statement number number-1 exceeds the number of partitions in the table space.

User response: This is treated the same as a table space not found in Catalog, message number NGTR328. If +ONERROR(CONTINUE), then the statement is skipped, else the run aborts.

NGTR352

CONFLICTING FUNCS (REORG/SDELETE/LOAD/REPART/RESTORE) FOR string-1.string-2 string-3, STMT number-1


Explanation: Only one of the functions REORG, SDELETE, LOAD REPLACE, or REPART is allowed in the same input stream for the same table space.

User response: Put conflicting functions in different steps and resubmit the job.

NGTR353

COPY OF DB.TS string-1.string-2 string-3, STMT number-1 SKIPPED BECAUSE REORG SKIPPED.


Explanation: Input control statement number number-1 is a COPY of the named table space. A REORG of this table space was skipped (see NGTR352), making this copy redundant.

User response: No action is required.

NGTR354

TABLE string-1.string-2 WAS NOT FOUND IN THE DB2 CATALOG


Explanation: The utility control statement just printed named table string-1.string-2. This table is not defined to the DB2 subsystem named in the EXEC PARM.

User response: Check for typographical errors and for compatibility the names of the DB2 subsystem and the table. Consider qualifying an unqualified table name.

NGTR355

TABLE string-1 IS NOT UNIQUE IN THE DB2 CATALOG


Explanation: The utility control statement just printed named an unqualified table string-1. There is more than one table in the catalog with this name.

User response: Check for typographical errors and for compatibility the names of the DB2 subsystem and the table. You must qualify the table name if it is not unique.

NGTR356

TABLE string-1 IS NOT QUALIFIED, BUT DB2 IS NOT UP.


Explanation: The utility control statement just printed named an unqualified table string-1. DB2 is not active, so the table name must be qualified.

User response: You must specify creator.tablename if DB2 is not active.

NGTR357

TABLE tableName IS IN A TS WITH OTHER TABLES.


Explanation: The utility control statement just printed named a table that is in a table space that has more than one table. This utility does only supports single-table table spaces.

User response: The utility is aborted.

NGTR358

DB.TS tableSpaceName IS/HAS A LOB (NOT SUPPORTED)


Explanation: The above named table space is a DB2 LOB. It is currently not supported by NGT/superutilities.

User response: The statement will be skipped. MAXRC=4

NGTR359

DB.TS tableSpaceName HAS RRF (NOT SUPPORTED)


Explanation: The above named table space has reorder row format. It is not supported by the version of NGT/superutilities.

User response: The statement will be skipped. MAXRC=4

NGTR360

DBD UPDATE FAILED DURING FASTSWITCH PROCESSING (number-1)


Explanation: A catastrophic error has occurred trying to update the DBD with the new I/J name flags. number-1 is a code indicating where the error occurred.

User response: The run is aborted. Contact BMC Customer Support.

NGTR361

RELATED LOB DATA NOT FOUND FOR string-1.string-2, PROCESS ABORTED.


Explanation: An attempt to Query DB2 for Lob data related to the specified DB/TS returned no data.

User response: The run is aborted.

NGTR362

UNABLE TO CREATE DICTIONARY DUE TO INSUFFICIENT DATA. TABLESPACE tableSpaceName.


Explanation: An attempt to build a dictionary failed because there was not enough sample data read from the table.

User response: The dictionary page build process is bypassed.

NGTR363

UNABLE TO CREATE DICTIONARY DUE TO INSUFFICIENT DATA. TABLESPACE tableSpaceName PART number-1.


Explanation: An attempt to build a dictionary failed because there was not enough sample data read from the table.

User response: The dictionary page build process is bypassed.

NGTR364

OUTPUT ROWS FOR TABLE OBID hexstring-1 DO NOT MATCH INPUT COUNT. WRITE COUNT=number-1. READ COUNT=number-2.


Explanation: The count validation at the end of table space write failed for a specific table. This is almost always an internal logic error.

User response: The Reorg fails. The table space and all indexes are still in RW and have been unchanged by the Reorg. Check the status of DB2. Contact BMC Customer Support.

NGTR365

DISCARDED ROWS FOR TABLE OBID hexstring-1 DO NOT MATCH INPUT COUNT. OUT COUNT=number-1. IN COUNT=number-2.


Explanation: The count validation at the end of table space write failed for a specific table. This is almost always an internal logic error.

User response: The Reorg fails. The table space and all indexes are still in RW and have been unchanged by the Reorg. Check the status of DB2. Contact BMC Customer Support.

NGTR366

TREE LEVEL(number-1) COUNT ERROR EXPECTED=#9, ACTUAL=#9.


Explanation: The index tree level analysis reveals an inconsistency in the number of pages at a certain level. Level(1) is the Leaf level.

User response: The Reorg fails. The table space and all indexes are still in RW and have been unchanged by the Reorg. Check the status of DB2. Contact BMC Customer Support.

NGTR367

REORG PHASE 4 STARTING FOR TS tableSpaceName PART number-1 - IXSPACE string-3


Explanation: This message indicates that the named indexspace is beginning Phase 4 - Log Apply.

User response: No action is required.

NGTR368

REORG PHASE 4 STARTING FOR TS tableSpaceName - IXSPACE string-3


Explanation: This message indicates that the named indexspace is beginning Phase 4 - Log Apply.

User response: No action is required.

NGTR369

REORG PHASE 4 COMPLETED FOR TS tableSpaceName PART number-1 - IXSPACE string-3


Explanation: This message indicates that the indexspace Log Apply is complete.

User response: No action is required.

NGTR370

REORG PHASE 4 COMPLETED FOR TS tableSpaceName - IXSPACE string-3


Explanation: This message indicates that the indexspace Log Apply is complete.

User response: No action is required.

NGTR371

COUNTS ERR - TB hexstring-1, CLX hexstring-2, PT number-1 - TB = #8 ROWS, IX = #8, IXSPNM - string-1.


Explanation: This message is printed to indicate that the Reorg table space will abort because the clustering index rids count does not match the table rows count.

User response: Run Check Index against this object. If no error, contact BMC Customer Support.

NGTR372

COUNTS MISMATCH - string-1 - hexstring-1 - hexstring-2 (TYPE-PART-OBID) - INPUT COUNT #8, OUTPUT COUNT #8


Explanation: This message is printed to indicate that the Reorg table space will abort because there is a mismatch between input counts and output counts.

User response: Run Check Index against this object. If no error, contact BMC Customer Support.

NGTR373

DICTIONARY BUILD FAILED FOR TABLESPACE tableSpaceName string-3 string-4.


Explanation: The dictionary build processing for the referenced table space was not successful. The part will be specified if this is a partitioned table space.

User response: The job will continue processing and the creation of the dictionary will be skipped. Contact BMC Customer Support.

NGTR374

PREALLOCATING DATASETS FOR TS tableSpaceName - number-1 number-2 KPAGES


Explanation: This message signals the beginning of the preallocation of the table space.

User response: No action is required.

NGTR375

SYSIBM.SYSINDEXPART UPDATED FOR string-1.string-2 (number-1)


Explanation: This message names the indexspace name and part number updated in the DB2 Catalog.

User response: No action is required.

NGTR376

SYSIBM.SYSINDEXPART_HIST INSERTED FOR string-1.string-2 (number-1)


Explanation: This message names the indexspace name updated in the History Statistics table.

User response: No action is required.

NGTR377

SYSIBM.SYSINDEXES UPDATED FOR string-1.string-2


Explanation: This message names the indexspace name updated in the DB2 Catalog.

User response: No action is required.

NGTR378

SYSIBM.SYSINDEXES_HIST INSERTED FOR string-1.string-2


Explanation: This message names the indexspace name updated in the History Statistics table.

User response: No action is required.

NGTR379

SYSIBM.SYSINDEXSTATS UPDATED FOR string-1.string-2 (number-1)


Explanation: This message names the indexspace name and part number updated in the DB2 Catalog.

User response: No action is required.

NGTR380

SYSIBM.SYSINDEXSPACESTATS UPDATED FOR string-1.string-2 (number-1)


Explanation: This message names the indexspace name and part number updated in the RTS tables.

User response: No action is required.

NGTR381

SYSIBM.SYSTABSTATS UPDATED FOR TBCRE8 = string-1 (number-1)


Explanation: This message names the table creator and part number updated in the DB2 Catalog. The next line names the table.

User response: No action is required.

NGTR382

TABLE = string-1


Explanation: This message names the table updated in the DB2 Catalog or RTS tables.

User response: No action is required.

NGTR383

SYSIBM.SYSTABSTATS_HIST INSERTED FOR TBCRE8 = string-1 (number-1)


Explanation: This message names the table creator and part number updated in the DB2 Catalog. The next line names the table.

User response: No action is required.

NGTR384

SYSIBM.SYSTABLES UPDATED FOR TBCRE8 = string-1


Explanation: This message names the table creator updated in the DB2 Catalog. The next line names the table.

User response: No action is required.

NGTR385

UPDATE OR INSERT OF SYSIBM.SYSINDEXSPACESTATS FAILED FOR string-1.string-2 (number-1)


Explanation: The update or insert for the indicated object in the RTS table failed.

User response: No action is required.

NGTR386

UPDATE OR INSERT OF SYSIBM.SYSTABLESPACESTATS FAILED FOR string-1.string-2 (number-1)


Explanation: The update or insert for the indicated object in the RTS table failed.

User response: No action is required.

NGTR387

INDEX REORG STARTING FOR TS tableSpaceName PART number-1 - IXSPACE string-3


Explanation: This message indicates that the named indexspace is beginning Reorg - read and rewrite.

User response: No action is required.

NGTR388

INDEX REORG STARTING FOR TS tableSpaceName - IXSPACE string-3


Explanation: This message indicates that the named indexspace is beginning Reorg - read and rewrite.

User response: No action is required.

NGTR389

INDEX REORG COMPLETED FOR TS tableSpaceName PART number-1 - IXSPACE string-3


Explanation: This message indicates that the indexspace write is complete.

User response: No action is required.

NGTR390

INDEX REORG COMPLETED FOR TS tableSpaceName - IXSPACE string-3


Explanation: This message indicates that the indexspace write is complete.

User response: No action is required.

NGTR391

PREALLOCATING DATASETS FOR IX string-1.string-2 - number-1 number-2 KPAGES


Explanation: This message signals the beginning of the preallocation of the NPI.

User response: No action is required.

NGTR392

number-1 MEGS, #8 ROWS, number-2 ROWS/SCAN, number-3 SCANS, IAVG = number-4


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

User response: No action is required.

NGTR393

IF number-1 MEGS AVAILABLE, number-2 SCANS OF number-3 ROWS/SCAN


Explanation: The +INITWINDOW parm specifies the total memory that can be used for this reorg. Approximately 80% of this is assigned to the table space process. This message indicates that the process might be faster with more memory.

User response: No action is required.

NGTR394

SCAN STARTING - PAGES hexstring-1 TO hexstring-2 (HEX), number-1 CYLS


Explanation: A sequential scan of a section of the table space is beginning. This message notes the page range of the scan.

User response: No action is required.

NGTR395

RSCN - number-1 PRD, number-2 PRW, number-3 RWS, number-4 ROWS LEFT


Explanation: A sequential scan of a section of the table space is complete. This message summarizes the result of the scan.

User response: No action is required.

NGTR397

FRAMES AVAIL (number-1) LT MIN REQD (number-2) - RUN ABORTED


Explanation: The message displays the amount of real memory available at this time (in 4K frames) and the minimum amount the NPI translator requires. The run is aborted.

User response: No action is required.

NGTR398

LR COMPLETE - number-1 PAGES IN NEW TS - PCTF = number-2, FRPG = number-3


Explanation: The message displays the size of the new table space after reorg. It also shows the pctfree and freepage values used.

User response: No action is required.

NGTR399

LR STARTING FOR PBG tableSpaceName


Explanation: The message indicates that logical reorg is starting for the named PBG.

User response: No action is required.

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

Comments