tag:blogger.com,1999:blog-20769129.post5721829771940496174..comments2023-10-15T06:55:57.488-07:00Comments on Computing from Out in Left Field: Our journey with SAS's StoredProcessService object continues...Savianhttp://www.blogger.com/profile/17299246950932791515noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-20769129.post-17662262942822728862011-05-17T09:09:35.550-07:002011-05-17T09:09:35.550-07:00Async = false is the default which is why includin...Async = false is the default which is why including it works or commenting out the line works.Savianhttps://www.blogger.com/profile/17299246950932791515noreply@blogger.comtag:blogger.com,1999:blog-20769129.post-3994608681361881532011-05-17T01:44:02.741-07:002011-05-17T01:44:02.741-07:00It works ok for me if I set Common.SasLanguageServ...It works ok for me if I set Common.SasLanguageService.Async = false under C#.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-20769129.post-33060664551924625512011-04-23T09:50:49.268-07:002011-04-23T09:50:49.268-07:00I did not have much time to investigate the .NET c...I did not have much time to investigate the .NET component either. I discovered it by accident :P (like all nice SAS stuff it is hidden very good) and only used it in a simple demo, but as far as i understand it, the stored process has to be already registered in the metadata server. <br />If you just want to execute some SAS code from a file location (which is not registered in the metadata) you should use a workspace server, right?<br /><br />Well good luck on meeting your deadline. It would be very nice if you could share your experience with the managed assembly. I guess there are only very few people like us who use SAS/ Integration Technologies in combination with Microsoft technology.Andreas Menrathhttp://analytical-software.denoreply@blogger.comtag:blogger.com,1999:blog-20769129.post-71432369802177743012011-04-19T11:19:49.681-07:002011-04-19T11:19:49.681-07:00Well, the issue with the .NET component is that it...Well, the issue with the .NET component is that it relies on a Stored Process Server already being set up (from what I could tell). Hence, you can't just pass the file locations and the parms and execute. I would love it if this wasn't the case but that is what I gleaned from my short exploration.<br /><br />I will work on it more once I clear a deadline that I have to meet.Savianhttps://www.blogger.com/profile/17299246950932791515noreply@blogger.comtag:blogger.com,1999:blog-20769129.post-71477441249019842662011-04-19T09:35:42.379-07:002011-04-19T09:35:42.379-07:00xoxoxo
Now THAT's what I have been looking fo...xoxoxo<br /><br />Now THAT's what I have been looking for for a long, long time. Playing with the help file now...<br /><br />More info to come later.Savianhttps://www.blogger.com/profile/17299246950932791515noreply@blogger.comtag:blogger.com,1999:blog-20769129.post-13854040171401155062011-04-19T08:22:53.460-07:002011-04-19T08:22:53.460-07:00It seems like you're trying it the hard way us...It seems like you're trying it the hard way using SAS IOM via COM. Did you know that there might be a managed wrapper in your Integration Technologies folder if you have SAS9.2?<br /><br />Look for a <b>StoredProcessService.dll</b> and the documentation file <b>StoredProcessService.chm</b> in the <i>%programfiles%\SAS\Shared Files\Integration Technologies</i> folder.<br /><br />BTW: i really like your blog!Andreas Menrathhttp://www.analytical-software.denoreply@blogger.com