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.
PROTECTED]
Pour :[EMAIL PROTECTED]
cc :
Objet : RE: Réf. : Re: Backup reporting
I believe that this only affects the summary table data, not the accounting
records. The accounting records are correct in the byte counts. I know you
can't get it with a simple SQL, but it's there. Can you speak PERL
I believe that this only affects the summary table data, not the accounting
records. The accounting records are correct in the byte counts. I know you
can't get it with a simple SQL, but it's there. Can you speak PERL??
Bill
-Original Message-
From: ADSM: Dist Stor Manager
Hello,
there is still a problem with the number of bytes
reported in the summary table for sessions that get
dropped and restarted. There is apar IC34462 on this
subject. This apar is currently opened and does not
have a fix/patch just yet.
It would be a good idea to open a pmr like you said
so
