TDP2334 "xpname" IS NOT CONFIGURED IN LOGICAL-HOST X'xxxx' (nnnnn) - 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

TDP2334 "xpname" IS NOT CONFIGURED IN LOGICAL-HOST X'xxxx' (nnnnn)

Explanation:

The Teradata Database reports that the identified CP or NP is not configured in the same Logical-host as the CP's and NP's previously started by this TDP. The Logical-host id is displayed in hexadecimal, as associated with a CP, and in decimal, as would be set using the CONFIG command.

Generated By:

TDP.

Notes:

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

Remedy:

If the CP or NP is intended for this TDP, then the Teradata Database configuration must be corrected. Subsequent use of the CP or NP may be attempted by first issuing the appropriate TDP STOP CPxxxx or STOP NPxxxx command (necessary only if it is in the PERM ERR state), then the appropriate TDP START CPxxxx or START NPxxxx command.