Instead of using CRON to schedule the script, why not have a TSM client schedule with ACTION=COMMAND pointing to the script. Then the 'script' could be for any OS. We do this on AIX and NT/2K also also use Perl to pretty-up the output. This way if you need to change the time the script runs, you don't need ROOT access to the AIX server, just TSM admin access. Plus you get the benefit of being able to report on the success/failure/miss of the schedule with the Q EVENT command.
Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of George Lesho Sent: Tuesday, March 05, 2002 12:52 PM To: [EMAIL PROTECTED] Subject: Re: reporting on backup successes/failures Depends on what O/S your TSM server is running on but for an AIX server, a script running out of cron which queries events for the past 24 hours seems to work for me (plus the script checks lots of other things)... George Lesho AFC Entprises "Glass, Peter" <Peter.K.Glass@WELLS To: [EMAIL PROTECTED] FARGO.COM> cc: (bcc: George Lesho/Partners/AFC) Sent by: "ADSM: Dist Subject: reporting on backup Stor Manager" successes/failures <[EMAIL PROTECTED] U> 03/05/02 10:26 AM Please respond to "ADSM: Dist Stor Manager" What would be the best way to produce a report that shows the number of client backup successes vs. failures, for a given day? Peter Glass Distributed Storage Management (DSM) Wells Fargo Services Company > * [EMAIL PROTECTED] >
