Messages NGTT000 through NGTT999
This topic contains messages for the BMC AMI Utilities.
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
| Number | Description |
|---|---|
| NGTT000 | #ERREL ERRORS Explanation: An internal logic error or an unrecoverable error has occurred. A message should be on the //SYSERROR DD to describe this condition. User response: Contact BMC Support with this message number and text. |
| NGTT001 | BEGINNING RUNSTATS CATALOG UPDATE Explanation: This message signals that the catalog update is beginning - detail messages are on the //RUNSTATS DD. User response: No action is required. |
| NGTT002 | +RUNSTATS(NO) PARM OVERRIDES STATS OPTIONS - ONLY RTS TABLES UPDATED Explanation: +RUNSTATS(NO) was set for the specific utility. Catalog statistics are not updated. Only RTS tables are updated. User response: No action is required. |
| NGTT003 | THERE ARE NO INDEXES ON THIS TABLESPACE - NO STATS GATHERED/UPDATED FOR string-1.string-2 Explanation: No statistics are gathered at this time. User response: No action is required. |
| NGTT004 | CHECK RUNSTATS DD FOR ERROR MESSAGES - STATS ABORTED Explanation: One or more SQL errors occurred during Catalog update. There should be an error message on the RUNSTATS file. User response: Contact BMC Support. |
| NGTT005 | CHECK SYSERROR DD FOR ERROR MESSAGES - STATS ABORTED Explanation: A logic error occurred during Catalog update. There should be an error message on the SYSERROR file. User response: Contact BMC Support. |
| NGTT006 | ABEND WHEN PROCESSING CATALOG UPDATES - STATS ABORTED Explanation: There was an abend during Catalog update. There should be an error message on the CDBPRINT file. User response: Contact BMC Support. |
| NGTT007 | RUNSTATS DATA GATHERING COMPLETE Explanation: This message signals that all the indexes have been read and the Catalog update is about to begin. User response: No action is required. |
| NGTT008 | RUNSTATS STARTING READ FOR string-1 string-2.string-3 (number-1) Explanation: This message marks the start of RUNSTATS read processing for the named Index. User response: No action is required. |
| NGTT009 | RUNSTATS COMPLETED READ PROCESSING FOR string-1 string-2.string-3 (number-1) Explanation: This message marks the completion of RUNSTATS read processing for the named Index. User response: No action is required. |
| NGTT010 | CDBSTATS OPTIONS CHANGED FOR INDEX(SPACE) indexSpaceName (number-1) Explanation: The user REXX exit XSTAT001 has changed some of the statistics gathering variables. The new values are reported in the next message. User response: No action is required. |
| NGTT011 | INDEXSPACE indexSpaceName EXCLUDED - DEFERRED OR MISSING Explanation: RUNSTATS for this Index will be skipped - there is no underlying VSAM data set to read. User response: No action is required. |
| NGTT012 | INDEXSPACE string-1 PT number-1 EXCLUDED - DEFERRED OR MISSING Explanation: RUNSTATS for this Index will be skipped - there is no underlying VSAM data set to read. User response: No action is required. |
| NGTT013 | UTS CONVERSION DETECTED FOR TABLESPACE tableSpaceName. +RUNSTATS(NO) FORCED. ONLY RTS TABLES UPDATED Explanation: BMC AMI Reorg detected that a pending ALTER statement exists to convert the table space to a universal table space (UTS). BMC AMI Reorg performs a space only reorganization to materialize the ALTER statement. RUNSTATS is turned off, but real-time statistics records are added for any new partitions. User response: To obtain RUNSTATS, run an additional REORG or RUNSTATS utility on the table space. |
| NGTT014 | RUNSTATS FOR LOB TABLESPACE tableSpaceName NOT SUPPORTED - PROCESSING SKIPPED Explanation: RUNSTATS does not support LOB table spaces at this time. This table space will be skipped. User response: No action is required. |
| NGTT015 | INDEX(NAME) ON NGTSTATS TABLESPACE tableSpaceName IS NOT SUPPORTED. ONLY 'ALL' IS SUPPORTED Explanation: BMC AMI Stats INDEX(ALL) is the only specification supported at this time. User response: Change the SYSIN statement and resubmit the job. |
| NGTT016 | NGTSTATS TABLESPACE tableSpaceName PARTS XXX IS NOT SUPPORTED YET Explanation: No parts specification is supported for this version of BMC AMI Stats. The parts specifications are ignored. User response: Change the SYSIN statement and resubmit the job. |
| NGTT017 | NGTSTATS TABLESPACE tableSpaceName READTS HAS RESTRICTED PARTS Explanation: Cannot do a READTS process when parts are restricted. User response: Clear the restricted status and resubmit the job. |
| NGTT018 | SYSIBM.SYSTABLEPART UPDATED FOR string-1.string-2 (number-1) Explanation: The table SYSTABLEPART has been updated with entries for the referenced object and part number. User response: No action is required. |
| NGTT019 | SYSIBM.SYSTABLEPART_HIST UPDATED FOR string-1.string-2 (number-1) Explanation: The table SYSTABLEPART_HIST has been updated with entries for the referenced object and part number. User response: No action is required. |
| NGTT020 | string-1.string-2 (number-1) NOT FOUND IN SYSIBM.SYSTABLESPACESTATS, INSERTING ROW Explanation: The row for the object and part was not found in the SYSTABLESPACESTATS table, so, it could not be updated. it was inserted instead. User response: No action is required. |
| NGTT021 | UPDATE OR INSERT OF SYSIBM.SYSTABLESPACESTATS FAILED FOR string-1.string-2 (number-1) Explanation: The row for the object and part was not found in the SYSTABLESPACESTATS table, so, it could not be updated. User response: No action is required. |
| NGTT022 | SYSIBM.SYSTABLESPACESTATS UPDATED FOR string-1.string-2 (number-1) Explanation: The row for the object and part has been updated in the SYSTABLESPACESTATS table. User response: No action is required. |
| NGTT023 | SYSIBM.SYSTABSTATS UPDATED FOR TABLE Explanation: The SYSTABSTATS table has been updated for the specified table. User response: No action is required. |
| NGTT024 | SYSIBM.SYSTABSTATS_HIST UPDATED FOR TABLE Explanation: The SYSTABSTATS_HIST table has been updated for the specified table. User response: No action is required. |
| NGTT025 | SYSIBM.SYSTABLESPACE UPDATED FOR string-1.string-2 Explanation: The SYSTABLESPACE table has been updated for the specified object. User response: No action is required. |
| NGTT026 | SYSIBM.SYSTABLES UPDATED FOR TABLE Explanation: The SYSTABLES table has been updated for the specified object. User response: No action is required. |
| NGTT027 | SYSIBM.SYSTABLES_HIST UPDATED FOR TABLE Explanation: The SYSTABLES_HIST table has been updated for the specified object. User response: No action is required. |
| NGTT028 | SYSIBM.SYSTABLES (NC) UPDATED FOR TABLE Explanation: The SYSTABLES table has been updated for the specified object. This update did not reference a card value. User response: No action is required. |
| NGTT029 | SYSIBM.SYSTABLES_HIST (NC) UPDATED FOR TABLE Explanation: The SYSTABLES_HIST table has been updated for the specified object. This update did not reference a card value. User response: No action is required. |
| NGTT030 | SYSIBM.SYSLOBSTATS UPDATED FOR Explanation: The SYSLOBSTATS table has been updated for the specified object. User response: No action is required. |
| NGTT031 | SYSIBM.SYSLOBSTATS_HIST UPDATED FOR Explanation: The SYSLOBSTATS_HIST table has been updated for the specified object. User response: No action is required. |
| NGTT032 | string-1.string-2 (number-1) NOT FOUND IN SYSIBM.SYSTABLESPACESTATS, INSERTING ROW Explanation: The entry for the referenced table space and part was not found in the SYSTABLESPACESTATS table. The row will now be inserted instead of updated. User response: No action is required. |
| NGTT033 | SYSINDEXPART UPDATED FOR Explanation: The entry for the referenced indexspace has been updated in the SYSINDEXPART table. User response: No action is required. |
| NGTT034 | SYSINDEXPART_HIST INSERTED FOR Explanation: The entry for the referenced indexspace has been updated in the SYSINDEXPART_HIST table. User response: No action is required. |
| NGTT035 | string-1.string-2 (number-1) NOT FOUND IN SYSIBM.SYSINDEXSPACESTATS, INSERTING ROW Explanation: The entry for the referenced indexspace was not found id in the SYSINDEXSPACESTATS table. So, this entry will be inserted instead of updated. User response: No action is required. |
| NGTT036 | UPDATE/INSERT OF SYSIBM.SYSINDEXSPACESTATS FAILED FOR Explanation: The update or insert of the SYSINDEXSPACESTATS table failed for the referenced indexspace. User response: No action is required. |
| NGTT037 | SYSIBM.SYSINDEXSPACESTATS UPDATED FOR Explanation: The update of the SYSINDEXSPACESTATS table for the referenced indexspace was successful. User response: No action is required. |
| NGTT038 | SYSIBM.SYSINDEXES UPDATED FOR Explanation: The update of the SYSINDEXES table for the referenced indexspace was successful. User response: No action is required. |
| NGTT039 | SYSIBM.SYSINDEXES_HIST INSERTED FOR Explanation: The insert into the SYSINDEXES_HIST table for the referenced indexspace was successful. User response: No action is required. |
| NGTT040 | SYSIBM.SYSINDEXSTATS UPDATED FOR Explanation: The update to the SYSINDEXSTATS table for the referenced indexspace was successful. User response: No action is required. |
| NGTT041 | SYSIBM.SYSINDEXSTATS_HIST UPDATED FOR Explanation: The update to the SYSINDEXSTATS_HIST table for the referenced indexspace was successful. User response: No action is required. |
| NGTT042 | string-1.string-2 (number-1) NOT FOUND IN SYSIBM.SYSTABLESPACESTATS, INSERTING ROW Explanation: The entry for the referenced table space and part was not found in the SYSTABLESPACESTATS table. The row will be inserted instead. User response: No action is required. |
| NGTT043 | SPACE string-1.string-2 number-1 IS RESTRICTED BY DB2 Explanation: The referenced space name is in a restricted or stopped state. It will not be processed and will be put on the EXCLUDE queue. User response: Take the appropriate action for the referenced object and resubmit the job. |
| NGTT044 | HISTORY OPTION RETRIEVED FROM ZPARMS: string-1 Explanation: No parameter value was specified for the history option. The referenced default stats history option was retrieved from the ZPARMS specification. User response: No action is required. |
| NGTT045 | ROLLUP OPTION RETRIEVED FROM ZPARMS: string-1 Explanation: No parameter value was specified for the rollup option. The referenced default stats rollup option was retrieved from the ZPARMS specification. User response: No action is required. |
| NGTT046 | TABLESPACE tableSpaceName CONTAINS NO string-3 - PROCESSING SKIPPED FOR TABLESPACE Explanation: The referenced tablespace will be skipped due to the fact that it contains no tables or indexes. User response: No action is required. |
| NGTT047 | MULTI-TABLE SIMPLE TABLESPACES NOT SUPPORTED BY UTILITY- PROCESSING SKIPPED FOR TABLESPACE Explanation: The referenced tablespace will be skipped due to the fact that it is a simple tablespace with more than one table. User response: No action is required. |
| NGTT048 | string-1 NOT PARTITIONED BUT PART NUMBERS SPECIFIED - PROCESSING SKIPPED FOR string-2 Explanation: The referenced tablespace will be skipped due to the fact that it is identified with part numbers when it is not a partitioned tablespace. User response: No action is required. |
| NGTT049 | string-1 NOT PARTITIONED BUT PART NUMBERS SPECIFIED - PROCESSING SKIPPED FOR string-2 Explanation: The referenced tablespace will be skipped due to the fact that it is identified with part numbers when it is not a partitioned tablespace. User response: No action is required. |
| NGTT050 | SYNTAX ERROR - MORE THAN ONE TABLESPACE SPECIFIED - PROCESSING SKIPPED FOR TABLESPACE Explanation: The referenced tablespace will be skipped due to the fact that more than one tablespace is referenced in the sysin statement. User response: Specify only one tablespace in the SYSIN statement and resubmit the job. |
| NGTT051 | SYNTAX ERROR - ONLY PARTITIONED TABLESPACES CAN BE EXCLUDED - PROCESSING SKIPPED FOR TABLESPACE Explanation: Excludes can not be specified on tables or non-partitioned table spaces. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT052 | MORE THAN ONE TABLE SPECIFIED FOR NON-SEGMENTED TABLESPACE - PROCESSING SKIPPED FOR TABLESPACE Explanation: Multiple tables can be specified only for multi-table segmented table spaces. This tablespace will be skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT053 | SYNTAX - ONLY TABLES OF SEGMENTED TABLESPACES CAN BE EXCLUDED - PROCESSING SKIPPED FOR TABLESPACE Explanation: An attempt was made to exclude a table from a non-segmented tablespace. This tablespace will be skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT054 | SYNTAX - MORE THAN ONE NON-PARTITIONED TABLESPACE SPECIFIED - PROCESSING SKIPPED FOR TABLESPACE Explanation: Only one non-partitioned tablespace can be specified in the input statement. This tablespace will be skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT055 | SYNTAX - CANNOT EXCLUDE ALL PARTS OF A PARTITONED TABLESPACE - PROCESSING SKIPPED FOR TABLESPACE Explanation: At least one part of the partitioned tablespace must be processed. This tablespace will be skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT056 | ROLLUP ABORTED. NO ENTRIES RETURNED FROM SYSTABSTATS QUERY FOR string-1.string-2 Explanation: No entries were found in SYSIBM.SYSTABSTATS for the tablespace being processed. User response: No action is required. |
| NGTT057 | SYNTAX ERROR - SPECIFIED PART NUMBER RANGE IS NOT ASCENDING - PROCESSING SKIPPED FOR TABLESPACE Explanation: The part specification must be requested in ascending order. This tablespace will be skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT058 | SYNTAX ERROR - ALL SPECIFIED BUT INPUT CONTAINS INCLUDE(S) - PROCESSING SKIPPED FOR TABLESPACE Explanation: The keyword all was specified in the SYSIN statement but some parts are excluded. This tablespace will be skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT059 | string-1 NOT PARTITIONED BUT PART NUMBERS SPECIFIED - PROCESSING SKIPPED FOR string-2 Explanation: The referenced index is non-partitioned and a part number was specified. This object will be skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT060 | EXEC XSTAT001 SET SKIPIX TO Y, ONLY RTS UPDATES FOR INDEX string-1.string-2 (number-1) Explanation: The REXX exit XSTAT001 was called during the processing of the referenced object. Catalog statistics are not updated because SKIPIX = Y was set. Only RTS tables are updated for the specified object. User response: No action is required. |
| NGTT061 | NO INDEXES ON TABLE. PROCESSING SKIPPED FOR string-1.string-2 Explanation: The table must have an index for it to be processed. This object will be skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT062 | NO PART NUMBER SPECIFIED FOR A PARTITIONED INDEX Explanation: The partitioned index must have a part number identified for it to be processed. This index will be skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT063 | TABLESPACE tableSpaceName IS XML - PROCESSING SKIPPED FOR TABLESPACE Explanation: XML table spaces are not supported at this time. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT064 | DB2 AUTHORIZATION REJECT Explanation: A DB2 authorization failure has been encountered for the object being processed. This object will be skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT065 | SYNTAX ERROR - ALL PARTS HAVE BEEN EXCLUDED - PROCESSING SKIPPED FOR TABLESPACE Explanation: All parts of the partitioned object have been excluded. This tablespace is skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT066 | SYNTAX ERROR - SPECIFIED TABLE IS NOT IN THE TABLESPACE - PROCESSING SKIPPED FOR TABLESPACE Explanation: The table referenced in the sysin statement does not exist in the tablespace. This object is skipped. User response: Adjust the sysin statement as needed and resubmit the job. |
| NGTT067 | RESET OF SYSIBM.SYSCOLUMNS SUCCESSFUL FOR TABLE tableName Explanation: The row for the object and part was reset in the SYSCOLUMNS table. User response: No action is required. |
| NGTT068 | RESET OF SYSIBM.SYSCOLUMNS FAILED FOR string-1.string-2 Explanation: The row for the object and part was not successfully reset in the SYSCOLUMNS table. User response: No action is required. |
| NGTT069 | +RUNSTATS(NO) PARM SPECIFIED. RESET SKIPPED FOR string-1.string-2 Explanation: The RESET work was not done for the identified object because the RUNSTAST(NO) parameter was specified in the job. User response: No action is required. |
| NGTT070 | SYSIBM.SYSTABLESPACE RESET FOR string-1.string-2 Explanation: The entries in the SYSTABLESPACE table were reset for the referenced object. User response: No action is required. |
| NGTT071 | RESET OF SYSIBM.SYSTABLESPACE FAILED FOR string-1.string-2 Explanation: The resetting of the entries in the SYSTABLESPACE failed for the referenced object. User response: No action is required. |
| NGTT072 | RESET OF SYSIBM.SYSKEYTARGETS SUCCESSFUL FOR string-1.string-2 Explanation: The resetting of the entries in the SYSKEYTARGETS table was successful for the referenced object. User response: No action is required. |
| NGTT073 | RESET OF SYSIBM.SYSKEYTARGETS FAILED FOR string-1.string-2 Explanation: The resetting of the entries in the SYSKEYTARGETS table failed for the referenced object. User response: No action is required. |
| NGTT074 | RESET OF SYSIBM.SYSTABLES SUCCESSFUL FOR TABLESPACE tableSpaceName Explanation: The resetting of the entries in the SYSTABLES table was successful for the referenced object. User response: No action is required. |
| NGTT075 | RESET OF SYSIBM.SYSTABLES FAILED FOR string-1.string-2 Explanation: The resetting of the entries in the SYSTABLES table failed for the referenced object. User response: No action is required. |
| NGTT076 | RESET OF SYSIBM.SYSINDEXES SUCCESSFUL FOR string-1.string-2 Explanation: The resetting of the entries in the SYSINDEXES table failed for the referenced object. User response: No action is required. |
| NGTT077 | RESET OF SYSIBM.SYSINDEXES FAILED FOR string-1.string-2 Explanation: The resetting of the entries in the SYSINDEXES table failed for the referenced object. User response: No action is required. |
| NGTT078 | DELETE OF SYSIBM.SYSTABSTATS ENTRY SUCCESSFUL FOR string-1.string-2 Explanation: The entry for the referenced object was deleted from the SYSIBM.SYSTABSTATS table. User response: No action is required. |
| NGTT079 | ENTRY NOT FOUND IN SYSIBM.SYSTABSTATS FOR string-1.string-2 Explanation: The entry for the referenced object does not exist in the SYSIBM.SYSTABSTATS table. User response: No action is required. |
| NGTT080 | SYSIBM.SYSCOLSTATS ENTRIES DELETED FOR string-1.string-2 Explanation: The entry for the referenced object was deleted from the SYSIBM.SYSCOLSTATS table. User response: No action is required. |
| NGTT081 | SYSIBM.SYSCOLSTATS ENTRY NOT FOUND FOR string-1.string-2 Explanation: The entry for the referenced object does not exist in the SYSIBM.SYSCOLSTATS table. User response: No action is required. |
| NGTT082 | SYSIBM.SYSINDEXSTATS ENTRIES DELETED FOR string-1.string-2 Explanation: The entry for the referenced object was deleted from the SYSIBM.SYSINDEXSTATS table. User response: No action is required. |
| NGTT083 | SYSIBM.SYSINDEXSTATS ENTRY NOT FOUND FOR string-1.string-2 Explanation: The entry for the referenced object does not exist in the SYSIBM.SYSINDEXSTATS table. User response: No action is required. |
| NGTT084 | SYSIBM.SYSCOLDIST ENTRIES DELETED FOR string-1.string-2 Explanation: The entry for the referenced object was deleted from the SYSIBM.SYSINCOLDIST table. User response: No action is required. |
| NGTT085 | SYSIBM.SYSCOLDIST ENTRY NOT FOUND FOR string-1.string-2 Explanation: The entry for the referenced object does not exist in the SYSIBM.SYSCOLDIST table. User response: No action is required. |
| NGTT086 | SYSIBM.SYSCOLDISTSTATS ENTRIES DELETED FOR string-1.string-2 Explanation: The entry for the referenced object was deleted from the SYSIBM.SYSINCOLDISTSTATS table. User response: No action is required. |
| NGTT087 | SYSIBM.SYSCOLDISTSTATS ENTRY NOT FOUND FOR string-1.string-2 Explanation: The entry for the referenced object does not exist in the SYSIBM.SYSCOLDISTSTATS table . User response: No action is required. |
| NGTT088 | SYSIBM.SYSKEYTARGETSTATS ENTRY DELETED FOR string-1.string-2 Explanation: The entry for the referenced object was deleted from the SYSIBM.SYSKEYTARGETSTATS table. User response: No action is required. |
| NGTT089 | SYSIBM.SYSKEYTARGETSTATS ENTRY NOT FOUND FOR string-1.string-2 Explanation: The entry for the referenced object does not exist in the SYSIBM.SYSKEYTARGETSTATS table . User response: No action is required. |
| NGTT090 | SYSIBM.SYSKEYTGTDIST ENTRY DELETED FOR string-1.string-2 Explanation: The entry for the referenced object was deleted from the SYSIBM.SYSKEYTGTDIST table. User response: No action is required. |
| NGTT091 | SYSIBM.SYSKEYTGTDIST ENTRY NOT FOUND FOR string-1.string-2 Explanation: The entry for the referenced object does not exist in the SYSIBM.SYSKEYTGTDIST table. User response: No action is required. |
| NGTT092 | SYSIBM.SYSKEYTGTDISTSTATS ENTRY DELETED FOR string-1.string-2 Explanation: The entry for the referenced object was deleted from the SYSIBM.SYSKEYTGTDISTSTATS table. User response: No action is required. |
| NGTT093 | SYSIBM.SYSKEYTGTDISTSTATS ENTRY NOT FOUND FOR string-1.string-2 Explanation: The entry for the referenced object does not exist in the SYSIBM.SYSKEYTGTDISTSTATS table. User response: No action is required. |
| NGTT094 | THE RUNSTATS RESET FEATURE IS ONLY SUPPORTED IN DB2 V11 OR HIGHER - PROCESSING SKIPPED Explanation: An attempt was made to run the runstats reset feature on a DB2 system that is not version 11 or higher. The processing of this object is skipped. User response: No action is required. |
| NGTT095 | INSERT OF SYSIBM.SYSINDEXES_HIST SUCCESSFUL FOR string-1.string-2 Explanation: The entry for the referenced object was inserted into the SYSIBM.SYSINDEXES_HIST table. User response: No action is required. |
| NGTT096 | INSERT OF SYSIBM.SYSINDEXES_HIST FAILED FOR string-1.string-2 Explanation: The entry for the referenced object could not be inserted into the SYSIBM.SYSINDEXES_HIST table . User response: No action is required. |
| NGTT097 | INSERT OF SYSIBM.SYSTABLES_HIST SUCCESSFUL FOR string-1.string-2 Explanation: The entry for the referenced object was inserted into the SYSIBM.SYSTABLES_HIST table. User response: No action is required. |
| NGTT098 | INSERT OF SYSIBM.SYSTABLES_HIST FAILED FOR string-1.string-2 Explanation: The entry for the referenced object could not be inserted into the SYSIBM.SYSTABLES_HIST table. User response: No action is required. |
| NGTT100 | BMCNGT_STABLEPART INSERTED FOR tableSpaceName(partitionNumber) Explanation: BMC AMI Stats has updated the RS_TABLEPART table with entries for the indicated object. User response: No action is required. |
| NGTT101 | BMCNGT_STABLESPACE INSERTED FOR tableSpaceName Explanation: BMC AMI Stats has updated the RS_TABLESPACE table for the indicated object. User response: No action is required. |
| NGTT102 | BMCNGT_STABLES INSERTED FOR TABLE Explanation: BMC AMI Stats has updated the RS_TABLES table for the indicated object. User response: No action is required. |
| NGTT103 | BMCNGT_STABLES (NC) INSERTED FOR TABLE Explanation: BMC AMI Stats has updated the RS_TABLES table for the indicated object. This update did not reference a card value. User response: No action is required. |
| NGTT104 | BMCNGT_SINDEXPART INSERTED FOR Explanation: BMC AMI Stats has updated the RS_INDEXPART table for the indicated object. User response: No action is required. |
| NGTT105 | BMCNGT_SINDEXES INSERTED FOR Explanation: BMC AMI Stats has updated the RS_INDEXES table for the indicated object. User response: No action is required. |
| NGTT106 | STATS NOT WRITTEN TO DB2 CATALOG DUE TO OMITCARD0 PROCESSING FOR TP tableSpaceName(partitionNumber) Explanation: Due to OMITCARD0 processing, BMC AMI Stats did not update SYSTABLEPART with entries for the indicated object. User response: No action is required. |
| NGTT107 | STATS NOT WRITTEN TO DB2 CATALOG DUE TO OMITCARD0 PROCESSING FOR TABLE Explanation: Due to OMITCARD0 processing, BMC AMI Stats did not update SYSTABLES with entries for the indicated object. User response: No action is required. |
| NGTT108 | STATS NOT WRITTEN TO DB2 CATALOG DUE TO OMITCARD0 PROCESSING FOR INDEX Explanation: Due to OMITCARD0 processing, BMC AMI Stats did not update SYSINDEXES with entries for the indicated object. User response: No action is required. |
| NGTT109 | STATS NOT WRITTEN TO DB2 CATALOG DUE TO OMITCARD0 PROCESSING FOR INDEXPART Explanation: Due to OMITCARD0 processing, BMC AMI Stats did not update SYSINDEXPART with entries for the indicated object. User response: No action is required. |
| NGTT110 | STATS NOT WRITTEN TO DB2 CATALOG DUE TO OMITCARD0 PROCESSING FOR TS tableSpaceName Explanation: Due to OMITCARD0 processing, BMC AMI Stats did not update SYSTABLESPACE with entries for the indicated object. User response: No action is required. |
| NGTT111 | TABLESPACE databaseName.tableSpaceName HAS EXCLUDE NULL INDEX. PROCESSING SKIPPED FOR TABLESPACE Explanation: BMC AMI Stats does not currently support EXCLUDE NULL index. NGTSTAT9 processing bypasses the referenced table space. The bypass is visible only in NGTSTAT9. User response: No action is required. |
| NGTT112 | THE FOLLOWING DATA SET IS MIGRATED OR NOT FOUND. PROCESSING SKIPPED FOR OBJECT Explanation: This message indicates that the DB2 VSAM data set is migrated. This message is issued when the job includes the UTLPARMS +HRECALL(NO) parameter. If this message is issued in the job output, the BMC AMI Stats job will fail with a high return code and the associated DB2 object will be queued to the ERROR queue. User response: If this message is issued in the job output, you can specify +HRECALL(YES) and the data set will be automatically recalled. |
| NGTT113 | SQL STMT CACHE CLEARED FOR TABLESPACE string-1.string-2 Explanation: The SQL statements in the dynamic statement cache that reference the indicated table space have been invalidated. User response: No action is required. |
| NGTT114 | CLEAR SQL STMT CACHE FAILED FOR TABLESPACE string-1.string-2 Explanation: An attempt to clear SQL statements in the dynamic statement cache that reference the listed table space has failed. Additional error messages might appear in the job output. User response: Search the SYSERROR DD output to determine the cause of the error. |
| NGTT115 | INVALIDATECACHE FORCED SINCE NO UPDATES OR REPORTS REQUESTED Explanation: The SQL statements in the dynamic statement cache that reference the current object have been forcefully invalidated because no statistics updates or reports were requested. User response: Search the SYSERROR DD output to determine the cause of the error. |
| NGTT116 | SPACE string-1.string-2 PART number-1 IN RESTRICTED STATUS (RBDP OR RECP) – EXCLUDED Explanation: The indicated index is in a restrictive state. Statistics processing for the index is skipped. User response: Resolve the restrictive state for the index and rerun the job. |
| NGTT117 | TBCOLFREQ(YES) SPECIFIED - READTS SET TO READTS(YES) - EXPECT INCREASED RESOURCE CONSUMPTION Explanation: You specified TBCOLFREQ(YES) but not READTS(YES). The parser set the READTS option to YES to honor the TBCOLFREQVAL(YES) option. Because BMC AMI Stats reads the table space, resource consumption increases. User response: No action is required. |
| NGTT118 | COLUMN LIST COLUMN NOT FOUND: columnName Explanation: You included the indicated column name in a COLUMN list, but BMC AMI Stats did not find the column in the processed table. BMC AMI Stats skipped the object. User response: Correct the column name in the COLUMN list and rerun the job. |
| NGTT119 | DUPLICATE COLUMN IN COLUMN LIST: columnName Explanation: You included the the indicated column name in the COLUMN list multiple times. BMC AMI Stats skipped the object. User response: Correct the column name in the COLUMN list and rerun the job. |
| NGTT120 | COLUMN LIST SPECIFIED - READTS SET TO READTS(YES) - EXPECT INCREASED RESOURCE CONSUMPTION Explanation: You specified a COLUMN list but not READTS(YES). The parser set the READTS option to YES to honor the COLUMN list option. Because BMC AMI Stats reads the table space, resource consumption increases. User response: No action is required. |
| NGTT121 | COLUMN LIST NOT ALLOWED FOR MULTI-TABLE SPACES Explanation: You specified a COLUMN list for a multi-table table space. BMC AMI Stats does not support this action and skips the object. User response: Correct the COLUMN list and rerun the job. |
| NGTT122 | COLGROUP NOT ALLOWED FOR MULTI-TABLE SPACES – PROCESSING SKIPPED FOR TABLESPACE Explanation: You specified a COLGROUP for a multi-table space. BMC AMI Stats does not support this action and skips the object. User response: Correct the COLGROUP and rerun the job. |
| NGTT123 | COLGROUP COLUMN NOT FOUND: columnName Explanation: You included the indicated column name in a COLGROUP>, but BMC AMI Stats did not find the column in the processed table. BMC AMI Stats skipped the object. User response: Correct the column name in the COLGROUP and rerun the job. |
| NGTT124 | OBJECT SKIPPED DUE TO COLUMN LIST ERROR Explanation: BMC AMI Stats skipped the object because of a previously displayed COLUMN list error. User response: Correct the COLUMN list and rerun the job. |
| NGTT125 | COLUMN GROUP SPECIFIED - READTS SET TO READTS(YES) – EXPECT INCREASED RESOURCE CONSUMPTION Explanation: You specified a COLGROUP but not READTS(YES). The parser set the READTS option to YES to honor the COLGROUP option. Because BMC AMI Stats reads the table space, resource consumption increases. User response: No action is required. |
| NGTT126 | COLUMN GROUP CANNOT CONTAIN MORE THAN 127 COLUMNS - PROCESSING SKIPPED FOR TABLESPACE Explanation: You specified a COLGROUP that contains more than 127 columns, which exceeds the maximum that COLGROUP processing supports. BMC AMI Stats skipped the object. User response: Correct the COLGROUP and rerun the job. |
| NGTT127 | NO MORE THAN 255 COLUMN GROUPS ALLOWED - PROCESSING SKIPPED FOR TABLESPACE Explanation: You specified more than 255 COLGROUP statements. The maximum number of column groups allowed is 255. BMC AMI Stats skipped the object. User response: Reduce the number of COLGROUP options and rerun the job. |
| NGTT128 | DUPLICATE COLUMN GROUPS NOT ALLOWED – PROCESSING SKIPPED FOR TABLESPACE Explanation: Multiple column groups contain the same column list, which is not allowed. BMC AMI Stats skipped the object. User response: Eliminate the duplicate COLGROUP options and rerun the job. |
| NGTT129 | DUPLICATE COLUMN IN COLGROUP LIST: columnName Explanation: The indicated column name is found in a single COLGROUP multiple times. BMC AMI Stats skipped the object. User response: Eliminate the duplicate column and rerun the job. |
| NGTT130 | COLUMN GROUP DATA CANNOT EXCEED 2000 BYTES - PROCESSING SKIPPED FOR TABLESPACE Explanation: The length of COLGROUP data cannot exceed 2000 bytes. BMC AMI Stats skipped the object. User response: Reduce the COLGROUP data size and rerun the job. |
| NGTT131 | SQL ERROR WHEN PROCESSING CATALOG UPDATES - STATS ABORTED Explanation: An SQL error occurred during the BMC AMI Stats update phase. BMC AMI Stats skipped SQL processing for the object. User response: If you are unable to determine and correct the SQL error, contact BMC Support. |
| NGTT132 | SQL ERROR - MODULE: moduleName - DIAGNOSTIC DATA FOLLOWS Explanation: An SQL error occurred during the BMC AMI Stats update phase in the identified module. BMC AMI Stats skipped SQL processing for the object. Additional diagnostic data follows. User response: If you are unable to determine and correct the SQL error, contact BMC Support. |
NGTT133 | +HISTORY PARAMETER SET TO DFLT - HISTORY WILL BE SET FROM ZPARM: STATHIST Explanation: The +HISTORY configuration parameter is set to DFLT or D. The SYSIN HISTORY parameter will be set to the value currently contained in the STATHIST variable in the Db2 DSNZPARM or equivalent module. User response: No action is required. |
| NGTT134 | HISTORY OPTION SET FROM ZPARM STATHIST TO: value Explanation: The SYSIN HISTORY option is set to the indicated value, which is based on the STATHIST variable in the Db2 DSNZPARM or equivalent module. Possible values are as follows:
User response: No action is required. |
| NGTT135 | +SKIPIX(YES), ONLY RTS UPDATES FOR INDEX string-1 .string-2 (number-1) Explanation: +SKIPIX(YES) was set for the specific utility. Catalog statistics are not updated. Only RTS tables are updated for the specified object. User response: No action is required. |
| NGTT136 | EXEC XSTAT001 SET SKIPIX TO N, +SKIPIX(YES) IGNORED FOR INDEX string-1.string-2 (number-1) Explanation: +SKIPIX(YES) was set for the specific utility and the REXX exit XSTAT001 was called during the processing of the referenced object and set SKIPIX = N. The value of SKIPIX = N returned from the REXX exit XSTAT001 overrides +SKIPIX(YES) so that index statistics are updated for the specified objects. User response: No action is required. |
| NGTT137 | TABLE SPACE string-1.string-2 IS A PBG – READTS SET TO YES – EXPECT INCREASED RESOURCE CONSUMPTION Explanation: The BMC AMI Stats job detected processing of a PBG object. To gather the table space statistic values, the parser set the READTS option to YES to enable the reading of the table space. Because BMC AMI Stats reads the table space, resource consumption increases. User response: No action is required. |
| NGTT138 | SAVESTATS YES PPROCESSING DISABLED FOR DB.TS dbname.tsname Explanation: A BMC AMI Stats job ran with the SAVESTATS option that drives the BMCSTATS repository table updates. The column field definition for the repository table referred to in the previous message is in error. The BMC AMI Stats job will continue processing the table space indicated in this message, but SAVESTATS processing is disabled. The BMCSTATS repository tables will not be processed for this specific table space during the processing of this job. User response: Review the message in the SYSERROR file and contact BMC Support. |
| NGTT990 | diagnostic text Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
| NGTT991 | diagnostic text Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
| NGTT992 | diagnostic text Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
| NGTT993 | diagnostic text Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
| NGTT994 | diagnostic text Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
| NGTT995 | diagnostic text Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
| NGTT996 | diagnostic text Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
| NGTT997 | diagnostic text Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
| NGTT998 | diagnostic text Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
| NGTT999 | diagnostic text Explanation: These messages are to be used by BMC Support. They are diagnostic/trace messages. User response: No action is required. |
Comments
Log in or register to comment.