About AllanBowe

AllanBowe · ‎10-01-2021

It appears to be a bug on the TABLE_CATALOG field in dictionary.TABLE_CONSTRAINTS proc sql; create table work.example( TX_FROM float format=datetime19., DD_TYPE char(16), DD_SOURCE char(2048), DD_SHORTDESC char(256), constraint pk primary key(tx_from, dd_type,dd_source), constraint unq unique(tx_from, dd_type), constraint nnn not null(DD_SHORTDESC) ); /* this table has no records */ create table work.zero_records as select * from dictionary.TABLE_CONSTRAINTS where upcase(TABLE_CATALOG)="WORK"; /* this table has expected records */ create table work.has_records as select * from dictionary.TABLE_CONSTRAINTS where TABLE_CATALOG="WORK"; The behaviour is exhibited with other functions as well. The behaviour does not apply to other columns (eg TABLE_NAME). SYSVLONG=9.04.01M7P080520

AllanBowe · ‎09-29-2021

There's definitely an easier way, surely not a _faster_ way though. We wrote a macro to avoid the need for you to produce boilerplate: https://core.sasjs.io/mp__updatevarlength_8sas.html The nice thing about the macro is that it will drop and recreate constraints if it's a key variable (it will also avoid the rewrite if you choose the same length)

AllanBowe · ‎09-28-2021

After downloading all 10 files, you can set filerefs to each eg: filename fref1 "/location/file1"; filename fref2 "/location/file2"; filename fref3 "/location/file3"; ... And then append them all in one go using this macro as follows: %mp_appendfile(baseref=basefile, appendrefs=fref1 fref2 fref3 ...)

AllanBowe · ‎09-28-2021

The `in=` parameter can be a FILEREF, it doesn't have to be a string Just create the fileref exactly how you want it and pass it in, eg as follows (untested): filename example temp; data _null_; file example; put '{"projectId":"290","data": "id,study_refusal\n100009,0\n104568,1" ,"dataFormat":"csv","serverName":"INTERNAL"}'; run; ods escapechar="\" proc http url="&myurl." OAUTH_BEARER="&mytoken." method="POST" in=example ct="application/json" ; run; quit;

AllanBowe · ‎09-28-2021

You can use the metabrowse feature in Base SAS to check the Responsible Parties. It's also possible in Data Controller for SAS - with the MetaNav feature:

AllanBowe · ‎09-27-2021

Maybe your log has been redirected. There are many reasons. Please share code and log!

AllanBowe · ‎09-27-2021

Thanks for taking the time to put together such a comprehensive series @XavierBizoux

AllanBowe · ‎09-22-2021

The `sysjobid` is the PID and it CAN be the same across multiple sessions. Your question is confusing as you ARE creating different log files per process / session due to the use of a timestamp. To ensure uniqueness though, you might want to use a random number as well, as shown here: https://core.sasjs.io/mf__uid_8sas_source.html For even better uniqueness you can use the `uuidgen()` function as shown in this macro: https://core.sasjs.io/mf__getuniquename_8sas.html

AllanBowe · ‎09-16-2021

Hi @gyambqt, Loading excel files (of any type), with varying column position / order, as many extra columns as you like, from any range, on any worksheet, with any filename is perfectly possible using Data Controller for SAS This is a third party tool (which my team maintain) which is also free for 5 users. The user simply chooses the target table and drags the excel file into the browser. Based on the target table metadata, we can extract the relevant columns, perform any data quality rules, and upload both the data and the original excel file to SAS - using SCD2 if needed. Bitemporal, Retained Keys, composite keys etc are all supported. You can even configure a job to run after an upload. There is a video explaining the process here: https://youtu.be/Dhy1pAbCaEw?t=592 No need for any special ACCESS engines, we use an OEM version of SheetJS to parse the excel. Further documentation here.

AllanBowe · ‎09-10-2021

Just to throw another option into the mix - we recently open sourced our (Analytium) sas9 REST API - it's available here on github: https://github.com/analytium/sas9api It provides REST endpoints for all manner of SAS functions such as listing libraries, fetching datasets, listing users & groups etc.

AllanBowe · ‎09-09-2021

Is there a reason you are using BIWS? As you can see, it involves some security issues, such as embedded passwords and disabled certificates in your case. Just create a regular STP and call it using PROC STP - here's an example: %let appLoc=/Public/app; /* Metadata or Viya Folder per SASjs config */ /* compile macros (can also be downloaded & compiled seperately) */ filename mc url "https://raw.githubusercontent.com/sasjs/core/main/all.sas"; %inc mc; /* create an STP */ filename ft15f001 temp; parmcards4; /* write a file to the file system */ data _null_; file "/tmp/dc/example.txt"; /* write a parameter sent from the client */ put "&myparam"; run; ;;;; %mp_createwebservice(path=&appLoc/example,name=makefile) /* now call the STP with a param */ proc stp program="&apploc/example/makefile"; inputparam myparam="Hello, file!"; run; /* check the file was created */ data _null_; infile "/tmp/dc/example.txt"; input; list; run; Result: The following macro is also helpful for testing SAS web services (on both SAS 9 and Viya): https://core.sasjs.io/mp__testservice_8sas_source.html In any case, I would recommend examining the web server logs to further understand the cause of your internal server error. If you are looking to compile and deploy Stored Processes as web services, you could also look at https://cli.sasjs.io -> it provides DevOps for SAS Apps as well as a mechanism for documenting and testing your services, jobs & macros. More info here: https://sasjs.io/resources/

AllanBowe · ‎09-08-2021

This macro will create a dataset containing all the libraries defined in metadata: https://core.sasjs.io/mm__getlibs_8sas.html Attributes returned: - LibraryId - LibraryName - LibraryRef - Engine

AllanBowe · ‎09-08-2021

You can mock a table using SAS code with DATALINES (also known as CARDS), or - if you'd like the ability to put your mocked table inside a macro - you can use INSERTS. Whichever method you prefer, you can also generate the mocked data directly from an existing table. The following macros may help: https://core.sasjs.io/mp__ds2inserts_8sas.html https://core.sasjs.io/mp__ds2cards_8sas.html https://core.sasjs.io/mp__lib2cards_8sas.html https://core.sasjs.io/mp__lib2inserts_8sas.html If you are generating mocks as part of a test suite, you might also be interested in sasjs test - a commandline approach for testing Jobs, Services and Macros in both SAS 9 and Viya.

AllanBowe · ‎09-03-2021

Your input led to the solution! No need to apologise. It's a strange limitation indeed, or at least, not intuitive. The best thing is, we finally have a way to allow end users to send custom abort messages from the user provided validation programs in our main product - Data Controller for SAS https://datacontroller.io

AllanBowe · ‎09-03-2021

So in the end this did NOT fix my use case - as those macro variables are NOT available inside of macros! SYSINCLUDEFILEDEVICE SYSINCLUDEFILEDIR SYSINCLUDEFILEFILEREF SYSINCLUDEFILENAME To deal with this scenario, I made a macro wrapper for the %include statement, that inserts these variables as precode - it's documented here: https://core.sasjs.io/mp__include_8sas.html