Messages NGTZ400 through NGTZ499

For the Next Generation Technology products, this topic explains each message in the designated range.
NumberDescription
NGTZ400

CURRENT TIME (string-1:string-2:string-3) FALLS WITHIN RTS SCHEDULE TABLE'S START AND END TIMES.


Explanation: The current time falls within the Start and End times specified in the RTS Schedule table row.

User response: No action required--information only.

NGTZ401

RTS SCHEDULE TABLE MONTH MATCHES CURRENT MONTH (number-1).


Explanation: The RTS Schedule table month value matches the current month value.

User response: No action required--information only.

NGTZ402

UID string-1 WILL BE RESTARTABLE (SOME OBJECTS ARE IN STEP-MUST-COMPLETE).


Explanation: The XSUTTIME REXX exec has issued a return code that requests all new work be halted. The RESTARTABLE variable has been ignored because some objects are in STEP-MUST-COMPLETE.

User response: No action required--information only.

NGTZ403

DB2 SSN ssid ATTACH API ERROR (RETURN CODE=returnCode REASON=reasonCode).


Explanation: The utility encountered an internal error and terminated. Most likely either DB2 Solution Common Code (SCC) is not bound to the NGT plan, or the SCC load library is not included in the STEPLIB.

User response: If you understand the reason for the error, correct the problem and resubmit the job. If you need further assistance, contact BMC Customer Support.

NGTZ404

DB2 SSN ssid ATTACH API DB2 ERROR (RETURN CODE=returnCode REASON=reasonCode)


Explanation: The utility encountered a DB2 call attachment facility (CAF) error and terminated. Likely causes are as follows:

  • The plan is not bound on the specified DB2 subsystem.

  • You are not authorized to run the plan.

  • The maximum number of threads has been reached.

  • The CAF release level does not match the release level of the DB2 subsystem.


User response: Check the IBM DB2 messages and codes documentation for an explanation of the indicated reason code. Correct the problem and resubmit the job.

NGTZ405

SERIALIZATION ERROR (RETURN CODE=returnCode REASON=reasonCode).


Explanation: You attempted to run a utility on an object, but the utility encountered a conflict with the object and terminated. Most likely, a utility with exclusive access is already running on that object. Message lines after the first line provide additional information about the problem, and about the utility ID and object on which the problem occurred.

User response: Determine the cause of the conflict. Resolve the conflict and resubmit the job.

NGTZ406

UTILITY ENTRY CREATED IN BMCUTIL FOR UTILITY ID utilityID.


Explanation: The utility registered the indicated utility ID in the BMCUTIL table for the current execution of that utility.

User response: No action is required.

NGTZ407

UTILITY ENTRY DELETED FROM BMCUTIL FOR UTILITY ID utilityID.


Explanation: When the job with the indicated utility ID completed, the utility removed the entry for that ID from the BMCUTIL table.

User response: No action is required.

NGTZ408

SYNC ENTRIES CREATED IN BMCSYNC FOR UTILITY ID utilityID.


Explanation: In the BMCSYNC table, the utility registered the objects on which it is operating for the indicated utility ID.

User response: No action is required.

NGTZ409

SYNC ENTRIES DELETED FROM BMCSYNC FOR UTILITY ID utilityID.


Explanation: For the indicated utility ID, the utility removed rows from the BMCSYNC table for the objects on which it was operating.

User response: No action is required.

NGTZ410

ALL ENTRIES DELETED FROM BMCSYNC FOR UTILITY ID utilityID.


Explanation: The utility removed all rows from the BMCSYNC table for the indicated utility ID. This action usually occurs when you restart a job with NORESTART.

User response: No action is required.

NGTZ411

ERROR OCCURRED PROCESSING OBJECTSET RECORD


Explanation: An error occurred while the utility was processing the object set record. The utility terminated.

User response: To determine the nature of the problem, check the JOBLOG and SYSERROR file for additional messages. Correct the problem and rerun the job step. If you are unable to resolve the problem, contact BMC Customer Support.

NGTZ412

OBJECTSET objectSetName ERROR (RETURN CODE=returnCode REASON=reasonCode).


Explanation: An error occurred while the utility was attempting to resolve an object set. The utility terminated.

User response: To help determine the nature of the problem, check the JOBLOG and SYSERROR file for additional messages. Correct the problem and rerun the job step. If you are unable to resolve the problem, contact BMC Customer Support, providing them with the information in this message.

NGTZ413

OBJECTSET INSTALLATION ERROR - PACKAGES NOT PROPERLY BOUND.


Explanation: The utility uses the BMC DB2 Solution Common Code (SCC) component to resolve the object set. However, the SCC packages were not bound properly.

User response: To help determine the nature of the problem, check the JOBLOG and SYSERROR file for additional messages. Correct the problem and rerun the job step. If you are unable to resolve the problem, contact BMC Customer Support.

NGTZ414

OBJECTSET INSTALLATION ERROR - SYNONYMS NOT DEFINED.


Explanation: The utility uses the BMC DB2 Solution Common Code (SCC) component to resolve the object set. However, the SCC synonyms were not created.

User response: To help determine the nature of the problem, check the JOBLOG and SYSERROR file for additional messages. Correct the problem and rerun the job step. If you are unable to resolve the problem, contact BMC Customer Support.

NGTZ415

OBJECTSET objectSetName NOT FOUND.


Explanation: The utility could not find the indicated object set. This problem might occur, for example if the BMC DB2 Solution Common Code (SCC) packages were not bound properly. The utility terminated.

User response: To help determine the nature of the problem, check the JOBLOG and SYSERROR file for additional messages. Correct the problem and rerun the job step. If you are unable to resolve the problem, contact BMC Customer Support.

NGTZ416

OBJECTSET SQL ERROR SQLCode HAS OCCURRED


Explanation: The indicated SQL error occurred while the utility was trying to resolve an object set. The utility terminated.

User response: To help determine the nature of the problem, check the JOBLOG and SYSERROR file for additional messages. Correct the problem and rerun the job step. If you are unable to resolve the problem, contact BMC Customer Support.

NGTZ417

USING tableName FOR {BMCUTIL | BMCSYNC} TABLE (FOUND USING {ALIAS | SYNONYM}).


Explanation: The NGTDISP utility is using the indicated table to query the BMCSYNC or BMCUTIL table.

User response: No action is required.

NGTZ418

OUTPUT DDname DATA SET NAME ERROR (TOO LONG).


Explanation: The data set name in the OUTPUT statement is longer than 44 characters, which the utility does not support. The utility terminated.

User response: Correct the data set name in the OUTPUT statement and resubmit the utility.

NGTZ419

DATA SET MASK IS EMPTY (DDNAME = DDname).


Explanation: The data set name in the OUTPUT statement is missing. The utility terminated.

User response: Correct the data set name in the OUTPUT statement and resubmit the utility.

NGTZ420

SUBSTITUTION ERROR HAS OCCURRED WITH DATA SET MASK (DDNAME = DDname).


Explanation: An error occurred while attempting to resolve the variables in the OUTPUT statement data set name. The utility terminated.

User response: Correct the data set name in the OUTPUT statement and resubmit the utility.

NGTZ421

OUTPUT (DDname) DATA SET NAME IS NOT VALID FOR GDG.


Explanation: An error occurred while attempting to build the GDG base for the data set name specified in the OUTPUT statement. The utility terminated.

User response: Correct the data set name in the OUTPUT statement and resubmit the utility.

NGTZ422

UTILITY ENTRY UPDATED IN BMCUTIL FOR UTILITY ID utilityID (STATUS=status)


Explanation: The utility has updated the BMCUTIL table with the indicated status for the indicated utility ID. For information about the BMCUTIL table and the utility status, see Next Generation Technology (NGT) products 12.1 .

User response: No action is required.

NGTZ423

WHERE CLAUSE WILL NOT BE USED.


Explanation: The utility encountered an invalid WHERE clause. The utility continues, but does not use the WHERE clause that you specified.

User response: Review messages in the SYSERROR DD, including the WHERE clause that is in error. If appropriate, correct the WHERE clause and rerun the job.

NGTZ424

UTILITY ENTRY UPDATED IN BMCUTIL FOR UTILITY ID utilityID (CKPT DSN).


Explanation: The BMCUTIL table row for the specified utility ID was updated with the name of the CKPT data set used by the utility.

User response: No action required.

NGTZ426

UID utilityID TYPE type MUST BE INITIATED THRU SMARTSWITCH USING CLASSIC UTILITY


Explanation: A SmartSwitch run initiated from one of the classic utilities has failed and you tried to run RESTART, FORCEID or QUICKEXIT from native NGT using the utility ID.

User response: Run RESTART, FORCEID, or QUICKEXIT using SmartSwitch from the classic utility.

NGTZ427

DSNAME VALIDATION WARNING: NO DSNAME VALUE FOUND.

Explanation: The NGT utility did not find a resolved data set name value during the data set name validation process. The OUTPUT command processor issues this message to indicate a possible runtime error.

User response: Review the SYSERROR file to ensure that the resolved data set name used during the NGT utility run is valid.

NGTZ428

DSNAME VALIDATION WARNING: RESOLVED DSNAME LONGER THAN 44 CHARACTERS.

Explanation: The OUTPUT command process referenced a resolved data set name value that is longer than 44 characters. The OUTPUT command processor issues this message to indicate a possible runtime error.

User response:  Review the SYSERROR file to ensure that the resolved data set name used during the NGT utility run is valid.

NGTZ429

DSNAME VALIDATION ERROR: UNRESOLVED VARIABLES FOUND IN DATASET NAME.

Explanation: The OUTPUT command processor issued this message to indicate a possible runtime error. The NGT utility found unresolved variables in the data set name used in the OUTPUT command. The utility issues a high return code value of 8.  

User response: Review the SYSERROR file to ensure that the resolved data set name used during the NGT utility run is valid.

NGTZ430

DSNAME VALIDATION WARNING: RESOLVED NODE LONGER THAN 8 CHARACTERS.

Explanation: The OUTPUT command processor issued this message to indicate a possible runtime error. The OUTPUT command process referenced a resolved data set name that contains at least one qualifier that is longer than eight characters.

User response: Review the SYSERROR file to ensure that the resolved data set name used during the NGT utility run is valid.

NGTZ438

NGTZ438 PROCESSING OF UTILITY BY NGT PREVENTED BY XSUTSMSW


Explanation: The XSUTSMSW automation routine has issued a return code indicating the utility should not be processed by NGT. SmartSwitch will use BMC Classic to process the utility.

User response: No action is required.

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

Comments