MFE SCF: How to determine SRP usage for a device or for an application
Summary: This article provides instructions on how to determine Storage Resource Pool (SRP) usage for a device or for an application (multiple devices in the application).
Instructions
How to determine SRP usage for a device or for an application:
1) This process is a manual calculation procedure. This method is a workaround until the engineering enhancement requests are approved. The enhancements are designed to provide data that makes the SRP usage determination simpler.
2) The SRP usage calculation requires a calculation of the Standard Allocations counts for source and target volumes. The Shared Owned allocations from the CREATE ONLY of SNAPSHOTs, SNAPSETs, and HardLinks are used to obtain the replicated data. This can be accomplished by collecting these two reports:
The QUERY ALLOC report:
EMCU500I QUERY ALLOC LOCAL(UNIT(8010)) DEV(040-042)
EMCU060I Thin Allocations on 0001976-00361 API Ver: 8.40
EMCU014I Device# Alloc Used Shared Persist SRP Name
EMCU015I 00000040 30020 30020 30017 N SRP_0x102
EMCU015I 00000041 17 17 0 N SRP_0x102
EMCU015I 00000042 30020 3 30017 N SRP_0x102
The QUERY ALLALLOCS report:
The QUERY ALLALLOCS is used when there is more than one pool under an SRP. This can occur when adding devices to an existing SRP, since all devices in a pool have to have the same physical characteristics. In this manner, the two pools' allocations are added together.
In the following example, pools DG1_C_7 and DG2_C_7 are operating as one for device 0024:
EMCU500I QUERY ALLALLOCS LOCAL(UNIT(8010)) DEV(0024)
EMCU060I Thin Allocations on 0001976-00361 API Ver: 8.40
EMCU015I 00000024 76981 DG1_C_7
EMCU015I 00000024 288232 DG2_C_7
The QUERY SNAPSHOT with the MLQ(YES) report is used for SNAPVX (Legacy SNAP requires QUERY VOLUME with the MLQ(YES) report). For zDP, can use the QUERY SNAPSHOT with the MLQ(YES) or the EIPINIT program QUERY VDG(vdgname) with SNAPSET parameter.
EMCP001I QUERY SNAPSHOT(UNIT(8010) DEV(040-047))
ESNP1AAI SRC CUU VOLSER TGT CUU VOLSER NAME YYDDD/HH:MM:SS STATUS ACT
ESNP1AAI ----------------------------------------------------------------------------------------------------------
ESNP1AAI 00000040(N/A ) FFFFFFFF(N/A ) BOP8010SEQ1 20149/11:11:17 CREATE SOFT Y
ESNP1AAI UNIQUE TRACKS: 0000000000
ESNP1AAI SRC MODIFIED TRACKS (UNIQUE+SHARED): 0000000000
ESNP1AAI TGT MODIFIED TRACKS (UNIQUE+SHARED): 0000000000
ESNP1AAI TRACKS TO BE COPIED: 0000000000
ESNP1AAI TIME TO LIVE DDDD/HH:MM:SS: 0000/00:00:00
ESNP1AAI TIME SINCE CREATION DDDD/HH:MM:SS: 0000/00:01:22
ESNP1AAI SNAPSHOT ID: ADAD0001
ESNP1AAI SECURE SNAPSHOT: NO
ESNP1AAI COPY MODE: N/A
ESNP1AAI TARGET HOLD: N/A
ESNP1AAI
ESNP1AAI -----------------------------------------------------------------------------------------------------------
ESNP1AAI
ESNP1AAI TOTAL UNIQUE TRACKS IN REQUEST: 0000000000000000
ESNP1AAI TOTAL TRACKS TO BE COPIED IN REQUEST: 0000000000000000
ESNP1AAI TOTAL SRC MODIFIED TRACKS (UNIQUE+SHARED) IN REQUEST: 0000000000000000
ESNP1AAI TOTAL TGT MODIFIED TRACKS (UNIQUE+SHARED) IN REQUEST: 0000000000000000
3) The SRP usage calculation is calculated by totaling the Used column for a device (or all devices in a job) from the QUERY ALLOC report. Then add that count to the TOTAL UNIQUE TRACKS at the bottom of the Query SNAPSHOT report. Do the count for the CREATE SNAPSHOTs ONLY of that device (or all devices in an application or job).
Note: From the QUERY SNAPSHOT report, do not include linked target tracks as these are copies of the CREATE SNAPSHOTs. These tracks are counted in the QUERY ALLOC STD USED for the target devices.
For more details, review the Mainframe Enablers (MFE) product guides for the target release.