Hi Wayne,
I know that this problem didn't exist in V3.7 or V4.1 since both were tested
and deployed.
Thanks.
-----Original Message-----
From: Wayne T. Smith [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 18, 2001 3:33 PM
To: [EMAIL PROTECTED]
Subject: Re: Custom dsm.opt in Client v4.1.2
Thanks to Jennifer and Arthur for discussing this TSM Windows client
bug. Some postings on ADSM-L last year suggest that the problem
may have been around since v3.7 (but I can't verify that, as we
skipped v3.7 for a number of reasons).
We tailor our installables very much as Cornell does. None of files
DSM.OPT, dsm.opt, ba_dsm.opt, BA_DSM.OPT nor dsm.smp in the
/program files/Tivoli/TSM/config folder get copied during install of
v4.1.2. No dsm.opt or dsm.new is created on install.
The v4.1.2 wizards are quite wonderful compared to the 10-foot long
DSMCUTIL command we used to have to force on our client
operators. This tailored DSM.OPT facility is quite important to us
however!
Can a Tivoli person or anyone else recommend I open a PMR/APAR
on the subject, or is support aware and working on the problem? Can
I answer this question with a DB search someplace?
Thanks, wayne
Wayne T. Smith [EMAIL PROTECTED]
ADSM Technical Coordinator - UNET University of Maine System
---------------------------------------
The information contained in this e-mail message, and any attachment thereto, is
confidential and may not be disclosed without our express permission. If you are not
the intended recipient or an employee or agent responsible for delivering this message
to the intended recipient, you are hereby notified that you have received this message
in error and that any review, dissemination, distribution or copying of this message,
or any attachment thereto, in whole or in part, is strictly prohibited. If you have
received this message in error, please immediately notify us by telephone, fax or
e-mail and delete the message and all of its attachments. Thank you.
Every effort is made to keep our network free from viruses. You should, however,
check this e-mail message, as well as any attachment thereto, for viruses. We take no
responsibility and have no liability for any computer virus which may be transferred
via this e-mail message.
