Have you considered just using Data Controller for SAS?  https://datacontroller.io   We recently changed the pricing, so it is now free for unlimited users: https://datacontroller.io/pricing   Would be happy to shadow a deployment.  Thanks to our OEM licence of the HandsOnTable grid system, it can handle on-page editing of several thousand rows (per data page), even hundreds of columns.  For excel uploads, it can be tens of thousands, or more if you have a powerful PC.  For CSV uploads there is no limit, as the processing is done backend in SAS.   We have multiple customer references, including banks / government / insurance if needed.  The source is also available, you can build it yourself - https://git.datacontroller.io   ... View more

Mixing HTML / JS code with SAS is an antipattern - I would not recommend it, for many reasons:   Your app now requires developers with TWO skillsets (SAS + Web) to maintain.  These guys are like unicorns, very rarely are they competent in both disciplines. You cannot test your web / sas code in isolation You cannot lint either your SAS code nor web code using regular IDEs You are reliant on a SAS instance to work on the web component You cannot build a complex application this way (because even a very simple app will rapidly get complex) Good luck using React, Angular, or any modern frontend framework that requires compilation.  (By the way, it's not impossible, you can do this with SASjs Streamed apps) When we built the JES API approach (documented here: https://adapter.sasjs.io/#using-the-jes-api ) it was not possible to re-use session ids, perhaps that has changed now, if so I hope that this thread will be updated. To my understanding though your performance gains will be limited to the use of a re-usable compute context - meaning best case 2 seconds on Viya 3.5 and 6-8 seconds on Viya 4. Contrast with Compute API which is ~1 second - https://adapter.sasjs.io/#using-the-compute-api ... View more

That's pretty much what the SASjs CLI does (although it starts by polling fast, then polls more slowly).   Thanks for sharing your solution! ... View more

That's right, SASjs uses a 'session array' and spawns additional sessions as they are popped off.  It also kills the sessions after they are used, which is more efficient than leaving it running for 15 minutes.   If you want to to re-use a single session you just need to post to the `/compute/sessions /$sessionid/jobs ` endpoint, eg:  https://github.com/sasjs/adapter/blob/master/src/api/viya/executeScript.ts#L157 ... View more

My theory on this is that the reusable context "reuses" a (parent) SAS session for each of the "sas00xx" (child) sessions.  That parent session will have already run the autoexec, and have the options set, making the creation of each child session much faster.   The reason you are seeing new session ids is likely because you are creating new sessions with each request (expensive / still quite slow).  If you want to re-use a specific session, you need to connect to that particular session id (they last 15 minutes without activity by default).   Connecting to an existing session is much faster than creating one each time - which is why, in the SASjs Adapter, we pre-spawn sessions for subsequent use (providing sub-second response time if everything is set up correctly).     ... View more

Definitely - it's done in the DC Data Catalog generator, and the macros are open source:    mm_getlibs - fetch all meta libraries: https://core.sasjs.io/mm__getlibs_8sas_source.html mm_assignlib - assign lib using META engine: https://core.sasjs.io/mm__assignlib_8sas.html If you need to assign a DIRECT libname engine, that's also (mostly) possible:   mm_assigndirectlib - assign lib using NATIVE engine:  https://core.sasjs.io/mm__assigndirectlib_8sas.html Let me know if you need any additional libname engines supported in that last one, or feel free to raise a PR!   /Allan ... View more

Joe - that's fascinating, thanks for sharing!     I also wanted to share our go-to tool for HTTP request sniffing (which also works for https out-of-the-box for certain tools):  https://httptoolkit.com/   Much easier to use than WireShark and can often be deployed without admin rights.   (Edited to remove PG inaccuracy) ... View more

Hi Anne - you are seeing pre-assigned (in metadata) libraries in EG.  These won't be visible in SASHELP or DICTIONARY tables until they are assigned.   More info here:  https://documentation.sas.com/doc/en/bicdc/9.4/bidsag/p1ac6c9mrz0gn2n1spvpkf55ttyk.htm   For info, these libraries CAN be explored without needing to assign them using our free tool:  https://datacontroller.io   /Allan ... View more

the dictionary tables will only give you info for datasets that are assigned to a library in the current session   so the answer would be, to assign a library for each directory to extract the metadata ... View more

Hi Anne,   Probably the most expedient fix would simply be to make the metada match (case-wise).  For that, you could consider updating the physical metadata using these two macros (one to get the formats, the other to apply them (after an uppercase):   https://core.sasjs.io/mp__getformats_8sas.html https://core.sasjs.io/mp__applyformats_8sas.html /Allan ... View more

You could use this macro to create an empty dataset using the metadata definition:  https://core.sasjs.io/mm__createdataset_8sas.html   Then find some way to append the data into it.  Perhaps by using this macro to export: https://core.sasjs.io/mp__ds2csv_8sas.html   You could then use a tool such as https://datacontroller.io to do the import (drag & drop the CSV back into the new table definition).  Feel free to get in touch if you need assistance, we built the tool.   ... View more

to close this one off - this was the issue:  https://github.com/sasjs/core/issues/331 ... View more