Purpose
Allocates a CP to a TDP.
Syntax
where:
- cpname
- CP as IFPnnnn, where nnnn is the device number of the even-numbered CP or device, in three or four hexadecimal digits.
Usage Notes
The devices for a CP can be either explicitly or dynamically allocated. Dynamic allocation is the more usual operation since no explicit allocation is required: TDP automatically allocates the required devices. Explicit allocation requires that the following be performed prior to ATTACHing the CP:
If using this operating system | Do the following |
---|---|
z/OS VOS3 |
Include two DD statements in the JCL procedure that is used to start TDP. |
The DD statements should be in this format: // IFP nnnn DD UNIT= nnn |
|
One of these statements is for the even CP device number, the other for the corresponding odd CP device number. | |
If a four-digit device number is specified for the UNIT keyword, z/OS requires that a slash precede the digits, as in UNIT=/nnnn | |
The FILEDEFs should be in this format: FILEDEF IFPnnnn DUMMY IFP nnnn I |
For either operating system, IFPnnnn corresponds to the ifpname used in the ATTACH command. IFPnnn and IFP0nnn are equivalent. That is, the command can specify one form and the static system definition can specify the other.
Before any session can be assigned to a newly attached CP, the following must occur:
- The RUN command must be executed
- A START CP command must be executed for the CP
- TDP must respond with an IFP STARTED message
Because a CP is implicitly attached to a TDP by the RUN/START CP command execution sequence, the explicit use of the ATTACH CP command is unnecessary under normal operating conditions.
Example: ATTACH IFP
ATT IFP490
Completion Message
TDP1356 IFP490 ATTACHED