SAS Viya Copilot Explained: Building Machine Learning Pipelines in Minutes, Not Hours
Recent Library Articles
SAS Viya Copilot is a set of software as a service (SaaS) features and capabilities that use large language models (LLMs) to provide users with a more intuitive and accessible way to work with SAS Viya offerings. SAS Viya Copilot is for developers, data scientists, citizen data scientists, and business analysts who are writing code, analyzing data, building machine learning model pipelines, and doing more across the data and AI life cycle.
Already a SAS Viya user? Then you know you’ve got a wealth of capabilities at your fingertips. We’ll explore those together, giving you access to all the insights you’ll need. Join us on December 10 at 11 a.m. ET.
CONCERN: PROC SQL DESCRIBE should correctly list the formats applied to the columns in the queried table. However, if a format is applied to one or more columns in the table, any format name that exceeds 8 characters in length is truncated to 8 characters in the table definition that is written to the SAS log. RESOLUTION: PROC SQL DESCRIBE TABLE should displays the full format name rather than truncating them to 8 characters. Change PROC SQL so that full format names are displayed. proc format;
value TellMeIfItWorks
1 = 'Yes'
2 = 'No'
3 = 'Maybe';
run;
data LONGFMTS;
length a b c 8.;
format a roman8. b comma12.2 c TellMeIfItWorks.;
a = 1;
b = 2;
c = 3;
run;
proc sql;
describe table work.longfmts;
quit;
* work around;
%let tellmeabout = LONGFMTS;
data _null_;
set sashelp.vcolumn end=eof;
where libname = 'WORK' and upcase(memname) = upcase("&tellmeabout");
if _n_ = 1 then
put "WORK.&tellmeabout." / "(";
comma = ifc(eof, '', ',');
if format = '' then
put ' ' name type comma;
else
put ' ' name type format= comma;
if eof then
put ")";
run;
... View more
Hi Experts, I recently created a new SAS Workspace Server (SASApp2) using the SAS Deployment Wizard. The workspace was created successfully and validation in SAS Management Console (SMC) is successful. However, when I try to access the new workspace through SAS Studio, I receive the following error: "The application could not log on to the server 'SASengineserver.domain.com:8592'. No server is available at that port on that machine." Environment details: Metadata & Mid-tier Server: SASMetamid.domain.com Application Server: SASengineserver.domain.com SASApp: Working fine SASApp2: Not working through SAS Studio Could you please help me understand what could be causing this issue and what configurations I should verify? Thanks in advance for your support. Regards, Srinivas
... View more
I, To show a data decreasing or increasing, I try to put an arrow on a chart on visual analytics.
But in text, ican only put Measure, not text. There is someone who can help me please.
... View more
Hello SAS Community, I’d like to introduce MCP4SAS, a project I’ve been developing to connect AI assistants with SAS through the Model Context Protocol (MCP). MCP4SAS provides a Perl-based MCP server and command-line runner backed by SASPy. It helps an AI assistant submit SAS programs, inspect execution logs, retrieve results, and revise code based on actual SAS errors and warnings. It supports connections to: SAS OnDemand for Academics (SAS ODA) Local Windows SAS, using SASPy IOM or COM Local Linux SAS, using SASPy STDIO Features include persistent sessions for reusing WORK datasets and macro state, HTML output retrieval, file transfers, macro dependency handling, and execution diagnostics. You can also use the runner directly from Perl/Bash without an AI assistant. For example, after installation and configuration, this command runs a descriptive analysis through SAS ODA: perl run_sas_codes_or_files_in_ODA.pl \
--saspy-cfgname oda \
--code 'proc means data=sashelp.class n mean std;
var height weight;
run;' \
--output-prefix SAS_Output_RandID_class_demo \
--run-timeout-seconds 120 For local SAS, the option --dir4local_sas_home supplies a working directory represented by ~ for supported file operations and quoted SAS paths. ODA and local Windows execution have been tested with real SAS sessions. Linux configuration and connection-selection logic have passed offline tests; live Linux SAS validation is still needed. The GitHub homepage includes installation instructions and examples for all three targets. An ODA account or an installed, licensed local SAS system is required. I’d welcome feedback, especially from people interested in SAS macro debugging, statistical analysis, and AI-assisted SAS workflows. Reports from users with local Linux SAS would be particularly helpful!
... View more
anyone knows the one below?
ERROR: Windows error code: 21 in hc_disk_normal_read for
E:\sastemp\_TD16080_LAPTOP-LF4NQTV2_\sastmp-000000005.sas7butl
Work with pc/sas, ever session to restart sas, get this and need reboot sas.
... View more