@Patrick The log scan originated from a peculiar issue we encountered when we FTP'd files from the MVS mainframe. Sometimes the download would be incomplete, but without a standard FTP error message, instead we'd get a proprietary response (in the 600 range IIRC) from the FTP server which SAS would include in the log, but without issuing a WARNING or ERROR. It seemed to be that, although the previous job creating the file had successfully finished, MVS was still doing some "housekeeping" with its catalog when we tried to read the file. Anyway, in such a case I would rerun the SAS program and keep a counter for the repeats. If that exceeded a certain threshold, I would exit the script with a dedicated exit code so the operators immediately knew what to look for. In RL, we never got that far. Usually the issue was "fixed" on the MVS side with the first rerun. There might even have been a SAS option for this situation, but since I know quite a bit about UNIX shell scripting, that was the easier way to go. As of now, the issue is moot as we haven't been using FTP for a long time. The "mainframe" now runs as some kind of emulator on a Linux instance, so ssh is available OOTB. Which opened another can of worms, because the SAS implementation of SFTP is (was?) not reliable at all. Ask if you want to know more.   Once I had the log scan established, it was rather easy to extend it for other issues SAS would not catch on its own. ... View more

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. ... View more

And what is your question? ... View more

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. ... View more

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

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. ... View more

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

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

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. ... View more

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. ... View more

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. ... View more

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

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. ... View more

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