Mark_sas Tracker

Re: Which SAS Viya version I can install on premise?

Mark_sas — Wed, 02 Jun 2021 13:26:26 GMT

As has been pointed out in the thread, SAS Viya 3.x is indeed supported for deployments on-premises (and in the cloud), just as SAS 9.x is.

The latest version of SAS Viya, colloquially referred to as "SAS Viya 4" and technically referred to by its continuous delivery release numbers [i.e., LTS 2020.1 (released in November 2020), LTS 2021.1 (May 2021), Stable 2020.1.x (monthly releases through April 2021), Stable 2021.1.1 (May 2021)] is currently available for public cloud deployment. As of LTS 2021.1, that includes Azure, AWS, and GCP. SAS is targeting delivery of an on-premises option based on OpenShift running on VMWare this summer.

Migrating from SAS® 9.4 to SAS® Viya®

Mark_sas — Thu, 23 Jul 2020 18:35:10 GMT

SAS® Viya® brings with it a wealth of new analytic and data management capabilities, as well as a resilient, scalable, and open architecture. Users of SAS® 9.4 need an easy path to migrate their workloads to SAS Viya in order to leverage these capabilities. In the 20-minute video and paper linked below, I cover options for adopting SAS Viya to complement, and in some cases replace, a SAS 9.4 environment. The options fall into three general categories: interoperability, content promotion, and replacement.

Video highlights

00:40 - Why move to SAS Viya?

02:49 - How SAS 9.4 clients can interoperate with SAS Viya analytic servers

09:48 - How to promote content like library definitions and SAS Visual Analytics reports from SAS 9.4 to SAS Viya

15:28 - Scenarios for replacing SAS 9.4 workloads with equivalent SAS Viya product support

Read the Paper

Related resources

A recipe for success in migrating to SAS Viya (community article)

SAS Viya Install Center (documentation)

Re: LSF time event not firing after job exit

Mark_sas — Mon, 27 Apr 2020 15:46:33 GMT

That's an interesting question - i.e., whether time events are honored after a job fails within a flow whose policy is set to continue running. I think you're going to want to engage Tech Support on this one as I'm not sure if you're getting expected behavior.

Re: Setting up Email alerts for SAS Admin in SAS Viya 3.5

Mark_sas — Tue, 14 Apr 2020 13:16:56 GMT

I'm not sure. If you're able to run other sas-admin commands in the same session, you should be able to run healthcheck. It wouldn't hurt to refresh your token by re-authenticating according to the procedure laid out in https://go.documentation.sas.com/?docsetId=calcli&docsetTarget=n1e2dehluji7jon1gk69yggc6i28.htm&docsetVersion=3.5&locale=en.

If you continue to have issues with just healthcheck, please contact Tech Support.

Re: Setting up Email alerts for SAS Admin in SAS Viya 3.5

Mark_sas — Fri, 03 Apr 2020 18:49:58 GMT

SAS Viya does not have a built-in email alerting mechanism for when services go down; however, you can use the sas-admin healthcheck CLI to periodically query service status and generate email when you detect any which are down. You'll find a good blog on healthcheck here.

Re: SAS Viya Grant permission to Custom Group

Mark_sas — Fri, 03 Apr 2020 17:53:38 GMT

Since you say "top-level content folder," you've obviously eliminated the inheritance angle that can get in the way. My next step would probably be to search the raw rules themselves (under Rules in SAS Environment Manager) to see if there are any other rules which are getting in the way. These rules are created behind the scenes when you set authorizations using the dialogs from the Content area. As you know, SAS Viya defaults to declining access, so even if you've set up Read access at the atomic folder level for a given group, there may be a conflicting rule that is denying them permission.

If that doesn't uncover the issue, and you're sure you're logging in as a userid in the custom group to test this, I think you'll want to engage Tech Support.

I'm sure you're already aware of the associated doc, but for the other readers' benefit, you can find an overview of SAS Viya general authorization here.

Re: Data Source for Availability Dashboard in SAS Environment Manager in SAS Viya 3.5.

Mark_sas — Tue, 24 Mar 2020 14:44:48 GMT

Unlike the reports available from the SAS Environment Manager dashboard, the availability grid itself (i.e., the matrix of traffic lit boxes for the machines, services, and instances in your environment) is not based on a data table you can query. However, you can get the same (actually better in some ways) information programmatically using the sas-admin healthcheck CLI. See more information in the SAS Viya 3.5 Administration: Monitoring guide here.

Re: Scheduled Jobs are Failed in SAS EM (SAS Viya) while user was logged off.

Mark_sas — Fri, 20 Mar 2020 14:56:06 GMT

Make sure you've followed the instructions under "Schedule a Job" in the SAS Viya 3.5 Administration: Jobs and Flows doc related to setting the "Run as" field appropriately. If you're still experiencing problems, you'll likely want to engage Tech Support.

Re: SAS Studio Tasks Global Repository

Mark_sas — Fri, 31 Jan 2020 16:35:14 GMT

SAS Studio tasks are not definable as metadata objects, so you can't set up authorization for these tasks using SAS Studio, SASMC or the Metadata Server. There is no user permission model built into SAS Studio to control access to tasks. As such, your only option is to control access to where you store the tasks. You can share tasks in segregated repositories or shared folders, and limit access to these repositories/folders using operating system permissions. You can read more about this here:

http://support.sas.com/software/products/sas-studio/faq/SASStudio_sharesnippets.htm

Re: SAS OLAP Cube Auditing

Mark_sas — Thu, 07 Nov 2019 20:39:12 GMT

I would check out what you can find in the OLAP Server log file itself. The rolling logs for this server should be located under your Configuration Directory at SASApp/OLAPServer/logs.

Re: How to schedule a Unix/Linux shell script with Process Manager ?

Mark_sas — Mon, 23 Sep 2019 19:30:22 GMT

As you say, the OEM'ed version doesn't support execution of non-SAS programs. You can either license SAS Grid Manager (as opposed to SAS Grid Manager for Platform) from SAS, which supports the execution of non-SAS programs through a SAS-developed Grid provider, or you can license the full LSF version separately.

Re: Report SAS BDN Terms metadata

Mark_sas — Fri, 23 Aug 2019 15:05:39 GMT

There's a section in the BDN User's Guide describing the procedure you can use to export terms to an XML file. See page 52 of https://support.sas.com/documentation/cdl/en/dmbdnug/69815/PDF/default/dmbdnug.pdf.

Re: SAS Platform GMS v8.01 - Java Vulnerability v1.6.0_11

Mark_sas — Mon, 29 Jul 2019 17:42:36 GMT

With the latest release of SAS Grid Manager which accompanies the 9.4M6 Platform maintenance release, Grid Management Services (GMS) was not updated to support the latest version of the Load Sharing Facility (LSF - the workload management component of Platform Suite for SAS). As a result, 9.4M6 users are directed to the redesigned SAS Grid Manager for Platform module in SAS Environment Manager, rather than the old SAS Management Console plug-in which relied on GMS.

An older version of GMS still ships with 9.4M6, but it is only intended to provide compatibility with users who remain at older versions of LSF.

Re: Add test cases for application health check

Mark_sas — Wed, 03 Jul 2019 17:48:05 GMT

The components you list are related to data access. Seems like you could accomplish this validation by submitting a corresponding SAS job you construct which includes statements to access these data sources. Such a job can be submitted to your SAS Grid using SASGSUB, and scheduled to run periodically if you want to continuously validate your environment.

Deployment Tester is a general-purpose utility to validate a SAS deployment, and extensible through writing OQ tests. But you may not want to go to that much trouble, including ensuring that the Deployment Tester infrastructure is installed on all machines you're trying to validate.

Re: Acknowledging alerts in Environment Manager

Mark_sas — Tue, 21 May 2019 19:47:17 GMT

The ACKNOWLEDGE button comes into play when you have an alert definition which involves an escalation scheme. For information on creating alerts, including escalation schemes, consult:

http://support.sas.com/documentation/cdl/en/evug/69029/HTML/default/viewer.htm#p18n3hxpsz255zn1432pf2s42cv3.htm

Note that if you have an escalation scheme in place for an alert, an icon will appear in the "Ack" column next to it, in addition to the ACKNOWLEDGE button being enabled when you've selected one or more such alerts.

Re: Register Oracle tables via SAS Environment Manager

Mark_sas — Thu, 09 May 2019 18:23:03 GMT

The doc should be right. Perhaps the person you chatted with at SGF was referring to SAS Viya's Environment Manager.

Re: Has anyone implemented SAS Workload Orchestrator in a Windows environment?

Mark_sas — Thu, 02 May 2019 17:58:07 GMT

I would first make sure you are up-to-date with the software. Coincidentally, SAS just updated its SAS Workload Orchestrator hot fix bundle yesterday (01may2019). This is available for download now, and addresses several issues as noted on the associated hot fix page here:

http://ftp.sas.com/techsup/download/hotfix/HF2/E3Y.html#E3Y002

Re: SAS Web APP Server Not restarting after applying Hotfix - BAd Gateway Error 502

Mark_sas — Wed, 27 Mar 2019 19:21:22 GMT

I believe this may take a bit more specific diagnosis using your Web App Server log and Tech Support.

Re: Upcoming SUGA Webinar on SAS Grid Manager: Tuesday, March 12

Mark_sas — Wed, 13 Mar 2019 21:06:36 GMT

That's correct. You should work with your SAS account representative in order to get a trial order containing the new SAS Grid Manager. You'll deploy this separately from your existing SAS Grid Manager for Platform installation.

Re: Scheduling Data Integration Studio jobs from SAS Management Console

Mark_sas — Fri, 08 Mar 2019 14:17:18 GMT

You may be able to get away with rerunning the SAS Deployment Wizard, and choosing to selectively configure products. Then choose Operating System Services Scheduling Server in the product dialog and configure. If you're still having trouble activating this scheduling server, please contact Technical Support.