the problem when using distinct is that your subquery still gets more than one row for the same provider and patient_id. That's why distinct will not help. Simple fix is that you update your where clause with some extra condition or group by statement. The simliest way could be using min or max function with distinct. But i don't think that is correct with some business logic. (select distinct min(r.patient_birth_yr) from up_date as R where S.provider=R.provider and s.patient_id=r.patient_id); ... View more

What are these tables: Mi.tbl_bau_stats_details Mi.tbl_bau_status_valuations? Are they SAS tables? I had the same problems when using oracle data. Workaround was done then downloaded data, then used proc sql; After this data was sorted. ... View more

I think, the problem is here: When macro starts, the table subgroup is not still created, because call execute submits only after "run;" statement. Try this: data _null_ ; set Overall; subGroup="g" ||compress(var1,' ') ||"c"||compress(var2,"-") ; call execute ( "data " || subgroup||";" || "set Overall ( where =( group = " || put(var1,1.) || " and centre = '" || put(var2,7.) || "'));" || "run ;" ) ; run ; %CalByCentre(subgroup);**********Subgroup won't be resolved; ... View more

> You cannot combine macro language (specifically your > use of macro variables) with the PROC SQL code that > is supposed to generate the macro variable values. Why not? Everything seems to be ok. Macro generates code. Code generates macroVars. ... View more

I don't see where &y is increasing. And besides do not use &attrib_item ne Instead use "&attrib_item" ne "" ... View more

Macro and macro variable is different. All macro variables are stored in a view: sashelp.Vmacro. Its better to deal with a subset of table sashelp.Vmacro, if you use big sequences of macro variables. Every sas session deals with their own macro variables. ... View more

Yes you can. Storing a macro: libname AAA "C:/macros"; options mstored sasMSTORE=AAA; %macro TestStore/store; %put stored macro; %mend testStore; The macro will be stored in library AAA. If you want to use it, you have to use the same option, and assigned library AAA. libname AAA "C:/macros"; options MSTORED SASMSTORE = AAA; %testStore; ... View more

what is the option XCMD value. If XCMD = NOXCMD, then you can not run X command. Simplest way to do check: proc options option=XCMD; quit; ... View more

What is that command you are executing? OS: Windows, Unix? It's better, to know more info about your problem. ... View more

Thank you, Chris, that worked. Besides, the option that must be "excluded" is signonwait=n. Well there's some problems about inhering libraries in the "second" singon. Here is the code. And log that was produced: ***************** CODE *******************; dm log "clear"; signon _001 sascmd="!sascmd" inheritLib=(WORK=WORK1); data _null_; call sleep(5,1); put "==> Wait for signon 1"; run; rsubmit _001 wait=no macvar=JOB001 signonwait=y persist=n ; data _null_; put "==> Rsubmit on _001 ok"; run; signon _002 sascmd="!sascmd" inheritLib=(WORK=WORK2); signoff _002; ***************** LOG *******************; 28 dm log "clear"; 29 signon _001 sascmd="!sascmd" inheritLib=(WORK=WORK1); NOTE: Remote signon to _001 commencing (SAS Release 9.01.01M3P020206). NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened instead. NOTE: All profile changes will be lost at the end of the session. NOTE: Copyright (c) 2002-2003 by SAS Institute Inc., Cary, NC, USA. NOTE: SAS (r) 9.1 (TS1M3) NOTE: This session is executing on the XP_PRO platform. NOTE: (E9BX04) SAS 9.1.3 SP 4 NOTE: SAS initialization used: real time 0.56 seconds cpu time 0.26 seconds NOTE: Remote signon to _001 complete. 30 31 data _null_; 32 call sleep(5,1); 33 put "==> Wait for signon 1"; 34 run; ==> Wait for signon 1 NOTE: DATA statement used (Total process time): real time 5.00 seconds cpu time 0.15 seconds 35 36 rsubmit _001 wait=no macvar=JOB001 signonwait=y persist=n ; NOTE: Background remote submit to _001 in progress. NOTE: Remote submit to _001 commencing. 1 data _null_; 2 put "==> Rsubmit on _001 ok"; 3 run; ==> Rsubmit on _001 ok NOTE: DATA statement used (Total process time): real time 0.03 seconds cpu time 0.03 seconds 4 signon _002 sascmd="!sascmd" inheritLib=(WORK=WORK2); ERROR: Read Access Violation In Task [ CONNECT ) Exception occurred at (012D9718) Task Traceback Address Frame (DBGHELP API Version 4.0 rev 5) 012D9718 06B2C110 sashost:Main+0x2A88 60346FE4 06B2FEAC sasxdmr:mcn_main+0x5FE4 60391219 06B2FF88 saslcsrv:mcn_main+0x219 012E2B72 06B2FFA0 sashost:Main+0xBEE2 012E6C90 06B2FFB4 sashost:Main+0x10000 7C80B729 06B2FFEC kernel32:GetModuleFileNameA+0x1BA ERROR: Generic critical error. ERROR: Server init failed, INHERITLIB option will be ignored. NOTE: Remote signon to _002 commencing (SAS Release 9.01.01M3P020206). NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened instead. NOTE: All profile changes will be lost at the end of the session. NOTE: Copyright (c) 2002-2003 by SAS Institute Inc., Cary, NC, USA. NOTE: SAS (r) 9.1 (TS1M3) NOTE: This session is executing on the XP_PRO platform. NOTE: (E9BX04) SAS 9.1.3 SP 4 NOTE: SAS initialization used: real time 0.43 seconds cpu time 0.40 seconds NOTE: Remote signon to _002 complete. 5 signoff _002; NOTE: Remote signoff from _002 commencing. NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414 NOTE: The SAS System used: real time 0.45 seconds cpu time 0.40 seconds NOTE: Remote signoff from _002 complete. NOTE: Remote submit to _001 complete. NOTE: Remote signoff from _001 commencing. NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414 NOTE: The SAS System used: real time 6.95 seconds cpu time 0.85 seconds NOTE: Remote signoff from _001 complete. ... View more

Thank You for your answer, Daniel, I understand about setting threads from main thread, but in my situation i have to start a thread inside one child thread. Is it possible? ... View more

How can i do that? ... View more