ADSM-L

Re: [ADSM-L] Log issues and scheduled commands and CHANGINGRETRIES

2010-04-08 11:09:37
Subject: Re: [ADSM-L] Log issues and scheduled commands and CHANGINGRETRIES
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 8 Apr 2010 11:08:40 -0400
Thanks for the info and suggestions.

Thought about the "low power" id but we need the "show logpinned" to see
the culprit.

As much as folks use these "undocumented/unsupported commands", I am
surprised IBM hasn't given us an equivalent "supported" command.  I even
saw a patch for the "show logpinned" command.
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html



From:
"Allen S. Rout" <asr AT UFL DOT EDU>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
04/08/2010 10:35 AM
Subject:
Re: [ADSM-L] Log issues and scheduled commands and CHANGINGRETRIES
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



>> On Thu, 8 Apr 2010 10:17:11 -0400, Zoltan Forray/AC/VCU
<zforray AT VCU DOT EDU> said:

> So, I would like to schedule a "show logpinned" command every 15-minutes
> and send the output somewhere so it can be emailed to me.

> I have never messed with server scripting so this is new territory for
me.

> Does anyone have a script/process they can share, to deal with this? The
> TSM servers are RedHat Linux 5.



You want to drop email, so there needs to be an outside-tsm component
to it.

In that case, I'd suggest something like the following:


Define an admin ID with no privileges.  This becomes the appropriate
credential for putting passwords in scripts so you can ask questions
from outside the server.

Then develop the command you want to run.  I don't know if 'q log'
will satisfy you; 'sh' requires more privileges.

You don't want mail every 15 minutes, you want mail if the log is more
full than [foo], right?


If you're comfortable in PERL, there are a variety of modules out
there to ease the transition from TSM to easy PERL data structures:
mine is


http://nersp.osg.ufl.edu/~asr/media/cg/tsm_query.pm


and I use it to say things like

my ($devsize) = &tsm_query($server,
"select capacity  from devclasses where devclass_name='$targetdev'");

or

my @fses = &tsm_query($server,
"select node_name,filespace_name,filespace_ID,backup_end,filespace_type
from filespaces order by node_name,filespace_ID");

 foreach $line (@fses)
   {
     my ($node,$fs,$id,$end,$type) = split(/,/,$line);
     # yadda yadda

   }




- Allen S. Rout