TDP3529 "npname" UNUSABLE -- LOGICAL-HOST nnnnn (X'xxxx') WAS SPECIFIED, BUT TDP IS USING nnnnn (X'xxxx') - Teradata Director Program

Teradata Director Program (TDP Prefix) Messages

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Director Program
Release Number
15.xx, 16.xx, 17.xx, 20.xx
Published
June 2020
Language
English (United States)
Last Update
2023-11-20
lifecycle
Latest
Product Category
Teradata Tools and Utilities

TDP3529 "npname" UNUSABLE -- LOGICAL-HOST nnnnn (X'xxxx') WAS SPECIFIED, BUT TDP IS USING nnnnn (X'xxxx')

Explanation:

When starting the displayed NP, the indicated Logical-host id was specified but already STARTed CPs and NPs are using a different Logical-host id, as indicated. Both Logical-host ids are displayed in decimal, as would be set using the CONFIG command, and in hexadecimal, for diagnostic comparison to the value associated with a CP.

Generated By:

TDP.

Notes:

If START processing has not yet completed, the START will fail, otherwise, the NP enters the PERM ERR state and will not be used further. Any requests that are active on the NP will be failed and the associated sessions will be logged off. Sessions without active requests or with requests active on other NPs are unaffected.

Remedy:

Subsequent use of the NP may be attempted by first issuing the TDP STOP NP command (necessary only if the NP is in the PERM ERR state), then the TDP START NP command specifying the proper LHID. Contact Customer Support personnel and provid the text of this message.