06-21-2011 09:43 AM
rsubmit task1 wait=no ;
data cust2 ;
set cust (obs=10000) ;
rsubmit task2 wait=no ;
data accs2 ;
set accs (obs=10000) ;
waitfor _all_ task1 task2 ;
06-21-2011 06:08 PM
06-22-2011 09:22 AM
06-22-2011 09:52 PM
06-23-2011 05:14 PM
Thanks for confirming this Patrick.
I suspected that this might be the case as the SUGI Paper 124-29, page 3 section D (www2.sas.com/proceedings/sugi29/124-29.pdf) suggests creating a macro variable with the physical path of the child process and using this to assign a libref in the parent session. This would allow me to access the data in the work directories of the child processes before the signoff is executed and the session output lost.
I think the thing that's confusing me at the moment are the following few lines in my autoexec as it means any session I start isn't 'clean';
1 %let mserv=coserv66 7551;
2 %let servname=coserv66;
3 options remote=mserv;
4 signon mserv user=****** password="******";
6 options no$syntaxcheck;
As I've never delved too deeply into this, I have always believed that if I ran the following;
that it would submit the code to the server named mserv rather than a task named mserv running on the server it was assigned to.
As SASKiwi pointed out in his reply, I had to assign a server to the tasks before I could tell them to signon. (this is something I've not had to do before as it was handled in the autoexec).
I've also had to specify a user and password when using the signon.
Are you aware of any papers which introduce the concepts of rsubmit, signon or task handling?
All the results I've found on Google or SAS.com are a little too technical and I think I need to start with the basics first.
Thanks in advance for any guidance you can give.
04-09-2014 04:43 PM
there is an option for signon or rsubmit statements INHERITLIB
It would make writing direct to a client library straightforward from the server sessions.