Running concurrent multiple recycles within a single GRSplex

Any customer that recycles the same category of DFSMShsm tapes at the same time on different hosts within a GRSplex will encounter failed requests.

Attention: Use the following patches to avoid recycle conflicts between two HSMplexes that use the RNAMEDSN=NO translation method. If you are using RNAMEDSN=YES on either or both, the following patches are unnecessary.

If your environment has a single GRS-type serialization ring that includes more than one HSMplex, you may want to use different resource names (Rnames) for the recycle tape category, which allows multiple HSMplexes to recycle the same category concurrently. You can patch the Rnames to represent different resources. Place the patches in the DFSMShsm startup procedure.

For example, the following PATCH commands illustrate how you could change the RNAMEs to reflect HSMPLEX 1 ('H1').

PATCH .YGCB.+14 'RCYH1-L2' VER(.YGCB.+14 'RECYC-L2')
PATCH .YGCB.+1C 'RCYH1-SP' VER(.YGCB.+1C 'RECYC-SP')
PATCH .YGCB.+24 'RCYH1-DA' VER(.YGCB.+24 'RECYC-DA')

This change does not require that you change the QNAME.

To provide the needed protection, make sure that you use the same resource name in each host of an HSMplex. For example, if a 2-host HSMplex and a 3-host HSMplex share a GRS ring, then apply the same patches to both systems in the 2-host HSMplex or to all three systems in the 3-host HSMplex. One HSMplex can use the DFSMShsm-provided names.

For more information about sysplex environments, see DFSMShsm in a sysplex environment.