Defining VTAM resources in a parallel sysplex

In an installation with a Parallel Sysplex® where the scheduler can start on any of a number of z/OS® images, each z/OS image within the parallel sysplex should have the same local LU name for a given server. The same LU name must not exist in any other network interconnected to the parallel sysplex network; identical LU names within network, unique LU names across networks.

For details on the parallel sysplex installation, see Step 14. Using XCF for communication.

For installations with VTAM® Version 4 Release 3 the LU name (the APPL statement name) should be given with a wildcard character, in case the scheduler works in a parallel sysplex and is not set up to run on a specific z/OS image. The APPL statement will then become a Model Application Program Definition, for the identically named LUs on the z/OS images where the scheduler might start. The wildcard character should be chosen such that one model definition is set up for the controller and one model definition for each of the servers. The optional ACBNAME parameter must be omitted, the name of the APPL statement is then used as the ACBNAME.

For example, say the scheduler can start on z/OS images MVS1 and MVS2 in a parallel sysplex. The LU name for controller OPCB is IS4MOPCB, and there are three servers to handle the communication to OPCB, OPCBCOM1, OPCBCOM2 and OPCBCOM3, with LU names IS4MSV1B, IS4MSV2B and IS4MSV3B. VTAM Version 4 Release 3 is available. The following model definitions could then be used (a '?' in the APPL statement name represents a single unspecified character):

 IS4MOP?B  APPL APPC=YES,...
 IS4MS?1B  APPL APPC=YES,...
 IS4MS?2B  APPL APPC=YES,...
 IS4MS?3B  APPL APPC=YES,...

Note that the wildcard character must be chosen such that the no other VTAM LU name than the intended LU name matches the model definition.