z/OS Communications Server: SNA Programming
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Session parameter fields (BIND image)

z/OS Communications Server: SNA Programming
SC27-3674-00

The displacements indicated in Figure 1 refer to the ISTDBIND DSECT. The displacements are 1 greater in the actual BIND RU, because the BIND RU contains a request code that is not contained in the ISTDBIND DSECT. Note that the BIND image field in the CINIT RU also does not contain the BIND request code.

The format of the session parameter fields is shown in Figure 1. A description of each field follows.

Figure 1. Format of session parameters area (BIND image)
The diagram shows the format of the session parameters area (BIND image). The dashed vertical line in the diagram indicates continuation of the field to the next line.
Note: When session parameters are part of the BIND or CINIT RU, the primary- logical-unit-name length field can have a value ranging 1–8, thus changing the displacements of the user-data-length and user-data fields. Similarly, for these RUs, the cryptographic-control field can be a variable-length field and thus alter succeeding displacements. For session parameters received in INQUIRE OPTCD=SESSPARM or in the SCIP exit routine (pointed to by word 4 of the exit parameter list), the primary-logical-unit name field is always 8 bytes long. The associated length field is set to 8 (or 0). Also, in these cases, the cryptographic-control field is always 1 byte long. Therefore, the displacements shown in this figure are correct.

Although the PLU name can be 1-17 bytes in the BIND RU, the ISTDBIND DSECT requires it to be exactly 8 bytes. This causes the offset of the user data field to vary in the BIND RU but not in the BIND DSECT. The area provided by VTAM® to the SCIP exit will have an 8 in the PLU name length field and the name may be padded with blanks or truncated, if necessary. VTAM requires the bind area to be in this format when it is supplied by the application on an OPNDST or OPNSEC macroinstruction. Also note that in the case of a BIND error, the offset contained in sense code 0835nnnn is adjusted, if necessary, when given to the application to parse the BIND DSECT. See BIND area format and DSECT for information about these session parameters.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014