ADSM-L

Re: [ADSM-L] How to monitor Archive Log space in TSM V6?

2010-10-01 13:59:59
Subject: Re: [ADSM-L] How to monitor Archive Log space in TSM V6?
From: Scott McCambly <mccambly AT UNOPSYS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 1 Oct 2010 13:58:04 -0400
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 an automatic backup is
triggered by DB2.

Also, I would simply like to track the usage during the day.

Quoting "Vandeventer, Harold [BS]" <Harold.Vandeventer AT DA.KS DOT GOV>:
Are you looking for more than the Q LOG FORMAT=DETAILED produces?



Happy Friday everyone.

Does anyone know of a way to monitor the current utilization, along
with total
and free space, in the Archive Log directory from within TSM or DB2?  I guess
this is really a DB2 question.

It is clear that DB2 does this internally so that it can trigger automated DB
backups, but I have never seen any reference to queries or tables
accessible via
SQL that report anything other than the size and utilization of the
space within
the pre-allocated Active Log files.

I am trying to remotely monitor this resource on a number of TSM servers on
different platforms and don't want to go the route of rsh/rexec if possible.

Thanks!
Scott


<Prev in Thread] Current Thread [Next in Thread>