To migrate the existing CXRC sessions from individual
coupling to clustering, do the following steps:
- Suspend the master session by using the TIMEOUT parameter and
install the program temporary fix (PTF).
- Issue the XCOUPLE PURGE command to clear the information about
the individual sessions from the master session.
- Modify the ANTXIN00 parmlib member to associate each data mover
LPAR with a master session and a unique cluster name. To modify the
ANTXIN00 parmlib member, use the ClusterMSession and the ClusterName
parameters in the STARTUP category. Here is an example:
STARTUP -
ClusterMSession(TUCSON) -
Clustername(SYSTEM1 CLUSTER1 - SYSTEM2 CLUSTER2 - SYSTEM3 CLUSTER3)
- Modify the parmlib to enable the cluster monitoring to data set
(optional).
- Allocate and initialize a cluster control data set for each LPAR
that operates as a cluster. Use the following JCL as an example:
//STEP1 EXEC PGM=IEBDG
//SYSPRINT DD SYSOUT=*
//DD1 DD DSN=mhlq.XCOPY.clustername.CLUSTER,
// DCB=(RECFM=FB,LRECL=15360,BLKSIZE=15360,DSORG=PS)
// SPACE=(CYL,(1,0)),STORCLAS=XRCSTATE,DISP=(NEW,CATLG)
//SYSIN DD *
DSD OUTPUT=(DD1)
CREATE QUANTITY=30
END
Note: You cannot use the extended format data
set. You can place the data set on the same volume as any state data
set accessible by the cluster LPAR.
- To collect the cluster-level monitor data, allocate a state data
set for each cluster. Use the following JCL as an example:
//STEP2 EXEC PGM=IEFBR14
//DD1 DD DSN=mhlq.XCOPY.clustername.STATE,
// DCB=(RECFM=F,LRECL=4096,BLKSIZE=4096,DSORG=PO),
// DSNTYPE=LIBRARY,
// SPACE=(CYL,(2,0,1)),STORCLAS=XRCSTATE,DISP=(NEW,CATLG)
The
data set must be a PDSE data set. The data set can be placed on the
same volume as any state data set accessible by the cluster LPAR.
In the XRC parmlib, ensure that the MONITOR category for each individual
XRC session in the cluster has MonitorOutput(ON). If a MonitorWakeup
value is specified, use the same value for all individual XRC sessions
in the cluster.
- You can attain the following results by changing the XRC parmlib
to use a smaller SHADOW READDELAY value, such as 500:
- Achieve more aggressive Recovery Point Objective targets.
- Avoid delays from lightly loaded data movers in large scale configurations.
Note: This operation results in higher CPU utilization
during periods of non-peak workloads.
- Issue the F ANTAS000,CREFRESH command to each LPAR to initiate
cluster setup processing.
- Restart individual sessions and resynchronize.
- When duplex is reached, issue the XCOUPLE ADD command to couple
individual sessions to the master session.
Note: Do not
use the cluster name in the XCOUPLE commands.
Note: Before increasing the number of XRC data
movers per LPAR, ensure that sufficient system resources (processor
and memory) are available to handle the expected simultaneous peak
data mover workload. Workload demands and system constraints might
significantly reduce the number of data movers that can run effectively
on a given LPAR.
To migrate the existing CXRC sessions from clustering
to individual coupling, do the following steps:
- Suspend master session by using TIMEOUT parameter.
- Issue XCOUPLE PURGE command to clear information about all individual
XRC sessions that are previously coupled through the cluster.
- Modify the ANTXIN00 parmlib member to specify ClusterMSession
(DISABLED).
- Issue F ANTAS000,CREFRESH command to restart the cluster setup
processing and disable clustering.
- Issue XCOUPLE ADD command to couple the individual XRC sessions
to the master session.
Note: You can only migrate the existing
CXRC sessions from clustering to individual coupling when the coupled
session has fewer than 14 individual XRC session members.