On Tue, 20 Sep 2005 11:14:28 -0500, Adam Floro <[EMAIL PROTECTED]> wrote:
> >$HASP000 EXIT3 replaced > >OK so far. Yepper. So you have $REPEXIT working. > > > >OK......now here's the latest on trying to get this exit to work. I am >replacing Exit3 which is our jobclass/time checker. I created a new 'T' >jobclass in Exit3 which is currently active, then removed it from the >reassm/relink'd, did the $REPEXIT,EXIT3 command, got the $HASP000 message, >all ok so far. But, when I submit a job with class 'T', it goes through, >when it should not. So, now I'm stumped again. > What makes you think $REPEXIT didn't work? It is probably your code or your process. For example, if exit3 is in the LNKLST, did you remember to refresh/update LLA first? IPL with your updated EXIT3 in place to begin with and see if you get the same results from your test. If you do, $REPEXIT has nothing to do with it. Another way to verify the exit is loading something is to do a $DLOADMOD(EXIT5) before the $REPEXIT command and afterwards. You should see a different address even if you (re)load the same exit. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America and Farmers Insurance Group mailto: [EMAIL PROTECTED] Systems Programming expert at http://Search390.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
