I don't know about Mac, but for NT and 2000, you can use the FINDSTR
command, which includes some grep-like behavior. For example:

   grep -i fail sched.log

could be written as:

   findstr /i /c:fail sched.log

A weaker version of FINDSTR, FIND, is also available. The same command
would be written like this:

   find /i "fail" sched.log

Just as with grep, you can pipe the output to another program.

I work mainly with NT and 2000, so I usually prefer FINDSTR. I don't
believe that FINDSTR is implemented in Win9X, but I'm pretty sure that
FIND is implemented there.

Also, check out the event logging facilities on the server. You can read
about this in the Administrator's Guide, in the chapter on monitoring the
TSM server.

Regards,

Andy

Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: araibeck AT us.ibm DOT com
"The only dumb question is the one that goes unasked."
"The command line is your friend"





Francisco Reyes <lists AT NATSERV DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/27/2001 09:39
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Admin changes in last 2 years?




On Fri, 27 Jul 2001, Cook, Dwight E wrote:

> On the failed client schedules...
> You could set a "postschedcmd" to run a script that does something like
a
>         grep -i fail sched.log | mail -s $(hostname)_bkup_failures
> myid AT my DOT mail.system

How about if the clients are not Unix? In particular NT and Mac.
Except for purchasing the MKS toolkit $$$, I have not found a grep for NT
and I have not even tried to look for a grep on the Mac, specially any pre
OS X Mac. In my opinion this really should be part of the server logs.