Morning Ed,

I'm not sure how useful this would be if you're wanting to hunt for bad file 
names, but in the past we've used the built in HEX function to convert problem 
strings to hex and have an external script convert it back into ASCII/Unicode 
(whatever it should be).
That way all the intelligence goes into an external script and there's no 
digging around in ILM to find a solution. I don't have an example to hand, but 
if you're interested in the approach I can probably get one for you.

Regards,

Pete Chase
Met Office SVM team

-----Original Message-----
From: gpfsug-discuss-boun...@spectrumscale.org 
<gpfsug-discuss-boun...@spectrumscale.org> On Behalf Of 
gpfsug-discuss-requ...@spectrumscale.org
Sent: 05 October 2021 07:11
To: gpfsug-discuss@spectrumscale.org
Subject: gpfsug-discuss Digest, Vol 117, Issue 1

This email was received from an external source.   Always check sender details, 
links & attachments.

Send gpfsug-discuss mailing list submissions to
        gpfsug-discuss@spectrumscale.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://gpfsug.org/mailman/listinfo/gpfsug-discuss
or, via email, send a message with subject or body 'help' to
        gpfsug-discuss-requ...@spectrumscale.org

You can reach the person managing the list at
        gpfsug-discuss-ow...@spectrumscale.org

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of gpfsug-discuss digest..."


Today's Topics:

   1. Handling bad file names in policies? (Wahl, Edward)
   2. Re: Handling bad file names in policies? (Jonathan Buzzard)
   3. Re: Handling bad file names in policies? (Olaf Weiser)


----------------------------------------------------------------------

Message: 1
Date: Mon, 4 Oct 2021 22:23:59 +0000
From: "Wahl, Edward" <ew...@osc.edu>
To: "gpfsug-discuss@spectrumscale.org"
        <gpfsug-discuss@spectrumscale.org>
Subject: [gpfsug-discuss] Handling bad file names in policies?
Message-ID:
        
<ch0pr01mb68256062068702aa353aa758a8...@ch0pr01mb6825.prod.exchangelabs.com>
        
Content-Type: text/plain; charset="utf-8"

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.

Ed Wahl
OSC

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20211004/37e22476/attachment-0001.html>

------------------------------

Message: 2
Date: Tue, 5 Oct 2021 00:28:57 +0100
From: Jonathan Buzzard <jonathan.buzz...@strath.ac.uk>
To: gpfsug-discuss@spectrumscale.org
Subject: Re: [gpfsug-discuss] Handling bad file names in policies?
Message-ID: <ad1cdd69-a6f6-353a-b544-fada54f01...@strath.ac.uk>
Content-Type: text/plain; charset=utf-8; format=flowed

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


------------------------------

Message: 3
Date: Tue, 5 Oct 2021 06:10:26 +0000
From: "Olaf Weiser" <olaf.wei...@de.ibm.com>
To: gpfsug-discuss@spectrumscale.org
Cc: gpfsug-discuss@spectrumscale.org
Subject: Re: [gpfsug-discuss] Handling bad file names in policies?
Message-ID:
        <offb8f8011.06f188d6-on00258765.00213af9-00258765.0021e...@ibm.com>
Content-Type: text/plain; charset="us-ascii"

An HTML attachment was scrubbed...
URL: 
<http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20211005/29d6c6ff/attachment.html>

------------------------------

_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss


End of gpfsug-discuss Digest, Vol 117, Issue 1
**********************************************

_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Reply via email to