I don't have CDI, but I'm a big fan of log scanning. Assuming CDI is generating SAS code (like DI studio or EG or many other SAS clients), I would look for a way (perhaps with a "custom code" element) to invoke proc printto at the beginning of your job/session to write the log file to somewhere you can access. Then at the end of the job you can scan the log for whatever you want. That's how I approach it with DI studio, EG, and web reporting. I'm a fan of log scanning macros. My favorite approach is from this paper:
http://www.lexjansen.com/nesug/nesug01/cc/cc4008.pdf
I blogged about log scanning in the stored process setting here:
http://bi-notes.com/2012/07/stored-process-ignore-log-your-own-peril/
HTH,
--Q.
BASUG is hosting
free webinars Next up:
Jane Eslinger presenting PROC REPORT and the ODS EXCEL destination on Mar 27 at noon ET. Register now at the Boston Area SAS Users Group event page:
https://www.basug.org/events.