I guess for any of these approaches, the question becomes "how tight does this have to be/how clever (or malicious) are your users?" I think there is probably a tradeoff between how hard it is to do and maintain versus how well it addresses the question in this paragraph.
We have not even mentioned the lightest weight approach, which might be sufficient for the average user: just change the PROCs to execute your program instead of the original target. A solution that fully addresses the question above will require modifications to LOAD, etc., etc., with all of the baggage that that implies. Perhaps some combination of approaches would be the best: a front-end CSECT for the programs you can re-link; some other approach for the programs you cannot. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jon Renton Sent: Monday, January 29, 2007 8:36 AM To: [email protected] Subject: AW: Getting control Charles, only problem with this approach is that the user can call the original module ($A) directly and avoid my code. This would be a major loophole! ---------------------------------------------------------------------- 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
