da
Sent: Wednesday, November 17, 2004 2:20 PM
To: [EMAIL PROTECTED]
Subject: Re: dsmsched.log , reporting
It's the ACTLOG table. One of the columns is SEVERITY (you can ask for
all E or W messages), or select on the specific message numbers that
have the information you want.
Andy'
Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Prather, Wanda
Sent: Wednesday, November 17, 2004 3:20 PM
To: [EMAIL PROTECTED]
Subject: Re: dsmsched.log , reporting
It's the ACTLOG table. One of the columns is SEVERITY (you can ask for all
E or
ms for you!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Mike Bantz
Sent: Wednesday, November 17, 2004 5:11 PM
To: [EMAIL PROTECTED]
Subject: Re: dsmsched.log , reporting
Any hints on what tables and columns to query off of? I'm comfortable
with a
s
Prather, Wanda
Sent: Wednesday, November 17, 2004 2:54 PM
To: [EMAIL PROTECTED]
Subject: Re: dsmsched.log , reporting
The client file failures and the summary information is all echoed back to
the TSM server activity log - you can get it with a SELECT.
: [EMAIL PROTECTED]
Subject: dsmsched.log , reporting
Anyone have a good mechanism for looking at the tail end of a clients
dsmsched.log from the server ?? ie.. maybe an sql query that allows me
to look into the client logs. I dont want to scroll through each client
log to see if there were
Have you looked at the TSM operational reporting feature?
If so, what items in the client logs are missing from ops reporting?
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail:
Anyone have a good mechanism for looking at the tail end of a clients
dsmsched.log from the server ?? ie.. maybe an sql query that allows me to look
into the client logs. I dont want to scroll through each client log to see if
there were failures and if so what they were, each day. The importa
