How about some sort of scheme in which you alias your program as A, and re-name program A to $A? So when the user runs A, s/he gets your program, which then links to the old A?
In this approach or the one suggested by John, you could turn the function on and off with a system variable or a parm file. Your program would still get called every time, but it would just exit to the old A if you did not desire your added functionality. In my scheme, you *might* be able to turn it on and off by juggling link pack or steplibs, but that sounds overly-complicated to me. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jon Renton Sent: Monday, January 29, 2007 6:40 AM To: [email protected] Subject: AW: Getting control John, a "relink" is not an option as I would like to enable/disable my function dynamically (at least from IPL to IPL) and some of the load modules are third party software - ie. I do not want to change these! > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Jon Renton > Sent: Monday, January 29, 2007 7:23 AM > To: [email protected] > Subject: Getting control > > > 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)? ---------------------------------------------------------------------- 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
