gtps2m36 | ACF/SNA Data Communications Reference |
Define the ALS name of the 37x5 channel adapter to the TPF system. The name of the ALS resource in the TPF resource definition must be identical to the name on the PU statement in the NCP generation deck.
See Defining SNA Resources to the TPF System for more information about defining ALS resources to the TPF system.
The following items must be specified in an NCP gen to define a channel-attached TPF system as a PU 2.1 node:
You must define the control point (CP) name of the VTAM system that owns the 37x5 to the TPF system. If you have backup VTAM systems capable of owning the 37x5, define to the TPF system the CP names of these VTAM systems using the LUTYPE=REMCP option in the OSTG RSC statement or using dynamic LU support. The CP name in the TPF resource definition must be identical to the value of the SSCPNAME start option in the VTAM system.
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.
When the TPF system is operating in APPN mode, you do not need to predefine TPF resources (LUs) to the NCP or to VTAM. Instead, the TPF system registers its resources with the APPN network when you bring up the network.
When the TPF system is operating in LEN mode, all TPF SLU resources (TPF SLU threads, FMMR, and CLU resources) must be defined in the NCP generation deck of the channel-attached NCP. The NCP generation deck is used by VTAM to define TPF SLU resources. For an example of the definitions of SLU resources, see Figure 92.
When the TPF system is operating in LEN mode, you must define all TPF PLU resources (TPF PLU applications) in the NCP generation deck of the channel-attached NCP. These names must have a 1-character CPU ID suffix of the TPF host with which the names are associated and the 2-byte hexadecimal number (X'00'-X'FF') associated with this ALS. This number must match the ALSQN parameter on the ALS macro in OSTG because of the VTAM restriction that all PLU names must be defined before they can issue a BIND request. VTAM does not support dynamic discovery of independent PLUs. The reason for the suffixing is that there is no multiple peripheral node support in VTAM or NCP; to make the PLU name unique per host per ALS, the 4-character PLU name must have a suffix. Figure 92 contains sample alias names for PLU resources. Resource GMT1B30 is an example of how TPF application GMT1 is defined with suffix B30, where B is the CPUID and 30 is the ALSQN.
See Figure 92 for a sample definition of an NCP generation deck with the TPF system channel-attached as a PU type 2.1 LEN node.
Figure 92. NCP Gen with TPF Channel-Attached as a PU Type 2.1 LEN Node
********************************************************************** * BUILD MACRO FOR N30H521 * *********************************************************************** N30H521 BUILD MODEL=3745, * SUBAREA=511, * TYPGEN=NCP, * BFRS=80, * MAXSESS=1000, * NEWNAME=N30H521, * PUNAME=N30H521, * NETID=VTAMNET, * SALIMIT=1023, * SLODOWN=12 * ******************************************************** * LINE FOR REMOTE PS/2 FOR LU6.2 * ******************************************************** * L3027S LINE ADDRESS=27, * CLOCKNG=EXT, * SPEED=9600, * DUPLEX=FULL, * ISTATUS=INACTIVE, * SSCPFM=USSSCS, * MODETAB=LU62MOD1, * DLOGMOD=TPFLU62 * SERVICE ORDER=(P3027A) P3027A PU ADDR=C1, * PUTYPE=2, * ANS=STOP, * MAXDATA=265, * MAXOUT=7, * PASSLIM=8, * PACING=7, * XID=YES, * RETRIES=(,1,4) * T3027A01 LU LOCADDR=0,ISTATUS=ACTIVE,RESSCB=10 * ***************************************************** * CHANNEL DEFINITION FOR TPF PROCESSOR B PU2.1 * ***************************************************** L30CA4B LINE ADDRESS=(11), * CASDL=420, * TRANSFR=52, * DELAY=0, * INBFRS=4, * ISTATUS=INACTIVE, * TIMEOUT=120 * P30CA4B PU PUTYPE=2, * ANS=CONT * CLUBB004 LU LOCADDR=0,RESSCB=1,ISTATUS=ACTIVE GMT1B30 LU LOCADDR=0,RESSCB=100,ISTATUS=ACTIVE,DLOGMOD=TPF3270 NEFBB30 LU LOCADDR=0,RESSCB=100,ISTATUS=ACTIVE ZZZZB004 LU LOCADDR=0,RESSCB=1,ISTATUS=ACTIVE ZZZZB006 LU LOCADDR=0,RESSCB=1,ISTATUS=ACTIVE PPPPB001 LU LOCADDR=0,RESSCB=1,ISTATUS=ACTIVE, * MODETAB=LU62MOD1,DLOGMOD=TPFLU62 PPPPB002 LU LOCADDR=0,RESSCB=1,ISTATUS=ACTIVE, * MODETAB=LU62MOD1,DLOGMOD=TPFLU62 *
The VTAM logon manager application is used when the TPF system is operating in LEN mode. When you migrate the TPF system to APPN mode, the VTAM logon manager application is no longer used; therefore, if the TPF system is operating in APPN mode, the following information does not apply.
Users on a PU 2.1 or PU 5 CTC connection can LOGON RES0 and have RES0 as an application controlled by the Logon Manager. The Logon Manager then forwards the SESINIT to the TPF CLU on behalf of the SLU for the TPF PLU RES0. TPF suffixes the PLU name in the BIND to make it unique within the network.