gtps2m37ACF/SNA Data Communications Reference

Non-37x5 Considerations

The TPF system connects to PU 2.1 devices other than 37x5 devices. Some of these devices, like a 3174 APPN controller or RISC System/6000 system, do not provide their ALS name in the XID during link activation. The TPF system creates an ALS name using the following format:

TPFxnnnn

Where:

x
is the 1-character CPU ID of the TPF processor.

nnnn
is the 4-character SDA number of the ALS channel adapter.

You must define the ALS names to the TPF system using the TPFxnnnn format described previously. See Defining SNA Resources to the TPF System for more information about defining ALS resources to the TPF system.

If a new symbolic device address (SDA) is required for a non-37x5 PU 2.1 device, you must add an IODEV macro with the parameter DVTYP=37x5 to the SIP deck. See the TPF System Generation for more information about the IODEV macro.

A VTAM system is not required for non-37x5 PU 2.1 devices that are channel-attached to the TPF system; however, consider a VTAM system for network management purposes.

Non-37x5 and APPN Considerations

You must define the control point (CP) name of the channel-attached PU 2.1 node to the TPF system using the LUTYPE=REMCP option in the OSTG RSC statement or using dynamic LU support.

See TPF ACF/SNA Network Generation for more information about the OSTG RSC statement. See Using Dynamic LU Support to Define SNA Resources for more information about dynamic LU support.

A VTAM system or other APPN network node that is a dependent LU server is required if there are dependent LUs attached to the non-37x5 device, and this device is only a dependent LU requester (not a server).

Non-37x5 and LEN Considerations

When the TPF system is connected to non-37x5 devices as a LEN node, only LU 6.2 sessions are supported and these sessions must be started by the remote LU, not by the TPF system. The remote LU 6.2 devices must, therefore, be independent LUs.

3174 Considerations