ADSM-L

Re: NT long file names

1999-05-19 10:09:32
Subject: Re: NT long file names
From: Andy Raibeck <storman AT US.IBM DOT COM>
Date: Wed, 19 May 1999 07:09:32 -0700
Hi Jack,

Is the problem recreatable? When you say the client aborts, what specifically
do you mean? Are there any other error messages in the dsmerror.log file?
If the client actually crashes, do you get a Dr. Watson log generated? The
ANS4005E should not cause the client to abort, at least if you are at
3.1.0.6. Also, it seems strange that the client abort occurred 10 minutes
after the ANS4005E. This also suggests that the ANS4005E is not related to
the abort problem, at least not directly. When encountering a file name that
is too long, the client should skip it and go on.

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."

I have a current problem (87425) open with IBM where NT 3.51 ADSM 3.1 0.6
client was doing a selective backup to an AIX 4.3 ADSM 3.1.2.20 server and
after 15+ hrs and 39GB of data encountered a fully qualified dataset name of
length 270 and dropped an informative message (ANx4005E) on both client and
server log. Ten minutes later the client aborts.  IBM's response is that
it's not an ADSM problem as Microsoft doesn't support file names greater
than 256 and points me to a microsoft doc (search on the MS site for 'Path
Too Long Error Message When Exceeding MAX_PATH ').  This doc does support
IBM's position re lfn, but also notes that NTBackup has no problem with such
files.
Last June in this forum, Andy Riebeck indicated similar concerns with NT
file names and pointed out certain limits (_MAX_DIR = 256, _MAX_EXT= 256,
_MAX_FNAME = 256, _MAX_PATH =260).
I can understand ADSM not processing 'errant' files, but I can't accept ADSM
abending or aborting backups when such a filename is encountered.  And in
general, IBM seems to agree with this position (note fixes IC20506,
IC18235).
Some questions:  Is anyone aware of attempts to remove the restriction of
the fully qualified dataset name being no greater in length than 256 or 260?
If no, is there any way to prevent users from creating such datasets?

***********************************************************
This email transmission and any files that accompany it may
contain sensitive information belonging to the sender. The
information is intended only for the use of the individual
or entity named. If you are not the intended recipient, you
are hereby notified that any disclosure, copying,
distribution, or the taking of any action in reliance on the
contents of this information is strictly prohibited. If you
have received this email transmission in error, please
immediately notify the Security Administrator.
Security.Administrator AT dowcorning DOT com
***********************************************************
<Prev in Thread] Current Thread [Next in Thread>