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 : CA TPX for z/OS
With TPX defined as a generic resource, each TPX will:
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
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 CA-TPX to operate as a VTAM generic resource, you need to define the Coupling Facility structure.
Note: To use this feature, CA-TPX must run from an APF-authorized library, as mentioned above.
To define the Coupling Facility structure:
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)