SNAX/HLS Application Programming Manual

HLS-ALLOCATE Verb
SNAX/HLS Verbs
104707 Tandem Computers Incorporated 5–15
PROFILE–NAME
identifies the name of a PROFILE. If the session is not yet allocated, this field must
be nonblank and contain a name of one of the entries in the currently defined RDT
to satisfy this PROFILE. If the session is already allocated but this field is blank, or
the field contains the same name as the one currently associated with the session,
the request is satisfied with no change.
If, however, all the following are true
The PROFILE–NAME field is nonblank
The name is different from that currently associated with the session
The session is not open
The PROFILE–NAME field identifies a valid PROFILE
The PIPELINE–LU–IND matches that required by the new PROFILE
then the old session is deallocated, and a new one is allocated with the same name
and SESSION–ID, and different PROFILE name.
Note Programmers should be careful using this facility with sessions where more than one program (or
instance thereof) has allocated the session, because the other sessions encounters
RC–SESSION–NOT–ALLOCATED conditions when they next attempt to access this session.
PIPELINE–LU–IND
identifies whether you acknowledge that you are using a pipeline LU. This is
essentially a sanity check; the setting of this attribute must agree with that given in
the PROFILE. The valid values are Y for yes, and N for no.
FUTURE
is reserved.
Reply Details
VERB–CODE
identifies the reply by an integer constant (of value 14), named as follows:
VERB–HLS–ALLOCATE (in SCOBOL)
VERB^HLS^ALLOCATE (in TAL)
SESSION–ID
contains one of the following:
0. There is no session ID because the SNAX/HLS server could not begin the
session. See the error response.
A nonzero value, which is the session ID of the new session.