Messages NGTB000 through NGTB999

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

SYNTAX ERROR - 'ALL' NOT SPECIFIED AND NO INDEXES NAMED - PROCESSING SKIPPED FOR TABLESPACE.


Explanation: Neither ALL nor a list of index names was specified for REBUILD INDEX processing, which is required. Processing continues but indexes are not rebuilt.

User response: To rebuild the indexes, correct the list of index names to be processed, or specify ALL, and rerun the job.

NGTB001

IX DBID - IXOBID (DBID-IXOBID) not same DB as TS DBID (DBID) - Processing skipped for Tablespace.


Explanation: The indicated index OBID does not match the indicated table space DBID, which is required for REBUILD INDEX processing. Processing is skipped for this table space.

User response: Correct the mismatch between the indexes and table spaces for the database. Rerun the job.

NGTB002

TABLESPACE IS DEFERRED - PROCESSING ABORTED.


Explanation: The table space is defined as deferred. Deferred table spaces are not valid for REBUILD INDEX processing and the job terminates.

User response: Ensure that no table spaces selected for REBUILD INDEX processing are deferred and rerun the job if needed.

NGTB003

TABLESPACE tableSpaceName CONTAINS NO {IXES | TBLS} - PROCESSING SKIPPED FOR TABLESPACE.


Explanation: The indicated table space, named on a REBUILD INDEX statement, has no indexes or tables, so the statement is skipped. (This is not an error because the statement might have been generated via a wild card specification.)

User response: No action is required.

NGTB004

MULTI-TABLE SIMPLE TABLESPACES NOT SUPPORTED BY UTILITY - PROCESSING SKIPPED FOR TABLESPACE.


Explanation: You attempted to use a multi-table simple table space with an NGT utility product, but these table spaces are not supported. The utility skips processing for this table space.

User response: Ensure that the table spaces selected for processing are supported table space types.

NGTB005

objectName not Partitioned but PART Numbers specified - Processing skipped for objectName.


Explanation: You specified PART for an object that is not partitioned. The utility skips processing for the indicated object.

User response: Remove the PART option, or change the object that you are operating on if appropriate. Rerun the job.

NGTB006

objectName is Partitioned but specified PART # exceeds # of objectName Parts - Processing skipped for objectName.


Explanation: You specified a partition number on the PART option that exceeds the number of partitions that are defined on the object. The utility skips processing for the indicated object.

User response: Correct the PART option and rerun the job.

NGTB007

Syntax Error - ALL specified but input contains Include(s) - Processing skipped for Tablespace.


Explanation: You specified both ALL and a list of included objects for REBUILD INDEX processing. These options are mutually exclusive.

User response: Correct the REBUILD INDEX syntax and rerun the job.

NGTB008

NO DBD entry found for input Index - Processing skipped for Index.


Explanation: The input index does not have a DBD entry, which REBUILD INDEX requires. REBUILD INDEX skips the processing for this index.

User response: Find the missing DBD or correct the input index and rerun the job.

NGTB009

Conflicting input - Multiple Includes but NO Parts - Processing skipped for Tablespace.


Explanation: You specified multiple include statements, but did not specify partitions. REBUILD INDEX requires that you specify partitions in this case.

User response: Specify the correct partitions for the multiple include statements and rerun the job.

NGTB010

Conflicting input - Exclude(s) Parts but NO Include(s) - Processing skipped for Index.


Explanation: You specified partitions to exclude but nothing to include. REBUILD INDEX requires an include statement in this case.

User response: Correct the include and exclude syntax and rerun the job.

NGTB011

Conflicting input - Both Include(s) Parts and Exclude(s) - Processing skipped for Index.


Explanation: You specified an exclude statement and also specified an include statement for partitions. REBUILD INDEX does not support this condition.

User response: Correct the include and exclude syntax and rerun the job.

NGTB012

Conflicting input - Both Tablespace Parts and Include(s) - Processing skipped for Index.


Explanation: You specified table space parts and also specified an include statement for partitions. REBUILD INDEX does not support this condition.

User response: Correct the syntax and rerun the job.

NGTB013

NO INDEXES ON TABLE. PROCESSING SKIPPED FOR tableSpaceName.


Explanation: The indicated table space does not have an index. An index is required for REBUILD INDEX processing. Processing is skipped for the indicated object.

User response: Correct the problem and rerun the job if appropriate.

NGTB014

TS = tableSpaceName; PT partitionNumber; ALLO allocatedSpace; USED usedSpace; PQ primaryQuantity; SQ secondaryQuantity; VL volume; DS numberOfDataSets; EX numberOfExtents - Processing complete for TS.


Explanation: This message provides diagnostic information for BMC Customer Support.

User response: No action is required.

NGTB015

Syntax Error - More than one Tablespace specified - Processing skipped for Tablespace.


Explanation: You specified multiple table spaces for REBUILD INDEX, but REBUILD INDEX processing supports only a single table space.

User response: Specify one table space per job step and rerun the job.

NGTB016

Syntax Error - Only Partitioned Tablespaces can be Excluded - Processing skipped for Tablespace.


Explanation: You specified EXCLUDE for a table space that is not partitioned. REBUILD INDEX exclude processing supports partitioned table spaces only.

User response: Correct the EXCLUDE statement and rerun the job.

NGTB017

More than one Table specified for non-Segmented Tablespace - Processing skipped for Tablespace.


Explanation: You specified more than one table for a non-segmented table space. REBUILD INDEX processing supports only a single table for non-segmented table spaces.

User response: Correct the syntax and rerun the job.

NGTB018

Syntax - Only Tables of Segmented Tablespaces can be Excluded - Processing skipped for Tablespace.


Explanation: You specified tables for a table space that is not segmented. REBUILD INDEX exclude processing is limited to tables of segmented table spaces. Processing is skipped for the table space.

User response: Correct the exclude statement and rerun the job.

NGTB019

Syntax - More than one non-Partitioned Tablespace specified - Processing skipped for Tablespace.


Explanation: You specified more than one nonpartitioned table space. REBUILD INDEX processing supports only a single nonpartitioned table space.

User response: Specify one table space per job step and rerun the job.

NGTB020

Syntax - Cannot Exclude all Parts of a Partitioned Tablespace - Processing skipped for Tablespace.


Explanation: You excluded all partitions of the table space. REBUILD INDEX processing requires that at least one partition be included.

User response: Correct the syntax and rerun the job.

NGTB021

Syntax Error - Specified PART Number range is not ascending - Processing skipped for Tablespace.


Explanation: You specified a range for PART that is not in ascending order. REBUILD INDEX processing requires that the range be in ascending order.

User response: Correct the syntax and rerun the job.

NGTB022

Syntax Error - Included PART Number number-1 is repeated - Processing skipped for Tablespace.


Explanation: You specified a partition more than once in your INCLUDE statement. REBUILD INDEX processing requires unique partition numbers.

User response: Correct the syntax and rerun the job.

NGTB023

Syntax Error - Excluded PART Number was never Included - Processing skipped for Tablespace.


Explanation: You specified a partition in your EXCLUDE statement that is not included. REBUILD INDEX processing requires that a partition be included before specifying it in an EXCLUDE statement.

User response: Correct the syntax and rerun the job.

NGTB024

Syntax Error - All Parts have been Excluded - Processing skipped for Tablespace.


Explanation: You excluded all partitions of the table space. REBUILD INDEX processing requires that at least one partition be included.

User response: Correct the syntax and rerun the job.

NGTB025

Syntax Error - Specified Table is not in the Tablespace - Processing skipped for Tablespace.


Explanation: You specified a table that is not in the table space that you are processing.

User response: Correct the specified table or table space name and rerun the job.

NGTB026

Syntax - Cannot specify both Includes and Excludes of Tables - Processing skipped for Tablespace.


Explanation: You specified tables in both the INCLUDE and EXCLUDE statements for REBUILD INDEX processing. These specifications are mutually exclusive.

User response: Correct the syntax and rerun the job.

NGTB027

Specified Table (OBID) does not belong to Tablespace - Processing skipped for Tablespace.


Explanation: The indicated table is not in the table space that you specified.

User response: Correct the table or table space name and rerun the job.

NGTB028

Syntax - Specified Table (OBID) Included multiple times - Processing skipped for Tablespace.


Explanation: The indicated table is included multiple times. REBUILD INDEX processing supports specifying a table only once.

User response: Correct the INCLUDE syntax and rerun the job.

NGTB029

Syntax - Specified Table (OBID) Excluded multiple times - Processing skipped for Tablespace.


Explanation: The indicated table is excluded multiple times. REBUILD INDEX processing supports excluding a table only once.

User response: Correct the EXCLUDE syntax and rerun the job.

NGTB030

WORK SELECTION MANAGER DID NOT FIND ANY MORE ITEMS IN THE OBJECT EXPAND QUEUE.


Explanation: The Work Selection Manager is empty. It did not identify any more items that match the naming pattern.

User response: No action is required.

NGTB031

WORK SELECTION MANAGER RETURNED AN ERROR.


Explanation: The Work Selection Manager encountered an error while attempting to process database object names.

User response: Contact BMC Customer Support for assistance.

NGTB032

SLAB ENTRY ENCOUNTERED WHEN NOT EXPECTED.


Explanation: An internal process detected an unexpected error.

User response: Contact BMC Customer Support for assistance.

NGTB033

SQL QUERY ERROR HAS OCCURRED.


Explanation: An unexpected SQL error occurred during utility processing.

User response: Contact BMC Customer Support for assistance.

NGTB034

ERROR OCCURRED WHEN ADDING ENTRY TO STATUS TABLE.


Explanation: An unexpected error occurred during processing.

User response: Contact BMC Customer Support for assistance.

NGTB035

ERROR OCCURRED WHEN ADDING ENTRY TO INFORMATION TABLE.


Explanation: An unexpected error occurred during processing.

User response: Contact BMC Customer Support for assistance.

NGTB036

SQL ERROR PROCESSING SELECT STATEMENT.


Explanation: An unexpected error occurred during processing.

User response: Contact BMC Customer Support for assistance.

NGTB037

EXCLUDE TYPE (I.E., TABLESPACE, TABLE, INDEX) DOES NOT MATCH SPECIFIED OBJECT TYPE.


Explanation: Processing detected a mismatch between the target object type and the object type being excluded. Object types must match when using an EXCLUDE clause.

User response: Change the SYSIN statement so that the type of object being excluded matches the target object type. Rerun the job.

NGTB038

NO MATCHES FOUND IN DB2 CATALOG FOR STATEMENT statementNumber.


Explanation: The SYSIN specified an object name or wildcard pattern that failed to match any objects in the DB2 catalog.

User response: Correct the object name or wildcard specification and rerun the job.

NGTB039

+SERVER(YES) IS REQUIRED FOR process PROCESSING.


Explanation: A submitted job attempted to use non-server processing, but server processing is required for the indicated process.

User response: Change the parameter value to +SERVER(YES) and resubmit the job.

NGTB040

No PENDING Indexes for TS - tableSpaceName


Explanation: REBUILD INDEX SCOPE PENDING found no pending indexes for the indicated table space.

User response: No action is required.

NGTB041

SERVER FOUND WORK FOR process.


Explanation: A server has identified work for the indicated process.

User response: No action is required.

NGTB042

SERVER SELECTED hexadecimalKey FOR queue/processName.


Explanation: A server has selected the indicated key for the indicated process.

User response: No action is required.

NGTB043

STARTING numberOfTapeServers TAPE SERVERS AND numberOfDiskServers DISK SERVERS.


Explanation: NGT processing has started additional tape and disk servers.

User response: No action is required.

NGTB044

STC SERVERS REQUESTED BUT +SVRPROC procName NOT SPECIFIED.


Explanation: NGT processing attempted to run a started task process, but+SVRPROC(STC) was not specified.

User response: Change the parameter to +SVRPROC(STC) and re-submit the job.

NGTB045

NGTSERVR STCPARM VALUE IS MISSING OR INVALID.


Explanation: NGT processing encountered an invalid started task parameter value.

User response: Correct the parameter value to a valid value and resubmit the job.

NGTB046

COMMAND RECEIVED - command.


Explanation: NGT processing received the indicated console command.

User response: No action is required.

NGTB047

RESERVED FOR COMMAND RESPONSE


Explanation: A general processing status message.

User response: No action is required.

NGTB048

REQUIRED DDNAME DATA NOT IN INFO IDB.


Explanation: An unexpected internal processing error occurred.

User response: Contact BMC Customer Support for assistance and provide them with this message.

NGTB049

TABLESPACE HAS databaseName.tableSpaceName PENDING DDL WITH PENDING RECOVER


Explanation: The table space being reorganized has a PENDING RECOVER in the SYSIBM.SYSPENDINGDDL table.

User response: No action is required.

NGTB050

DUPLICATE KEYS FOUND FOR A UNIQUE INDEX.


Explanation: The utility is processing a unique index, but encountered duplicate keys. The index in error is named in the next message.

User response: DROP the index and re-create it as a non-unique index. Rerun the job step.

NGTB051

SYNTAX ERROR - NOT ALL MASSDELETED PARTS WERE INCLUDED - PROCESSING SKIPPED FOR THIS TS.


Explanation: Partitions that were not specified were also deleted during MASSDELETE processing. All mass-deleted partitions must be specified in order to process this table space.

User response: Include all mass-deleted partitions when processing this object.

NGTB052

ANALYZING INDEXES FOR TABLESPACE tableSpaceName


Explanation: The utility is analyzing the table space in preparation for rebuilding indexes.

User response: No action is required.

NGTB053

REBUILD IS MISSING DATA FROM PART partitionNumber for dbid - psid - tbid (dbid-psid-tbid)


Explanation: While preparing for the final merge, the utility determined that not all data is available and terminated. This is an internal error.

User response: Contact BMC Customer Support.

NGTB054

REBUILD INDEX PHASE phaseNumber STARTING FOR tableSpaceName PART partitionNumber


Explanation: The rebuild process has started for indexes on the indicated table space. The partition number displays if the table space is partitioned.

User response: No action is required.

NGTB055

REBUILD INDEX PHASE phaseNumber STARTING FOR tableSpaceName


Explanation: The rebuild process has started for indexes on the indicated table space.

User response: No action is required.

NGTB056

REBUILDING INDEX indexName


Explanation: The utility has completed the read process for the table space and has started the index-write process for the indicated index.

User response: No action is required.

NGTB057

CALLING MERGE FOR INDEX indexName


Explanation: The utility has completed the table space read process. The utility is passing the keys for the indicated index to a merge process.

User response: No action is required.

NGTB058

REBUILD INDEX PHASE phase COMPLETED FOR tableSpaceName PART partitionNumber


Explanation: The rebuild process has completed for indexes on the indicated table space. For partitioned table spaces, this message lists the partition number.

User response: No action is required.

NGTB059

REBUILD INDEX PHASE phase COMPLETED FOR tableSpaceName


Explanation: The rebuild process has completed for indexes on the indicated table space.

User response: No action is required.

NGTB060

READING TABLESPACE tableSpaceName FOR DISTRIBUTION STATISTICS


Explanation: The utility is analyzing information for the indicated table space in preparation for a running distribution statistics.

User response: No action is required.

NGTB061

TOO MANY ROWS TO PROCESS THIS TABLESPACE. WILL BE FIXED IN A FUTURE VERSION OF REBUILD.


Explanation: The memory allotted to the rebuild function has been exceeded.

User response: If multiple indexes were being rebuilt, try rebuilding fewer indexes. If you are unable to rebuild fewer indexes, consider changing the indexes to nonpadded indexes.

NGTB062

THE MEMBER memberName WAS NOT FOUND IN THE NGTSVR PDS.


Explanation: A server parameter referred to a member that does not exist in the server PDS.

User response: Check the spelling of the member name or review the member list for the PDS. Correct the name and resubmit the job.

NGTB063

ERROR OCCURRED READING memberName FROM THE NGTSVR PDS.


Explanation: An unexpected condition occurred while reading a member of a server PDS.

User response: Contact BMC Customer Support and provide this message number and text.

NGTB064

NGTSVR PDS HAS AN INVALID LRECL.


Explanation: The server PDS is defined with an invalid logical record length.

User response: Copy the members of the server PDS into another server PDS with a valid logical record length. Resubmit the job.

NGTB065

ERROR OCCURRED ALLOCATING THE NGTSVR PDS: string-1


Explanation: An unexpected condition occurred while allocating the server PDS for this job.

User response: Review the messages in the JES message log for additional information about the problem. If you need assistance determining the cause of the problem, contact BMC Customer Support.

NGTB066

OPEN FAILED FOR THE NGTSVR PDS.


Explanation: An unexpected condition occurred while opening the server PDS for this job.

User response: Review the messages in the JES message log for additional information about the problem. If you need assistance determining the cause of the problem, contact BMC Customer Support.

NGTB068

PARTS SPECIFIED BUT NON-PARTITIONED TABLESPACE (tableSpaceName) ENCOUNTERED.


Explanation: PART(S) was specified on the utility statement, but one or more of the table spaces are not partitioned.

User response: Correct the SYSIN statement and resubmit the job.

NGTB069

XRTSSYIN REXX EXEC NOT FOUND.


Explanation: (RTS(,GENERATESYSIN) requires the XRTSSYIN automation control point to run successfully. XRTSSYIN was not found in the NGTAUTO library.

User response: Add an XRTSSYIN automation control point to the NGTAUTO library.

NGTB070

CHECK INDEX SUCCESSFUL FOR INDEX(SPACE) indexSpaceName - numberOfRows ROWS


Explanation: NGT Check found no errors analyzing the indicated index.

User response: No action is required.

NGTB071

CHECK INDEX SUCCESSFUL FOR INDEX(SPACE) indexSpaceName (partitionNumber) - numberOfRows ROWS


Explanation: NGT Check found no errors analyzing the indicated index and partition.

User response: No action is required.

NGTB072

CHECK INDEX FAILED ON sectionNumber (OF totalNumberOfSections) TS SECTIONS FOR INDEX(SPACE) indexSpaceName


Explanation: NGT Check found inconsistencies between the table space and the indicated index. Check Index performs the analysis on the table space by sections. The message indicates the degree of the problem.

User response: Rebuild the index.

NGTB073

CHECK INDEX FAILED ON sectionNumber (OF totalNumberOfSections) TS SECTIONS FOR INDEX(SPACE) indexSpaceName PART partitionNumber


Explanation: NGT Check found inconsistencies between the table space and the indicated index. Check Index performs the analysis on the table space by sections. The message indicates the degree of the problem.

User response: Rebuild the index.

NGTB074

CHECK INDEX COUNT MISMATCH - TS(numberOfTableSpaceRows) IX(numberOfIndexedRows) - INDEX(SPACE) indexSpaceName


Explanation: NGT Check found inconsistencies between the table space and the indicated index. The number of rows indexed does not match the number of rows in the table space.

User response: Rebuild the index.

NGTB075

CHECK INDEX COUNT MISMATCH - TS(numberOfTableSpaceRows) IX(numberOfIndexedRows) - INDEX(SPACE) indexSpaceName PART partitionNumber


Explanation: NGT Check found inconsistencies between the table space and the indicated index. The number of rows indexed does not match the number of rows in the table space.

User response: Rebuild the index.

NGTB076

CHECK INDEX COMPLETED FOR TABLESPACE tableSpaceName


Explanation: The CHECK INDEX run for the indicated table space completed. Messages follow for each index.

User response: No action is required.

NGTB077

CHECK INDEX COMPLETED FOR TABLESPACE tableSpaceName PART partitionNumber


Explanation: The CHECK INDEX run for the indicated table space completed. Messages follow for each index.

User response: No action is required.

NGTB078

INDEX indexName CONTAINS number INVALID RIDS


Explanation: The CHECK INDEX run for the indicated nonpartitioned index completed, but found RIDs that have invalid partition flags.

User response: This index should be rebuilt.

NGTB079

TABLESPACE tableSpaceName IS A CLONE - PROCESSING SKIPPED FOR TABLESPACE.


Explanation: The utility does not currently support clone table spaces.

User response: No action is required.

NGTB080

SHRLEVEL REFERENCE IGNORED, SHRLEVEL CHANGE WILL BE USED.


Explanation: SHRLEVEL REFERENCE was specified on the CHECK INDEX or DSTATS statement. These utilities always run in RW mode.

User response: No action is required.

NGTB081

TCP/IP INTERFACE FOR CKPT string-1 NOT FOUND.


Explanation: The TCP/IP listener does not seem to be active. The interface cannot display output for this utility without the listener functioning.

User response: No action required.

NGTB082

INDEX indexName - PAGE hexPageNumber POINTS TO TS PAGE hexPageNumber, MAX IS hexMaxTableSpacePages


Explanation: NGT Check running on the indicated index detected an invalid RID with a page reference outside the size of the table space.

User response: Rebuild the index.

NGTB083

UNABLE TO SUBMIT ALL SERVERS DUE TO A DUPLICATE JOBNAME - string-1. PROCESSING ENDS.


Explanation: An attempt to generate a unique jobname for a server failed.

User response: Verify the job mask specified on the job card. If the mask is valid, check to see if server jobs are sitting in the JES INPUT queue.

NGTB084

ALLOCATED DD string-1 DOES NOT MATCH DSN IN MASTER. DD REPLACED WITH MASTER DSN.


Explanation: The specified DD DSN does not match the DSN specified for the Master job.

User response: The DD is reallocated using the data from the Master job. No action is required.

NGTB085

+SVRDISK(0) IS NOT SUPPORTED.


Explanation: The specified parameters are inconsistent. Some server value must be used.

User response: Change the parameters and resubmit the job.

NGTB086

INVALID APPLICATION TYPE FOR COPY.


Explanation: The application name used on the COPY statement is not valid for the COPY utility.

User response: Change the SYSIN and resubmit the job.

NGTB087

DOWN LEVEL SOFTWARE DETECTED. PROCESSING ENDS.


Explanation: The Sever and Master jobs are running on different levels of the product. Inconsistent results would occur.

User response: Check the STEPLIBs used for the Master and Server JCL.

NGTB088

TABLESPACE HAS NO INDEXES - REBUILD STATEMENT SKIPPED.


Explanation: Rebuild Index was submitted against a tablespace that does not have any indexes defined.

User response: Check the spelling or name of the tablespace specified for the job, correct it, and then resubmit the job.

NGTB089

DDNAME string-1 ALLOCATED TO string-2.


Explanation: The DDNAME is allocated to the specified data set.

User response: No action is required.

NGTB090

TABLESPACE string-1.string-2 IS A LOB - PROCESSING SKIPPED FOR TABLESPACE.


Explanation: LOB tablespaces are not Reorganized in this release.

User response: No action is required.

NGTB091

REBUILD INDEX SUBTASK STARTED FOR INDEXSPACE string-1.string-2


Explanation: A processing subtask has been started for this index. The message names the indexspace. A following message prints the entire index name.

User response: No action is required.

NGTB092

REBUILD INDEX SUBTASK STARTED FOR INDEXSPACE string-1.string-2 PART number-1


Explanation: A processing subtask has been started for this index. The message names the indexspace. A following message prints the entire index name.

User response: No action is required.

NGTB093

CHECK INDEX SUBTASK STARTED FOR INDEXSPACE string-1.string-2


Explanation: A processing subtask has been started for this index. The message names the indexspace. A following message prints the entire index name.

User response: No action is required.

NGTB094

CHECK INDEX SUBTASK STARTED FOR INDEXSPACE string-1.string-2 PART number-1


Explanation: A processing subtask has been started for this index. The message names the indexspace. A following message prints the entire index name.

User response: No action is required.

NGTB095

REBUILD INDEX FOR LOB TABLESPACE string-1.string-2 NOT SUPPORTED - PROCESSING SKIPPED.


Explanation: The rebuild process does not support lob tablespaces at this time. This tablespace will be skipped.

User response: No action is required.

NGTB097

TABLESPACE string-1.string-2 IS XML - PROCESSING SKIPPED FOR TABLESPACE.


Explanation: NGT Reorg does not process XML table spaces in this release.

User response: No action is required.

NGTB098

GENERIC SYNTAX ERROR MESSAGE


Explanation: An unexpected condition occurred during processing.

User response: Contact BMC Customer Support or your local representative with this message number and text.

NGTB099

string-1.string-2 (number-1) number-2 PAGES EXCEEDS MAXIMUM ALLOWABLE SIZE OF number-3 PAGES


Explanation: REBUILD INDEX will process data sets up to a maximum size. The tablespace exceeded that maximum. The value in parentheses is the partition number.

User response: Contact BMC Customer Support or your local representative.

NGTB100

ERROR OCCURRED WHILE PROCESSING DISCARD DATA.


Explanation: An unexpected condition occurred during processing of the discard data.

User response: Contact BMC Customer Support or your local representative with this message number and text.

NGTB101

ERROR OCCURRED WHEN ADDING DISCARD DATA TO INFORMATION TABLE.


Explanation: An unexpected condition occurred during processing.

User response: Contact BMC Customer Support or your local representative with this message number and text.

NGTB102

TABLESPACE string-1.string-2 IS VERSIONED, LOAD REPLACE NOT ALLOWED - PROCESSING SKIPPED


Explanation: LOAD REPLACE is not allowed on Versioned Tables. Check the IBM Utility documentation.

User response: No action is required.

NGTB103

LIBRARY LEVELID MISMATCH. PROCESSING ENDS.


Explanation: A utility was restarted using a library with a different maintenance level that is not compatible with the control files built by the original maintenance level.

User response: Restart the utility using the original maintenance level. Contact BMC Customer Support or your local representative

NGTB104

UNABLE TO DETERMINE JOBNAME FOR STARTED TASK SERVERS.


Explanation: The JOBCARD member did not contain a valid JOB card. Without a valid JOB card, the JOBNAME for the started task servers cannot be determined.

User response: Verify the JOBCARD member contains a valid JOB card. Contact BMC Customer Support or your local representative

NGTB105

UNABLE TO DELETE string-1 - OUTPUT FILE WILL NOT BE DELETED.


Explanation: The data set could not be deleted. Either it did not exist or it is being held by another job.

User response: Manually delete the data set. Contact BMC Customer Support or your local representative for more information.

NGTB106

TABLESPACE string-1.string-2 IS AN INSTANCE - PROCESSING SKIPPED FOR TABLESPACE.


Explanation: INSTANCED tablespaces not processed by this release.

User response: No action is required.

NGTB108

TS tableSpaceName HAS ROTATED PARTS AND CONFLICTS WITH REBALANCE SUPPORT.


Explanation: The indicated table space contains rotated partitions and you specified REBALANCE on the REORG command. NGT Reorg does not support this scenario and terminates processing for this table space.

User response: Remove the REBALANCE option and rerun the job.

NGTB109

TS tableSpaceName HAS ROTATED PARTS AND CONFLICTS WITH ALTER LIMITKEY SUPPORT


Explanation: The indicated table space contains rotated partitions and pending limit key changes. NGT Reorg does not support this scenario and terminates processing for this table space.

User response: Use another method to materialize the rotated partitions and pending limit key changes. If appropriate, rerun the NGT Reorg job.

NGTB110

string-1 (number-1) - TREE PAGE - #8 PAGES, number-2 KEYS, #8 SPACE USED


Explanation: Reporting a summary after index read. This line summarizes tree pages.

User response: No action is required.

NGTB111

string-1 (number-1) ROOT PG# hexstring-1, ID hexstring-2, FLGS hexstring-3, number-2 LVLS, string-2 string-3 string-4


Explanation: Displays index root page information.

User response: No action is required.

NGTB112

PAGE REFC


Explanation: Displays pages referenced by this page.

User response: The index may need to be rebuilt.

NGTB113

LEAF PAGES COUNT MISMATCH - FROM TREE PAGES = #8, LEAFSREAD = #8


Explanation: CHECK has found a count mismatch between the number of leaf pages read and the number pointed to by tree pages.

User response: The index may need to be rebuilt.

NGTB114

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


Explanation: CHECK has found a Tree level inconsistency at the named index page.

User response: The index may need to be rebuilt.

NGTB115

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


Explanation: CHECK has found a Leaf page that is referenced by multiple Tree pages. This may cause SQL Delete/Insert errors.

User response: The index may need to be rebuilt.

NGTB116

COUNTS MISMATCH - TBL hexstring-1 (number-1) HAS #8 ROWS, IX HAS #8, IXSPNM - string-1.


Explanation: Counts from the table do not match counts from the index. There should be detail messages showing rows with no index or index entries with no corresponding row.

User response: The index may need to be rebuilt.

NGTB117

- RUN TERMINATED - number-1 INDEXES WITH ERRORS


Explanation: There were errors in the shown number of indexes. If this is a partitioned tablespace and errors were found in the partitioned indexes, NPI checking will be bypassed.

User response: The index(es) may need to be rebuilt.

NGTB118

- MISSING TS PART number-1


Explanation: This is an internal error - Some of the tablespace parts did not record their summary values for the NPI processor.

User response: Contact BMC Customer Support or your local representative with this message number and text.

NGTB119

KEY SEQC ERR - TS string-1.string-2, IX string-3 (number-1). PG hexstring-1 - KEYS AT hexstring-2 - hexstring-3


Explanation: CHECK has found a Leaf page that has keys out of sequence within the page. This may cause SQL Delete/Insert errors.

User response: The index may need to be rebuilt.

NGTB120

- CHECK SUCCESSFUL FOR INDEX string-1 (number-1), #8 ROWS


Explanation: Check has completed successfully - all tests were positive. The value in the parentheses is the part number. It will be 0 if not a partitioned index.

User response: No action is required.

NGTB121

KEY TREE ERR - TS string-1.string-2, IX string-3 (number-1). PG hexstring-1 - KEYS AT hexstring-2 - hexstring-3


Explanation: CHECK has found a Tree page that has keys out of sequence within the page. This may cause SQL Delete/Insert errors.

User response: The index may need to be rebuilt.

NGTB122

PROCESSING SKIPPED FOR TABLESPACE databaseName.tableSpaceName.


Explanation: NGT Reorg encountered an error while attempting to reorganize the indicated table space and terminates processing for this table space.

User response: Review additional messages reported for this table space to determine the cause of the error. Follow the instructions provided in the documentation for these additional messages.

NGTB123

REBALANCE DOES NOT SUPPORT OBJECTS WITH unsupportedFeature .


  Explanation:   The REORG REBALANCE job has stopped because objects selected for processing contain an unsupported feature.

  User response:   Perform one of the following actions and rerun the REORG job:

  • Remove the object that contains the unsupported feature.

  • Remove the REBALANCE keyword from the REORG SYSIN statement.

NGTB124

REORG WITH DISCARD IS NOT SUPPORTED FOR ALTER LIMKEYS. PROCESSING SKIPPED (TS tableSpaceName).


  Explanation:   Limit key changes are pending on the indicated table space and you specified DISCARD on the REORG command. NGT Reorg does not support this scenario and terminates processing of this table space.

  User response:   Remove the DISCARD option and rerun the job.

NGTB125

TS databaseName.tableSpaceName HAS PENDING ALTERS AND CONFLICTS WITH REBALANCE SUPPORT


Explanation: The REORG REBALANCE job has stopped because it has detected that pending alters exist for this table space.

User response: Perform the following actions:

  1. Remove the REBALANCE command option from the NGT REORG SYSIN command.

  2. Rerun the reorganization to materialize all pending alters.

You can then rerun the reorganization with the REBALANCE option.

NGTB126

TS tableSpaceName IS NON-PARTITIONED AND CONFLICTS WITH REBALANCE SUPPORT.


Explanation: You specified REBALANCE to rebalance partitions during the reorganization of the indicated table space. However, this table space is not partitioned.

User response: Remove the REBALANCE option or change the table space name, and rerun the reorganization.

NGTB128

RUNSTATS FOR VERSIONED TABLESPACE databaseName.tableSpaceName IS NOT SUPPORTED - PROCESSING SKIPPED.   


Explanation: NGTSTATS does not currently support versioned objects. Processing for versioned objects is skipped.

User response: No action is required.

 

NGTB127

TS tableSpaceName HAS A PART SPECIFICATION WHICH CONFLICTS WITH REBALANCE SUPPORT.


Explanation: You specified REBALANCE to rebalance partitions during the reorganization of the indicated table space, but specified a subset of partitions. NGT Reorg does not support partition rebalancing on a partial reorganization.

User response: Remove the partition specification or the REBALANCE option, and rerun the reorganization.

NGTB130

TS string-1.string-2 SPCMP PG hexstring-1 (number-1) HAS INV OBID hexstring-2


Explanation: The segmented TS space map page in the named partition has an OBID that is not a valid obid and the segment is not empty.

User response: Obtain a DSN1PRNT of the specified page and call BMC Customer Support.

NGTB131

TS string-1.string-2 SPCMP PG hexstring-1 HAS INV OBID hexstring-2


Explanation: The segmented TS space map page has an OBID that is not a valid OBID and is not an empty segment.

User response: Obtain a DSN1PRNT of the specified page and call BMC Customer Support.

NGTB132

TS string-1.string-2 (number-1) #8 PTRS, PTR-OFL AVG DISTANCE number-2


Explanation: The segmented TS has the shown number of ptr/oflow rows. the avg distance between a ptr and its overflow is shown. A high number indicates a valid reason to Reorg the TS.

User response: No action is required.

NGTB133

TS string-1.string-2 (number-1) number-2 LT PREFETCH, number-3 GT 2X PREFETCH


Explanation: This is a continuation of message NGTB132. It shows how many of the ptr-oflow pairs are within the DB2 prefetch size (and hence have no performance impact) and how may exceed twice the prefetch size. The latter have a serious performance impact.

User response: No action is required.

NGTB134

TS string-1.string-2 number-1 PTRS, number-2 OFLOW - RUN ABORTED


Explanation: At the completion of the table space read, the number of pointers does not match the number of overflows. REBUILD INDEX WILL NOT FIX THIS. This is a table space error.

User response: Recovery of the table space may be required.

NGTB135

TABLESPACE string-1.string-2 IS PBG OR PBR - PROCESSING SKIPPED FOR TABLESPACE.


Explanation: Processing of objects defined as PBG or PBR are not supported at this level.

User response: Processing for this object will be skipped.

NGTB136

TABLESPACE tableSpaceName USES DB2 versionNumber NFM FEATURES - PROCESSING SKIPPED FOR THIS TABLESPACE.


Explanation: You attempted to use a DB2 feature that the utility does not support. Additional messages, such as NGTU766 or NGTZ999, provide more information about the unsupported feature. The utility skips processing for this object.

User response: If applicable, change and resubmit the job, or contact BMC Customer Support.

NGTB148

"CLEANUP" PROCESSING ENDED WHILE IN A STEP-MUST-COMPLETE STATE.

Explanation: Clean-up processing ended while the job was in a Step-Must-Complete state. The cleanup is not finished and may require manual intervention.

User response: Contact BMC Support or your local representative with the message number and details.

NGTB153

TABLESPACE string-1.string-2 IS PARTITIONED AND NOCLIX - PROCESSING SKIPPED FOR TABLESPACE.


Explanation: A REORG of a partitioned tablespace with the NOCLIX keyword specification is not allowed.

User response: No action is required.

NGTB154

PARTITION NUMBER SPECIFIED (number-1) EXCEEDS MAX ALLOWED (number-2) FOR OBJECT (string-1.string-2).


Explanation: PART(S) have been specified that exceed the maximum number of partitions for the object.

User response: Correct the SYSIN statement and resubmit.

NGTB190

#ERREL ERRORS


Explanation: An internal logic error or an unrecoverable error has occurred. The message should be on //SYSERROR to describe the condition.

User response: Contact BMC Customer Support or your local representative with this message number and text.

NGTB202

CHECK INDEX STARTING READ FOR string-1 string-2.string-3.


Explanation: This message marks the start of CHECK INDEX read processing for the named object (TS/IX).

User response: No action is required.

NGTB203

CHECK INDEX STARTING READ FOR string-1 string-2.string-3 PART number-1 .


Explanation: This message marks the start of CHECK INDEX read processing for the named object (TS/IX).

User response: No action is required.

NGTB206

CHECK INDEX COMPLETED READ PROCESSING FOR string-1 string-2.string-3.


Explanation: This message marks the completion of CHECK INDEX read processing for the named object (TS/IX).

User response: No action is required.

NGTB207

CHECK INDEX COMPLETED READ PROCESSING FOR string-1 string-2.string-3 PART number-1.


Explanation: This message marks the completion of CHECK INDEX read processing for the named object (TS/IX).

User response: No action is required.

NGTB208

CHECK INDEX PHASE number-1 STARTING FOR string-1 string-2.string-3.


Explanation: This message marks the start of CHECK INDEX processing for the named phase on the named tablespace.

User response: No action is required.

NGTB209

CHECK INDEX PHASE number-1 STARTING FOR string-1 string-2.string-3 PART number-2


Explanation: This message marks the start of CHECK INDEX processing for the named phase on the named tablespace.

User response: No action is required.

NGTB210

CHECK INDEX PHASE number-1 COMPLETED FOR string-1 string-2.string-3.


Explanation: This message marks the completion of CHECK INDEX processing for the named phase and named tablespace.

User response: No action is required.

NGTB211

CHECK INDEX PHASE number-1 COMPLETED FOR string-1 string-2.string-3 PART number-2


Explanation: This message marks the completion of CHECK INDEX processing for the named phase and named tablespace.

User response: No action is required.

NGTB213

REORG WITH DDLIN NOT ALLOWED WITH +FASTSWITCH(NO). PROCESSING ABORTED FOR TS tableSpaceName.


Explanation: You included a DDLIN DD to perform partition rebalancing on the indicated table space during the reorganization. However, the UTLPARMS parameter +FASTSWITCH is NO, which is not supported for partition rebalancing.

User response: Specify +FASTSWTICH(YES) and rerun the job.

NGTB215

RUNSTATS STARTING READ FOR string-1 string-2.string-3 PART number-1.


Explanation: This message marks the start of RUNSTATS read processing for the named Index.

User response: No action is required.

NGTB216

REORG REBALANCE NOT ALLOWED WITH +FASTSWITCH(NO). PROCESSING ABORTED FOR TS tableSpaceName.


Explanation: You specified REBALANCE on your REORG command. However the UTLPARMS parameter +FASTSWITCH is NO, which is not supported for partition rebalancing.

User response: Specify +FASTSWITCH(YES) and rerun the job.

NGTB217

RUNSTATS COMPLETED READ PROCESSING FOR string-1 string-2.string-3 PART number-1.


Explanation: This message marks the completion of RUNSTATS read processing for the named Index.

User response: No action is required.

NGTB220

SERVER SUBMITTED - NAME(string-1) JESID(string-2).


Explanation: This message shows the JOBNAME and JESID of a submitted server.

User response: No action is required.

NGTB221

NGTWORK DISPLAY STARTED.


Explanation: The NGTWORK DISPLAY command has started.

User response: No action is required.

NGTB222

NGTWORK DISPLAY COMPLETED.


Explanation: The NGTWORK DISPLAY command has completed.

User response: No action is required.

NGTB223

NGTWORK NAME(string-1) SET number-1 ASSIGNED TO THIS UTILITY.


Explanation: The permanent work file set has been assigned the to current utility. This utility will use this set of permanent work files.

User response: No action is required.

NGTB224

NGTWORK NAME(string-1) SET number-1 RELEASED.


Explanation: The permanent work file set has been released and is available for use by another utility.

User response: No action is required.

NGTB225

NGTWORK NAME(string-1) SET number-1 string-2 FILE RESET.


Explanation: The permanent work file specified has been reset in preparation for use by the current utility.

User response: No action is required.

NGTB226

NGTWORK NAME(string-1) SET number-1 string-2 FILE RESET FAILED (LISTC ERROR).


Explanation: An attempt was made to reset a work file. The reset failed because a LISTC of the work file failed.

User response: Verify the work file data set exists. Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB227

NGTWORK NAME(string-1) SET number-1 string-2 FILE RESET FAILED (LOCATE ERROR).


Explanation: An attempt was made to reset a work file. The reset failed because a LOCATE of the work file failed.

User response: Verify the work file data set exists. Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB228

NGTWORK NAME(string-1) SET number-1 string-2 FILE HAS EXCEEDED MAX SIZE.


Explanation: The specified work file has exceeded the MAXSIZE parameter of the NGTWORK command. The file will be deleted and allocated with initial values.

User response: No action is required.

NGTB229

NGTWORK NAME(string-1) DEFINE RECORD WAS NOT FOUND.


Explanation: The DEFINE record was not found for the specified NGTWORK set.

User response: Verify the name specified in the NGTWORK NAME() parameter or in the +WORKMODE() parameter is correct. Contact BMC Customer Support or your local representative

NGTB230

NGTWORK NAME(string-1) DOES NOT HAVE ANY SETS AVAILABLE.


Explanation: The specified set does not have any work file sets available for use by this utility.

User response: No action is required.

NGTB231

NGTWORK NAME(string-1) SET number-1 IS NOT RESERVED BY THIS UID.


Explanation: The utility tried to release the specified work file set, but found that the utility was not the owner of the set.

User response: Verify the name specified in the NGTWORK NAME() parameter or in the +WORKMODE() parameter is correct. Contact BMC Customer Support or your local representative

NGTB232

NGTWORK NAME(string-1) SET number-1 string-2 FILE ALLOCATION FAILED.


Explanation: Allocation of the specified work file set file failed.

User response: Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB233

NGTWORK NAME(string-1) SET number-1 string-2 FILE IS UNUSABLE.


Explanation: An error has occurred while attempting to process the specified work file set file. The work file set will be marked as unusable.

User response: Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB234

UPDATE OF NGTWORK DATA SET INFORMATION FAILED.


Explanation: An error occurred while attempting to update the CKPT file with NGTWORK usage information.

User response: Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB235

UID 'string-1' - +WORKMODE(PERM) SPECIFIED BUT THERE ARE NO WORKFILE SETS AVAILABLE.


Explanation: +WORKMODE(PERM) has been specified but all the work file sets are assigned to other utilities or marked as unusable.

User response: The utility is terminated. Rerun the utility when a work file set is available or use +WORKMODE(ANY) to allocated temporary work files.

NGTB236

NGTWORK NAME(string-1) SET number-1 RELEASE STARTED.


Explanation: NGTWORK RELEASE command has started.

User response: No action is required.

NGTB237

NGTWORK NAME(string-1) SET number-1 RELEASED FROM UID string-2 IN JOB string-3 (string-4).


Explanation: The NGTWORK RELEASE command has released the specified workfile set.

User response: No action is required.

NGTB238

NGTWORK NAME(string-1) SET number-1 RELEASE COMPLETED SUCCESSFULLY.


Explanation: NGTWORK RELEASE command has completed successfully.

User response: No action is required.

NGTB239

NGTWORK NAME(string-1) SET number-1 DOES NOT EXIST.


Explanation: The workfile set specified by the NGTWORK RELEASE command does not exist.

User response: Verify the name specified in the NGTWORK NAME() parameter or in the +WORKMODE() parameter is correct. Contact BMC Customer Support or your local representative

NGTB240

NGTWORK NAME(string-1) SET number-1 RELEASED (PREVIOUSLY MARKED UNUSABLE).


Explanation: The NGTWORK RELEASE command has released the specified workfile set.

User response: No action is required.

NGTB241

NGTWORK NAME(string-1) IS USE BY THIS UTILITY. DELETE NOT POSSIBLE.


Explanation: NGTWORK DELETE is running in this utility, but the utility is using the work files which are to be deleted.

User response: Verify the name specified in the NGTWORK NAME() parameter is correct. Specify +WORKMODE(TEMP). Contact BMC Customer Support or your local representative

NGTB242

ALL OBJECTS EXCLUDED/SKIPPED FOR STATEMENT number-1 .


Explanation: All the objects were excluded by EXCLUDE parameters or RTS processing.

User response: Verify the SYSIN statement to make sure objects are not being excluded incorrectly. Verify RTS parameters to make sure objects are not being excluded incorrectly.

NGTB244

TS string-1.string-2 IS SMALLER THAN MINTSSIZE REQUIREMENT; PROCESSING SKIPPED FOR TABLESPACE.


Explanation: The tablespace is smaller than the parameter +MINTSSIZE specification.

User response: The object will be skipped with no error. To process this object, reduce the value of the parameter +MINTSSIZE.

NGTB245

BMC/CHECKIX SYNTAX MUST NOT SPECIFY PARTS, TABLE NAME OR SPECIFIX INDEXES.


Explanation: CHECK INDEX (ALL) or CHECK INDEXSPACE (ALL) with no part specification

User response: The object will be skipped. Correct the syntax and resubmit.

NGTB246

DROPPED COLUMN EXISTS IN AN INDEX. USE 'ALTER ... RESTRICT' OR DROP THE INDEX.


Explanation: REORG cannot process an ALTER to DROP a column that exists in an index.

User response: The object will be skipped. Correct the syntax and resubmit.

NGTB247

AUX(YES) CHANGED TO AUX(NO) DUE TO DROPPED LOB COLUMN


Explanation: REORG will not reorganize LOBs on the TS because a LOB column has been dropped

User response: No action is required.

NGTB248

NGTRTS TABLES AND INDEXES NOT DROPPED (DROP_TABLES NOT SPECIFIED).


Explanation: The DROP_TABLES parameter was not specified so the BMC RTS tables and indexes will not be dropped.

User response: No action is required.

NGTB249

NGTRTS TABLES AND INDEXES DROPPED (DROP_TABLES SPECIFIED).


Explanation: The DROP_TABLES parameter was specified so the BMC RTS tables and indexes were dropped.

User response: No action is required.

NGTB250

NGTRTS REQUIRES A CONNECTION TO DB2.


Explanation: This message indicates that we are not connected to DB2.

User response: Re-run the job without the NOCONNECT parameter.

NGTB251

NGTRTS PRODUCT RECORD NOT FOUND. UNABLE TO DROP RTS OBJECTS.


Explanation: An unexpected condition occurred during processing.

User response: Contact BMC Customer Support or your local representative with this message number and text.

NGTB252

NGTRTS IS ALREADY DEFINED.


Explanation: The RTS facility is already defined.

User response: No action is required.

NGTB253

CREATE FAILED FOR A REQUIRED NGTRTS OBJECT.


Explanation: An unexpected condition occurred during processing.

User response: Contact BMC Customer Support or your local representative with this message number and text.

NGTB254

NGTRTS PROCESS STARTED.


Explanation: The RTS facility has begun processing.

User response: No action is required.

NGTB255

NGTRTS PROCESS COMPLETED.


Explanation: The RTS facility has completed processing.

User response: No action is required.

NGTB256

OBJECT TO BE QUEUED TO THE ERROR QUEUE - reasonText


Explanation: This message explains why an object was placed on the error queue. The executing utility will issue associated messages if it sets a high return code or sets the object in error status.

User response: See the recommended user response in the reasonText. Also see associated messages for specific details regarding the error condition encountered in the utility execution. If a server ends with active work in its queue, review the server output to determine the condition encountered during its processing and why the server ended prematurely.

NGTB257

TAPE SERVERS ARE CURRENTLY NOT SUPPORTED.


Explanation: This message is issued when a non-zero value is specified in the +SVRTAPE parameter.

User response: Change the parameter to reflect +SVRTAPE(0)

NGTB260

'REDEFINE' SPECIFIED BUT BMC RTS DEFINITIONS ALREADY EXIST.


Explanation: NGTRTS DEFINE has been specified with the REDEFINE keyword, however, the BMC RTS definitions already exist in the Checkpoint data set.

User response: Verify correct DB2 subsystem and checkpoint data set. Contact BMC Customer Support or your local representative

NGTB261

'REDEFINE' SPECIFIED BUT BMC RTS CRITERIA TABLE DOES NOT EXIST.


Explanation: NGTRTS DEFINE has been specified with the REDEFINE keyword, however, the BMC RTS Criteria table does not exist.

User response: Verify correct DB2 subsystem and checkpoint data set. Contact BMC Customer Support or your local representative

NGTB262

'REDEFINE' SPECIFIED BUT BMC RTS CRITERIA INDEX DOES NOT EXIST.


Explanation: NGTRTS DEFINE has been specified with the REDEFINE keyword, however, the BMC RTS Criteria Index does not exist.

User response: Verify correct DB2 subsystem and checkpoint data set. Contact BMC Customer Support or your local representative

NGTB263

'REDEFINE' SPECIFIED BUT BMC RTS EXCEPTIONS TABLE DOES NOT EXIST.


Explanation: NGTRTS DEFINE has been specified with the REDEFINE keyword, however, the BMC RTS Exceptions Table does not exist.

User response: Verify correct DB2 subsystem and checkpoint data set. Contact BMC Customer Support or your local representative

NGTB264

'REDEFINE' SPECIFIED BUT BMC RTS EXCEPTIONS INDEX DOES NOT EXIST.


Explanation: NGTRTS DEFINE has been specified with the REDEFINE keyword, however, the BMC RTS Exceptions Index does not exist.

User response: Verify correct DB2 subsystem and checkpoint data set. Contact BMC Customer Support or your local representative

NGTB265

UNABLE TO LOCATE A TAPE UNIT FOR OBJECT hexString-1.


Explanation: A problem occurred during the processing of variables used by XSVRJCL automation control point for the specified object.

User response: If you used variables in the OUTPUT command, review them to ensure that they are accurate. If you used multiple OUTPUT commands in the same SYSIN statement to reference tape units, ensure that each OUTPUT command contains a unique ID. This will enable the XSVRJCL automation control point to correctly identify the variables for each separate command.

NGTB266

NO TAPE UNITS ALLOCATED


Explanation: This message indicates that a tape server is in use but the tape manager has determined that no tape units are allocated and available for processing.

User response: Ensure that a tape unit is available for use. Resubmit the job.

NGTB268

SERVER FILES DELETED - +DELETEOUTPUT(Y) SPECIFIED.


Explanation: You specified YES or accepted the default (YES) for the SmartSwitch DELETEFILES option.

User response: No action is required.

NGTB272

NGTWORK PROCESS STARTED.


Explanation: The NGTWORK command has started.

User response: No action is required.

NGTB273

NGTWORK PROCESS COMPLETED.


Explanation: The NGTWORK command has completed.

User response: No action is required.

NGTB274

NGTWORK NAME(string-1) DEFINE STARTED.


Explanation: The NGTWORK DEFINE command has started.

User response: No action is required.

NGTB275

NGTWORK NAME(string-1) DEFINE INFORMATION SAVED IN PRODUCT TABLE.


Explanation: The DEFINE information for the specified workfile set has been saved in the CKPT data set.

User response: No action is required.

NGTB276

NGTWORK NAME(string-1) SET number-1 RECORD SAVED IN PRODUCT TABLE.


Explanation: The Set information for the specified workfile set has been saved in the CKPT data set.

User response: No action is required.

NGTB277

NGTWORK NAME(string-1) DEFINE COMPLETED SUCCESSFULLY.


Explanation: The NGTWORK DEFINE command has completed successfully.

User response: No action is required.

NGTB278

NGTWORK NAME(string-1) IS ALREADY DEFINED.


Explanation: The NGTWORK DEFINE command found the workfile set already defined in the CKPT data set.

User response: Verify the name specified in the NGTWORK NAME() parameter is correct. Contact BMC Customer Support or your local representative

NGTB279

INVALID string-1 string-2 VALUE SPECIFIED (MUST END IN K, M, OR G).


Explanation: The PRIMARY or SECONDARY value specified in the NGTWORK DEFINE command is invalid. The value must end in 'K', 'M', or 'G'.

User response: Verify the value specified is correct. Contact BMC Customer Support or your local representative

NGTB280

NGTWORK NAME(string-1) SET number-1 string-2 FILE ALLOCATED.


Explanation: The specified workfile set file was allocated successfully.

User response: No action is required.

NGTB281

NGTWORK NAME(string-1) SET number-1 string-2 FILE ALLOCATION FAILED.


Explanation: The allocation of the specified workfile set file failed.

User response: Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB282

NGTWORK QUERY OF PRODUCT TABLE FAILED.


Explanation: A Query of the NGTWORK information in the CKPT data set failed.

User response: Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB283

NGTWORK SAVE OF DEFINE INFORMATION FAILED.


Explanation: An error occurred while attempting to update the CKPT file with NGTWORK DEFINE information.

User response: Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB284

NGTWORK SAVE OF DATA SET INFORMATION FAILED.


Explanation: An error occurred while attempting to update the CKPT file with NGTWORK SET information.

User response: Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB285

NGTWORK ALLOCATION OF string-1 DATA SET FAILED.


Explanation: Allocation of the specified workfile set file failed.

User response: Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB286

NGTWORK NAME(string-1) DEFINE INFORMATION DELETED FROM PRODUCT TABLE.


Explanation: The NGTWORK DEFINE information has been successfully deleted from the CKPT data set.

User response: No action is required.

NGTB287

NGTWORK NAME(string-1) SET number-1 RECORD DELETED FROM PRODUCT TABLE.


Explanation: The NGTWORK SET information has been successfully deleted from the CKPT data set.

User response: No action is required.

NGTB288

DATA SET DELETED - string-1


Explanation: The specified data set has been deleted.

User response: No action is required.

NGTB289

NGTWORK NAME(string-1) DELETE STARTED.


Explanation: The NGTWORK DELETE command has started.

User response: No action is required.

NGTB290

NGTWORK NAME(string-1) DELETE COMPLETED SUCCESSFULLY.


Explanation: The NGTWORK DELETE command has completed successfully.

User response: No action is required.

NGTB291

NGTWORK NAME(string-1) SET number-1 RECORD DELETED FROM PRODUCT TABLE.


Explanation: The NGTWORK SET information has been successfully deleted from the CKPT data set.

User response: No action is required.

NGTB292

NGTWORK NAME(string-1) DEFINE INFORMATION DELETED FROM PRODUCT TABLE.


Explanation: The NGTWORK DEFINE information has been successfully deleted from the CKPT data set.

User response: No action is required.

NGTB293

NGTWORK NAME(string-1) WAS NOT FOUND.


Explanation: The DEFINE record was not found for the specified NGTWORK set.

User response: Verify the name specified in the NGTWORK NAME() parameter is correct. Contact BMC Customer Support or your local representative

NGTB294

NGTWORK DELETE OF DEFINE INFORMATION FAILED.


Explanation: An error occurred while attempting to delete the DEFINE information from the CKPT file.

User response: Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB295

NGTWORK DELETE OF DATA SET INFORMATION FAILED.


Explanation: An error occurred while attempting to delete the SET information from the CKPT file.

User response: Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB296

NGTWORK NAME(string-1) SET number-1 string-2 FILE DELETED.


Explanation: The specified workfile data set has been deleted.

User response: No action is required.

NGTB297

NGTWORK NAME(string-1) SET number-1 string-2 FILE DELETE FAILED.


Explanation: The delete of the specified workfile data set has failed.

User response: Check SYSERROR for error messages. Contact BMC Customer Support or your local representative

NGTB298

NGTWORK NAME(string-1) SET number-1 IS RESERVED BY string-2 (string-3).


Explanation: A NGTWORK DELETE was specified but one of the work file sets is being used by another utility. In this message:

  • string1—an 8-character permanent WORK file name specified on the NGTWORK statement
  • number1 the data set sequence number
  • string2 the JOBNAME
  • string3 the JOBID

User response: Perform QUICKEXIT or complete the utility using the work file set. Contact BMC Customer Support or your local representative

NGTB299

FLUSHING JOURNAL BUFFERS


Explanation: Journal buffers are being flushed.

User response: No action is required.

NGTB300

INVALID parameter VALUE SPECIFIED (VALUE IS MISSING)


Explanation: A value was missing for the indicated NGTWORK parameter.

User response: Provide the missing value and rerun the NGTWORK job.

NGTB330

UNABLE TO PROCESS WORK IN ISVR DUE TO +SVRMODE(M) MEMORY LIMIT.


Explanation: The internal server found work to be processed but was unable to accept the work due to internal server memory limitations.

User response: No action is required.

NGTB331

CDBAMS PROCESS STARTED.


Explanation: NGTAMS processing has started.

User response: No action is required.

NGTB332

CDBAMS PROCESS COMPLETED.


Explanation: NGTAMS processing completed.

User response: No action is required.

NGTB333

CDBAMS DEFINE (JCLRXMDL) CONTROL RECORD SAVED.


Explanation: NGTAMS DEFINE successfully created the product control record in the BMC product table.

User response: No action is required.

NGTB334

CDBAMS DEFINE (JCLRXMDL) DATA RECORDS (numberOfRecords) SAVED.


Explanation: NGTAMS DEFINE successfully saved the JCLRXMDL data records in the BMC product table.

User response: No action is required.

NGTB335

CDBAMS (JCLRXMDL) IS ALREADY DEFINED.


Explanation: The NGTAMS information is already defined.

User response: Either delete the current NGTAMS information (by using NGTAMS DELETE) or add the REPLACE parameter on the NGTAMS DEFINE statement.

NGTB336

CDBAMS DEFINE DD (DDname) WAS NOT FOUND.


Explanation: NGTAMS did not find the indicated DD in the job.

User response: Ensure that the NGTAMS DEFINE DDNAME parameter references the correct DD. If DDNAME is not specified, ensure that the JCLRXMDL DD is specified in the NGTAMS DEFINE job.

NGTB337

CDBAMS DEFINE OPEN FAILED FOR DD (DDname).


Explanation: An error occurred while attempting to open the indicated NGTAMS DEFINE DD.

User response: Contact BMC Customer Support for assistance.

NGTB338

CDBAMS DEFINE DD (DDname) CONTAINS NO RECORDS.


Explanation: The NGTBAMS DEFINE DDNAME parameter points to an empty data set.

User response: Ensure that NGTBAMS DEFINE DDNAME references the correct DD.

NGTB339

CDBAMS DEFINE (JCLRXMDL) INFORMATION DELETED FROM PRODUCT TABLE.


Explanation: NGTAMS DELETE successfully deleted the product record from the BMC product table.

User response: No action is required.

NGTB340

CDBAMS DELETE (JCLRXMDL) COMPLETED SUCCESSFULLY.


Explanation: NGTAMS DELETE completed successfully.

User response: No action is required.

NGTB341

CDBAMS DELETE (JCLRXMDL) RECORD WAS NOT FOUND.


Explanation: The NGTAMS product record was not found in the BMC product table. Nothing exists for NGTAMS DELETE to delete.

User response: No action is required.

NGTB342

QUERY OF PRODUCT TABLE FAILED.


Explanation: An error occurred during a query of the BMC product table.

User response: Contact BMC Customer Support.

NGTB343

CDBAMS DELETE OF DEFINE (JCLRXMDL) INFORMATION FAILED.


Explanation: An error occurred when NGTAMS attempted to delete the define information from the BMC product table.

User response: Contact BMC Customer Support.

NGTB344

CDBAMS PRODUCT RECORD(S) NOT FOUND.


Explanation: The NGTAMS product record was not found in the BMC product table. NGTAMS DISPLAY has no information to display.

User response: No action is required.

NGTB345

JCLRXMDL (productTableIdentifier) READ FROM PRODUCT TABLE.


Explanation: The IDCAMS define and delete model (JCLRXMDL) was successfully read from the BMC product table.

Note

If the product table is read from the global table, the identifier is 0GBL. If read from a DB2-specific table, the identifier is the DB2 subsystem ID.

User response: No action is required.

NGTB346

JCLRXMDL NOT FOUND IN PRODUCT TABLE. DEFAULT MODEL USED.


Explanation: The IDCAMS define and delete model (JCLRXMDL) was not found in the BMC product table. A default model will be used.

User response: No action is required.

NGTB347

UTILITY IDB CONVERTED TO VERSION versionNumber.


Explanation: The utility IDB in the checkpoint data set has been converted to the indicated version.

User response: No action is required.

NGTB348

'REDEFINE' SPECIFIED BUT BMC RTS SCHEDULE INDEX DOES NOT EXIST.


Explanation: NGTRTS DEFINE was specified with the REDEFINE keyword; however, the BMC RTS schedule index does not exist.

User response: Verify that you are using the correct DB2 subsystem and checkpoint data set. Contact BMC Customer Support for assistance.

NGTB350

TABLESPACE tableSpaceName IS A TABLE WITH ALTER ADD XML - PASSING TO DSNUTILB FOR PROCESSING


Explanation: The indicated table space contains a table to which a column was added via an ALTER statement. The utility does not currently support this type of object natively and passes processing to DSNUTILB.

User response: No action is required.

NGTB351

TABLESPACE tableSpaceName IS A CLONE - PASSING TO DSNUTILB FOR PROCESSING


Explanation: The indicated table space contains a clone table, which the utility does not currently support natively. The utility passes processing to DSNUTILB.

User response: No action is required.

NGTB352

TABLESPACE tableSpaceName IS AN INSTANCE - PASSING TO DSNUTILB FOR PROCESSING.


Explanation: The indicated table space is a base table space that is participating (or has participated) in a clone relationship. The utility does not currently support this type of object natively and passes processing to DSNUTILB.

User response: No action is required.

NGTB353

TABLESPACE tableSpaceName IS MULTI-TABLE SIMPLE - PASSING TO DSNUTILB FOR PROCESSING.


Explanation: The indicated table space is a simple, multi-table table space, which the utility does not support natively. The utility passes processing to DSNUTILB.

User response: No action is required.

NGTB354

TABLESPACE tableSpaceName USES DB2 Vvr NFM FEATURES - PASSING TO DSNUTILB FOR PROCESSING.


Explanation: The indicated table space uses a feature for the indicated DB2 version that the utility does not currently support natively. The utility passes processing to DSNUTILB.

User response: No action is required.

NGTB355

XCPYMDIA ERROR HAS OCCURRED.


Explanation: During DSNUTILB processing, the utility called the XCPYMDIA automation control point. The XCPYMDIA automation routine encountered an error and processing terminated.

User response: Determine the cause of the error and restart or resubmit the job. For assistance, contact BMC Customer Support.

NGTB356

XCPYDYNM ERROR HAS OCCURRED.


Explanation: During DSNUTILB processing, the utility called the XCPYDYNM automation control point. The XCPYDYNM automation routine encountered an error and processing terminated.

User response: Determine the cause of the error and restart or resubmit the job. For assistance, contact BMC Customer Support.

NGTB357

XULDDYNM ERROR HAS OCCURRED (dataSetType DATA SET).


Explanation: During DSNUTILB processing, the utility called the XULDDYNM automation control point to allocate the indicated type of data set. The XULDDYNM automation routine encountered an error and processing terminated.

User response: Determine the cause of the error and restart or resubmit the job. For assistance, contact BMC Customer Support.

NGTB358

OUTPUT COMMAND ERROR HAS OCCURRED (ddname DD).


Explanation: You specified the OUTPUT command for the indicated DD. During DSNUTILB processing, processing for the OUTPUT command encountered an error and the utility terminated.

User response: Determine the cause of the error and restart or resubmit the job. For assistance, contact BMC Customer Support.

NGTB359

ALLOCATION ERROR HAS OCCURRED (ddname DD).


Explanation: During DSNUTILB processing, the utility attempted to allocate a data set for the indicated DD. Data set allocation failed and the utility terminated.

User response: Determine the cause of the error and restart or resubmit the job. For assistance, contact BMC Customer Support.

NGTB360

DSNUTILB HAS ENDED WITH AN ERROR.


Explanation: DSNUTILB processing encountered an error. Processing failed and the utility terminated.

User response: Determine the cause of the error and restart or resubmit the job. For assistance, contact BMC Customer Support.

NGTB361

*****START OF DSNUTILB MESSAGES*****


Explanation: The utility passed processing to DSNUTILB for the reason provided in a previous message. The messages that follow this message are those issued by the DSNUTILB utility during processing. If you need more information about these messages, see the IBM DB2 Messages documentation.

User response: No action is required.

NGTB362

*****END OF DSNUTILB MESSAGES*****


Explanation: This message indicates that DSNUTILB processing has completed and returned to the BMC NGT utility.

User response: No action is required.

NGTB363

COMPRESSED LOBS ARE NOT SUPPORTED (tableSpaceName) - PASSING TO DSNUTILB FOR PROCESSING.


Explanation: The indicated table space contains compressed LOB data, which the utility does not currently support natively. The utility passes processing to DSNUTILB.

User response: No action is required.

NGTB368

TS HAS LOB OR XML COLUMNS AND IS DOING DISCARDS (tableSpaceName) - PASSING TO DSNUTILB


Explanation: The indicated table space contains LOB or XML columns and you specified an option to request that the utility discard rows. The utility does not currently support this functionality natively for this type of object and passes processing to DSNUTILB.

User response: No action is required.

NGTB369

TS HAS XML COLUMNS AND ALTERED LIMITKEYS (tableSpaceName) - PASSING TO DSNUTILB


Explanation: The indicated table space contains XML columns and limit key changes are pending. The utility does not currently support this functionality natively for this type of object and passes processing to DSNUTILB.

User response: No action is required.

NGTB370

TS HAS LOB OR XML COLUMNS AND IS DOING REBALANCE (tableSpaceName) - PASSING TO DSNUTILB


Explanation: The indicated table space contains LOB or XML columns and you specified an option to request that the utility rebalance partitions. The utility does not currently support this functionality natively for this type of object and passes processing to DSNUTILB.

User response: No action is required.

NGTB371

DDLIN DD NAME (ddName) NOT FOUND, DDLIN DATA WILL NOT BE USED.


Explanation: You specified DDLIN to rebalance partitions, but NGT Reorg did not find the indicated DD. The reorganization continues but NGT Reorg does not rebalance your partitions.

User response: No action is required. However, if you intended to rebalance partitions, ensure that you specify an existing DDLIN data set and then rerun the job.

NGTB372

ERROR IN ALTER STATEMENT, errorText.


Explanation: You specified DDLIN to rebalance partitions, but one of the ALTER statements is in error as shown in the indicated errorText. NGT Reorg terminates.

User response: Correct the ALTER statement and rerun the job.

NGTB373

OPEN FAILED FOR DDLIN DD (ddName).


Explanation: You specified DDLIN to rebalance partitions, but NGT Reorg could not open the specified DDLIN data set. The reorganization continues but NGT Reorg does not rebalance your partitions.

User response: No action is required. However, if you intended to rebalance partitions, ensure that you specify an existing DDLIN data set and then rerun the job.

NGTB377

PBGA WITH LOBS NOT SUPPORTED (tableSpaceName) - PASSING TO DSNUTILB FOR PROCESSING


Explanation: The indicated table space is a partition-by-growth table space that contains LOB columns. However, you did not specify AUX to use NGT LOBMaster to reorganize both the LOB table space and base table space at the same time. The utility does not currently support this type of object natively (unless you are using NGT LOBMaster) and passes processing to DSNUTILB.

User response: No action is required.

NGTB378

DSNUTILB PROCESSING NOT ALLOWED (+DSNUTILB(NO)). SKIPPING OBJECT.


Explanation: You are attempting to perform a function on an object for which the utility invokes DSNUTILB. However, the UTLPARMS parameter +DSNUTILB has a value of NO, which tells the utility not to invoke DSNUTILB. The utility does not process this object.

User response: Change the +DSNUTILB parameter and rerun the job step.

NGTB379

OBJECT IS IN A RESTRICTED STATE objectName PART partitionNumber - PASSING TO DSNUTILB FOR PROCESSING.


Explanation: The indicated object is in a restricted state that the utility does not support. The utility invokes DSNUTILB.

User response: No action is required.

NGTB380

PASSING TO DSNUTILB FOR PROCESSING


Explanation: The utility encountered an object or DB2 feature that it does not support. The utility invokes DSNUTILB.

User response: Review additional messages for more information. No action is required.

NGTB381

INDEX (databaseName.indexSpaceName) NOT SUPPORTED AT THIS TIME


Explanation: The utility does not currently support this type of object.

User response: No action is required.

NGTB383

INDEX indexName IS XML NODEID OR XPATH INDEX - PROCESSING SKIPPED FOR THIS INDEX


Explanation: You are attempting to reorganize an XML node ID index or a user-defined (XPATH) XML index. This release of NGT Reorg does not process these indexes.

User response: Repeat the reorganization without this index

NGTB384

TABLESPACE tableSpaceName HAS PENDING ALTERS, DDLIN WILL NOT BE PROCESSED


Explanation: You have provided a DDLIN data set that contains ALTER statements that will change the limit keys for the table space that you are reorganizing. However, pending ALTER statements exist on the table space that will change the limit keys and the pending ALTER statements take precedence. NGT Reorg does not process the ALTER statements in the DDLIN data set.

User response: No action is required.

NGTB388

CHECK INDEX NOT ALLOWED ON LOBS: databaseName.tableSpaceName. OBJECT SKIPPED


Explanation: NGT Check attempted to run a CHECK INDEX job on an LOB table space. NGT Check does not support CHECK INDEX jobs on an LOB table space. NGT Check places the object on the error queue.

User response: No action required.

NGTB389

type TABLESPACE IS DEFERRED: dbname.tableSpacename – PROCESSING ABORTED


Explanation: NGT Reorg detected an unavailable VSAM data set due to a table space created with DEFINE NO. The table space type is either AUX or BASE. The table space is identified by dbname.tsname to show the database and table space name.

User response: Review the indicated table space and any partitions within the table space to determine if all appropriate data sets are available.

NGTB390

LOB TABLESPACE MISSING FROM DB2 CATALOG.


Explanation: A search of the DB2 catalog shows that the large object (LOB) table space is missing.

User response: Ascertain why the LOB table space is missing.

NGTB394

HUFFMAN COMPRESSION ACTIVATED. NOT SUPPORTED AT THIS TIME.


Explanation: An object was created on a subsystem using Huffman compression, or the current subsystem uses Huffman compression. Objects and subsystems using Huffman compression are not supported in the current version.

User response: Switch to an object or subsystem that does not use Huffman compression.

Note

This message is not applicable if PTF BQU2907 is applied.

NGTB909

CHECK INDEX REPORT OF NPI LOGICAL PARTITIONS


Explanation: This is a report of rows per logical partition in an NPI.

User response: No action is required.

NGTB910

CHECK INDEX HASH WRITE TRACE


Explanation: This is a report of rows per logical partition in an NPI.

User response: No action is required.

NGTB911

COUNTS MISMATCH - NPI string-1 LPART number-1 - TS HAS #8 ROWS, IX HAS #8


Explanation: The count of rows in this logical partition from the NPI does not match the count of rows read from the tablespace.

User response: The index may need to be rebuilt.

NGTB912

LOCATE FAILED FOR hexstring-1, UPDATE WILL NOT BE DONE.


Explanation: A status queue update failed. This is normally the update of the I/J status. If so, the run will fail before Rename.

User response: The index may need to be rebuilt.

NGTB922

BIX8ROWZ INIT COMPLETE


Explanation: This is a report of tasks and indexes per task.

User response: If the I/J set, call BMC Customer Support for assistance.

NGTB923

BIX8ROWZ INIT COMPLETE


Explanation: This is a report of tasks and indexes per task.

User response: No action is required.

NGTB924

TABLESPACE string-1.string-2 - PARTS INVALID WITH DSNUM ALL FOR PBG - PROCESS SKIPPED FOR OBJECT.


Explanation: The object is skipped because it is a PBG object and the sysin statement referenced specific parts with the DSNUM ALL keyword.

User response: Object is skipped and put on error queue.

NGTB990

diagnostic text.


Explanation: These messages are to be used by BMC Customer Support. They are diagnostic/trace messages.

User response: No action is required.

NGTB991

diagnostic text.


Explanation: These messages are to be used by BMC Customer Support. They are diagnostic/trace messages.

User response: No action is required.

NGTB992

diagnostic text.


Explanation: These messages are to be used by BMC Customer Support. They are diagnostic/trace messages.

User response: No action is required.

NGTB993

diagnostic text.


Explanation: These messages are to be used by BMC Customer Support. They are diagnostic/trace messages.

User response: No action is required.

NGTB994

diagnostic text.


Explanation: These messages are to be used by BMC Customer Support. They are diagnostic/trace messages.

User response: No action is required.

NGTB995

diagnostic text.


Explanation: These messages are to be used by BMC Customer Support. They are diagnostic/trace messages.

User response: No action is required.

NGTB996

diagnostic text.


Explanation: These messages are to be used by BMC Customer Support. They are diagnostic/trace messages.

User response: No action is required.

NGTB997

diagnostic text.


Explanation: These messages are to be used by BMC Customer Support. They are diagnostic/trace messages.

User response: No action is required.

NGTB998

diagnostic text.


Explanation: These messages are to be used by BMC Customer Support. They are diagnostic/trace messages.

User response: No action is required.

NGTB999

diagnostic text.


Explanation: These messages are to be used by BMC Customer Support. They are diagnostic/trace messages.

User response: No action is required.

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

Comments