Error: ERROR: The SERVER= option is required for establishing a connection through the SAS/ACCESS Interface to PC Files.   code :   proc sql; connect to pcfiles(path="&path/database/SQL_DB.accdb" dbpassword=sastest); select UserID, Income format=dollar16., State from connection to pcfiles (select top 10, UserID, Income, State from customer order by Income desc); disconnect from pcfiles; quit;   I am learning sas sql 1 essential , currently at lesson 7 , there is an activity s107a01.sas . I don't know the server ! Please help . ... View more

wrtwtetw ... View more

NEW SAS ® VIYA ® FEATURES   Into the Viya Verse See what’s new in under 10 minutes. David Weik walks through this month’s SAS Viya updates. Watch now   SAS Data Governance: Connected business glossary The business glossary in SAS Data Governance now does more than define terms. You can create term-to-term relationships, assign terms to additional asset types, use enhanced term attributes and import terms more easily. Terms are also managed as dedicated glossary objects while continuing to provide metadata for discovery and lineage, improving performance and scalability. Data stewards and analysts can see how business concepts connect to actual data assets. Explore the feature   SAS Visual Analytics: SAS Viya Copilot for report viewers (preview) Report viewers can now ask questions about a report in plain language using the SAS Viya Copilot pane in SAS Visual Analytics. Explore the data items assigned in a report, such as top-performing products or regional averages, and get answers grounded in the report’s data and the official SAS Visual Analytics documentation. That means fewer quick questions for report authors and faster answers for business users. Explore the feature   SAS Data and AI Studio: SAS Viya Copilot Code Assistance for R SAS Viya Copilot for Code Assistance now supports R alongside SAS and Python. Use natural language to generate, explain and refine R code directly in SAS Data and AI Studio, whether you are preparing data, building statistical models, troubleshooting code or writing documentation. Teams that work across SAS and open source languages can move faster without leaving one environment. Explore the feature   SAS Data and AI Studio: Markdown editor SAS Data and AI Studio now includes a native editor for viewing and editing Markdown (.md) files in SAS Server and SAS Content locations. A side-by-side view shows your raw edits next to a formatted preview, making it easy to document pipelines, code logic and project dependencies alongside your assets. Keeping documentation in the platform also helps new team members get up to speed faster without switching to an external text editor. Explore the feature   Browse all release notes Want to see what else is new? Explore the full list of updates at your own pace. Browse release notes   Use case SAS Visual Analytics: SAS Viya Copilot for report viewers (preview) Interpreting complex dashboards no longer requires hunting through dense charts or relying on data analysts for straightforward answers. The SAS Viya Copilot pane introduces a conversational, natural-language interface directly into the report-viewing experience. Instead of manually cross-filtering visuals or guessing how metrics were aggregated, report consumers can simply ask targeted business questions in plain English. They can identify top-performing products, check regional averages or clarify data origins and get immediate, context-aware answers grounded in the report’s underlying data and official SAS documentation.   Tip of the month Brought to you by David Weik Senior Systems Architect, SAS Quick tip: Did you know that SAS Viya Copilot in SAS Data and AI Studio can now help you write SAS, Python and R code? That’s right. All three languages can be used in a single workflow thanks to PROC PYTHON and PROC R, and SAS Viya Copilot can help you understand and extend code in any of them.   Try SAS Viya Copilot code assistance ... View more

Did you know it’s easier now to use agentic AI with SAS 9.4? We’ll show you why and reveal some best practices along the way.     Watch the Webinar   You will learn how: Agentic AI can help you as a SAS 9.4 developer or researcher. To connect agentic AI with SAS 9.4. To apply best practices for using agentic AI with SAS 9.4. The questions from the Q&A segment held at the end of the webinar are listed below and the slides from the webinar are attached.   1. How can we ensure that Claude Code cannot and will not access sensitive data, such as patient-level information? Would project-level hooks or rules in CLAUDE.md help? Rules in CLAUDE.md and similar instructions can help, but I consider those “soft limits.” They aren't a 100% guarantee. For highly sensitive data, I would make it impossible for the agent to access that data in the first place. For example, you can run VS Code and the AI agent under an account or service account that does not have permission to access sensitive project folders or databases. You can also use models hosted in a controlled environment, including private cloud environments or locally hosted models.   2. We have SAS compute servers on a grid. How do we integrate VS Code, Claude, and SASPy so jobs run on the SAS compute server? You can use VS Code as the interface, with an AI agent such as Claude Code or GitHub Copilot working within it, and SASPy to connect to your SAS environment. For server-based SAS installations, IOM is one of the most flexible connection methods and can connect to SAS Grid. Once SASPy is configured, the agent can use SASPy directly, through a wrapper, or through an MCP to submit SAS code and retrieve the results.   3. SASPy is free. Is the SAS license you mentioned also free if we already have SAS 9.4 running? SASPy itself is open source, so you don't need a separate license for SASPy. You do need a SAS license for the SAS server you're connecting to. If you already have a licensed SAS 9.4 environment, SASPy simply gives you a way to connect to and work with that existing SAS installation.   4. What if the SAS server doesn't have internet access? You still need some way for the AI agent to access an AI model. Depending on your environment, you can run an open-weight model locally or make an approved model available within a protected cloud environment. We have projects with this type of limitation, so not having general internet access isn't necessarily a blocker. You just need a way to connect to an AI model that your IT department approves.   5. Is Agentic AI embedded in SAS 9.4? No. With SAS 9.4, the AI agent operates outside SAS and needs a way to execute SAS code. You can do that directly through SAS batch execution or through SASPy. I generally prefer SASPy because AI agents are very good at working with Python, and SASPy gives them a straightforward way to submit SAS code and work with the results.   6. I use Copilot or Gemini to generate SAS code without a SAS connection, but I often see basic syntax errors. Does a live connection take care of these error-correction iterations? Giving the agent a live connection to SAS helps because it can write the SAS code, run it, look at the log, and iterate when something doesn't work. Without that connection, the agent can generate the code, but it can't actually test whether the code works. You should still review what it produces and make sure the results are correct.   7. I haven't fully understood how to connect SAS to AI. What resources can I use to explore this further? For SAS 9.4, SASPy is a good place to start. It's an open-source Python package that lets Python access SAS data and analytics capabilities. Depending on your environment, you can configure SASPy using SSH, IOM, or COM. You can then use SASPy directly or put a simpler wrapper or MCP around it so the AI agent has a more controlled way to interact with SAS. If you're working with SAS Viya, I recommend using the SAS Viya MCP.   8. Since Claude doesn't actually run SAS code itself, how can we make sure it produces valid SAS code and correctly handles things like macros and SAS behavior? You shouldn't assume that everything the AI generates is correct. That's one of the reasons I recommend giving the agent a way to actually execute SAS code. It can write the code, submit it to SAS, look at the log, and iterate when it encounters errors. You should still review the final code and results to make sure they're doing what you intended.   9. Can this be used with SAS Enterprise Guide and SAS 9.4? Yes. This approach can work with SAS 9.4 environments where you're using tools such as SAS Enterprise Guide or SAS Studio. The agent doesn't have to operate inside Enterprise Guide itself. It can connect to the underlying SAS environment through SASPy. For server-based SAS environments, IOM is one of the most flexible SASPy connection methods.   Recommended Resources Github link to SAS MCP Please see additional resources in the attached slide deck.   Want more tips? Be sure to subscribe to the Ask the Expert board to receive follow-up Q&A, slides and recordings from other SAS Ask the Expert webinars. ... View more

Updates are available for the SAS Private JRE.   Updates for Java 11: https://support.sas.com/downloads/browse.htm?fil=&cat=629 Updates for Java 21: https://support.sas.com/downloads/browse.htm?fil=&cat=1569 ... View more