Le 09/11/2015 20:46, rob@xxxxxxxxx a écrit :
Thank you.
Is this out of line?
Default interval . . . . . . . . 15.00
This is the default value. It should be OK.
Collection library . . . . . . . QPFRDATA
Default collection profile . . . *STANDARDP
It collects basic parameters, including network usage. It should be OK.
Cycle time . . . . . . . . . . . 000000
Every new *MGTCOL starts at midnight. Fine.
Cycle interval . . . . . . . . . 24
One new *MGTCOL is created every 24 hours. Fine.
*MGTCOL retention period:
Number of units . . . . . . . 00168
Unit of time . . . . . . . . . *HOURS
*MGTCOL objects are deleted from the system 168 hours (7 days) after
their usage for collecting data.
Note that *MGTCOL must be dumped to database file to be analyzed (with
CRTPFRDTA command or with "Create standard database files" set to *YES
during collection). I am not aware of any interface to access *MGTCOL
content.
You could, may be, reduce the retention to 2 or 3 days, as they are
dumped to database members.
Enable system monitoring . . . . *YES
Create standard database files *YES
As far as members...
File . . . . . . QAPMAPPN
Library . . . . QPFRDATA
Member Date
Q302000021 10/30/15
Q303000021 10/31/15
Q304000021 11/01/15
...
Q310000021 11/07/15
Q311000021 11/08/15
Q312000021 11/09/15
Q313000021 11/09/15
Database members can be removed according to STDDTARET parameter of
CFGPFRCOL. And, If I remember fine, PM/400 processes can also remove
those members depending on CFGPM400 or GO PM400 settings.
Therefore, in my opinion, the size of *MGTCOL is due to your workload.
All the *MGTCOL below look to have the same size per day, around 4,5 GB.
You have 3 collections for 01th of November probably because of some
restricted state (or collecting jobs ended) between 01:00 and 23:00, but
the total is quite 4,5 GB.
The size of the collection of 05th of November is lower than the other
because of the RTVDSKINF snapshot at 04:00.
Information collected . . . . . . . . . : 11/05/15 04:00:00
Library/ % of Size in Last
Object Type Owner Library 1000 bytes Change
QPFRDATA *LIB QSYS 34438541.3 11/05/15
Q303000102 *MGTCOL QCOLSRV 13.04 4491321.3 10/30/15
Q306000102 *MGTCOL QCOLSRV 13.04 4491321.3 11/02/15
Q307000102 *MGTCOL QCOLSRV 13.04 4491321.3 11/03/15
Q308000102 *MGTCOL QCOLSRV 13.04 4491321.3 11/04/15
Q302000102 *MGTCOL QCOLSRV 12.99 4474544.1 10/29/15
Q304000102 *MGTCOL QCOLSRV 12.85 4424212.5 10/31/15
Q305010002 *MGTCOL QCOLSRV 11.82 4069138.4 11/01/15
Q309000102 *MGTCOL QCOLSRV 2.29 787136.5 11/05/15
Q305000102 *MGTCOL QCOLSRV 1.16 400629.8 11/01/15
Q305230102 *MGTCOL QCOLSRV .63 216473.6 11/01/15
If the size of QPFRDATA is a concern, you could keep less *MGTCOL.
Usually we keep only two of them, but we make sure to have 40 days of
database members so that we cover one month and more.
Rob Berendt
Marc
midrange.com
