If it was working a week ago then what has changed since then? Worth checking with your DB2 Administrator in case anything has changed on the database side. SAS Tech Support is your best option for progressing this. ... View more

Updating cells that contain a formula is always done dynamically while a workbook is loaded in Excel. The workbook file itself is a dead, inert object, and only the things you explicitly do to it (like loading data to a spreadsheet) will happen. If you want logic to happen while only SAS is active, you need to do all of it in SAS.   In my opinion, this kind of split processing is just a disaster waiting to happen. Move all the logic into SAS. Formulas or VBA code in Excel make sense only when no better tool is available. But you do have SAS, so make use of it. ... View more

Just sending ERROR messages without the surrounding code is useless (you can see how useless this is in many threads here with suboptimal questions). Send the whole log instead, or even better, send a link to the log.   I have created a framework where every individual batch job run creates a separate log file; a listing of job runs is kept, with links to the logs (they can be accessed by the web server); if the wrapper script (sasbatch) detects a non-zero return code from a SAS job, a notification is triggered. When I receive a notification, I call up the list of job runs, click on the failed job, and get the whole log. ... View more