Since the security issue affects just the client, I don't see how the
server repackage could be related. I am bucking this over to the server
folks to see if they know what happened to the info about fixed APARs.

Regards,

Andy

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

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

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

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 09/28/2007
08:31:58 AM:

> I notice that there are 5.4.1.2 server versions on the ftp site this
> morning,
> but nothing in the README that points to the problems that have been
> fixed. Is this just a repackaging of 5.4.1.1 in light of the security
> announcement
> earlier this week?
>
> Also, as I moved from 5.4.0.x to 5.4.1.x on my AIX servers, I've noticed
> that
> the 'pick order' for reclamations has changed. It used to be that the
> volumes
> with the most amount of available space were reclaimed first; with
> 5.4.1.x
> (5.4.1.1 at least), it's using the recl=xx setting and working its way
> 'backwards'.
>
> As an example, if I have three volumes with the following amounts of
> reclaimable space:
>
> VOL000 99.9
> VOL001 98.3
> VOL002 95.7
>
> Under 5.4.0.x, a rec=95 would start processing VOL000 first and
> then proceed to VOL001 and then VOL002. Under 5.4.1.x, issuing the
> same rec=95, the server starts processing in the reverse order, starting
> with VOL002.
>
> Is this 'fixing' something?
>
> Gretchen Thiele
> Princeton University