gtps2m18ACF/SNA Data Communications Reference

TPF/APPC Installation Checklist

The following describes the tasks you must perform to use the TPF/APPC support.

General Installation Tasks

The following list contains the tasks that you must perform regardless of your network environment:

Installation Tasks for Low-Entry Networking (LEN)

The following tasks must be performed when the TPF system is operating in LEN mode; however, if the TPF system is operating in APPN mode, skip this section.

Defining TPF/APPC LUs to the Network

This section describes how to define a TPF/APPC LU to the network based on your configuration.

Defining LUs across a PU 5 Connection

To define TPF/APPC LUs across a PU 5 NCP connection, define the LUs to VTAM under the owning cross-domain resource manager (CDRM).

To define TPF/APPC LUs across a PU 5 CTC connection for a TPF system operating in APPN mode, also define the LUs to VTAM under the owning CDRM.

Figure 32 shows sample definitions for TPF/APPC primary LUs (PLUs) and secondary LU (SLU) threads. The real name of a TPF/APPC PLU is used.

Figure 32. Defining TPF/APPC LUs to VTAM across a PU 5 Connection


  TPFA       CDRM
  LU62       CDRSC
  LU62A001   CDRSC
  LU62A002   CDRSC
  LU62A003   CDRSC
  LU62A004   CDRSC
  LALA       CDRSC
  MONY       CDRSC
  MONYA001   CDRSC
  MONYA002   CDRSC
  MONYA003   CDRSC

Defining Alias LU Names across a PU 5 CTC Connection to VTAM

When the TPF system is operating in LEN mode, you must define an alias name to VTAM for each TPF/APPC PLU; however, when the TPF system is operating in APPN mode, do not define an alias name.

To define TPF/APPC alias LU names across a PU 5 CTC connection, define the alias LU names to VTAM under the owning CDRM. Define the LU alias name for a TPF/APPC PLU as a cross domain resource with the CDRSC statement. The format is: xxxxyzz CDRSC

Where:

xxxx
is the 4-character LU name.

y
is the 1-character CPU ID.

zz
is the 2-character qualifier number defined with the QN parameter on the OSTG CTC statement.

Figure 33 shows sample definitions for TPF/APPC PLUs and SLU threads. The alias name for a TPF/APPC PLU is used.

Figure 33. Defining TPF/APPC Alias LU Names to VTAM across a PU 5 CTC Connection


  TPFA       CDRM
  APPCA01    CDRSC
  APPCA001   CDRSC
  APPCA002   CDRSC
  APPCA003   CDRSC
  APPCA004   CDRSC
  DEADA01    CDRSC
  TPARA01    CDRSC

Defining LUs across a PU 2.1 LEN Connection

To define a TPF/APPC LU across a PU 2.1 LEN connection, do the following:

Defining LUs across a PU 2.1 APPN Connection

In an APPN network, LUs do not need to be predefined to the NCP or VTAM because an APPN node has the ability to register its LUs dynamically when links are activated. LUs can be predefined or registered dynamically in an APPN network. See LU-LU Sessions in an APPN Network for more information.

To define a TPF/APPC LU across a PU 2.1 APPN connection, do the following:

Defining TPF/APPC LUs to a VTAM Subsystem

The definition of an LU to a subsystem, such as CICS, depends on the convention used by the subsystem. TPF's LU 6.2 support follows the SNA protocol that is comparable to the LUTYPE62 as supported by CICS (see CICS/DOS/VS Intercommunication Facilities Guide). Figure 36 provides an example of the CICS definition for a TPF 6.2 logical unit.

Figure 36. Defining a TPF/APPC LU to CICS


 DFHTCT TYPE=SYSTEM,            REQUIRED               X
        ACCMETH=VTAM,           REQUIRED               X
        TRMTYPE=LUTYPE62,       REQUIRED               X
        FEATURE=SINGLE,         REQUIRED               X
        SYSIDNT=APPC            TPF LU NAME            X
        CONNECT=AUTO,           OPTIONAL               X
        TRMSTAT=TRANSCEIVE,     DEFAULT                X
        RUSIZE=256              DEFAULT

Defining a TPF/APPC LU to a PS/2 Workstation (Using a Generic Name)

See the following publications for information about defining LU 6.2 communications to OS/2.

For OS/2 1.30.1 or earlier, see:

For OS/2 1.30.2 or later, see: