Request/response header (RH)
The request/response header (RH) is used for maintaining the session's protocols. Each bit in the 3 bytes is an indicator.
The following bits are relevant while you use the distributed data facility (DDF):
BYTE 0 - X'6B'
- Request response indicator (RRI - byte 0 bit 0). If this bit is on (1), this PIU is a response PIU. If it is off (0), then the PIU is a request.
- Sense data included (SDI - byte 0 bit 5).
If this bit is on, then the first 4 bytes of the RU is SNA sense data. This sense data can often help to determine the cause of a problem.
BYTE 1 - X'80'
Pacing indicator (PI - byte 1 bit 7)
- If this bit is on and the PIU is a request, it is called a pacing request. A number of PIUs have been sent across the session and the origin LU is asking for confirmation that the destination LU is capable of taking more data. The LU that receives this PIU would normally (if there were no resource shortages) send back a pacing response.
- The pacing response (with both the RRI and PI bits on) is normally sent with no user data. That is, it is sent on its own. The pacing request, however, is usually sent on a PIU that contains data.
BYTE 2 - X'00'
- Begin bracket indicator (BBI - byte 2 bit 0)
- End bracket indicator (EBI - byte 2 bit 1)
- Conditional End Bracket Indicator (EBI - byte 2 bit 7). These 3 bits control the use of bracketing on the session. Brackets are used around each distributed data facility (DDF) conversation.
- Change Direction Indicator (CDI - byte 2 bit 2). This bit is used in the control of the half duplex session. On a half duplex session, only one LU can be sending at a time. The other LU, at this stage, must be receiving. The CDI allows the receiving LU to send data after the receive is complete.