READ

Read syntax diagramSkip visual syntax diagram
>>-READ--=--+-channel_unit_address-------+---------------------><
            '-(--channel_unit_address--)-'   

Specifies the subchannel address used to read data from the adjacent APPN node or Open Systems Adapter port. You must code at least one READ subchannel.

For an OSA-Express feature, it specifies the subchannel address used to read MPC or ULP specific control data. You must code exactly one READ subchannel.

Subchannel addresses can be defined as a single address, as a range of addresses, or both. A range is indicated by a hyphen(-). VTAM® generates addresses for the range. For example, READ=(132,128-130,13A) defines the addresses 132, 128, 129, 12A, 12B, 12C, 12D, 12E, 12F, 130, and 13A.

For connections to an adjacent APPN host node:

each address on the READ operand, code the corresponding address on the WRITE operand in the adjacent host to provide a complete path.

For connections to an Open Systems Adapter port or an OSA-Express port:

you can specify only one subchannel address and that address must be an even number that is one less than the address specified on the corresponding WRITE operand. For example, if you specify 500 on the READ operand, you must specify 501 on the WRITE operand.

If this Open Systems Adapter port is for native ATM access, the last two digits of the subchannel address you specify on the READ operand must match the Even Unit Address as it is defined during Open Systems Adapter configuration on the ATM Native Support Settings panel, which is part of the OSA Configuration pull down option accessed through the OSA/SF interface.

If this Open Systems Adapter port is for an OSA-Express feature, there is no matching configuration required.

For an adjacent APPN node or an Open Systems Adapter port, do not code the same subchannel address for the READ operand and the WRITE operand in the same host.

Note: Start of changeAll READ and WRITE channels that you configure must have similar physical characteristics. If some channels take different physical paths with longer distances, this might result in data arriving out of order on the partner host. For connections to an adjacent APPN node, and MPCLEVEL=HPDT is specified, HPR is required to resequence the inbound packets that they arrive out of order. HPR performs best when packets arrive with consistent times and data arrives in order. If the physical paths of the underlying HPDT MPC connection are vastly different, this might lead to excessive retransmissions from HPR. The excessive retransmissions might lead to performance degradation.End of change