Maybe convert the VOC entries for the programs to R pointers. The r pointer would point to a file with the original VOC entry for the program. Then in attribute 4 of the R pointer put a security subroutine which logs the calling details for each call etc. That way you can gain a picture of when a program is called and how often and by who and from where.....
-----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of McGowan, Ian Sent: Tuesday, 7 January 2014 1:08 p.m. To: U2-Users@listserver.u2ug.org Subject: [U2] Logging program execution in Unidata? We're looking into a major conversion late this year, which will involve checking out several thousand programs (mostly opens, reads or writes). Some programs are run many times a day, whereas some were throwaway and haven't been touched in years. It would be great to get some sense of which ones are active. We unfortunately don't have a wrapper program, wondering if anyone has run into this before - is it possible to somehow log when a program is executed in Unidata? Any magic triggers, directory flags or other audit flags that can get turned on? Any ideas gratefully received, Ian ----------------------------------------- IMPORTANT NOTICE: This message is intended only for the addressee and may contain confidential, privileged information. If you are not the intended recipient, you may not use, copy or disclose any information contained in the message. If you have received this message in error, please notify the sender by reply e-mail and delete the message. _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
