If I write a stored process that uses a (non-pooled) workspace server, the server actually starts a new session to run the process, right?
Is there a way I can define SAS invocation options for the stored process (-altlog -autoexec -config etc?). I want to define these at the stored process level (so, e.g. different stored processes might use different autoexecs), not at the server level. I'm developing stored processes, but I don't administer the server.
One approach would be to use systask to kick off a new SAS session (with the desired options), as Scott Bass describes:
SASAUTOS can be defined in the actual stored process code. And that is what I'm doing now:
But lots of system options (ALTLOG, AUTOEXEC, CONFIG) can only be specified during invocation. Seems that when a new SAS process is invoked to run a stored process, it would be nice to be able to define (in the metadata associated with the stored process), the system options that should be set during the invocation.
But I guess we can't do that yet. Maybe I'll propose this to the SASware ballot.
Registration is open! SAS is returning to Vegas for an AI and analytics experience like no other! Whether you're an executive, manager, end user or SAS partner, SAS Innovate is designed for everyone on your team. Register for just $495 by 12/31/2023.
If you are interested in speaking, there is still time to submit a session idea. More details are posted on the website.