ADSM-L

RE: Réf. : Re: Backup reporting: SUMMARY TABLE ISSUE IS FOUND

2002-10-21 02:24:14
Subject: RE: Réf. : Re: Backup reporting: SUMMARY TABLE ISSUE IS FOUND
From: Don France <DFrance-TSM AT ATT DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sun, 20 Oct 2002 03:10:10 -0500
Better yet, ignore all the backup/restore/archive/retrieve data in SumTab...

It is truly FUBAR, at this point in time -- especially with all the multiple
threads & recovery sessions being done;  I haven't seen a good point-release
for b/a statistics since 4.1!

BTW, only ba-client records session info;  TDP agents & BRMS were not
updated for SumTab... just as well stick to either/both of actlog and
dsmaccnt.log (like SMF, it just keeps humming along).

OTOH, the admin processing stats are nice to have, and this is the only
place to get them -- unless you want to scan the actlog for the grubby
details (okay by me).

Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france AT att DOT net

Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Seay, Paul
Sent: Tuesday, October 15, 2002 8:37 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: RE: Rif. : Re: Backup reporting: SUMMARY TABLE ISSUE IS FOUND


Yes, this is true.  And, according to the Level 2 person involved with this
APAR 4.2.3 requires a upgradedb as a result.  He thought for this fix.
Sorry, I was the one that opened the APAR.  But, at least they may have
fixed it this time.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180


-----Original Message-----
From: Guillaume Gilbert [mailto:guillaume.gilbert AT DESJARDINS DOT COM]
Sent: Tuesday, October 15, 2002 9:59 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Rif. : Re: Backup reporting: SUMMARY TABLE ISSUE IS FOUND


Just got word from Tivoli that APAR IC34462: BYTES FIELD IN SUMMARY TABLE
SHOWS VALUE 0 IF THE BACKUP SESSION IS LOST AND WHEN REOPENED AGAIN is fixed
in maintenance level 4.2.3.0 and is now available.

Guillaume Gilbert
CGI Canada

<Prev in Thread] Current Thread [Next in Thread>