About AllanBowe

AllanBowe · ‎07-17-2025

The FILESRVC method of the filename statement is a useful beast indeed - you can even use it in pure macro functions! Here are some examples from the SASjs Core library: mfv_existfile.sas - Checks whether a file exists in SAS Drive mfv_existfolder.sas - Checks whether a folder exists in SAS Drive. mfv_getfolderpath.sas - Returns the path of a folder from the URI. mfv_getpathuri.sas - Returns the uri of a file or folder.

AllanBowe · ‎06-09-2025

Finally figured it out - was triggered by this usage note: https://documentation.sas.com/doc/zh-cn/sasadmincdc/v_021/caljobs/n0t21mf756sv0en1kd176kky8upt.htm Turns out that the behaviour changed in February this year, and now _omitSessionResults is both mandatory (if you want the results) and - CASE SENSITIVE This smells like a bug and it's currently in SAS track, case number CS0254721 The fix to the SASjs adapter is here: https://github.com/sasjs/adapter/pull/845/files And the fix to SASjs Core is here: https://github.com/sasjs/core/pull/397/files

AllanBowe · ‎06-05-2025

Unfortunately not. I went and created a SASjs project to illustrate the issue. You can deploy it to Viya in 3 lines of code: %let apploc=/Public/jes_demo; /* your preferred SAS Drive location */ filename demo url "https://raw.githubusercontent.com/allanbowe/jes_issue/refs/heads/main/viya.sas"; %inc demo; In the last line of the log there is a link to a Job - this contains the PROC HTTP calls that illustrate the problem (preceded by some supporting macro definitions). Copy that URL into a browser and add "&_DEBUG=2477" before submitting. This will show the log and the reponses from the HTTP calls. You can edit that job directly, eg to play around with the request body. Just save the job definition and refresh the browser for the results. Source code for the project is here: https://github.com/allanbowe/jes_issue

AllanBowe · ‎05-29-2025

Thanks @gwootton and @jazmon for your feedback! Indeed the problem turned out to be nothing to do with SAS and an issue with the external (to SAS platform) Azure Gateway. The SAS Admin "removed the limits on the WAF associated with the NetApp gateway" and the issue was fixed. Related SAS Track: CS0255081

AllanBowe · ‎05-20-2025

The behaviour of the JES API appears to have changed in the last year or so, and we need some help getting our (previously functional) code to work! We are running a Job (using POST /jobExecution/jobs - https://developer.sas.com/rest-apis/jobExecution/createJob ) that returns a JSON file generated using the following code (as described here ) filename _webout filesrvc parenturi="&SYS_JES_JOB_URI" name="_webout.json"; data _null_; file _webout; put '{"name" : "value")'; run; The exact API request looks like this: With the following payload: We then poll for results using: /jobExecution/jobs/db8810ec-7282-4093-a0f9-41f693ebf359/state?_action=wait&wait=300 And finally fetch the results using: /jobExecution/jobs/db8810ec-7282-4093-a0f9-41f693ebf359 With the following response: We have tried tweaking the arguments, to no avail. The _webout fileref is definitely created. We have also tried using the RESULTFILE option. How to get the _webout result location returned to the JES API triggered Job?

AllanBowe · ‎05-17-2025

looks like multipart form data isn't yet supported https://communities.sas.com/t5/SAS-Procedures/multipart-form-data-REST-API-POST-in-PROC-HTTP-failing/td-p/325284 EDIT: catching up, indeed it is actually supported in 2025 https://documentation.sas.com/doc/en/pgmsascdc/v_063/proc/p10hyllh9kzzwxn1juthxahne5vp.htm

AllanBowe · ‎05-13-2025

When submitting a relatively large (>20k lines) SAS program in SAS Studio we are getting the 403 below We are also unable to upload the file to SAS Content, or the SAS Server directly using the file explorer (just hangs) SYSVLONG=V.04.00M0P030625 Product name: SAS® Studio (Analyst) Version: Stable 2025.03 Release: 20250506.1746542786204 Any hints / suggestions?

AllanBowe · ‎06-17-2024

This is a native feature in Data Controller for SAS, and available in the community (free) version Go to View / Lineage / choose library / choose table / choose column (optional) and you get a full impact analysis (jobs and tables in png / svg / csv formats) https://docs.datacontroller.io/videos/#data-lineage https://git.datacontroller.io/dc/dc/releases

AllanBowe · ‎10-16-2023

actually, there is a way you can still keep your web app contained in your SAS code, and stream everything through WEBOUT, and comply with CSP We manage it with Data Controller - one SAS program (demostream_sas9.sas) deploys the entire app: https://git.datacontroller.io/dc/dc/releases An overview of the technique is described here: http://sasapps.io/sas-streamed-apps

AllanBowe · ‎10-16-2023

The option you describe (putting the web content on the web server) is in fact, the correct approach to take. Mixing HTML/CSS/JS/IMG/ICO/WOFF etc into DATA STEP and PROC STREAM is a very hacky / hard to maintain & extend way to build (non trivial) web apps. The option you are probably looking for, would be to modify the CSP policy in the web server directly. You cannot change CSP policy from SAS code, nor from the content (or headers) of the WEBOUT destination. More info here: https://sasjs.io/security/#content-security-policy

AllanBowe · ‎10-06-2023

You can stream web files using STPs so long as you set the http headers, eg using a macro similar to this one: https://core.sasjs.io/mp__streamfile_8sas.html In general though it's not a recommended approach. You will have the overhead of a SAS session for every asset (html, css, js files etc) plus the challenge of writing code to deal with situations such as very wide lines of text, binary files (images), different encodings etc. You would be far better off just using a web server to serve your web content, and calling your SAS services as needed using JS. If you don't have SAS 9 EBI, or SAS Viya, you could try out SASjs Server as an alternative: https://server.sasjs.io The advantage of following the SASjs Server approach is that (so long as you use the SASjs framework) you will be able to easily migrate to Viya at a later date.

AllanBowe · ‎09-04-2023

@YuryShkoda found the issue Seems the "arguments" attribute is no longer supported on the compute API side We use it as our payload is also used for executing Jobs as well as arbitrary code. Solution is simply to remove that object from the request Body.

AllanBowe · ‎09-04-2023

This thread is in relation to this ticket: https://github.com/sasjs/adapter/issues/829 Looking for support here whilst we figure out the root cause (maybe someone is already aware). It looks like something has changed recently on Viya 4 when it comes to running code in an existing session. This is the request / response (running SASjs CLI with verbose mode): ℹ HTTP Request: POST /compute/sessions/ca3f4bdf-3cf8-48b5-91fb-f9f11999789c-ses0000/jobs HTTP/1.1 Accept: application/json Content-Type: application/json Authorization: Bearer eyJhbGciOiJSUzI1NiIsIREDACTED User-Agent: axios/0.27.2 Content-Length: 1162 Host: extviya4.emea.sas.com Connection: close { name: 'myJob', description: 'Powered by SASjs', code: [ 'data work.demo;', ' do x=1 to 1e6;', ' y=ranuni(0);', ' end;', 'run;' ], variables: { SYS_JES_JOB_URI: '', _program: '/Viyademo08 Group Folder/4GL/proj/yurshk/jobs/long/long', _DEBUG: 131 }, arguments: { _contextName: 'SAS Job Execution compute context', _OMITJSONLISTING: true, _OMITJSONLOG: true, _OMITSESSIONRESULTS: false, _OMITTEXTLISTING: true, _OMITTEXTLOG: false } } HTTP Response Code: 400 HTTP Response: Date: Fri, 01 Sep 2023 15:14:27 GMT Content-Type: application/vnd.sas.error+json;charset=utf-8;version=2 Content-Length: 470 Connection: close Set-Cookie: sas-ingress-nginx=9a59cdfa1a238157REDACTED; Path=/compute/; Secure; HttpOnly; SameSite=Lax Cache-Control: no-cache, no-store, max-age=0, must-revalidate Content-Security-Policy: default-src 'self'; object-src 'none'; frame-ancestors 'self'; form-action 'self'; Expires: 0 Pragma: no-cache Sas-Service-Response-Flag: true Vary: Origin X-Content-Type-Options: nosniff X-Xss-Protection: 1; mode=block Strict-Transport-Security: max-age=63072000; includeSubDomains { version: 2, httpStatusCode: 400, errorCode: 5036, message: 'The input provided for this request is not valid for this endpoint. ', details: [ 'path: /compute/sessions/ca3f4bdf-3cf8-48b5-91fb-f9f11999789c-ses0000/jobs', 'correlator: d03057f5-3c73-4a2c-b171-af28f8367024' ], remediation: 'Check to make sure the request made to the server is a valid request. Contact your system administrator to determine if the request made from your application is formatted correctly.' } Checking the API docs the example body does appear to be different however it does not correspond to the referred JobRequest schema. Does anyone have any working examples, or can see what is wrong with our payload? It has worked fine for several years until now..

AllanBowe · ‎09-01-2023

Great to chat, we're on the case in relation to the root cause, the issue can be tracked here: https://github.com/sasjs/adapter/issues/829

AllanBowe · ‎09-01-2023

Interesting. This code is not within SASjs either. Perhaps we can schedule a call to take a look? I'd be happy to help, if I can. https://4gl.io/cal Am also free for the rest of today if you want to send me a PM.