Purpose
Begins communication with the database using a specified channel device.
Syntax
where:
- cpname
- Pair of database communication devices specified as CPnnnn, where nnnn is the device number of the even-numbered IFP device. Either three or four hexadecimal digits can be specified.
- CCU
- Specification that this CP requires a communication protocol known as the Structure Protocol. All CPs using ESCON and CPs implemented by hardware known as an EBCA have this requirement. This is the default.
- CIC
- Specification that this CP requires a communication protocol known as the Segment Protocol. All CPs for the DBC/1012 and CPs implemented by hardware known as an MCA have this requirement.
Usage Notes
If an ATTACH CP command has not been issued previously, it is executed implicitly.
Before TDP will use the CP, a RUN command must be issued and complete.
The devices for an IFP can be either explicitly or dynamically allocated. Dynamic allocation by TDP is the normal choice since only the START command is required. Explicit allocation requires that the following be performed before the START command is issued:
If using this operating system | Do the following |
---|---|
z/OS VOS3 |
In the JCL procedure used to run TDP, include one DD statement for each of the two devices for the CP. Each statement is in the form: //CPnnn DD UNIT=nnn In one DD statement the nnn is the even device number; for the other it is the odd device number. For four digit device numbers, z/OS requires that the UNIT parameter contain a slash: UNIT=/nnnn |
Example: START CP
START CPC308
Completion Message
The following message confirms that the command has been validated.
TDP1363 START COMMAND ACCEPTED FOR CPC308
The following message subsequently confirms that the command has been completed.
TDP1354 "CPC308" HAS BEEN STARTED