To: OAS     --LMS1

FROM: Betsy Moir (TTCEDM) Ext 85020
      VM Tech Services
      email:  elizabeth.moir AT vm.ssw.abbott DOT com
Subject: ANS4243E File name too long

I think the file name would be in the dsmsched.log file if this was a
scheduled event rather than a manual one.

Betsy
*** Forwarding note from OWNERAD1--INTERNET 96/09/17 13:21 ***





TO:          INTERNET  ADSM-L AT VM.MARIST DOT EDU
FROM: OWNERAD1 INTERNET  OWNER-ADSM-L AT VM.MARIST DOT EDU
DATE: 09/17/96 13:21
SUBJECT: ANS4243E File name too long
COPYLIST:
According to the Messages manual, the above referenced message
indicates that "The file name specified is too long to be handled
by ADSM." The purported system action is that the file is
skipped, however, I have two clients that are failing their
nightly schedule following this error message (the ANS4847E
Scheduled event failed. message occurs at the same time as the
File name too long message).

According to the messages manual, I should look in to the
appropriate "Using the Backup-Archive Client" book for the file
names that are handled by ADSM. A search of the online book for
the Unix client gives no indication as to what the outer limit is
for file names.

Is there any way that I can figure out at least *what* file it is
that is too long, so that I can temporarily exclude it and
continue backing up these machines? Is the file name logged
anywhere? It is not in dsmerror.log on the client side.

Thanks for any help.

What if the Hokey-Pokey              Tom La Porte
is what it's all about?              <tlaporte AT dreamworks DOT com>