Paul, The problem was fixed in version 3.7.2 starting with 3.7.2.16. The problem was fixed in version 4 starting with version 4.1.1 and up.
Be sure to read the APA R text carefully! If you are running 4.1.3, then the problem should be fixed there, unless your file names are exceeding the TSM architectural limits OR you are using USEUNICODEFILENAMES YES. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Tomes, Paul" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 01/30/2002 09:38 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: ANS1512E Scheduled event 'OVERNIGHT' failed after ANS4018E "f ile name too long" Thanks for the info Andy. However, I cannot see which PTF fixes IC27346 and which level of the client code incorporates the fix. The Support Centre in the UK does not have this info! Thanks. Paul William Tomes IS / TSG UISL Bournemouth, England Tel: 01202-407568 ----Original Message----- From: Andrew Raibeck [mailto:[EMAIL PROTECTED]] Sent: 30 January 2002 15:31 To: [EMAIL PROTECTED] Subject: Re: ANS1512E Scheduled event 'OVERNIGHT' failed after ANS4018E "file name too long" Regarding the long file name issue, you should refer to APAR IC27346. This APAR has a fairly detailed explanation of the problem and should answer most of your questions on this subject. If you have access to looking up IBM APARs, you can go that route. Otherwise try looking in the ADSM-L archives at http://www.adsm.org. Use search criteria of: +ic27346 +raibeck +useunicodefilenames That should give you a relatively small number of hits; one of them should be a post of mine that includes the APAR text. Of course, you can do less refined searches if you want to see more postings that discuss this issue. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Tomes, Paul" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 01/30/2002 07:20 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: ANS1512E Scheduled event 'OVERNIGHT' failed after ANS4018E "file name too long" We run TSM V4.1 server under OS390 V2.9. A Windows NT4 client is doing a scheduled backup of the C, D and E drives. The C drive backup completes ok but the D drive backup fails with ANS1228E "Sending of object xxx........................ failed" and ANS4018E "Error processing xxx.......................... : file name too long". This is followed by a backup of a further directory and two files. Then message ANS4018E "Error procesing D drive : file name too long" is given. A large number of files on the D drive are not backed up and nothing on the E drive is backed up. I have an issue open with the IBM Support Centre but they say the backup should not have aborted. I have the following questions: 1. Has anyone else experienced this problem? 2. The TSM V4.1 Windows Client manual states "The maximum number of characters for a file name is 256. The maximum number of characters for a path name is 260 characters." Does anyone know what the Windows NT 4 limit is for these values? 3. It looks like in the short term we will have to get our customers to shorten their path names. However, if Windows can create file names and path names greater than the above limits, can someone in IBM / TIVOLI comment on why the TSM client limits are less than the Windows limits and is there any intention of increasing these limits? Thanks. Paul William Tomes IS / TSG UISL Bounemouth, England Tel: 01202-407568 ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. http:\\www.mimesweeper.com ********************************************************************** ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. http:\\www.mimesweeper.com **********************************************************************