About AllanBowe

AllanBowe · ‎06-14-2021

Great article! It's also possible to dynamically create backend SAS Jobs in Viya using macro, here is an example: https://core.sasjs.io/mv__createjob_8sas.html

AllanBowe · ‎06-04-2021

You can log events as part of the stpinit program More info: https://rawsas.com/event-logging-of-stored-process-server-sessions/

AllanBowe · ‎06-04-2021

Hi Mahesh - you don't need to open the SPK file, the mappings are there in metadata. We built this functionality into Data Controller - it works at two levels: 1) Table level. This is a proc metadata call that extracts all the job mappings into a table. 2) Column level. This is a bit more involved, with recursive queries. For efficiency, in Data Controller, we cache the results in a table for a faster response the next time around. If you'd like to build something similar, we made some process notes here: https://docs.datacontroller.io/dcu-lineage/ And you can view the generated diagrams here: https://docs.datacontroller.io/videos/#data-lineage Data Controller is free for 5 users.

AllanBowe · ‎05-23-2021

For reference, this is what we did in the end: 1. Install xquartz: https://www.xquartz.org/releases/index.html 2. Open xquartz terminal and run: ssh -Y user@server 3. execute the following file: ./opt/sas/sas9/SASHome/SASManagementConsole/9.4/sasmc Then follow the prompts to log in, and the folder is created. I have to say, x11 on mac is much faster than it used to be!

AllanBowe · ‎05-22-2021

Thanks Paul! Indeed that appears to be the "proper" way to achieve the programmatic approach.

AllanBowe · ‎05-21-2021

Thanks Carmine - we don't currently have that installed - will give it a crack if we don't find an easier way.

AllanBowe · ‎05-21-2021

I have a SAS 9 user with a Macbook Pro. He's a Stored Process app developer, and I'd like for him to be able to create his content in his home directory in metatdata. According to the docs - "The first time a user logs on to an application that requires a home folder, the user's home folder is automatically created." Is there a list of apps anywhere that will do the 'home directory' stuff? Neither logging onto /SASStudio nor /SASStoredProcess/do does the trick. What is the best course of action? Get him to download xquartz and x11 into SMC? Create the folder programmatically, and update the permissions?

AllanBowe · ‎05-13-2021

Hi @elisehoo1 - two things: 1) the options must be in "system option" format, not written as an options statement, eg with the initial dash. See example here. 2) you don't typically see the log from the autoexec in the resulting session. On that last point - in testing I've also found (with a pooled session, in 3.5) that the autoexec is not "viya aware" - so you cannot set CASLIBs for instance, and not all macro variables are available.

AllanBowe · ‎05-10-2021

Hi Dave - this macro may help (credit to @PaulHomes who wrote the original): https://core.sasjs.io/mm__getlibmetadiffs_8sas.html If you are interested in finding more issues with your SAS 9 metadata, we built a "plug and play" scanner that can find all kinds of health issues in a SAS 9 environment, as such as dangling metadata, security misconfigurations, SAS coding issues, custom code in DI Studio, missing primary keys, etc. Well over 100 different checks. Do get in touch if you'd like to give it a whirl.

AllanBowe · ‎05-02-2021

The only places in Viya that I know of, where you can set up an "automatic" autoexec, are: * The compute contexts (eg SAS Studio, SAS Job Execution). This is the 'official', 'system' autoexec. * The "user autoexec" in SAS Studio, this is user-specific and not useful for batch jobs. Beyond that it's a case of running precode as part of your code, somehow. Maybe someone here, more knowledgeable, can correct me. I don't see any other options in the REST API.

AllanBowe · ‎05-02-2021

Doesn't have to be a URL param - it can also be passed in under "parameters" in the input JSON to the REST APIs (here's an example for the SASjs adapter: https://github.com/sasjs/adapter/blob/0aa0ae65e0cae3564177ba105ad90b73edf9073a/src/SASViyaApiClient.ts#L327 ) The thing with Viya is that all requests are going through either the REST API, or through the job execution web service. The CLI (eg the SASjs CLI or the official SAS CLIs) are just wrappers for making those requests. In reference to "normal command line SAS call", this isn't really a thing any more. It IS possible to invoke the SAS exe from a Viya server, but that's really just a SAS 9 session, it's not "Viya aware" insofar as you can trigger viya services from SAS code without extra authentication etc..

AllanBowe · ‎05-02-2021

You can control the context used for running jobs via the "_contextname" URL parameter in the SASJobExecution web app. It's worth noting that in most enterprise SAS 9 deployments, the autoexec (eg autoexec_usermods.sas) file is also typically locked to those with admin rights.

AllanBowe · ‎05-02-2021

Hi @elisehoo1 In Viya, the autoexec is stored as part of the compute context. To modify it you need to log onto SASEnvironment Manager as an administrator, select Contexts, View Compute Contexts. Choose the relevant compute context (eg for SAS Studio, or Job Execution Service), click the edit icon, then click the "Advanced" tab. You can now enter autoexec statements and any startup options. To help automate this process, we (Analytium SAS Apps team) built a tool that makes use of the Viya REST APIs to modify compute contexts. The benefit of this approach is that you can keep your source configuration in GIT and deploy on demand. The documentation for that is available here: https://cli.sasjs.io/context If you don't have the administrator rights, you could also configure your jobs to include an autoexec as "precode". If you are using SASjs to compile your jobs / services / tests, you can do this via the initProgram setting. More info: https://github.com/sascommunities/sas-global-forum-2021/blob/main/papers/1135-2021_Scaffolding-SAS-Projects/README.pdf https://cli.sasjs.io/compile Example repository: https://gitpod.io/#github.com/sasjs/template_jobs Video: https://www.youtube.com/watch?v=KKfUHTngSFo

AllanBowe · ‎04-10-2021

this fixed it for me - thanks!

AllanBowe · ‎04-03-2021

Not at all - GIT does not need to be connected to SAS at all. Rather it's something that each developer connects to, in order to build their SAS projects. Once code is linted, documented, compiled, built, deployed and unit-tested - then it is promoted (each job / service being fully self contained, either in metadata or a Viya job) through the usual deployment process into production. If you choose to make that part of your git / dev ops automated workflow (eg push to production upon merge to a main or master branch) that is up to you. I use git exclusively from within my local VS Code instance and push my finished jobs to SAS when they are ready (using `sasjs deploy`). Happy to jump on a call and explain more.