BIND response

The BIND request from the PLU includes session parameters that specify the protocols to be used on the session. The BIND can be negotiable or non-negotiable. If it is non-negotiable, the SLU application program must accept the BIND as it is, or reject it. It cannot modify the session parameters. If the BIND is negotiable, the application program can modify the session parameters and return them to the PLU in a negotiable BIND response. To send a negotiable BIND response, the application program must issue OPNSEC with PROC=NEGBIND specified in the NIB, with the BNDAREA field in the NIB pointing to the session parameters and user data to send to the PLU. The ISTDBIND DSECT can be used to map this area. If no changes to the BIND are required, then PROC=NNEGBIND, or BNDAREA=0 can be specified in the NIB to send a non-negotiable response to the BIND, indicating to the PLU that the original BIND session parameters are acceptable. The application program cannot send a negotiable BIND response to a non-negotiable BIND request. If PROC=NEGBIND is specified on the OPNSEC macroinstruction for a non-negotiable BIND request, the OPNSEC macroinstruction is rejected with (RTNCD,FDB2)=(X'14',X'74'); a BIND request rejected response with sense code=X'08010000' is sent to the PLU. See Table 1 for a description of OPNSEC macroinstruction PROC options used to send the BIND response. See Specifying a session parameter, to determine which session parameters can be modified in a negotiable BIND response.