Messages NGTU700 through NGTU799

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

LIMIT KEY VIOLATION: DISCARD NOT ALLOWED DURING CHANGE APPLY


Explanation: Changes to the table space during the reorganization, such as inserts or changes to the limit key, resulted in rows after the last limit key. NGT Reorg does not allow discards in this case and terminates. Additional NGTU700 and NGTZ999 messages provide current and last limit key information.

User response: Rerun the reorganization and do not make changes to the table space until the reorganization completes.

NGTU702

FINAL CHANGE APPLY STARTED.ESTIMATED TIME=numberSeconds SECONDS,PENDING TRANSACTIONS=numberPendingTransactions databaseName.objectName


Explanation: The final change apply phase has started. This message indicates the estimated remaining time and number of pending transactions.

User response: No action is required.

NGTU703

FINAL CHANGE APPLY AND SWITCH COMPLETED. ELAPSED TIME=numberSeconds SECONDS databaseName.objectName


Explanation: The final change apply and switch phase has completed. The message shows the elapsed time.

User response: No action is required.

NGTU704

CATCH UP PROCESSING FAILED AFTER numberCycles CYCLES.


Explanation: Change Apply processing has failed because the number of Change Apply processing cycles has exceeded the variable specified in the +CATCHUP_CYCLES(numberCycles) parameter.

User response: Perform one of the following actions:

  • Increase the +CATCHUP_CYLCES(numberCycles) parameter variable and rerun the job.
  • Rerun the job when application activity on the table is minimal.
NGTU710

numberOfRows TOTAL ROWS UNLOADED FOR TABLE DBName.tableSpaceName


Explanation: Indicates that the total number of rows, numberOfRows, were unloaded from the table DBName.tableSpaceName. If unloading from multiple table spaces, the final table space will be listed. The total rows unloaded is the total for all table spaces processed.

User response: No action is necessary.

NGTU711

NO INPUT SELECTED FROM INFILE:  inputFile

Explanation: The input file was read and the desired object identifiers (OBIDs) were not found in the file.

User response: Specify an appropriate OBID that is contained in the input file, or use a different input file.

NGTU712

UNLOAD INPUT HAS OBID(S):  obid1, obid2 , obid3 ,...

Explanation: An input file was read and the listed object identifiers (OBIDs) were found in the input.

User response: Specify the appropriate OBID that is contained in the input file, or use a different input file.

NGTU713

UNLOAD OUTPUT FILE outputFile LACKS SYMBOLIC VARIABLE FOR GENERATING SEPARATE OUTPUT DSNAMES BY PARTITION.

Explanation: When NGT Unload detects the BYPART keyword, the utility attempts to unload partitions as separate outputs. However, if the OUTPUT command DSNAME value lacks an appropriate symbolic variable, the utility cannot properly create individual partition outputs.

User response: Modify the OUTPUT command DSNAME value to include an appropriate symbolic variable (for example, &DSNUM, &PART, or &PART4) to generate individual output data set names for each partition.

NGTU715

+SYSINORDER(HONOR) IN USE. MULTIPLE SELECT TO SAME OUTPUT DATASET CANNOT BE PERFORMED.

Explanation: You cannot specify +SYSINORDER(HONOR) and an UNLOAD command with multiple SELECT statements for the same data set.

User response: Remove +SYSINORDER(HONOR) and rerun the UNLOAD command.

NGTU716

SPANNED YES RESTRICTED FOR MULTIPLE SELECT TO SAME OUTPUT DATASET.

Explanation: You cannot specify SPANNED YES on an UNLOAD command with multiple SELECT statements for the same data set.

User response: Remove SPANNED YES and rerun the UNLOAD command.

NGTU717

"INFILEPFX" IS MUTUALLY EXCLUSIVE WITH MULTIPLE SELECT STATEMENTS

 Explanation:  NGT Unload cannot handle the INFILE ddname as a prefix when you use multiple SELECT statements.

User response:  Respecify the input as separate UNLOAD commands and rerun the job.

NGTU718

NO DDNAMES TO MATCH PREFIX ddName FOR PARTITION: partitionList

Explanation: INFILE ddName INFILEPFX was specified. The NGT utility was unable to find DD names to correspond to all partitions. The partition list shows which partitions lack corresponding DD names.

User response: Respecify all corresponding DD names and rerun the job.

NGTU719

NO DDNAMES FOUND FOR "INFILE ddName INFILEPFX". ALLOCATE AND RERUN

Explanation: INFILE ddName INFILEPFX was specified. The NGT utility was unable to find any DD names to match the specified DD name prefix.

User response: Respecify all appropriate DD names and rerun the job.

NGTU720

VARIABLE "DSNAME" SET BY REXX EXEC “XULDDYNM” IS INVALID.
- INVALID DATA SET NAME FOR DDNAME=ddName

Explanation: NGT Unload attempted to dynamically allocate a data set using values returned from the XULDDYNM REXX EXEC, but the returned data set name is invalid or missing.

User response: Use a JCL DD statement or an OUTPUT statement to specify the required data set name or correct the XULDDYNM REXX EXEC.

NGTU730

TABLESPACE tableSpaceName (number-1) ROWS ARE CURRENTLY IN BASIC ROW FORMAT.


Explanation: Rows in the above named tablespace and partition are in Basic Row Format. The ROWFORMAT indicator in the DB2 catalog for this TS shows Reordered Row Format.

User response: No action is required.

NGTU731

TABLESPACE tableSpaceName (number-1) ROWS ARE CURRENTLY IN REORDERED ROW FORMAT.


Explanation: Rows in the above named tablespace and partition are in Reordered Row Format. The ROWFORMAT indicator in the DB2 catalog for this TS shows Basic Row Format.

User response: No action is required.

NGTU732

TABLESPACE tableSpaceName (number-1) ROWS WILL BE CONVERTED TO BASIC ROW FORMAT (BRF).


Explanation: Rows in the above named tablespace and partition will be converted to Basic Row Format due to the 'ROWFORMAT BRF' specification on the utility statement.

User response: No action is required.

NGTU733

TABLESPACE tableSpaceName (number-1) ROWS WILL BE CONVERTED TO REORDERED ROW FORMAT (RRF).


Explanation: Rows in the above named tablespace and partition will be converted to Reordered Row Format due to the 'ROWFORMAT RRF' specification on the utility statement.

User response: No action is required.

NGTU734

ENCRYPTED VSAM DSN=dataSetName IS NOT SUPPORTED.


Explanation:
The indicated IBM DB2 object data set is not supported because of the use of IBM's Transparent Data Encryption.

User response: No action is required.

NGTU735

STRIPED VSAM DSN=dataSetName IS NOT SUPPORTED.


Explanation:
The indicated striped data set for IBM VSAM objects is not supported because of the use of IBM's Transparent Data Encryption.

User response: No action is required.

NGTU736

MM I/O ERROR DSN=dataSetName RC=returnCode


Explanation:
A media manager error has occurred in the indicated IBM DB2 object data set.

User response: Collect the job output and contact BMC Customer Support.

NGTU738

CDBSS VERSION versionNumber ON systemName DOES NOT SUPPORT ENCRYPTION.


Explanation:
The indicated version of the CDB subsystem (CDBSS) is not supported because of the use of IBM's Transparent Data Encryption.

User response: Update to a newer version of the CDBSS.

NGTU739

CDBSS VERSION versionNumber ON systemName IS BACK LEVELED. VERSION versionNumber.releaseNumber OR HIGHER IS REQUIRED.


Explanation:
The indicated version of the CDB subsystem (CDBSS) is back leveled.

User response: Update to a newer version of the CDBSS.

NGTU740

SORT ENTERED FOR OBJECT (hexstring-1) KEYLEN=number-1 DATALEN=number-2 MAXMEM=number-3.


Explanation: This message indicates that data sorting is about to commence for the current utility. The data will be ordered based on a key size of KeyLen and having maximum record size of DataLen using an internal memory size of MaxMem in megabytes.

User response: No action is required.

NGTU741

SORT COMPLETED FOR OBJECT (hexstring-1). TOTAL RECORDS=numberOfRecords BYTES=numberOfBytes FILES=number-1.


Explanation: This message indicates that data sorting has completed with statistics on the total number of records, total bytes and total internal disk files used.

User response: No action is required.

NGTU742

EXTERNAL SORT ENTERED FOR OBJECT (hexstring-1).


Explanation: This message indicates that in-memory sort capacity has exceeded and an external disk file sort has been invoked.

User response: No action is required.

NGTU750

PBG ADDPART SERVICE FAILED.


Explanation: This message is issued before an unrecoverable abend. The service to add a partition to a PBG failed.

User response: Please send the produced abend info to BMC Customer Support.

NGTU751

PBG ADDPART FUNCTION FAILED.


Explanation: This message is issued before an unrecoverable abend. The service to add a partition to a PBG failed.

User response: Please send the produced abend info to BMC Customer Support.

NGTU752

PBG ADDPART FUNCTION TIMED OUT.


Explanation: The service to add a partition to a PBG failed has timed out.

User response: Please send the produced abend info to BMC Customer Support.

NGTU753

PBG ADDPART FUNCTION TIMED OUT. RETRY IN PROGRESS.


Explanation: The service to add a partition to a PBG failed has timed out. Reorg is retrying the service.

User response: No action is required.

NGTU754

PBG ADDPART FUNCTION SUCCESSFUL. PART number-1 ADDED TO tableSpaceName.


Explanation: The service to add a partition to a PBG was successful.

User response: No action is required.

NGTU755

PBG ADDCOPY FUNCTION SUCCESSFUL. PART number-1 ADDED TO tableSpaceName.


Explanation: The service to add a partition to a PBG was successful.

User response: No action is required.

NGTU760

MISSING DB2 DATASET(S) DSN=string-1 TO string-2.


Explanation: While physically renaming newly created shadow DB2 data sets to replace old existing DB2 data sets, it was found that the above named data set or range of data sets 'TO nnnn' is/are missing. Rename will continue only if the missing gap is not filled.

User response: No action is required. However if message NGTU761 is issued right after, then you need to consider deleting the data set creating this gap.

NGTU761

RENAME CAN NOT CONTINUE DUE TO MISSING DB2 DATASETS OLD=number-1 GAP=number-2 NEW=number-3.


Explanation: See prior message for more information on this error situation. The numbers in the message show existing count of DSNUMs followed by the number of missing DSNUMs followed by the number of new DB2 shadow datasets

User response: This is a terminating error. Take action by deleting datasets following the names reported in message NGTU760. For example: if the last reported name is A003, then delete from A004 onward.

NGTU762

VSAM CATALOG HURBA ERROR. EXPECTED VALUE=hexstring-1 ACTUAL VALUE=hexstring-2 .


Explanation: The high formatted page number recorded in the header page of the TS or IX can not be greater than the VSAM catalog hurba of the TS data set. This condition is further explained by DB2 error code 00C20110.

User response: This is a terminating error. See the recommended action set by DB2 error code 00C20110.

NGTU763

string-1 SPACE string-2.string-3 PART number-1 REACHED MAXIMUM SIZE OF sizeOfDataSet.


Explanation: The above named TABLE or INDEX SPACE partition has reached the maximum data set size and can no longer be extended. number-2 is the current data set size in bytes.

User response: To increase the amount of available space, consider running REORG using FREEPAGE 0 and PCTFREE 0 or change the DSSIZE of the partition via the DB2 ALTER facility.

NGTU764

string-1 SPACE string-2.string-3 PIECE LIMIT (number-1) REACHED. TOTAL SIZE IS sizeOfDataSet.


Explanation: The above named TABLE or INDEX SPACE has reached its architectural data set limit of number-1 number-2 is the current space size in bytes.

User response: To increase the amount of available space, consider running REORG using FREEPAGE 0 and PCTFREE 0 or for an INDEX, consider increasing the piece size via the DB2 ALTER INDEX facility.

NGTU765

'string-1' ENCLAVE ACTUAL ZIIP=string-2 ELIGIBLE ZIIP=string-3 SECONDS.


Explanation: string-1 is the name of an internal process that has just completed. string-2 is the zIIP engine utilization time for the process. string-3 is the General CPU utilization time for the process. These values are unweighted.

User response: No action is required.

NGTU766

NGT(TM) RESTRICTED FUNCTION 'functionName' DETECTED ON DB.objectType=objectName.


Explanation: The utility encountered an object or function that it does not currently support. Message NGTB136 might follow this one and provide more information. The utility terminates processing for the indicated object.

User response: Review any additional messages. If applicable, change and resubmit the job.

NGTU767

JOB ACTUAL ZIIP=string-1 ELIGIBLE ZIIP=string-2 SECONDS.


Explanation: string-1 is the zIIP processor utilization time in seconds for the current job. string-2 is the time in seconds eligible for a zIIP processor. These values are unweighted.

User response: No action is required.

NGTU777

TOTAL ENCLAVE SRB CPUTIME=string-1 SECONDS.


Explanation: This message shows the total number of CPU seconds executed in ENCLAVE SRB mode. These values are unweighted.

User response: No action is required.

NGTU778

FUNCTION=hexstring-1 TIMER STARTED FOR hexstring-2.


Explanation: This is a trace message showing that an internal timer has been activated for the reported internal function and the actual time in hundreds of seconds.

User response: No action is required.

NGTU779

FUNCTION=hexstring-1 TIMER EXPIRED.


Explanation: This is a trace message showing that the timer that was started for the reported function has expired before completion of the function.

User response: No action is required.

NGTU781

SYNTAX ERROR OCCURRED AT STATEMENT NO. statementNumber.


Explanation: There is a syntax error in the specified statement.

User response: Review the syntax diagram for the NGT product that you are running.

NGTU782

TEXT IN ERROR IS: errorText


Explanation: A syntax error was found in the specified statement.

User response: Review the syntax diagram for the NGT product that you are using. 

NGTU783

string-1.


Explanation: An error was found in the statement specified in NGTU781 or NGTZ170.

User response: Review the syntax diagram for the NGT product that you are running.

NGTU784

EXPECTED TOKENS FOLLOWS:


Explanation: A syntax error was found in the statement specified in NGTU781 or NGTZ170.

User response: Review the Syntax Diagram for the NGT product that is being executed.

NGTU785

string-1.


Explanation: This message indicates a syntax error was found. This message is related to NGTU784 and identifies the missing tokens.

User response: Review the Syntax Diagram for the NGT product that is being executed.

NGTU790

string-1.


Explanation: Records from the DIAGNOSE file are read and then echoed to the output file prior to parsing the diagnose statement. Parsing errors if any will be reported via NGTU78X message.

User response: No action is required.

NGTU791

DIAGNOSE string-1 (string-2)INSTANCE(number-1) HAS MATCHED.


Explanation: This message indicates that a defined diagnostic event has matched its criteria and its action clause will be processed. string-1 is the event type and string-2 is the event ID and number-1 is the event occurrence number.

User response: No action is required.

NGTU792

DIAGNOSE string-1 (string-2)INSTANCE(number-1) IS WAITING FOR REPLY.


Explanation: This message is the result of executing an ACTION(WAIT) clause specified on a Diagnose statement. Refer to message NGTU791 for more details on the event that took place.

User response: To continue program execution, reply to the above message with any single character using a console operator command.

NGTU793

ENVIRONMENT DOES NOT ALLOW EXECUTION OF REXX EXEC (string-1).


Explanation: An attempt to execute ACTION(EXEC) clause specified on a Diagnose statement has failed due to environment restrictions. For a description of the event that took place, see prior NGTU791 message.

User response: No action is required.

NGTU794

DIAGNOSE string-1 (string-2)INSTANCE (number-1) SVCD FOR BMC SOFTWARE INC.


Explanation: This message is the result of executing an ACTION(SVCD) clause specified on a Diagnose statement. Refer to message NGTU791 for more details on the event that took place.

User response: Please send the produced SVC DUMP to BMC Customer Support.

NGTU795

string-1 (string-2) HITS (number-1) SUPP (number-2) EXECS (number-3) WAITS (number-4) SNAPS (number-5) SVCD (number-6).


Explanation: This message shows Diagnose facility event statistics.

User response: No action is required.

NGTU796

DIAGNOSE REXX EXEC (string-1) DOES NOT EXIST.


Explanation: An 'ACTION(EXEC)' is coded on a Diagnose statement but the EXEC does not exist in the PDS referenced by //NGTEXEC dd statement.

User response: Correct the EXEC name or add the EXEC to the NGTEXEC library.

NGTU797

DIAGNOSE string-1 (string-2)INSTANCE (number-1) MOD (string-3) LOGPDS DUMP SUPPRESSED.


Explanation: This message is the result of executing an ACTION(SUPPRESS) clause specified on a Diagnose ABEND statement. MOD is the module name that issued the abend. The logpds dump has been suppressed.

User response: No action is required.

NGTU798

DIAGNOSE string-1 (string-2)MATCHLIM HAS REACHED.


Explanation: The matchlim value specified on the diagnose statement for above named event has reached its limit and as a result, the event will be disabled from diagnose processing.

User response: No action is required.

NGTU799

DIAGNOSE IS EXECUTING ACTION (string-1).


Explanation: The diagnose processor is in the process of executing the action clause of the event that matched in a prior NGTU791 message.

User response: No action is required.

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

Comments