About Kurt_Bremser

Kurt_Bremser

First of all, you should do such data cleaning immediately when the data is read into the SAS environment in the first place. You can define DATA step or SQL views (DATA preferred) that do the conversion, and use these in the MERGE.

Kurt_Bremser

And what is your question?

Kurt_Bremser

I prefer to have the log scan and the mail creation in a separate process. Otherwise, if a serious problem arises in the SAS program (e.g. out of memory exception), you‘ll never be notified. So I did the log scan in our sasbatch.sh with OS means (grep) and set an „artificial“ exit code, which would then make the scheduler do the alerts.

Kurt_Bremser

Run a ping from your on-premises server to the Oracle server, then do the same from AWS. Compare the results.

Kurt_Bremser

Let the scheduler handle this. I did it this way: Use a shell script to run your program. In the script, define the location of the log file. If the SAS program ends with a non-zero return code, stream the log file to standard output. The scheduler catches the output and includes it in the mail. I also kept a dataset recording all program runs having links to the respective logs; from this I built a website which allowed "live" viewing of the logs by simply refreshing in the browser.

Kurt_Bremser

Use 6,30 instead of 12,31 in the MDY function?

Kurt_Bremser

Maxim 30. : Analyze, Then Optimize. You must get a clear picture of the issue first. Run a diagnostic tool on the server while you execute your code (with OPTIONS STIMER for in-depth log analysis, of course). My favorite on AIX was topas, where I could see the detailed CPU load ( sys, user, wait), disk throughput, network activity, top processes all at once. You also see if there‘s paging activity when not enough physical memory is available for the processes, which is a serious performance killer. You should always use your fastest storage for WORK; unless there‘s a quota set (which any diligent admin will always do), any user can use it all. A local PC being faster than a server points to a serious mis-conception in the design of the server.

Kurt_Bremser

Please do not double-post. If a question ends up in a wrong community, we can move it.

Kurt_Bremser

Consider using the external command (mv on UNIX) to move the files. If the move happens within the same physical filesystem, mv will only move the directory entries, which is much faster.

Kurt_Bremser

Please provide the complete log of the export step, and also tell us which format is assigned to the datetime variable. If it is a custom format, do also supply the PROC FORMAT code.

Kurt_Bremser

Also look for the typical patterns of conversion NOTEs and NOTEs for missing values caused by erroneous calculations. But frankly, you must read the whole log regularly to catch more complex failures. Must. I mean it.

Kurt_Bremser

But from all your posts, I think a call to SAS technical support is in order.

Kurt_Bremser

It‘s always better to have blanks instead of tabs in your saved code. Tabs have different widths in different environments and also may depend on personal settings (e.g. I use 2), which leads to hilarious results when someone else views your code.

Kurt_Bremser

Two ways: use SQLOBS after the query, or set a default value before the query with a %LET.

Kurt_Bremser

Have your SAS admins inspect the spawner and workspace server logs. They will provide more detail.

Online Status	Offline
Date Last Visited	7 hours ago