If I'm dealing with large logs, I run such jobs in batch mode, then log size doesn't matter hence no log clearing is necessary. That also frees up your user interface of choice to just concentrate on development work. ... View more

I ran your test program on M8 and got identical results to you.   I'd suggest opening a Tech Support track as they are more likely to know about maintenance level differences and any fixes. ... View more

IMHO PROC COMPARE is such a useful tool and is one of my most frequently used ones. It's invaluable for developers to check the impact of process changes, but also for administrators to confirm if data is identical across SAS environments.   It could definitely do with a bit of love though, as its reporting capabilities still seem to be stuck in pre-ODS days.   ... View more

Can you post a test program that reproduces the problem plus a screenshot of the PDF produced? We can run it in a later maintenance release to see if it behaves the same. ... View more

The usual place to start when investigating problems of this type is server logs. Since you have already worked with your platform administrator I'm guessing that's already happened. Opening a track with Tech Support is the next best option since more troubleshooting will be needed. ... View more

Very cunning! ... View more

If EG is running local SAS on your PC then there is already the CALL SOUND routine which you can try. You can even play a tune if you so wish 😊   Of course this isn't an option if EG uses remote SAS servers. ... View more

I'm wondering if there's some unprintable characters in the load data upsetting the layout of bulk load file. Maybe try bulk loading a small sample first. ... View more

What happens if you don't use the BULKLOAD option? Still the same errors? Also what version and maintenance level of SAS is this? ... View more

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: SASKiwi_0-1786581079707.png   ... 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: SASKiwi_0-1786074367691.png 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