Hi I you have SAS/Share installed then this could be a way to go (also even with SAS/Share it's sometimes a bit tricky) - look at statements like "modify", avoid "proc sql" as it doesn't always behave like one would expect. Without SAS/Share row-level-locking is not possible for normal SAS datasets. What you can do is having process B waiting for the table until process A is done with it. Have a look at: http://www.lexjansen.com/pharmasug/2005/posters/po33.pdf HTH Patrick ... View more

Looking at your data I think Geniz solution comes only close to what you asked for. May be this might help (not tested): proc format; value bool >0 =1 ; run; data lag; set input; time_1 = input(put(lag1(cash_balance),bool.),8.); time_1 = input(put(lag2(cash_balance),bool.),8.); time_1 = input(put(lag3(cash_balance),bool.),8.); run; ... View more

Have a look at this SAS note: http://support.sas.com/kb/16/223.html Have also a look at the "SAS National Language Support:Users Guide" in the SAS OnlineDoc (http://support.sas.com/onlinedoc/913/docMainpage.jsp), i.e. this link might be helpful: http://support.sas.com/onlinedoc/913/getDoc/en/nlsref.hlp/a002601967.htm HTH Patrick ... View more

This sounds like SAS/Graph using the Annotate facility and PROC GSLIDE - and it sounds also awful complicated for the purpose. I think it would be easier to create a gif file with your name in a circle (using some 3rd party product like Adobe Illustrator) and then include this gif file in your output using ODS. HTH Patrick ... View more

Hi Daniele An alternative could be to use some of Richard A. DeVenezia's macros: http://www.devenezia.com/downloads/sas/macros/index.php?m=ds2text HTH Patrick ... View more

The LAG() function might also be of some help for you. ... View more

HTH Patrick data have; do timekey=1 to 12; do borrid=1 to 10; if ceil(ranuni(0)*5)=5 then output; end; end; run; proc sort data=have; by borrid timekey; run; data want; set have; by borrid timekey; N_change+1; if last.borrid then do; if N_change>=3 then output; N_change=0; end; run; proc print data=want; run; ... View more

You will have to explain a bit better what you have and what you want. May be you give us also some examples. ... View more

According to this links http://www.quicklabs.com/Integration/qbintegration.html, http://www.qodbc.com/qodbc.htm there should be possibilities using ODBC. Do you have the SAS/Access to ODBC interface? And what version of Quick Book under which OS are you speaking about? ... View more

I think it would be very hard to develop what you ask for - and even if possible you would most likely not have the appropriate priviledges to implement it. An approach could be to develop a add-in for EG which does what you want (check for started task every x minutes - and if there's non run a tiny little program on the server). I know that the work-around I proposed is not very handy - but it's right now the best I can come up with. I think that you have to request a change from your IT department and explain them what it means for you to loose every 30 minutes the connection (and therefore all your work datasets and results). HTH Patrick ... View more

Hi I think you have very valid reasons to request for a change in how and when idle EG sessions are terminated. I can't think of a solution which you as a user could implement to "trick the system". A workaround could be: Whenever you leave your workstation for more than 30 minutes you start the following task in EG - and you stop the task when you come back. As I understand what's going on this should keep your session alive because you keep the workspace server busy. data _null_; do i=1 to 16; rc=sleep(1,1700); end; run; HTH Patrick ... View more

Hi I would contact the person who is responsible for the SAS installation in your organisation. It's often a problem that a user's SAS EG session (yours for example) stays alive for days eventually locking datasets which have to get updated overnight. There must be some customised process implemented on the mainframe side which terminates EG sessions which are not active for more than 30 minutes. May be you can convince the person responsible to increase this time (at least during working hours). Is your problem only convenience (you have to re-connect) or is it that long running jobs get canceled? If the latter is the case then you sure have a good reason to ask for a change of how and when idle sessions are killed. HTH Patrick ... View more

Hi Thomas What I have seen working is: - The metadata definitions use &DBUSER and &DBPASS (like that, as text string). - The values are set in the autoexec -> %let DBUSER=.... The deployed code contains then something like ..password=&DBUSER... - which resolves at runtime and based on the value set in the autoexec used. HTH Patrick And yes: use proc pwencode to mask the passwords at least a bit. Message was edited by: Patrick ... View more

I investigated a bit more: DI doesn't let you save too long lines (>254) as such lines would get truncated in SAS batch processing. Linus got it once more right: Just add line breaks and everything will work fine. Patrick ... View more

..... from check a LEFT JOIN kinder B ..... A INNER JOIN gives you only the rows with common keys in both tables. If table A has a row where the key doesn't match with table B then this row won't be part of the result table. Use a left join and you won't loose rows from table A (but of course: one row in the result table will have missings for all vars coming from table B). HTH Patrick ... View more