Each channel adapter attached to a mainframe channel must be described
to the mainframe hardware. This is performed with an IOCP generation or
some other method of defining the CPU's UCWs (Unit Control Words),
depending on the host CPU type and operating system. For example,
VM has an IOCP MODULE on the system disk which builds
the IOCP configuration file for you. MVS/ESA Version 5 and above
has HCD, an interactive utility which runs under TSO and which
will build the IOCP configuration file. Please refer to the instructions
that accompany your mainframe and operating system for more information
on how to define devices to your particular system.
Regardless of the method used to define
the IOCP, the general definitions will be the same for a given
channel attached device. Below you will find IOCP sample definitions
for the various Bus-Tech channel-attached controllers. Please review
the definitions for the appropriate type of device your want to define.
Bus-and-Tag (Parallel) Channel Attached Devices
Example for a VTAM 3174 controller
Example for a DataBlaster 2 with Parallel Data Mover (PDM)
ESCON Channel Attached Devices
Example for a VTAM 3174 controller
Example for a DataBlaster 2 with Parallel Data Mover (PDM)
Defining a Bus-and-Tag Channel Adapter for VTAM 3174 PUs
For proper operation observe the following IOCP or UCW parameter requirements:
- The Channel adapter can support up to 32 subchannel (device) addresses. However, NetWare for SAA 1.3B, 2.0, and 2.2 can only support a maximum of eight Data Link Adapters (PUs) due to Netware limitations. IntraNetware for SAA 3.0 can support a maximum of 32 PUs if all the latest Netware 4.11 PTFs and Service Packs are applied. Microsoft NT SNA Server and IBM Comm Server for NT support up to 32 addresses.
- For each PU to be supported by the channel adapter, generate the IOCP or UCW for a separate 3791L control unit with 1 device per controller. Do not define multiple devices on a 3791L control unit. You may also use the more modern control unit type of 3174, which permits multiple devices per control unit.
- The channel mode in the IOCP or UCW generation must match the channel mode set for the adapter (refer to hardware guide). The channel modes supported by Bus-Tech adapters are DC Interlock, 3.0 MB Streaming, and 4.5 MB Streaming. Your bus-and-tag cables must be rated for streaming, if using Streaming Mode.
- The PBCA/EBCA (UCWs) must be generated as nonshared.
- For IOCP CNTLUNIT and IODEVICE definitions, specify either UNIT=3791L or UNIT=3174. If using 3791L types, assign only one device per 3791L control unit statement (for each PU, create a pair of CNTLUNIT and IODEVICE statements which define a single 3791L device). If you are using MVS's HCD utility, specify DYNAMIC: NO and LOCANY: NO. We also recommend that if you wish to run the PBCA or EBCA with both SNA 3174 emulation as well as TCP/IP 3172 emulation, then choose a Control Unit type of NOCHECK instead of 3791L or 3174. NOCHECK will bypass the objections of HCD that it detects two types of devices on a single controller. The IODEVICE statements still require the appropriate device type of 3791L or 3174 however.
For further information on IOCP or UCW generation methods and parameters, refer to your mainframe CPU documentation.
The following is an example of an IOCP generation for a typical channel attached installation. This particular configuration defines one channel adapter, with addresses 5F0 and 5F1.
The IOCP generation is the same for all types of PUs supported by the channel adapter. The PUs supported by the channel adapter are NetWare for SAA PUs, type 2.0 and type 2.1.
If your mainframe (such as an IBM 4381) does not require an IOCP definition, simply configure your UCWs similarly using the method required for your CPU.
|
Note: If your channel supports streaming mode, then chose the appropriate S or S4 operand on the PROTOCL= parameter. You must also ensure that the channel adapter is configured accordingly. Incorrect matching of the CPU's channel mode and the adapter's channel mode may cause unpredictable errors on the mainframe channel.
Defining an ESCON Channel Adapter for VTAM 3174 PUs
For proper operation observe the following IOCP or UCW parameter requirements:
- The ESCON adapter can support up to 32 subchannel (device) addresses. However, NetWare for SAA 1.3B, 2.0, and 2.2 can only support a maximum of eight Data Link Adapters (PUs) due to Netware limitations. IntraNetware for SAA 3.0 can support a maximum of 32 PUs if all the latest Netware 4.11 PTFs and Service Packs are applied. Microsoft NT SNA Server and IBM Comm Server for NT support up to 32 addresses.
- For IOCP CNTLUNIT and IODEVICE definitions, specify UNIT=3174.
- There is no PROTOCL= used for ESCON devices, ESCON uses a constant channel speed.
For further information on IOCP or UCW generation methods and parameters, refer to your mainframe CPU documentation.
The following are examples for creating the Mainframe IOCP Generation for ESCON Adapter cards connecting to IBM ESCON Channels.
Example A: CONNECTION DIRECT TO ESCON CHANNEL (ONE VTAM PU)
The following example shows a configuration of one subchannel address, 2F0, (i.e. one VTAM PU) generated on the adapter connected to a mainframe using CHPID 21:
|
Example B: CONNECTION DIRECT TO ESCON CHANNEL (MULTIPLE VTAM PU'S)
The following example shows a configuration of three subchannel addresses, 380, 381, and 382 (i.e. three VTAM PU's) generated on the adapter connected to a mainframe using CHPID 19:
|
Example C: CONNECTION TO ESCON DIRECTOR IN BASIC MODE (ONE VTAM PU)
The following example shows a configuration of one subchannel address, 2F0,
(ie,one VTAM PU) generated on the adapter connected to a mainframe using CHPID 22:
|
Example D: CONNECTION TO ESCON DIRECTOR IN BASIC MODE (MULTIPLE VTAM PU'S)
The following example shows a configuration of three subchannel addresses (ie,
two VTAM PU's) generated on the adapter connected to a mainframe using CHPID 22:
|
Defining a Bus-and-Tag Adapter For a TCP/IP Controller
The following example defines the two required devices for a TCP/IP controller using mainframe addresses 9F0 and 9F1, with a channel data rate of 1 MByte/second in DC Interlock mode.
Please note that if your mainframe does not require an IOCP definition, simply configure your mainframe’s UCWs similarly, using the method required for your mainframe.
If using MVS HCD and IBM's MVS TCP/IP, we recommend that you specify
DYNAMIC: NO and LOCANY: NO
to avoid possible program ABENDs in the IBM TCP/IP product. This appears to be a software "bug" in the IBM TCP/IP product over which Bus-Tech has no control.
|
The following example defines the two required devices for a TCP/IP controller using mainframe addresses 4A0 and 4A1, with a channel data rate of 4.5 MBytes/second in streaming mode:
|
Defining an ESCON Adapter For a TCP/IP Controller
The following are examples of the mainframe IOCP generation for a Bus-Tech ESCON adapter card connecting to IBM ESCON channels and supporting TCP/IP Passthrough. Note that ESCON devices do not use the PROTOCL= keyword, which applies only to bus and tag channels.
If using MVS HCD and IBM's MVS TCP/IP, we recommend that you specify
DYNAMIC: NO and LOCANY: NO
to avoid possible program ABENDs in the IBM TCP/IP product. This appears to be a software "bug" in the IBM TCP/IP product over which Bus-Tech has no control.
Example A: Connection Directly to an ESCON Channel
The following example defines the two required devices for a TCP/IP controller using mainframe addresses 2F0 and 2F1 on CHPID 21 using a direct ESCON connection:
|
Example B: Connection to ESCON Director in Basic Mode
The following example defines the two required devices for a TCP/IP controller using mainframe addresses 0F0 and 0F1 on CHPID 22 connecting through an ESCON director. The director's identifier is C3, and it is using switch 01 to connect to the ESCON adapter:
|
Defining a Bus-and-Tag DataBlaster-2
The following examples show mainframe IOCP definitions for a Bus-Tech Parallel (Bus-and-Tag) channel connection that is supporting Datablaster-2 3480 tape emulation.
The number of virtual tape devices required is based on the planned number of connections between the mainframe and the various SCSI hosts. Your Datablaster-II controller unit has been built according to specifications given to us at the time of your order, and the number of connections you will have is a function of the number of SCSI and channel adapters which you ordered. Consult the various user manuals supplied by Bus-Tech to determine how many connections your unit will support, and then prepare your IOCP based on those estimates.
Please note that if your mainframe does not require an IOCP definition, simply configure your mainframe’s UCWs similarly, using the method required for your mainframe.
This particular sample configuration creates 2 virtual tape drives using address pair 2C0 and 2C1, with a channel speed of 4.5MB streaming. Each virtual drive would be logically paired with a unique LUN on a SCSI adapter. Note below that the CUNUMBR is a relative value, having no particular special value to anyone except the data center staff. It could just as easily be equal to the base device address value of 2C0.
|
This next sample configuration creates 1 virtual tape drive using address 810, with a channel speed of 3.0MB streaming. This virtual drive would be logically paired with a LUN on a single SCSI adapter. In this example, we make CUNUMBR the same value as the device address:
|
Defining an ESCON Datablaster-II
The following examples show mainframe IOCP definitions for a Bus-Tech ESCON adapter card connecting to IBM ESCON channels and supporting Datablaster-II 3490 tape emulation. Note that ESCON devices do not use the PROTOCL= keyword, which applies only to Bus-and-Tag channels.
The number of virtual tape devices required is based on the planned number of connections between the mainframe and the various SCSI hosts. Your Datablaster-II controller unit has been built according to specifications given to us at the time of your order, and the number of connections you will have is a function of the number of SCSI and channel adapters which you ordered. Consult the various user manuals supplied by Bus-Tech to determine how many connections your unit will support, and then prepare your IOCP based on those estimates.
Example A: EBSA/PBSA Connection DIRECT to ESCON Channel
The following example defines the 2 virtual 3490 ESCON tape drives to Datablaster-II as mainframe addresses 200 and 201 on CHPID 21 using a direct ESCON connection.
Each virtual drive would be logically paired with a unique LUN on a SCSI adapter. Note below that the CUNUMBR is a relative value, having no particular special value to anyone except the data center staff. It could just as easily be equal to the base device address value of 200.
|
Example B: EBSA/PBSA Connection to ESCON Director in Basic Mode
The following example defines the 4 virtual 3490 ESCON tape drives as mainframe addresses 310 through 313 on CHPID 22 connecting through an ESCON director. The director's identifier is C2, and it is using switch 02 to connect to the EBSA/PBSA ESCON adapter::
|
Defining a Bus-and-Tag DataBlaster-II For PDMAt this time, Bus-Tech is not offering the PDM product with the EBCA adapter. If your company has an interest in such a product, please contact our marketing department. Defining an ESCON DataBlaster-II For PDMThe following are examples of the mainframe IOCP generation for a Bus-Tech ESCON adapter card connecting to IBM ESCON channels and supporting PDM Channel-to-Channel Adapter (CTCA) emulation. Note that ESCON devices do not use the PROTOCL= keyword, which applies only to Bus-and-Tag channels. The number of CTCA devices required is based on the planned number of connections between the mainframe and the various SCSI hosts. Your PDM controller unit has been built according to specifications given to us at the time of your order, and the number of connections you will have is a function of the number of SCSI and channel adapters which you ordered. Consult the various user manuals supplied by Bus-Tech to determine how many connections your unit will support, and then prepare your IOCP based on those estimates. Example A: EBSA/PBSA Connection DIRECT to ESCON Channel The following example defines the 16 virtual 3088 CTCAs to PDM as mainframe addresses 200 through 20F on CHPID 21 using a direct ESCON connection. Note below that the CUNUMBR is a relative value, having no particular special value to anyone except the data center staff. It could just as easily be equal to the base device address value of 200.
Example B: EBSA/PBSA Connection to ESCON Director in Basic Mode The following example defines the 4 virtual ESCON CTCAs as mainframe addresses 310 through 313 on CHPID 22 connecting through an ESCON director. The director's identifier is C4, and it is using switch 03 to connect to the EBSA/PBSA ESCON adapter:
|
