SAS Viya Copilot for Code Assistance in SAS Data and AI Studio
Recent Library Articles
In this post, we’ll take a look at how SAS Viya Copilot for Code Assistance can help with some of those everyday tasks: understanding code, improving it, and making changes more confidently—all without leaving the SAS Data and AI Studio environment.
SAS V9.4. I'm stumped. I have a small file containing error messages from an IBM z/OS utility. I am reading a file that is the SYSPRINT messages from an IDCAMS DCOLLECT run. I have multiple types of records, and delete what I consider trash - for example, the first line. The records I want all begin with 'IDC11808I' but the record is spread across two lines. One field on the first line is a dataset name(Bad_VVR_DSN) and can be up to 44 characters long. After each dataset name is ' ON ' followed by a 6-character volser. I read the dataset name (Bad_VVR_DSN) and use an '@' to hold the record. I then do on_ix = index(Full_Rec,' ON '); I then have VOL_START = on_ix + 4. Followed by INPUT @(VOL_START) volser $char6.; But I'm not getting the value for volser off most of the records. I also only see half my records (that is, I know there are 8 problems and only see 4 of them). For example, in the file Lloyd_C_DCOLLECT_SYSPRINT.txt there is a pair of records for Bad_VVR_DSN = LLOYD.CWC.GLOBAL.CSI.BKUP.DATA and it shows in the SASPRINT. There is also a pair of lines for LLOYDC.CWC.GLOBAL.CSI.BKUP.INDEX but that is not in the output. The SAS code is in Lloyd_C_DCOLLECT_BADVVR.txt. I output the full record in the SASLOG. Why is the INPUT @VOL_START not resulting in a value for most of the records? Why am I only seeing half of my input records?
... View more
Imagine two organizations managing hundreds of models.
The first organization relies on emails, spreadsheets, and manual reminders to move models through development, validation, approval, and production.
The second organization uses structured workflows that automatically guide users through every step of the model lifecycle.
Which organization is more likely to maintain consistent governance, meet regulatory requirements, and reduce operational risk?
For most organizations, the answer is obvious.
Workflows are the backbone of model governance. They define how work moves through your organization, who performs each activity, and what conditions must be met before the next step can begin.
In SAS Model Risk Management (MRM), workflows help ensure that every model follows an approved governance process from initial registration through retirement.
Before administrators begin building or modifying workflows, it's important to understand the architecture that makes workflow-driven governance possible.
In this post, we'll explore the key components that power workflow-driven governance in SAS Model Risk Management and build the foundation you'll need for designing, managing, and troubleshooting workflows.
... View more
I am trying to create the equivalent of the below using sas-viya CLI and I am not sure how to achieve it (if it is possible at all):
EyalGonen_0-1788328546040.png
Specifically how to set the conopts parameter within the datasource option
Thanks!
... View more
Was playing around over the weekend and knocked together a SAS platformer game You can run it standalone, without SAS: https://dash.sasjs.io Or you can hook it up to Viya and compete against each other for high scores:
%let apploc=/Public/app/macro-dash; /* SAS Content location */
filename md url "https://github.com/sasjs/macro-dash/releases/latest/download/macro-dash-viya.sas";
%inc md;
Source:
https://github.com/sasjs/macro-dash
More info: https://sasapps.io/macro-dash
macro-dash.png
... View more