About bheinsius

bheinsius · ‎08-24-2023

That does the trick, thanks!

bheinsius · ‎08-24-2023

Hi, In SAS Studio, how can I programmatically detect if I have an active CAS session? I compared all macro variables and SAS options between the two situation but found nothing that indicates this. Thanks, Bart

bheinsius · ‎12-15-2022

So how do I join the webinar?

bheinsius · ‎08-08-2022

Hi Berry, To do this: 2) Is it possible to manipulate more specifically how long a table stays in memory? For example, if the data is not used for 3 weeks it should be dropped from memory. you can use the lifetime subparameter in the CasOut parameter, as in : I got this from @briankinnebrew 's post "Tired of deleting temporary CAS tables? Let CAS do it for you", found here. Regards, Bart

bheinsius · ‎08-05-2022

Hi Koen, This one tells how to do it: Viya administrators can now get personal with users' Caslibs By Gerry Nelson on SAS Users February 17, 2020 https://blogs.sas.com/content/sgf/2020/02/17/viya-administrators-personal-caslibs/ From there: With the (super user) role assumed, the administrator can execute the accessControl.accessPersonalCaslibs action and the subsequent table.caslibinfo action returns all caslibs including any personal caslibs that existed when the session started. Thanks! Bart

bheinsius · ‎08-05-2022

Hi Koen, Thanks for your reply. While that is an option I don't think this option is available for tables imported using the Viya interfaces or those loaded from SAS94 to CAS. Also it puts the responsibility for housekeeping with the users where we probably both know they are not so good at that 😉 A periodic restart of the CAS Server would do the job of course but that seems a bit rigorous. Cheers, Bart

bheinsius · ‎08-05-2022

Hi, On Viya 4, as CAS memory is a scarce resource, we want to periodically cleanup in-memory CASUSER tables that are older than x days. Since CASUSER is a Personal CASLIB, it is only accessible to the user who owns the CAS session. Is there a way to do this centrally? - Bart

bheinsius · ‎10-04-2021

Thanks, both the followRefrerrals option as narrowing the baseDN fix the problem for me.

bheinsius · ‎09-28-2021

Hi, For a Viya 3.5 deployment on Windows I configured the Identities Service LDAP connection to use port 636 (ldaps). It doesn't work, the identities log shows: Unprocessed Continuation Reference(s); remaining name 'DC=example,DC=org' On the internet I find that the solution to this problem is to use port 3269 instead. I did that for other deployments and it usually works, except that this specific customer doesn't expose port 3269. Is there a way to get this to work with port 636? - Bart

bheinsius · ‎06-28-2021

Hi, I have a SAS DI job with a Table Loader that loads data to a table in a library assigned with the META engine. I get this error: ERROR: You cannot create or delete datasets, views or indexes in this mode. Try the option METAOUT=DATA. Use Proc Metalib to create metadata for datasets. I tried adding the metaout=data option to the Library but that caused the library to fail to assign. Adding it as a table option in the Table Loader also does not work: ERROR 22-7: Invalid option name METAOUT. How can I get this working? Any help is appreciated. - Bart

bheinsius · ‎06-07-2021

Your curl command returns: curl: (7) couldn't connect to host where executing this with a connection to the original server returns HTTP/1.1 200 OK So indeed it seems like the F5 does not permit these methods, I will verify this with the F5 administrator, and let you know, thanks.

bheinsius · ‎06-04-2021

Hi, I just configured an 94M7 environment for a customer reverse proxy (F5) following instructions at https://documentation.sas.com/doc/en/bicdc/9.4/bimtag/p0sxhuco18v167n13dsmnrfqv7yy.htm I have done this many times before - with success - but this time I can't get it to work. Everything works well except for the SAS Content Server. Validating it from SAS Management Console gives an error: [6/4/21 11:21 PM] INFO: Starting simple validation for WebDAV server (level 1) - ping [6/4/21 11:21 PM] INFO: Ping successful! [6/4/21 11:21 PM] INFO: Starting extended validation for WebDAV server (level 1) - Making a connection [6/4/21 11:21 PM] INFO: Path: 'https://xxxxxxxxxxx:443/SASContentServer/repository/default/sasfolders/' [6/4/21 11:21 PM] SEVERE: Exception accessing https://xxxxxxxxxxxxxxxxx (Connection reset) I have not seen this error before. I can access the content server just fine from a web browser. No errors in SASContentServer log or SASServer1_1.log either. Also no hits on Google for this specific error. Any ideas? -Bart

bheinsius · ‎05-25-2021

Hi @klay_martens , Ik get the same error as you: {"errorCode":1008, "message":"A data error occurred that prevented the successful completion of the operation.", "details":["traceId: 06902c391b830125", "path: /SASLogon/oauth/clients"], "remediation":null, "links":[], "version":2, "httpStatusCode":500 } and I am also running on AWS. Can you share what you changed to make it work? - Bart

bheinsius · ‎04-05-2021

That is a good idea except that a -NOTE in my sasv9_usermods.cfg gives me errors when starting SAS. Can you show me an example?

bheinsius · ‎03-25-2021

Would adding the options in Lev1/sasv9.cfg instead to <SASHome>/SASFoundation/9.4/sasv9_local.cfg work for your purposes? I tried it out and it works. As it is unclear what the order or execution - and thus the order of precedence - of the files is, I cannot be sure this will always work but for now there are no options in <SASHome>/SASFoundation/9.4/sasv9_local.cfg that also exist in other configuration files so it works. Thanks.

Online Status	Offline
Date Last Visited	yesterday

Re: Programmatically detect an active CAS session?

Programmatically detect an active CAS session?

Re: What are the New Capabilities of SAS® Analytics Pro Advanced Progr...

Re: SAS Viya table scope

Re: Cleanup CASUSER tables

Re: Cleanup CASUSER tables

Cleanup CASUSER tables

Re: SAS Viya 3.5 Identities Service - LDAP port 636 gives Unprocessed ...

SAS Viya 3.5 Identities Service - LDAP port 636 gives Unprocessed Cont...

DI Studio Table Loader - try the option METAOUT=DATA

Azure Storage for SAS Architects

Re: SAS Viya 3.5 Deployment failed: The generated orchestration is not...

Re: Promotion Viya to Viya : Change folder location of report.

Re: Promotion Viya to Viya : Change folder location of report.

Re: Promotion Viya to Viya : Change folder location of report.

DI Studio Table Loader - try the option METAOUT=DATA

Re: SAS Viya table scope

Re: Cleanup CASUSER tables

Cleanup CASUSER tables

Re: SAS Viya 3.5 Identities Service - LDAP port 636 gives Unprocessed ...

Re: Programmatically detect an active CAS session?

Programmatically detect an active CAS session?

Re: What are the New Capabilities of SAS® Analytics Pro Advanced Progr...

Re: SAS Viya table scope

Re: Cleanup CASUSER tables

Re: Cleanup CASUSER tables

Cleanup CASUSER tables

Re: SAS Viya 3.5 Identities Service - LDAP port 636 gives Unprocessed ...

SAS Viya 3.5 Identities Service - LDAP port 636 gives Unprocessed Cont...

DI Studio Table Loader - try the option METAOUT=DATA

Re: SAS M7 Content Server validate gives SEVERE: Exception accessing h...

SAS M7 Content Server validate gives SEVERE: Exception accessing https...

Re: Full authentication is required to access this resource when tryin...

Re: SASCFGPATH in SAS 9.4 - order of execution?

Re: SASCFGPATH in SAS 9.4 - order of execution?

SAS Inner Circle Panel

SAS Global Forum 2019

SAS Innovate 2025

SUGA

SAS Global Forum 2016