How to use a single PROC for Datacom Primary and Shadow MUF regions
Article ID: 129884
Updated On:
Products
CA Datacom
CA DATACOM - AD
CA CIS
CA Common Services for z/OS
CA 90s Services
CA Database Management Solutions for DB2 for z/OS
CA Common Product Services Component
CA Common Services
CA Datacom/AD
CA ecoMeter Server Component FOC
CA Easytrieve Report Generator for Common Services
CA Infocai Maintenance
CA IPC
Unicenter CA-JCLCheck Common Component
CA Mainframe VM Product Manager
CA Chorus Software Manager
CA On Demand Portal
CA Service Desk Manager - Unified Self Service
CA PAM Client for Linux for zSeries
CA Mainframe Connector for Linux on System z
CA Graphical Management Interface
CA Web Administrator for Top Secret
CA CA- 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.
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:
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
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
Feedback
Yes
No
Powered by
