I think Q LOG F=D just reports active space usage. My solution was
to monitor the usage on the directory containing the archive log files
through cron. Once the free space on the filesystem drops below a
certain threshold I'll kick off a DB backup using dsmadmc.
On 10/01/10 10:45, Vandeventer,
Are you looking for more than the Q LOG FORMAT=DETAILED produces?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Scott
McCambly
Sent: Friday, October 01, 2010 11:24 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] How to monitor Archive Log space
Yes. Q LOG F=D only shows the Active Log space.
It is true that if the Archive Log space fills to 100% then the Active
Log would not be able to clear archived logs and it too would then
begin filling towards 100%, but I want to know about the Archive Log
being full long before then, and before
TSM will monitor the usage of the archive log file system (please make sure
it's a file system/Windows drive, not just a directory in some file system). If
you find that there are frequent database backups triggered, you might want to
make the file system/Windows drive bigger. There is an
