What you want can be accomplished. In the 90's, when we had jobs stopping mid process, we made them not kick off future jobs and email us with all the particulars when the process stopped. Most of the methods we used were found in User group Papers and SAS documents. I bet you can find what you need if you Google it. We used stop and notify methods because we had jobs running on the mainframe downloading SAS data to UNIX. If any part of the process failed, we had to stop the remaining processes. Unfortunately I do not have copies of the coding. The best way to begin is by changing your code to write your logs to datasets. Then insert code at the end of each process step, that checks the dictionary tables to verify that the previious step created a dataset with more than zero obs. After that we created a macro variable that held a "stop" or "go" value. If the macro variable was a go, we processed the next step. %put statements wrote the stop and go values to the log dataset. If the macro was a stop, we emailed ourselves a note saying that the job did not run to normal completion.
... View more
