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 undocumented dsmserv.opt option, ARCHLOGUSEDTHRESHOLD xx where xx is the percentage fullness of the file system that you are using for the archive log file system to trigger a database backup. If you have a large file system, say 500GB or 500GB, and you find that there is a lot of empty space in it, you might want to set xx fairly high, for example ARCHLOGUSEDTHRESHOLD 90. I don't know if this option will be documented or if it will persist over TSM releases. Other options have become invalid, for example the DISKSTGPOOLMemsize option is no longer valid even though it is still documented in the 6.2 Admin Ref book.
Joerg Pohlmann 250-585-3711 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Scott McCambly Sent: Friday, October 01, 2010 10:58 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to monitor Archive Log space in TSM V6? 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.vandeven...@da.ks.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 >
