SNAX/HLS Configuration and Control Manual

Step 5. Planning for Programming Standards

Planning the SNAX/HLS Environment

104705 Tandem Computers Incorporated 2–27

DT^INTERRUPT^REQUEST ->

. ! We have an interrupt message. The use of interrupt

. ! messages is application-specific.

. ! The important observation is not to process

. ! this message as a message from session partner.

. CALL PROCESS^INTERRUPT^MESSAGE;

DT^SSCP^DATA ->

. ! We have a message from the SSCP. The PROFILE must

. ! allow delivery of SSCP messages for us to get here.

. ! Again, the use of SSCP messages is application-

. ! specific. Do not process

. ! as a message from session partner.

. CALL PROCESS^SSCP^MESSAGE;

DT^PREPARED^TO^CLOSE ->

. ! Session partner is prepared to close the session.

. ! If we are a PLU, this confirms that our partner has

. ! received and responded to a PREPARE-TO-CLOSE verb.

. ! If we are an SLU, we must confirm this request by

. ! sending a PREPARE-TO-CLOSE verb when convenient.

. ! We assume that such activities

. ! are under the control of a flag such as shown below.

. TIME^FOR^PREPARE^TO^CLOSE := TRUE;

DT^LU^STATUS ->

. ! We have received a LUSTAT message from our partner.

. ! The sense codes might have a predefined meaning in SNA,

. ! or might be unique between session partners.

. ! See the SNA references listed in the Preface. We

. ! assume here that the status is not SNA defined and

. ! unique to the session partners.

. CALL PROCESS^PARTNER^STATUS;