Compile time of vanishingly small order can be compared with runtime execution of the datepart() function It really is a vanishingly small amount of time to compile a date or datetime constant.  Reading SAS logs to decypher a problem is far easier to validate when a macro var resolves to a date string rather than a number of days or seconds. That is why I always recommend using a date string and date constants, rather than a "number of days"   to represent a date in coding  (Use a very different approach for data) ... View more

Passing date strings like 01Jan2018 in macro variables can still be used to check a transaction date-time, and your test would also work faster/better without the datepart() function e.g. t1.txn_reqst_dt BETWEEN "&dateS:0:0:0"dt and "&dateE:23:59:59.99"dt Remember to use double quotes around macro vars you need expanded ... View more

http://support.sas.com/documentation/cdl/en/mcrolref/61885/HTML/default/tw3514-syscc-var.htm SYSCC is defined as end-of-job status, but appears to provides the max value (so far) of SYSERR during the job ... View more

Would it not be sufficient to test &SYSCC (or is it sysrc) ? ... View more

What if there is a syntax error in (SAS CODE here)? The code to send the email probably won't execute How are you able to read the log of the current session? ... View more

Upgrade your office ... View more

Sounds like a candidate for a data _null_ step to call execute a proc datasets that will change column names and install those descriptive labels ... View more

Looks like a candidate for special user-defined in/formats. That separates the definition of the "group" from the coding which is logically straightforward ..... Is this candidate one of the required group ..... If input( cause_death, user_informat. ) ; ... View more

Might be interesting to demonstrate IF there are decimal fractions of a second in the value DT1= Put dt1= datetime21.2 ; ... View more