Unusable CP or NP - Teradata Tools and Utilities

Teradata® Call-Level Interface Version 2 Reference for Mainframe-Attached Systems - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Tools and Utilities
Release Number
17.20
Published
June 2022
ft:locale
en-US
ft:lastEdition
2023-11-17
dita:mapPath
oxw1641281447623.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
vfj1470443597526
lifecycle
previous
Product Category
Teradata Tools and Utilities

A Channel Processor (CP) is a communication path using the mainframe channel between TDP and the database; a Network Processor (NP) is a communication path using the network between TDP and the database. Since more than one CP or NP is often installed, the failure of one does not prevent communication with the database, but it does have a dramatic impact on requests that are using the failed CP or NP. Unlike a database restart in which all requests are terminated, leaving the sessions in a known, usable state, the failure of a CP or NP does not clean up current requests but since their state cannot be ascertained by TDP, TDP must logoff the affected sessions. A return code of 544 indicates this condition. If the application is to recover, it must connect that session again, ascertain whether the requests successfully completed, and continue processing as appropriate. However, the return code is presented immediately but it may take an indeterminate amount of time for TDP to abort the original request and logoff the original session. Any database resources associated with that request and session may not yet have been freed so may not yet be available.