This post was kindly contributed by SAS from Out in Left Field - go there to comment and to read the full post. |
Check out this code:
string newParms = “outdata=WORK.TEST”;
Common.SasLanguageService.Async = true;
StoredProcessService sp = Common.SasLanguageService.StoredProcessService;
sp.Repository = storedProcLibrary;
sp.Execute(storedProcedureName, newParms);
Standard stuff when working with the stored process server through VB or C# (or any other means of hitting these dlls).
Funny thing is the SAS log shows that the macro assignment of newParms never takes place. Hence, &outdata is undefined:
SYMBOLGEN: Macro variable OUTDATA resolves to
Commenting out the Async makes this all work:
SYMBOLGEN: Macro variable OUTDATA resolves to WORK.ALAN_20110418_070053
Now, even wiring up the event handlers for SubmitComplete do not fix the issue. Seems like a bug but I’ll let the guys in R&D figure it out. If you have to waste a lot of time on it, however, keep in mind the nuances here until SAS R&D dives in.
Well, back out to the far left field where I hang out. Time to work on the business problem.
This post was kindly contributed by SAS from Out in Left Field - go there to comment and to read the full post. |