As the first step in the decommissioning of sasCommunity.org the site has been converted to read-only mode.


Here are some tips for How to share your SAS knowledge with your professional network.


Difference between revisions of "Tip of the Day:May 24"

From sasCommunity
Jump to: navigation, search
m (Scheduled Using &SQLOBS to report on empty sets)
(Scheduled Waiting for LOCKed datasets.)
 
Line 5: Line 5:
 
sasCommunity Tip of the Day
 
sasCommunity Tip of the Day
 
</h1><div style="padding:10px;">
 
</h1><div style="padding:10px;">
{{Tips:Using &SQLOBS to report on empty sets}}
+
{{Tips:Waiting for LOCKed datasets.}}
 
<div style="width:100%"><hr></div>
 
<div style="width:100%"><hr></div>
Feel free to [[Tips Talk:Using &SQLOBS to report on empty sets|comment]] on this tip.
+
Feel free to [[Tips Talk:Waiting for LOCKed datasets.|comment]] on this tip.
 
</div>
 
</div>
 
</td></tr>
 
</td></tr>

Latest revision as of 21:32, 12 May 2011

sasCommunity Tip of the Day

A dataset may become locked explicitly using the LOCK statement or automatically if it is being modified by another SAS program. When a dataset has a lock on it, it cannot be read or modified until the lock is removed. One very easy method for waiting for the lock to be released is to use the FILELOCKWAIT libname option. For example,

libname MYLIB "/mypath" filelockwait=10;

If a dataset in MYLIB is locked and another SAS program attempts to read it, SAS will wait up to 10 seconds before giving an error.

Submitted by Sterling Paramore. Contact me at my Discussion Page.



Feel free to comment on this tip.


Prior tip - Next tip - Random Tip

Submit a Tip