From: MichelleZ on 14 May 2010 12:31 Or no shell script is needed at all. In the old days I used to string a bunch of jobs together using submit and jcl........ But now maybe... filename submit pipe "nohup.sh /apps/SAS/SAS_9.1/sas -nodms &dir./ sasprocess -log /directory/"; data _null_; file submit; run;
From: RolandRB on 14 May 2010 14:04 On May 14, 6:31 pm, MichelleZ <michelle_zunnur...(a)hotmail.com> wrote: > Or no shell script is needed at all. > > In the old days I used to string a bunch of jobs together using submit > and jcl........ > > But now maybe... > > filename submit pipe "nohup.sh /apps/SAS/SAS_9.1/sas -nodms &dir./ > sasprocess -log /directory/"; > > data _null_; > file submit; > run; The question the O/P asked was how to run the jobs using parallel processing while at the same time sticking to certain dependencies.
From: MichelleZ on 14 May 2010 17:13 On May 14, 1:04 pm, RolandRB <rolandbe...(a)hotmail.com> wrote: > On May 14, 6:31 pm, MichelleZ <michelle_zunnur...(a)hotmail.com> wrote: > > > Or no shell script is needed at all. > > > In the old days I used to string a bunch of jobs together using submit > > and jcl........ > > > But now maybe... > > > filename submit pipe "nohup.sh /apps/SAS/SAS_9.1/sas -nodms &dir./ > > sasprocess -log /directory/"; > > > data _null_; > > file submit; > > run; > > The question the O/P asked was how to run the jobs using parallel > processing while at the same time sticking to certain dependencies. I thought the nohup would allow "parallely" but it did not. A quick test showed the jobs ran sequentially using multiple filename submit pipe statements. Back to thinking.....
From: MichelleZ on 14 May 2010 17:55 Mark responsed via SAS-L Hi Michelle, When running jobs asynchronously on a Unixsystem requires two thing when running remotely,or if you plan on logging off, or only one thingwhen you know the batch or user session will notdrop. i.e. the nohup is named for the old daysprior to internet. Back when your connection wasdial-up the nohup instructs Unix not to hang-upthe connection even if it sees the connection lost.The other piece is to tell Unix to run synchronouslyor asynchronously. This is done by placing an &(ampersand) at the end of the command line whenyou want the job to run separately from the currentshell and you are given your prompt back immediatelyafter you execute the command. Try adding a spacefollowed by an ampersand to the end of your commandstring. Hope this is helpful. Mark TerjesonInvestment Business IntelligenceInvestment Management & ResearchRussell Investments253-439-2367 RussellGlobal Leaders in Multi-Manager Investing Michelle responde to Mark, Thanks for clearing that up Mark, I did, and it worked. 2 jobs ran simultaneously, or should I say, parallely. Ok, synchronously. So Amar, it's up to your personal preference whether to use shell script or try this instead. This will eliminate the need for another separate process, just add to your current processes.
From: Patrick on 15 May 2010 09:45 Did you see this post? http://groups.google.com/group/comp.soft-sys.sas/browse_thread/thread/2cb5450f7abc847a
First
|
Prev
|
Pages: 1 2 Prev: Merging 2 datasets by 2 variables Next: "BackTesting" Vintage analysis |