Rejection CAN be Rewarding - comment by geethareddy

hi Carrie,
I wanted to ask the same question asked by AbeK but for different reason. We have a stats process owned by application dba and other teams ownership. Being a system dba, now a days i am noticing couple of important tables with SI and PI on it are not been refreshed for past 180 days (I have a sql to catch the tables that are not refreshing the stats for N number of days). 
We are on TASM 13.10, SLES10 system. I am thinking  to have an event in all states which can send a notification to the DBA on following criteria to catch the most critical tables in the system with missing stats OR not refreshing on regular basis.
 
1) Create a Period Event for 7 days a week. 
2) Under Notification section, under RunProgram have my sql to be run and send an email to DBA.
Do you think it is a good idea to make use of period events on stats perspective?
OR my 2nd thought is, have a filter and just create it under 'WarningOnly' mode and log the occurances if there is a huge difference in ESTIMATED and ACTUAL seocnds, then analyze and send the report to concern users on missing stats.
 
Appreciate your thoughts.