This document assumes that you already have TPX set up and running.
Following are the steps required specific to setting up multiple TPX started tasks defined as a generic resource.

Applications such as CICS or TSO can be defined within VTAM as a generic resource - multiple regions or instances grouped together under a common generic resource name.  
TPX can also be defined as a generic resource in VTAM to group multiple TPX started tasks.

Release : TPX 5.4
Component : TPX for z/OS

With TPX defined as a generic resource, each TPX will:

• Access the same VSAM Databases (ADMIN1, ADMIN2, MAIL, NOTES, VIEW)
• Use the same executable load library (LOADLIB) so by default all TPX started tasks will be at the same release and maintenance level
• Use separate TPX VTAM nodes (DO NOT specify ACBNAME in the VTAM major node APPL definition.)
• Have individual VTAM APPL and an exclusive set of VTs (virtual terminals)
• Specify the same Generic Resource parameters

NOTE: If you currently have multiple standalone TPX tasks, each with their own set of VSAM files, you must determine the best way to merge the files using VSAM utilities outside of TPX.

Define VTAM APPLs

1. Each TPX must have an exclusive VTAM APPL and exclusive virtual terminals (ACBs not defined to any other TPX).
2. Specify YES on the SRBEXIT parameter of each APPL statement in your major node.
3. Vary the major node inactive, and then vary it active.

Using the Authorized Path Facility

The APF facility is required for VTAM generic resource support.
Specify Y in the VTAM Authorized Path Facility field of the SMRT Performance Parameters panel.
For information about changing the performance parameters, see the TPX 5.4 Administrating Guide - Modify Parameters on the System Options Table.

Defining the Coupling Facility Structure

When using TPX to operate as a VTAM generic resource, you need to define the Coupling Facility structure.
    Note: To use this feature, TPX must run from an APF-authorized library, as mentioned above.

To define the Coupling Facility structure:

1. Open member CFSTRUCT in the INSTALL data set.
2. Define the name of your structure and its size. Note the structure name consists of two parts:
    
   
   • An eight-byte prefix, which cannot contain blanks.
      
     • Each generic resource name requires its own structure.
     • The generic name must be different than the application network name (VTAM applid of TPX).
     • For details on determining the structure storage requirements, see the TPX Systems Programming Guide.
       The generic resource name used for all instances of the product. You may need more than one generic resource name.
       
       
3. Update the Coupling Facility policy data set to reflect the definition of the structure.
    
4. Update the SMRT Generic Resource Parameters.
    
   
   • prefix (as in step 2)
   • resource name (as in step 2)
   • member count - This is the maximum number of TPX started tasks (applids) that will connect to this generic resource at one time.
     
     For example...
     Coupling facility structure name: STRUCTURE NAME(TPXGR001TPXINT)
     
     Corresponding SMRT:
     

         Generic Resource Parameters
         ---------------------------
             Coupling structure name prefix:  TPXGR001
             VTAM Generic Resource name:      TPXINT
             Generic Resource member count:   04

TPX should not be defined with affinity and as a generic resource.  
These should be considered mutually exclusive.  
Turning on affinity when TPX is defined as a generic resource could cause a conflict between the TPX option and Workload Manager.
We recommend affinity be disabled in a GR setup.  (SMRT System Parameters - Affinity: N)

Generic Resource Parameters
Define the Coupling Facility Structure