Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Record Control Byte (RCB) Network Job Entry (NJE) Formats and Protocols SA32-0988-00 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Each logical record begins with a record control byte (RCB), which contains the stream identifier (type and number). In non-SNA transmissions, the end of the record is defined by a null string control byte (SCB) for compressed records, or by the data length byte for non-compressed records (signon, signoff, and path manager records).The initial signon record NCCIMRCB flag allows you to send mixed RCBs in a single transmission buffer. To use this flag, you must use the wait-a-bit only and ignore the FCS stream flags that indicate there is more tham one stream in a buffer. These messages cannot be avoided. See 2-93 for a description of this field. If you do not use the initial signon record NCCIMRCB flag, your
transmission buffer cannot contain records with different RCBs. The
connection must be terminated (all streams) if a transmission buffer
is received that contains an unexpected, unrecognized, or incorrect
RCB. This includes:
When the next compressed transmission record will not fit in the buffer, a special “stand-alone” RCB of X'00' (EOB) is placed after the last record and the buffer is truncated at this point for transmission. Segments are never spanned across transmission buffers, however, uncompressed records may be. Valid RCBs received out of sequence will also cause a connection to terminate. For example, a X'B0' receiver cancel with an unstarted stream referenced in the SRCB constitutes an error situation. A request to start a stream that has already been started is handled
differently. In this case, the request is rejected with the X'B0' (permission
denied) RCB. The connection is not terminated; instead, the transmitting
system can terminate the stream upon receipt of the X'B0' RCB. Table 1 depicts possible binary and hexadecimal values and
their meanings in a RCB.
For complete system-dependent and product-specific information, see System-Dependent Considerations. |
Copyright IBM Corporation 1990, 2014
|