Hi all,
A new fixtest for the Windows Intel client is now available:
ftp site: service.boulder.ibm.com
directory: /storage/adsm/fixtest/v3r1/win32/intel
files: IC24236C.BAT
IC24236C.FILE1.EXE
IC24236C.FILE2.EXE
IC24236C.FILE3.EXE
IC24236C.FILE4.EXE
IC24236C.FILE5.EXE
IC24236C.FILE6.EXE
IC24236C.FILE7.EXE
IC24236C.README.1ST
IC24236C.README.FTP
The .BAT and .EXE files must be downloaded in binary format;
the README files are ASCII. Please review the README.FTP file
for installation information.
The following describes the fixes in this fixtest.
Fixtest 7c, IC23129 ADSM 3.1.0.6 client installation under Windows NT
and Windows 95 brings empty extra window with 2
buttons "Yes" and "No".
IC24185 Client option ERRORLOGRETENTION does not work
correctly. This APAR is related to IC24236 (see
below).
IC24196 DSMCUTIL removes the node's password from the
registry when using CLUSTERNODE YES.
IC24236 Incorrect date in DSMSCHED.LOG if the
SCHEDLOGRETENTION option is used.
IX89813 When a directory showing active and inactive files
is selected for restore from the web client, only
active files are restored.
WARNING: THIS FIXTEST SOFTWARE HAS NOT BEEN FULLY SYSTEM TESTED. It is
strongly recommended that you not install this fixtest on a
production machine, at least until you have had the opportunity
to test it on a non-production machine.
COMMENTS: IC23129 was known to occur on non-U.S. English Windows systems
during installation of the ODBC driver. The ODBC driver should
not be installed on non-U.S. English systems. The InstallShield
setup has been fixed so that ODBC will not be installed unless
the target machine is running a U.S. English version of Windows.
For IC24196, the following two options must be specified with
the DSMCUTIL command when configuring the ADSM scheduler to back
up cluster disk resources:
/clusternode:yes /group:<clustername>
Note: <clustername> is the name of the NT cluster. For example,
if the cluster name is IBMCLUS, the options would look like:
/clusternode:yes /group:ibmclus
An attempt has been made to clean up and enhance the install
process. The major changes include:
- The progress indicators remain on the screen throughout the
install, rather than appear and disappear as they did in the
past. Also, they now more accurately reflect the progress of
the install. This change is cosmetic only, and does not affect
the final results of the install.
- The install now attempts to be a bit "smarter" about
determining whether a reboot is required. If a reboot is not
required, instead of being presented with a dialog that asks
whether you wish to reboot, you will be presented with a
dialog asking if you would like to view the README file, and
if you would like to start ADSM. This latter option, if
selected, will start the ADSM GUI interface. This is
recommended only if you already have a valid options file. If
you do not have a valid options file, then the GUI will start,
but will issue error messages. Creating a valid options file
will permit normal ADSM operations.
- A new option has been added to the customc.ini file, located
in the ADSMCLI\WIN32\INTEL\CONFIG directory. This option,
"ViewAfterSilentInstall", will cause your custom README file
to be displayed even if you are performing a silent install.
This is intended for users who use silent install on attended
machines to (for example) ensure consistent installs across
the enterprise. At the end of the install, the user can still
be presented with the custom README file.
At this time an Alpha version of this fixtest is not planned. If
you require an Alpha version, please let me know.
Best regards,
Andy
Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."
|
