On 04/10/2021 23:23, Wahl, Edward wrote:
I know I've run into this before way back, but my notes on how I solved
this aren't getting the job done in Scale 5.0.5.8 and my notes are from
3.5.Â đŸ˜‰
Anyone know a way to get a LIST policy to properly feed bad filenames
into the output or an external script?
When I say bad I mean things like control characters, spaces, etc.  Not
concerned about the dreaded 'newline' as we force users to fix those or
the files do not get backed up in Tivoli.
Since when? Last time I checked which was admittedly circa 2008, TSM
would backup files with newlines in them no problem. mmbackup on the
other hand in that time frame would simply die and backup nothing if
there was a single file on the file system with a newline in it.
I would take a look at the mmbackup scripts which can handle such stuff
(least ways in >4.2) which would also suggest dsmc can handle it.
As an aside I now think I know how you end up with newlines in file
names. Basically you cut and paste the file name complete with newlines
(most likely at the end) into a text field when saving the file.
Personally I think any program should baulk at that point but what do I
know.
JAB.
--
Jonathan A. Buzzard Tel: +44141-5483420
HPC System Administrator, ARCHIE-WeSt.
University of Strathclyde, John Anderson Building, Glasgow. G4 0NG
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
