Re: SMF SWITCHING WITH IEFU29
Thanks again to everyone who assisted with this, particularly Mark and Peter. While its true that we could name the exit anything, the IBM supplied sample jobs use IEFU29 thereby duplicating the dummy name. It would be interesting, if I wasn't up to my handsome nose in DB2 v8, to research the history of the two IEFU29's. Why should be a good story. This situation would be simpler, I think, if IEFU29 was only the sample version. The worst, at least that I can think of on one cup of coffee, thing that happens is the DUMPXY started task jcl errors out. That at least is visible and obvious to fix. I will pass Mark's suggestion regarding the SYS1.LPALIB fix on to the ADCD guys as something they may want to do on their distributed version to make we developer's life a little less complex. Its a pretty common requirement to automatically capture SMF data. I suppose they could remove the dummy as well. Thanks again for the great assistance. Edward Long -- 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
Re: SMF SWITCHING WITH IEFU29
One thing that I did not see mentioned: There is no requirement whatsoever that you use an exit routine named IEFU29 for the exit. So if you called it FRED (apologies to anyone named Fred out there) and had suitable statements in your IPL-time PROGxx, the system would use FRED and would not even try to locate a module named IEFU29. This approach is followed for all the dynamic SMF exits. Mark Zelden's append was fully correct with respect to how to get USER.LPALIB first if that is what you feel you must do. Peter Relson z/OS Core Technology Design -- 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
Re: SMF SWITCHING WITH IEFU29
On Sun, 28 Oct 2007 20:03:48 -0700, Ed Long [EMAIL PROTECTED] wrote: Hi everyone. Sorry for the delay in replying to the several most helpful suggestions for which I am most grateful. Root cause identified and solved. I had in fact assembled and linked the exit correctly into user.lpalib. USER.LPALIB is #1 in the LPALSTXX concatenation. LPALSTXX (actually LPALSTDB) is being selected at IPL time. SYS1.LPALIB is in fact referenced about 2/3's of the way down in the LPALSTXX member. BUT, at least on z/OS 1.5, a copy of SYS1.LPALIB is always, and under the covers, prepended to the LPALST so that it gets selected first even if its included in the list. Been that way forever (since LPALSTxx existed). As a result, the dummy IEEU29 was being used. It, of course, does nothing, and does it quietly. The way you get USER.LPALIB first is to specify it in SYSLIB LPALIB in your PROGxx member. Then you must explicitly include SYS1.LPALIB in your LPALSTxx member (I always put it first there). So, I renamed the bogus IEEU29 to IEEU29BG (for bogus), reipled and away go my SMF datasets. You can have used PROGxx to delete / re-add the exit from the proper library without IPLing... regardless of LPA list order. You can load it from the library you want in PROGxx at IPL time - even if you don't use the SYSLIB override I wrote about above. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ 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
Re: SMF SWITCHING WITH IEFU29
Hi everyone. Sorry for the delay in replying to the several most helpful suggestions for which I am most grateful. Root cause identified and solved. I had in fact assembled and linked the exit correctly into user.lpalib. USER.LPALIB is #1 in the LPALSTXX concatenation. LPALSTXX (actually LPALSTDB) is being selected at IPL time. SYS1.LPALIB is in fact referenced about 2/3's of the way down in the LPALSTXX member. BUT, at least on z/OS 1.5, a copy of SYS1.LPALIB is always, and under the covers, prepended to the LPALST so that it gets selected first even if its included in the list. As a result, the dummy IEEU29 was being used. It, of course, does nothing, and does it quietly. So, I renamed the bogus IEEU29 to IEEU29BG (for bogus), reipled and away go my SMF datasets. The default IEEU29 appears to also have a hard restriction on DSN length of 4 characters after the period. In response to Mark's query, MULCFUNC -- DEFAULT MEMLIMIT(0M) -- DEFAULT DDCONS(YES) -- DEFAULT LASTDS(MSG) -- DEFAULT NOBUFFS(MSG) -- DEFAULT SYNCVAL(00) -- DEFAULT INTVAL(30) -- DEFAULT DUMPABND(RETRY) -- DEFAULT SUBSYS(STC,NOTYPE(19,69,99,110)) -- SYS SUBSYS(STC,NODETAIL) -- SYS SUBSYS(STC,INTERVAL(SMF)) -- PARMLIB SUBSYS(STC,EXITS(IEFUSO)) -- PARMLIB SUBSYS(STC,EXITS(IEFUJP)) -- PARMLIB SUBSYS(STC,EXITS(IEFU84)) -- PARMLIB SUBSYS(STC,EXITS(IEFU83)) -- PARMLIB SUBSYS(STC,EXITS(IEFU29)) -- PARMLIB SID(SYS1) -- PARMLIB SYS(NOINTERVAL) -- DEFAULT SYS(NODETAIL) -- PARMLIB SYS(EXITS(IEFU29)) -- PARMLIB SYS(EXITS(IEFUJI)) -- PARMLIB SYS(EXITS(IEFUSI)) -- PARMLIB SYS(EXITS(IEFACTRT)) -- PARMLIB SYS(EXITS(IEFU84)) -- PARMLIB SYS(EXITS(IEFU83)) -- PARMLIB SYS(NOTYPE(19,69,99,110)) -- PARMLIB LISTDSN -- PARMLIB JWT(1800) -- PARMLIB STATUS(01) -- PARMLIB MAXDORM(3000) -- PARMLIB REC(PERM) -- PARMLIB NOPROMPT -- PARMLIB DSNAME(SYS1.MN16) -- PARMLIB DSNAME(SYS1.MN15) -- PARMLIB DSNAME(SYS1.MN14) -- PARMLIB DSNAME(SYS1.MN13) -- PARMLIB DSNAME(SYS1.MN12) -- PARMLIB DSNAME(SYS1.MN11) -- PARMLIB ACTIVE -- PARMLIB SUBPARM(SVAA(250,2,5,7)) -- PARMLIB Ed Long [EMAIL PROTECTED] wrote: Hi everyone. I have finished upgrading one of my 7060's to the latest, and last version of z/OS 1.5. The one remaining, nagging, issue it has, is the DUMPXY exit aka IEFU29 doesn't seem to execute when I issue a i smf command. The previous system it worked fine. Load modules are same length;both are in USER.LPALIB. I am certain its something I've done, but darned if I know what it is. Any and all suggestions most appreciated. As you can see from the following, the exit is being seen, and loaded properly, its not being heard however. CSV550I 18.21.37 LPA DISPLAY 581 FLAGS MODULE ENTRY PT LOAD PT LENGTH DIAG P IEFU29 8507FA68 0507FA68 0020 08C1C860 CSV461I 18.21.37 PROG,EXIT DISPLAY 584 EXIT MODULE STATE MODULE STATE MODULE STATE SYS.IEFU29 IEFU29 A CSV461I 18.21.37 PROG,EXIT DISPLAY 585 EXIT MODULE STATE MODULE STATE MODULE STATE SYSSTC.IEFU29 IEFU29 A Edward Long Edward Long -- 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
Re: SMF SWITCHING WITH IEFU29
On Oct 28, 2007, at 10:03 PM, Ed Long wrote: Hi everyone. Sorry for the delay in replying to the several most helpful suggestions for which I am most grateful. Root cause identified and solved. I had in fact assembled and linked the exit correctly into user.lpalib. USER.LPALIB is #1 in the LPALSTXX concatenation. LPALSTXX (actually LPALSTDB) is being selected at IPL time. SYS1.LPALIB is in fact referenced about 2/3's of the way down in the LPALSTXX member. BUT, at least on z/OS 1.5, a copy of SYS1.LPALIB is always, and under the covers, prepended to the LPALST so that it gets selected first even if its included in the list. As a result, the dummy IEEU29 was being used. It, of course, does nothing, and does it quietly. So, I renamed the bogus IEEU29 to IEEU29BG (for bogus), reipled and away go my SMF datasets. The default IEEU29 appears to also have a hard restriction on DSN length of 4 characters after the period. Ed: Check to see which version of IEFU29 you have. There was at least one bug I found in the CBIPO version and it was at least 5 years before we hit the bug. I don't have the source for it, but IIRC I found a really old reference to the bug on IBMLINK. Not sure how to tell you if you have the most recent version but look at the assembled output and see if there is a change that occurred in or before 2000 +- 5 years (probably -5 years). IIRC it was a small change. If you have the most recent version take a look at CBTTAPE.ORG for a newer version. Ed -- 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
Re: SMF SWITCHING WITH IEFU29
Ed Long wrote: The one remaining, nagging, issue it has, is the DUMPXY exit aka IEFU29 doesn't seem to execute when I issue a i smf command. The previous system it worked fine. Load modules are same length;both are in USER.LPALIB. CSV550I 18.21.37 LPA DISPLAY 581 FLAGS MODULE ENTRY PT LOAD PT LENGTH DIAG P IEFU29 8507FA68 0507FA68 0020 08C1C860 Are you sure the same lenght? Check your display of LENGTH above. The length of x'20' usually means you're picking up a default IBM supplied IEFU29 in SYS1.LPALIB. You can use ISRDDN in ISPF and search for IEFU29. Probably not in USER.LPALIB. HTH! Groete / Greetings Elardus Engelbrecht -- 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
Re: SMF SWITCHING WITH IEFU29
- Original Message From: Ed Long [EMAIL PROTECTED] CSV550I 18.21.37 LPA DISPLAY 581 FLAGS MODULE ENTRY PT LOAD PT LENGTH DIAG P IEFU29 8507FA68 0507FA68 0020 08C1C860 As Elardus already said a length of 20 could mean you're picking up the dummy LMOD in LPALIB delivered with the SystemPac/ServerPac. You should be able to dynamically delete the dummy IEFU29 and then add your own from USER.LPALIB using the SETPROG EXIT command. Look at the Command Reference or in the ibm-main archive to see how to do it. Walter Marguccio z/OS Systems Programmer Munich - Germany ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ -- 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
Re: SMF SWITCHING WITH IEFU29
On Mon, 22 Oct 2007 16:03:59 -0700, Ed Long [EMAIL PROTECTED] wrote: Hi everyone. I have finished upgrading one of my 7060's to the latest, and last version of z/OS 1.5. The one remaining, nagging, issue it has, is the DUMPXY exit aka IEFU29 doesn't seem to execute when I issue a i smf command. The previous system it worked fine. Load modules are same length;both are in USER.LPALIB. I am certain its something I've done, but darned if I know what it is. Any and all suggestions most appreciated. As you can see from the following, the exit is being seen, and loaded properly, its not being heard however. CSV550I 18.21.37 LPA DISPLAY 581 FLAGS MODULE ENTRY PT LOAD PT LENGTH DIAG P IEFU29 8507FA68 0507FA68 0020 08C1C860 CSV461I 18.21.37 PROG,EXIT DISPLAY 584 EXIT MODULE STATE MODULE STATE MODULE STATE SYS.IEFU29 IEFU29 A CSV461I 18.21.37 PROG,EXIT DISPLAY 585 EXIT MODULE STATE MODULE STATE MODULE STATE SYSSTC.IEFU29 IEFU29 A Please post the output of D SMF,O from this system. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ 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
Re: SMF SWITCHING WITH IEFU29
On Tue, 23 Oct 2007 03:25:15 -0500, Elardus Engelbrecht [EMAIL PROTECTED] wrote: CSV550I 18.21.37 LPA DISPLAY 581 FLAGS MODULE ENTRY PT LOAD PT LENGTH DIAG P IEFU29 8507FA68 0507FA68 0020 08C1C860 Are you sure the same lenght? Check your display of LENGTH above. The length of x'20' usually means you're picking up a default IBM supplied IEFU29 in SYS1.LPALIB. Good catch. Didn't notice that before I replied.I agree, but Ed did say the modules were the same length as before (although maybe he was looking at the library and not the output of the D PROG command. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ 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
SMF SWITCHING WITH IEFU29
Hi everyone. I have finished upgrading one of my 7060's to the latest, and last version of z/OS 1.5. The one remaining, nagging, issue it has, is the DUMPXY exit aka IEFU29 doesn't seem to execute when I issue a i smf command. The previous system it worked fine. Load modules are same length;both are in USER.LPALIB. I am certain its something I've done, but darned if I know what it is. Any and all suggestions most appreciated. As you can see from the following, the exit is being seen, and loaded properly, its not being heard however. CSV550I 18.21.37 LPA DISPLAY 581 FLAGS MODULE ENTRY PT LOAD PT LENGTH DIAG P IEFU29 8507FA68 0507FA68 0020 08C1C860 CSV461I 18.21.37 PROG,EXIT DISPLAY 584 EXIT MODULE STATE MODULE STATE MODULE STATE SYS.IEFU29 IEFU29 A CSV461I 18.21.37 PROG,EXIT DISPLAY 585 EXIT MODULE STATE MODULE STATE MODULE STATE SYSSTC.IEFU29 IEFU29 A Edward Long -- 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
