<?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: rename data set that is read-locked in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68571#M14857</link>
    <description>Processes in question are in ETL environment. In most cases they read tables only once.&lt;BR /&gt;
So when they read and processes that builds table can't update table - this is the issue.&lt;BR /&gt;
While doing UNIX-tied deletes and removes we can update tables well.&lt;BR /&gt;
&lt;BR /&gt;
It's strange why not to have some options for this case.</description>
    <pubDate>Wed, 02 Sep 2009 08:13:43 GMT</pubDate>
    <dc:creator>Opa4ki</dc:creator>
    <dc:date>2009-09-02T08:13:43Z</dc:date>
    <item>
      <title>rename data set that is read-locked</title>
      <link>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68568#M14854</link>
      <description>Hi&lt;BR /&gt;
&lt;BR /&gt;
My issue is that when some process is reading data set i cannot rename it with sas utilities. E.g. "Change statement in datasets procedure". Sas says that "data set XX is in use by user YY" or something like that.&lt;BR /&gt;
&lt;BR /&gt;
We now overcome this by issuing OS-commands. OS is Solaris. When we want to rename XX, we have macro that do "rm or mv XX". &lt;BR /&gt;
&lt;BR /&gt;
I wonder, whether SAS actually has some way to do this without me going to issue OS-commands?</description>
      <pubDate>Tue, 01 Sep 2009 08:34:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68568#M14854</guid>
      <dc:creator>Opa4ki</dc:creator>
      <dc:date>2009-09-01T08:34:59Z</dc:date>
    </item>
    <item>
      <title>Re: rename data set that is read-locked</title>
      <link>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68569#M14855</link>
      <description>And when i try to use 'rename' or 'delete' function like that&lt;BR /&gt;
data _null_;&lt;BR /&gt;
 sysrc=delete('TABLENAME');&lt;BR /&gt;
run;&lt;BR /&gt;
SAS says &lt;BR /&gt;
&lt;I&gt;The function DELETE is unknown, or cannot be accessed.&lt;/I&gt;</description>
      <pubDate>Tue, 01 Sep 2009 09:40:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68569#M14855</guid>
      <dc:creator>Opa4ki</dc:creator>
      <dc:date>2009-09-01T09:40:51Z</dc:date>
    </item>
    <item>
      <title>Re: rename data set that is read-locked</title>
      <link>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68570#M14856</link>
      <description>SAS is designed to "play well with others". It's behavior is consistent in not allowing you to rename a dataset while someone else is using it.   &lt;BR /&gt;
&lt;BR /&gt;
Unix was written with the philosophy that the user know what they are doing and will take the consequences of his behavior.  If you rename a dataset with with the OS and the other user does another read, their process fails. &lt;BR /&gt;
&lt;BR /&gt;
I think that you are stuck with using the OS to do the rename.  BTW, other OSs will not allow you to do a rename while another process has a file open.</description>
      <pubDate>Tue, 01 Sep 2009 13:09:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68570#M14856</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2009-09-01T13:09:23Z</dc:date>
    </item>
    <item>
      <title>Re: rename data set that is read-locked</title>
      <link>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68571#M14857</link>
      <description>Processes in question are in ETL environment. In most cases they read tables only once.&lt;BR /&gt;
So when they read and processes that builds table can't update table - this is the issue.&lt;BR /&gt;
While doing UNIX-tied deletes and removes we can update tables well.&lt;BR /&gt;
&lt;BR /&gt;
It's strange why not to have some options for this case.</description>
      <pubDate>Wed, 02 Sep 2009 08:13:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68571#M14857</guid>
      <dc:creator>Opa4ki</dc:creator>
      <dc:date>2009-09-02T08:13:43Z</dc:date>
    </item>
    <item>
      <title>Re: rename data set that is read-locked</title>
      <link>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68572#M14858</link>
      <description>You may want to explore the behavior differences with the FILELOCKS system / CONFIG option.  The SAS UNIX Companion Guide should have reference information.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
      <pubDate>Wed, 02 Sep 2009 12:18:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68572#M14858</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2009-09-02T12:18:41Z</dc:date>
    </item>
    <item>
      <title>Re: rename data set that is read-locked</title>
      <link>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68573#M14859</link>
      <description>&amp;gt;So when they read and processes that builds table can't update table - this is the issue.&lt;BR /&gt;
&lt;BR /&gt;
A product called SAS/Share exists to manage multi-user table access, so you can read and write (as in update, not delete or rename, see below) tables at the same time&lt;BR /&gt;
&lt;BR /&gt;
&amp;gt;In most cases they read tables only once. While doing UNIX-tied deletes and removes we can update tables well.&lt;BR /&gt;
&lt;BR /&gt;
If the table is still locked, it is still being being read, unless the process does bizarre things. Your deleting/renaming will likely cause errors and abort the reading process. If it doesn't, maybe the reading process can release it earlier?  Does it use sasfile statements or similar?</description>
      <pubDate>Wed, 02 Sep 2009 21:29:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/rename-data-set-that-is-read-locked/m-p/68573#M14859</guid>
      <dc:creator>ChrisNZ</dc:creator>
      <dc:date>2009-09-02T21:29:57Z</dc:date>
    </item>
  </channel>
</rss>

