SAS Viya and SAS Grid Manager can actually work together, tackling the distributed processing of two different aspects of workloads.  SAS Grid manages the distribution of SAS jobs using advanced scheduling and resource management.  The CAS Server in SAS Viya manages the distribution of individual tasks within a job, splitting things up based on the way the data is or can be distributed.  Both are "divide and conquer" approaches, with SAS Viya being at a more granular level and SAS Grid being more at a gross level.  Note that since SAS Grid Manager is currently a 9.4-based offering, you'll need to make sure you're at 9.4M5 in order to take advantage of direct connectivity to a CAS Server running as part of a SAS Viya offering.  This same direct connectivity is also available from V9 clients like EG, Enterprise Miner, and stored processes.  SAS Viya offerings themselves do not include these clients.   While SAS Viya does support scheduling of jobs, SAS Viya offerings do not currently include LSF - something which is obviously available with V9-based SAS Grid Manager.   SAS Viya uses an entirely new installation/configuration paradigm.  You can watch this video to get a taste for the new process.   SAS Viya offerings can be installed on-premises, in a customer's public or private cloud of choice, or managed by SAS.  SAS does not need to host SAS Viya deployments, but will obviously do so if a customer prefers to outsource this management. ... View more

As you suspected, vdbadm is the userid (an internal metadata user) associated with the VDBService database.  It is not the database itself.  Considering the specific nature of your problem, I believe opening up a track with Tech Support to be in order. ... View more

There are some great resources/papers located in the Enterprise Management Integration Focus area on the support.sas.com Web site.  If you haven't already found them, check out the Environment Manager page under this focus area.  If you drill further into the Service Architecture Framework, you'll see additional information on the Data Mart.  Finally, if you go to the SAS Environment Manager User's Guide, you'll find a Data Mart Table Reference in the Appendixes. ... View more

It sounds like you're getting different behavior when you execute SAS code under a scheduler than when you run it interactively through SAS Studio.  There are a number of ways to schedule a SAS job.  Check out this blog for info.  It would be good to know if you could run this code directly as a batch script (in a .bat file), taking the scheduler out of the picture.   As to other forums you might consult, SAS Programming is a good option if you're just talking about submitting standard .sas code. ... View more

I'd also be interested in everyone's favorite reports under Report Center, so I encourage others to respond.   As to your question about reports showing zero observations, this is expected behavior in many situations.  I've clipped a related paragraph from the SAS Environment Manager's User's Guide below (italics added):   Note: Some reports might be blank, even though SAS Environment Manager is working properly. If data has not been generated that a report depends on, then the report will be blank. For example, a report that displays metadata activity will contain data only if there has been any activity on the SAS Metadata Server. If a report is blank, you can verify that the report is being generated properly by performing an activity that will generate data for the report. For example, to verify a metadata activity report, you could perform an action that would cause a metadata change, such as creating a user definition in metadata.   If you continue to experience blank reports which you feel should be populated, you should make sure you've got the SAS Environment Manager agent running on all your machines which host SAS server processes. ... View more

  When an AMO 7.13 or 7.14 user attempts to perform an action associated with "Create or Modify SAS Programs," AMO will check to ensure they have the "Advanced" role.  Prior to 7.13, no such checking occurs.   In order to be able to control this new capability in metadata, you need to update your Metadata Server machine with the version of "SAS Add-in for MS Office Server Data" that came with the order containing AMO 7.13 (or 7.14).  Once you've done so, you can also create custom roles (i.e., in addition to the default Advanced role) which specify this new capability. ... View more

It is technically possible to install SAS Viya on the same physical or virtual machines hosting a VA 7.3 environment; however, you need to take care that the respective environments do not have overlapping port numbers.  That said, to take full advantage of the performance improvements in SAS Viya, it is recommended that you install it on dedicated machines. ... View more

The system requirements for a Visual Analytics 8.1 deployment on top of Viya 3.2 can be found here.   Note that your use of VA 8.1 on Viya should be considered less of a "migration" and more of an installation of a new environment to which you can promote existing VA 7.3 reports (using Viya's promotion capability).  See this link for information on migrating content from 9.4 to Viya.     ... View more

In order to do this, you're really going to want to have a custom deployment plan that you can specify in the SAS Deployment Wizard.  You'll need to contact your SAS partner manager in order to get such a deployment plan which specifies only CM and RTDM.  Picking and choosing which products to install from a preexisting deployment plan (standard or custom) is not recommended as you can easily miss product dependencies.  Getting a custom deployment plan from SAS ensures that the right products/components will be included in your install. ... View more

I would verify that you have available disk space in the outfile location you're specifying.  You could also try redirecting to a different output location (with available space).  If these don't help, I believe you're best served taking this one to Tech Support. ... View more