SNAX/HLS Application Programming Manual

Procedure Specifications
Customization
104707 Tandem Computers Incorporated 7–23
bind^rq
points to the BIND RU received by SNAX/HLS.
bind^rq^len
defines the length (in bytes) of the BIND RU received by SNAX/HLS. Note that
this excludes the SNAX header, and can be in the range of 1 through 256.
bind^rsp
points to the positive BIND response built by SNAX/HLS.
bind^rsp^len
defines the length (in bytes) of the positive BIND response built by SNAX/HLS.
Note that this excludes the SNAX header, and can be in the range of 1 through 256.
sense
defines SNA sense data returned for the BIND request. A nonzero value would
result in SNAX/HLS sending a negative response for the BIND request with this
sense data. A zero would result in SNAX/HLS sending a positive response of 4
bytes for the BIND request.
A BIND template is provided in the TAL definitions file, HLSDDT, to ease the parsing
of the BIND request.
The profile name can be used as a means to identify the type of session, and the
routine can reject the BIND if its attributes do not match for this session. Note that the
attributes may be legal for SNA, but not the application.
The PLU-NAME and USER-DATA fields of the BIND RU are in ACSII.
The user-exit routine must not modify the profile^name, the bind^rq, the bind^rsp, or
the bind^rsp^len arguments. The only argument this routine can modify is the
routine itself.