gtps2m18 | ACF/SNA Data Communications Reference |
The following describes the tasks you must perform to use the TPF/APPC support.
The following list contains the tasks that you must perform regardless of your network environment:
There can be many TPF/APPC local LUs in a TPF system. 1 of the LUs defined is considered the default LU and is used by the TPF system for the following conditions:
The definition is done with the SIP MSGRTA macro and the offline
ACF/SNA table generation (OSTG) program. The output from the MSGRTA
macro consists of an ANT deck, which is then used as input to the OSTG
process. To define the default TPF/APPC LU, code the MSGRTA macro
as follows:
MSGRTA APLIC=appl,EDIT=CHDD,ASNA=APPC
To define additional TPF/APPC LUs, code the MSGRTA macro as
follows:
MSGRTA APLIC=appl,EDIT=CHDD,ASNA=LU62
In both macro statements, appl is the local LU name.
See Defining SNA Resources to the TPF System for more information about defining local TPF applications to the TPF system.
See Defining SNA Resources to the TPF System for more information about defining remote LU resources to the TPF system.
See the VTAM Resource Definition Reference and NCP/SSP/EP Resource Definition Reference for more information.
This is done with the RAMFIL statement in the system initialization program (SIP) deck. #CCBRU records are 4-KB records that are used to hold the checkpointed copies of the main storage conversation control blocks (CCBs). Enough records must be allocated to hold the number of CCBs allocated with the MAXCCB parameter of the SNAKEY macro in the SNA communications keypoint (CTK2, defined by the CK2SN data macro).
#SC1RU and #SC2RU records are 4-KB records that are used to hold the checkpointed copies of the main storage session control blocks (SCBs). Enough records must be allocated to hold the number of SCBs allocated with the MAXSCB parameter of the SNAKEY macro in CTK2.
#CMSIT records are 4-KB records that are used to hold the side information table needed for C language mapped conversations.
See TPF System Generation for more information about the SIP RAMFIL statement, and see TPF ACF/SNA Network Generation for more information about the SNAKEY macro and the number of records to define.
See TPF ACF/SNA Network Generation for details about the SNAKEY macro.
The TPNT contains the local transaction program name and the associated TPF E-type program segment that provides the application function. Use the ITPNT macro to define these programs. See TPF General Macros for details on this macro.
The side information table is used to identify a partner LU name, remote transaction program name, and mode name with a symbolic destination name. Use the side information table offline program (CHQI) to generate the table offline. See Generating the Side Information Table for Mapped Conversations for details on how to use this program. Use the ZNSID command to build or change the table online. See TPF Operations for details about this command.
See Considerations for a Loosely Coupled Environment for more information.
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.
This is done in OSTG when there will be TPF/APPC sessions across a CTC connection managed by the logon manager. Sessions across an ALS connection are always managed by the logon manager. There must be a CLU-logon manager session over each CTC connection if the logon manager will be used. See TPF ACF/SNA Network Generation for details about coding the CTC and ALS statements.
See Defining SNA Resources to the TPF System for more information about defining SNA resources to the TPF system.
See VTAM Resource Definition Reference for more information.
See NCP/SSP/EP Resource Definition Reference for more information.
See NCP/SSP/EP Resource Definition Reference for more information.
This section describes how to define a TPF/APPC LU to the network based on your configuration.
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 |
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:
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 |
To define a TPF/APPC LU across a PU 2.1 LEN connection, do the following:
Where:
Figure 34 shows sample definitions for TPF/APPC PLUs and SLU threads in 2 ALSs. The alias name for a TPF/APPC PLU is used.
Figure 34. Defining TPF/APPC LUs across PU 2.1 LEN Connections
P30CA4A PU PUTYPE=2 APPCA30 LU LOCADDR=0 APPCA005 LU LOCADDR=0 APPCA006 LU LOCADDR=0 APPCA007 LU LOCADDR=0 TPARA30 LU LOCADDR=0 AMFMA30 LU LOCADDR=0 P42CA4A PU PUTYPE=2 APPCA42 LU LOCADDR=0 APPCA008 LU LOCADDR=0 APPCA009 LU LOCADDR=0 APPCA010 LU LOCADDR=0 TPARA42 LU LOCADDR=0 AMFMA42 LU LOCADDR=0 |
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:
Figure 35 shows sample definitions for TPF/APPC PLUs and SLU threads in 2 ALSs.
Figure 35. Defining TPF/APPC LUs across PU 2.1 APPN Connections
P30CA4A PU PUTYPE=2 APPC LU LOCADDR=0 APPCA005 LU LOCADDR=0 APPCA006 LU LOCADDR=0 APPCA007 LU LOCADDR=0 TPAR LU LOCADDR=0 AMFM LU LOCADDR=0 P42CA4A PU PUTYPE=2 APPC LU LOCADDR=0 APPCA008 LU LOCADDR=0 APPCA009 LU LOCADDR=0 APPCA010 LU LOCADDR=0 TPAR LU LOCADDR=0 AMFM LU LOCADDR=0 |
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 |
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: