STOP IFP (Deprecated by the STOP CP command) - Teradata Director Program

Teradata® Director Program Reference

Product
Teradata Director Program
Release Number
17.00
Published
June 2020
Language
English (United States)
Last Update
2020-06-18
dita:mapPath
pxm1544831938750.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
B035-2416
lifecycle
previous
Product Category
Teradata Tools and Utilities

Purpose

Causes TDP to stop communicating with a CP.

While the command completes immediately, the CP does not stop until all activity on the CP ends. The status in a DISPLAY CP command indicates STOPPING until all sessions end, and STOPPED thereafter.

Syntax



where:

cpname
CP as IFPnnnn, where nnnn is the device number of the even-numbered CP device, in three or four hexadecimal digits.

Usage Notes

The purpose of the STOP IFP command is to stop a CP for servicing without shutting down the TDP to which it is attached. It can also be used if a CP is to be detached from the current TDP and then attached to another TDP. In this case, once the CP is stopped (logically detached from the current TDP), it must be physically detached from the current TDP using the DETACH CP command.

All activity on the CP must end before the CP stops. On some versions of the database, the CP stops when an active request completes. On other versions, all sessions on SPs associated with the CP must end before the CP will stop. In the latter case, in addition to application sessions, this includes any unassigned session pool sessions and any TDP internal sessions. It might be necessary to stop relevant session pools using the STOP POOL command and relevant TDP internal sessions using the DISABLE IRF command. The START POOL and ENABLE IRF commands can then be used to restore the necessary sessions.

Example: STOP IFP

STO IFP490

Completion Messages

TDP1363 STOP IFP COMMAND ACCEPTED

After all activity has ended:

TDP0531 devicename SUCCESSFULLY STOPPED