ATTACH CP - Teradata Director Program

Teradata Director Program Reference

Product
Teradata Director Program
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-09
dita:mapPath
hwt1488824663348.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2416
lifecycle
previous
Product Category
Teradata Tools and Utilities

Purpose

Allocates a specified channel device from the operating system.

Syntax



where:

cpname
Pair of Database communication devices specified as CPnnnn, where nnnn is the device number of the even-numbered device. Either three or four hexadecimal digits can be specified.

Usage Notes

The devices for an IFP can be either explicitly or dynamically allocated. Dynamic allocation by TDP is the normal choice since only the ATTACH command is required. Explicit allocation requires that the following be performed before the ATTACH command is issued:

If using this operating system Do the following
z/OS

VOS3

In the JCL procedure used to start TDP, include one DD statement for each of the two devices for the CP. Each is of the form:

//IFP nnnn DD UNIT= nnn

In one DD statement the nnn is the even device. In the other DD statement the nnn is the odd device number.

For four-digit device numbers, z/OS requires that the UNIT parameter contain a slash as in UNIT=/nnnn

Before TDP will use the CP, a START command for that CP and a RUN command must be issued and complete.

Example: ATTACH CP

ATTACH CPC308

Completion Message

The following message confirms that the command has been validated:
TDP1356 ATTACH COMMAND ACCEPTED FOR CPC308
The following message subsequently confirms that the command has been completed:
TDP1356 "CPC308" HAS BEEN ATTACHED