dsmaccnt.log not moved to new dir structure during v3.7 TSM

-IBM/Tivoli still verifying this one, but I didn't want "you'all"
to loose any good dsmaccnt.log info.
to loose any good dsmaccnt.log info.
Platform:  TSM on AIX.
Possible users effected: Those who have accounting turned on...do
    a     q status   command...about 16 (or so) lines down...
Upgrade scenario: upgrading from 3.1.2.42 to 3.7.0.0 (then onto 3.7.2.0..)
SUM: TSM's install changes the install directory structure to a new target
location. At least for me, the dsmaccnt.log file was not moved and may (for
you) have to be moved 'manually.'
Be advised..
FYI Thanks Tim

DETAIL:
Abstract: dsmaccnt.log and TSM 3.7 upgrade

Since you guys are changing the location of adsm/tsm from
/usr/lpp/adsmserv/bin to
/usr/tivoli/tsm/server/bin...AND
you have in the readme.srv that dsmserv.dsk and dsmserv.opt will be
"copied" to the 'new' directory...2 questions...
Since 'ADSM will be deinstalled (again, according to the readme),
will /usr/lpp/adsmserv/bin be deleted??!!
How will the dsmaccnt.log file be handled for those who have set
accounting on??!!
Thanks Tim
 -IBM                   -576556402  -                 00/02/28-12:41-
 -IBM                   -576556402  -                 00/02/28-14:33-
 -IBM                   -576556402  -                 00/02/28-15:13-
Tim,
The /usr/lpp/adsmserv/bin directory will not be deleted.  The
dsmaccnt.log should be copied to the /usr/tivoli/tsm/server/bin
directory, just like the dsmserv.dsk and dsmserv.opt files.
Regards,
G



 -FRTO13    FRTO        -576556402  -                 00/02/29-13:18-
RESPOND ELECTRONICALLY.
[spdo11][/usr/lpp/adsmserv/bin]>ls
adsmserv.devconfig    dsmaccnt.log          log.dsm
adsmserv.volhistory1  dsmserv.err           nodelock
db.dsm                dsmserv.samp          tivready.dsm
delit                 fixinfo.srv
**
dsmaccnt.log was neither copied or moved.
**
readme.srv indicates a COPY (difference between move and copy), but
the upgrade process moved dsmserv.dsk and the dsmserv.opt.
**
awaiting response.


 -IBM                   -576556402  -                 00/02/29-21:18-
 -IBM                   -576556402  -                 00/02/29-21:19-
Action taken: Reviewed pmr update.  Requested time on lab system to
              attempt to recreate upgrade from 3.1 -> 3.7 server.
Action plan:  Test 3.1->3.7 upgrade for correct behavior regarding
              the copying of the dsmserv.opt, dsmserv.dsk, dsmaccnt.log.
dsmaccnt.log not moved to new dir structure during v3.7 TSM upgrade
