PLU to SLU, Exp; SC
________________________________________________________________________
| BIND (BIND SESSION) |
|_______ _____ __________________________________________________________|
| Byte | Bit | Content |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 0 | | X'31' request code |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 1 | 0-3 | Format: 0000 (only value defined) |
|_______|_____|__________________________________________________________|
| | 4-7 | Type: |
|_______|_____|______ ___________________________________________________|
| | | 0000 | negotiable (only value defined for LU 6.2) |
|_______|_____|______|___________________________________________________|
| | | 0001 | nonnegotiable |
|_______|_____|______|___________________________________________________|
|_______ _____ __________________________________________________________|
| 2 | | FM profile: |
|_______|_____|_______ __________________________________________________|
| | | X'02' | FM profile 2 |
|_______|_____|_______|__________________________________________________|
| | | X'03' | FM profile 3 |
|_______|_____|_______|__________________________________________________|
| | | X'04' | FM profile 4 |
|_______|_____|_______|__________________________________________________|
| | | X'07' | FM profile 7 |
|_______|_____|_______|__________________________________________________|
| | | X'12' | FM profile 18 |
|_______|_____|_______|__________________________________________________|
| | | X'13' | FM profile 19 (only value defined for LU 6.2) |
|_______|_____|_______|__________________________________________________|
|_______ _____ __________________________________________________________|
| 3 | | TS profile: |
|_______|_____|_______ __________________________________________________|
| | | X'02' | TS profile 2 |
|_______|_____|_______|__________________________________________________|
| | | X'03' | TS profile 3 |
|_______|_____|_______|__________________________________________________|
| | | X'04' | TS profile 4 |
|_______|_____|_______|__________________________________________________|
| | | X'07' | TS profile 7 (only value defined for LU 6.2) |
|_______|_____|_______|__________________________________________________|
|_______ _____ __________________________________________________________|
| | | FM Usage--Primary LU Protocols for FM Data |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 4 | 0 | Chaining use selection: |
|_______|_____|___ ______________________________________________________|
| | | 0 | only single-RU chains allowed from primary LU |
| | | | half-session |
|_______|_____|___|______________________________________________________|
| | | 1 | multiple-RU chains allowed from primary LU |
| | | | half-session (only value defined for LU 6.2) |
|_______|_____|___|______________________________________________________|
| | 1 | Request control mode selection: |
|_______|_____|___ ______________________________________________________|
| | | 0 | immediate request mode (only value defined for LU |
| | | | 6.2) |
|_______|_____|___|______________________________________________________|
| | | 1 | delayed request mode |
|_______|_____|___|______________________________________________________|
| | 2-3 | Chain response protocol used by primary LU half-session |
| | | for FMD requests; chains from primary will ask for: |
|_______|_____|____ _____________________________________________________|
| | | 00 | no response |
|_______|_____|____|_____________________________________________________|
| | | 01 | exception response |
|_______|_____|____|_____________________________________________________|
| | | 10 | definite response |
|_______|_____|____|_____________________________________________________|
| | | 11 | definite or exception response (only value defined |
| | | | for LU 6.2) |
|_______|_____|____|_____________________________________________________|
| | 4 | 2-phase commit for sync point (reserved if any TS |
| | | profile other than 4): |
|_______|_____|___ ______________________________________________________|
| | | 0 | 2-phase commit not supported |
|_______|_____|___|______________________________________________________|
| | | 1 | 2-phase commit supported |
|_______|_____|___|______________________________________________________|
| | 5 | Reserved |
|_______|_____|__________________________________________________________|
| | 6 | FMH-1 SCB compression indicator (reserved for LU 6.2): |
|_______|_____|___ ______________________________________________________|
| | | 0 | FMH-1 SCB compression will not be used on requests |
| | | | from primary |
|_______|_____|___|______________________________________________________|
| | | 1 | FMH-1 SCB compression may be used |
|_______|_____|___|______________________________________________________|
| | 7 | Send End Bracket indicator: |
|_______|_____|___ ______________________________________________________|
| | | 0 | primary will not send EB (only value defined for LU |
| | | | 6.2) |
|_______|_____|___|______________________________________________________|
| | | 1 | primary may send EB |
|_______|_____|___|______________________________________________________|
|_______ _____ __________________________________________________________|
| | | FM Usage--Secondary LU Protocols for FM Data |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 5 | 0 | Chaining use selection: |
|_______|_____|___ ______________________________________________________|
| | | 0 | only single-RU chains allowed from secondary LU |
| | | | half-session |
|_______|_____|___|______________________________________________________|
| | | 1 | multiple-RU chains allowed from secondary LU |
| | | | half-session (only value defined for LU 6.2) |
|_______|_____|___|______________________________________________________|
| | 1 | Request control mode selection: |
|_______|_____|___ ______________________________________________________|
| | | 0 | immediate request mode (only value defined for LU |
| | | | 6.2) |
|_______|_____|___|______________________________________________________|
| | | 1 | delayed request mode |
|_______|_____|___|______________________________________________________|
| | 2-3 | Chain response protocol used by secondary LU |
| | | half-session for FMD requests; chains from secondary |
| | | will ask for: |
|_______|_____|____ _____________________________________________________|
| | | 00 | no response |
|_______|_____|____|_____________________________________________________|
| | | 01 | exception response |
|_______|_____|____|_____________________________________________________|
| | | 10 | definite response |
|_______|_____|____|_____________________________________________________|
| | | 11 | definite or exception response (only value defined |
| | | | for LU 6.2) |
|_______|_____|____|_____________________________________________________|
| | 4 | 2-phase commit for sync point (reserved if any TS |
| | | profile other than 4): |
|_______|_____|___ ______________________________________________________|
| | | 0 | 2-phase commit not supported |
|_______|_____|___|______________________________________________________|
| | | 1 | 2-phase commit supported |
|_______|_____|___|______________________________________________________|
| | 5 | Reserved |
|_______|_____|__________________________________________________________|
| | 6 | FMH-1 SCB compression indicator (reserved for LU 6.2): |
|_______|_____|___ ______________________________________________________|
| | | 0 | FMH-1 SCB compression will not be used on requests |
| | | | from secondary |
|_______|_____|___|______________________________________________________|
| | | 1 | FMH-1 SCB compression may be used |
|_______|_____|___|______________________________________________________|
| | 7 | Send End Bracket indicator: |
|_______|_____|___ ______________________________________________________|
| | | 0 | secondary will not send EB (only value defined for |
| | | | LU 6.2) |
|_______|_____|___|______________________________________________________|
| | | 1 | secondary may send EB |
|_______|_____|___|______________________________________________________|
|_______ _____ __________________________________________________________|
| | | FM Usage--Common LU Protocols |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 6 | 0 | Whole-BIUs required indicator (reserved in nonextended, |
| | | non-LU 6.2 BINDs, i.e., when control vector X'60' is not |
| | | present): |
|_______|_____|___ ______________________________________________________|
| | | 0 | the sending node supports receipt of segments on |
| | | | this session |
|_______|_____|___|______________________________________________________|
| | | 1 | the sending node does not support receipt of |
| | | | segments on this session; the maximum send-RU size |
| | | | specified in bytes 10 and 11 of BIND and RSP(BIND) |
| | | | are negotiated so that BIUs on this session are not |
| | | | segmented when sent to a node requiring whole BIUs |
|_______|_____|___|______________________________________________________|
| | 1 | FM header usage: |
|_______|_____|___ ______________________________________________________|
| | | 0 | FM headers not allowed |
|_______|_____|___|______________________________________________________|
| | | 1 | FM headers allowed (only value defined for LU 6.2) |
|_______|_____|___|______________________________________________________|
| | 2 | Brackets usage and reset state: |
|_______|_____|___ ______________________________________________________|
| | | 0 | The value of this bit should be 0 if either |
| | | | condition (1) or condition (2) is true. |
| | | | |
| | | | 1. Brackets are not used if neither primary nor |
| | | | secondary will send EB (byte 4, bit 7 = 0 and |
| | | | byte 5, bit 7 = 0). |
| | | | 2. Brackets are used and the bracket state |
| | | | managers' reset states are INB if: |
| | | | ° either primary or secondary, or both, may |
| | | | send EB (byte 4, bit 7 = 1 or byte 5, bit 7 |
| | | | = 1). |
| | | | ° FM profile 19 is specified (byte 2 = X'13'). |
| | | | |
| | | | (only value defined for LU 6.2) |
|_______|_____|___|______________________________________________________|
| | | 1 | brackets are used and bracket state managers' reset |
| | | | states are BETB |
|_______|_____|___|______________________________________________________|
| | 3 | Bracket termination rule selection; byte 4, bit 7 = 0, |
| | | and byte 5, bit 7 = 0; and if FM profile is not 19): |
|_______|_____|___ ______________________________________________________|
| | | 0 | Rule 2 (unconditional termination) will be used |
| | | | during this session |
|_______|_____|___|______________________________________________________|
| | | 1 | Rule 1 (conditional termination) will be used during |
| | | | this session (only value defined for LU 6.2) |
|_______|_____|___|______________________________________________________|
| | | Note: This bit is reserved if both of the following |
| | | conditions are true. |
| | | |
| | | 1. Brackets are not used (byte 4, bit 7 = 0, byte 5, |
| | | bit 7 = 0 , and byte 6, bit 2 = 0). |
| | | 2. The FM profile is not 19 (byte 2 &nesym. X'13'). |
|_______|_____|__________________________________________________________|
| | 4 | Alternate code set allowed indicator: |
|_______|_____|___ ______________________________________________________|
| | | 0 | alternate code set will not be used |
|_______|_____|___|______________________________________________________|
| | | 1 | alternate code set may be used |
|_______|_____|___|______________________________________________________|
| | 5 | Sequence number availability for sync point |
| | | resynchronization (reserved if any TS profile other than |
| | | 4 is used): |
|_______|_____|___ ______________________________________________________|
| | | 0 | sequence numbers not available |
|_______|_____|___|______________________________________________________|
| | | 1 | sequence numbers available |
|_______|_____|___|______________________________________________________|
| | | Note: Sequence numbers are transaction processing |
| | | program sequence numbers from the previous activation of |
| | | the session with the same session name; they are |
| | | associated with the last acknowledged requests and any |
| | | pending requests to commit a unit of work. If no |
| | | previous activation existed, the numbers are 0, and this |
| | | bit is set to 0. |
|_______|_____|__________________________________________________________|
| | 6 | BIS sent (reserved for TS profiles other than 4): |
|_______|_____|___ ______________________________________________________|
| | | 0 | BIS not sent |
|_______|_____|___|______________________________________________________|
| | | 1 | BIS sent |
|_______|_____|___|______________________________________________________|
| | 7 | BIND queuing indicator: |
|_______|_____|___ ______________________________________________________|
| | | 0 | BIND cannot be queued (held, pending resource |
| | | | availability, thus delaying the BIND response) |
|_______|_____|___|______________________________________________________|
| | | 1 | BIND sender allows the BIND receiver to queue the |
| | | | BIND for an indefinite period, thus delaying the |
| | | | sending of the BIND response |
| | | | Note: BIND sender may provide a timer or operator |
| | | | interface to send UNBIND if session-activation time |
| | | | exceeds BIND sender's implementation-defined limits. |
| | | | BIND queuing is terminated by sending UNBIND to the |
| | | | BIND receiver. |
|_______|_____|___|______________________________________________________|
|_______ _____ __________________________________________________________|
| 7 | 0-1 | Normal-flow send/receive mode selection: |
|_______|_____|____ _____________________________________________________|
| | | 00 | full-duplex |
|_______|_____|____|_____________________________________________________|
| | | 01 | half-duplex contention |
|_______|_____|____|_____________________________________________________|
| | | 10 | half-duplex flip-flop |
|_______|_____|____|_____________________________________________________|
| | | 11 | reserved |
|_______|_____|____|_____________________________________________________|
| | | Note: Values 00 and 10 are the only values defined for |
| | | LU 6.2. |
|_______|_____|__________________________________________________________|
| | 2 | Recovery responsibility: |
|_______|_____|___ ______________________________________________________|
| | | 0 | contention loser responsible for recovery (see byte |
| | | | 7, bit 3 for specification of which half-session is |
| | | | the contention loser) |
|_______|_____|___|______________________________________________________|
| | | 1 | symmetric responsibility for recovery (only value |
| | | | defined for LU 6.2) |
|_______|_____|___|______________________________________________________|
| | | Note: This bit is reserved if the normal-flow |
| | | send/receive mode is full-duplex and the FM profile is |
| | | not 19 (byte 2 &nesym. X'13'). |
|_______|_____|__________________________________________________________|
| | 3 | Contention winner/loser: |
|_______|_____|___ ______________________________________________________|
| | | 0 | secondary is contention winner and primary is |
| | | | contention loser |
|_______|_____|___|______________________________________________________|
| | | 1 | primary is contention winner and secondary is |
| | | | contention loser |
|_______|_____|___|______________________________________________________|
| | | Note 1: Contention winner is also brackets first |
| | | speaker. |
|_______|_____|__________________________________________________________|
| | | Note 2: This bit is reserved if either condition (1) or |
| | | condition (2) holds. |
| | | |
| | | 1. The normal-flow send/receive mode is full-duplex and |
| | | the FM profile is not 19 (byte 2 &nesym. X'13'). |
| | | 2. All of the following are true. |
| | | ° The normal flow send/receive mode is HDX-FF |
| | | (byte 7, bits 0-1 = 10). |
| | | ° Brackets are not used (byte 4, bit 7 = 0, byte |
| | | 5, bit 7 = 0 , and byte 6, bit 2 = 0). |
| | | ° The FM profile is not 19 (byte 2 &nesym. X'13'). |
| | | ° Symmetric responsibility for recovery is used |
| | | (byte 7, bit 2 = 1). |
|_______|_____|__________________________________________________________|
| | 4-5 | Alternate code processing identifier (reserved unless |
| | | Alternate Code Set Allowed indicator (byte 6, bit 4) is |
| | | 1): |
|_______|_____|____ _____________________________________________________|
| | | 00 | Process alternate code FMD RUs as ASCII-7. |
|_______|_____|____|_____________________________________________________|
| | | 01 | Process alternate code FMD RUs as ASCII-8 (only |
| | | | value defined for LU 6.2). |
|_______|_____|____|_____________________________________________________|
| | | Note: When the Alternate Code Processing Identifier |
| | | indicator is set to the value 01, the entire FMD request |
| | | RU is to be translated using the transforms defined by |
| | | the ANSI X3.26 Hollerith Card Code. |
|_______|_____|__________________________________________________________|
| | 6 | Control vectors included indicator: |
|_______|_____|___ ______________________________________________________|
| | | 0 | Control vectors are not included after the SLU name |
| | | | (bytes r+1-s). |
|_______|_____|___|______________________________________________________|
| | | 1 | Control vectors are included after the SLU name |
| | | | (bytes r+1-s). |
|_______|_____|___|______________________________________________________|
| | 7 | Half-duplex flip-flop reset states: |
|_______|_____|___ ______________________________________________________|
| | | 0 | HDX-FF reset state is RECEIVE for the primary and |
| | | | SEND for the secondary (e.g., the secondary sends |
| | | | normal-flow requests first after session activation) |
|_______|_____|___|______________________________________________________|
| | | 1 | HDX-FF reset state is SEND for the primary and |
| | | | RECEIVE for the secondary (e.g., the primary sends |
| | | | normal-flow requests first after session activation) |
| | | | (only value defined for LU 6.2) |
|_______|_____|___|______________________________________________________|
| | | Note: This bit is reserved unless either condition (1) |
| | | or conditions (2) and (3) hold. |
| | | |
| | | 1. The FM profile is 19. |
| | | 2. The normal-flow send/receive mode is half-duplex |
| | | flip-flop (byte 7, bits 0-1 = 10). |
| | | 3. Brackets are not used or the bracket state manager's |
| | | reset state is INB (byte 6, bit 2 = 0). |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| | | TS Usage |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 8 | 0 | Staging indicator for session-level pacing of the |
| | | secondary-to-primary normal flow: |
|_______|_____|___ ______________________________________________________|
| | | 0 | the secondary send window size (byte 8, bits 2-7) |
| | | | and the primary receive window size (byte 13, bits |
| | | | 2-7) are for one-stage (or APPN hop-by-hop) pacing |
| | | | (The secondary send window size is always equal to |
| | | | the primary receive window size.) |
|_______|_____|___|______________________________________________________|
| | | 1 | the secondary send window size (byte 8, bits 2-7) |
| | | | and the primary receive window size (byte 13, bits |
| | | | 2-7) are for two-stage pacing |
|_______|_____|___|______________________________________________________|
| | | Note: The meanings of 0 and 1 are reversed from the |
| | | corresponding staging indicator for the |
| | | primary-to-secondary normal flow. |
|_______|_____|__________________________________________________________|
| | 1 | Reserved |
|_______|_____|__________________________________________________________|
| | 2-7 | Secondary send window size, in binary, for session-level |
| | | pacing: a value of 0 indicates that there will be no |
| | | pacing of requests flowing from the secondary. |
|_______|_____|__________________________________________________________|
| | | Note: If pacing on a session stage in a particular |
| | | direction is not to be performed, the values for the |
| | | window size on that stage are set to 0. For example, if |
| | | there is to be no pacing in the secondary to primary |
| | | direction, the primary receive and secondary send window |
| | | sizes are both set to 0. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 9 | 0 | Adaptive session-level pacing support: |
|_______|_____|___ ______________________________________________________|
| | | 0 | adaptive pacing not supported by the sending node: |
| | | | pacing window values in bits 2-7 of bytes 8, 9, 12, |
| | | | and 13 specify the fixed value implied in each |
| | | | pacing response; a 0 value in bits 2-7 of bytes 8 |
| | | | and 13 specifies no pacing in the |
| | | | secondary-to-primary direction; a 0 value in bits |
| | | | 2-7 of bytes 9 and 12 specifies the maximum window |
| | | | size is requested |
|_______|_____|___|______________________________________________________|
| | | 1 | adaptive pacing supported by the sending node: |
| | | | pacing window values in bits 2-7 of bytes 8, 9, 12, |
| | | | and 13 specify the preferred minimum value for each |
| | | | ISOLATED PACING MESSAGE; a 0 value specifies that |
| | | | the preferred minimum value is as large as possible; |
| | | | each adaptive pacing partner initializes its own |
| | | | send window size to 1 at session activation |
| | | | |
|_______|_____|___|______________________________________________________|
| | | Note: If the PLU specifies adaptive pacing in BIND, and |
| | | the SLU is able to support adaptive pacing, the SLU |
| | | responds with this bit set to 1 in RSP(BIND). If the |
| | | PLU indicates it does not support adaptive pacing, or if |
| | | the SLU does not support adaptive pacing, this bit will |
| | | be set to 0 in RSP(BIND). |
|_______|_____|__________________________________________________________|
| | 1 | Reserved |
|_______|_____|__________________________________________________________|
| | 2-7 | Secondary receive window size, in binary, for |
| | | session-level pacing: a value of 0 causes the boundary |
| | | function (BF) to substitute the value set by a system |
| | | definition pacing parameter (if the system definition |
| | | includes such a parameter) before it sends the BIND RU |
| | | toward the secondary node; a value of 0 received at the |
| | | secondary from the BF is interpreted to mean no pacing |
| | | of requests flowing to the secondary. When fixed |
| | | session-level pacing is used (byte 9, bit 0 = 0), this |
| | | value is the fixed window size for the |
| | | primary-to-secondary direction of the session stage. |
| | | When adaptive session-level pacing is used (byte 9, bit |
| | | 0 = 1), this value is the preferred minimum window size |
| | | the primary end of the session stage recommends the |
| | | secondary end of the session stage place in the IPMs it |
| | | sends. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 10 | | Maximum RU size sent on the normal flow by the secondary |
| | | half-session. Bit 0 is interpreted as follows. |
| | | |
| | | 1. If bit 0 is set to 0, no maximum is specified and |
| | | the remaining bits 1-7 are ignored. |
| | | 2. If bit 0 is set to 1 (only value defined for LU |
| | | 6.2), the byte is interpreted as X'ab' = a×2(b) |
| | | (Notice that, by definition, a°8 and therefore X'ab' |
| | | is a normalized floating point representation.) See |
| | | Figure 6-1 for all possible values. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 11 | | Maximum RU size sent on the normal flow by the primary |
| | | half-session: identical encoding as described for byte |
| | | 10 |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 12 | 0 | Staging indicator for session-level pacing of the |
| | | primary-to-secondary normal flow: |
|_______|_____|___ ______________________________________________________|
| | | 0 | the primary send window size (byte 12, bits 2-7) and |
| | | | the secondary receive window size (byte 9, bits 2-7) |
| | | | are for two-stage pacing |
|_______|_____|___|______________________________________________________|
| | | 1 | the primary send window size (byte 12, bits 2-7) and |
| | | | the secondary receive window size (byte 9, bits 2-7) |
| | | | are for one-stage (or APPN hop-by-hop) pacing (The |
| | | | primary send window size is always equal to the |
| | | | secondary receive window size.) |
|_______|_____|___|______________________________________________________|
| | | Note: The meanings of 0 and 1 are reversed from the |
| | | corresponding staging indicator for the |
| | | secondary-to-primary normal flow (byte 8, bit 0). |
|_______|_____|__________________________________________________________|
| | 1 | Reserved |
|_______|_____|__________________________________________________________|
| | 2-7 | Primary send window size, in binary, for session-level |
| | | pacing: a value of 0 causes the value set by a system |
| | | definition pacing parameter (if the system definition |
| | | includes such a parameter) to be assumed for the |
| | | session; if this is also 0, it means no pacing of |
| | | requests flowing from the primary (For one-stage pacing |
| | | in the primary-to-secondary direction, this field is |
| | | redundant with, and will indicate the same value as, the |
| | | secondary receive window size--see byte 9, bits 2-7, |
| | | above.) |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 13 | 0-1 | Reserved |
|_______|_____|__________________________________________________________|
| | 2-7 | Primary receive window size, in binary, for |
| | | session-level pacing: a value of 0 means no pacing of |
| | | requests flowing to the primary (For one-stage pacing in |
| | | the secondary-to-primary direction, this field is |
| | | redundant with, and will indicate the same value as, the |
| | | secondary send window size--see byte 8, bits 2-7, |
| | | above.) |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| | | PS Profile |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 14 | 0 | PS Usage field format: |
|_______|_____|___ ______________________________________________________|
| | | 0 | basic format (only value defined) |
|_______|_____|___|______________________________________________________|
| | 1-7 | LU type: |
|_______|_____|_________ ________________________________________________|
| | | 0000000 | LU type 0 |
|_______|_____|_________|________________________________________________|
| | | 0000001 | LU type 1 |
|_______|_____|_________|________________________________________________|
| | | 0000010 | LU type 2 |
|_______|_____|_________|________________________________________________|
| | | 0000011 | LU type 3 |
|_______|_____|_________|________________________________________________|
| | | 0000100 | LU type 4 |
|_______|_____|_________|________________________________________________|
| | | 0000110 | LU type 6 |
|_______|_____|_________|________________________________________________|
| | | 0000111 | LU type 7 |
|_______|_____|_________|________________________________________________|
|_______ _____ __________________________________________________________|
| | | PS Usage field |
|_______|_____|__________________________________________________________|
| | | Note: The following format for bytes 15-25 applies only |
| | | to LU 6.2; for information on PS usage bytes 15-25 for |
| | | other than LU 6.2 (indicated by byte 14, bits 1-7 = |
| | | 0000110 and byte 15 = 00000010), see SNA: Sessions |
| | | Between Logical Units. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 15 | | LU-6 level: |
|_______|_____|_______ __________________________________________________|
| | | X'02' | Level 2 (i.e., LU 6.2) |
|_______|_____|_______|__________________________________________________|
|_______ _____ __________________________________________________________|
| 16-21 | | Reserved |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| | 22 | 0 | Extended security mechanism support: |
|_______|_____|___ ______________________________________________________|
| | | | 0 | Extended security mechanisms are not supported. |
|_______|_____|___|______________________________________________________|
| | | | 1 | At least one extended security mechanism is |
| | | | | supported. (And a structured data subfield X'14' is |
| | | | | present.) |
|_______|_____|___|______________________________________________________|
|_______ _____ __________________________________________________________|
| | 1 | Security extended sense data support: |
|_______|_____|___ ______________________________________________________|
| | | 0 | This RU sender does not support receipt of sense |
| | | | data values in the range X'080FFF00' to X'080FFFFF'. |
|_______|_____|___|______________________________________________________|
| | | 1 | This RU sender supports receipt of sense data values |
| | | | in the range X'080FFF00' to X'080FFFFF' (and it does |
| | | | not automatically send UNBIND for the session if it |
| | | | does not understand a sense data value that it |
| | | | receives in this range). |
|_______|_____|___|______________________________________________________|
|_______ _____ __________________________________________________________|
| | 2-7 | Reserved |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 23 | | Security Support Indicators |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| | 0-2 | Retired |
|_______|_____|__________________________________________________________|
| | 3 | Conversation-level security support: |
|_______|_____|___ ______________________________________________________|
| | | 0 | Access Security Information field will not be |
| | | | accepted on incoming FMH-5s. |
|_______|_____|___|______________________________________________________|
| | | 1 | Access Security Information field will be accepted |
| | | | on incoming FMH-5s. |
|_______|_____|___|______________________________________________________|
| | 4 | LU-LU verification protocol supported: |
|_______|_____|___ ______________________________________________________|
| | | 0 | basic verification protocol |
|_______|_____|___|______________________________________________________|
| | | 1 | enhanced verification protocol |
|_______|_____|___|______________________________________________________|
| | 5 | Password substitution support: |
|_______|_____|___ ______________________________________________________|
| | | 0 | not supported |
|_______|_____|___|______________________________________________________|
| | | 1 | supported |
|_______|_____|___|______________________________________________________|
| | 6 | Already-verified function support: |
|_______|_____|___ ______________________________________________________|
| | | 0 | Already-Verified indicator will not be accepted on |
| | | | incoming FMH-5s. |
|_______|_____|___|______________________________________________________|
| | | 1 | Already-Verified indicator will be accepted on |
| | | | incoming FMH-5s. |
|_______|_____|___|______________________________________________________|
| | 7 | Persistent verification capability: |
|_______|_____|___ ______________________________________________________|
| | | 0 | Persistent Verification indicator is not supported |
| | | | on incoming FMH-5s. |
|_______|_____|___|______________________________________________________|
| | | 1 | Persistent Verification indicator is supported on |
| | | | incoming FMH-5s. |
|_______|_____|___|______________________________________________________|
|_______ _____ __________________________________________________________|
| 24 | 0 | Reserved |
|_______|_____|__________________________________________________________|
| | 1-2 | Synchronization level: |
|_______|_____|____ _____________________________________________________|
| | | 01 | confirm is supported |
|_______|_____|____|_____________________________________________________|
| | | 10 | confirm, sync point, and backout are supported |
|_______|_____|____|_____________________________________________________|
| | 3 | Reserved |
|_______|_____|__________________________________________________________|
| | 4-5 | Responsibility for session reinitiation (reserved when |
| | | bit 6 of this byte is set to 1): |
|_______|_____|____ _____________________________________________________|
| | | 00 | operator controlled |
|_______|_____|____|_____________________________________________________|
| | | 01 | primary half-session will reinitiate |
|_______|_____|____|_____________________________________________________|
| | | 10 | secondary half-session will reinitiate |
|_______|_____|____|_____________________________________________________|
| | | 11 | either may reinitiate |
|_______|_____|____|_____________________________________________________|
| | 6 | Parallel session support for LU-LU pair: |
|_______|_____|___ ______________________________________________________|
| | | 0 | not supported |
|_______|_____|___|______________________________________________________|
| | | 1 | supported |
|_______|_____|___|______________________________________________________|
| | 7 | Change Number of Sessions GDS variable flow support (set |
| | | to 1 if byte 24, bit 6 = 1): |
|_______|_____|___ ______________________________________________________|
| | | 0 | not supported |
|_______|_____|___|______________________________________________________|
| | | 1 | supported |
|_______|_____|___|______________________________________________________|
|_______ _____ __________________________________________________________|
| 25 | 0 | Reserved |
|_______|_____|__________________________________________________________|
| | 1 | Limited-resource session indicator: |
|_______|_____|___ ______________________________________________________|
| | | 0 | not a limited-resource session and thus the |
| | | | contention-winner LU will not deactivate it when it |
| | | | is no longer busy |
|_______|_____|___|______________________________________________________|
| | | 1 | a limited-resource session and thus the |
| | | | contention-winner LU will deactivate it when it is |
| | | | no longer busy |
|_______|_____|___|______________________________________________________|
| | 2-5 | Reserved |
|_______|_____|__________________________________________________________|
| | 6-7 | Length-checked compression options: |
|_______|_____|___ ______________________________________________________|
| | | 00| no compression |
|_______|_____|___|______________________________________________________|
| | | 01| compression supported by the PLU -- compression to |
| | | | be determined by the SLU |
|_______|_____|___|______________________________________________________|
| | | | Note: This value indicates that the PLU supports |
| | | | compression but the PLU does not have any |
| | | | information that would indicate that this session |
| | | | would benefit from compression. |
|_______|_____|___|______________________________________________________|
| | | 10| reserved |
|_______|_____|___|______________________________________________________|
| | | 11| compression requested by the PLU |
|_______|_____|___|______________________________________________________|
| | | | Note: This value indicates that the PLU both |
| | | | supports and desires compression on this session. |
|_______|_____|___|______________________________________________________|
| | | Note 1: On extended BINDs, the Length-Checked |
| | | Compression (X'66') control vector serves to define the |
| | | requested compression options. |
|_______|_____|__________________________________________________________|
| | | Note 2: Bits 6-7, as defined, apply also to LU types 0, |
| | | 1, 2, 3, and 6.1. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| | | End of PS Usage Field |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 26-k | | Cryptography Options |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| 26 | 0-1 | Private cryptography options (reserved for LU 6.2): |
|_______|_____|____ _____________________________________________________|
| | | 00 | no private cryptography supported |
|_______|_____|____|_____________________________________________________|
| | | 01 | private cryptography supported: the session |
| | | | cryptography key and cryptography protocols are |
| | | | privately supplied by the end user |
|_______|_____|____|_____________________________________________________|
| | 2-3 | Session-level cryptography options: |
|_______|_____|____ _____________________________________________________|
| | | 00 | no session-level cryptography supported |
|_______|_____|____|_____________________________________________________|
| | | 01 | session-level selective cryptography supported; all |
| | | | cryptography key management is supported by the |
| | | | SSCP and LU; exchange (via +RSP(BIND)) and |
| | | | verification (via CRV) of the cryptography |
| | | | session-seed value is supported by the LUs for the |
| | | | session; all FMD requests carrying ED are |
| | | | enciphered/deciphered by the TCs |
|_______|_____|____|_____________________________________________________|
| | | 10 | reserved |
|_______|_____|____|_____________________________________________________|
| | | 11 | session-level mandatory cryptography supported; all |
| | | | cryptography key management is supported by the |
| | | | SSCP and LU; exchange (via +RSP(BIND)) and |
| | | | verification (via CRV) of the cryptography |
| | | | session-seed value is supported by the LUs for the |
| | | | session; all FMD requests are enciphered/deciphered |
| | | | by TC |
| | | | |
|_______|_____|____|_____________________________________________________|
| | 4-7 | Session-level cryptography options field length: |
|_______|_____|______ ___________________________________________________|
| | | X'0' | no session-level cryptography specified; |
| | | | following additional cryptography options fields |
| | | | (bytes 27-k) omitted |
|_______|_____|______|___________________________________________________|
| | | X'9' | session-level cryptography specified; additional |
| | | | options follow in next nine bytes |
|_______|_____|______|___________________________________________________|
|_______ _____ __________________________________________________________|
| 27 | 0-1 | Session cryptography key encipherment method: |
|_______|_____|____ _____________________________________________________|
| | | 00 | session cryptography key enciphered under SLU |
| | | | master cryptography key using a seed value of 0 |
| | | | (only value defined) |
|_______|_____|____|_____________________________________________________|
| | 2-4 | Reserved |
|_______|_____|__________________________________________________________|
| | 5-7 | Cryptography cipher method: |
|_______|_____|_____ ____________________________________________________|
| | | 000 | block chaining with seed and cipher text feedback, |
| | | | using the Data Encryption Standard (DES) algorithm |
| | | | (only value defined) |
|_______|_____|_____|____________________________________________________|
|_______ _____ __________________________________________________________|
| 28-k | | Session cryptography key enciphered under secondary LU |
| | | master cryptography key; an 8-byte value that, when |
| | | deciphered, yields the session cryptography key used for |
| | | enciphering and deciphering FMD requests |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| k+1-m | | Network Services (NS) Primary LU Name Field (always |
| | | present) |
| | | |
| | | This parameter is always network-qualified for |
| | | implementations at the current level of SNA; back-level |
| | | implementations may omit the network ID. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| k+1 | | Length of primary LU name (values 1 to 17 are valid) |
|_______|_____|__________________________________________________________|
| | | Note: Value 0 is retired. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| k+2-m | | Primary LU name or, if the secondary LU issued an |
| | | INIT-SELF (or INIT-OTHER), the uninterpreted name as |
| | | carried in that RU (and also in CDINIT for a |
| | | cross-domain session) |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| m+1-n | | User Data Field |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| m+1 | | Length of user data |
|_______|_____|__________________________________________________________|
| | | Note: X'00' = no User Data field present; if |
| | | unstructured user data present, values 1 to 65 are |
| | | valid. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| m+2-n | | User Data |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| m+2 | | User data key: |
|_______|_____|_______ __________________________________________________|
| | | X'00' | Structured subfields follow (only value defined |
| | | | for LU 6.2). |
| | | | Note: Individual structured subfields may be |
| | | | omitted entirely. When present, they appear in |
| | | | ascending subfield-number order. |
|_______|_____|_______|__________________________________________________|
| | | ¬X'00'| First byte of unstructured user data. |
|_______|_____|_______|__________________________________________________|
|________________________________________________________________________|
| For unstructured user data: |
|________________________________________________________________________|
|_______ _____ __________________________________________________________|
| m+3-n | | Remainder of unstructured user data |
|_______|_____|__________________________________________________________|
|________________________________________________________________________|
| For structured user data: |
|________________________________________________________________________|
|_______ _____ __________________________________________________________|
| m+3-n | | Structured subfields
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| n+1-p | | User Request Correlation Field (present only if carried |
| | | in INIT from SLU, or if Secondary LU name field or |
| | | control vectors are included) |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| n+1 | | Length of user request correlation (URC) field (values 0 |
| | | to 12 are valid) |
|_______|_____|__________________________________________________________|
| | | Note: X'00' = no URC present. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| n+2-p | | URC: LU-defined identifier (present only if carried in |
| | | INIT from SLU) |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| p+1-r | | Network Services (NS) Secondary LU Name Field (always |
| | | present for negotiable BINDs; optionally present for |
| | | nonnegotiable BINDs that include control vectors; |
| | | otherwise, omitted) |
| | | |
| | | This parameter is always network-qualified for |
| | | implementations at the current level of SNA; back-level |
| | | implementations may omit the network ID. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| p+1 | | Length of secondary LU name (values 1 to 17 are valid) |
|_______|_____|__________________________________________________________|
| | | Note: Value 0 is retired. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| p+2-r | | Secondary LU name |
|_______|_____|__________________________________________________________|
|________________________________________________________________________|
| Bytes r+1-s are included only if byte 7, bit 6 specified that control |
| vectors are included after the SLU name. |
|________________________________________________________________________|
|_______ _____ __________________________________________________________|
| r+1-s | | Control vectors | |
|_______|_____|__________________________________________________________|
| | | Note: The following control vectors may be included; |
| | | they are parsed according to subfield parsing rule KL |
| | | | |_______|_____|_______ __________________________________________________|
| | | X'0E' | Network Name control vector: PLU network name, |
| | | | X'F3' (present in extended BINDs when bytes |
| | | | k+2-m contain a name that is not |
| | | | network-qualified, such as an uninterpreted |
| | | | name) |
|_______|_____|_______|__________________________________________________|
| | | X'0E' | Network Name control vector: network-qualified |
| | | | CP name, X'F4' (present in extended BINDs sent |
| | | | from nodes at the current level of SNA for |
| | | | PLU-inititated sessions when the Fully Qualified |
| | | | PCID (X'60') control vector does not contain the |
| | | | real CP(PLU) name and the real CP(PLU) name is |
| | | | known) |
|_______|_____|_______|__________________________________________________|
* | | | X'27' | XRF Session Activation control vector |
|_______|_____|_______|__________________________________________________|
* | | | Note: Control vector X'27' specifies that an XRF-active |
* | | | or XRF-backup session is to be activated. |
|_______|_____|_______ __________________________________________________|
| | | X'2B' | Route Selection control vector (present in |
| | | | extended BINDs when the BIND sender has the |
| | | | information available as the result of a Locate |
| | | | search and the session-route calculation) |
|_______|_____|_______|__________________________________________________|
| | | X'2C' | COS/TPF control vector (present in extended |
| | | | BINDs when the BIND sender supports mode-to-COS |
| | | | mapping or when it received the control vector |
| | | | on a Locate search reply) |
|_______|_____|_______|__________________________________________________|
| | | X'2D' | Mode control vector (present in non-LU6.2 |
| | | | extended BINDs unless the default mode name -- |
| | | | eight X'40' characters -- is intended) |
|_______|_____|_______|__________________________________________________|
| | | X'60' | Fully Qualified PCID control vector (in which |
| | | | case the BIND is called an extended BIND) |
|_______|_____|_______|__________________________________________________|
| | | X'66' | Length-Checked Compression control vector |
| | | | (present in extended BINDs when compression is |
| | | | supported) |
|_______|_____|_______|__________________________________________________|
| | | Note: The receiving LU simply ignores unrecognized |
| | | control vectors. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| Note: | | The length of the BIND RU cannot exceed 256 or 512 |
| | | bytes. The length of the basic BIND RU is restricted to |
* | | | 256 bytes including the X'0E', X'2C', X'2D', and X'60' |
| | | control vectors; any additional control vectors may |
| | | cause the length to increase up to 512 bytes. |
|_______|_____|__________________________________________________________|
|_______ _____ __________________________________________________________|
| Note: | | If the last byte of a Format 0 BIND request not having |
| | | control vectors is a length field and that field is 0, |
| | | that byte may be omitted from the BIND request. |
|_______|_____|__________________________________________________________|
_________________________________________________________
| |
| Mantissa (a) |
| |
__________|_________________________________________________________|
| | |
| Exponent | 8 9 A B C D E F |
| (b) | (10) (11) (12) (13) (14) (15)|
| | |
|__________|_________________________________________________________|
| 0 | 8 9 10 11 12 13 14 15 |
|__________|_________________________________________________________|
| 1 | 16 18 20 22 24 26 28 30 |
|__________|_________________________________________________________|
| 2 | 32 36 40 44 48 52 56 60 |
|__________|_________________________________________________________|
| 3 | 64 72 80 88 96 104 112 120 |
|__________|_________________________________________________________|
| 4 | 128 144 160 176 192 208 224 240 |
|__________|_________________________________________________________|
| 5 | 256 288 320 352 384 416 448 480 |
|__________|_________________________________________________________|
| 6 | 512 576 640 704 768 832 896 960 |
|__________|_________________________________________________________|
| 7 | 1024 1152 1280 1408 1536 1664 1792 1920 |
|__________|_________________________________________________________|
| 8 | 2048 2304 2560 2816 3072 3328 3584 3840 |
|__________|_________________________________________________________|
| 9 | 4096 4608 5120 5632 6144 6656 7168 7680 |
|__________|_________________________________________________________|
| A (10) | 8192 9216 10240 11264 12288 13312 14336 15360 |
|__________|_________________________________________________________|
| B (11) | 16384 18432 20480 22528 24576 26624 28672 30720 |
|__________|_________________________________________________________|
| C (12) | 32768 36864 40960 45056 49152 53248 57344 61440 |
|__________|_________________________________________________________|
| D (13) | 65536 73728 81920 90112 98304 106496 114688 122880 |
|__________|_________________________________________________________|
| E (14) | 131072 147456 163840 180224 196608 212992 229376 245760 |
|__________|_________________________________________________________|
| F (15) | 262144 294912 327680 360448 393216 425984 458752 491520 |
|__________|_________________________________________________________|
Note: A value of X'ab' in byte 10 or byte 11 of BIND represents
a*2**b
.
For example, X'C5' represents (in decimal)
12*2**5
= 384.
Figure 6-1. RU Sizes Corresponding to Values X'ab' in BIND