ADSM-L

Re: Server Level 5.1.7.0 & APAR IC34754

2003-06-25 22:24:06
Subject: Re: Server Level 5.1.7.0 & APAR IC34754
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 25 Jun 2003 19:23:41 -0700
There is an APAR for this problem, IC36575. I asked about this, and
learned that this was discovered and fixed before 5.1.7.0 went out the
door. But because of the timing, a risk/benefit analysis yielded that the
risk of putting in a fix for what is basically a cosmetic issue in 5.1.7
so soon before it was scheduled for delivery was too great. And that's how
we ended up effectively trading one problem for another.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Coyle, Jack" <Jack.Coyle AT REXHEALTH DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06/25/2003 04:54
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Server Level 5.1.7.0 & APAR IC34754



Like the rest of the group, our 5.1.x server suffered the "mashed" output
from a "query process" command. An append to this forum from Mr. Raibeck
indicated that this behavior was indeed anomalous and that APAR IC34754
had
been opened to address the problem. We have obtained level 5.1.7.0
recently
and the README.SRV file indicates that this level indeed contains the
"fix"
for the subject APAR. However, after installing the level on our AIX 4.3.3
server, we are now seeing output from a "query process" command similar to
that shown below. Has anyone else observed "strange" output after applying
what was supposed to be a fix for strange output?

Regards,
Jack Coyle
Rex Healthcare
(919) 784-3792
jack.coyle AT rexhealth DOT com

tsm: SRV_01>q pro

 Process Process Description  Status

  Number
-------- --------------------
-------------------------------------------------
       1 Space Reclamation    Volume 10202 (storage pool TAPEPOOL1), Moved

                               Files: 5624, Moved Bytes: 3,212,860,540,

                               Unreadable Files: 0, Unreadable Bytes: 0.

                               Current Physical File (bytes):

                               35,241,912
Current input volume: 10202.
Current
                               output volume: 10042.


tsm: SRV_01>q pro

 Process Process Description  Status

  Number
-------- --------------------
-------------------------------------------------
       1 Space Reclamation    Volume 10202 (storage pool TAPEPOOL1), Moved

                               Files: 5635, Moved Bytes: 3,656,498,172,

                               Unreadable Files: 0, Unreadable Bytes: 0.

                               Current Physical File (bytes): 2,080,724
Current
                               input volume: 10202.
Current output volume:
                               10042.


tsm: SRV_01>q pro

 Process Process Description  Status

  Number
-------- --------------------
-------------------------------------------------
     234 Space Reclamation    Volume 10053 (storage pool TAPEPOOL1), Moved

                               Files: 4464, Moved Bytes: 1,263,379,404,

                               Unreadable Files: 0, Unreadable Bytes: 0.

                               Current Physical File (bytes): 754,580
Current
                               input volume: 10053.
Current output
                               volume: 10201.

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