I'll take a stab at a possible solution if you haven't found a
solution yet.

        As we upgraded our ADSM servers to latter versions of the OS and the
TSM server software, we experienced significant slowdowns on the system
especially when there were multiple sessions or processes going on. We
eventually found our answer in the readme file for the TSM server. I believe
this  bit us when we upgraded the OS as you did.

Here are some notes from the readme file for version 4.1.1.

_______________________________
**********************************************************************
* Possible performance degradation due to threading                  *
**********************************************************************

On some systems Tivoli Storage Manager for AIX may exhibit significant
performance degradation due to TSM using user threads instead of
kernel threads.

This may be an AIX problem however, to avoid the performance degradation
you should set the following environment variables before you start
the server.

    export AIXTHREAD_MNRATIO=1:1
    export AIXTHREAD_SCOPE=S
_______________________________

        Not having these 2 settings basically turns your multi-threading
machine into a single-threaded process and performance really gets bad.

        Making these changes don't require a reboot, so it's worth a shot to
add these in, make sure they get sourced into your current environment (by
logging out & back in, or just running these 2 lines) and then stop and
start the ADSM service.


Ben Bullock
Unix system manager
Micron Technology Inc.


> -----Original Message-----
> From: irene [mailto:irene AT MAILDROP.SRV.UALBERTA DOT CA]
> Sent: Wednesday, June 27, 2001 9:54 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: ADSM 3.1.2.90 on AIX 4.3.3-06
>
>
> We were running ADSM 3.1.2.90 on AIX 4.2.1 and it behaved
> normally.  When we migrated AIX to 4.3.3-06, ADSM slowed
> down to unacceptable response times.  For example, a backup
> that used to take 5 minutes now takes 50 minutes.  The operating
> system seems to be performing O.K.  All of this is being done on
> a test machine at the moment.  Does anyone have any ideas
> why this is happening?  Should we have done a complete overwrite
> rather than a migrate when moving to AIX 4.3.3-06 from AIX 4.2.1?
> Thank-you for any insight provided.
>   Irene Braun
>   EMAIL:  irene.braun AT ualberta DOT ca
>