Expand Configuration and Management Manual (H06.21+, J06.10+)

Configuring Expand-Over-SNA Lines

Expand Configuration and Management Manual — 529522-013

11 - 8

Step 2: Add the LUs for the SNAX/APN Line

You must configure a local and a remote logical unit (LU) for the SNAX/APN line. The

Expand-over-SNA line-handler process is configured to use a particular local LU.

You use the SNAX/APN subsystem SCF ADD LU command to add the local LU. For

example, this command creates a local LU with a subdevice name of #LLUA for the

SNAX/APN line $SNAPA:

-> ADD LU $SNAPA.#LLUA, TYPE (14,21), SNANAME LUA, PROTOCOL NAM, &

DLUNAME #RLUA, RSPTYPE ER

Before you can add the remote LU, you must add a remote physical unit (PU); the

remote LU will be subordinate to this PU. You use the SNAX/APN SCF ADD PU

command to add a remote PU. For example, this command creates a remote PU with

a subdevice name of #RPUA for the SNAX/APN line $SNAPA:

-> ADD PU $SNAPA.#RPUA, TYPE (13,21), ADDRESS %HC1, RECSIZE 521, &

MAXLUS 30

After you have created the remote PU, you use the SNAX/APN subsystem SCF ADD

LU command to add the remote LU. For example, this command creates a remote LU

with a subdevice name of #RLUA for the SNAX/APN line $SNAPA:

-> ADD LU $SNAPA.#RLUA, TYPE (14,21), SNANAME LUB, PUNAME #RPUA

For details about configuring LUs and PUs, and SCF ADD LU and ADD PU command

attributes, see the SNAX/XF and SNAX/APN Configuration and Management Manual.

Considerations

This configuration considerations apply to local LU object attributes:

•

The PROTOCOL attribute must be set to NAM.

•

The local SNANAME on one system must match the remote LU SNANAME on the

other system.

•

If the local LU is to initiate sessions, DLUNAME must be defined (matching the last

part of the remote LU object name). If the remote PU has DYNAMIC ON, remote

LUs will always be able to initiate sessions. However, DLUNAME must be specified

in one of the two systems in order for the connection to become active.