gtpm1m2jTPF V4R1 Migration Guide: 3.1 to 4.1

Systems Network Architecture (SNA) Communication

In the TPF 3.1 system, when new network definitions were installed, the network had to be brought down and all the processors in the loosely coupled complex had to be cycled down before the pilot tape could be loaded.

All large SNA tables were under 16 MB.

The Logon Manager allowed independent logical units (LUs) to use generic names for TPF application programs rather than secondary logical unit (SLU) thread names in session requests when the TPF system was defined to IBM ACF/VTAM Version 3 Release 4 or later release as a T2.1 node.

In the TPF 4.1 system, a pilot tape or general data set (GDS) contains new network definitions that can be loaded in NORM state without disturbing the network and without cycling all the processors in the loosely coupled complex to 1052 state. This is described in ACF/SNA Table Generation Support. If errors are detected during a dynamic load operation, a summary of LU names is sent to the receive-only computer room agent set (RO CRAS) console. If problems are found with the network definitions, you can fall back to the previous network definitions, regardless of how many CPUs may have incorporated the new resource definitions.

The following SNA tables are now above 16 MB:

In the TPF 4.1 system, generic name support was expanded so that cross-domain LUs can also use generic TPF application program names in session requests when the TPF 4.1 system is defined to IBM ACF/VTAM Version 3 Release 4 or later releases as a T5 node across a channel-to-channel (CTC) connection. Also, TPF/APPC support will activate a session, if necessary, due to an ALLOCATE request from a transaction program. Two new parameters, CLU and QN, were added to the CTC statement of offline ACF/SNA table generation (OSTG) program to allow control point LU (CLU) sessions with the Logon Manager across CTC connections. See Generating the Systems Network Architecture (SNA) Table for more information.

Support for 3600 multithread with message recovery was dropped.