<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic spaces replaced by __20 after pathworks upgrade in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261841#M60104</link>
    <description>Upgraded Pathworks from 6.0c to 7.3B and files created by word *.docs are now showing this type of changes&lt;BR /&gt;&lt;BR /&gt;before upgrade:- &lt;BR /&gt;various upgrade notes.doc&lt;BR /&gt;&lt;BR /&gt;after upgrade:-&lt;BR /&gt;various__20upgrade__20notes.doc&lt;BR /&gt;&lt;BR /&gt;can anything be done to resolve this? apart from obviously changing each file manually.&lt;BR /&gt;thanks&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 08 Nov 2010 09:31:27 GMT</pubDate>
    <dc:creator>robert70</dc:creator>
    <dc:date>2010-11-08T09:31:27Z</dc:date>
    <item>
      <title>spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261841#M60104</link>
      <description>Upgraded Pathworks from 6.0c to 7.3B and files created by word *.docs are now showing this type of changes&lt;BR /&gt;&lt;BR /&gt;before upgrade:- &lt;BR /&gt;various upgrade notes.doc&lt;BR /&gt;&lt;BR /&gt;after upgrade:-&lt;BR /&gt;various__20upgrade__20notes.doc&lt;BR /&gt;&lt;BR /&gt;can anything be done to resolve this? apart from obviously changing each file manually.&lt;BR /&gt;thanks&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Nov 2010 09:31:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261841#M60104</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-08T09:31:27Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261842#M60105</link>
      <description>also odd things happening with long named files after upgrade (also upgraded vms 7.3-2 to vms 8.3)&lt;BR /&gt;&lt;BR /&gt;doing a directory of files we have&lt;BR /&gt;&lt;BR /&gt;before upgrade:-&lt;BR /&gt;QUESTIONNAIRE_ADDITIONAL_NOTES_29-2017.DOC&lt;BR /&gt;&lt;BR /&gt;and after upgrade:-&lt;BR /&gt;QUESTIONNAIRE__20__28ADDITIONAL__20NOTE.S__29__20-__2017__2E02__2E00__2EDOC&lt;BR /&gt;&lt;BR /&gt;?</description>
      <pubDate>Mon, 08 Nov 2010 09:45:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261842#M60105</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-08T09:45:52Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261843#M60106</link>
      <description>ODS5 disk?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Nov 2010 11:36:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261843#M60106</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2010-11-08T11:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261844#M60107</link>
      <description>AHH YES JUST UPGRADED THIS TO AN ODS5-DISK&lt;BR /&gt;does this have limitations on length of names?&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Nov 2010 12:23:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261844#M60107</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-08T12:23:01Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261845#M60108</link>
      <description>no, the  opposite - ODS5 has allows a greater variety of names.&lt;BR /&gt;&lt;BR /&gt;However you may need to tell Advanced Server to act differently.&lt;BR /&gt;&lt;BR /&gt;(BTW do you have V7.3B ECO2?)&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Nov 2010 13:07:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261845#M60108</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2010-11-08T13:07:04Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261846#M60109</link>
      <description>NO ECO2 &lt;BR /&gt;just 7.3B&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Nov 2010 14:32:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261846#M60109</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-08T14:32:04Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261847#M60110</link>
      <description>Hello Robert,&lt;BR /&gt;&lt;BR /&gt;Back in the day, I used to wonder why we wrote documentation - folks never read it I thought.  And they still don't read it, apparently. ;^)  &lt;BR /&gt;&lt;BR /&gt;Seeing as you installed V7.3B, I think it appropriate to point you to the V7.3B Server Installation and Configuration Guide.   You'll find it at &lt;A href="http://h71000.www7.hp.com/doc/82final/6540/6540pro.html." target="_blank"&gt;http://h71000.www7.hp.com/doc/82final/6540/6540pro.html.&lt;/A&gt;  &lt;BR /&gt;&lt;BR /&gt;In particular, read Chapter 5.8 - "Converting Encoded File Names from ODS-2 to ODS-5".&lt;BR /&gt;&lt;BR /&gt;You see, ODS-2 does not support extended file names and things like spaces in file names.  So, PATHWORKS and Advanced Server will encode the non-ODS2 compatible characters in a file name by replacing them with __XX where XX=ascii hex value of the character.  for example, a space in a file name is encoded as "__20" (that's underscore underscore two zero).  &lt;BR /&gt;&lt;BR /&gt;Now that you converted the disk to ODS-5 and ODS-5 supports the extended file names, there is no need for the encoding and Advanced Server assumes there is no encoding.  So when it sees "__20" it no longer changes it to a " " (space), it leaves it as "__20" which is exactly what you see.   &lt;BR /&gt;&lt;BR /&gt;You need to run the PWCONVERT utility against the disk to get rid of all those encoded characters.  &lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;&lt;BR /&gt;Brad McCusker&lt;BR /&gt;Software Concepts International&lt;BR /&gt;&lt;A href="http://www.sciinc.com" target="_blank"&gt;www.sciinc.com&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Nov 2010 03:16:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261847#M60110</guid>
      <dc:creator>Brad McCusker</dc:creator>
      <dc:date>2010-11-09T03:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261848#M60111</link>
      <description>This does not make sense:&lt;BR /&gt;&amp;gt;&amp;gt;before upgrade:-&lt;BR /&gt;&amp;gt;&amp;gt;QUESTIONNAIRE_ADDITIONAL_NOTES_29-2017.DOC&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;and after upgrade:-&lt;BR /&gt;&amp;gt;&amp;gt;QUESTIONNAIRE__20__28ADDITIONAL__20NOTE.S__29__20-__2017__2E02__2E00__2EDOC&lt;BR /&gt;&lt;BR /&gt;Are you showing us what the client PC sees, or what you see from VMS?&lt;BR /&gt;&lt;BR /&gt;Did this disk get converted from ODS-2 to ODS-5?  &lt;BR /&gt;&lt;BR /&gt;"QUESTIONNAIRE_ADDITIONAL_NOTES_29-2017.DOC" is a legal ODS-2 file name.  There should have been no encoding for that file name which is why I say something doesn't make sense with regards to that name.&lt;BR /&gt;&lt;BR /&gt;Are there many other files like that one? &lt;BR /&gt;&lt;BR /&gt;Brad McCusker&lt;BR /&gt;Software Concepts International&lt;BR /&gt;&lt;A href="http://www.sciinc.com" target="_blank"&gt;www.sciinc.com&lt;/A&gt;</description>
      <pubDate>Tue, 09 Nov 2010 03:28:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261848#M60111</guid>
      <dc:creator>Brad McCusker</dc:creator>
      <dc:date>2010-11-09T03:28:22Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261849#M60112</link>
      <description>This does not make sense:&lt;BR /&gt;&amp;gt;&amp;gt;before upgrade:-&lt;BR /&gt;&amp;gt;&amp;gt;QUESTIONNAIRE_ADDITIONAL_NOTES_29-2017.DOC&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;and after upgrade:-&lt;BR /&gt;&amp;gt;&amp;gt;QUESTIONNAIRE__20__28ADDITIONAL__20NOTE.S__29__20-__2017__2E02__2E00__2EDOC&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sorry Brad this was showing &lt;BR /&gt;&lt;BR /&gt;QUESTIONNAIRE ADDITIONAL NOTES 29-2017.DOC&lt;BR /&gt;&lt;BR /&gt;before the upgrade&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;Are you showing us what the client PC sees, or what you see from VMS?&lt;BR /&gt;&lt;BR /&gt;this is showing both what the client sees and what vms sees - both the same&lt;BR /&gt;&lt;BR /&gt;It was the system disk that was upgraded from ODS2 to ODS5 - the user disk which contains the files mentioned above were already ODS5&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;Are there many other files like that one? &lt;BR /&gt;&lt;BR /&gt;There are many files yes&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Nov 2010 08:30:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261849#M60112</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-09T08:30:15Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261850#M60113</link>
      <description>$ CHAS:SYSTEM&amp;gt; pwconvert&lt;BR /&gt;_FILENAME: FAQ__20184__20-__20SAUDI__20QUARTERLY__.20REBALANCING_NOTES__2EDOC&lt;BR /&gt;%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000690&lt;BR /&gt;0000, PC=FFFFFFFF8083B424, PS=0000001B&lt;BR /&gt;%TRACE-F-TRACEBACK, symbolic stack dump follows&lt;BR /&gt;  image    module    routine             line      rel PC           abs PC&lt;BR /&gt; LIBRTL                                     0 000000000000B424 FFFFFFFF8083B424&lt;BR /&gt; DECC$SHR_EV56                              0 000000000005FD24 FFFFFFFF80AF7D24&lt;BR /&gt; DECC$SHR_EV56                              0 000000000002994C FFFFFFFF80AC194C&lt;BR /&gt; DECC$SHR_EV56                              0 0000000000133284 FFFFFFFF80BCB284&lt;BR /&gt; DECC$SHR_EV56                              0 0000000000134BA4 FFFFFFFF80BCCBA4&lt;BR /&gt; DECC$SHR_EV56                              0 000000000000E4C8 FFFFFFFF80AA64C8&lt;BR /&gt; DECC$SHR_EV56                              0 000000000000BD00 FFFFFFFF80AA3D00&lt;BR /&gt; DECC$SHR_EV56                              0 000000000010CC08 FFFFFFFF80BA4C08&lt;BR /&gt; DECC$SHR_EV56                              0 00000000001138A0 FFFFFFFF80BAB8A0&lt;BR /&gt; PWRK$CNVTOHFS  PWRK$CNVTOHFS  main     37852 000000000000094C 000000000003094C&lt;BR /&gt; PWRK$CNVTOHFS  PWRK$CNVTOHFS  __main       0 0000000000000070 0000000000030070&lt;BR /&gt;                                            0 FFFFFFFF8037FCE4 FFFFFFFF8037FCE4&lt;BR /&gt;%TRACE-I-END, end of TRACE stack dump&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Nov 2010 08:33:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261850#M60113</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-09T08:33:19Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261851#M60114</link>
      <description>i get a failure when using pwconvert on a file that has had its name changed - see above</description>
      <pubDate>Tue, 09 Nov 2010 08:34:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261851#M60114</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-09T08:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261852#M60115</link>
      <description>obviously because the disk which has corrupted file names was already ODS5 I am getting this on a pwconvert also.....&lt;BR /&gt;&lt;BR /&gt;$pwconvert *.*&lt;BR /&gt;&lt;BR /&gt; File is not ODS-2 - $1$DGA1:[PCCOMMON.FAQ]FAQ__20001__20-__20157__20__20INDEX.DO&lt;BR /&gt;C;1&lt;BR /&gt;&lt;BR /&gt;etc...........&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Nov 2010 08:36:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261852#M60115</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-09T08:36:33Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261853#M60116</link>
      <description>Robert,&lt;BR /&gt;&lt;BR /&gt;You should have run this command right after the upgrade.&lt;BR /&gt;Now several files have been touched by Advanced Server and now have an ODS5 header.&lt;BR /&gt;&lt;BR /&gt;There are 3 undocumented switches to overcome this issue.&lt;BR /&gt;If either of the following checks fail, PWCONVERT refuses to perform a conversion.&lt;BR /&gt; - Is the device ODS5 ?&lt;BR /&gt; - Is the file's fileheader NOT already an ODS5 type?&lt;BR /&gt; - Does the file have a Pathworks ACE ?&lt;BR /&gt;&lt;BR /&gt;This can be bothersome. Accessing a file (even a $type command) may already be enough to have OpenVMS automatically change the fileheader layout from ODS2 to ODS5.&lt;BR /&gt;&lt;BR /&gt;Each of the above checks can be overruled with the /DISABLE qualifier:&lt;BR /&gt;&lt;BR /&gt; $ PWCONVERT /DISABLE=(ods5, struct, ace) &lt;FILE&gt;&lt;BR /&gt; &lt;BR /&gt;where  disable=ods5: do not check if the device is ODS5&lt;BR /&gt; disable=struct: do not check if the fileheader is ODS5 &lt;BR /&gt; disable=ace: do not check if the file has a PWRK ace.&lt;BR /&gt;&lt;BR /&gt;Normally it will suffice to use /DISABLE=(struct) or /DISABLE=(struct,ace).&lt;BR /&gt;Using /DISABLE=ods5 is not recommended.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;/FILE&gt;</description>
      <pubDate>Tue, 09 Nov 2010 08:50:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261853#M60116</guid>
      <dc:creator>Hans Hosang</dc:creator>
      <dc:date>2010-11-09T08:50:52Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261854#M60117</link>
      <description>Robert,&lt;BR /&gt;&lt;BR /&gt;the crash you had in pwconvert is listed in the solved problems of V7.3B-eco1.&lt;BR /&gt;&lt;BR /&gt;So I guess you didn't upgrade to the latest ECO version but to V7.3B plain.&lt;BR /&gt;&lt;BR /&gt;Am I correct?&lt;BR /&gt;$ pwver should list V7.3-210B for the latest ECO version.&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Nov 2010 08:56:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261854#M60117</guid>
      <dc:creator>Hans Hosang</dc:creator>
      <dc:date>2010-11-09T08:56:27Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261855#M60118</link>
      <description>thanks hans&lt;BR /&gt;&lt;BR /&gt;this command worked great thanks&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; $ PWCONVERT /DISABLE=(struct, ace) &lt;FILE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/FILE&gt;</description>
      <pubDate>Tue, 09 Nov 2010 10:06:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261855#M60118</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-09T10:06:49Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261856#M60119</link>
      <description>&amp;gt;&amp;gt;$pwver should list V7.3-210B for the latest ECO version&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;we have V7.3-200B&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Nov 2010 10:08:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261856#M60119</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-09T10:08:23Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261857#M60120</link>
      <description>Your version is outdated, Robert.&lt;BR /&gt;I'd upgrade to V7.3B-eco1 asap.&lt;BR /&gt;&lt;BR /&gt;You can download it from our web:&lt;BR /&gt;&lt;A href="http://www11.itrc.hp.com/service/patch/patchDetail.do?admit=109447626+1289298124257+28353475&amp;amp;patchid=ADVANCSERV-V0703-B1" target="_blank"&gt;http://www11.itrc.hp.com/service/patch/patchDetail.do?admit=109447626+1289298124257+28353475&amp;amp;patchid=ADVANCSERV-V0703-B1&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Nov 2010 10:23:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261857#M60120</guid>
      <dc:creator>Hans Hosang</dc:creator>
      <dc:date>2010-11-09T10:23:44Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261858#M60121</link>
      <description>THANKS HANS - WILL DO</description>
      <pubDate>Tue, 09 Nov 2010 10:57:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261858#M60121</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-09T10:57:32Z</dc:date>
    </item>
    <item>
      <title>Re: spaces replaced by __20 after pathworks upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261859#M60122</link>
      <description>THANKS ALL FOR HELP</description>
      <pubDate>Tue, 09 Nov 2010 10:57:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/spaces-replaced-by-20-after-pathworks-upgrade/m-p/5261859#M60122</guid>
      <dc:creator>robert70</dc:creator>
      <dc:date>2010-11-09T10:57:58Z</dc:date>
    </item>
  </channel>
</rss>

