SNAX/HLS Configuration and Control Manual

Using HLSCMI to Create a SNAX Loop-Back Environment

Installing SNAX/HLS

104705 Tandem Computers Incorporated 3–13

The procedure automatically assigns LU names of the form:

where

is the PU number (0, 1, 2, ...) and

is the LU number (0, 1, 2, ...). The

procedure lists the names of the LUs it defines. For example, the following statement

creates eight LUs on three PUs on primary line $SNA1 to secondary line $SNA2:

HLSCMI PRI $SNA1, SEC $SNA2, LU 8

SNAX-HLS/HLSCMI - (T9089C10 15Mar88 b20)

Creating LoopBack configuration...

Primary line is $sna1

Secondary line is $sna2

There are 8 LUs on 3 PUs, named as follows:

#P0L0 #P0L1 #P0L2 #P0L3 #P0L4 #P0L5 #P0L6 #P0L7

#P1L0 #P1L1 #P1L2 #P1L3 #P1L4 #P1L5 #P1L6 #P1L7

#P2L0 #P2L1 #P2L2 #P2L3 #P2L4 #P2L5 #P2L6 #P2L7

The names of SNAX/XF line and SNAX/XF LUs are needed for SNAX/HLS program

execution (for example, a SNAX/XF LU name is used in OPEN-SESSION and

HLS-ALLOCATE verbs). The system programmer should therefore document the

SNAX/XF environment for the application programmers. Important things to

consider at this point are the following:

If a loopback configuration is used, PU and LU addresses must match on both the

primary and secondary line.

The specification of LU translation might conflict with the application

assumptions. It is recommended that character-set translation, if needed, be

performed by SNAX/HLS. Refer to Section 2, “Planning the SNAX/HLS

Environment,” for more information.