If you are only interested in auditing the use of a program, have you considered implementing RACF PROGRAM protection (or the equivalent in your security system) for the program. Set the audit options of the PROGRAM profile to audit successful accesses. Then you can determine use by processing the appropriate SMF records. Or get control in the appropriate security system exit.
Regards, Bill "Jon Renton" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > Hello, > > I am looking for a way to prevent users calling certain load modules > directly. Instead I would like my module to get control. This module > can then perform certain tasks before passing control to the user > requested processing module. > > Here as a simple flow: > > - User calls module "A" > - My module "B" gets control instead (without the user noticing this) > - After internal processing "B" calls "A" > > Is there a way to achieve this using documented interfaces (or > otherwise)? > > Many thanks in advance > > Regards > Jon > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.432 / Virus Database: 268.17.12/654 - Release Date: 27.01.2007 > 17:02 > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
