Messages NGTU000 through NGTU099

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

diagnostic text.


Explanation: Verification Tracing and Diagnostic Purposes.

User response: No action is required.

NGTU001

THE CURRENT KEYWORD IS 'string-1'.


Explanation: The keyword currently being parsed is string-1.

User response: No action necessary--information only.

NGTU002

+PBGCHKDICT(NO) SET BECAUSE +PBGKEEPDICT(YES) HAS BEEN SPECIFIED.


 Explanation:   You cannot specify +PBGCHKDICT(YES) if you have specified +PBGKEEPDICT(YES). The NGT product has changed the +PBGCHKDICT parameter setting to NO.

 User response:  No action required.

NGTU004

DDNAME 'string-1' IS UNACCEPTABLE. LENGTH IS number-1.


Explanation: String-1 is unacceptable as a DDname. At least one of the following conditions does not hold: the DDname must be one through eight characters long; the first character must be alphabetic or National; all other characters must be alphanumeric.

User response: Correct the DDname and rerun the utility.

NGTU010

ELEMENT MISSING IN COMMA-DELIMITED CLAUSE.


Explanation: The clause currently being parsed is comma-delimited: that is, the elements within the clause are to be separated from each other by commas. This clause contains a null or empty element. The reason is one of the following:

  • Either two consecutive commas, with or without intervening blanks (that is, ',' or ', ,')

  • An open parenthesis followed by a comma (that is, '(,')

  • A close parenthesis preceded by a comma (that is, ',)')

User response: Correct the coding of the utility or SQL statement and rerun the utility.

NGTU011

CONTROL STATEMENT SYNTAX ERROR:


Explanation: The current utility statement, string-1, contains a syntax error. That is, the statement violates the format defined in the DB2 Command and Utility Reference. The nature of this error is structural; errors contextual in nature (for example, a keyword missing its value) are checked after this level of checking is completed. The following syntax errors are checked:

  • NO CLAUSE FOUND IN INPUT STREAM—No words are recognizable

  • UNBALANCED PARENTHESES—Hit a ')' with no matching '('

  • UNMATCHED STRING DELIMITER—Either a quote or apostrophe is not paired

User response: Correct the control statement and rerun the utility.

NGTU012

UTILITY ID 'string-1' IN USE BY DB2=string-2, UNAVAILABLE TO DB2=string-3.


Explanation: This utility with UID string-1 was submitted for DB2 subsystem string-2. A different DB2 subsystem, whose id is string-3 ,owns an identically-named utility which either (a) is active or (b) has failed and is awaiting restart.

User response: Check the DB2 id; if it is wrong, correct it before resubmitting. If it is correct, change the UID.

NGTU013

number-1 RECORDS WRITTEN TO //string-1.


Explanation: Number-1 is the number of records written to the output dd named //string-1.

User response: Informational only--no action required.

NGTU014

MISSING OBJECT NAME FOLLOWING CREATOR 'string-1'.


Explanation: When parsing a CREATOR-ID.OBJECT-NAME, the OBJECT-NAME was found to be missing. The CREATOR-ID parsed is string-1.

User response: Change the utility or SQL statement in error to complete or correct the syntax.

NGTU015

CREATOR-ID STARTING WITH 'string-1' IS TOO LONG. LENGTH IS number-1.


Explanation: The DB2 object CREATOR-ID, starting with the characters string-1, is too long. The maximum length of a CREATOR-ID is eight (8) characters. The length determined is number-1.

User response: Correct the utility statement or SQL statement and rerun.

NGTU016

CREATOR-ID SUPPLIED IS INVALID. LENGTH IS number-1.


Explanation: The DB2 object CREATOR-ID has been determined to have the invalid length number-1. The most probable cause is that CREATOR-ID was specified as '' (i.e., a null value).

User response: Correct the utility statement or SQL statement and rerun.

NGTU017

OBJECT NAME STARTING WITH 'string-1' IS TOO LONG.


Explanation: A DB2 object name need not be qualified. You may specify either objectName or creator.objectName. The length of the objectname part of the name, shown as string-1, may not exceed 18 characters.

User response: Correct the utility or SQL statement and rerun.

NGTU018

OBJECT NAME SUPPLIED IS INVALID. LENGTH IS number-1.


Explanation: The DB2 object name has been determined to have the invalid length number-1. The most probable cause is that the object name was specified as '' (i.e., a null value).

User response: Correct the utility statement or SQL statement and rerun.

NGTU019

OBJECT NAME STARTING WITH 'string-1' IS TOO LONG.


Explanation: A DB2 space name need not be qualified. You may specify either spaceName or database.spaceName. The length of the spacename part of the name, shown as string-1, may not exceed eight (8) characters.

User response: Correct the utility or SQL statement and rerun.

NGTU020

THE NAME 'string-1' CONTAINS INVALID CHARACTERS.


Explanation: The DB2 object name string-1 is invalid. Either its first character is invalid, or non-alphanumeric or national characters occur in the remainder of the name.

User response: Correct the utility or SQL statement and rerun. Use delimiters if necessary.

NGTU021

DATABASE NAME STARTING WITH 'string-1' IS TOO LONG. LENGTH IS number-1.


Explanation: The DB2 database name, starting with the characters shown in string-1, is too long. The maximum length of a database name is eight (8) characters. The length determined is number-1.

User response: Correct the utility statement or SQL statement and rerun.

NGTU022

DATABASE NAME SUPPLIED IS INVALID. LENGTH IS number-1.


Explanation: The DB2 database name has been determined to have the invalid length number-1.

User response: Correct the utility statement or SQL statement and rerun.

NGTU023

DATABASE NAME OR SPACE NAME MUST NOT BE DELIMITED. NAME IS --> string-1 <--.


Explanation: The name of a DB2 data base, table space or index space name must not be delimited. The incorrectly delimited name is shown as string-1 between two arrows.

User response: Correct the utility statement or SQL statement and rerun.

NGTU024

THE NAME 'objectName' CONTAINS INVALID CHARACTERS.


Explanation: The indicated DB2 database name or creator ID is invalid. Either its first character is non-alphanumeric, or it contains non-alphanumeric or national characters in the remainder of the name.

User response: Correct the utility or SQL statement and rerun. Use delimiters if necessary.

NGTU025

RETURN CODE FROM SORT WAS returnCode.


Explanation: The SORT program returned a non-zero return code. Processing could not continue.

User response: Analyze the SYSOUT output for messages that might indicate why a failure occurred. Correct the error and retry the utility. If you cannot determine the failure or the corrective action, contact BMC Customer Support for assistance.

NGTU026

versionAndMaintenanceInformation


Explanation: The utility issues this message during product initialization. The message displays the following information:

  • Product name and version number

  • PTFs applied to your system for that product

  • The same information for components of that product, for example, the BMC DB2 Solution Common Code component (SCC)

User response: No action is required. However, if you encounter a problem with the product, be prepared to provide this information to BMC Customer Support to assist with problem analysis.

NGTU027

WRITE ERROR DD=DDname, CC=completionCode, CSW=channelStatusWord, SENSE=sense.


Explanation: A write error occurred while writing to the data set represented by the indicated DD. The message provides the I/O completion code and remaining information in hexadecimal format.

User response: If you do not find any relevant system messages on the job log, contact BMC Customer Support for assistance. This message is followed by an S001 abend and a dump to the log PDS.

NGTU028

//string-1 COMMENT NESTING ERROR, STILL AT LEVEL number-1.


Explanation: After parsing the string-1 input parameters, the nesting level for comments had not decremented to 0. The number of unmatched comment start delimiters is number-1.

User response: Correct the comments in your parameters file.

NGTU029

string-1 IS NOT AUTHORIZED.


Explanation: A license module with a valid password for the product string-1 could not be found.

User response: Add a BMC license module with a valid password for the product specified in string-1 and rerun the utility.

NGTU030

NO DEFAULT CNTL DATASET NAME.


Explanation: No CNTL data set was allocated during the configuration, so there is no default CNTL data set name.

User response: No action necessary--information only.

NGTU031

THE string-1 STATEMENT REQUIRES string-2.


Explanation: The utility statement being parsed, (string-1), is incomplete. Fewer than the minimum number of keywords were supplied. String-2 is required but not supplied.

User response: Complete the control statement and rerun the utility.

NGTU032

NAME 'string-1' IS UNACCEPTABLE. LENGTH IS number-1.


Explanation: String-1 is unacceptable as a Module name. It is too long or the module cannot be loaded.

User response: Correct the Name and rerun the utility.

NGTU033

DDNAME 'string-1' IS UNACCEPTABLE. IT DOES NOT EXIST.


Explanation: String-1 is a DDname, but it was not found in the JCL.

User response: Correct the JCL, supply the DDname and rerun the utility.

NGTU034

STRING 'string-1' IS TOO LONG. LENGTH IS number-1, MAX IS number-2.


Explanation: String-1 is longer than is allowed. Number-1 is the length of the string in the input command. Number-2 is the maximum length allowed.

User response: Correct the String and rerun the utility.

NGTU035

MODULE string-1 COULD NOT BE LOADED.


Explanation: A load module, string-1, needed for processing, perhaps an EDITPROC or DELETE EXIT, could not be found or loaded.

User response: If an EDITPROC, supply a //EDITPLIB DD statement with the JCL, naming the library containing the EDITPROC module. For either EDITPROC or DELETE EXIT, you can add the load library containing the load module to STEPLIB.

NGTU036

EDITPROC string-1 ERROR: R15=hexstring-1, RETURN CODE=hexstring-2, REASON CODE=hexstring-3.


Explanation: A table being processed (loaded or in a table space being reorganized) is defined with EDITPROC string-1. When called to compress or decompress a table row, the module returned X'hexstring-1' in R15. The Return code and Reason codes come from the DB2 exit parameter list passed to the module.

User response: If you have reason to suspect that the EDITPROC module is not the problem, contact BMC Customer Support.

NGTU037

NO STATEMENTS WERE READ FROM SYSIN.


Explanation: There must be at least one utility statement in the input file.

User response: Correct the input file and resubmit.

NGTU038

NO DB2 SUBSYSTEM ID.


Explanation: The DB2 subsystem has not been identified.

User response: If there is no DB2 subsystem ID, first set the DB2 subsystem ID, and then repeat. Otherwise contact BMC Customer Support.

NGTU039

UNACCEPTABLE DB2 SUBSYSTEM string-1.


Explanation: Acceptable DB2 subsystem IDs are from one through four characters in length. The value beginning string-1 is not.

User response: If the DB2 subsystem ID is too long, first correct it, and then repeat. Otherwise contact BMC Customer Support.

NGTU040

NGT HAVE NOT BEEN CONFIGURED FOR DB2 SUBSYSTEM string-1.


Explanation: NGT utilities have not been configured for DB2 subsystem string-1.

User response: Either configure NGT utilities for DB2 subsystem string-1, or correct the DB2 subsystem ID. Then repeat.

NGTU041

UNEXPECTED FORMAT IN CONFIGURATION DEFAULTS MODULE string-1.


Explanation: The configuration defaults module string-1 in which a permanent password was to be set has an unexpected format.

User response: Use IEBCOPY to copy the configuration defaults module string-1. Use the COPYMOD control statement rather than the COPY control statement. Specify MINBLK=4096.

NGTU042

COMPANY NAME OMITTED.


Explanation: While setting a permanent password, no company name was provided.

User response: Please contact BMC Customer Support.

NGTU043

COMPANY NAME EXCEEDS MAXIMUM LENGTH SUPPORTED:


Explanation: While setting a permanent password, a company name was encountered which exceeded the maximum length supported. The company name appears on the next line.

User response: Please contact BMC Customer Support.

NGTU044

PASSWORD(S) SET SUCCESSFULLY FOR DB2 SUBSYSTEM string-1.


Explanation: A password, either temporary or permanent, has been set for one or more NGT utilities for DB2 subsystem string-1.

User response: No action necessary--information only.

NGTU045

PASSWORD RESET FOR string-1 ON DB2 SUBSYSTEM string-2.


Explanation: The password for string-1 on DB2 subsystem string-2 has been reset. You will no longer be able to execute this utility function against this DB2 subsystem until NGT utilities are reconfigured.

User response: No action necessary--information only.

NGTU046

CONFIGURATION DEFAULTS DELETED FOR DB2 SUBSYSTEM string-1.


Explanation: The configuration defaults module for DB2 subsystem string-1 has been deleted. You will no longer be able to execute any utility function against this DB2 subsystem until NGT utilities are reconfigured.

User response: No action necessary--information only.

NGTU047

SORT BEGINNING FOR INDEX.


Explanation: The index being processed by this task is being reorganized using SORT.

User response: No action necessary--information only.

NGTU048

'PART ALL' AND 'PART N' CANNOT BOTH BE SPECIFIED.


Explanation: One statement specified PART ALL and another PART n. You must run these in separate steps.

User response: Correct the control statements and resubmit.

NGTU049

THE string-1 FUNCTION CANNOT BE RUN AGAINST THE DB2 CATALOG OR DIRECTORY.


Explanation: The named function is not valid on the DB2 Catalog (DSNDB06) or Directory (DSNDB01) table spaces.

User response: Correct the control statements and resubmit.

NGTU050

THE KEYWORD 'string-1' CONFLICTS WITH 'string-2'.


Explanation: String-1 is a keyword that conflicts with a previously specified keyword, string-2. Use one or the other, but not both.

User response: Correct the control statements and resubmit.

NGTU051

DSNAME ERROR 'string-1'.


Explanation: A data set name value is not acceptable. This message is issued first with the diagnostic in string-1, then again with the data set name.

User response: Correct the control statements and resubmit.

NGTU052

KEYWORD 'string-1' HAS AN IMPROPER VALUE SPECIFIED, 'string-2'.


Explanation: String-1 is a keyword and string-2 is its value. The value is improper: e.g., it should be numeric but is not.

User response: Correct the control statements and resubmit.

NGTU053

ERROR OPENING SPACE-SPECIFIC DEFINE DATASET.


Explanation: The open failed for the space-specific AMS DEFINEs data set identified in the following message NGTU056. The default AMS DEFINEs contained in member JCLRXMDL of the NGT/Utilities. System PDS are used instead.

User response: Follow the action suggested for messages which accompany this one.

NGTU054

SPACE-SPECIFIC-DEFINE DATASET MUST HAVE LRECL=80, RECFM=F(B).


Explanation: The data set containing space-specific AMS DEFINEs must have fixed-length 80-byte records; the data set identified in the following message NGTU056 does not. The default AMS DEFINEs contained in member JCLRXMDL of the NGT/Utilities. System PDS are used instead.

User response: Either omit the DD statement string-1 identified in message NGTU056, or copy the statements to a data set with fixed-length 80-byte records and use that data set instead.

NGTU055

SPACE-SPECIFIC DEFINES BEING PROCESSED.


Explanation: Instead of using the default AMS DEFINEs contained in member JCLRXMDL of the NGT/Utilities. System PDS, NGT utilities is using the data set identified in the following message NGTU056.

User response: No action necessary--information only.

NGTU056

DDN=string-1, DSN=string-2.


Explanation: This message identifies the data set referred to by the prior message NGTU053, NGTU054 or NGTU055. The DDname is string-1 and the data set name is string-2. If it is a member of a PDS, then its member name is shown as string-3.

User response: Take the action, if any, specified for the prior message NGTU053, NGTU054 or NGTU055.

NGTU057

DEFINE CLUSTER STATEMENT NOT FOUND string-1.


Explanation: No DEFINE CLUSTER statement for the current space was found in the data set identified by message NGTU056 (if string-1 appears, it gives the reason). The name of the space appears on the next line. Definition proceeds using the default AMS member of the NGT/Auto-Utilities System PDS, JCLRXMDL.

User response: If no such statement exists, then no action is necesary. If such a DEFINE CLUSTER statement does exist, then test its validity by copying all the records in the complete statement (that is, including comments and continuation lines) to a new data set and passing them to IDCAMS. If there is an IDCAMS error, then make the corrections in the original data set; otherwise, contact BMC Customer Support.

NGTU058

INSTALL ERROR. PROGRAM IS NOT APF-AUTHORIZED.


Explanation: NGT utilities must be installed in an APF-authorized system library.

User response: Install NGT utilities in an APF-authorized system library or authorize the current library.

NGTU059

INVALID SYNTAX, MISSING FIELD NAME, CLAUSE number-1.


Explanation: While parsing, a field or column name was expected by not found. The clause in error is Number-1.

User response: Correct the syntax and provide a valid field or column name.

NGTU060

OPERAND 2 OF CLAUSE number-1 FOR 'string-1' IS INVALID.


Explanation: An invalid number or unexpected characters were found one the right side of clause Number-1 for column String-1.

User response: Correct the syntax and retry.

NGTU061

OPERATOR WAS EXPECTED AFTER 'string-1' IN CLAUSE number-1 AND WAS NOT FOUND.


Explanation: An operator was expected in clause Number-1 after column String-1 and was not found.

User response: Check the syntax and ensure that a relational operator exists.

NGTU062

MISSING OPERAND 2 IN CLAUSE.


Explanation: An operand was expected after the operator and none was found.

User response: Check to be sure you have coded an operand after the operator.

NGTU063

CANNOT COMPARE TO EMPTY STRING.


Explanation: The string constant in a comparison has a length of 0. A fixed length column must have a non-zero length. Varying columns can have a length of 0.

User response: Provide a valid string for the comparison. If you are comparing to blanks, provide at least one blank character between the delimiters.

NGTU064

GRAPHIC STRINGS MUST HAVE EVEN LENGTH.


Explanation: Graphic fields are made up of double-byte characters. Therefore, the length of any graphic string must be even, not odd.

User response: Correct the string and rerun.

NGTU065

UNKNOWN IDENTIFIER 'string-1' IN CLAUSE.


Explanation: A DB2 identifier was expected but not found. Identifiers are reserved words such is 'NOT' or 'NULL'.

User response: Correct the clause and rerun.

NGTU066

INVALID OPERATOR 'string-1' AFTER 'string-2' IN CLAUSE number-1.


Explanation: A valid operator was expected and not detected. What was found in clause Number-1 after column String-2 is shown as String-1.

User response: Correct the clause and rerun.

NGTU067

MISSING IDENTIFIER 'string-1'.


Explanation: The identifier named in string-1 was expected but was not coded.

User response: Correct the clause and rerun.

NGTU068

INVALID COMPARISON BETWEEN DATA TYPE AND STRING TYPE.


Explanation: The data type or actual data value in the constant is not compatible with the data type of the compared column. Data types must be compatible or convertible to satisfy the comparison. These are neither.

User response: Correct the clause and rerun.

NGTU069

CONSTANT IS TOO LONG FOR COMPARE.


Explanation: The string constant, delimited, hex, graphic or numeric, is too long or its value is too large for a valid comparison to take place.

User response: Correct the clause and rerun.

NGTU070

string-1 VALUE IS BLANK.


Explanation: A date, time or timestamp value to be converted was blank.

User response: Provide a valid value and rerun.

NGTU071

VALUE LENGTH OF number-1 IS OUT OF RANGE.


Explanation: A date, time or timestamp value either exceeded the maximum length or was less than the minimum length allowed.

User response: Provide a valid value and rerun.

NGTU072

string-1 VALUE string-2 IS INVALID.


Explanation: A date, time or timestamp value is not in a recognizable or valid format.

User response: Provide a valid value and rerun.

NGTU073

RESERVED WORD 'string-1' OUT OF PLACE IN CLAUSE number-1.


Explanation: The placement of reserved word String-1 in clause Number-1 is not correct for the clause being parsed.

User response: Correct the clause and retry.

NGTU074

LOGICAL OPERATOR WAS EXPECTED AFTER 'string-1', CLAUSE number-1, AND WAS NOT FOUND.


Explanation: A logical operator (NOT, AND, OR) was expected in clause Number-1 after column String-1 and was not found.

User response: Check the syntax and ensure that a logical operator exists.

NGTU075

TABLESPACE tableSpaceName DEFINITION IS INCOMPLETE, REASON 'string-3'.


Explanation: The DB2 catalog table SYSIBM.SYSTABLESPACE column 'STATUS' contains a code, shown as string-3, that indicates the reason. The database and table space name are string-1 and string-2.

User response: Check the DB2 documentation under Catalog Descriptions for the meaning of the STATUS reason. Correct and rerun the operation.

NGTU076

ESA COMPRESSION IS NOT SUPPORTED ON THIS MVS SYSTEM.


Explanation: The ESA hardware compression facility is not installed on the processor on which this job was run. Also, the software simulator provided by MVS V4R3 or higher is not present.

User response: Rerun the job on a processor having the ESA compression facility or on an MVS V4R3 or higher system.

NGTU077

OBTAIN MACRO FAILED FOR 'string-1'. RC=number-1.


Explanation: An OBTAIN macro failed with return code number-1 for ddname string-1.

User response: Return codes for OBTAIN are documented in the MVS/DFP Systems Programming Reference manul. Attempt to resolve locally. If you need assistance, contact BMC Customer Support.

NGTU078

COMPRESSION DICTIONARY BUILD IS IN PROGRESS databaseName.tableSpaceName


Explanation: This message indicates that the current task has started the process to build an ESA/390 Compression Dictionary for the current table space.

User response: No action necessary--information only.

NGTU079

COMPRESSION DICTIONARY BUILD COMPLETED. ENTRIES=number-1 databaseName.tableSpaceName part_clause


Explanation: This message concludes the ESA/390 compression dictionary build process. number-1 represents the number of entries in the new dictionary. If the table space is not partitioned, the part_clause does not appear in the message. If the table space is partitioned, the part_clause is printed as PART(n), where n is the table space partition number. When you reorganize a partition-by-growth (PBG) table space, the part_clause is printed as PART(ALL).    

User response: No action is required.

NGTU080

COMPRESSION DICTIONARY BUILD FAILED. REASON CODE=hexstring-1


Explanation: The process to build the ESA/390 compression Dictionary has failed due to reason code X'hexstring-1'. The current task will continue its function without compression. Reason code 00000F means that too few rows are in the table for the dictionary to be built.

User response: For further assistance, contact BMC Customer Support.

NGTU081

RECORD LENGTH number-1 TOO LARGE FOR REQUEST.


Explanation: The requested function requires creating a data set. The LRECL needed by the data set exceeds the maximum allowed by MVS. The calculated size is number-1.

User response: Change your request to make the record length needed shorter. For further assistance, contact BMC Customer Support.

NGTU082

TABLESPACE tableSpacename DEFINITION IS INCOMPLETE, STATUS = string-3.


Explanation: The DB2 catalog table SYSIBM.SYSTABLESPACE column 'STATUS' contains a code, shown as string-3, that indicates the reason. The database and table space name are string-1 and string-2.

User response: Check the DB2 documentation under Catalog Descriptions for the meaning of the STATUS reason. Correct and rerun the operation. The table space is skipped.

NGTU083

INCOMPLETE COMPRESSION DICTIONARY


Explanation: A request to expand or compress a row using an ESA/390 compression dictionary could not be performed due to missing or incomplete dictionary pages. The current utility will be terminated with an error.

User response: Investigate why the dictionary definition in the table space is incomplete. Refer to the DB2 diagnosis reference for a complete description on the format of dictionary pages. For further assistance, contact BMC Customer Support.

NGTU084

//string-1 DD STATEMENT IS MISSING.


Explanation: The ddname string-1 is required and must be provided in order to continue.

User response: Supply a dd statement in the JCL and resubmit.

NGTU085

REXX AUTOMATION FEATURE IS DISABLED FOR 'string-1'.


Explanation: A password is required to run the REXX AUTOMATION Feature.

User response: See the action for NGTU086. Certain EXECs are allowed to be used with this feature installed.

NGTU086

STEP RETURN CODE OVERRIDE BY cleanupFunction FROM oldReturnCode to newReturnCode


Explanation: In this message:

  • cleanupFunction can be the +CLEANUP configuration parameter or the XSVRXERR automation control point.
  • oldReturnCode is the current value of the STEP return code.
  • newReturnCode is the new value of the STEP return code.

If the cleanupFunction is +CLEANUP, the STEP return code has changed to the STEP return code specified by the +CLEANUP configuration parameter. If the cleanupFunction is the XSVRXERR automation control point, the STEP return code has changed because the XSVRXERR automation control point requested the change.

User response: No action is required.

NGTU087

INVALID RETURN CODE SET FOR EXEC 'string-1'.


Explanation: The return code, issued via message NGTR228, is not valid for the calling exec string-1.

User response: Refer to the documentation for the exec. Correct the exec return code and retry.

NGTU088

GLOBAL VARIABLE 'string-1' TOO LONG. LENGTH IS number-1


Explanation: The global variable string-1 (whose name may have been truncated itself if longer than 40 bytes) was fetched from the REXX variable pool and the length of its value (number-1) is longer than allowed.

User response: Processing continues. However, the new value for that variable is not saved in the global variable pool. If this is the first time this variable was used, there will be no entry in the pool. If used before, the previous value will not be changed.

NGTU089

VARIABLE 'string-1' VALUE INVALID OR TRUNCATED, CODE= hexstring-1.


Explanation: The variable string-1 was fetched from the REXX variable pool and its value was either not defined, it was of the wrong data type or its value was longer that allowed. string-2 is the SHVRET return code.

User response: The SHVRET codes are documented in the REXX Reference manul and in macro IRXSHVB in SYS1.MACLIB. Review variable TERMVARS.n.TYPE to verify the data type you set is what is expected. If the error persists, contact BMC Customer Support.

NGTU090

REXX EXIT ENVIRONMENT INITIALIZATION IS IN PROGRESS


Explanation: NGTUTIL has detected the presence of the ddname CDBEXEC or NGTAUTO. This DD points to a library of REXX EXEC exits which will be used to control superutility processing. Refer to User's Guide for more details.

User response: No action necessary--information only.

NGTU091

REXX EXIT ENVIRONMENT INITIALIZATION COMPLETE


Explanation: This message marks the end of the process which was described by message NGTU090.

User response: No action necessary--information only.

NGTU092

REXX EXIT 'string-1' CPU TIME LIMIT EXCEEDED


Explanation: The REXX EXEC whose name is string-1 was found using excessive CPU time and deemed to be looping and was taken out of service. NGTUTIL program will fail due to this error.

User response: Determine why the EXEC named above is using more that 10 seconds of CPU time. Correct the EXEC and rerun your utility JOB again. If the error persists, contact BMC Customer Support.

NGTU093

LOAD FAILED FOR REXX MODULES.


Explanation: One of the REXX interface modules could not be loaded, either IRXINIT or IRXTERM. See the JOB LOG for details.

User response: Make these modules available for loading via LINKLIST or STEPLIB.

NGTU094

UNABLE TO INITIALIZE REXX ENVIRONMENT, RC=number-1, REASON=number-2


Explanation: The initialization routine was unable to build a new LPE. Module IRXINIT returned code number-1, and reason code number-2.

User response: The TSO/E REXX Reference manual lists the return codes for this module. If you are unable to correct the error, contact BMC Customer Support.

NGTU095

REXX EXIT ENVIRONMENT COLLAPSED.


Explanation: REXX could not be initialized due to a prior failure or an error occurred while processing the exec. Check prior messages for an error description.

User response: To bypass REXX processing, remove the DDname CDBEXEC or NGTAUTO from the utility JOB and rerun your JOB again. The error may be correctable at the REXX exit level. Check messages.

NGTU096

REXX EXIT 'string-1' LOAD ERROR, RC=number-1


Explanation: The REXX EXEC whose name is string-1 have experienced a load error. Module IRXLOAD return code is number-2.

User response: The TSO/E REXX Reference manual lists the return codes for this module. If you are unable to correct the error, contact BMC Customer Support.

NGTU097

REXX EXIT 'string-1' RUN ERROR, RC=number-1


Explanation: The REXX EXEC whose name is string-1 have experienced a run error. Module IRXEXEC return code is *number-2

User response: The TSO/E REXX Reference manual lists the return codes for this module. If you are unable to correct the error, contact BMC Customer Support.

NGTU098

REXX EXIT RETURN CODE OVERRIDE FROM number-1 TO number-2.


Explanation: The REXX EXEC termination exit set a new return code of number-2. The return code would have been number-1.

User response: No action required. The termination exit, XSUTTERM, set a new return code. If in error, correct the exit. This return code only effects the JCL return code.

NGTU099

'EXEC OUTPUT'


Explanation: All output generated by the EXEC will be printed on CDBPRINT under this message ID. If you desire to route the output to a different file without this message id, then add a SYSTSPRT DD to your JCL and rerun the JOB again.

User response: No action necessary--information only. If this message includes the message IRX0406E, this is merely an informational message that the exec in question will not be used by the NGT automation facility. This message will appear for each exec not found.

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

Comments