gtpm2m0tMigration Guide: Program Update Tapes

TPF Advanced Peer-to-Peer Networking (TPF/APPN) Support (APAR PJ19949)

The following section discusses the migration considerations for TPF Advanced Peer-to-Peer Networking (TPF/APPN) support.

Prerequisite APARs

See the APEDIT for APAR PJ19949 for information about prerequisite APARs.

Functional Overview

TPF/APPN support enables the TPF 4.1 system to connect to a Systems Network Architecture (SNA) network as an Advanced Peer-to-Peer Networking (APPN) end node (EN).

Before TPF/APPN support:

With TPF/APPN support, the TPF 4.1 system can connect as an APPN end node (EN). The APPN architecture defines how to manage resources and establish LU-LU sessions in a PU 2.1 network environment. Resources in the TPF 4.1 system no longer need to be predefined; the TPF system will register its resources when the network is activated. The TPF 4.1 system as an APPN node is able to initiate LU-LU session activation, and all LU types (not just LU 6.2) are supported across the different communications controllers.

TPF/APPN support also includes the SNA printer sharing function, which allows an SNA printer to be shared between the TPF 4.1 system and a remote host. When a TPF processor adds a message to the queue for a printer that is not in session with any TPF processor in the loosely coupled complex, the TPF 4.1 system will now send a request to the APPN network to establish a session with the desired printer. If the printer is already in session with a remote host, that remote host will be asked to release the session at its earliest convenience, allowing a new session to be established between the TPF 4.1 system and the printer. Before TPF/APPN support, an SNA printer could be shared by all the processors in a TPF loosely coupled complex, but not between the TPF 4.1 system and a remote host (remote TPF processor or other data host).

Architecture

A node in a PU 2.1 network can connect as one of three types:

Each APPN node in the network has a control point (CP). Each APPN network node (NN) has control sessions, called CP-CP sessions, with the control point in each adjacent APPN network node. Each APPN end node can be connected to multiple adjacent network nodes, but can have CP-CP sessions with only 1 network node. The network node with which an end node has CP-CP sessions is called the network node server (NNS) for that end node. An APPN end node (EN) registers its resources with its NNS using the CP-CP sessions.

Because the TPF 4.1 system is an APPN EN, it communicates with its NNS during the LU-LU session activation process. For an LU-LU session initiated by the TPF 4.1 system, the NNS will locate the remote LU and calculate the best route (path) that can be used by the session. For an LU-LU session initiated by the remote LU or remote operator, the NNS for the TPF 4.1 system will use the information that the TPF 4.1 system registered to return the correct routing information to the NNS of the remote LU. After an LU-LU session is active, the control points are no longer involved with the operation of that session; an active session in a TPF 4.1 system that is an APPN node is no different than an active session in a TPF 4.1 system that is a LEN node.

Operating Environment Requirements and Planning Information

To ensure that your TPF 4.1 system performs correctly with TPF/APPN support, you must establish the required operating environment. The following section describes hardware and software requirements specific to TPF/APPN support.

Operating Environment Requirements and Planning Information provides information about the minimum system configuration requirements that are necessary to operate the TPF 4.1 system. You may find it helpful to review that chapter along with the following information.

Hardware

There are no hardware requirements.

Software (Programming Requirements)

The following section contains information about software requirements.

Communication

The following section summarizes the communication changes.

Operating Environment for SNA-Based Communication

The TPF 4.1 system as an APPN end node can connect (channel-attach) to the following devices:

TPF/APPC support is required for TPF/APPN support because the TPF 4.1 system communicates with its network node server (NNS) using a pair of LU 6.2 sessions called control point to control point (CP-CP) sessions. See TPF ACF/SNA Data Communications Reference for information about installing TPF/APPC support.

Network Considerations  A TPF 4.1 system running loosely coupled in an APPN environment is viewed differently by the network than when it is running in a PU 5 or LEN environment. Table 89 summarizes the differences.

Table 89. TPF Loosely Coupled SNA Network Comparisons

TPF Node Type How Network Views the TPF 4.1 system Control Sessions
PU 5 Each TPF processor is viewed as a separate subarea node. One CDRM-CDRM session exists with each TPF processor.
PU 2.1 LEN Each link is viewed as connecting to a different TPF 4.1 system. One CLU-CLU session exists for every active link in the loosely coupled complex.
PU 2.1 APPN EN The entire complex is viewed as 1 node. CP-CP sessions exist with only 1 TPF processor in the loosely coupled complex.

Load balancing LU-LU sessions among the active processors in the loosely coupled complex is an important consideration. In most cases a given TPF application resides in all processors in the loosely coupled complex, not only for load balancing purposes but for availability if a processor fails. When running TPF/APPN support, only 1 processor in the loosely coupled complex has control sessions (CP-CP sessions), therefore, all LU-LU session initiation requests will flow into that 1 TPF processor. When a session initiation request is received, the UAPN user exit is invoked to select the TPF processor for the new LU-LU session. See TPF System Installation Support Reference for a complete description of the UAPN user exit.

Note:
For LU-LU sessions initiated by a remote primary LU (PLU), the network rather than the TPF 4.1 system will do the load balancing. The network will calculate the route for the session and the selected TPF processor will receive the BIND request.

Interface Changes

The following section summarizes interface changes.

C/C++ Language

There are no changes.

Configuration Constant (CONKC) Tags

There are no changes.

Control Program Interface (CINFC) Tags

There are no changes.

Copy Members

Table 90 summarizes copy member changes. This information is presented in alphabetic order by the name of the copy member.

Table 90. Changes to Copy Members for TPF/APPN Support

Copy Member Type CSECT Where Copy Member Is Located New, Changed, or No Longer Supported? Description of Change
CSX0 Control Program CCSNA1 Changed XID updated to process APPN links.
CSX1 Control Program CCSNA1 Changed XID updated to process APPN links.
CSX2 Control Program CCSNA1 Changed XID updated to process APPN links.
CS0A Control Program CCSNA1 Changed Build parameter list for link failure messages.
CS0B Control Program CCSNA4 Changed Process slowdown timers for NCP/ALS links.
CS0F Control Program CCSNA4 Changed Changed building extended UNBIND.
CS0H Control Program CCSNA1 Changed Set or reset NCP/ALS slowdown flags.
CS01 Control Program CCSNA1 Changed Build parameter list for link failure messages.
CS03 Control Program CCSNA1 Changed Reset NCP/ALS slowdown indicators.
CS05 Control Program CCSNA1 Changed Updated to process APPN links.
CS06 Control Program CCSNA1 Changed Search for CDRM alias name in an ACTCDRM.
CS08 Control Program CCSNA1 Changed Reset NCP/ALS slowdown indicators.
CS96 Control Program CCSNA3 Changed Allow message for a shared printer.
CT15 Control Program CCCTIN Changed Carve out space for APPN TAPST.

Fixed File Records

There are no changes.

Macros

The following section summarizes the macro changes. This information is presented in alphabetic order by the type of macro.

Advanced Program-to-Program Communications (APPC) Macros

There are no changes.

Communication Macros and Statements

Table 91 summarizes changes to the communication macros and statements. This information is presented in alphabetic order by the name of the communication macro or statement.

Table 91. Changes to Communication Macros or Statements for TPF/APPN Support

Communication Macro or Statement New, Changed, or No Longer Supported? Do You Need to Reassemble Programs?
CDRM Changed No
RSC Changed No
SNAKEY Changed Yes

Data Macros

Table 92 summarizes the data macro changes. This information is presented in alphabetic order by the name of the data macro.

Table 92. Changes to Data Macros for TPF/APPN Support

Data Macro New, Changed, or No Longer Supported? Do You Need to Reassemble Programs Using This Data Macro?
CK2SN Changed No
CVTEQ Changed No
CW0CC Changed No
CZ1SE Changed No
DLTEC Changed No
IFMH5 Changed No
IPCID New Not Applicable
ISCB Changed No
ITAPST New Not Applicable
NC0CB Changed No
PIUEQ Changed No
RC0AT Changed No
RR0RT Changed No
RV1VT Changed No
SNAEQ Changed No
ST0TB Changed Yes

General Macros

There are no changes.

Selected Equate Macros

There are no changes.

Structured Programming Macros (SPMs)

There are no changes.

System Initialization Program (SIP) Skeleton and Internal Macros (Inner Macros)

Table 93 summarizes the system initialization program (SIP) skeleton and internal macro changes. This information is presented in alphabetic order by the name of the SIP skeleton and internal macro. See TPF System Generation for a complete description of the SIP skeleton and internal macros. If the SIP skeleton and internal macro (inner macro) is changed, you must reassemble the SIP Stage I deck and run the appropriate job control language (JCL) jobs from the SIP Stage II deck.

Table 93. Changes to SIP Skeleton and Internal Macros for TPF/APPN Support

SIP Skeleton and Internal Macro New, Changed, or No Longer Supported?
SKANTD Changed
SPGLB Changed
SYSEQ Changed

System Initialization Program (SIP) Stage I Macros and Statements

Table 94 summarizes system initialization program (SIP) Stage I macro and statement changes. This information is presented in alphabetic order by the name of the SIP Stage I macro. See TPF System Generation for a complete description of the SIP Stage I macros. If the SIP Stage I macro is changed, you must run the appropriate job control language (JCL) jobs from the SIP Stage II deck.

See System Initialization Program (SIP) and System Generation Changes for a description of other system generation changes you must make for TPF/APPN support.

Table 94. Changes to SIP Stage I Macros and Statements for TPF/APPN Support

SIP Stage I Macro New, Changed, or No Longer Supported?
MSGRTA Changed

System Initialization Program (SIP) Stage II Macros

There are no changes.

System Communication Keypoint (SCK) Generation Macros

There are no changes.

System Macros

There are no changes.

System Macros (IBM Use Only)

There are no changes.

Segments

Table 95 summarizes segment changes. This information is presented in alphabetic order by the name of the segment.

Table 95. Changes to Segments for TPF/APPN Support

Segment Type Link-Edit Module (Where Offline Segment Is Linked) New, Changed, or No Longer Supported? Description of Change
CCIM Real-Time Assembler Not Applicable Changed Add new ALS error messages.
CHEA Real-Time Assembler Not Applicable Changed Do not process CP-CP sessions.
CHNT Real-Time Assembler Not Applicable Changed Do not allow MODE=CPSVCMG.
CHNV Real-Time Assembler Not Applicable Changed Do not allow MODE=CPSVCMG.
CHPR Real-Time Assembler Not Applicable Changed Do not allow MODE=CPSVCMG.
CHRF Real-Time Assembler Not Applicable Changed Process APPN reserved TP names.
CHRR Real-Time Assembler Not Applicable Changed Process MODE=CPSVCMG as special case.
CHRS Real-Time Assembler Not Applicable Changed Process MODE=CPSVCMG as special case.
CHRY Real-Time Assembler Not Applicable Changed Process MODE=CPSVCMG as special case.
CHSB Real-Time Assembler Not Applicable Changed Process CP-CP sessions.
CHSD Real-Time Assembler Not Applicable Changed Do not echo unrecognized control vectors.
CMTK Real-Time Assembler Not Applicable Changed Check for printer sharing.
CMTQ Real-Time Assembler Not Applicable Changed Add printer sharing support.
CMTS Real-Time Assembler Not Applicable Changed Clear new field in the node control block (NCB).
CMTZ Real-Time Assembler Not Applicable Changed Check for printer sharing.
CNAB Real-Time Assembler Not Applicable Changed Invoke APPN cleanup when a TPF processor fails.
CONN Real-Time Assembler Not Applicable Changed Determine if the application is processor shared.
CSBA Real-Time Assembler Not Applicable New Activate CP-CP sessions.
CSBB Real-Time Assembler Not Applicable New Build an APPN BIND request.
CSBC Real-Time Assembler Not Applicable New CP capabilities TP.
CSBD Real-Time Assembler Not Applicable New PCID table handler.
CSBE Real-Time Assembler Not Applicable New TAPST core table handler.
CSBF Real-Time Assembler Not Applicable New Add TG to TAPST table.
CSBG Real-Time Assembler Not Applicable New TAPST file record handler.
CSBH Real-Time Assembler Not Applicable New Request TG during link activation.
CSBI Real-Time Assembler Not Applicable New Receive network search TP.
CSBJ Real-Time Assembler Not Applicable New Request resource registration TP.
CSBK Real-Time Assembler Not Applicable New Topology update TP.
CSBL Real-Time Assembler Not Applicable New Build an APPN LOCATE.
CSBM Real-Time Assembler Not Applicable New APPN cycle-up processing.
CSBN Real-Time Assembler Not Applicable New Build GDS variables for LOCATE.
CSBO Real-Time Assembler Not Applicable New Send network search TP.
CSBP Real-Time Assembler Not Applicable New Process LOCATE from the network.
CSBQ Real-Time Assembler Not Applicable New Process LOCATE for new LU-LU session.
CSBR Real-Time Assembler Not applicable New Receive SIPCC requests.
CSBS Real-Time Assembler Not Applicable New Send SIPCC requests.
CSBT Real-Time Assembler Not Applicable New Process LOCATE from another TPF processor.
CSBU Real-Time Assembler Not Applicable New Interface to the UAPN user exit.
CSBV Real-Time Assembler Not Applicable New Validate LOCATE request.
CSBW Real-Time Assembler Not Applicable New Build LOCATE information.
CSBX Real-Time Assembler Not Applicable New Process newly activated or deactivated CP-CP session.
CSBZ Real-Time Assembler Not Applicable New APPN cleanup.
CSB0 Real-Time Assembler Not Applicable New Process the ZNAPN command.
CSCA Real-Time Assembler Not Applicable Changed Pass RVT information to the CSCB segment.
CSCB Real-Time Assembler Not Applicable Changed Verify RVT information before scheduling the SNA command.
CSCD Real-Time Assembler Not Applicable Changed SNABBEGS processing updated for APPN.
CSCI Real-Time Assembler Not Applicable Changed Process a BIND for the APPN LU-LU sessions.
CSCQ Real-Time Assembler Not Applicable Changed Clean up APPN information.
CSDV Real-Time Assembler Not Applicable Changed Process BIND time out.
CSEA Real-Time Assembler Not Applicable Changed Add code for CP-CP sessions.
CSEC Real-Time Assembler Not Applicable Changed Add code check for CP-CP sessions.
CSED Real-Time Assembler Not Applicable New Activate CP-CP sessions.
CSEF Real-Time Assembler Not Applicable Changed Add code for CP-CP sessions.
CSEL Real-Time Assembler Not Applicable Changed Add new APPN messages.
CSES Real-Time Assembler Not Applicable Changed Clear NCP/ALS slowdown indicators.
CSFQ Real-Time Assembler Not Applicable Changed Display control point (CP) information.
CSFR Real-Time Assembler Not Applicable Changed Display control point (CP) information.
CSFV Real-Time Assembler Not Applicable Changed Display control point (CP) information.
CSGA Real-Time Assembler Not Applicable Changed Invoke APPN cycle-up processing.
CSGB Real-Time Assembler Not Applicable Changed Process APPN links during restart.
CSGI Real-Time Assembler Not Applicable Changed Fill in APPN information in the resource vector table (RVT).
CSG0 Real-Time Assembler Not Applicable Changed Invoke APPN restart processing.
CSG2 Real-Time Assembler Not Applicable Changed Fill in APPN information in the resource vector table (RVT).
CSG9 Real-Time Assembler Not Applicable New Build APPN tables during SNA restart.
CSJA Real-Time Assembler Not Applicable Changed Change ACTCDRM response processing.
CSJK Real-Time Assembler Not Applicable Changed Process APPN LU-LU sessions.
CSJO Real-Time Assembler Not Applicable Changed Do not echo unrecognized control vectors.
CSK0 Real-Time Assembler Not Applicable Changed Add entries for the MAXPCID and SLOWTIME parameters.
CSN0 Real-Time Assembler Not Applicable Changed Add entry for the ZNAPN command.
CSPA Real-Time Assembler Not Applicable Changed Check CP-CP session status during cycle down.
CSTC Real-Time Assembler Not Applicable Changed Changes for UNBIND rejecting a BIND.
CSTI Real-Time Assembler Not Applicable Changed Process APPN LU-LU sessions.
CSTJ Real-Time Assembler Not Applicable Changed Process APPN CP-CP sessions.
CSTK Real-Time Assembler Not Applicable Changed Assign SIDs based on PU type.
CSX3 Real-Time Assembler Not Applicable Changed Add messages for APPN links.
CVYA Real-Time Assembler Not Applicable Changed Add entry for the ZNAPN command.
CVYB Real-Time Assembler Not Applicable Changed Update help information for the ZNDLU and ZNETW commands.
CVYD Real-Time Assembler Not Applicable Changed Add help information for the ZNAPN command.
OSTGIP Offline Assembler OSTG Changed Process control points (CPs) and CDRM alias names.
OSTGP2 Offline Assembler OSTG Changed New error processing added.
OSTGUP Offline Assembler OSTG Changed Process control points (CPs) and CDRM alias names.

System Equates

The following section summarizes system equate changes.

SYSEQ Tags

Table 96 summarizes changes to equates that are not configuration dependent (in SYSEQ). This information is presented in alphabetic order by the name of the SYSEQ tag.

Table 96. Changes to SYSEQ Tags for TPF/APPN Support

SYSEQ Tag Equate Value New, Changed, or No Longer Supported?
#APPN 120 New

User Exits

Control Program (CP) User Exits and ECB User Exits summarize the control program (CP) and ECB user exit changes. See TPF System Installation Support Reference for a complete description of all user exits.

Control Program (CP) User Exits

There are no changes.

ECB User Exits

This information is presented in alphabetic order by the name of the function.

Table 97. Changes to ECB User Exits for TPF/APPN Support

Function User Exit Activated In User Exit Program New, Changed, or No Longer Supported? Description of Change
APPN CP-CP Session Activation CSBA UACP New Determines whether or not this TPF processor is allowed to have CP-CP sessions.
APPN LU-LU Session Activation CSBU UAPN New Selects the TPF processor for a new LU-LU session.
APPN LU Registration CSBJ UARG New Determines which LUs in the TPF 4.1 system should be registered with the APPN network.

Functional and Operational Changes

The following section summarizes functional and operational changes. This information is presented in alphabetic order by the functional or operational change.

See Appendix A, PUT 2-15 Interface Changes by Authorized Program Analysis Report (APAR) for a summary of functional and operational changes by APAR.

Commands

Table 98 summarizes command changes. This information is presented in alphabetic order by the name of the command. See TPF Operations for a complete description of all commands.

Attention: Changes to commands can impact any automation programs you are using in your complex.

Table 98. Changes to Commands for TPF/APPN Support

Command New, Changed, or No Longer Supported? Description of Change
ZNAPN New Display or change the mode in which the TPF system is operating (LEN or APPN mode).
ZNDLU Changed Added support for APPN control points (CPs).
ZNETW ACT Changed Added support for CP-CP sessions and ALSNODES.
ZNETW INACT Changed Added support for CP-CP sessions and ALSNODES.
ZNKEY Changed Added support to display the value of MAXPCID. Added support to display or change the value of SLOWTIME.

Messages and System Errors

Table 99 summarizes message (offline and online messages) and system error changes.

The message IDs or system error numbers are listed in numeric order preceded by their alphabetic prefix. Some offline and online messages do not have a standard message ID. For these, the messages are presented in alphabetic order based on the initial message text; or for those messages that begin with variable information, the initial message text that follows that variable information. See Messages (System Error and Offline) and Messages (Online) for a complete description of all messages and system errors.

Attention: Changes to offline messages, online messages, and system errors may impact any automation programs you are using in your complex.

Table 99. Changes to Messages and System Errors for TPF/APPN Support

Message ID or System Error Number Message Type New, Changed, or No Longer Supported?
APPN0001I Online New
APPN0002I Online New
APPN0003I Online New
APPN0040W Online New
APPN0050E Online New
APPN0051E Online New
APPN0052A Online New
APPN0053A Online New
CCIM0092W Online New
CCIM0093W Online New
C62100 System Error New
C62101 System Error New
C62102 System Error New
C62103 System Error New
C62104 System Error New
C62105 System Error New
C62105 System Error New
C62107 System Error New
C62108 System Error New
C62109 System Error New
C6210A System Error New
C6210B System Error New
C6210C System Error New
C6210D System Error New
C6210E System Error New
C6210F System Error New
C62110 System Error New
C62111 System Error New
C62112 System Error New
C62113 System Error New
C62114 System Error New
EM116 Offline New
NAPN0001A Online New
NAPN0002I Online New
NAPN0003I Online New
NAPN0004I Online New
NAPN0005W Online New
NAPN0006E Online New
NAPN0007E Online New
NAPN0008E Online New
NAPN0009E Online New
NAPN0010E Online New
NAPN0012I Online New
NAPN0013E Online New
NAPN0014E Online New
NAPN0015I Online New
NETW0062I Online New
NETW0063I Online New
NETW0064I Online New
NETW0065I Online New
NETW0100I Online New
NETW0101I Online New
NETW0103E Online New
NETW0104E Online New
NETW0105E Online New
NETW0106E Online New
NETW0107E Online New
NETW0108E Online New
NETW0109E Online New
NETW0110E Online New
NETW0111E Online New
NETW0112E Online New
NETW0113E Online New
NETW0114E Online New
NETW0115E Online New
NETW0116E Online New
NETW0117W Online New
NETW0118E Online New
NETW0119E Online New
NETW0120E Online New
XID30000I Online No Longer Supported
XID30001I Online No Longer Supported
XID30002I Online No Longer Supported
XID30003I Online No Longer Supported
XID30050E Online No Longer Supported
XID30051E Online No Longer Supported
XID30052E Online No Longer Supported
XID30053E Online No Longer Supported
XID30054E Online No Longer Supported
XID30055E Online No Longer Supported
XID30056E Online No Longer Supported
XID30060I Online New
XID30061I Online New
XID30062I Online New
XID30063I Online New
XID30070E Online New
XID30071E Online New
XID30072E Online New
XID30073E Online New
XID30074E Online New
XID30075E Online New
XID30076E Online New

Performance or Tuning Changes

Network Considerations discusses load balancing LU-LU sessions in a loosely coupled complex that is connected to an APPN network.

Storage Considerations and Changes

There are no changes.

System Initialization Program (SIP) and System Generation Changes

The following section contains information about defining new SNA resources and parameters that are required for TPF/APPN support.

Defining the TPF Control Point (CP) Name

Specify ASNA=LOCP on an MSGRTA macro to define the name of the APPN control point (CP) for the TPF 4.1 system. The control point is a special LU 6.2 resource used by TPF/APPN support that must reside on all processors in the loosely coupled complex.

Note:
If you do not define the name of the CP, the name of the default local TPF/APPC LU (the LU with ASNA=APPC specified on the MSGRTA macro) will also be the TPF control point name. If neither an APPN control point or a default local TPF/APPC LU exists, the TPF system will not be able to use TPF/APPN support.

See TPF System Generation for more information about the MSGRTA macro.

Defining Remote Control Point (CP) Names

Remote control point (CP) names must be defined to the TPF 4.1 system for each adjacent APPN network node (NN) that is capable of being the network node server (NNS) for the TPF 4.1 system. Define these remote CPs by coding LUTYPE=REMCP on the RSC statements in the offline ACF/SNA table generation (OSTG) program.

See TPF ACF/SNA Network Generation for more information about the OSTG process.

Defining Alias CDRM Names

If the TPF 4.1 system is connected to a VTAM interchange node using both PU 5 NCP connections and APPN connections, you must define an alias name for the VTAM CDRM to the TPF 4.1 system. The VTAM system, as an interchange node, supports PU 5 resources through its system service control point (SSCP) and APPN resources through its CP. The VTAM SSCP name and CP name are identical, but OSTG does not allow a resource to be defined as two different types (remote CDRM and remote CP). To allow both connections, define the CP name to the TPF 4.1 system using the real VTAM CP name, and define the CDRM to the TPF 4.1 system using an alias name as well as the VTAM SSCP name.

See TPF ACF/SNA Network Generation for more information about the OSTG process. See TPF ACF/SNA Data Communications Reference for sample OSTG statements that define VTAM resources to the TPF 4.1 system.

Defining Shared Printers

To use the SNA printer sharing function for a given printer, define the printer as shared by coding PRSHR=YES on the RSC statement in the OSTG program.

See TPF ACF/SNA Network Generation for more information about the OSTG process.

Creating the SNA Keypoint (CTK2)

Define the number of PCID table entries by coding the MAXPCID parameter on the SNAKEY macro in keypoint 2 (CTK2). One PCID table entry is needed for each LU-LU session in the loosely coupled complex that is being activated. Once the LU-LU session becomes active, the PCID table entry can be reused.

Define the PU 2.1 network identifier for the TPF 4.1 system by coding the LENNETID parameter on the SNAKEY macro in CTK2.

Define the maximum number of adjacent link station (ALS) resources that can be defined to the TPF 4.1 system by coding the MAXALS parameter parameter on the SNAKEY macro in CTK2. Define the maximum number of LU-LU sessions for each ALS by coding the MAXSID parameter on the SNAKEY macro in CTK2.

Define the amount of time that an ALS can be in slowdown before the TPF 4.1 system deactivates the link by coding the SLOWTIME parameter on the SNAKEY macro in CTK2.

See TPF ACF/SNA Network Generation for more information about the SNAKEY macro.

Loading Process Changes

There are no changes.

Online System Load Changes

There are no changes.

Publication Changes

Table 100 summarizes changes to the publications in the TPF library. This information is presented in alphabetic order by the publication title.

See the TPF Library Guide for more information about the TPF library.

Table 100. Changes to TPF Publications for TPF/APPN Support

Publication Title Softcopy File Name Description of Change
TPF ACF/SNA Data Communications Reference GTPSNR03 Updated by TPF/APPN support.
TPF ACF/SNA Network Generation GTPACF03 Updated by TPF/APPN support.
TPF Library Guide GTPDOC03 Updated with definitions for new terminology in the master glossary.
Messages (System Error and Offline) and Messages (Online) Not Applicable Updated with information about the messages and system errors that were added, changed, and no longer supported for TPF/APPN support.
TPF Migration Guide: Program Update Tapes GTPMIG03 Updated with migration considerations for TPF/APPN support.
TPF Operations GTPOPR03 Updated with information about the commands that were added and changed for TPF/APPN support.
TPF Program Development Support Reference GTPPDR03 Updated by TPF/APPN support.
TPF System Generation GTPSYG03 Updated by TPF/APPN support.
TPF System Installation Support Reference GTPINR03 Updated by TPF/APPN support.

Host System Changes

There are no changes.

Application Programming Interface (API) Changes

There are no changes.

Database Changes

There are no changes.

Feature Changes

There are no changes.

Installation Validation

There are no changes.

Migration Scenarios

The steps for migrating the TPF 4.1 system to an APPN node depend on how the TPF 4.1 system is currently connected to the SNA network. The TPF 4.1 system can connect to the network as both a PU 5 node and an APPN node at the same time; however, the TPF 4.1 system cannot operate as both a LEN node and APPN node connected to a VTAM system. TPF/APPN support provides an APPN-LEN migration switch that determines the mode in which the TPF 4.1 system operates when there are PU 2.1 links between the TPF 4.1 system and a VTAM system. The TPF 4.1 system can run in either LEN mode or APPN mode.

Common APPN Migration Tasks

There are certain tasks that you must perform to set up the TPF 4.1 system as an APPN node, regardless of how the TPF system is currently connected to the network.

To Convert Your Complex to the New TPF/APPN Support
  1. Install PUT 3, which contains APAR PJ19949 for TPF Advanced Peer-to-Peer Networking support.
  2. Define the TPF control point (CP) name in the system initialization program (SIP). See Defining the TPF Control Point (CP) Name for more information.
  3. Run SIP Stage 1 to create the ANT deck that will be input to the OSTG program.
  4. Define the remote control point names in the OSTG program. See Defining Remote Control Point (CP) Names for more information.
  5. If printer sharing will be used, define the shared printers in the OSTG program. See Defining Shared Printers for more information.
  6. If the TPF 4.1 system has PU 5 NCP connections to the VTAM system, define an alias name for the CDRM in the OSTG program. See Defining Alias CDRM Names for more information.
  7. Run the OSTG program to create an SNA pilot tape.
  8. Define the size of the PCID table in the SNA keypoint (CTK2). See Creating the SNA Keypoint (CTK2) for more information.
  9. Load the updated SNA keypoint (CTK2) to the TPF 4.1 system.
  10. Load the updated OSTG to the TPF 4.1 system using the ZNOPL command.
  11. IPL the TPF 4.1 system.
  12. Complete the tasks that follow, that apply to your current network environment. If you are migrating from PU 5 to APPN, complete the tasks in Migrating from PU 5 to APPN. If you are migrating from LEN to APPN, complete the tasks in Migrating from LEN to APPN.

Additional Information:

Migrating from PU 5 to APPN

Migrating the TPF 4.1 system from a PU 5 node to an APPN node can be done gradually because application LUs in the TPF 4.1 system can be defined to the VTAM system as residing in both the PU 5 (subarea) network and the APPN network. Migrating the TPF 4.1 system from a PU 5 node to a LEN node does not have this dual LU definition capability; therefore, migration had to be done all at once.

Migration Planning - PU 5 to APPN

You must complete the following tasks before or as part of installing TPF/APPN support:

To Migrate Your Complex from PU 5 to APPN
  1. Enter ZNAPN STATUS to display the mode of operation for the TPF 4.1 system. If the response to the command indicates that the TPF 4.1 system is in LEN mode, enter ZNAPN APPN to switch the TPF 4.1 system to APPN mode.

    If the response to the ZNAPN command indicates that the TPF 4.1 system is already in APPN mode, you do not need to enter any command.

  2. Activate the network using the existing NCP load modules, which define the channel adapters connected to the TPF 4.1 system as PU 5.
  3. Activate the LU-LU sessions in the network.
  4. Deactivate one of the NCPs and then load it again using the new NCP load module, which defines the channel adapters connected to the TPF 4.1 system as PU 2.1.
  5. If all the NCPs are being converted to PU 2.1, deactivate the CDRM-CDRM session between the TPF 4.1 system and the VTAM system to prevent new sessions from being established using PU 5 protocols. Use the SAVESESS option of CDRM deactivation so that active LU-LU sessions are not taken down when the CDRM-CDRM session ends.
    Note:
    If all the NCPs are not being converted to PU 2.1, do not deactivate the CDRM-CDRM session because it is still needed for the PU 5 links.
  6. From the VTAM system, activate the PU 2.1 channel adapters between the NCP and the TPF 4.1 system. After XID processing ends, the TPF 4.1 system will start CP-CP sessions with its network node server (NNS), which is the VTAM system. The TPF 4.1 system will then register its resources (LUs) with the NNS.
  7. Activate an LU that is attached to the newly loaded NCP. This will cause the LU to send a session initiation request to the VTAM system. The VTAM system will exchange information with the TPF 4.1 system using the APPN CP-CP sessions. Next, the TPF 4.1 system will send a BIND command to establish the LU-LU session. Repeat this step for all of the LUs that are attached to the NCP.
  8. Repeat steps 4-7 for each remaining NCP that you want to convert to PU 2.1.

Additional Information:

Migrating from LEN to APPN

The procedure for migrating the TPF 4.1 system from a LEN node to an APPN node depends on whether or not the TPF 4.1 system is connected to a VTAM system that is using the VTAM Logon Manager application.

If the VTAM Logon Manager application is not being used, there are no special considerations. Simply change the LEN node definition to an APPN network node (NN) in the configuration file in the communications controller (3174 APPN Controller or RISC System/6000).

The remainder of this section applies only if you are using the VTAM Logon Manager application.

Migration Planning - LEN to APPN

The VTAM Logon Manager application requires that each application (LU) residing in the TPF 4.1 system be defined as an application that resides in the VTAM system. This enables the VTAM Logon Manager application to intercept logon requests for TPF applications and forward the session initiation request to the TPF 4.1 system over special sessions called CLU-CLU sessions. The definitions used by the VTAM Logon Manager application make the network think that the TPF LUs reside in the VTAM system when they really do not. When the TPF 4.1 system becomes an APPN node, the VTAM Logon Manager application is no longer needed and the TPF LUs will be defined correctly to the network (as residing in the TPF 4.1 system, not residing in the VTAM system). During the actual migration, you must delete the APPL statements that define the VTAM applications that represent the TPF LUs in order for the TPF 4.1 system to be able to register (define) its resources (LUs) to the network.

You must complete the following tasks before or as part of installing TPF/APPN support:

To Migrate Your Complex from LEN to APPN
  1. Activate the network using the existing NCP load modules, which define the channel adapters connected to the TPF 4.1 system as PU 2.1 LEN links.
  2. Activate the control sessions (CLU-CLU) between the TPF 4.1 system and the VTAM Logon Manager application.
  3. Activate the LU-LU sessions in the network.
  4. Deactivate one of the NCPs and then load it again using the new NCP load module that defines the channel adapters connected to the TPF 4.1 system as PU 2.1 APPN links.
  5. From the VTAM system, activate the PU 2.1 APPN channel adapters between the NCP and the TPF 4.1 system. During XID processing the TPF 4.1 system will indicate that it is APPN-capable; however, the TPF 4.1 system will treat the link as a LEN link for now because the TPF 4.1 system is running in LEN mode.

    Repeat this step for each NCP that will have APPN links connected to the TPF 4.1 system.

  6. Deactivate all the CLU-CLU sessions and then deactivate the VTAM Logon Manager application.
    Note:
    Active LU-LU sessions are not affected by this action; however, no new LU-LU sessions can be started until APPN CP-CP sessions are activated between the TPF 4.1 system and the VTAM system.
  7. Deactivate the VTAM application program major node that contains the APPL statements defining all the TPF LUs.
  8. Enter ZNAPN APPN to switch the TPF 4.1 system from LEN mode to APPN mode.
  9. Enter ZNETW ACT ID-CPCP to start CP-CP sessions between the TPF 4.1 system and the VTAM system. You can now establish new LU-LU sessions again.

Additional Information:

Fallback Scenarios

If the conversion to TPF/APPN support is not successful, you will need to fall back to your previous network environment, correct the problem, and then try the conversion again.

To Fall Back Your Complex from APPN to PU 5

  1. Deactivate each NCP that contains the PU 2.1 definitions.
  2. Activate the NCP again using the original NCP generation definition, which defines the channel adapters connected to the TPF 4.1 system as PU 5.
  3. Activate the CDRM-CDRM session again.
  4. Activate the LU-LU sessions.

Additional Information:

See VTAM Operation for more information about activating and deactivating NCPs and CDRM-CDRM sessions.

To Fall Back Your Complex from APPN to LEN

  1. Enter ZNETW INACT ID-CPCP,F to deactivate the CP-CP sessions.
  2. Enter ZNAPN LEN to switch the TPF 4.1 system from APPN mode to LEN mode.
  3. Activate the VTAM application program major node that contains the APPL statements defining all the TPF LUs.
  4. Activate the VTAM Logon Manager application.
  5. Activate the CLU-CLU sessions between the TPF 4.1 system and the VTAM Logon Manager application. You can now bring up new LU-LU sessions using the VTAM Logon Manager application.

Additional Information: