<?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 Re: SAS File Lock and I/O errors in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292692#M59949</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/90915"&gt;@Reaensh&lt;/a&gt; wrote:&lt;BR /&gt;
&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I got this error:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ERROR: An I/O error has occurred on file RPW.SWITCHER.DATA.&lt;BR /&gt;ERROR: File RPW.SWITCHER.DATA is damaged. I/O processing did not complete.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I look in the folder there is a file of this type now:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;.nfs002d00000006822000001da2&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would this suggest a hardware issue as opposed to program?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;That "nfs" lets me suspect that you are working on an NFS mount here. You might have run into a short network outage that caused the error.&lt;/P&gt;
&lt;P&gt;My solution: stop working via network mounts and use locally mounted disks.&lt;/P&gt;</description>
    <pubDate>Fri, 19 Aug 2016 09:54:40 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2016-08-19T09:54:40Z</dc:date>
    <item>
      <title>SAS File Lock and I/O errors</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292679#M59943</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I keep getting SAS I/O Errors or a Filelock issue on a datastep I am trying to run at times on a Unix environment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have seen the FILELOCKWAIT is set to 0, so how do I change this to 20 seconds in the config file, as I have tried and it does not work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also does anyone know how to get rid os I/O errors and locking of files as it happens intermittently, or can I access a specific log to check what the issues are?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Reanesh&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2016 09:05:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292679#M59943</guid>
      <dc:creator>Reaensh</dc:creator>
      <dc:date>2016-08-19T09:05:12Z</dc:date>
    </item>
    <item>
      <title>Re: SAS File Lock and I/O errors</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292682#M59944</link>
      <description>&lt;P&gt;AS for your question on file locks, this is discussed in many posts on here. &amp;nbsp;There are ways to force it, its an os lock not sas, but its not recommended. &amp;nbsp;Its more of a process issue, why is it that you and someone else are trying to access the same file? &amp;nbsp;Is there a better way of doing it, the answer to that is yes. &amp;nbsp;There are various methods - have user areas where files are checked out to and you work on those rather than all on the same files. &amp;nbsp;Or use a database - that allows concurrent access. &amp;nbsp;Or choose some warehouse software that can control accesses, assign queues etc. &amp;nbsp;Many options.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2016 09:10:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292682#M59944</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2016-08-19T09:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: SAS File Lock and I/O errors</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292684#M59945</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No one else is accessing this file and I am the user running a few data steps and proc means and this issue appears.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I deleted the lock file yet it still appears when I try to re-process the sas program.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please advise on a better method please.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2016 09:14:14 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292684#M59945</guid>
      <dc:creator>Reaensh</dc:creator>
      <dc:date>2016-08-19T09:14:14Z</dc:date>
    </item>
    <item>
      <title>Re: SAS File Lock and I/O errors</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292685#M59946</link>
      <description>&lt;P&gt;This could be due to some fault logic in your program, or some constraint/issue at the OS level. Work closely with your system&amp;nbsp;administrator and try to capture the lock event at the OS level.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2016 09:24:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292685#M59946</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2016-08-19T09:24:54Z</dc:date>
    </item>
    <item>
      <title>Re: SAS File Lock and I/O errors</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292689#M59947</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I got this error:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ERROR: An I/O error has occurred on file RPW.SWITCHER.DATA.&lt;BR /&gt;ERROR: File RPW.SWITCHER.DATA is damaged. I/O processing did not complete.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I look in the folder there is a file of this type now:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;.nfs002d00000006822000001da2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would this suggest a hardware issue as opposed to program?&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2016 09:48:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292689#M59947</guid>
      <dc:creator>Reaensh</dc:creator>
      <dc:date>2016-08-19T09:48:44Z</dc:date>
    </item>
    <item>
      <title>Re: SAS File Lock and I/O errors</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292690#M59948</link>
      <description>&lt;P&gt;A lock problem usually causes this message to be written to the log:&lt;/P&gt;
&lt;PRE&gt;ERROR: A lock is not available for LIBARY.DATASET.DATA.
ERROR: Lock held by process nnnnnnn.&lt;/PRE&gt;
&lt;P&gt;So you need to look in the UNIX ps list for the offending process and determine why it had the dataset open.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2016 09:52:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292690#M59948</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2016-08-19T09:52:24Z</dc:date>
    </item>
    <item>
      <title>Re: SAS File Lock and I/O errors</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292692#M59949</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/90915"&gt;@Reaensh&lt;/a&gt; wrote:&lt;BR /&gt;
&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I got this error:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ERROR: An I/O error has occurred on file RPW.SWITCHER.DATA.&lt;BR /&gt;ERROR: File RPW.SWITCHER.DATA is damaged. I/O processing did not complete.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I look in the folder there is a file of this type now:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;.nfs002d00000006822000001da2&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would this suggest a hardware issue as opposed to program?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;That "nfs" lets me suspect that you are working on an NFS mount here. You might have run into a short network outage that caused the error.&lt;/P&gt;
&lt;P&gt;My solution: stop working via network mounts and use locally mounted disks.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2016 09:54:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292692#M59949</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2016-08-19T09:54:40Z</dc:date>
    </item>
    <item>
      <title>Re: SAS File Lock and I/O errors</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292835#M59953</link>
      <description>&lt;P&gt;Reaensh,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Bummer!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Though you have received some&amp;nbsp;good advice and suggestions, I don't think anybody directly answered your question about setting the FILELOCKWAIT option.&amp;nbsp; Here is an example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;libname timing "r:\path"&lt;STRONG&gt; filelockwait=10;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;HTH!&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2016 19:57:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SAS-File-Lock-and-I-O-errors/m-p/292835#M59953</guid>
      <dc:creator>MMMIIIIKKKKEEEE</dc:creator>
      <dc:date>2016-08-19T19:57:34Z</dc:date>
    </item>
  </channel>
</rss>

