Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Receiving a BIND request z/OS Communications Server: SNA Programming SC27-3674-00 |
|
When a BIND request is received, VTAM® schedules the SCIP exit routine unless the SCIP exit routine is being held by SETLOGON OPTCD=HOLD. If SCIP exits are being held, an exit for the BIND request is scheduled after the next SETLOGON OPTCD=START. The exit parameter list provides the CID of the session to be established. This CID can be used to identify the BIND that is to be accepted by OPNSEC or rejected by SESSIONC CONTROL=BIND. The BIND request that is passed to the SCIP exit routine contains the PLU name. For information about uninterpreted PLU names, see OPNDST macroinstruction and SESSIONC macroinstruction with CONTROL=BIND. The exit parameter list also provides a user-request correlator. If the application program initiates the session with the REQSESS macroinstruction, the correlator field has the same value as the USERFLD field in the NIB at the time REQSESS is issued. Otherwise, the field is 0. The field provides a means for the application program to determine if the BIND is caused by a REQSESS macroinstruction and if so, which one. A read-only RPL is also provided to the exit routine. The AREA field in this RPL points to a read-only copy of the BIND request. The RPL's RECLEN field contains the length of the request. For a description of the BIND request unit, refer to SNA Formats. BIND session parameters are also discussed in Specifying a session parameter. Certain information can appear in control vectors appended
to the BIND RU.
|
Copyright IBM Corporation 1990, 2014
|