This worked fine for me. I created a test PPTX in Powerpoint, saved it to a SAS server folder, ran the below program. I just double-clicked on the email attachment and the Powerpoint opened as I expected: filename mymail email "[email protected]" subject="PPTX Test" attach=("TestPPTX.pptx" content_type="application/pptx" ); data _null_; file mymail; put 'Hi Me,'; put 'This is a test.'; run; This is the test email:   ... View more

The usual way to add an email attachment that is for a specific application is to use the CONTENT_TYPE option. Try something like this: filename mymail email "[email protected]" subject="PPT Test" attach=("MyPPT.pptx" content_type="application/pptx"); data _null_; file mymail; put 'Hi Me,'; put 'This is a test.'; run; ... View more

It depends on what your Java frontend application is doing and where it is installed. If it is only, for example, installed on PCs and is running SAS jobs in batch (sas -sysin "MySASPgm.sas") on remote SAS servers then retrieving Excel and HTML file from the batch jobs, what Java version you use doesn't matter. All SAS sees are the batch program calls.   Where the Java version does matter is if it is part of the software stack installed on the SAS servers themselves.  ... View more

If you use SAS/ACCESS Interface to SAP HANA then this is the default data type in SAS for VARBINARY: if you haven't done so already then I'd suggest confirming that SAS is actually reading the binary key OK by comparing a few hex values in SAS with those in SAP. If they look good then as you say it must be how you are writing back to SAP that is the problem. I think you need to provide more details on how you are doing that. ... View more

Personally, I've found it more productive to use Google for SAS questions as it provides AI answers, SAS documentation links, SAS Support links, SAS Community links all in one go and with a much higher chance of finding relevant answers. That's the competition that the SAS Community faces.   ... View more

Given this is a SAS-supplied product, opening a track with SAS Tech Support is the best option. ... View more

If you can't reproduce the problem then I suggest you "park" it until it reappears 🙂  ... View more

Take a look at these two notes: PROC SORT: NOTE: The data set WORK.TMP has 6636340 observations and 110 variables.   PROC RANK: NOTE: There were 997665 observations read from the data set WORK.TMP.   I can only assume that the TMP data SORT processes is NOT the same as the TMP dataset RANK processes as the observation count doesn't match. Why would that be? Are we missing some processing between the SORT and the RANK? ... View more

@ed_hcf - Could the reason for the duplication be two different variables with the same variable label? You can check this by running PROC CONTENTS on shrdat.ea_rc_fc_metrics2 ... View more

@EyalGonen  - From what I understand, PureStorage also have a cloud-based solution that should also work with SAS Viya. AFAIK, it functions like a real-time backup and restore so doesn't involve any file replication at all. Perhaps you could ask SAS if they know of any Viya customers using this technology.    ... View more

FYI, we have implemented a SAS 9.4M8 Disaster Recovery solution using a data centre technology called PureStorage. When we failover to our DR data centre, PureStorage simply reinstates the required storage in it's last recorded state so the avoids the requirement for replication completely. As far as SAS is concerned PureStorage drives are just like any traditional storage so no special configuration is required. It works like a charm for us.  ... View more

This recent post should be able to answer some of your questions: https://communities.sas.com/t5/SAS-Communities-Library/Introducing-PROC-R-Part-3-Creating-and-Calling-R-Scripts/ta-p/990279/jump-to/first-unread-message  ... View more

As already mentioned, I would check the SAS licence file you are using to ensure it hasn't already expired. ... View more

Most likely your data has been growing so it no longer fits in your current MEMSIZE setting. Try increasing it to see if that fixes the problem. In my experience ODS is very resource intensive. If you don't need your Excel reports customised then using PROC EXPORT or the XLSX LIBNAME engine would work a lot faster with 50K rows. ... View more

Check with your IT folks to see if your Windows account has the right permissions to install software. Many organisations restrict this permission. Also you could right-click on SAS's setup.exe and try "Run as administrator" if you haven't done so already. ... View more