topic How to trigger multiple programs at same time? in SAS Procedures

How to trigger multiple programs at same time?

deleted_user — Thu, 16 Sep 2010 14:17:42 GMT

Would like to know if its possible to trigger multiple sas scripts at the same time with out using rsubmit?

if so how can we do it?

Thanks,
activa

Re: How to trigger multiple programs at same time?

twocanbazza — Thu, 16 Sep 2010 23:19:03 GMT

have a look at
x cmd with nowait.

Cheers

Barry

Re: How to trigger multiple programs at same time?

SASKiwi — Thu, 16 Sep 2010 23:37:19 GMT

First you need to establish multiple SAS server sessions, then do asynchronous RSUBMITs using WAIT=NO:

signon session1;

signon session2;

rsubmit session1 wait=no;
sas code here....
endrsubmit;

rsubmit session2 wait=no;
sas code here....
endrsubmit;

If you then want your parent session to wait for both session1 and session2 to finish then use:

waitfor _all_ session1 session2;

Re: How to trigger multiple programs at same time?

ChrisNZ — Mon, 20 Sep 2010 02:09:26 GMT

I too read " with out using rsubmit" as "with using rsubmit" at first glance... 🙂

Re: How to trigger multiple programs at same time?

SASKiwi — Mon, 20 Sep 2010 04:50:11 GMT

Maybe I should read more carefully! BTW the RSUBMIT approach is so much more flexible and easier to manage I would only use alternatives if I didn't have SAS/CONNECT.

Re: How to trigger multiple programs at same time?

ieva — Mon, 20 Sep 2010 07:57:48 GMT

you can try submitting also some programs in EG, others in batch mode

Re: How to trigger multiple programs at same time?

Peter_C — Mon, 20 Sep 2010 11:42:55 GMT

how about a scheduler?

What makes the decision to launch those SAS processes?
A long time ago (forget galaxy ...) I wrote a routine that would launch SAS programs based on a trigger = "that a file exists".

My routine was a SAS task that watched and tested for the trigger file with fileexist( 'trigger file name') which is FALSE (0) until that file exists. Once TRUE, it used the X-statement to launch the SAS programs because they were to run independantly. Another trigger was needed to stop the "watching" task. That watcher process could have been set up as a windows service.

I think a proper scheduler should be able to do that in a much more supportable way 😉

peterC