gtpm2m0xMigration Guide: Program Update Tapes

Dynamic LU Support (APAR PJ21044)

The following section discusses the migration considerations for dynamic LU support.

Prerequisite APARs

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

Functional Overview

The following information describes the enhancements made to the TPF 4.1 system for dynamic LU support.

Defining SNA Network Resources

Currently in the TPF 4.1 system, you must use the offline ACF/SNA table generation (OSTG) program to define all of your SNA network resources, which requires significant effort and careful planning. If, after the TPF 4.1 system is generated, you want to define more resources or change existing resource definitions, you must update the OSTG input data sets, run the OSTG program again, and perform another fresh or dynamic load to incorporate the new or changed resource definitions. This requires additional effort and can impact system availability.

Now, with dynamic LU support, remote terminals (LU resources) can log on to applications in the TPF 4.1 system without first being defined using the OSTG program. Instead, when an LU resource that was not previously defined to the TPF 4.1 system tries to log on, the TPF 4.1 system automatically creates a resource definition for that LU resource, which allows the session to be started.

If the TPF 4.1 system is running in TPF Advanced Peer-to-Peer Networking (TPF/APPN) mode, the same is true for adjacent link station (ALS) resources; you no longer need to define ALS resources to the TPF 4.1 system using the OSTG program. When an ALS resource that was not previously known to the TPF 4.1 system tries to activate the PU 2.1 link, the TPF 4.1 system automatically creates a resource definition for that ALS resource, which allows the link to be activated.

You can also use new commands to create and change resource definitions online for ALS, cross-domain resource manager (CDRM), channel-to-channel (CTC), and network control program (NCP) resources. These new commands are the ZNDYN ADD and ZNDYN CHANGE commands.

Imagine the flexibility and capability that dynamic LU support provides you, especially when it is coupled with TPF/APPN support. With TPF/APPN support, the TPF 4.1 system automatically registers its LU resources with the remainder of the SNA network when the SNA network is activated. With dynamic LU support, the opposite is true. The TPF 4.1 system automatically creates resource definitions for remote LU resources when the remote LU resources log on, and for ALS resources when a PU 2.1 link is activated. Clearly, these enhancements simplify the process of defining and maintaining the SNA network resources.

See the following for more information:

Performing a Dynamic Load

Significant enhancements were also made to the SNA dynamic load function, which is performed using the ZNOPL commands. You are no longer required to perform an initial program load (IPL) on the TPF 4.1 system to incorporate the new resource definitions during a dynamic load. Now you can enter the new ZNOPL MERGE command in any TPF system state to incorporate the new resource definitions without disrupting the SNA network.

In addition, if the update function is not successful during a dynamic load, you are no longer required to enter the ZNOPL FALLBACK command and perform an IPL to fall back to the old resource definitions. The TPF 4.1 system will automatically fall back to the old resource definitions for you. Simply enter the new ZNOPL MERGE command to incorporate the old resource definitions in the TPF 4.1 system. No IPL is necessary.

See TPF ACF/SNA Data Communications Reference for more information about performing a dynamic load. See TPF Operations for more information about the ZNOPL commands.

Improving Expandability and Availability

Dynamic LU support, especially when it is used with TPF/APPN support, significantly reduces the planning required to expand your communication network. It also eliminates the need for scheduled outages.

For example, in a TPF 4.1 system without dynamic LU support, if 2 airlines want to merge their communication networks, they must increase the size of the resource vector table (RVT) and define more fixed file NCB records to accommodate the increased number of resources. Each of these tasks require you to perform a fresh load. The 2 airlines must also define all the new ALS, CDRM, CTC, NCP, and remote LU resources using the OSTG program and load these new resource definitions to the TPF 4.1 system. This requires an IPL and possibly a fresh load.

Dynamic LU support allows you to easily expand your communication network by offering the following:

Customizing Dynamic LU Support

The dynamic LU user exit is provided with dynamic LU support. This user exit allows you to define certain characteristics of the dynamic LU resources that log on to the TPF 4.1 system. A dynamic LU resource is any remote LU resource that is defined to the TPF 4.1 system using dynamic LU support rather than the OSTG program.

You can also use this user exit to restrict specific dynamic LU resources from logging on to the TPF 4.1 system. You can even restrict all dynamic LU resources from logging on to the TPF 4.1 system and continue to define all of the remote SNA resources using the OSTG program.

See TPF System Installation Support Reference for more information about the dynamic LU user exit.

Architecture

The main objective of dynamic LU support is to allow the TPF 4.1 system to learn about new remote SNA resources and create the necessary control structures (RVT entries and NCB records) while the TPF 4.1 system is in any TPF system state. The following information describes the changes that were made to the TPF 4.1 system to meet these requirements.

The TPF 4.1 System Before Dynamic LU Support

Before dynamic LU support, the RVT was (and still is) divided into the following sections:

The size of the RVT was (and still is) defined by the MAXRVT parameter in the SNAKEY macro. The size of the non-LU section was determined by the number of non-LU resources loaded using the OSTG program (one RVT entry for each non-LU resource), and the remaining entries in the RVT became the LU section. There could be spare entries in the LU section of the RVT, but there were never spare entries in the non-LU section of the RVT.

SNA resources were assigned a resource ID (RID) when the resource definitions were created using the SNA fresh load or dynamic load function. Therefore, RID assignments were the same across all the processors in the loosely coupled TPF 4.1 system. That is, if the APPLA resource was assigned RID 23 on processor B, it was also assigned RID 23 on processor C and processor D.

RIDs were not a direct index into the RVT; that is, RID 3 did not necessarily correspond to the third entry in the RVT. Instead, a structure called the RID table was used to map RIDs with the appropriate entry in the RVT.

After a fresh load was performed, the RIDs did happen to be a direct index into the RVT. Figure 1 shows an example of what the RID table and RVT could look like after a fresh load.

Figure 1. RID Table and RVT after a Fresh Load. The RVT1 delimiters are not included in this figure.


Notice the following in Figure 1:

Once a resource was assigned an RID, the RID for that resource never changed. Because the LU section of the RVT was kept in alphabetic order, adding new LU resources or deleting existing resources using the dynamic load function could easily cause the RIDs to no longer be a direct index into the RVT.

Figure 2 shows an example of what the RID table and RVT could look like after a dynamic load was performed to add 2 new LU resources (NEW001 and NEW002) to the TPF 4.1 system.

Figure 2. RID Table and RVT after a Dynamic Load. The RVT1 delimiters are not included in this figure.


Notice the following in Figure 2:

The RID assigned to each resource was also the NCB ordinal number of the 381-byte fixed file NCB record that was also assigned to each resource. RIDs and NCB ordinals were identical because RIDs were the same across all the processors in a loosely coupled TPF 4.1 system.

The architecture described previously in this section presented the following problems for dynamic LU support:

The following information describes the changes that were made to the TPF 4.1 system to resolve these problems for dynamic LU support.

Changes to the Non-LU Section of the RVT

You can now define the size of the non-LU section in the RVT and create spare entries using the new NUMALS parameter, which was added to the SNAKEY macro. Spare entries must exist in the non-LU section of the RVT if you want to use dynamic LU support or the ZNDYN ADD command to define SNA resources to the TPF 4.1 system.

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

In addition, the entries for the CDRM resources and the local SSCP are not necessarily first in the RVT anymore. This change simplifies the organization of the non-LU section and eliminates the need to maintain 3 separate spare areas in the RVT (1 spare area for the CDRM and SSCP resources, 1 spare area for the other non-LU resources, and 1 spare area for the LU resources). Instead, only 2 spare areas are maintained in the RVT (1 spare area for the non-LU resources and 1 spare area for the LU resources).

Figure 3 shows an example of what the RVT could look like with dynamic LU support.

Figure 3. Layout of the RVT with Dynamic LU Support. The RVT1 delimiters are not included in this figure.


Notice the following in Figure 3:

Changes to the LU Section of the RVT

The LU section of the RVT is no longer maintained in alphabetic order. This eliminates the need to rearrange the RVT entries when new LU resources are defined using dynamic LU support, and allows the TPF 4.1 system to define new LU resources in any TPF system state.

New LU resources are now simply assigned the next available spare entry in the LU section of the RVT. Each RVT entry, including the spare RVT entries, are assigned an RID in sequential order when the TPF 4.1 system is generated. Therefore, the RID is now a direct index into the RVT and the RID table is no longer used. That is, RID 3 always corresponds to the third entry in the RVT.

Figure 4 shows an example of how LU resources are added to the RVT when they are defined to the TPF 4.1 system using dynamic LU support.

Figure 4. Creating RVT Entries for LU Resources Defined Using Dynamic LU Support. The RVT1 delimiters are not included in this figure.


Notice the following in Figure 4:

RID Assignments across Processors in a Loosely Coupled TPF 4.1 System

Because different resources can be defined on different processors using dynamic LU support and the ZNDYN ADD command, RIDs are not necessarily consistent across the processors in a loosely coupled TPF 4.1 system. For example, consider the following scenario:

  1. The OSTG program was used to define the following LU resources to the TPF 4.1 system:
  2. Processor B and processor C both perform an initial program load (IPL) to incorporate the new resource definitions. The RID assignments on both processor B and processor C are identical.
  3. The DYN001 LU resource is defined on processor B using dynamic LU support.
  4. The DYN003 LU resource is defined on processor C using dynamic LU support.
  5. The DYN002 LU resource is defined on processor B using dynamic LU support.
  6. The RID assignments on processor B and processor C are no longer consistent, as shown in Figure 5. Notice that on processor B, RID 00000A is assigned to DYN001 but on processor C, RID 00000A is assigned to DYN003.

Figure 5. Inconsistent RID Assignments across Processors in a Loosely Coupled TPF 4.1 System. The RVT1 delimiters are not included in this figure.


New Structures Added for the RVT

Now that the LU section of the RVT is no longer maintained in alphabetic order, a hashing algorithm is necessary so that the TPF 4.1 system can effectively search the RVT for a particular LU resource. The hashing algorithm used is based on the resource name and it requires a number of new structures to access the entries in the RVT.

The following resource name hash (RNH) tables, which are all located in main storage and built during SNA restart, were created for dynamic LU support:

See TPF ACF/SNA Data Communications Reference for a description of these structures.

NCB Records and New NCB Structures

Resources defined using the OSTG program are still assigned a 381-byte fixed file NCB record when the OSTG program is run. However, because RIDs are no longer consistent across the processors in a loosely coupled TPF 4.1 system, the ordinal number of the NCB record is no longer the same as the RID. Therefore, to access the appropriate NCB record for a resource, you must use the CSNB segment. See TPF ACF/SNA Data Communications Reference for more information about the CSNB segment.

New LU resources that are defined to the TPF 4.1 system using dynamic LU support are not assigned a 381-byte fixed file NCB record. Instead, these LU resources are assigned from 1-8 long-term pool file NCB records. The contents of the 381-byte fixed file NCB record and the long-term pool-file NCB record is the same, and both types of NCB records are shared by all processors in a loosely coupled TPF 4.1 system.

The following NCB structures, which are also shared by all processors in a loosely coupled TPF 4.1 system, were created for dynamic LU support:

See TPF ACF/SNA Data Communications Reference for more information about these records.

Scratch Pad Area (SPA)

The NCB/SPA ordinal is assigned by the OSTG program. The SPA ordinal is identical to the NCB ordinal and the NCB/SPA ordinal is saved at RV1ORDN in the RVT. You can assign spared SPA ordinals to the dynamic LUs using the dynamic LU user exit. For a dynamic LU, the ordinal saved at RV1ORDN only means the SPA ordinal and cannot be used as an NCB ordinal. You can use the CSNB segment to access the SPA record. However, the SPA fixed file record must be initialized before calling the CSNB segment. Without doing so, the CSNB segment sets an error return code and returns to the calling segment.

Export ROUTC Changes

Before dynamic LU support, when RIDs were consistent across processors in a loosely coupled TPF 4.1 system, the RID was used by the export ROUTC function to determine the destination LU for routing messages. Now that the RIDs are no longer consistent across processors, this function was changed to pass the name and network ID of the destination LU between processors rather than the RID.

Functional Management Message Routing (FMMR) Changes

Before dynamic LU support, functional management message routing (FMMR) used only the name of the destination LU to send messages to LUs in other TPF 4.1 system complexes. FMMR was changed to pass the network ID, as well as the name, of the destination LU between processors.

Operating Environment Requirements and Planning Information

To ensure that your TPF 4.1 system performs correctly with dynamic LU support, you must create the required operating environment. The following section describes hardware and software requirements specific to dynamic LU 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

With dynamic LU support, you are no longer required to define all of the SNA resources to the TPF 4.1 system using the OSTG program. See Defining SNA Network Resources for more information.

Interface Changes

The following section summarizes interface changes.

C/C++ Language

The following section summarizes C/C++ language changes. This information is presented in alphabetic order by the type of C/C++ language information. See the TPF C/C++ Language Support User's Guide and TPF Application Programming for more information about the C/C++ language.

Build Scripts

There are no changes.

Dynamic Load Module (DLM) Stubs

There are no changes.

General Use C Language Header Files

Table 120 summarizes the general use C language header file changes. This information is presented in alphabetic order by the name of the general use C language header file.

General use means these header files are available for your use.

Table 120. Changes to General Use C Language Header Files for Dynamic LU Support

General Use C Language Header File TARGET (TPF) ISO-C New, Changed, or No Longer Supported? Do You Need to Recompile Segments?
c$ck2sn.h X   Changed No
c$fva0.h X   Changed Yes
rcp0pl.h X   Changed No
c$rv1vt.h X   Changed No
c$syseq.h X   Changed No

Implementation-Specific C/C++ Language Header Files (IBM Use Only)

There are no changes.

Library Interface Scripts

There are no changes.

Library Members (Object Files)

There are no changes.

Link-Edited Modules

There are no changes.

Members (Object Files)

There are no changes.

Object Code Only (OCO) Stubs

There are no changes.

Configuration Constant (CONKC) Tags

There are no changes.

Control Program Interface (CINFC) Tags

There are no changes.

Copy Members

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

Table 121. Changes to Copy Members for Dynamic LU Support

Copy Member Type CSECT Where Copy Member Is Located New, Changed, or No Longer Supported? Description of Change
CDC1 Control Program CCDCOL Changed Updated to bypass data collection for LU resources that are defined after data collection is started.
CSX2 Control Program CCSNA1 Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSX6 Control Program CCSNA1 Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CS0B Control Program CCSNA4 Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CS0D Control Program CCSNAD Changed Updated to build the negotiable BIND image for FMMR-FMMR sessions.
CS0F Control Program CCSNA4 Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource. Also updated to build the negotiable BIND image for FMMR-FMMR sessions.
CS0J Control Program CCSNA1 Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CS06 Control Program CCSNA1 Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CS11 Control Program CCSNA0 Changed Removed the resource identifier (RID) table.
CS12 Control Program CCSNA0 Changed Removed the resource identifier (RID) table.
CS13 Control Program CCSNA0 Changed Updated the INQRC macro for dynamic LU support.
CS20 Control Program CCSNAB Changed Added checks for FMMR input messages.
CS96 Control Program CCSNA3 Changed Updated to save the input message sequence number for the system recovery table (SRT) in the trailer of the message block.
CT15 Control Program CCCTIN Changed Allocated storage for the RNHCT.

Fixed File Records

Table 122 summarizes fixed file record changes. This information is presented in alphabetic order by the name of the fixed file record.

Table 122. Changes to Fixed File Records for Dynamic LU Support

Fixed File Record New, Changed, or No Longer Supported? Description of Change
#NCBN4 New NCB directory record.
#NCBN5 New NCB directory record.

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 123 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 123. Changes to Communication Macros and Statements for Dynamic LU Support

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

Data Macros

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

Table 124. Changes to Data Macros for Dynamic LU Support

Data Macro New, Changed, or No Longer Supported? Do You Need to Reassemble Programs That Use This Data Macro?
AN0NT Changed Yes
CK2SN Changed No
CZ1SE Changed No
DC0DC Changed No
DLTEC Changed No
IDSDLR Changed Yes
INC1CR New Not Applicable
IND1DT New Not Applicable
IRNHCT New Not Applicable
IRNHET New Not Applicable
IRNHPT New Not Applicable
IRNHST New Not Applicable
ISCB Changed No
NC0CB Changed No
NODEQ Changed No
RC0AT Changed No
RC0PL Changed No
RC1IT Changed No
RR0RT Changed No
RV1VT Changed No
SP0PA Changed No

General Macros

Table 125 summarizes the general macro changes. This information is presented in alphabetic order by the name of the general macro. See TPF General Macros for a complete description of all general macros.

Table 125. Changes to General Macros for Dynamic LU Support

General Macro New, Changed, or No Longer Supported? Do You Need to Reassemble Programs?
INQRC Changed No
RIDCC Changed Yes, if SVC=NO was specified.

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 126 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 126. Changes to SIP Skeleton and Internal Macros for Dynamic LU Support

SIP Skeleton and Internal Macro New, Changed, or No Longer Supported?
SKANTD Changed
SKGLB Changed
SKRCIT Changed
SKSET Changed
SPERRG Changed
SPGLB Changed
SPPGML Changed
SPRIAT Changed
SYSEQ Changed

System Initialization Program (SIP) Stage I Macros and Statements

Table 127 summarizes system initialization program (SIP) Stage I macros 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 dynamic LU support.

Table 127. Changes to SIP Stage I Macros and Statements for Dynamic LU Support

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

System Initialization Program (SIP) Stage II Macros

Table 128 summarizes the system initialization program (SIP) Stage II macro changes. This information is presented in alphabetic order by the name of the SIP Stage II macro. See TPF System Generation for a complete description of the SIP Stage II macros. If IBMPAL is changed, you must run the system allocator (SALO) and load the new program allocation table (PAT) to the TPF 4.1 system.

Table 128. Changes to SIP Stage II Macros for Dynamic LU Support

SIP Stage II Macro New, Changed, or No Longer Supported?
IBMPAL Changed

System Communication Keypoint (SCK) Generation Macros

There are no changes.

System Macros

Table 129 summarizes system macro changes. This information is presented in alphabetic order by the name of the system macro. See TPF System Macros for a complete description of all system macros.

Table 129. Changes to System Macros for Dynamic LU Support

System Macro New, Changed, or No Longer Supported? Do You Need to Reassemble Programs?
DHASHC New Not Applicable
GROUP Changed No

System Macros (IBM Use Only)

There are no changes.

Segments

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

Table 130. Changes to Segments for Dynamic LU Support

Segment Type Link-Edit Module (Where Offline Segment Is Linked) New, Changed, or No Longer Supported? Description of Change
BKDB Real-Time Assembler Not Applicable Changed Added descriptor records for dynamic LU support.
BRCP Real-Time Assembler Not Applicable Changed Added checks to prevent Recoup from being started if the NCB reorganization function is active.
CDLA Real-Time Assembler Not Applicable New Build the RNHCT, RNHET, RNHPT, and RVT termination list.
CDLB Real-Time Assembler Not Applicable New Keypoint newly created RVT entries.
CDLC Real-Time Assembler Not Applicable New Process the ZNDYN DISPLAY command.
CDLD Real-Time Assembler Not Applicable New Process the ZNDYN RECYCLE command.
CDLF Real-Time Assembler Not Applicable New Process the ZNDYN ADD and ZNDYN CHANGE commands.
CDLI Real-Time Assembler Not Applicable New Parse the ZNDYN commands.
CDLX Real-Time Assembler Not Applicable New Verify the changes made in the dynamic LU user exit (CDLY).
CDLY Real-Time Assembler Not Applicable New Dynamic LU user exit.
CDL0 Real-Time Assembler Not Applicable Changed Updated for the ZNOPL BUILD and ZNOPL MERGE commands.
CDL1 Real-Time Assembler Not Applicable Changed Updated to process the ZNOPL LOAD command using the new control bytes.
CDL2 Real-Time Assembler Not Applicable Changed Updated to process the ZNOPL UPDATE command using the new control bytes.
CDL3 Real-Time Assembler Not Applicable Changed Updated to process the ZNOPL FALLBACK command using the new control bytes.
CDL5 Real-Time Assembler Not Applicable Changed Added more information to the ZNOPL STATUS command for dynamic LU support.
CDL6 Real-Time Assembler Not Applicable Changed Updated the root dynamic load record (RDLR) for migration to dynamic LU support.
CDL7 Real-Time Assembler Not Applicable Changed Added additional messages for the ZNOPL commands.
CDL8 Real-Time Assembler Not Applicable New Process the ZNOPL MERGE command. This segment replaces the CSGI segment.
CDL9 Real-Time Assembler Not Applicable New Create online a SNA resource definition for an ALS, CDRM, CTC, or NCP resource.
CHKB Real-Time Assembler Not Applicable Changed Updated to no longer initialize the NCB records for service LUs.
CHKR Real-Time Assembler Not Applicable Changed Updated to no longer initialize the NCB records for service LUs.
CHNV Real-Time Assembler Not Applicable Changed Updated to issue INQRC to allocate resources for remote LUs when issuing a CNOS INITIALIZE verb.
CHRR Real-Time Assembler Not Applicable Changed Updated to clean up and return resources to the TPF 4.1 system when an LU 6.2 session ends.
CHRY Real-Time Assembler Not Applicable Changed Updated to issue INQRC to allocate resources for remote LUs when issuing a TPPCC ALLOCATE verb.
CHSB Real-Time Assembler Not Applicable Changed Updated LU 6.2 BIND processing for dynamic LU support.
CHZL Real-Time Assembler Not Applicable Changed Updated with miscellaneous changes.
CIT6 Real-Time Assembler Not Applicable Changed Updated to determine if a network ID is appended to an FMMR input message.
CMTE Real-Time Assembler Not Applicable Changed Updated to check the input message sequence number in the SRT and the message block if a FIND or FILE error occurs while searching the SRT.
CMTQ Real-Time Assembler Not Applicable Changed Updated to determine if a network ID is appended to an OMT wake-up message.
CMTS Real-Time Assembler Not Applicable Changed Added a check for session awareness.
CMWA Real-Time Assembler Not Applicable Changed Appended a network ID to the routing control parameter list (RCPL) for high-performance FMMR.
CMWB Real-Time Assembler Not Applicable Changed Appended a network ID to the routing control parameter list (RCPL) for FMMR.
COAD Real-Time Assembler Not Applicable Changed Appended a network ID to the routing control parameter list (RCPL) for export ROUTC.
COAE Real-Time Assembler Not Applicable Changed Added a node counter check.
CONN Real-Time Assembler Not Applicable Changed Updated to store the NCB device type and user area byte in the RCAT.
CSAD Real-Time Assembler Not Applicable New Process the ZNNCB DISPLAY command for the ALL parameter.
CSAE Real-Time Assembler Not Applicable New Process the ZNNCB DISPLAY command for the NAME parameter.
CSAF Real-Time Assembler Not Applicable New Initialize the NCB directory records.
CSAG Real-Time Assembler Not Applicable New Process the ZNNCB RECON command.
CSAH Real-Time Assembler Not Applicable New Process the ZNNCB REORG command.
CSAI Real-Time Assembler Not Applicable New Copy the current NCB directory record to the staged NCB directory record.
CSA0 Real-Time Assembler Not Applicable Changed Added processing to initialize the long-term pool file NCB records, as well as the fixed file NCB records, when the ZNNCB command is entered with the ALL parameter.
CSA1 Real-Time Assembler Not Applicable Changed Added processing to initialize the long-term pool file NCB records, as well as the fixed file NCB records, when the ZNNCB command is entered with the NAME or NOD parameter.
CSA2 Real-Time Assembler Not Applicable Changed Added processing to initialize the long-term pool file NCB records, as well as the fixed file NCB records, when the ZNNCB command is entered with the MOD parameter.
CSA3 Real-Time Assembler Not Applicable Changed Added additional messages for the ZNNCB commands.
CSA4 Real-Time Assembler Not Applicable Changed Updated to not initialize an SPA record if the SPA record does not have a valid SPA ordinal number.
CSA6 Real-Time Assembler Not Applicable Changed Updated to not initialize an SPA record if the SPA record does not have a valid SPA ordinal number.
CSA8 Real-Time Assembler Not Applicable New Parse the ZNNCB commands.
CSBH Real-Time Assembler Not Applicable Changed Updated to allow the TPF 4.1 system to define ALS resources using dynamic LU support.
CSBI Real-Time Assembler Not Applicable Changed Updated to allow the TPF 4.1 system to define ALS resources using dynamic LU support.
CSBP Real-Time Assembler Not Applicable Changed Updated to allow the TPF 4.1 system to define ALS resources using dynamic LU support.
CSBQ Real-Time Assembler Not Applicable Changed Updated to enable dynamic LU support for X.25 NPSI resources.
CSBU Real-Time Assembler Not Applicable Changed Updated to allow the TPF 4.1 system to define ALS resources using dynamic LU support.
CSBV Real-Time Assembler Not Applicable Changed Updated to not put an RVT on the RVT termination list for certain conditions.
CSCD Real-Time Assembler Not Applicable Changed Updated the cleanup processing for ALS, CDRM, and NCP resources.
CSCI Real-Time Assembler Not Applicable Changed Updated the processing of BIND responses for dynamic LU support.
CSCP Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSCQ Real-Time Assembler Not Applicable Changed Updated to clean up dynamic LU resources.
CSCY Real-Time Assembler Not Applicable Changed Updated the ZNRVT command to handle duplicate LU resources.
CSEA Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSEC Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSEI Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSEJ Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSES Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSFQ Real-Time Assembler Not Applicable Changed Added processing to sort the RVT entries and display them in alphabetic order when the ZNDLU command is entered.
CSGA Real-Time Assembler Not Applicable Changed Updated to restart the NCB reconciliation function when the TPF 4.1 system is cycling up if the NCB reconciliation function was active.
CSGB Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSGD Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSGE Real-Time Assembler Not Applicable Changed Updated to remove the RVT entry for both the target and alternate printers from the RVT termination list during ZNALT processing, if necessary.
CSGF Real-Time Assembler Not Applicable Changed Updated to put the RVT entry for both the target and alternate printers on the RVT termination list during ZNACT processing, if necessary.
CSGI Real-Time Assembler Not Applicable No Longer Supported Replaced by the CDL8 segment.
CSG0 Real-Time Assembler Not Applicable Changed Updated to process SNA restart using the new control bytes in the root dynamic load record (RDLR) and enter CDLA to build the RNH tables.
CSG1 Real-Time Assembler Not Applicable Changed Added more information to the subarea address table (SAT).
CSG2 Real-Time Assembler Not Applicable Changed Updated to load resources to the non-LU or LU section of the RVT and to initialize the spare RVT entries.
CSG3 Real-Time Assembler Not Applicable Changed Updated to initialize the spare RVT2 entries.
CSG4 Real-Time Assembler Not Applicable Changed Added messages for SNA restart.
CSG5 Real-Time Assembler Not Applicable Changed Updated to perform a nonfresh load and initialize the new RVT entries when the size of the RVT is increased.
CSG7 Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSJB Real-Time Assembler Not Applicable Changed Updated to create and determine some characteristics of dynamic LU resources during CDINIT request processing.
CSJC Real-Time Assembler Not Applicable Changed Updated to enter the dynamic LU user exit during CDCINIT request processing.
CSJK Real-Time Assembler Not Applicable Changed Updated FMMR BIND processing for dynamic LU support.
CSJO Real-Time Assembler Not Applicable Changed Updated to keypoint the new dynamic LU resources.
CSJU Real-Time Assembler Not Applicable Changed Updated with miscellaneous changes.
CSK0 Real-Time Assembler Not Applicable Changed Added new parameters to the ZNKEY command.
CSLD Real-Time Assembler Not Applicable Changed Updated to not add the LEID to the log processor because the CDLY segment will add the LEID.
CSLJ Real-Time Assembler Not Applicable New 3270 welcome screen user exit.
CSM0 Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSNB Real-Time Assembler Not Applicable Changed Updated to support both fixed file NCB records and long-term pool file NCB records.
CSN0 Real-Time Assembler Not Applicable Changed Added an entry for the ZNDYN commands and changed the entry for the ZNNCB commands.
CSTA Real-Time Assembler Not Applicable Changed Updated to create and determine some characteristics of dynamic LU resources during SESINIT request processing.
CSTB Real-Time Assembler Not Applicable Changed Updated to keypoint dynamic LU resources.
CSTC Real-Time Assembler Not Applicable Changed Updated to create and determine some characteristics of dynamic LU resources during BIND request processing.
CSTE Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSTF Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSTG Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSTJ Real-Time Assembler Not Applicable Changed Updated to search the entire non-LU section of the RVT when looking for a specific non-LU resource.
CSXD Real-Time Assembler Not Applicable Changed Updated to call the 3270 welcome screen user exit.
CTKO Real-Time Assembler Not Applicable Changed Updated to determine if the NCB reorganization function must be restarted.
CVAQ Real-Time Assembler Not Applicable Changed Updated to create a dynamic LU resource for import ROUTC if the resource does not exist in the processor.
CVYA Real-Time Assembler Not Applicable Changed Added an entry for the ZNDYN commands.
CVYB Real-Time Assembler Not Applicable Changed Updated the help information for the ZNNCB commands.
CVYD Real-Time Assembler Not Applicable Changed Added help information for the ZNDYN commands and updated the help information for the ZNOPL commands.
FTVA03 Offline C Language Not Applicable Changed Added new record definitions for dynamic LU support.
GLBL Real-Time Assembler Not Applicable Changed Updated to prevent online file recoup from being started when the NCB reorganization function is active.
JCD6 Real-Time Assembler Not Applicable Changed Updated to bypass data collection for LU resources that are defined after data collection is started.
JRA2 Offline PL/I Not Applicable Changed Updated to bypass data reduction for LU resources that are defined after the data collection is started.
OSTGIP Offline Assembler OSTG Changed Updated to set up session awareness in the ANT deck.
OSTGUP Offline Assembler OSTG Changed Updated to set up session awareness in the OSTG output.
RCTD Real-Time Assembler Not Applicable Changed Updated the display to include the NCB slot that will be used when an LU logs on to the application.

System Equates

The following section summarizes system equate changes.

SYSEQ Tags

Table 131 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 131. Changes to SYSEQ Tags for Dynamic LU Support

SYSEQ Tag Equate Value New, Changed, or No Longer Supported?
#NCBCR0 117 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 132. Changes to User Exits for Dynamic LU Support

Function User Exit Activated In User Exit Program New, Changed, or No Longer Supported? Description of Change
Dynamic LU CDLX CDLY New Allows you to define certain characteristics for dynamic LU resources that log on to the TPF 4.1 system and to specify which dynamic LU resources can log on to the TPF 4.1 system.
3270 Welcome Screen CSXD CSLJ New Provides a skeleton for a 3270 welcome screen that can be used with session awareness support.

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 133 summarizes command changes. This information is presented in alphabetic order by the name of the command.

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

See TPF Operations for a complete description of all commands.

Table 133. Changes to Commands for Dynamic LU Support

Command New, Changed, or No Longer Supported? Description of Change
ZDRCT Changed Added to the display the number of the NCB slot that will be used by an LU when it logs on to the application.
ZNDLU Changed Added support to list LUs in alphabetic order in the information that is displayed.
ZNDYN ADD New Adds a new ALS, CDRM, CTC, or NCP resource to the TPF 4.1 system.
ZNDYN CHANGE New Changes the name of an ALS, CDRM, CTC, or NCP resource in the TPF 4.1 system. Also changes the subarea of a CDRM, CTC, or NCP resource.
ZNDYN DISPLAY New Displays information from the resource name hash (RNH) tables.
ZNDYN RECYCLE New Recycles the RVT entries that are currently on the RVT termination list.
ZNKEY Changed Added support for the DYNTO, MAXPRIM, and NUMALS parameters.
ZNNCB Changed Added support to initialize long-term pool file NCB records as well as fixed file NCB records. Also added support for the NAME parameter.
ZNNCB DISPLAY New Displays information about NCB records.
ZNNCB RECON New Reconciles the NCB directory records in the TPF 4.1 system and returns to it the long-term pool file NCB records that are no longer being used.
ZNNCB REORG New Changes the number of NCB directory records being used in the TPF 4.1 system.
ZNOPL BUILD New Rebuilds the RVT by forcing a fresh load from the current RRT.
ZNOPL FALLBACK Changed Fallback is now allowed only after the update or merge function is performed.
ZNOPL LOAD Changed Disabled the fallback function after a dynamic or fresh load is performed.
ZNOPL MERGE New Merges the current RRT with the RVT without requiring an IPL.
ZNOPL STATUS Changed Added information about the build and merge functions to the status display. Also added information that indicates if a particular processor is active.
ZNOPL UPDATE Changed No longer calculates RIDs for the RVT entries. Instead, this function now calculates the NCB ordinal number that is used to determine the NCB file address.

Messages and System Errors

Table 134 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.

Table 134. Changes to Messages and System Errors for Dynamic LU Support

Message ID or System Error Number Message Type New, Changed, or No Longer Supported?
0009D0 System Error New
0009D1 System Error New
0009E0 System Error New
0009E1 System Error New
0009E2 System Error New
0009E3 System Error New
0009E4 System Error New
0009E5 System Error New
0009E6 System Error New
0009E7 System Error New
0009EA System Error New
0009EB System Error New
0009F0 System Error New
0009F1 System Error New
0009F2 System Error New
0009F3 System Error New
0009F4 System Error New
0009F5 System Error New
0009F6 System Error New
0009F7 System Error New
0009F8 System Error New
BRCP0005E Online New
CSG40053E Online New
CSG40054W Online New
CSG40055E Online New
CSNB0001E Online New
CSNB0002I Online New
CSNB0003E Online New
CSNB0004I Online New
CSNB0005I Online New
NDYN0000E Online New
NDYN0004E Online New
NDYN0005I Online New
NDYN0006I Online New
NDYN0020I Online New
NDYN0030I Online New
NDYN0040I Online New
NDYN0050I Online New
NDYN0061E Online New
NDYN0062E Online New
NDYN0063E Online New
NDYN0064I Online New
NDYN0065E Online New
NDYN0066E Online New
NDYN0070E Online New
NDYN0072E Online New
NDYN0073E Online New
NDYN0074I Online New
NDYN0075I Online New
NDYN0077E Online New
NDYN0078E Online New
NDYN0079E Online New
NDYN0080I Online New
NDYN0081E Online New
NDYN0082E Online New
NDYN0083E Online New
NDYN0084E Online New
NDYN0085E Online New
NDYN0086E Online New
NDYN0087E Online New
NDYN0088E Online New
NDYN0089E Online New
NDYN0090E Online New
NDYN0091E Online New
NDYN0092E Online New
NNCB0003E Online No Longer Supported
NNCB0018E Online New
NNCB0019E Online New
NNCB0020E Online New
NNCB0021E Online New
NNCB0022E Online New
NNCB0023E Online New
NNCB0024E Online New
NNCB0026E Online New
NNCB0027E Online New
NNCB0028E Online New
NNCB0029I Online New
NNCB0030E Online New
NNCB0031E Online New
NNCB0032E Online New
NNCB0033E Online New
NNCB0034E Online New
NNCB0035E Online New
NNCB0051E Online No Longer Supported
NNCB0070I Online New
NNCB0071I Online New
NNCB0072E Online New
NNCB0073W Online New
NNCB0074I Online New
NNCB0075I Online New
NNCB0076I Online New
NNCB0077I Online New
NNCB0078I Online New
NNCB0079E Online New
NNCB0080E Online New
NNCB0083W Online New
NNCB0084I Online New
NNCB0085I Online New
NNCB0086I Online New
NNCB0087E Online New
NNCB0088E Online New
NNCB0089E Online New
NNCB0090E Online New
NNCB0091E Online New
NNCB0092E Online New
NNCB0093I Online New
NNCB0094W Online New
NNCB0096E Online New
NNCB0097I Online New
NNCB0098I Online New
NNCB0099I Online New
NNCB0100E Online New
NNCB0110I Online New
NNCB0130I Online New
NOPL0003I Online New
NOPL0033E

NOPL0034E

Online Changed
NOPL0040E Online No Longer Supported
NOPL0040A Online New
NOPL0041E

NOPL0042E

Online No Longer Supported
NOPL0042A Online New
NOPL0050E Online No Longer Supported
NOPL0052A Online New
NOPL0062A

NOPL0063A

Online Changed
NOPL0064I Online New
NOPL0065I Online New
NOPL0066E Online New
NOPL0067E Online New
NOPL0068E Online New
NOPL0069A Online New
NOPL0072E Online New
NOPL0073E Online New
NOPL0074E Online New
NOPL0075E Online New
NOPL0076E Online New
NOPL0077E Online New
NOPL0078E Online New

Performance or Tuning Changes

There are no changes.

Storage Considerations and Changes

There are no changes.

System Initialization Program (SIP) and System Generation Changes

The following information describes the changes that were made to the system initialization program (SIP) and system generation for dynamic LU support.

Defining Records for Dynamic LU Support

Specify in the SIP stage I deck how many of the following types of records you want to generate in the TPF 4.1 system:

The TPF 4.1 system uses 381-byte long-term pool file records to create NCB records for the new LU resources that are defined using dynamic LU support. As many as 8 NCB records can be created for each of these LU resources. Therefore, define enough of these records to accommodate the new LU resources that will log on to the TPF 4.1 system using dynamic LU support.

The TPF 4.1 system uses the #NCBN4 records to create the current NCB directory records, which are structures used to access the NCB records for LU resources that log on to the TPF 4.1 system using dynamic LU support. Each of these LU resources is assigned an entry in an NCB directory record when it logs on to the TPF 4.1 system.

Each NCB directory record contains 84 entries. To calculate the total number of NCB directory records that you need, estimate the number of LU resources that will log on to the TPF 4.1 system using dynamic LU support. Divide this number by 84 and double the result to determine the total number of NCB directory records to define.

For example, if you estimate that 8400 LU resources will log on to the TPF 4.1 system using dynamic LU support, define (8400 ÷. 84) × 2, or 200, NCB directory records.

You can increase the number NCB directory records defined in the TPF 4.1 system at any time by using the NCB reorganization function. This function copies the current NCB directory records (which are initially the #NCBN4 records) to the staged NCB directory records (which are initially the #NCBN5 records). Therefore, define enough #NCBN5 records to accommodate any possible future expansion.

See TPF ACF/SNA Data Communications Reference for more information about the current NCB directory records, staged NCB directory records, and NCB reorganization function.

Defining User Application Programs

With the addition of dynamic LU support, you must now specify a value for the following MSGRTA parameters or use the default value that is provided:

See TPF System Generation for more information about the MSGRTA macro and these new parameters.

Creating the SNA Keypoint (CTK2)

With the addition of dynamic LU support, you must now specify a value for the following SNAKEY parameters or use the default value that is provided:

You may also want to define more spare entries in the RVT to accommodate dynamic LU resources that will log on to the TPF 4.1 system. To define spare entries in the RVT, specify a value for the MAXRVT parameter that is greater than the number of resources you will define using the OSTG program. The number of dynamic LU resources that can log on to the TPF 4.1 system is limited by the number of spare entries defined in the RVT.

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

Generating the TPF 4.1 System without Dynamic LU support

Dynamic LU support is an option for the TPF 4.1 system. If you do not generate #NCBN4 or #NCBN5 in your TPF 4.1 system, then SIP stage 1 reports a warning and disables dynamic LU support. If you want to enable dynamic LU support at a later time, use this procedure.

  1. Code the RAMFIL macros for the #NCBN4 and #NCBN5 records in your SIP stage 1 deck.
  2. Run the FACE table generator.
  3. Assemble your SIP stage 1 deck.
  4. Update SYSET and SYGLB from the resulting SIP stage 2 deck.
  5. Assemble and load BKDB.

Loading Process Changes

There are no changes.

Online System Load Changes

There are no changes.

Publication Changes

Table 135 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 135. Changes to TPF Publications for Dynamic LU Support

Publication Title Softcopy File Name Description of Change
TPF ACF/SNA Data Communications Reference GTPSNR04 Added detailed, task-oriented information about dynamic LU support.
TPF ACF/SNA Network Generation GTPACF04 Updated the description of the SNAKEY macro and the ANTNME statement to include information about the new parameters that were added for dynamic LU support. Also updated the information about the OSTG program for dynamic LU support.
TPF General Macros GTPGEN04 Updated the description of the INQRC macro to include information about the new parameters that were added for dynamic LU support.
TPF Library Guide GTPDOC04 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 dynamic LU support.
TPF Migration Guide: Program Update Tapes GTPMIG04 Updated with migration considerations for dynamic LU support.
TPF Operations GTPOPR04 Updated with information about the commands that were added and changed for dynamic LU support.
TPF Program Development Support Reference GTPPDR04 Updated with information about the new dump labels that were added for dynamic LU support.
TPF System Generation GTPSYG04 Updated the description of the MSGRTA macro to include information about the new parameters that were added for dynamic LU support.
TPF System Installation Support Reference GTPINR04 Updated with information about the new ECB-control program (CP) user exits that were added for dynamic LU support.
TPF System Macros GTPSYS04 Added information about the new DHASHC macro.
TPF System Performance and Measurement Reference GTPSPR04 Added information about data collection and reduction considerations for dynamic LU 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

You can install dynamic LU support on all of the processors in a loosely coupled TPF 4.1 system at the same time, or you can install dynamic LU support on only 1 processor at first and the remaining processors at a later time.

If you install dynamic LU on all of the processors in the loosely coupled TPF 4.1 system at the same time, follow the procedure described in To Install Dynamic LU Support on All the Processors at Once.

If you do not want to install dynamic LU support on all of the processors in the loosely coupled TPF 4.1 system at the same time, do the following:

  1. Install dynamic LU support on the first processor in the loosely coupled TPF 4.1 system by using the procedure described in To Install Dynamic LU Support on the First Processor.
  2. Install dynamic LU support on the remaining processors in the loosely coupled TPF 4.1 system by using the procedure described in To Install Dynamic LU Support on the Remaining Processors.
  3. Fully enable dynamic LU support once it is installed on all the processors in the loosely coupled TPF 4.1 system by using the procedure described in To Fully Enable Dynamic LU Support.

When you install dynamic LU support on some, but not all, of the processors in a loosely coupled TPF 4.1 system, the following limitations exist:

To Install Dynamic LU Support on All the Processors at Once

Use the following procedure to install dynamic LU support on all the processors in a loosely coupled TPF 4.1 system at the same time.

  1. Install PUT 4, which contains the dynamic LU support APAR (PJ21044).
  2. Update the dynamic LU user exit.

    This user exit is shipped by IBM to reject all log on requests for all remote LU resources. You must update this user exit before you can use dynamic LU support. See TPF System Installation Support Reference for more information about the dynamic LU user exit.

  3. Specify in the SIP stage I deck the number of #NCBN4 and #NCBN5 records that you want to generate in the TPF 4.1 system. Also define any additional 381-byte long-term pool file records for dynamic LU support. See Defining Records for Dynamic LU Support for more information.
  4. If you want to load new SNA resource definitions, do the following:
    1. Specify values for the new parameters that were added to the MSGRTA macro for dynamic LU support. See Defining User Application Programs for more information.
    2. Run SIP stage I to create the ANT deck, which will be used as input to the OSTG program.
    3. Run the OSTG program to create an SNA pilot tape.
  5. Use the SNAKEY macro to define the following information in the SNA keypoint (CTK2):
    • Size of the RVT using the MAXRVT parameter.
      Note:
      Consider increasing the size of the RVT to accommodate the LU resources that may log on to the TPF 4.1 system using dynamic LU support.
    • Size of the non-LU section in the RVT using the NUMALS parameter.
    • Number of resource name hash prime table (RNHPT) entries defined in the TPF 4.1 system using the MAXPRIM parameter.
    • Recycle time for an RVT entry using the DYNTO parameter.

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

  6. Load the updated SNA keypoint (CTK2) to each processor in the loosely coupled TPF 4.1 system.
  7. Perform a fresh load to rebuild the RVT for dynamic LU support and load any new SNA resource definitions that you created in step 4.

    See TPF ACF/SNA Data Communications Reference for more information about the SNA fresh load function.

    Note:
    You must perform a fresh load even if you did not create new SNA resource definitions.
  8. Enter the ZRIPL commnd on each processor in the loosely coupled TPF 4.1 system to complete the fresh load function.

    See TPF Operations for more information about the ZRIPL commnd.

Dynamic LU support is now installed and fully enabled on each processor in the loosely coupled TPF 4.1 system.

To Install Dynamic LU Support on the First Processor

Use the following procedure to install dynamic LU support on the first processor in your loosely coupled TPF 4.1 system.

  1. Install PUT 4, which contains the dynamic LU support APAR (PJ21044).
  2. Update the dynamic LU user exit.

    This user exit is shipped by IBM to reject all log on requests for all remote LU resources. You must update this user exit before you can use dynamic LU support. See TPF System Installation Support Reference for more information about the dynamic LU user exit.

  3. Specify in the SIP stage I deck the number of #NCBN4 and #NCBN5 records that you want to generate in the TPF 4.1 system. Also define any additional 381-byte long-term pool file records for dynamic LU support. See Defining Records for Dynamic LU Support for more information.
  4. If you want to load new SNA resource definitions, do the following:
    1. Specify values for the new parameters that were added to the MSGRTA macro for dynamic LU support. See Defining User Application Programs for more information.
    2. Run SIP stage I to create the ANT deck, which will be used as input to the OSTG program.
    3. Run the OSTG program to create an SNA pilot tape.
  5. Use the SNAKEY macro to define the following information in the SNA keypoint (CTK2):
    • Size of the RVT using the MAXRVT parameter.
      Note:
      Consider increasing the size of the RVT to accommodate the LU resources that may log on to the TPF 4.1 system using dynamic LU support.
    • Size of the non-LU section in the RVT using the NUMALS parameter, which must be equal to the number of non-LU resources defined in the OSTG input data set.
      Note:
      After you install dynamic LU support on all of the processors in your loosely coupled TPF 4.1 system, you will increase the value assigned to the NUMALS parameter, which will allow you to define new non-LU resources using dynamic LU support or the ZNDYN ADD command.
    • Number of resource name hash prime table (RNHPT) entries defined in the TPF 4.1 system using the MAXPRIM parameter.
    • Recycle time for an RVT entry using the DYNTO parameter.

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

  6. Load the updated SNA keypoint (CTK2) to the processor where you are installing dynamic LU support.
  7. Enter the following command on one of the processors in your loosely coupled TPF 4.1 system where dynamic LU support is not installed:
    ZAPGM CDL0 003C 47F08178

    This command will disable the SNA fresh load, dynamic load, and fallback functions on the processors that do not have dynamic LU support installed.

    See TPF Operations for more information about the ZAPGM command.

  8. Perform a fresh load on the processor where you are installing dynamic LU support to rebuild the RVT for dynamic LU support and load any new SNA resource definitions that you created in step 4.

    See TPF ACF/SNA Data Communications Reference for more information about the SNA fresh load function.

    Note:
    You must perform a fresh load on this processor even if you did not create new SNA resource definitions.
  9. Enter the ZRIPL command on the processor where you are installing dynamic LU support to complete the fresh load function.

    See TPF Operations for more information about the ZRIPL command.

  10. Enter the ZRIPL command on each of the processors that do not have dynamic LU support installed.

    See TPF Operations for more information about the ZRIPL command.

  11. Continue with the steps in To Install Dynamic LU Support on the Remaining Processors.

To Install Dynamic LU Support on the Remaining Processors

Use the following procedure when you are ready to install dynamic LU support on the remaining processors in your loosely coupled TPF 4.1 system.

  1. Load the updated SNA keypoint (CTK2) to the processor where you are installing dynamic LU support.
  2. Perform a fresh load on the processor where you are installing dynamic LU support to rebuild the RVT for dynamic LU support.

    See TPF ACF/SNA Data Communications Reference for more information about the SNA fresh load function.

    Note:
    You must perform a fresh load on this processor even if you did not create new SNA resource definitions.
  3. Enter the ZRIPL command on the processor where you are installing dynamic LU support to complete the fresh load function.

    See TPF Operations for more information about the ZRIPL command.

  4. Repeat steps 1-3 for each of the remaining processors in the loosely coupled TPF 4.1 system.
  5. Continue with the steps in To Fully Enable Dynamic LU Support.

To Fully Enable Dynamic LU Support

Use the following procedure to fully enable dynamic LU support after you install it on each processor in the loosely coupled TPF 4.1 system.

  1. Use the SNAKEY macro to increase the value of the NUMALS parameter in the SNA keypoint (CTK2). This will create spare entries in the non-LU section of the RVT and allow you to define non-LU resources using dynamic LU support or the ZNDYN ADD command.
  2. Load the new version of the SNA keypoint to each processor in your loosely coupled TPF 4.1 system.
    Note:
    Because you increased the value of the NUMALS parameter, a fresh load will automatically be performed on each processor when you load the new version of the SNA keypoint.

Dynamic LU support is now installed and fully enabled on each processor in the loosely coupled TPF 4.1 system.

Fallback Scenarios

If the conversion to dynamic LU support is not successful, you will need to fall back to the previous TPF environment, correct the problem, and try the conversion again.

To Fall Back to the Previous TPF 4.1 System Environment

If you used multiple TPF images to install dynamic LU support, use the following procedure to easily fall back to the previous TPF environment.

  1. Ensure that the value assigned to the NUMALS parameter in the SNAKEY macro is equal to the number of non-LU resources defined in the OSTG input data set.
  2. On all but 1 of the processors that have dynamic LU support installed, do the following:
    1. Enter the ZNOPL LOAD command and specify the FRESH parameter.
    2. Restore the original version of the SNA keypoint (CTK2).
    3. Perform a hard initial program load (IPL) on the processor and come up on the original TPF image (that is, the image that does not have dynamic LU support installed).
  3. On the last processor in the complex that has dynamic LU support installed, do the following:
    1. Perform a fresh load by using the ZNOPL LOAD command with the FRESH parameter.
    2. Enter ZAREC LIBMML.1B 002 00 to reset the indicator bit in the root dynamic load record (RDLR).
    3. Restore the original version of the SNA keypoint (CTK2).
    4. Perform a hard IPL on the processor and come up on the original TPF image (that is, the image that does not have dynamic LU support installed).
    5. Enter ZAPGM CDL0 003C 4D5081B8 to enable the processors to enter the ZNOPL LOAD, ZNOPL UPDATE, and ZNOPL FALLBACK commands.

Use the following procedure to fall back to the previous TPF environment if you used an offline loader to install dynamic LU support.

  1. Use the same offline loader to fall back to the previous TPF environment.
  2. Once you fall back the last processor that had dynamic LU support installed, enter ZAREC LIBMML.1B 002 00 on that processor. This will reset the indicator bit in the root dynamic load record (RDLR).
  3. Perform an IPL on each processor.
  4. Enter ZAPGM CDL0 003C 4D5081B8 on one of the processors to enable the processors to enter the ZNOPL LOAD, ZNOPL UPDATE, and ZNOPL FALLBACK commands.

See TPF Operations for more information about the ZNOPL LOAD, ZAREC, and ZAPGM commands.