Messages NGTR900 through NGTR999

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

VARIABLE INDEX VERSIONING NOT SUPPORTED. REBUILD THE INDEX.


Explanation: NGTUTIL does not support unpadded index keycolumn conversion from CHAR to VARCHAR. Index Rebuild is recommended.

User response: Run INDEX REBUILD utility.

NGTR903

UID 'utilityID' IS IN USE BY ANOTHER JOB (BMCUTIL) - RUN ABORTED


Explanation: The indicated utility ID is currently being used by another utility, as identified by a conflict in the BMCUTIL table.

User response: No action is required.

NGTR904

PBG REORDERED ROW FORMAT INCONSISTENCY. THIS PART (partitionNumber) DIFFERS FROM PART 1 ({ON | OFF})


Explanation: Not all partitions of the table space have the same row format, which is required if you are reorganizing a partition-by-growth table space, and you did not specify the ROWFORMAT option to force this consistency. The utility terminates. If the message displays ON, the indicated partition is in reordered row format (RRF), but partition one is not. If the message displays OFF, the indicated partition is not in RRF, but partition one is.

User response: Correct the inconsistency by either specifying ROWFORMAT with NGT Reorg and rerunning the job, or by running the IBM REORG utility on the object.

NGTR905

PBG EXTENDED RBA FORMAT INCONSISTENCY. THIS PART (partitionNumber) DIFFERS FROM PART 1 ({XTD | BASC})


Explanation: Not all partitions of the table space have the same row format, which is required if you are reorganizing a partition-by-growth table space, and you did not specify the RBALRSN_CONVERSION option to force this consistency. The utility terminates. If the message displays XTD, the indicated partition is in extended RBA format, but partition one is in basic format. If the message displays BASC, the indicated partition is in basic RBA format, but partition one is in extended format.

User response: Correct the inconsistency by either specifying RBALRSN_CONVERSION with NGT Reorg and rerunning the job, or by running the IBM REORG utility on the object.

NGTR906

CR=tableName


Explanation: This message displays the creator and table name that applies to a previous message.

User response: No action is required. See the response for the message displayed before this one.

NGTR907

DICTIONARY IN TS databaseName.tableSpaceName PART partitionNumber DIFFERS FROM THAT IN PART 1 - JOB TERMINATES.


Explanation: You used the NGT Reorg +PBGCHKDICT(NO) parameter while reorganizing a partition-by-growth (PBG) object that has different dictionaries across partitions. Therefore, NGT Reorg did not check or rebuild the dictionaries. The job has terminated because the dictionaries for a PBG object must be the same across all partitions.

User response: Specify +PBGCHKDICT(YES) or rebuild the dictionaries so that they are the same across all partitions.

NGTR908

COMPRESS SETTING IN TS databaseName.tableSpaceName PART partitionNumber DIFFERS FROM PART 1.

Explanation: You used the NGT Reorg +PBGCHKDICT(NO) parameter while reorganizing a partition-by-growth (PBG) object that has different compression settings across partitions. The job has terminated because the compression for a PBG object must be consistent across all partitions.

User response: No action is required. Ensure that the compression attribute is the same across all the table space partitions and perform the reorganization again.

NGTR909

SIZE OF hexstring-1 PAGES EXCEEDS THE MAX ALLOWED BY DB2 FOR INDEX


Explanation: The size of the index has exceeded the capacity allowed by DB2 for the index.

User response: Reduce either PCTFREE or FREEPAGE or both so that the keys fit within DB2 limits.

NGTR910

FORCEID IS NOT AUTHORIZED BY +FORCEID(variable) PARAMETER


Explanation: You tried to execute FORCEID. Based on the +FORCEID() configuration parameter, you are not authorized to execute FORCEID.

User response: Contact BMC Customer Support.

NGTR911

UTILITY ERROR, JOB MUST BE RE-EXECUTED WITH 'RESTART/QUICKEXIT'.


Explanation: This message is issued when a critical error occurs and the reorganized or loaded objects are in an inconsistent state (that is, they cannot be used by DB2).

User response: Do not attempt to rename data sets. Rerun the job without modifications. You may change the restart parameter to either RESTART or QUICKEXIT. If the problem persists contact BMC Customer Support for assistance.

NGTR912

READING TS TO BLD DICTIONARY FOR COMPARISONS.

Explanation: NGT Reorg has started to build a new compression dictionary.

User response: No action is required.

NGTR913

ALL ROWS WILL BE RECOMPRESSED USING THE SELECTED DICTIONARY

Explanation: NGT Reorg has started to reorganize a partition-by-growth (PBG) object and build a new compression dictionary for use across all table space partitions.

User response: No action is required.

NGTR914

RESTORE INDEX PROCESSING TERMINATED, REASON=(INVALID SYNCHRONIZATION POINTS).


Explanation: The process of restoring a reorganized index on an interim sequential file (TAPEDD) to the index space identified by a previous NGTR578 message has failed, possibly because of an I/O error.

User response: There should be prior messages indicating the nature of the problem. Check the JOBLOG and SYSERROR file for other error messages. There should also be dump information in the LOGPDS. Contact BMC Customer Support.

NGTR915

RESTORE INDEX PROCESSING TERMINATED, REASON=(INVALID COUNTS).


Explanation: See message NGTR914.

User response: See message NGTR914.

NGTR916

RESTORE INDEX PROCESSING TERMINATED, REASON=(TRAILER RECORD MISSING).


Explanation: See message NGTR914.

User response: See message NGTR914.

NGTR917

INDEX RECORDER IS WAITING.


Explanation: This message indicates that the current task is waiting for the process to record the completed index onto an interim sequential file (TAPEDD). The process or task currently holding this resource can be identified by a previous NGTR918 message.

User response: No action is required.

NGTR918

INDEX RECORDER STARTED. DSN=string-1


Explanation: The current task has just started the process of writing the completed index onto an interim sequential file string-1. Other tasks requesting this resource will queue behind and can be identified by message NGTR917.

User response: No action is required.

NGTR919

INDEX RECORDER RESET.


Explanation: The current task has experienced a severe error writing the completed index onto an interim sequential file (TAPEDD). The internal stack pointer will be reset so that other tasks will write over the data previously recorded.

User response: There should be prior messages indicating the nature of the problem. Check the JOBLOG and SYSERROR file for other error messages. Contact BMC Customer Support.

NGTR920

INDEX RECORDER ENDED, number-1 PAGES, number-2 TREE, number-3 LEAF, number-4 EMPTY


Explanation: This message marks the end of the process that was described by message NGTR918. Exclusive control of the 'INDEX RECORDER' resource has been released. As a result, the first waiting task will be activated.

User response: No action is required.

NGTR921

INDEX LOAD FAILED, TERMINATING.


Explanation: See message NGTR914.

User response: See message NGTR914.

NGTR922

string-1 FILE ERROR, DEVICE TYPE IS NOT SUPPORTED.


Explanation: The string-1 file must reference a data set on either tape or DASD. No other devices are supported.

User response: Verify that the DD statement string-1 is in your JCL. If it is on tape or DASD, then contact BMC Customer Support.

NGTR923

string-1 FILE ERROR, DATASET IS A PDS.


Explanation: The string-1 file must reference a data set that is not a partitioned data set (PDS).

User response: Change the string-1 DD statement to reference a sequential file.

NGTR924

string-1 FILE ERROR, DATASET IS TEMPORARY.


Explanation: The string-1 file must reference a non-temporary data set.

User response: Change the string-1 DD statement to reference a non-temporary data set.

NGTR925

FAILED TO OPEN FILE string-1.


Explanation: Open failed for the data set named in the //string-1 DD statement. This file is either for the index or the table space +TAPEDD parameter or a system-assigned name if restarting.

User response: Check system messages for any indications why this open has failed. Contact BMC Customer Support.

NGTR926

INSUFFICIENT AUX STORAGE TO RUN WRITERS


Explanation: There is insufficient auxiliary storage to which to write a table space partition.

User response: Increase the amount of auxiliary storage and rerun the job. If necessary, contact BMC Customer Support.

NGTR927

INDEX LOADER STARTED. DSN=string-1


Explanation: The current task has just started the process of loading the completed index from an interim sequential file string-1 into the index space.

User response: No action is required.

NGTR928

INDEX LOADER ENDED.


Explanation: This message marks the end of index load from an interim sequential file (TAPEDD).

User response: No action is required.

NGTR929

PBG tableSpaceName (number-1 - number-2) WILL BE FORMATTED AS EMPTY


Explanation: The last parts of a PBG must be formatted as empty parts. They will have a dictionary if one exists.

User response: No action is required.

NGTR930

LOGIC ERRORS.


Explanation: There will be a message text describing the internal error.

User response: Contact BMC Customer Support.

NGTR931

TABLESPACE RECORDER STARTED DSN=string-1


Explanation: The current task has just started the process of recording or writing the completed table space onto an interim sequential file string-1

User response: No action is required.

NGTR932

TABLESPACE RECORDER ENDED.


Explanation: This message marks the end of the process that was described by message NGTR931.

User response: No action is required.

NGTR933

RESTORE TABLESPACE PROCESSING TERMINATED, REASON=(INVALID COUNTS).


Explanation: The process of restoring a completed table space image on an interim sequential file (TAPEDD) to the target table space has failed due to a count mismatch between the actual number of records written to the file and the number of records read from it.

User response: There should be prior messages indicating the nature of the problem. Check the JOBLOG and SYSERROR file for other error messages. Contact BMC Customer Support.

NGTR934

RESTORE TABLESPACE PROCESSING TERMINATED, REASON=(INVALID BLOCK LENGTH).


Explanation: The process of restoring a completed table space image on an interim sequential file (TAPEDD) to the target table space has failed because the length of a block of data on the file was found not to be a multiple of 4K bytes.

User response: There should be prior messages indicating the nature of the problem. Check the JOBLOG and SYSERROR file for other error messages. Contact BMC Customer Support.

NGTR935

TWO DD STATEMENTS (string-1, string-2) REFERENCE THE SAME DATASET, CHANGE ONE.


Explanation: This message reports that the two files (string-1 and string-2) refer to the same data set.

User response: Correct the JCL and make sure that those DD statements have different data set names.

NGTR936

CATALOG SERVICE FAILED FOR FILE(string-1) RC=hexstring-1, R0=hexstring-2


Explanation: An attempt to catalog/recatalog the data set referenced by DD or file string-1 have failed. The return and reason code from the catalog service are X'hexstring-1' X'hexstring-2' respectively.

User response: This is an MVS catalog service error. If the RC=8, then R0 is the catalog error reason code. See catalog diagnosis guide for further information.

NGTR937

TASK ABENDING CODE= hexstring-1.


Explanation: This message is issued to identify the task which is currently abending.

User response: A dump may exist in the Log PDS. This may be an NGT abend or an MVS system abend. If an MVS system abend, refer to the appropriate MVS manual. Contact BMC Customer Support. Have the diagnostic information available for support personnel.

NGTR938

DISP=SHR OR DISP=NEW IS NOT ALLOWED. SPECIFY DISP=OLD OR DISP=MOD FOR DD DDname.


Explanation: The utility will use the data set referenced by the indicated DD name to restart, and a disposition of SHR or NEW is not allowed in this case.

User response: Correct the disposition and rerun the job.

NGTR939

CONDITIONAL DISP OF 'DELETE' IS NOT ALLOWED ON DD string-1.


Explanation: The data set referenced by DD string-1 will be used for restarting the utility. An abnormal termination (conditional) disposition subparameter value of DELETE conflicts with NGT utilities restart logic.

User response: Change the abnormal termination (conditional) disposition subparameter value to either CATLG or KEEP.

NGTR940

NORMAL DISP OF 'DELETE' IS NOT ALLOWED ON DD string-1.


Explanation: The data set referenced by DD string-1 will be used for restarting the utility. A normal termination subparameter value of DELETE conflicts with NGT/Utilities restart logic.

User response: Change the normal termination subparameter value to either CATLG or KEEP.

NGTR941

//string-1 DD DSN=string-2 IS MISSING


Explanation: The previous run with this utility id included a DD statement for DDname string-1 referring to data set string-2, but this run does not. The previous run failed and this is a restart. This DD statement cannot be changed across restarts.

User response: Add the DD statement to the JCL and rerun the utility. Alternatively, rerun the JOB with PARM=NORESTART.

NGTR942

DATASET string-1 IS ALREADY CATALOGED


Explanation: The data set named in message resides on a volume other that the one allocated to the JOBSTEP.

User response: Remove the VOL parameter from the DD statement for this data set. If no VOL was coded, then change the disposition from NEW to MOD.

NGTR943

UID 'string-1' IS IN USE BY ANOTHER JOB - RUN ABORTED.


Explanation: String-1 is the uid specified as the second value in the EXEC statement PARM field. If none is provided, the jobname is used. The enqueue issued to check concurrent execution returned an indication that this uid is active.

User response: Check on the uniqueness of your uid. If you can find no duplicate uid, contact BMC Customer Support.

NGTR944

EXCESSIVE RESOURCES REQUIRED, REORG THIS TABLESPACE USING +SORT(YES)


Explanation: The table space is too badly disorganized to reorg using the slots method. Run using SORT.

User response: The table space is too badly disorganized to reorg using the slots method. Run using SORT.

NGTR945

UID 'string-1' IS RUNNING IN A 'QUICKEXIT' MODE


Explanation: This message reports that utility whose name is string-1 will quickly do the following: complete any prior incomplete work from a previous run, perform any necessary cleanup, and then delete the restart members from the System PDS.

User response: No action is required.

NGTR946

LEVEL TABLE


Explanation: An unexpected condition occurred during processing.

User response: Contact BMC Customer Support.

NGTR948

TS HAS XML COLUMNS AND ALSO LOB COLUMNS OR IS DOING DISCARDS. tableSpaceName. OBJECT SKIPPED.


Explanation: The indicated table space contains at least one XML column. It also contains at least one LOB column, or discard processing is in effect. This combination is not supported and the utility skips the processing of this object.

User response: If appropriate for your organization, disable discard processing and rerun the job. Otherwise, contact BMC Customer Support.

NGTR950

RUNSTATS ENTRY NOT FOUND hexstring-1


Explanation: This message reports a probable internal error that will cause runstats processing to be bypassed.

User response: Contact BMC Customer Support.

NGTR951

DISCARD PROCESSING ACTIVE FOR TABLE tableName


Explanation: This message indicates that DISCARD will take place for the above named table during the course of REORG.

User response: No action is required.

NGTR952

OPEN FAILED FOR ARCHIVE DD - string-1


Explanation: A SDELETE statement or DISCARDDN parameter of REORG stmt named string-1 as the DDname for the copy of the deleted rows. The DDname exists, but the open failed for the data set.

User response: Check the system messages and the allocation messages for any indication of the error. Look for an IEC161I message. If the condition cannot be corrected, contact BMC Customer Support.

NGTR953

numberOfRows ROWS ARCHIVED TO dataSetName


Explanation: The utility has finished discarding rows and this message displays the number of rows written to the ARCHIVE DD or the DISCARDDN DD data set. The number of rows discarded does not include rows that were discarded due to altered limit keys. For information about these discarded rows, see message NGTU235 in the SYSERROR DD.

User response: No action is required.

NGTR954

numberOfRows ROWS DISCARDED FROM TABLE tableName


Explanation: NGT Reorg has finished discarding rows for the indicated table due to a DISCARD WHERE or DISCARD WHEN option. This message displays the number of rows that matched the DISCARD WHERE or DISCARD WHEN clause criteria. The number of rows discarded does not include rows that were discarded due to altered limit keys. For information about these discarded rows, see message NGTU235 in the SYSERROR DD.

User response: No action is required.

NGTR955

numberOfRows TOTAL ROWS DISCARDED FROM PART TABLE SPACE tableSpaceName.


Explanation: NGT Reorg has finished discarding rows for the indicated table space due to a DISCARD WHERE or DISCARD WHEN option. This message displays the number of rows that matched the DISCARD WHERE or DISCARD WHEN clause criteria. The number of rows discarded does not include rows that were discarded due to altered limit keys. For information about these discarded rows, see message NGTU235 in the SYSERROR DD.

User response: No action is required.

NGTR956

string-1 TOTAL ROWS DISCARDED FROM PART TABLE SPACE tableSpaceName.


Explanation: NGT Reorg has finished discarding rows for the indicated table space due to a DISCARD WHERE or DISCARD WHEN option. This message displays the number of rows that matched the DISCARD WHERE or DISCARD WHEN clause criteria. The number of rows discarded does not include rows that were discarded due to altered limit keys. For information about these discarded rows, see message NGTU235 in the SYSERROR DD.

User response: No action is required.

NGTR957

DISCARD DATASET NAME:  dataSetName


Explanation: The NGT Reorg utility discards rows during processing. This message identifies the discard data set output file name. This message is printed after the total discard row count is printed in the CDBPRINT file.

User response: No action is required.

NGTR958

TS databaseName.tableSpaceName HAS MULTIPLE TABLES WITH LOBS - AUX IGNORED.


Explanation: NGT LOBMaster was meant to run the job because the AUX keyword was specified in the SYSIN statement. NGT LOBMaster does not currently support multi-table table spaces. The AUX keyword will be ignored and NGT Reorg will perform a traditional reorganization.

User response: No action is required.

NGTR959

WTR writerName - PTN partitionName, BELOW a (b), ABOVE c (d)


Explanation: Internal documentation message that indicates the use of storage by the writer of this table space partition, where:

  • a represents the amount of memory required below the 18M line.
  • b represents the total amount of memory available below the 16M line.
  • c represents the amount of memory required above the 16M line.
  • d represents the total amount of memory available above the 16M line.

User response: No action is required.

NGTR960

WTR writerName - PTN partitionName, AUX a (b AVAIL, storageClassMemberMemory SCN AVAIL)


Explanation: Internal documentation message that indicates the use of storage by the writer of this table space partition, where:

  • a represents the remaining amount of auxiliary memory available in megabytes.
  • b represents the remaining amount of auxiliary storage available in megabytes.

User response: No action is required.

NGTR961

INSUFFICIENT MEMORY TO RUN THIS TASK (taskNumber) ON PART partitionNumber

Explanation: There is insufficient memory allocated to run the task for this table space partition.

User response: Increase the amount of MEMORY and rerun the job. If necessary, contact BMC Customer Support.

NGTR962

RUNSTATS UPDATE MISMATCH CODE number-1,ENTRY number-2 - LIST RE-SAVED


Explanation: Trying to update the Runstats information on the System PDS, a mismatch between the memory list and the DASD list was detected. The memory list is re-saved on DASD.

User response: No action is required.

NGTR963

OBJECT string-1.string-2 number-1 IS IN RW STATUS DURING REORG


Explanation: Reorg has detected that the above named object is in RW status during the process of a read-only REORG. Continuation of the reorg may result in DATA LOSS and therefore this reorg is aborted.

User response: This is a procedural error. Attempt to find out why this object is in this status during the course of the reorg. The current function will be marked complete and will not be subject to restart.

NGTR964

PARTS RANGE number-1 : number-2 WILL NOT BE PROCESSED BECAUSE COPYDDN EXISTS.


Explanation: A range of parts was specified on a REORG table space statement along with a COPYDDN or RECOVERYDDN operands that specify an existing DD statement. Only the first partition in the range will be processed. Return code will be set to 4.

User response: Either remove the DD statement for the copy operand or code a separate reorg stmt for each part in the range with a unique DDname.

NGTR965

RUNSTATS ROLLUP ABORTED DUE TO ERROR.


Explanation: An SQL error has caused the runstats rollup to abort. The failing statement follows this message.

User response: Contact BMC Customer Support.

NGTR966

PBG ADDED A PARTITION BETWEEN PREPROC AND BEFOREACC


Explanation: The PBG has grown since run initiation until utility start time.

User response: Rerun the utility.

NGTR968

XCPYDYNM ERROR. UNABLE TO PERFORM FLASHCOPY.


Explanation: The XCPYDYNM REXX exec encountered an error while trying to generate the FLASHCOPY output data set name.

User response: Check the XCPYDYNM REXX exec output to determine the cause of the error. Contact BMC Customer Support.

NGTR969

string-1 DD OPEN FAILED. UNABLE TO PERFORM FLASHCOPY.


Explanation: An error occurred while trying to open the string-1 DD.

User response: Check the NGT Journal to determine the cause of the error. Contact BMC Customer Support.

NGTR970

INITIALIZING FLASHCOPY.


Explanation: The utility is initializing the FLASHCOPY environment.

User response: No action is required.

NGTR971

totalRowCount TOTAL ROWS REORGED FOR TABLESPACE dbName.tableSpaceName.

Explanation: NGT Reorg issues a message to the CDBPRINT file that displays the total number of rows in the specified table space after the reorganization is complete. For partitioned objects, this count is only for the partitions being reorganized.

User response: No action is required.

NGTR972

string-1 DD ALLOCATED SUCCESSFULLY.


Explanation: The string-1 DD was allocated successfully.

User response: No action is required.

NGTR973

FLASHCOPY FAILED (ADRDSSU RC=number-1).


Explanation: The utility called DF/DSS (ADRDSSU program) to process the FLASHCOPY and it returned an error code.

User response: Check the NGT Journal to determine the cause of the error. Contact BMC Customer Support.

NGTR974

PROCESSING FLASHCOPY.


Explanation: The utility is processing the FLASHCOPY requests.

User response: No action is required.

NGTR975

FLASHCOPY COMPLETED SUCCESSFULLY.


Explanation: The utility processing of the FLASHCOPY requests completed successfully.

User response: No action is required.

NGTR976

ADRDSSU MESSAGE


Explanation: These messages are from the DF/DSS ADRDSSU utility.

User response: No action is required.

NGTR977

***** START OF ADRDSSU MESSAGES *****


Explanation: These following messages are output from the DF/DSS ADRDSSU utility used to process the FLASHCOPY request.

User response: No action is required.

NGTR978

***** END OF ADRDSSU MESSAGES *****


Explanation: This is the end of the messages from the DF/DSS ADRDSSU utility used to process the FLASHCOPY request.

User response: No action is required.

NGTR979

FLASHCOPY POST FAILED.


Explanation: The POST to SYSCOPY of the FLASHCOPY failed.

User response: Check the NGT Journal to determine the cause of the error. Contact BMC Customer Support.

NGTR980

POSTING FLASHCOPY.


Explanation: The utility is posting the FLASHCOPY information to SYSCOPY.

User response: No action is required.

NGTR981

POSTING FLASHCOPY COMPLETED.


Explanation: The posting of the FLASHCOPY information to SYSCOPY is complete.

User response: No action is required.

NGTR982

UNDO FLASHCOPY.


Explanation: The utility is undoing the FLASHCOPY due to QUICKEXIT.

User response: No action is required.

NGTR983

UNDO FLASHCOPY COMPLETED.


Explanation: The undo of the FLASHCOPY is complete.

User response: No action is required.

NGTR984

VERIFY FLASHCOPY.


Explanation: The utility is verifying the status of the FLASHCOPY.

User response: No action is required.

NGTR985

VERIFY FLASHCOPY COMPLETED.


Explanation: The verify of the status of the FLASHCOPY is complete.

User response: No action is required.

NGTR986

ALTERMessage


Explanation: This message displays the first part of each ALTER statement in SYSIBM.SYSPENDINGDDL for the object that you are reorganizing.

Note

This message does not display the entire ALTER statement, but provides you with an indication of the pending ALTER statements that exist for the object that you are reorganizing.

User response: No action is required.

NGTR987

PACKAGE INVALIDATION FAILED. ACCESS PATHS MIGHT NOT BE OPTIMAL.


Explanation: To ensure optimal access paths after a limit key change, NGT Reorg attempted to invalidate application packages to force a rebind of those packages. However, the invalidation failed.

User response: No action is required. However, to ensure optimal access paths, BMC recommends that you rebind applicable application packages.

NGTR988

DICTIONARY BUILT FOR TS databaseName.tableSpaceName KEEPDICTIONARY IGNORED


Explanation: The KEEPDICTIONARY option specified in +PBGKEEPDICT(YES) was ignored because compression is running and the table space does not have a compression dictionary or because REBUILDDICT was specified.

User response: No action is required. A compression dictionary will be built for the table space and processing will continue.

NGTR990

diagnostic text.


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

User response: No action is required.

NGTR991

diagnostic text.


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

User response: No action is required.

NGTR992

diagnostic text.


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

User response: No action is required.

NGTR993

diagnostic text.


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

User response: No action is required.

NGTR994

diagnostic text.


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

User response: No action is required.

NGTR995

diagnostic text.


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

User response: No action is required.

NGTR996

diagnostic text.


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

User response: No action is required.

NGTR997

diagnostic text.


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

User response: No action is required.

NGTR998

diagnostic text.


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

User response: No action is required.

NGTR999

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