Hi Geoff,
The problem is that the file's path exceeds the Windows
maximum length of 259 characters. Under certain circumstances,
the OS will allow applications to create files whose paths
exceed the maximum length. Unfortunately the Win32 API file
I/O functions do not fully support these extra-long files,
and that is the crux of the problem.
The I/O functions do, however, provide a limited circumvention.
Among other things, this circumvention requires that the
application be enabled for Unicode. The TSM client is not (yet)
enabled for Unicode so we are not yet able to completely use
the circumvention.
In the 3.7.2.16 client we were able to provide limited
support for these extra-long file names by going through a
few "gyrations" within the code. The limitations on this
support are discussed in the section near the top of the
client READ1STC.TXT file, where it talks about APAR
IC27346. One of these limitations is that the support only
works when USEUNICODEFILENAMES NO is in effect. Thus Mac
files that exceed the maximum path length of 259 characters
can not be supported. The reason for this limitation is due
to how the support for Mac files is implemented; the Mac
file support and the extra-long file name support are
mutually exclusive.
We are planning on a Unicode-enabled client for a future
release, at which time we hope to be able to lift this
restriction. (Standard caveat: this is not a formal
announcement, and plans are subject to change.)
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."
I'm getting the following errors when backing up a MAC volume on an NT
Client. This is a new client install and has never been backed up in the
past. The messages have been there for 2 days running, both backups. This is
not the only entry, there are many others, but all seem to be within this
directory structure. I'm wondering if anyone else has run across this
situation. The file is there so I'm wondering if this is a filename or
length issue. The readme for the client does mention something about
"backing up the Mac volumes with USEUNICODEFILENAMES YES", but it also says
it defaults to yes when the language is ameng.
The client is NT4 with TSM client 3.7.2.16
This is in the dsmerror.log:
09/07/2000 19:09:30 ANS1228E Sending of object '\\cp-atalk-serv01\e$\Mac
Support 2\MacOS Installs\Mac OS 8.1\Mac OS 8.1\Full Install Pieces\Software
Installers\Mac OS Runtime for Java\MRJ Install Data\Apple Extras\Mac OS
Runtime For Java\Apple Applet Runner\Applets\Lightweight
RoundButtons\ExampleActionListener.class' failed
09/07/2000 19:09:30 ANS1086E File not found during Backup, Archive or
Migrate processing
This is in the server log for the same file:
09/07/00 19:10:03 ANE4005E (Session: 22676, Node: CP-ATALK-SERV01) Error
processing '\\cp-atalk-serv01\e$\Mac Support 2\MacOS Installs\Mac OS 8.1\Mac
OS 8.1\Full Install Pieces\Software Installers\Mac OS Runtime for Java\MRJ
Install Data\Apple Extras\Mac OS Runtime For Java\Apple Applet
Runner\Applets\Lightweight RoundButtons\ExampleActionListener.class': file
not found
Thanks for the help...
> Geoff Gill
> NT Systems Support Engineer
> Computer Systems Group
> E-Mail: gillg AT saic DOT com
> Phone: (858) 826-4062
> Pager: (888) 997-9614
|
