A customer is trying to size their VTL space requirements for BRMS backups. They ran the PRTRPTBRM *CTLGRPSTAT command, after creating the data area to get the retention info included.
A customer with many (over 150) BRMS backup control groups in an LPAR finds that when they run the PRTRPTBRM *CTLGRPSTAT report it provides the usual info for the first 20 or 30 control groups that have been doing backups. Then midway through the listing of daily backups for a control group the report includes the Retention information page containing info expected for the backup control groups reported on so far (alphabetically). 
Then it seems to list the cartridges used for the remaining backup control groups but provides no info on the amount of data being backed up or the run dates/times. Then it completes with a second Retention details page for this latter group of control groups.
This occurs in all their LPARs with large numbers of backup control groups used.
Has anyone seen this before? I am trying to help them with the sizing but without the backup size info for most of the backup control groups it is difficult.

Have you tried using the SQL service QUSRBRM.CG_STATUS  - might be easier / cleaner to digest .....It doesn't look like it has the retention info, but it has the backup size you need/want.

BRMS SQL Services - IBM Partnership -

------------------------------
Rich Malloy
------------------------------

Generate CTLRGPSTAT report by control group
I'm leaving you a simple CLP script that goes through the existing BRMS control groups
and generates the PRTRPTBRM *CTLRGPSTAT report one by one, saving each output with a different
name so you can review them all without losing information.

PGM
DCLF FILE(QUSRBRM/Q1ACTLGRP) /* Archivo donde se listan los grupos */
DLTF FILE(QTEMP/CTLGRP)       
MONMSG MSGID(CPF0000)
CRTPF FILE(QTEMP/CTLGRP) RCDLEN(132)
DSPBRMCTLGRP OUTPUT(*OUTFILE) OUTFILE(QTEMP/CTLGRP)
OVRDBF FILE(Q1ACTLGRP) TOFILE(QTEMP/CTLGRP)
DCL VAR(&GRPNAME) TYPE(*CHAR) LEN(10)
READ: RCVF
MONMSG MSGID(CPF0864) EXEC(GOTO CMDLBL(END))
CHGVAR VAR(&GRPNAME) VALUE(&CTGRPN)
SNDPGMMSG MSG('Generando reporte para grupo: ' *CAT &GRPNAME)
PRTRPTBRM TYPE(*CTLRGPSTAT) CTLGRP(&GRPNAME) SPLFNAME(&GRPNAME)
GOTO CMDLBL(READ)
END: DLTOVR FILE(Q1ACTLGRP)
ENDPGM

Hi Nelson,

Generate CTLRGPSTAT report by control group
I'm leaving you a simple CLP script that goes through the existing BRMS control groups
and generates the PRTRPTBRM *CTLRGPSTAT report one by one, saving each output with a different
name so you can review them all without losing information.
PGM
DCLF FILE(QUSRBRM/Q1ACTLGRP) /* Archivo donde se listan los grupos */
DLTF FILE(QTEMP/CTLGRP)       
MONMSG MSGID(CPF0000)
CRTPF FILE(QTEMP/CTLGRP) RCDLEN(132)
DSPBRMCTLGRP OUTPUT(*OUTFILE) OUTFILE(QTEMP/CTLGRP)
OVRDBF FILE(Q1ACTLGRP) TOFILE(QTEMP/CTLGRP)
DCL VAR(&GRPNAME) TYPE(*CHAR) LEN(10)
READ: RCVF
MONMSG MSGID(CPF0864) EXEC(GOTO CMDLBL(END))
CHGVAR VAR(&GRPNAME) VALUE(&CTGRPN)
SNDPGMMSG MSG('Generando reporte para grupo: ' *CAT &GRPNAME)
PRTRPTBRM TYPE(*CTLRGPSTAT) CTLGRP(&GRPNAME) SPLFNAME(&GRPNAME)
GOTO CMDLBL(READ)
END: DLTOVR FILE(Q1ACTLGRP)
ENDPGM

es, I have seen that behavior with the command PRTRPTBRM *CTLGRPSTAT in LPARs with a high number of BRMS control groups. Apparently, the report has a limitation on the number of groups for which it shows full details, including backup size and execution dates.

An alternative that we have used in those cases is to generate custom reports with SQL by accessing the BRMS history tables (QUSRBRM / Q1ABRWH, QUSRBRM / Q1ABRBK, etc.), which allows to obtain precise details of the volume backed by control group. This makes it much easier to estimate the required VTL space.

We also recommend dividing the control groups into several executions or separate analyses, to avoid cuts in the standard report.  great from Chile