Fixtest 3.7.2.16 for the Windows client is now available
on the ftp site ftp.software.ibm.com. The directory is:
storage/tivoli-storage-management/patches/client/v3r7/Windows/v372/i386
From there, you can navigate to the "multi" or "single"
directory to obtain the fix.
One of the "highlights" of this fixtest is the ability to
support paths whose names exceed the Windows operating
system-defined maximum length of 259 characters.
Below my sig is the content of the IP21933_16_README.FTP
file that accompanies this fix:
Best regards,
Andy
Andy Raibeck
IBM/Tivoli
Tivoli Storage Manager Client Development
e-mail: andrew.raibeck AT tivoli DOT com
"The only dumb question is the one that goes unasked."
=============================================================================
Tivoli Storage Manager (TSM) for Windows README.FTP
Version 3 Release 7, Level 2.16 PTF IP21933 (x86)
Fixtest 16
+++++++++++++ One of the APARs fixed in this fixtest is IC27346, which
| IMPORTANT | addresses support for files whose names exceed 259 characters.
+++++++++++++ The official fix for IC27346 will be available in a maintenance
PTF to be issued on or around September 2000. If you install this fixtest,
please do not apply any subsequent package that is issued before the
September 2000 maintenance, as it will not contain this fix.
******************************************************************************
* Fixtest 16, IC26327 Expiration of files whose names include uppercase *
* DBCS characters (between 0x8260 and 0x8279) fails *
* with messages ANS1228E, ANS1304W, and ANS1802E. *
* *
* IC26855 Registry backup on Windows 95/98 fails with message *
* ANS4036E. *
* *
* IC26949 ANS1155E is reported for clusters whose names are *
* of the maximum length (15 characters), even though *
* the client is otherwise correctly configured for *
* cluster support. *
* *
* IC26980 "ANS1076E *** Directory path not found ***" issued *
* at the beginning of incremental backup when the *
* domain is set to ALL-LOCAL (either explicitly or by *
* default). *
* *
* IC27058 Registry backup requires an administrative account. *
* *
* NOTE: This fix allows an account belonging to the *
* "Backup Operators" group (with no additional *
* privileges) to successfully back up and restore the *
* registry. In order to back up normal files and *
* directories with a Backup Operators account, the *
* "Manage auditing and security log" privilige must *
* also be granted, either to the Backup Operators *
* group as a whole, or to the individual account used *
* to back up the system. This privilege is necessary *
* in order for TSM to back up file security *
* information. If you do not wish to grant this *
* privilege, and you do not wish to use an *
* administrative account to perform the backup, then *
* you can specify "SKIPNTPERMISSIONS YES" in the *
* client options file (dsm.opt). However, if you use *
* this option, TSM will not back up or restore NTFS *
* security information for your files. Refer to the *
* "Using the Backup-Archive Client" manual for more *
* information on using the SKIPNTPERMISSIONS option. *
* *
* IC27346 Windows client can not back up files whose names *
* exceed the Windows operating system limit of 259 *
* characters. *
* *
* NOTES ON THIS APAR FIX: The Windows client running *
* on Windows NT and 2000 can now handle longer file *
* names. Please be aware of the following: *
* *
* - USEUNICODEFILENAMES NO must be in effect. If *
* USEUNICODEFILENAMES YES is in effect, then these *
* longer file names are unsupported. Note that you *
* should always use USEUNICODEFILENAMES NO unless *
* you have Mac volumes. If you need to support both *
* Mac volumes *and* these longer file names, then *
* you will need to make provisions to run backups *
* for the Mac volumes separately from the non-Mac *
* files, backing up the Mac volumes with *
* USEUNICODEFILENAMES YES, and the non-Mac files *
* with USEUNICODEFILENAMES NO. *
* *
* If you do not explicitly code the *
* USEUNICODEFILENAMES option, then you should be *
* aware of how the default for this option works: *
* The default setting for USEUNICODEFILENAMES *
* depends on the LANGUAGE setting that the client *
* uses. If LANGUAGE AMENG is in effect, then *
* USEUNICODEFILENAMES defaults to YES. If the *
* LANGUAGE setting is something else, then *
* USEUNICODEFILENAMES defaults to NO. *
* *
* - The maximum length of the file name itself (not *
* including the directory in which it resides), is *
* 255 characters. *
* *
* - The maximum length of the directory path in which *
* the file resides (not including the file itself) *
* can not exceed 1,024 characters. *
* *
* - The maximum length of any component within a *
* directory path can not exceed 255 characters. *
* "Component" refers to a part of a directory *
* structure as delimited by the backslash ( \ ) *
* character. *
* *
* To illustrate: Given a path of the form: *
* *
* x:\comp1\comp2\comp3\filename *
* *
* Each component "compx" can not exceed 255 *
* 255 characters in length. Likewise, "filename" can *
* not exceed 255 characters in length. In addtion, *
* the "x:\comp1\comp2\comp3" can not exceed 1,024 *
* characters in length. Files that exceed any of *
* these limits are not supported. *
* *
* WARNING: THIS FIXTEST SOFTWARE HAS NOT BEEN FULLY SYSTEM TESTED. It is *
* strongly recommended that you not install this fixtest on a *
* production machine until you have had the opportunity to test it *
* on a non-production machine. *
******************************************************************************
Licensed Materials - Property of IBM
(C) Copyright IBM Corporation 1990, 2000. All rights reserved.
=============================================================================
This fixtest is available in a single file package and a multi file package.
You may download whichever package is more convenient. Please note that there
is no functional difference between the two packages. Upon extraction (via the
*.BAT file), either package will produce EXACTLY the same install image.
------------
Installation
Installation
------------
1) Download the following files in BINARY format:
1) Download the following files in BINARY format:
For the single file package:
IP21933_16.BAT
IP21933_16_FULL.EXE
For the multi file package:
IP21933_16.BAT
IP21933_16_FILE1.EXE
IP21933_16_FILE2.EXE
IP21933_16_FILE3.EXE
IP21933_16_FILE4.EXE
2) Create the install image by running the IP21933_16.BAT file:
IP21933_16 target
where "target" is the directory where you would like the installation
image to reside. Examples:
Extract the files to the C:\NEWTSM directory:
IP21933_16 C:\NEWTSM
Extract the files to the current directory
IP21933_16 .
NOTE: Running IP21933_16.BAT with no parameters will provide usage
information.
3) Change into the directory where you extracted the installation image.
Example (assuming the image was extracted to C:\NEWTSM):
C:
CD \NEWTSM
4) Start the SETUP program by executing the following commands:
CD TSMCLI\WIN32\INTEL\DISK1
SETUP
5) Follow the SETUP program prompts to complete the install.
|
