Re: Longer SMFWAIT during IPL MSI
I remember having this issue years ago when using the old IPO SMFDUMP program. We forced a switch at midnight and dumped the last of the previous day's data on two loosely coupled systems. IIRC, the type 19s were produced by the IEFU29 exit under a global IPO1.SMF enqueue. The two dumps' time frames never matched because one had to wait a long time for the other to issue the l-space macro against every device in the system before proceeding. Record type 19 is written: 1. For each online device associated with a specific IPL time frame, 2. For each online device associated with a processed HALT EOD or SWITCH SMF command, and 3. When a direct access volume that is defined by DD statement is demounted. Therefore, the magnitude of the problem depends very much on the number of online devices and how fast their VTOCs can be read. Since our shop already had more modern DASD space reporting tools, we got rid of the problem by excluding type 19 in SMFPRMxx. db -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Shameem .K .Shoukath Sent: Friday, May 31, 2013 1:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Longer SMFWAIT during IPL MSI Thanks Bob for sharing the REDBOOK details it is of good help to understand the process. We are recording 19 in all LPARs. I think storage team uses it for their reporting using 20% or something, im not sure. My actual question still stands when i compare PROD and DEV SMFPRMxx then only diff i see is the SMF EXIT IEFU84. Is this exit heavy by itself or by poor coding ? is this affecting performance POST IPL as this EXIT takes control before each SMF Write. I need to raise a CHANGE if i want to remove it and test. So I was expecting to get a feedback from the LIST whether it worth a try. I have to give some justification in the CHANGE to request the removal. Thanks and Regards Shameem K Shoukath From: Bob Rutledge deerh...@ix.netcom.com To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, May 30, 2013 8:55 PM Subject: Re: Longer SMFWAIT during IPL MSI I suggest this Redbook: http://publib-b.boulder.ibm.com/abstracts/sg247816.html?Open Bob Shameem .K .Shoukath wrote: hi there, I was just going thru the IPL statistics of all LPARs in out org. I see in one LPAR the SMFWAIT is taking fairly longer comp to others. out of total 00:01:12 MSI time this takes 00:00:53.586 I am not sure what happens in this process, took a chance compared the SMFPRMxx and saw there is one exit IEFU84 additional compared to PROD and QA lpars. would this be the cause for slower IPL ? Will it also may be one reason contributing to performance issues? as i understand this exit gets control before each SMF write. *** IEEMB860 Statistics *** ILRTMRLG 00:00:00.278 ASM IEEVMSI 00:00:00.065 Reconfiguration IARM8MSI 00:00:00.030 RSM - bring storage online IECVIOSI 00:00:02.627 IOS dynamic pathing RACROUTE 00:00:00.000 Initialize Security Environment ATBINSYS 00:00:00.020 APPC IKJEFXSR 00:00:00.183 TSO IXGBLF00 00:00:00.029 Logger AXRINSTR 00:00:00.042 System REXX CEAINSTR 00:00:00.031 Common Event Adapter HWIAMIN1 00:00:00.067 BCPii COMMNDXX 00:00:00.091 COMMANDxx processing IEAVTMSI 00:00:00.071 RTM SMFWAIT 00:00:53.586 SMF ICHSEC05 00:00:12.113 Security Server MSIEXIT 00:00:00.000 Cnz_MSIExit Dynamic Exit IEFJSIN2 00:00:03.188 SSN= subsystem IEFHB4I2 00:00:00.015 ALLOCAS - UCB scan CSRINIT 00:00:00.005 Windowing services FINSHMSI 00:00:00.336 Wait for attached CMDs IEEMB860 00:01:12.797 Uncaptured time: 00:00:00.011 Thanks and Regards Shameem K Shoukath -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Longer SMFWAIT during IPL MSI
We IPL with type 19's turned off, and then enable in Command after IPL. Jerry Whitteridge Lead Systems Programmer Safeway Inc. 925 951 4184 If you feel in control you just aren't going fast enough. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Dave Barry Sent: Monday, June 03, 2013 12:40 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Longer SMFWAIT during IPL MSI I remember having this issue years ago when using the old IPO SMFDUMP program. We forced a switch at midnight and dumped the last of the previous day's data on two loosely coupled systems. IIRC, the type 19s were produced by the IEFU29 exit under a global IPO1.SMF enqueue. The two dumps' time frames never matched because one had to wait a long time for the other to issue the l-space macro against every device in the system before proceeding. Record type 19 is written: 1. For each online device associated with a specific IPL time frame, 2. For each online device associated with a processed HALT EOD or SWITCH SMF command, and 3. When a direct access volume that is defined by DD statement is demounted. Therefore, the magnitude of the problem depends very much on the number of online devices and how fast their VTOCs can be read. Since our shop already had more modern DASD space reporting tools, we got rid of the problem by excluding type 19 in SMFPRMxx. db -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Shameem .K .Shoukath Sent: Friday, May 31, 2013 1:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Longer SMFWAIT during IPL MSI Thanks Bob for sharing the REDBOOK details it is of good help to understand the process. We are recording 19 in all LPARs. I think storage team uses it for their reporting using 20% or something, im not sure. My actual question still stands when i compare PROD and DEV SMFPRMxx then only diff i see is the SMF EXIT IEFU84. Is this exit heavy by itself or by poor coding ? is this affecting performance POST IPL as this EXIT takes control before each SMF Write. I need to raise a CHANGE if i want to remove it and test. So I was expecting to get a feedback from the LIST whether it worth a try. I have to give some justification in the CHANGE to request the removal. Thanks and Regards Shameem K Shoukath From: Bob Rutledge deerh...@ix.netcom.com To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, May 30, 2013 8:55 PM Subject: Re: Longer SMFWAIT during IPL MSI I suggest this Redbook: http://publib-b.boulder.ibm.com/abstracts/sg247816.html?Open Bob Shameem .K .Shoukath wrote: hi there, I was just going thru the IPL statistics of all LPARs in out org. I see in one LPAR the SMFWAIT is taking fairly longer comp to others. out of total 00:01:12 MSI time this takes 00:00:53.586 I am not sure what happens in this process, took a chance compared the SMFPRMxx and saw there is one exit IEFU84 additional compared to PROD and QA lpars. would this be the cause for slower IPL ? Will it also may be one reason contributing to performance issues? as i understand this exit gets control before each SMF write. *** IEEMB860 Statistics *** ILRTMRLG 00:00:00.278 ASM IEEVMSI 00:00:00.065 Reconfiguration IARM8MSI 00:00:00.030 RSM - bring storage online IECVIOSI 00:00:02.627 IOS dynamic pathing RACROUTE 00:00:00.000 Initialize Security Environment ATBINSYS 00:00:00.020 APPC IKJEFXSR 00:00:00.183 TSO IXGBLF00 00:00:00.029 Logger AXRINSTR 00:00:00.042 System REXX CEAINSTR 00:00:00.031 Common Event Adapter HWIAMIN1 00:00:00.067 BCPii COMMNDXX 00:00:00.091 COMMANDxx processing IEAVTMSI 00:00:00.071 RTM SMFWAIT 00:00:53.586 SMF ICHSEC05 00:00:12.113 Security Server MSIEXIT 00:00:00.000 Cnz_MSIExit Dynamic Exit IEFJSIN2 00:00:03.188 SSN= subsystem IEFHB4I2 00:00:00.015 ALLOCAS - UCB scan CSRINIT 00:00:00.005 Windowing services FINSHMSI 00:00:00.336 Wait for attached CMDs IEEMB860 00:01:12.797 Uncaptured time: 00:00:00.011 Thanks and Regards Shameem K Shoukath -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists
Re: Longer SMFWAIT during IPL MSI
IEFU84 is an exit point provided by the operating system (yes - which gets invoked prior to the writing of MANY, but NOT ALL, SMF records) but the performance question is really a question of what the version of IEFU84 on this system is doing when it gets invoked. The actrual code being invoked could come from a variety of sources (IBM, in-house, vendor). The other thing to note is that for many year now the SMF exits are actually being managed by the CSV Dynamic Exist function so you also need to check the PROGxx parmlib member(s) on the system and look for EXITNAMEs values that include the string 'IEFU84'. By default the IEFU84 module is located in LPA storage (so if you are NOT using dynamic exits it should be fairly easy to locate in a dump and check the eyecatcher which would lead you to the next step in the investigation. NOTE: In general the SMF record exit points (IEFu83/4/5) are really intended to just be a quick peak and out thing but there are some pretty complicated exit modules out there!!! Good Luck; Bill (Former SMF Component Owner) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Longer SMFWAIT during IPL MSI
On Thu, 30 May 2013 23:05:21 -0500, Ed Gould edgould1...@comcast.net wrote: Bob: I was puzzled by his question. Then I remembered one time a LONG time ago (when SMF first went to VSAM) that we IPL'd and did not know about having to format the MAN datasets and the system did automatically. Could that be his issue? Ed LOL... that still happens, but light years after MSI (in computer time)! It would also be a one time event, not every IPL. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Longer SMFWAIT during IPL MSI
Thanks Bob for sharing the REDBOOK details it is of good help to understand the process. We are recording 19 in all LPARs. I think storage team uses it for their reporting using 20% or something, im not sure. My actual question still stands when i compare PROD and DEV SMFPRMxx then only diff i see is the SMF EXIT IEFU84. Is this exit heavy by itself or by poor coding ? is this affecting performance POST IPL as this EXIT takes control before each SMF Write. I need to raise a CHANGE if i want to remove it and test. So I was expecting to get a feedback from the LIST whether it worth a try. I have to give some justification in the CHANGE to request the removal. Thanks and Regards Shameem K Shoukath From: Bob Rutledge deerh...@ix.netcom.com To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, May 30, 2013 8:55 PM Subject: Re: Longer SMFWAIT during IPL MSI I suggest this Redbook: http://publib-b.boulder.ibm.com/abstracts/sg247816.html?Open Bob Shameem .K .Shoukath wrote: hi there, I was just going thru the IPL statistics of all LPARs in out org. I see in one LPAR the SMFWAIT is taking fairly longer comp to others. out of total 00:01:12 MSI time this takes 00:00:53.586 I am not sure what happens in this process, took a chance compared the SMFPRMxx and saw there is one exit IEFU84 additional compared to PROD and QA lpars. would this be the cause for slower IPL ? Will it also may be one reason contributing to performance issues? as i understand this exit gets control before each SMF write. *** IEEMB860 Statistics *** ILRTMRLG 00:00:00.278 ASM IEEVMSI 00:00:00.065 Reconfiguration IARM8MSI 00:00:00.030 RSM - bring storage online IECVIOSI 00:00:02.627 IOS dynamic pathing RACROUTE 00:00:00.000 Initialize Security Environment ATBINSYS 00:00:00.020 APPC IKJEFXSR 00:00:00.183 TSO IXGBLF00 00:00:00.029 Logger AXRINSTR 00:00:00.042 System REXX CEAINSTR 00:00:00.031 Common Event Adapter HWIAMIN1 00:00:00.067 BCPii COMMNDXX 00:00:00.091 COMMANDxx processing IEAVTMSI 00:00:00.071 RTM SMFWAIT 00:00:53.586 SMF ICHSEC05 00:00:12.113 Security Server MSIEXIT 00:00:00.000 Cnz_MSIExit Dynamic Exit IEFJSIN2 00:00:03.188 SSN= subsystem IEFHB4I2 00:00:00.015 ALLOCAS - UCB scan CSRINIT 00:00:00.005 Windowing services FINSHMSI 00:00:00.336 Wait for attached CMDs IEEMB860 00:01:12.797 Uncaptured time: 00:00:00.011 Thanks and Regards Shameem K Shoukath -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Longer SMFWAIT during IPL MSI
hi there, I was just going thru the IPL statistics of all LPARs in out org. I see in one LPAR the SMFWAIT is taking fairly longer comp to others. out of total 00:01:12 MSI time this takes 00:00:53.586 I am not sure what happens in this process, took a chance compared the SMFPRMxx and saw there is one exit IEFU84 additional compared to PROD and QA lpars. would this be the cause for slower IPL ? Will it also may be one reason contributing to performance issues? as i understand this exit gets control before each SMF write. *** IEEMB860 Statistics *** ILRTMRLG 00:00:00.278 ASM IEEVMSI 00:00:00.065 Reconfiguration IARM8MSI 00:00:00.030 RSM - bring storage online IECVIOSI 00:00:02.627 IOS dynamic pathing RACROUTE 00:00:00.000 Initialize Security Environment ATBINSYS 00:00:00.020 APPC IKJEFXSR 00:00:00.183 TSO IXGBLF00 00:00:00.029 Logger AXRINSTR 00:00:00.042 System REXX CEAINSTR 00:00:00.031 Common Event Adapter HWIAMIN1 00:00:00.067 BCPii COMMNDXX 00:00:00.091 COMMANDxx processing IEAVTMSI 00:00:00.071 RTM SMFWAIT 00:00:53.586 SMF ICHSEC05 00:00:12.113 Security Server MSIEXIT 00:00:00.000 Cnz_MSIExit Dynamic Exit IEFJSIN2 00:00:03.188 SSN= subsystem IEFHB4I2 00:00:00.015 ALLOCAS - UCB scan CSRINIT 00:00:00.005 Windowing services FINSHMSI 00:00:00.336 Wait for attached CMDs IEEMB860 00:01:12.797 Uncaptured time: 00:00:00.011 Thanks and Regards Shameem K Shoukath -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Longer SMFWAIT during IPL MSI
Check to see if the image is recording SMF19. This can take a lot of time HTH, snip I was just going thru the IPL statistics of all LPARs in out org. I see in one LPAR the SMFWAIT is taking fairly longer comp to others. out of total 00:01:12 MSI time this takes 00:00:53.586 I am not sure what happens in this process, took a chance compared the SMFPRMxx and saw there is one exit IEFU84 additional compared to PROD and QA lpars. would this be the cause for slower IPL ? Will it also may be one reason contributing to performance issues? as i understand this exit gets control before each SMF write. /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Longer SMFWAIT during IPL MSI
I suggest this Redbook: http://publib-b.boulder.ibm.com/abstracts/sg247816.html?Open Bob Shameem .K .Shoukath wrote: hi there, I was just going thru the IPL statistics of all LPARs in out org. I see in one LPAR the SMFWAIT is taking fairly longer comp to others. out of total 00:01:12 MSI time this takes 00:00:53.586 I am not sure what happens in this process, took a chance compared the SMFPRMxx and saw there is one exit IEFU84 additional compared to PROD and QA lpars. would this be the cause for slower IPL ? Will it also may be one reason contributing to performance issues? as i understand this exit gets control before each SMF write. *** IEEMB860 Statistics *** ILRTMRLG 00:00:00.278 ASM IEEVMSI 00:00:00.065 Reconfiguration IARM8MSI 00:00:00.030 RSM - bring storage online IECVIOSI 00:00:02.627 IOS dynamic pathing RACROUTE 00:00:00.000 Initialize Security Environment ATBINSYS 00:00:00.020 APPC IKJEFXSR 00:00:00.183 TSO IXGBLF00 00:00:00.029 Logger AXRINSTR 00:00:00.042 System REXX CEAINSTR 00:00:00.031 Common Event Adapter HWIAMIN1 00:00:00.067 BCPii COMMNDXX 00:00:00.091 COMMANDxx processing IEAVTMSI 00:00:00.071 RTM SMFWAIT 00:00:53.586 SMF ICHSEC05 00:00:12.113 Security Server MSIEXIT 00:00:00.000 Cnz_MSIExit Dynamic Exit IEFJSIN2 00:00:03.188 SSN= subsystem IEFHB4I2 00:00:00.015 ALLOCAS - UCB scan CSRINIT 00:00:00.005 Windowing services FINSHMSI 00:00:00.336 Wait for attached CMDs IEEMB860 00:01:12.797 Uncaptured time: 00:00:00.011 Thanks and Regards Shameem K Shoukath -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Longer SMFWAIT during IPL MSI
Bob: I was puzzled by his question. Then I remembered one time a LONG time ago (when SMF first went to VSAM) that we IPL'd and did not know about having to format the MAN datasets and the system did automatically. Could that be his issue? Ed On May 30, 2013, at 1:55 PM, Bob Rutledge wrote: I suggest this Redbook: http://publib-b.boulder.ibm.com/abstracts/sg247816.html?Open Bob Shameem .K .Shoukath wrote: hi there, I was just going thru the IPL statistics of all LPARs in out org. I see in one LPAR the SMFWAIT is taking fairly longer comp to others. out of total 00:01:12 MSI time this takes 00:00:53.586 I am not sure what happens in this process, took a chance compared the SMFPRMxx and saw there is one exit IEFU84 additional compared to PROD and QA lpars. would this be the cause for slower IPL ? Will it also may be one reason contributing to performance issues? as i understand this exit gets control before each SMF write. *** IEEMB860 Statistics *** ILRTMRLG 00:00:00.278 ASM IEEVMSI 00:00:00.065 Reconfiguration IARM8MSI 00:00:00.030 RSM - bring storage online IECVIOSI 00:00:02.627 IOS dynamic pathing RACROUTE 00:00:00.000 Initialize Security Environment ATBINSYS 00:00:00.020 APPC IKJEFXSR 00:00:00.183 TSO IXGBLF00 00:00:00.029 Logger AXRINSTR 00:00:00.042 System REXX CEAINSTR 00:00:00.031 Common Event Adapter HWIAMIN1 00:00:00.067 BCPii COMMNDXX 00:00:00.091 COMMANDxx processing IEAVTMSI 00:00:00.071 RTM SMFWAIT 00:00:53.586 SMF ICHSEC05 00:00:12.113 Security Server MSIEXIT 00:00:00.000 Cnz_MSIExit Dynamic Exit IEFJSIN2 00:00:03.188 SSN= subsystem IEFHB4I2 00:00:00.015 ALLOCAS - UCB scan CSRINIT 00:00:00.005 Windowing services FINSHMSI 00:00:00.336 Wait for attached CMDs IEEMB860 00:01:12.797 Uncaptured time: 00:00:00.011 Thanks and Regards Shameem K Shoukath -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
