Thanks Len,

I need to check whether NSS file system IS UNICODE. I know that people
store in the this specific file system files in all sorts of languages
(russian, arabic and probably others) with hebrew being second to
english. So I guess it is UNICODE. However the q f reports that it
isn't:

tsm> q f -detail
  #     Last Incr Date      Type    fsID  Unicode  File Space Name
---     --------------      ----    ----  -------  ---------------
  1   06/01/09   23:29:24   NSS        6  No       /media/nss/D31

The way I see it is that if a file system type supported by TSM v5.5
(NSS in this case) is capable of storing file name that long, TSM
should be able to pick it up?  I'll check tomorrow the true length of
the  file name.

Another thing that deeply concerns me is that despite the fact that
the error was logged, "failed files" count came out equal to zero.
Thus giving me no indication that something has just gone wrong:

06/01/09   22:07:25 --- SCHEDULEREC STATUS BEGIN
06/01/09   22:07:25 Total number of objects inspected:  394,423
06/01/09   22:07:25 Total number of objects backed up:      174
06/01/09   22:07:25 Total number of objects updated:          0
06/01/09   22:07:25 Total number of objects rebound:          0
06/01/09   22:07:25 Total number of objects deleted:          0
06/01/09   22:07:25 Total number of objects expired:          3
06/01/09   22:07:25 Total number of objects failed:           0
06/01/09   22:07:25 Total number of bytes transferred:   226.26 MB
06/01/09   22:07:25 Data transfer time:                   13.59 sec
06/01/09   22:07:25 Network data transfer rate:        17,041.36 KB/sec
06/01/09   22:07:25 Aggregate data transfer rate:      2,990.95 KB/sec
06/01/09   22:07:25 Objects compressed by:                    0%
06/01/09   22:07:25 Elapsed processing time:           00:01:17
06/01/09   22:07:25 --- SCHEDULEREC STATUS END
06/01/09   22:07:25 --- SCHEDULEREC OBJECT END 22_SCHED_3 06/01/09   22:00:00
06/01/09   22:07:25 Scheduled event '22_SCHED_3' completed successfully.
06/01/09   22:07:25 Sending results for scheduled event '22_SCHED_3'.
06/01/09   22:07:25 Results sent to server for scheduled event '22_SCHED_3'.

I spotted the error only because I have habit of manually going
through the "day one" logs of all new clients.
--
Warm regards,
Michael Green