JuanS_OCS Tracker

Re: Clinical analysis: PROC PSMATCH (SAS/STAT or SAS/OR) results differ between SAS 9.4 and Viya

JuanS_OCS — Tue, 11 Aug 2026 15:07:17 GMT

Hi @sbxkoenk, Koen, indeed.

How do you manage what is on an acceptable level within a clinical trial analysis? Do you have any experience around it?

Thanks in advance!
Best regards, Juan

Re: Writing Python inside SAS 9.4

JuanS_OCS — Fri, 07 Aug 2026 11:02:06 GMT

https://communities.sas.com/t5/SAS-Innovate-Presentations/SAS-9-4-M10-Continuing-Support-and-Roadmap-in-the-Era-of-Viya/tac-p/991867#M298

🙂

Re: SAS 9.4 M10: Continuing Support and Roadmap in the Era of Viya

JuanS_OCS — Fri, 07 Aug 2026 11:01:13 GMT

Available in SAS 9.4 M9 as a hotfix from July!
https://sas.service-now.com/csm/en/the-python-procedure-is-available-for-sas-9-4m9-ts1m9?id=kb_article_view&sysparm_article=KB0046084

Do note that requires other hotfixes first and there are post-configuration steps!

Re: Accelerating Clinical Analytics: Your Path from SAS LSAF or SAS 9 to SAS Clinical Acceleration

JuanS_OCS — Fri, 07 Aug 2026 08:10:12 GMT

Hi @pritesh_sas ,

this is really a great presentation, thank you. I was not able to attend Innovate this year, so this is great.
Do you think it would be possible to share a link to the slide deck? It would be great!

Thank you in advance!
Best regards, Juan

Re: SAS 9.4 M8 WebAuthentication : SASServer2_1 Issue

JuanS_OCS — Sat, 18 Jul 2026 15:48:20 GMT

In addition, look at this piece:

org.apereo.cas.web.support.mgmr.DefaultCasCookieValueManager - Invalid cookie. Required remote address 10.158.237.138 does not match 10.158.237.136

Do you know what those are? It seems as may be one of the many causes why it’s not working, in CAS. Should I assume one is web and the other is your compute?

Re: SAS 9.4 M8 WebAuthentication : SASServer2_1 Issue

JuanS_OCS — Sat, 18 Jul 2026 15:43:25 GMT

Hi there,
It seems to me you got SSO working well in SASServer1_1 via IWA/Kerberos.
However: did you configure it as well what is needed in SASServer2_1, where SASStudio lives? And, did you configure SSO with IWA/Kerberos in your SAS Metadata and Object Spawner/Workspace and Pooled Workspace servers?
Mind:
You need to prioritize IWA via Kerberos rather than NTLM (maybe just remove NTLM)
Depending on your configuration if it’s GRID, SASStudio may launch 2 sas.exe sessions per SASStudio session: an “spawner” or “launcher” and your actual Workspace. Both need the SSO via Kerberos/IWA.
Pleas search for @StuartRogers entries about Kerberos and SSO in SAS 9.4 or the advanced authentication and security topics for 9.4 in SAS VLE site, they are priceless.

Re: SAS® 9.4 Shows "Invalid Physical Name for Library SASUSER" After Applying Microsoft Wi

JuanS_OCS — Tue, 14 Jul 2026 08:10:06 GMT

@mopacreb66 updating the -SASUSER and including %USERNAME% in the path should resolve the issue, regadless.

Considering that you are on a server, I am wondering: - if you updated the correct sasv9 and/or sasv9_usermods file(s), - and if you fully restarted your compute services. You can check if the change took effect by opening a SAS session and run a code such as %put _all_; and check the value path of SASUSER.

And, indeed, if the issue persists, as @Bart_SAS suggests, please open a case with SAS support.

Re: SAS® 9.4 Shows "Invalid Physical Name for Library SASUSER" After Applying Microsoft Wi

JuanS_OCS — Wed, 08 Jul 2026 08:01:56 GMT

Hi @Bart_SAS , thanks for sharing this, good one.

Considering Windows updates are normally forced and scheduled at corporate environments, will there be any official communication to all affected customers, to try to prevent this - or to support them resolve it?

Thank you in advance.
Best regards, Juan

Re: SAS interruption and problems with reinstallation

JuanS_OCS — Sun, 14 Jun 2026 13:20:12 GMT

This error can mea
n a lot of things when you look at what library failed exactly, in the details below. I have seen these often in my 25+ years.

I would check if the license is expired and if all system requirements are properly in place. If all is correct, indeed, SAS Tech Support will be your best guidance.

Good luck!

Re: Query: Recommended DNS ndots setting for SAS Viya 2025 upwards

JuanS_OCS — Tue, 09 Jun 2026 08:43:46 GMT

Hi @timmat ,

if it is true there is an hourly pattern, I would look at the cron / jobs and the logs.

If the times of the cron / jobs will match your pattern, the issue might be generated internally in SAS or the Kubernetes deployment. Else, it might be an external process or code creating the issue you are facing (backups or network maintenance?).

As well, if you are sure this is a DNS issue, you might want to look at the DNS logs. They should tell you exactly which requests, at that time, are giving errors, and from which IP they are coming from.

Re: How can SAS Web Application users be tracked on a SAS Linux platform?

JuanS_OCS — Thu, 09 Apr 2026 13:00:19 GMT

Hi there @bmsampath ,

what you are asking is quite extensive. One could literally write a book about those topics. I would initially like to point you to the SAS documentation (wondering which documents you found so far), else SAS Professional Services or a trusted technological partner. (And, as side topic, I would also highly encourage your company to upgrade from M6 to latest maintenance in M9 with the latest hotfixes and security patches).

I will try to address your questions but providing some perspective, which might not be what you can find on documentation.

The web applications provided by SAS are no different from other web applications that are built in Java. What you need to keep in mind is:

- Your web app servers are tomcat alike. And they serve basically J2EE applications.

- You have an apache load balancer.

- Authentication and URL re-directions will be mostly governed by the SAS Metadata in one way or another.

- As any java web application, Log4J (now v2) rules your logging level, what informs, where and the rolling of the logs, based on the java libraries you enable and at what level (INFO, WARN, ERROR, DEBUG, TRACE)

- One of the applications is the SAS Environment Manager, which acts like an in-house data collection of your SAS system (however should never be your main monitoring tool, since it depends on several SAS services to be healthy and running).

- You could enable the extended monitoring (the so called EMI framework, which includes ACM and APM, as shared by @SASKiwi ) for SAS Environment Manager. This is a collection of scripts which will extend the level of information of your logs, and will add reports (and Stored Processes reports) and services and metrics being collected. - if you enable this, you need to set some cleaning of your EMI database in postgres, to ensure your system won't collapse of the amount of data collected.

If you manage to understand those foundations, you can understand all you need towards monitoring and auditing your SAS system, specially your SAS Web Applications. I mean it. Any web administrator or security expert based on Java web apps should be able to follow up and provide advice.

Indeed, SAS 9 is not the same as SAS Viya. There are many differences and improvements in SAS Viya towards auditing and monitoring, and make IT standards even more visible. Listing those differences could take a while.

I would like to point you to:

SAS Intelligence Platform: Overview
SAS Intelligence Platform: System Administration Guide
SAS Intelligence Platform: Security Administration Guide
SAS Intelligence Platform: Middle-Tier Administration Guide

Re: SAS Grid Installation Query and Plan file generation query

JuanS_OCS — Tue, 13 Jan 2026 08:57:17 GMT

Hi @start4mzero ,

I am now a little confused by what you are proposing/intending to achieve, or I might not be understanding well.

To clarify my previous comment:

- while /home binaries could potentially be in NFS, not all under a single same /sashome folder. You still want different NFS filesystem per SAS layer (eg /sashome/meta, /sashome/comp & /sashome/web)

- NFS might be suitable, but depends a lot of your configuration. A SAS tested DFS is definetely more recommended.

https://communities.sas.com/t5/SAS-Communities-Library/Contemplating-shared-file-systems-for-SAS/ta-p/468263

https://support.sas.com/resources/papers/proceedings17/SAS0569-2017.pdf

- you always need to prepare a plan file, custom to your designed deployment. However, if you follow above, there should not be a lot to customize.

A last note, in terms of recommendations:

Not for Sharing SAS 9.4 Deployment Files Across Meta and Middle Tiers:

The section above mentioned using a shared file system to host SAS 9.4 deployment files (software and configuration) for the SAS 9.4 compute tier software

However, the SAS 9.4 meta and middle tiers follow a different availability paradigm. We prefer that each host for the meta and middle tiers have their own local SAS software and configuration files

And even more importantly, never direct the SAS 9.4 Deployment Wizard to install one tier's software and configuration into the same physical directories for a different tier. In that way lies madness.

Re: SAS Grid Installation Query and Plan file generation query

JuanS_OCS — Mon, 12 Jan 2026 13:27:04 GMT

Hi @start4mzero ,

these kind of decisions should not be done at deployment time, but during the architecture sessions.
There are many variables involved.

For example, the fact that you are using NFS, instead of an Distributed Shared File System (DFS) has many implications for the questions you are posting. How will NFS will handle it? Files/blocks locking? Performance? Limitations of NFS (based on version and platform used)?

In general, and just to answer to your questions, very generally - but please mind my previous comment(s):

1- 1 time shared binaries /sashome should be enough. In all tiers. However I have no clue how your NFS will behave with such dependency. MIght create serious issues when you reach Production workloads. I suggest thorough testing and validation, and risk management.

2- I don't expect, by default, differences in the plan file. But of course all depends on architectural decisions

Re: Latency numbers of On Prem SAS/ SAS Viya and On cloud SAS Viya on AWS

JuanS_OCS — Mon, 12 Jan 2026 11:22:28 GMT

Hi there,

in general terms, SAS indicates that all layers of a SAS environment must stay as close as possible, preferably in the same datacenter. Specifically to minimize network latency while increasing network throughput data transfers.

Of course connections can be done towards outside, or from outside. But then you need to deal with all the aspects related to latency: timeouts, slowness, performance degradation, loss of packages and noise, etc.

As such, you really want low latency numbers. As close as possible as being part of the same datacenter. Meaning, preferably within single digit milliseconds, 2 digits max (I'd say no much more than 20 ms).

A (more complete) answer from AI, which should be taken with salt and pepper, but overall I can agree with it:

For a SAS environment with external connections, good latency means low single-digit milliseconds (ms) for interactive tasks like Enterprise Guide, while high throughput (hundreds of MB/s) is crucial for large data moves; slow network links (VPNs, high-latency internet) can severely degrade performance, emphasizing the need for fast, direct connections, ideally <20ms for cloud/remote, and very low internal SAS Grid latency for coordination, with <100ms overall being desirable for responsive user experience.

Key Latency & Throughput Factors

User Experience (SAS EG/VA):

<20ms: Excellent for fast, responsive work over LAN/direct cloud links.

20-50ms (Cable/Fast Internet): Generally acceptable but noticeable lag for some actions.

50-100ms+ (DSL/VPNs): Can cause significant delays (5-10s) due to aggregated small requests, frustrating users.

SAS Grid/Viya (Internal Nodes):

Very Low Latency: Essential for node-to-node coordination (e.g., 1-5ms).

High Throughput: Critical for loading data into memory (e.g., 100+ MB/s per core).

Cross-Prem/Cloud Data Movement:

Network Speed (Bandwidth): High latency can severely limit throughput (e.g., only 500KB/s to 20MB/s over some cloud links).

Physical Distance: Major contributor to latency; keep SAS and data close.

What's "Good"?

Aim for Sub-20ms: When connecting from outside (e.g., laptops, remote offices), aim for <20ms latency to the SAS environment (e.g., via dedicated circuits, ExpressRoute, fast VPNs) for a snappy feel.

Measure Throughput: Ensure you have hundreds of MB/s available for data loads, not just low latency.

Isolate Workloads: Use dedicated network paths (VNETs, subnets) for SAS nodes to avoid contention and latency spikes from other traffic.

In summary, think beyond just latency: low latency provides responsiveness, but adequate network throughput is vital for moving large datasets efficiently. For external users, <20ms latency with high bandwidth (100s of MB/s) is the goal for a good experience

Re: SAS grid Architecture consideration

JuanS_OCS — Mon, 15 Dec 2025 12:45:19 GMT

I think this is a tricky question. With NFS you will always hit some important limitation (google it).

Also, NFS has different limitations depending on the version of the protocol, the implementation, and the infrastructure/cloud.

Another reason why makes it tricky.

Normally, for Grid data or Grid SASWORK, I would rather use a proper Distributed Shared File System, which will face less limitations and risks, on top of higher performance. But, of course, those tend to be expensive solutions for storage.

Do you need SASWORK on shared storage, meaning, will your programs include checkpoints, so your programs can resume from defined points. If you don't I would strongly suggest to run away from the option to put SASWORK/UTILLOC in a shared storage. Local makes more sense.

And if you do need it, and you don't have a DFS available, then try to find your NFS options with your infra team, and try to run enough tests and stress tests, to ensure your Production workloads will go as you expect.

Re: Single machine SAS 9.4 Deployments

JuanS_OCS — Sun, 06 Jul 2025 19:02:54 GMT

The option is about the sizes of the Java Virtual Machines, as described in the MidTier admin guide, fine turning chapter.

Re: ERROR: Error retrieving DatabaseMetaData: java.sql.SQLFeatureNotSupportedException: getTypeInfo

JuanS_OCS — Thu, 19 Jun 2025 20:15:49 GMT

Excellent, thanks! I am planning on testing all the options and figure out the differences, especially in basic performance 😉 I am curious about your progress too!

Re: ERROR: Error retrieving DatabaseMetaData: java.sql.SQLFeatureNotSupportedException: getTypeInfo

JuanS_OCS — Thu, 19 Jun 2025 15:36:17 GMT

FYI, I see it is resolved with the latest version 1.3.1.0

83         libname x JDBC driverclass="org.duckdb.DuckDBDriver" URL="jdbc:duckdb::memory:"
83       ! classpath="/data-drivers/jdbc/duckdb_jdbc-1.3.1.0.jar";
NOTE: Libref X was successfully assigned as follows: 
      Engine:        JDBC 
      Physical Name: jdbc:duckdb::memory:
84         *libname x JDBC driverclass="org.duckdb.DuckDBDriver" URL="jdbc:duckdb::memory:"
84       ! classpath="/data/duckdb_jdbc-1.3.1.0.jar";

Re: The Quack is Back: SAS/ACCESS Meets DuckDB

JuanS_OCS — Thu, 19 Jun 2025 13:30:11 GMT

Great article @jarno , thanks!

Any experiences in SAS 9.4? And with multi-database support (https://duckdb.org/2024/01/26/multi-database-support-in-duckdb.html) queried from SAS?

Re: implementation of SSO for SAS Fat clients SAS EG, SAS DI Studio & SMC

JuanS_OCS — Mon, 16 Jun 2025 11:02:18 GMT

Hi,

yes, you will need SPNs and a UPN, and to enable (contrained) Keberos delegation.

Again, it is all well documented by SAS: https://documentation.sas.com/doc/en/bicdc/9.4/bisecag/n1d1zo1jsf2o0en1ehu4c4simfky.htm

If what you need is an overview, you can find a nice one provided by @PaulHomes here: https://platformadmin.com/blogs/paul/2015/01/iwa-sas-94m2-linux/

It is based on an old maintenance (2), but I am sure that, by reading the documentation provided by SAS, you can make the adjustments required for your actual SAS environment.

Kind regards,

Juan