Messages NGTL000 through NGTL099

This topic contains messages for the BMC AMI Utilities products. 
NumberDescription
NGTL000

diagnosticText.


Explanation : This message is a diagnostic message for use by BMC Support.

User response : No action is required.

NGTL001

NO MEMORY FOR workArea, size BYTES.


Explanation : The product attempted to allocate a work area and received an error that there was not enough memory available.

User response : Check and adjust job and system restraints that would prevent the allocation of an area the size specified in the message.

NGTL002

LOB FILE REFERENCE IS NOT SUPPORTED.


Explanation : BMC AMI Load does not currently support the loading of LOBs. BMC AMI Load calls DSNUTILB to load the LOB.

User response : No action is required.

NGTL003

LOAD PROCESSING HALTED. DISCARD DD (string-1) NOT FOUND


Explanation : BMC AMI Load did not find the DD for the allocated discard data set.

User response : Add the DD for the discard data set to the LOAD job and restart the utility.

NGTL010

EMPTY DISCARD DATA SET DELETED - DSN=dataSetName


Explanation : You specified SYSDISC YES for the DELETEFILES option or +DELETEDISCARD (YES) parameter. BMC AMI Load deleted the empty discard data set after successfully completing the load process.

User response : No action is required.

NGTL011

DB2-DEFINED REFERENTIAL CONSTRAINTS ARE NOT SUPPORTED – REFERENTIAL CONSTRAINTS IGNORED


Explanation : BMC AMI Load does not currently support referential integrity (RI) constraints.

User response : No action is required.

NGTL012

WARNING: DB2-DEFINED REFERENTIAL CONSTRAINTS ARE NOT SUPPORTED – REFERENTIAL CONSTRAINTS IGNORED


Explanation : BMC AMI Load does not currently support referential integrity (RI) constraints however, the utility continues load processing.

User response : You can review the ENFORCE parameter to determine if the keyword values need to be changed. Otherwise, no action is required.

NGTL013

ERROR: DB2-DEFINED REFERENTIAL CONSTRAINTS ARE NOT SUPPORTED – LOAD FAILED


Explanation : BMC AMI Load does not currently support referential integrity (RI) constraints. BMC AMI Load was configured to fail load processing when the ENFORCE option keywords specify (or default to) applying DB2-defined or informational referential constraints .

User response : Review the ENFORCE option if you want to change the keywords to not enforce referential constraints. Review the +ENFORCERI parameter if you want to change the action taken by BMC AMI Load when the ENFORCE option keywords specify (or default to) applying referential constraints.

NGTL014

ROWFORMAT BRF IS NOT ALLOWED ON TABLESPACE databaseName.tableSpaceName. REQUEST IGNORED.


Explanation : The ROWFORMAT BRF keyword specification is deprecated. The conversion to BRF is no longer supported. This request is ignored.

User response To avoid receiving this warning message in the utility execution, remove the ROWFORMAT BRF specification on the SYSIN statement. Consider specifying ROWFORMAT RRF to convert the object to reordered row format.

NGTL023

OPEN FAILED ON - dataSetName.


Explanation : This message names the data set for which open has failed.

User response : Check for any system messages that might explain the problem. Contact BMC Support for assistance.

NGTL030

CONVERSION OF columnName FROM inputType to columnType IS NOT SUPPORTED.


Explanation: The utility does not support the conversion of columnName from inputType to columnType during a load.

User response: Correct the specified input type or the defined column type and rerun the job.

NGTL036

RECORD logicalRowNumber OMITTED DUE TO WHEN PROCESSING.


Explanation : BMC AMI Load did not load the indicated row because it did not satisfy the WHEN clause condition.

User response : No action is required.

NGTL037

START OF TABLESPACE SCAN FOR SYSFIELDS.


Explanation : BMC AMI Load is processing a SELECT statement.

User response : No action is required.

NGTL038

END OF TABLESPACE SCAN FOR SYSFIELDS.


Explanation : BMC AMI Load finished processing the SELECT statement.

User response : No action is required.

NGTL047

STARTING DISCARD PHASE.


Explanation : The discard phase has started. BMC AMI Load copies discard rows to the discard data set.

User response : No action is required.

NGTL048

DISCARD PHASE COMPLETE.


Explanation : The discard phase finished.

User response : No action is required.

NGTL055

MULTIPLE 'INTO (FROM) TABLE' CLAUSES ARE NOT SUPPORTED.


Explanation : Either your LOAD statement contains multiple INTO TABLE clauses, or your UNLD statement contains multiple FROM TABLE clauses. The utilities do not support these multiple clauses.

User response : Separate each clause into its own utility statement and rerun the job.

NGTL057

ROW number-1 FAILED CONSTRAINT CHECK(S) FOR TABLESPACE tableSpaceName


Explanation : After building the indicated row, constraints checking failed. If discarding is active, BMC AMI Load discards the row; otherwise, the job terminates.

User response : Complete one of the following actions and rerun the job:

  • Fix the input data.
  • Remove the data from the input file.
  • Change the constraint to include the data that you are loading.
NGTL058

CHECK CONSTRAINT CHECKING IS ACTIVE WITH numberOfConstraints CONSTRAINTS.


Explanation : BMC AMI Load has found numberOfConstraints check constraints defined on the object being loaded. BMC AMI Load will perform constraint checking for this object.

User response : No action is required.

NGTL059

ROW rowNumber FAILED CONSTRAINT CHECK(S).


Explanation : After building the indicated row, constraints checking failed. If discarding is active, BMC AMI Load will discard the row; otherwise, the load terminates.

User response : Complete one of the following actions and rerun the load job:

  • Fix the input data.

  • Remove the data from the input file.

  • Change the constraint to include the data that you are loading.

NGTL071

DSP TOO LARGE. REQUESTED IS sizeNeeded, MAX IS maximumSize.


Explanation : The size of the data space needed to contain all the data is larger than the maximum allowed.

User response : Verify that the +FILESZ parameter is valid. Consider using sequential files if your data exceeds the in-storage limit.

NGTL073

UNKNOWN INIT PARAMETER 'parameterName'.


Explanation : The indicated initialization parameter is not a valid value. The utility cannot continue. Most likely this is an internal logic error.

User response : Contact BMC Support for assistance.

NGTL079

KEYWORD 'FORMAT' AND FIELD SPEC IS INVALID.


Explanation : The utility syntax statement contained both the FORMAT keyword and a field specification clause. The utility does not support specifying both in a single job step.

User response : Correct the LOAD or UNLD statement and restart the utility.

NGTL083

FIELD PROC fieldprocName COL 'columnName' R15=value, RETURN CODE=returnCode, REASON=reasonCode.


Explanation : A non-zero return code was returned from the indicated fieldproc for the indicated column. In some cases, NGTL084 provides additional information.

User response : Consult the supplier of the fieldproc for information about the return codes and reason codes. If you or the fieldproc supplier are able to determine the problem, correct it and rerun the job. If you need assistance, contact BMC Support.

NGTL084

FIELD PROC fieldprocName ERROR TEXT IS 'error'.


Explanation : This is the error text, if any, that the indicated fieldproc returns. Message NGTL083 provides additional information.

User response : If you or the fieldproc supplier are able to determine the problem, correct it and rerun the job. If you need assistance, contact BMC Support.

NGTL088

SYSREC DD ddname IS NOT ALLOCATED


Explanation : The DD name specified as the input data set does not exist.

User response : Either allocate the data set or correct the DD name.

NGTL099

The text of this message varies depending on the Syntax error LOAD encounters.


Explanation : LOAD has encountered an error with the LOAD statement provided. An inconsistency exists with keywords specified on the LOAD statement.

Examples of the message text you might see for this error are:

  • COPYLVL FULL NOT SUPPORTED.
  • "BLOB" REQUIRES 'SHRLEVEL CHANGE'.
  • "CLOB" REQUIRES 'SHRLEVEL CHANGE'.
  • "DBCLOB" REQUIRES 'SHRLEVEL CHANGE'.
  • LOADING LOBS REQUIRES RESUME YES SHRLEVEL CHANGE WITHOUT REPLACE.
  • SQL INSERT MODE IS INCOMPATIBLE WITH REUSE SPECIFICATION.
  • SQL INSERT MODE IS INCOMPATIBLE WITH LOG NO SPECIFICATION.
  • SQL INSERT MODE IS INCOMPATIBLE WITH PREFORMAT SPECIFICATION.
  • SQL INSERT MODE IS INCOMPATIBLE WITH ENFORCE NO SPECIFICATION.
  • SQL INSERT MODE IS INCOMPATIBLE WITH COPYDDN SPECIFICATION.
  • SQL INSERT MODE IS INCOMPATIBLE WITH RECOVERYDDN SPECIFICATION.
  • SQL INSERT MODE IS INCOMPATIBLE WITH COPY YES SPECIFICATION.
  • SQL INSERT MODE IS INCOMPATIBLE WITH PREFORMAT SPECIFICATION.
  • RESUME AND REPLACE CAN NOT BE INTERMIXED.
  • COPY Specification is not allowed under LOAD REPLACE SHRLEVEL CHANGE.
  • PART NUMBER #2 EXCEEDS MAX #2.
  • INVALID PARTITION SPECIFICATION (PBG).
  • INVALID CENTURY($$$$,$$$$).

User response : Correct the LOAD statement and resubmit the utility.

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

Comments