<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>
<!--
@font-face
        {font-family:Wingdings}
@font-face
        {font-family:Wingdings}
@font-face
        {font-family:Calibri}
@font-face
        {font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif"}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline}
tt
        {font-family:"Courier New"}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif"}
span.EmailStyle18
        {font-family:"Calibri","sans-serif";
        color:#1F497D}
span.BalloonTextChar
        {font-family:"Tahoma","sans-serif"}
.MsoChpDefault
        {font-size:10.0pt}
@page WordSection1
        {margin:1.0in 1.0in 1.0in 1.0in}
ol
        {margin-bottom:0in}
ul
        {margin-bottom:0in}
-->
</style><style type="text/css" id="owaParaStyle"></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hm. I can only log a public RFE against Scale ... and this is a change to Protect ;-)
<div><br>
</div>
<div>Simon<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF227223" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> gpfsug-discuss-bounces@spectrumscale.org [gpfsug-discuss-bounces@spectrumscale.org] on behalf of Bryan Banister [bbanister@jumptrading.com]<br>
<b>Sent:</b> 20 April 2016 16:19<br>
<b>To:</b> gpfsug main discussion list<br>
<b>Subject:</b> Re: [gpfsug-discuss] mmbackup and filenames<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">The Public RFE process sounds like a good way to go…  somebody put it up and I’ll vote for it!</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">-B</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> gpfsug-discuss-bounces@spectrumscale.org [mailto:gpfsug-discuss-bounces@spectrumscale.org]
<b>On Behalf Of </b>Simon Thompson (Research Computing - IT Services)<br>
<b>Sent:</b> Wednesday, April 20, 2016 10:15 AM<br>
<b>To:</b> gpfsug main discussion list<br>
<b>Subject:</b> Re: [gpfsug-discuss] mmbackup and filenames</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">Hi Mark,
</span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">I appreciate its a limitation of the TSM client, but Scale (IBM product) and Protect (IBM product) and preferred (?) method of backing it up ...</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">I agree with Kevin that given the push for protocol support, and people will use filenames like this, IBM need to get it fixed.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">Who should we approach at IBM as a user community to get this on the TSM fix list?</span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">Simon</span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
<div id="divRpF298955">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">
<a href="redir.aspx?REF=KjH3Mg15Jw1STzb6r39qjetl0-9hx11--QtQmh11I9yO8x8uMGnTCAFtYWlsdG86Z3Bmc3VnLWRpc2N1c3MtYm91bmNlc0BzcGVjdHJ1bXNjYWxlLm9yZw.." target="_blank">
gpfsug-discuss-bounces@spectrumscale.org</a> [gpfsug-discuss-bounces@spectrumscale.org] on behalf of Marc A Kaplan [makaplan@us.ibm.com]<br>
<b>Sent:</b> 20 April 2016 15:42<br>
<b>To:</b> gpfsug main discussion list<br>
<b>Subject:</b> Re: [gpfsug-discuss] mmbackup and filenames</span><span style="color:black"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:black">The problem is that the Tivoli Storage Manager (Ahem Spectrum Protect) Filelist option has some limitations:</span><span style="color:black"><br>
<br>
<a href="UrlBlockedError.aspx" target="_blank"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"">http://www.ibm.com/support/knowledgecenter/SS8TDQ_7.1.0/com.ibm.itsm.client.doc/r_opt_filelist.html</span></a><br>
<br>
</span><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:black">...</span><span style="color:black"><br>
</span><span style="font-size:7.5pt; font-family:"Arial","sans-serif"; color:black">The files (entries) listed in the filelist must adhere to the following rules:</span><span style="color:black">
</span></p>
<ul type="disc">
<li class="MsoNormal" style="color:black"><span style="font-size:7.5pt; font-family:"Arial","sans-serif"">Each entry must be a fully-qualified or a relative path to a file or directory. Note that if you include a directory in a filelist entry, the directory
 is backed up, but the contents of the directory are not.</span></li><li class="MsoNormal" style="color:black"><span style="font-size:7.5pt; font-family:"Arial","sans-serif"">Each path must be specified on a single line. A line can contain only one path.</span></li><li class="MsoNormal" style="color:black"><span style="font-size:7.5pt; font-family:"Arial","sans-serif"">Paths must not contain control characters, such as 0x18 (CTRL-X), 0x19 (CTRL-Y) and 0x0A (newline).</span></li><li class="MsoNormal" style="color:black; margin-bottom:12.0pt"><span style="font-size:7.5pt; font-family:"Arial","sans-serif"">By default, paths must not contain wildcard characters. Do not include asterisk (*) or question marks (?) in a path. This restriction
 can be overridden if you enable the option named </span><tt><span style="font-size:7.5pt">... AND SO ON...</span></tt></li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Arial","sans-serif"; color:black">IF TSM would implement some way of encoding or "escaping" special characters in filelists, we would happily fix mmbackup !</span><span style="color:black"></span></p>
</div>
</div>
</div>
</div>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
Note: This email is for the confidential use of the named addressee(s) only and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you are hereby notified that any review, dissemination or copying of this
 email is strictly prohibited, and to please notify the sender immediately and destroy this email and any attachments. Email transmission cannot be guaranteed to be secure or error-free. The Company, therefore, does not make any guarantees as to the completeness
 or accuracy of this email or any attachments. This email is for informational purposes only and does not constitute a recommendation, offer, request or solicitation of any kind to buy, sell, subscribe, redeem or perform any type of transaction of a financial
 product.<br>
</font></div>
</div>
</div>
</div>
</body>
</html>