How to use a single PROC for Datacom Primary and Shadow MUF regions

Products

• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• Datacom/AD
• CA ecoMeter Server Component FOC
• EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA On Demand Portal
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Primary/Shadow configuration requires that each MUF region runs with its own PXX dataset, i.e. PXX cannot be shared between the two MUF regions.

How to use a single JCL deck to start both the members of a Primary/Shadow MUF pair.

Environment

Release: DATABB00200-14.0-Datacom/AD
Component:

Resolution

Here are two possible options:
1) use a temporary PXX dataset in the JCL:
   //PXX DD DSN=&&PXX,UNIT=SYSDA, 
   //    SPACE=(TRK,(1000)),DISP=(,DELETE)
2) if the MUF STCs are running on the two different LPARs (e.g. TST1 and TST2), then two permanent datasets can be allocated with dsn names like:
   hlq.TST1.PXX
   hlq.TST2.PXX
   and then the PXX in the MUF startup can be referenced using the &SYSNAME variable:
   //PXX DD DSN=hlq.&SYSNAME.PXX