<?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: ERROR: A lock is not available for in New SAS User</title>
    <link>https://communities.sas.com/t5/New-SAS-User/ERROR-A-lock-is-not-available-for/m-p/501703#M566</link>
    <description>&lt;P&gt;Sorry, I don't have answers for that on Windows.&lt;/P&gt;</description>
    <pubDate>Thu, 04 Oct 2018 23:19:31 GMT</pubDate>
    <dc:creator>Astounding</dc:creator>
    <dc:date>2018-10-04T23:19:31Z</dc:date>
    <item>
      <title>ERROR: A lock is not available for</title>
      <link>https://communities.sas.com/t5/New-SAS-User/ERROR-A-lock-is-not-available-for/m-p/501689#M562</link>
      <description>&lt;P&gt;I'm getting the error "ERROR: A lock is not available for". I closed the session and re-started , yet this error comes. I'm using windows environment and submitting batch jobs.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Oct 2018 21:01:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/ERROR-A-lock-is-not-available-for/m-p/501689#M562</guid>
      <dc:creator>SASPhile</dc:creator>
      <dc:date>2018-10-04T21:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: ERROR: A lock is not available for</title>
      <link>https://communities.sas.com/t5/New-SAS-User/ERROR-A-lock-is-not-available-for/m-p/501695#M564</link>
      <description>&lt;P&gt;The typical scenario:&amp;nbsp; it takes patience.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One batch job is using the data set, while another batch job wants to use the data set.&amp;nbsp; If one of the batch jobs wants to change the data set (for example, running PROC SORT on a permanent SAS data set), it is not possible for both batch jobs to access the data set at the same time.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Your programming style can have some impact here.&amp;nbsp; For example, if you add OUT= to your PROC SORT, then that step doesn't need to tie up the data set.&amp;nbsp; But in a large number of cases, patience is a virtue.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Oct 2018 21:25:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/ERROR-A-lock-is-not-available-for/m-p/501695#M564</guid>
      <dc:creator>Astounding</dc:creator>
      <dc:date>2018-10-04T21:25:13Z</dc:date>
    </item>
    <item>
      <title>Re: ERROR: A lock is not available for</title>
      <link>https://communities.sas.com/t5/New-SAS-User/ERROR-A-lock-is-not-available-for/m-p/501698#M565</link>
      <description>&lt;P&gt;1. How to know what processes are running?&lt;/P&gt;&lt;P&gt;2. How to kill the processes on windows?&lt;/P&gt;</description>
      <pubDate>Thu, 04 Oct 2018 22:06:49 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/ERROR-A-lock-is-not-available-for/m-p/501698#M565</guid>
      <dc:creator>SASPhile</dc:creator>
      <dc:date>2018-10-04T22:06:49Z</dc:date>
    </item>
    <item>
      <title>Re: ERROR: A lock is not available for</title>
      <link>https://communities.sas.com/t5/New-SAS-User/ERROR-A-lock-is-not-available-for/m-p/501703#M566</link>
      <description>&lt;P&gt;Sorry, I don't have answers for that on Windows.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Oct 2018 23:19:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/ERROR-A-lock-is-not-available-for/m-p/501703#M566</guid>
      <dc:creator>Astounding</dc:creator>
      <dc:date>2018-10-04T23:19:31Z</dc:date>
    </item>
    <item>
      <title>Re: ERROR: A lock is not available for</title>
      <link>https://communities.sas.com/t5/New-SAS-User/ERROR-A-lock-is-not-available-for/m-p/501751#M570</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/16600"&gt;@SASPhile&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;1. How to know what processes are running?&lt;/P&gt;
&lt;P&gt;2. How to kill the processes on windows?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;If you want to make your life easier, can the toybox and switch to a real operating system. At the moment, this means UNIX.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I work on a UNIX platform, and on such this is a non-issue, as I can easily remove links to files (aka "directory entries") from the filesystem while a process is still using the file. That is because UNIX systems have a different concept of filesystem structure that is lightyears ahead of the much-too-simple method that Windows has.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Oct 2018 06:05:18 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/ERROR-A-lock-is-not-available-for/m-p/501751#M570</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-10-05T06:05:18Z</dc:date>
    </item>
  </channel>
</rss>

