To be honest 1,500 lines of code isn't really the problem (I've seen much bigger programs) it's the quantity of data and how it's being processed which is causing the long run time.
You could set the errorcheck option to STRICT as documented here -> http://documentation.sas.com/?docsetId=lesysoptsref&docsetTarget=n074sx2hkq8dzpn1ptoydcmzfspt.htm&do...
or use the errorabend option but that will terminate the whole session leaving you no wiser as to what went wrong....
Ensure the 1500 lines of code has been: modularised, validated, and stress tested. Then an unexpected error will not happen. Modularising the code will allow you to block the whole process up into smaller chunks, allowing for conditionally checking at various points.
The question really is what does your documentation on the process say - you do have all the documentation e.g. functional design, testing, data structures etc.
Even more reason for modularistion and documentation. Each new block should be documented and validated before being moved into the production process.
Try these two options.
options errorabend nosyntaxcheck;
Don't miss out on SAS Innovate - Register now for the FREE Livestream!
Can't make it to Vegas? No problem! Watch our general sessions LIVE or on-demand starting April 17th. Hear from SAS execs, best-selling author Adam Grant, Hot Ones host Sean Evans, top tech journalist Kara Swisher, AI expert Cassie Kozyrkov, and the mind-blowing dance crew iLuminate! Plus, get access to over 20 breakout sessions.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.