BookmarkSubscribeRSS Feed
GargS
Calcite | Level 5


The logs that are produced in CDI while working on a job, can still have warnings about numeric or character conversion or missing values generated. Has anyone come out with a way to have a log check to make sure that our logs are clean at the end of the day?

1 REPLY 1
Quentin
Super User

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.

sas-innovate-2024.png

Join us for SAS Innovate April 16-19 at the Aria in Las Vegas. Bring the team and save big with our group pricing for a limited time only.

Pre-conference courses and tutorials are filling up fast and are always a sellout. Register today to reserve your seat.

 

Register now!

New Learning Events in April

 

Join us for two new fee-based courses: Administrative Healthcare Data and SAS via Live Web Monday-Thursday, April 24-27 from 1:00 to 4:30 PM ET each day. And Administrative Healthcare Data and SAS: Hands-On Programming Workshop via Live Web on Friday, April 28 from 9:00 AM to 5:00 PM ET.

LEARN MORE

Discussion stats
  • 1 reply
  • 1083 views
  • 0 likes
  • 2 in conversation