Messages NGTR100 through NGTR199

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

objectType DATASET IS MIGRATED FOR shortObjecttype databasename.objectname


Explanation:   You have run an NGT product against an object whose VSAM data sets have been migrated. This message identifies the space related to the migrated data set.

The variables are defined as follows:

  • objectType is TABLESPACE or INDEXSPACE.
  • shortObjectType is TS (for table space) or IX (for index).
  • databaseName is the name of the database.
  • objectName is the name of the table space or index.

NGT products do not process migrated data sets.

User response:  

  • If +HRECALL(YES) is specified in the UTLPARMS DD, the NGT product attempts to recall the data set. Try to run the product again.
  • If  +HRECALL(NO) is specified in the UTLPARMS DD, the NGT product does not attempt to recall the data set. Recall the data set and try to run the product again.
NGTR101

'GET INFO' FAILED FOR string-1 - ERROR CODE number-1 .


Explanation: LISTCAT failed with return code number-1.

User response: It is possible the data set does not exist. A following message names the data set.

NGTR102

DEFINE FAILED FOR NEW DB2 DATASET.


Explanation: The AMS DEFINE failed for the data set named in message NGTR103.

User response: Perform the following steps:

  1. Check the IDCAMS in the JOURNAL for more detailed error messages.
  2. Check JESMSGLG for error information.
  3. Retry the utility. If the problem is no-space-on-volume, you can use the +VOLS option to specify different volumes.
  4. Contact BMC Customer Support.
NGTR103

DATASET NAME - string-1.


Explanation: This message names the data set that is the object of a previous message.

User response: No action is required.

NGTR104

// string-1 PARMS - NO MEMORY FOR string-2 - number-1 BYTES.


Explanation: A Getmain failed for an internal control block. String-1 names the parameter file being processed, string-2 is an identifier of the control block, and number-1 is the number of bytes required.

User response: If the number of bytes (number-1) is very large, this may be a logic error, in which case contact BMC Customer Support. If not, you may have to increase the region size.

NGTR105

NO MEMORY FOR //string-1 DD PARMS - string-2 - number-1 BYTES.


Explanation: A Getmain failed for an internal control block. String-1 names the parameter file being processed, string-2 is an identifier of the control block, and number-1 is the number of bytes required.

User response: If the number of bytes (number-1) is very large, this may be a logic error, in which case contact BMC Customer Support. If not, you may have to increase the region size.

NGTR106

parameter VALUE (prefix) EXCEEDS MAXIMUM ALLOWED SIZE (number CHARACTERS).


Explanation: The value for the indicated UTLPARMS parameter is longer than allowed. The utility is unable to allocate the data set and terminates.

User response: Change the value for the indicated parameter and resubmit the job.

NGTR107

SEVERE ERROR - TS ROWS COUNT (number-1) DOES NOT MATCH THE INDEX COUNT (number-2 ROWS).


Explanation: The ordering index picked for a table has a number of rows indexed different from the number of table rows. One is incorrect. In either case, processing cannot proceed. Message NGTR106 precedes this message, identifying the table and the index.

User response: If you feel that the index is wrong, run RECOVER INDEX. If you suspect the table, run RECOVER TABLESPACE.

NGTR108

INVALID FUNCTION CALL. CALLING MODULE=string-1, FUNCTION CODE=hexstring-1.


Explanation: Internal logic error.

User response: A snap dump should exist in the Log PDS. Find the dump member for this error. Contact BMC Customer Support.

NGTR109

INVALID PARAMETER PASSED. CALLING MODULE=string-1, PARM=hexstring-1.


Explanation: Internal logic error.

User response: A snap dump should exist in the Log PDS. Find the dump member for this error. Contact BMC Customer Support.

NGTR110

INVALID COMMON SECTION ADDRESS PASSED BY MODULE string-1, ADDRESS=hexstring-1.


Explanation: Internal logic error.

User response: A snap dump should exist in the Log PDS. Find the dump member for this error. Contact BMC Customer Support.

NGTR111

+RENAME(YES) AND +DELETE(YES) ARE INCOMPATIBLE. CHANGE ONE.


Explanation: If you intend to rename the temporary data sets to the real names after reorg, then you cannot also delete these data sets since they will have become your real DB2 data sets.

User response: Change one of the parameters and resubmit the Reorg.

NGTR112

ERROR OCCURRED DURING BLDMSG PROCESSING.


Explanation: Internal logic error.

User response: A snap dump should exist in the Log PDS. Find the dump member for this error. Contact BMC Customer Support.

NGTR113

UNEXPECTED EOF READING PAGE number-1 (hexstring-1).


Explanation: Number-1 is the page number in decimal, and X'hexstring-1' is the page number in hex. When attempting to read this page from DSNDB01.DBD01, an end-of-file condition was raised.

User response: This condition should not occur. It is possible that the DB2 Directory is in the process of being updated. Try to rerun the job. If the problem recurs, contact BMC Customer Support.

NGTR114

DSSIZE REQUIRES EXTENDED VSAM DATA SETS.


Explanation: The table space is using the DSSIZE attribute but the VSAM data set was not created with the EXTENDED attribute.

User response: The run is aborted.

NGTR115

DBD BUILD ERROR - string-1.


Explanation: An error occurred building a copy of the DBD. String-1 identifies the specific problem.

  • DBD NOT FOUND—The DBD was not found on the hash chain indicated by the internal DBID.

  • REC TYPE ERROR—The DBD record read is not for OBID 21 or 22.

  • DBDS REC MISSING—Either a DBDS RID is zero or the chain ends before the expected record is received.

  • DBD LENGTH ERR-2—A DBDS record exceeds the total DBD size from the first record.

  • DBD DATA ERROR—Either the DBD does not begin with 2039 or the DBD identifier is missing.

  • DBD OBID ERROR—The OBID value in the DBD does not match that from the catalog.

Each of these messages indicates an inconsistency in the DB2 directory.

User response: First, try to rerun the utility to eliminate the possibility of a transient error. If necessary, run the DB2 DSN1CHKR utility to check your DB2 directory. Contact BMC Customer Support for assistance.

NGTR116

DBD CONTENT ERROR - string-1.


Explanation: An error occurred building a copy of the DBD. String-1 identifies the specific problem.

  • PAGE NO. ERROR—The page read from the directory has a page number different from that expected.

  • BROKEN PAGE—The page read from the directory has the DB2 'broken page' bit set.

  • NOT A HASHED PG—Directory pages should have the 'Hashed Page' flag set. The page read does not.

  • PAGE FLAGS ERROR—The flags byte in the directory page has some unexpected flags set.

Each of these messages indicates an inconsistency in the DB2 directory.

User response: First, try to rerun the utility to eliminate the possibility of a transient error. If necessary, run the DB2 DSN1CHKR utility to check your DB2 directory. Contact BMC Customer Support for assistance.

NGTR117

//parameterType PARMS - SYNTAX ERROR – ENDING QUOTE - inputParameter.

Explanation: The closing quotation mark for this parameter was not found in the parameter value. The format for parameters containing a special character (for example, a blank or "&") is +PARM("value").

In this message:
- parameterType represents one of the following parameter types listed in the explanation for message NGTR120
- inputParameter represents the first 16 bytes of the input parameter.

User response: Correct the error and resubmit the job.

NGTR118

//string-1 PARMS - SYNTAX ERROR – OUTPUT COMMAND - string-2.

Explanation: The first word in the command is not OUTPUT. The +OUTPUT1, +OUTPUT2, +OUTPUT3, and +OUTPUT4 parameters must contain only an OUTPUT command. 

In this message:

  • string-1 represents one of the following parameter types listed in the explanation for message NGTR120.
  • string-2 represents the first 16 bytes of the input parameter.

User response: Correct the error and resubmit the job.

NGTR119

ERROR OCCURRED PROCESSING //string-1 PARMS - RUN ABORTED.


Explanation: This message follows one or more error messages that describe why this run is aborted.

User response: Correct the errors reported by the previous diagnostics.

NGTR120

//string-1 PARMS - VALUES MUST BE ENCLOSED IN PARENTHESES - string-2.


Explanation: String-1 is one of the following:

  • UTLPARMS (global parameters)

  • RRGPARMS (NGT Reorg table space parameters)

  • RRGPARMX (NGT Reorg index parameters)

  • LODPARMS (NGT Load parameters)

  • CPYPARMS (NGT Copy parameters)

  • ROLPARMS the repart function parameters)

  • ULDPARMS (NGT Unload parameters)

String-2 is the first 16 bytes of the input parameter. The format for parameters is +PARM(value). Parentheses are missing.

User response: Enclose parameter values in parentheses.

NGTR121

//string-1 PARMS - SYNTAX ERROR - TWO LEFT PARENTHESES - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is: +PARM(value). This parameter permits fewer values than are supplied. Most parameters allow only a single value.

User response: Correct the error and resubmit the utility.

NGTR122

//string-1 PARMS - MORE VALUES EXIST IN INPUT THAN ALLOWED - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is: +PARM(value). This parameter permits fewer values than are supplied. Most parameters allow only a single value.

User response: Correct the error and resubmit the utility

NGTR123

//string-1 PARMS - NOT ENOUGH VALUES IN INPUT FOR THIS PARM - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is: +PARM(value). This parameter permits fewer values than are supplied. Most parameters allow only a single value.

User response: Correct the error and resubmit the utility.

NGTR124

//string-1 PARMS - NULL VALUES ARE NOT ALLOWED FOR THIS PARM - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is: +PARM(value). This parameter permits fewer values than are supplied. Most parameters allow only a single value.

User response: Correct the error and resubmit the utility.

NGTR125

//string-1 PARMS - UNRECOGNIZED PARAMETER - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. This parameter (that is, the name following the + symbol) is not a name know to NGT utilities.

User response: Correct the error and resubmit the utility.

NGTR126

//string-1 PARMS - WARNING - DATA AFTER ')' IS IGNORED - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is: +PARM(value). There is additional data following the ) symbol. It is ignored.

User response: Correct the error and resubmit the utility.

NGTR127

//string-1 PARMS - THIS FILE MAY NOT CONTAIN THIS PARM - string-2.


Explanation: Certain parameters are valid only in RRGPARMS (NGT Reorg table space parameters) while some others are valid only in RRGPARMX (NGT Reorg index parameters).

User response: Remove the named parameter.

NGTR128

//string-1 PARMS - WARNING - PARM IS REPEATED - LATEST USE WINS - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. A parameter is repeated. The final occurrence is the value used.

User response: Remove duplicates of the named parameter from the //string-1 file.

NGTR129

//string-1 PARMS - VALUE IS NOT ONE OF THE REQUIRED VALUES - string-2.


Explanation: For string-1, see message NGTR120. This parameter requires one of a specific set of values (such as YES or NO). The value specified is not one of the values allowed.

User response: Correct the value and resubmit the utility.

NGTR130

//string-1 PARMS - NUMERIC VALUE CANNOT BE MORE THAN 15 DIGITS - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is +PARM(value). Numeric values can be at most 15 digits long, and the value must not exceed the maximum for a fullword number (for example, 2,147,483,647).

User response: Correct the value and resubmit the utility.

NGTR131

//string-1 PARMS - VALUE MUST BE NUMERIC BUT CONTAINS A NON-DIGIT - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is +PARM(value). This parameter accepts numeric values, but the value specified does not contain only digits.

User response: Correct the value and resubmit the utility.

NGTR132

//string-1 PARMS VALUE (number-1) IS ABOVE MAX (number-2) FOR PARM - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is +PARM(value). The value specified for this parameter (number-1) exceeds the predefined maximum (number-2) for values of this parameter.

User response: Correct the value. Specify a value no greater than number-2, and resubmit the utility.

NGTR133

//string-1 PARMS VALUE (number-1) IS BELOW MIN (number-2) FOR PARM - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is +PARM(value). The value specified for this parameter (number-1) is less than the predefined minimum for values of this parameter.

User response: Correct the value. Specify a value no less than number-2, and resubmit the utility.

NGTR134

//string-1 PARMS number-1 BYTE STRING EXCEEDS MAX OF number-2 BYTES - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is +PARM(value). This parameter accepts character string values whose length must not exceed number-2. The value string specified has length number-1.

User response: Shorten the string and resubmit the utility.

NGTR135

//string-1 PARMS - FIRST VALUE MUST BE 6 CHARS (MMSSTH), MM<60, SS<60, string-2.


Explanation: For string-1, see message NGTR120. The first value of the +DSCRL parameter must be a time in the format MMSSTH (six characters).

User response: Correct the value and resubmit the utility.

NGTR136

+RENAME(YES) AND NON-NULL PREFIX ARE INCOMPATIBLE.


Explanation: Use of +PREFIX is intended for testing only. Recovery and restartability are affected by use of +PREFIX, so it cannot be used in conjunction with +RENAME(YES).

User response: Either specify +RENAME(NO), or do not use +PREFIX.

NGTR137

//string-1 PARMS NUMERIC VALUE EXCEEDS 64G, TOO BIG FOR PARM - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is +PARM(value). A numeric value can be at most 15 digits long, and the value must not exceed the maximum for a fullword number.

User response: Correct the error and resubmit the utility.

NGTR138

RUN ABORTED BEFORE ANY UTILITIES STARTED.


Explanation: This message follows one or more error messages that describe why this run is aborted. This message indicates that utility restart or recovery will be unnecessary because no utilities were actually started.

User response: Correct any conditions that caused the errors and resubmit the utility.

NGTR139

+ALLO(REUSE) CONFLICTS WITH +MODE(24X7)


Explanation: +ALLO(REUSE) specifies overwriting the original data set. +MODE(24X7) specifies the creation of a 'B' copy in order that the table space is available during Reorg. These two are incompatible.

User response: Use +ALLO(USED|ALLO|DB2). Alternatively, add the +TAPEDD(ddname) parameter, and also supply a //ddname DD statement in the JCL.

NGTR141

+TAPEDD(string-1) REQUIRES A //string-2 DD STATEMENT. IT IS MISSING.


Explanation: When you use the +TAPEDD(ddname) parameter, you must supply a //ddname DD statement in the JCL.

User response: Either do not use +TAPEDD, or add the DD statement to the JCL. This may be issued if you have used +TAPEDD as a default installation option. If so, see +TAPEDD in the Reorg Reference.

NGTR142

+COPY(NO) NOT ALLOWED. PLEASE SEE INSTALLER FOR INFORMATION.


Explanation: See the installer.

User response: No action is required.

NGTR143

+TAPEDD(string-1) FOR TS IS SAME AS +TAPEDD FOR INDEX. CHANGE ONE.


Explanation: The DDname named in the +TAPEDD parameter is the same in both RRGPARMS and RRGPARMX. They must be different.

User response: Change one of the parameters and resubmit the Utility.

NGTR144

PLAN NAME REQUIRED BUT NOT SPECIFIED IN PARMS OR INSTALL.


Explanation: A plan name is required for proper execution of NGT utilities The plan name can be specified on the +PLAN parameter in //UTLPARMS.

User response: Supply the +PLAN(planName) parameter.

NGTR145

ERROR CONNECTING TO DB2=string-1 WITH NGT PLAN string-2.


Explanation: String-1 is the DB2 ID and string-2 is the plan name used for the Call-Attach connect attempt. The attempt failed.

User response: Check that the DB2 ID and plan name are valid and that the plan exists. Check for any other messages issued immediately previous to this one that might describe the problem. Processing continues based on the value of the +DB2DOWN parameter. Reason codes 00F3xxxx can be found in the DB2 Messages and Codes. Other return codes and reason codes are described in the DB2 Application Programming and SQL Guide (find CAF in the Index).

NGTR147

DB2 VERSIONS PRIOR TO VERSION 7 ARE NOT SUPPORTED IN THIS RELEASE.


Explanation: This release of the NGT utilities does not support versions of DB2 earlier than Version 7. NGT/Utilities V740 supports earlier versions.

User response: The utility job will fail.

NGTR148

PARMS SPECIFIED IN //string-1 DD ARE:


Explanation: For string-1, see message NGTR120.

User response: This message precedes a listing of the parameters in the named file.

NGTR149

NO //string-1 DD STATEMENT - DEFAULT PARMS USED.


Explanation: For string-1, see message NGTR120. This DD statement was not supplied, and so default values are used for these parameters.

User response: If you do not want to use the default values, then supply a DD statement specifying a file containing your parameter overrides.

NGTR150

NO '+' STATEMENTS IN //string-1 DD - DEFAULT PARMS USED.


Explanation: For string-1, see message NGTR120. This file contains no statements beginning with the + symbol. Therefore, no parameter values were recognized and all the defaults are used.

User response: If you do not want to use the default values, then supply parameter overrides in the named DD statement.

NGTR151

//DDName PARMS - ENDING QUOTE MISSING FROM PARAMETER parameterName


Explanation: The value for the indicated parameter has a beginning quotation mark but is missing an ending quotation mark. The utility terminates.

User response: Add the ending quotation mark, or, if appropriate, remove the beginning quotation mark. Rerun the utility.

NGTR152

//string-1 DD INPUT DATA EXCEEDS MAX OF number-1 BYTES.


Explanation: For string-1, see message NGTR120. The data in this file exceeds the maximum size allowed. The maximum value currently allowed is 256K bytes.

User response: Remove some input and resubmit the utility.

NGTR153

UNRECOGNIZED DATA IN //string-1 DD - string-2 IS NOT A '+' STMT.


Explanation: For string-1, see message NGTR120. This file contains a statement beginning with some character other than +. Only comments and + statements are allowed.

User response: Correct the error and resubmit the utility.

NGTR154

INVALID PARM IN //string-1 DD - string-2 PARM IS TOO LONG.


Explanation: For string-1, see message NGTR120. This file contains a single statement that exceeds 256 characters.

User response: Correct the error and resubmit the utility.

NGTR155

DB2 string-1 UID 'string-2' ORIGINAL JOB string-3.string-4 string-5.


Explanation: This message says that the uid is being restarted. The original job using this uid is string-2.

User response: No action is required.

NGTR156

UTILITY TASK TERMINATING - ABEND HAS OCCURRED.


Explanation: One or more errors have occurred processing the current table space or index. +ONERROR(STOP|ABEND) is in effect, so NGT utilities are terminating.

User response: Once the condition causing the problem has been corrected, simply resubmit the job. NGT utilities will automatically restart at the nearest valid point.

NGTR157

CDBUTIL "SYSPRINT" DD STATEMENT IS MISSING.


Explanation: The SYSPRINT DD statement is required and must be provided in order to run NGT utilities Additional print file DD statements are optional, including SYSERROR, SUMMARY and RUNSTATS.

User response: Supply a //SYSPRINT DD statement in the JCL.

NGTR158

SYSTEM PDS ERROR - string-1.


Explanation: Some error has occurred processing the PDS that contains the restart and control information. This information is critical to NGT utilities The text of the message should describe the nature of the problem.

User response: If the corrective action is not obvious from the diagnostic messages, contact BMC Customer Support.

NGTR159

DUPLICATE UID string-1 JOB string-2.string-3 string-4 AT string-5 string-6 LOGICALLY DELETED.


Explanation: A duplicate Utility-ID entry was found in the Utility table. This older UID entry will be marked as logically deleted.

User response: No action is required.

NGTR160

UNEXPECTED END OF FILE ON FUNCTION LIST MEMBER string-1 IN SYSTEM PDS.


Explanation: The Function-List member string-1 appears corrupted. This symptom can occur if you fall back to a prior level of NGT/SuperUtilities.

User response: Rerun the utility with PARM='db2-id,utility-id,NORESTART'. If this is unsuccessful, try to terminate the utility via NGT/SuperUtilities Interactive (NGTUTILI); if the utility terminates, rerun it a second time. If this, too, is unsuccessful, then contact BMC Customer Support.

NGTR161

RESTART OPTION 'QUICKEXIT' INAPPROPRIATE FOR UID 'utilityID' -- RUN ABORTED.


Explanation: utilityID is the utility ID (UID) specified as the second value in the PARM field on the EXEC statement. If you do not specify a utility ID, the utility uses the jobname.

This message is a response to the specification of PARM='dbid,uid,QUICKEXIT' on the EXEC statement. The utility identified by utilityID is not in a state where QUICKEXIT is appropriate.

User response: If you coded QUICKEXIT just to be sure the utility was not processing, then this is not an error. Otherwise, investigate the circumstances that instigated the use of QUICKEXIT. Contact BMC Customer Support if there is some inconsistency.

NGTR162

RESTART OPTION 'FORCEID' INAPPROPRIATE FOR UID 'utilityID'.


Explanation: utilityID is the utility ID (UID) specified as the second value in the PARM field on the EXEC statement. If you do not specify a utility ID, the utility uses the jobname.

This message is a response to the specification of PARM='dbid,uid,FORCEID' on the EXEC statement. The utility identified by utilityID was not found and a FORCEID is not appropriate.

User response: No action is required.

NGTR163

OBJECT LIST INCONSISTENCY - MEMBER 'string-1' IS DAMAGED.


Explanation: String-1 names the PDS member assigned as function list member for this Utility-ID. End-of-file was reached before the expected end of the data, indicating physical damage to the member.

User response: Use either NGT utilities Interactive (Review Restart Data) or PDF Browse to inspect the object list member, and print its contents. Have this available when you call BMC Software Support for assistance. You will have to use a new UID to run the utility until the problem is corrected.

NGTR164

UID 'string-1' NOT FOUND, NORMAL START IN PROGRESS.


Explanation: String-1 is the Utility-ID specified as the second value in the EXEC statement PARM field. If none is provided, the jobname is used. No current or interrupted execution of this UID is in progress, so the utility proceeds normally.

User response: No action required.

NGTR165

DB2 string-1 UID 'string-2' FOUND, FROM JOB string-3.string-4 string-5 AT string-6 AT string-7 .


Explanation: This message specifies the details of the Utility found from a previous job.

  • String-1 is the subsystem that is the source of the Utility ID.
  • String-2 is the Utility ID found.
  • String-3 and String-4 are the job name.
  • String-5 is the job number.
  • String-6 is the date.
  • String-7 is the time.

User response: No action is required.

NGTR166

UID 'string-1' - 'NORESTART' REQUESTED BUT DATABASE DAMAGE MAY RESULT.


Explanation: String-1 is the Utility-ID specified as the second value in the EXEC statement PARM field. If none is provided, the jobname is used. The restart parameter is NORESTART. However, the previous execution of this UID terminated in such a way that QUICKEXIT or RESTART is required to preserve data integrity.

User response: The utility terminates. Either use RESTART or QUICKEXIT or terminate the utility using NGTUTILI.

NGTR167

UID 'string-1' - OPERATOR CANCELLED 'NORESTART'.


Explanation: String-1 is the Utility-ID specified as the second value in the EXEC statement PARM field. If none is provided, the jobname is used. In response to message NGTR171 issued to verify NORESTART, the operator replied CANCEL. The utility is cancelled.

User response: The job should be resubmitted with RESTART or QUICKEXIT as the restart parameter.

NGTR168

UID 'string-1' WAS NOT RESTARTED BECAUSE 'PARM=NORESTART'.


Explanation: String-1 is the Utility-ID specified as the second value in the EXEC statement PARM field. If none is provided, the jobname is used. Either the UID did not require restart or the operator replied correctly to message NGTR171. The utility starts as if no prior execution had been processing.

User response: No action required.

NGTR169

UID 'string-1' IS NOT RECORDED, BUT IS IN USE BY ANOTHER JOB - RUN ABORTED.


Explanation: String-1 is the Utility-ID specified as the second value in the EXEC statement PARM field. If none is provided, the jobname is used. No entry exists in the control member for this UID but 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.

NGTR170

UID 'string-1' FOUND, JOB IS STILL RUNNING - THIS RUN ABORTED.


Explanation: String-1 is the Utility-ID specified as the second value in the EXEC statement PARM field. If none is provided, the jobname is used. Another job with the same UID is active, as indicated by the return code from the system-wide enqueue issued.

User response: Check on the uniqueness of your UID. Check on existing system enqueues using a system monitor product. If you can find no duplicate UID, contact BMC Customer Support.

NGTR171

NGT 'NORESTART' MAY CAUSE DATABASE DAMAGE - CALL DBA OR REPLY 'CANCEL'.


Explanation: Following message NGTR166, this message is issued to prevent unintentional damage to your data as a result of inadvertent NORESTART processing.

User response: Valid responses are CANCEL to cancel the job, and password, where password is the current valid password for the particular utility. The password is not readily available to the operator, so NORESTART cannot proceed by accident.

NGTR172

NGT - REPLY UNACCEPTABLE.


Explanation: This message is issued if the operator's response to message NGTR171 is neither a valid password nor 'CANCEL'. Message NGTR171 is reissued.

User response: See message NGTR171.

NGTR173

ERROR PROCESSING RENAME MEMBER.


Explanation: An internal inconsistency exists in a Rename member of the System PDS. It appears the Rename member has been modified.

User response: RECOVERY IS CRITICAL. Use either NGT utilities Interactive (Review Restart Data) or PDF Browse to inspect the control member, and print its contents. Have this available when you contact BMC Customer Support.

NGTR174

RESTART TYPE CONFLICTS WITH PREVIOUS RESTART.


Explanation: A restart is being processed on a Rename member. The type of restart specified in the EXEC statement PARM is not the same as that previously used when the Rename member was saved.

User response: This is a warning message. The current restart type is set to that in effect when the Rename member was saved.

NGTR175

DEFINING NEW string-1 DATASET - 'string-2'


Explanation: A new VSAM data set is being defined. String-1 is either 'TABLE' or 'INDEX', indicating the type of data set being created.

User response: No action is required.

NGTR176

DSNAME 'string-1' IS NOT UNIQUE WITHIN THIS JOB - RUN ABORTED.


Explanation: The data set name shown in string-1 is used for either SYSUT1 or a TAPEDD, but the same name is used for multiple DD statements within this step.

User response: Each DD statement must reference a different data set name. Correct the JCL and resubmit the job.

NGTR177

DSN 'string-1' IS USED IN 'string-2' - RUN ABORTED.


Explanation: The data set name shown in string-1 is used for either SYSUT1 or a TAPEDD, but the same name is used by another utility that is still active (that is, has yet to terminate successfully). String-2 names the uid that has the data set.

User response: No utility can use a SYSUT1 or TAPEDD in use by another utility. Use NGT utilities Interactive. to investigate the active utility. You must correct the JCL and use unique data set names.

NGTR178

MODULE 'string-1' SPECIFIED IN +ALLOTYPE COULD NOT BE LOADED - RUN ABORTED.


Explanation: The +ALLOTYPE parameter specified the module name string-1, but the system LOAD for this module failed. The Utility run is aborted.

User response: Check the system messages for MVS messages concerning the LOAD; the message prefix is usually 'CSV'. The module must exist in STEPLIB or in a Link-List library. Either correct the name specified in +ALLOTYPE or copy the module to STEPLIB, then rerun.

NGTR179

//string-1 PARMS - NOTE - PARAMETER IS IGNORED - string-2.


Explanation: The named parameter is either obsolete or is not proper in this particular file. It is ignored.

User response: You can remove the parameter. It will have no effect on processing.

NGTR180

NOTE - +RUNSTATS(YES) CHANGED TO +RUNSTATS(NO) BECAUSE +RENAME(NO).


Explanation: +RENAME(NO) specifies your intention that this is a test run. +RUNSTATS(YES) specifies to update the DB2 Catalog statistics. +RUNSTATS is changed to (NO) for this run.

User response: No action is required.

NGTR181

+ALLO(REUSE) REQUIRES +RENAME(YES).


Explanation: +ALLO(REUSE) implies overwriting the original data set. +RENAME(NO) specifies your intention not to replace the original data sets. These are in conflict.

User response: Use either +ALLO(USED|ALLO|DB2) or +RENAME(YES) .

NGTR182

UID 'string-1' - 'NORESTART' REQUESTED BUT RENAME MEMBER EXISTS . RESTART OR QUICKEXIT


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 restart parameter is NORESTART. However, the previous execution of this uid terminated in such a way that QUICKEXIT or RESTART is required to preserve data integrity.

User response: The utility terminates. Either use RESTART or QUICKEXIT or terminate the utility using NGTUTILI.

NGTR183

//string-1 PARMS number-1 BYTE STRING LESS THAN MIN OF number-2 BYTES - string-2.


Explanation: For string-1, see message NGTR120. String-2 is the first 16 bytes of the input parameter. The format for parameters is +PARM(value). This parameter accepts character string values whose length must be less than number-2. The value string specified has length number-1.

User response: Increase the length of the string and resubmit the utility.

NGTR184

UID string-1 HAS BEEN REMOVED FROM CONTROL MEMBER.


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 uid has completed and has been removed from the NGT control member.

User response: No action required.

NGTR187

+TAPEDD IS NOT SUPPORTED IN THIS RELEASE.


Explanation: +TAPEDD was specified in the parms input. +TAPEDD and +MODE(WORKCOPY) are no longer supported.

User response: Remove the +TAPEDD or use a prior release.

NGTR189

THE PART VALUE OF 'string-1' IS INVALID.


Explanation: The value supplied for the PART keyword is not a valid partition number. Partition numbers must be between 1 and 64, inclusive.

User response: Correct your input and rerun.

NGTR190

THE SORTNUM VALUE OF 'string-1' IS INVALID.


Explanation: The value supplied for the SORTNUM keyword is not a valid number.

User response: Correct your input and rerun.

NGTR191

A VALID KEYWORD NOT FOUND AFTER 'REORG'. 'string-1' IS INVALID.


Explanation: The only valid keywords after REORG are either TABLESPACE or INDEX .

User response: Correct your input and rerun.

NGTR192

THE OBJECT NAME 'string-1' DOES NOT CONFORM TO DB2 RULES.


Explanation: String-1 should be either a data base name or table space name, but it does not conform to the naming conventions for DB2 short identifiers.

User response: Correct the object name and rerun.

NGTR193

INVALID KEYWORD 'string-1'.


Explanation: The keyword named in string-1 is invalid for REORG.

User response: Correct the statement and rerun.

NGTR194

INVALID PARAMETER 'string-1' FOR KEYWORD 'string-2'.


Explanation: The parameter named in string-1 is invalid for the keyword named in string-2.

User response: Correct the statement and rerun. Refer to the syntax diagrams in the DB2 documentation for valid keyword parameters.

NGTR195

THE KEYWORD 'string-1' WAS SPECIFIED MORE THAN ONCE.


Explanation: The text string in string-1 is a keyword that has been previously specified in the same statement.

User response: Correct the text and rerun.

NGTR196

UNABLE TO ALLOCATE CDBPRINT.


Explanation: An attempt to clone the existing allocation of the SYSPRINT DD statement to the DDname 'CDBPRINT' has failed. This problem can be circumvented by adding a DD statement for 'CDBPRINT' to the JCL, and rerunning the job.

User response: Please report this problem to BMC Customer Support so that it can be corrected and the circumvention rendered unnecessary.

NGTR197

UTILITY NOT COMPLETE, SYSCOPY POST IS PENDING.


Explanation: After all utility statements were processed, it was determined that one or more functions were not posted to the DB2 Catalog table SYSIBM.SYSCOPY: either the DB2 subsystem was inactive, or NGT/SuperUtilities were not running from an APF-authorized library. The return code will be 4.

User response: Refer to the description of the +DB2DOWN parameter for more information on the effect of restarting the utility with a SYSCOPY pending condition.

NGTR198

UTILITY CAN ONLY BE RESTARTED/TERMINATED BY PROGRAM 'CDBUTIL'


Explanation: The utility has detected the presence of incomplete data left by a prior execution of program 'NGTUTIL'. The current executing program name is not 'NGTUTIL' and it is not capable of carrying out the restart process.

User response: Change the program name on the EXEC statement to that of 'NGTUTIL' and rerun the job.

NGTR199

UTILITY NOT COMPLETE, RESTART IS PENDING


Explanation: The utility has stopped execution due to a 'STOP' return code generated by the REXX exit 'XSUTFUNC'. The utility can be restarted or terminated at a later time. The minimum return code will be 6.

User response: Information only - no action is required.

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

Comments