SNAX/HLS Configuration and Control Manual

Step 5. Planning for Programming Standards
Planning the SNAX/HLS Environment
104705 Tandem Computers Incorporated 2–29
.
. CALL PROCESS^BIND^CINIT^DATA;
DT^SESSION^CLOSED ->
.
. ! This message signals that your partner has closed the
. ! session. This can occur if you separately allocate
. ! and open your session (that is, you used HLS-ALLOCATE
. ! and HLS-OPEN).
.
. CALL PROCESS^PARTNER^CLOSURE;
DT^FLOW^CONTROL ->
.
. ! This message signals receipt of a flow control message.
. ! This can occur only if you have enabled receipt of such
. ! messages, either through a PROFILE attribute, or by
. ! issuing a selected set of flow control requests.
. !
. CALL PROCESS^FLOW^CONTROL;
DT^BID^REJECTED ->
.
. ! This message signals that your partner attempted to
. ! begin a bracket and the attempt was rejected with a
. ! sense code of 0814. This message can occur only
. ! if your PROFILE specifies USER for the BID-REJECTION
. ! attribute and you are the first speaker.
. !
. ! As soon as you are willing to let your partner begin
. ! brackets, issue HLS-FLOW-CONTROL (RT).
END ! of case statement !;
Use of the CONVERT-ERROR-CODE Verb
The following question arises in SNAX/HLS application programming: What do you
do if RETURN-CODE does not equal RC-OK? While the answer is application-specific,
the CONVERT-ERROR-CODE verb offers significant functions to the application
programmer. SNAX/HLS is delivered with a standard file, HLSMSGS, that is used to
format CONVERT-ERROR-CODE replies. Included in the file is message text for
RETURN-CODES and SNA error codes as well as the RETRY-ACTION-CODE. In
addition, the SNA error-code entries can specify whether the occurrence of the error
should be logged. Installations are free to alter the message texts and the value of
RETRY-ACTION-CODE to local standards on a message-by-message basis by editing
the HLSMSGS file. However, if edits are performed, they have to be reapplied on each
new release of SNAX/HLS.