On Wed, 28 May 2008 10:20:23 -0400, Sproull, George CTR DISA GS4B14 <[EMAIL PROTECTED]> wrote:
>Hi, > We run a simple MPF exit specified in MPFLST00 that sets a >couple of bits in the CTXT DSECT pointed to by R1 at entrance. We also >include COM='MN JOBNAMES,T' in COMMND00 to require that the IEF403I >message is produced at job startup (required by our job scheduler). >Everything worked fine until we upgraded from z/OS 1.7 to 1.9, at which >point an invocation of the exit would turn off the JOBNAMES switch and >the IEF403I message would stop. We could reset it manually, but the exit >would again turn it off. OK....so the CTXT DSECT in IEZVX100 (the only >DSECT in the code) must have changed and we are setting bits dealing >with JOBNAMES. I reassembled it, refreshed the link list, etc. and the >problem went away....good! However, trying to understand the problem, I >looked at the differences of the DSECT between z/OS 1.7 and >1.9 and there were indeed flags added dealing with JOBNAMES monitoring, >but the displacement within the control block of the bits we were >setting had not changed. So, being a short program, I compared the >reassembled load module with the 1999 load module that had been causing >the problem, and, except for differences in the load module headers >(assembler version, link date, etc), the code was EXACTLY THE SAME. What >am I missing? I know it is normal practice to reassemble exits with OS >upgrades, but I can't see how doing it in this case fixed the problem. >Is it more likely that reloading the module fixed a corrupted module in >core? > >Here is the entire source: > >STM R14,R12,12(R13) SAVE CALLERS REGS >BASR R12,0 ESTABLISH MODULE BASE >USING *,R12 REGISTER >L R5,0(R1) ESTABLISH ADDRESSABILITY >USING CTXT,R5 TO THE CTXT >OI CTXTRFB2,CTXTRDTM NO HARDCOPY/NO DISPLAY >OI CTXTERF3,CTXTESJL SUPPRESS FROM JOBLOG >OI CTXTERF3,CTXTNWTP SUPPRESS FROM WTP >LM R14,R12,12(R13) RESTORE CALLERS REGISTERS >BR R14 RETURN TO CALLER >IEZVX100 > >This is why I am coming to the gurus....Thanks. >George Sproull George, I doubt that this is a problem with your MPF exit or with the CTXT. We enhanced the MONITOR function so that you can get the messages produced without requiring that they be displayed on a console. This was to help our own automation product, but I suspect others benefit from this change too. It does change some things though... Take a look at the R9 pubs. Any questions, drop me a note at [EMAIL PROTECTED] W. Kevin Kelley IBM POK Lab - z/OS Core Technical Development ---------------------------------------------------------------------- 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
