Re: SE/HMC driver update duration
> >We are updating our HMC/SE driver level. Our CE says the update takes 2 >days to complete. > Have you checked on IBM Resourcelink for your machine(s), the number of missing EC/MCLs? You can then use this info and list off the missing MCL details and/or HMC MCL Details and then ask your IBM SSR to provide more details on each of them and this might give you a better insight into the timings. If you are way behind in your EC/MCL levels then it is a possibility as some of the underlying MCLs for the SE could require "mirroring" between the two SEs and this has been known to take some time along with SE Reboot(s). At our site, we try and do a regular (every 3 months or so) MCL run and have never seen a requirement of up to 2 days Hope the above helps. Roger -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SE/HMC driver update duration
There are various answers. My experience: few hours. What is few? I can't provide exact number, but definitely less than 8 hours. Maybe 3 is reasonable choice. I did it several times (sometimes without CE), but never even it took more than I describe above. Single CPC, one HMC (included in the action). Of course YMMV. -- Radoslaw Skorupka Lodz, Poland W dniu 2019-12-18 o 09:24, Jake Anderson pisze: Hello We are updating our HMC/SE driver level. Our CE says the update takes 2 days to complete. I am trying to understand what are the factors which delays or takes time to complete the process. Regards Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN . == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2019 r. wynosi 169.347.928 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169.347.928 as at 1 January 2019. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SE/HMC driver update duration [EXTERNAL]
Jake, this may be a bad analogy but think of a driver upgrade like a z/OS upgrade. You are changing the base operating system used to run the hardware. It can touch all of the I/O features and other features in your box. An example of the "other" features would be the CFCC level for a coupling facility lpar. When you do the change dynamically the process has to be careful not to cause a disruption to any active processes running. So the dynamic process takes longer to run. I also think you have to be at a given MCL level on the current driver to support the dynamic change. Thanks.. Paul Feller AGT Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jake Anderson Sent: Wednesday, December 18, 2019 7:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SE/HMC driver update duration [EXTERNAL] Out of curiosity why Driver update takes time .. What happens internally and what are set of action takes (apologies for my ignorance) On Wed, 18 Dec, 2019, 5:42 PM Allan Staller, wrote: > I can believe Driver MCLs can take a long time on the support element. > I do not agree with the HMC updated. I have never seen a HMC upgrade > take more than a couple of hours. > > My $0.02 USD worth. > > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Jake Anderson > Sent: Wednesday, December 18, 2019 7:08 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SE/HMC driver update duration > > We have one CEC plus one SE and HMC. > > Updating from 32 to 36. > > On Wed, 18 Dec, 2019, 3:11 PM Jousma, David, < > 01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote: > > > I don’t know that a couple days are accurate, unless the CE just doesn’t > > want to work more than 8 hours. I will tell you though that it was a > > lengthy process. Probably 8-10 hours if I remember right when we made > > that jump a year or so ago. We normally allot 5-6 hours of time for IBM > > to complete before our maintenance window, and in this particular > > case, we almost blew through our window of work because the updates > > ran so long. WE now schedule a 12 hour window for IBM to do their > > work just because of this. My team mate, might see this post and > > offer up a bit more information. > > > > > > > > __ > > ___ > > Dave Jousma > > AVP | Manager, Systems Engineering > > > > Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand > > Rapids, MI 49546 > > 616.653.8429 | fax: 616.653.2717 > > > > > > -----Original Message- > > From: IBM Mainframe Discussion List On > > Behalf Of Jake Anderson > > Sent: Wednesday, December 18, 2019 3:24 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: SE/HMC driver update duration > > > > **CAUTION EXTERNAL EMAIL** > > > > **DO NOT open attachments or click on links from unknown senders or > > unexpected emails** > > > > Hello > > > > We are updating our HMC/SE driver level. Our CE says the update > > takes > > 2 days to complete. > > > > I am trying to understand what are the factors which delays or takes > > time to complete the process. > > > > Regards > > Jake > > > > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO > > IBM-MAIN **CAUTION EXTERNAL EMAIL** > > > > **DO NOT open attachments or click on links from unknown senders or > > unexpected emails** > > > > This e-mail transmission contains information that is confidential > > and > may > > be privileged. It is intended only for the addressee(s) named above. If > > you receive this e-mail in error, please do not read, copy or > > disseminate it in any manner. If you are not the intended recipient, > > any disclosure, copying, distribution or use of the contents of this > > information is prohibited. Please reply to the message immediately > > by informing the sender that the message was misdirected. After > > replying, please erase it from your computer system. Your assistance > > in correcting > this error is appreciated. > > > > > > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the messag
Re: SE/HMC driver update duration
> Probably 8-10 hours if I remember right when we made that jump a year or so > ago. We normally allot 5-6 hours of time for IBM > to complete before our maintenance window, and in this particular case, we > almost blew through our window of work because the > updates ran so long. WE now schedule a 12 hour window for IBM to do their > work just because of this. My team mate, might > see this post and offer up a bit more information. Because we have 3 HMCs that are configured to control all 3 of our CECs, IBM suggested we upgrade the HMCs ahead of the CECs. I don’t' recall the exact problem, but I do know that after upgrading the first CEC, we could no longer control that one using an HMC that wasn't at driver 36 yet (first CEC upgrade was completed before last HMC). So the HMCs were done ahead of time, during the day, non-disruptive to anything but the HMC itself. We had no problem accessing pre-Drive 36 HMCs with HMCs that had been upgraded to Driver 36 (backward compatible). Seems the HMC upgrades were started early in the morning, and completed by noon. I don't recall the specific times for these upgrades. But this is activity that can be done prior to the CEC Driver 36 upgrade. Our first CEC upgrade to Driver 36 took over 18 hours elapsed. The CE completed the upgrade to Driver 36 and was trying to get to a higher bundle level and spent a lot of time on the phone with the support center, as well as a break for another service call. Long day... The 2nd and 3rd CEC upgrades to driver 36 were about 9 and 7 hours. We did not have the problem getting to the next bundle level with these. Not sure if the time since last MCLs were applied makes a difference, but we had applied MCLs about 6 months before we went to Driver 36, so we were fairly current. If you are way behind, maybe this could be a reason for the longer estimated time. Getting to Driver 36 was a non-disruptive process, IBM performed this work while all systems were up and running. I guess if your CE wants 2 days, just start 2 days before you plan the disruptive POR. Tom Chicklon Fifth Third Bank _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jake Anderson Sent: Wednesday, December 18, 2019 3:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SE/HMC driver update duration **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Hello We are updating our HMC/SE driver level. Our CE says the update takes 2 days to complete. I am trying to understand what are the factors which delays or takes time to complete the process. Regards Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SE/HMC driver update duration
I don’t really know what goes on under the covers. Your IBM SE would be a better person to ask for the details. I think of the Driver MCL as a "level set". I suspect, each low level routine is updated and verified, which accounts for the duration. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jake Anderson Sent: Wednesday, December 18, 2019 7:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SE/HMC driver update duration Out of curiosity why Driver update takes time .. What happens internally and what are set of action takes (apologies for my ignorance) On Wed, 18 Dec, 2019, 5:42 PM Allan Staller, wrote: > I can believe Driver MCLs can take a long time on the support element. > I do not agree with the HMC updated. I have never seen a HMC upgrade > take more than a couple of hours. > > My $0.02 USD worth. > > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Jake Anderson > Sent: Wednesday, December 18, 2019 7:08 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SE/HMC driver update duration > > We have one CEC plus one SE and HMC. > > Updating from 32 to 36. > > On Wed, 18 Dec, 2019, 3:11 PM Jousma, David, < > 01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote: > > > I don’t know that a couple days are accurate, unless the CE just doesn’t > > want to work more than 8 hours. I will tell you though that it was a > > lengthy process. Probably 8-10 hours if I remember right when we made > > that jump a year or so ago. We normally allot 5-6 hours of time for IBM > > to complete before our maintenance window, and in this particular > > case, we almost blew through our window of work because the updates > > ran so long. WE now schedule a 12 hour window for IBM to do their > > work just because of this. My team mate, might see this post and > > offer up a bit more information. > > > > > > > > __ > > ___ > > Dave Jousma > > AVP | Manager, Systems Engineering > > > > Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand > > Rapids, MI 49546 > > 616.653.8429 | fax: 616.653.2717 > > > > > > -----Original Message- > > From: IBM Mainframe Discussion List On > > Behalf Of Jake Anderson > > Sent: Wednesday, December 18, 2019 3:24 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: SE/HMC driver update duration > > > > **CAUTION EXTERNAL EMAIL** > > > > **DO NOT open attachments or click on links from unknown senders or > > unexpected emails** > > > > Hello > > > > We are updating our HMC/SE driver level. Our CE says the update > > takes > > 2 days to complete. > > > > I am trying to understand what are the factors which delays or takes > > time to complete the process. > > > > Regards > > Jake > > > > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO > > IBM-MAIN **CAUTION EXTERNAL EMAIL** > > > > **DO NOT open attachments or click on links from unknown senders or > > unexpected emails** > > > > This e-mail transmission contains information that is confidential > > and > may > > be privileged. It is intended only for the addressee(s) named above. If > > you receive this e-mail in error, please do not read, copy or > > disseminate it in any manner. If you are not the intended recipient, > > any disclosure, copying, distribution or use of the contents of this > > information is prohibited. Please reply to the message immediately > > by informing the sender that the message was misdirected. After > > replying, please erase it from your computer system. Your assistance > > in correcting > this error is appreciated. > > > > > > > > -- 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 > ::DISCLAIMER:: > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) o
Re: SE/HMC driver update duration
Out of curiosity why Driver update takes time .. What happens internally and what are set of action takes (apologies for my ignorance) On Wed, 18 Dec, 2019, 5:42 PM Allan Staller, wrote: > I can believe Driver MCLs can take a long time on the support element. > I do not agree with the HMC updated. I have never seen a HMC upgrade take > more than a couple of hours. > > My $0.02 USD worth. > > > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Jake Anderson > Sent: Wednesday, December 18, 2019 7:08 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SE/HMC driver update duration > > We have one CEC plus one SE and HMC. > > Updating from 32 to 36. > > On Wed, 18 Dec, 2019, 3:11 PM Jousma, David, < > 01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote: > > > I don’t know that a couple days are accurate, unless the CE just doesn’t > > want to work more than 8 hours. I will tell you though that it was a > > lengthy process. Probably 8-10 hours if I remember right when we made > > that jump a year or so ago. We normally allot 5-6 hours of time for IBM > > to complete before our maintenance window, and in this particular > > case, we almost blew through our window of work because the updates > > ran so long. WE now schedule a 12 hour window for IBM to do their > > work just because of this. My team mate, might see this post and > > offer up a bit more information. > > > > > > __ > > ___ > > Dave Jousma > > AVP | Manager, Systems Engineering > > > > Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand > > Rapids, MI 49546 > > 616.653.8429 | fax: 616.653.2717 > > > > > > -----Original Message- > > From: IBM Mainframe Discussion List On > > Behalf Of Jake Anderson > > Sent: Wednesday, December 18, 2019 3:24 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: SE/HMC driver update duration > > > > **CAUTION EXTERNAL EMAIL** > > > > **DO NOT open attachments or click on links from unknown senders or > > unexpected emails** > > > > Hello > > > > We are updating our HMC/SE driver level. Our CE says the update takes > > 2 days to complete. > > > > I am trying to understand what are the factors which delays or takes > > time to complete the process. > > > > Regards > > Jake > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > **CAUTION EXTERNAL EMAIL** > > > > **DO NOT open attachments or click on links from unknown senders or > > unexpected emails** > > > > This e-mail transmission contains information that is confidential and > may > > be privileged. It is intended only for the addressee(s) named above. If > > you receive this e-mail in error, please do not read, copy or > > disseminate it in any manner. If you are not the intended recipient, > > any disclosure, copying, distribution or use of the contents of this > > information is prohibited. Please reply to the message immediately by > > informing the sender that the message was misdirected. After replying, > > please erase it from your computer system. Your assistance in correcting > this error is appreciated. > > > > > > -- > > 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 > ::DISCLAIMER:: > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or may contain > viruses in transmission. The e mail and its contents (with or without > referred errors) shall therefore not attach any liability on the originator > or HCL or its affiliates. Views or opinions, if any, presented in this > email are solely tho
Re: SE/HMC driver update duration
I can believe Driver MCLs can take a long time on the support element. I do not agree with the HMC updated. I have never seen a HMC upgrade take more than a couple of hours. My $0.02 USD worth. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jake Anderson Sent: Wednesday, December 18, 2019 7:08 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SE/HMC driver update duration We have one CEC plus one SE and HMC. Updating from 32 to 36. On Wed, 18 Dec, 2019, 3:11 PM Jousma, David, < 01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote: > I don’t know that a couple days are accurate, unless the CE just doesn’t > want to work more than 8 hours. I will tell you though that it was a > lengthy process. Probably 8-10 hours if I remember right when we made > that jump a year or so ago. We normally allot 5-6 hours of time for IBM > to complete before our maintenance window, and in this particular > case, we almost blew through our window of work because the updates > ran so long. WE now schedule a 12 hour window for IBM to do their > work just because of this. My team mate, might see this post and > offer up a bit more information. > > > __ > ___ > Dave Jousma > AVP | Manager, Systems Engineering > > Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand > Rapids, MI 49546 > 616.653.8429 | fax: 616.653.2717 > > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Jake Anderson > Sent: Wednesday, December 18, 2019 3:24 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: SE/HMC driver update duration > > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > Hello > > We are updating our HMC/SE driver level. Our CE says the update takes > 2 days to complete. > > I am trying to understand what are the factors which delays or takes > time to complete the process. > > Regards > Jake > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > This e-mail transmission contains information that is confidential and may > be privileged. It is intended only for the addressee(s) named above. If > you receive this e-mail in error, please do not read, copy or > disseminate it in any manner. If you are not the intended recipient, > any disclosure, copying, distribution or use of the contents of this > information is prohibited. Please reply to the message immediately by > informing the sender that the message was misdirected. After replying, > please erase it from your computer system. Your assistance in correcting this > error is appreciated. > > > -- > 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 ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SE/HMC driver update duration
We have one CEC plus one SE and HMC. Updating from 32 to 36. On Wed, 18 Dec, 2019, 3:11 PM Jousma, David, < 01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote: > I don’t know that a couple days are accurate, unless the CE just doesn’t > want to work more than 8 hours. I will tell you though that it was a > lengthy process. Probably 8-10 hours if I remember right when we made > that jump a year or so ago. We normally allot 5-6 hours of time for IBM > to complete before our maintenance window, and in this particular case, we > almost blew through our window of work because the updates ran so long. WE > now schedule a 12 hour window for IBM to do their work just because of > this. My team mate, might see this post and offer up a bit more > information. > > > _ > Dave Jousma > AVP | Manager, Systems Engineering > > Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand > Rapids, MI 49546 > 616.653.8429 | fax: 616.653.2717 > > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Jake Anderson > Sent: Wednesday, December 18, 2019 3:24 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: SE/HMC driver update duration > > **CAUTION EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > Hello > > We are updating our HMC/SE driver level. Our CE says the update takes 2 > days to complete. > > I am trying to understand what are the factors which delays or takes time > to complete the process. > > Regards > Jake > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION > EXTERNAL EMAIL** > > **DO NOT open attachments or click on links from unknown senders or > unexpected emails** > > This e-mail transmission contains information that is confidential and may > be privileged. It is intended only for the addressee(s) named above. If > you receive this e-mail in error, please do not read, copy or disseminate > it in any manner. If you are not the intended recipient, any disclosure, > copying, distribution or use of the contents of this information is > prohibited. Please reply to the message immediately by informing the sender > that the message was misdirected. After replying, please erase it from your > computer system. Your assistance in correcting this error is appreciated. > > > -- > 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: SE/HMC driver update duration [EXTERNAL]
Paul's, comments reminded me to add some clarification. In our shop, 2 times per year, IBM always puts the MCL updates on concurrently, and the driver level upgrade included both HMC's and SE's, and took them near 12 hours to complete. We happen to *choose* to then perform a POR after they are done to fully implement OSA and CEX microcode that loads onto those cards, in addition to any planned IODF changes, and implementing z/OS and ISV software maintenance into our PROD environments on that particular CEC. _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Feller, Paul Sent: Wednesday, December 18, 2019 7:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SE/HMC driver update duration [EXTERNAL] **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Jake are you updating one or more HMCs as well as the SEs? I would say if you are updating the Driver level on the SEs then you need to update the HMCs that talk to them. Updating an HMC can take a little time. As Dave said the update to the SEs can take some time. The dynamic process takes longer than if you turn over the box to IBM. I've had IBM do it both ways. In our case we can move workload around between two CECs so we could take one CEC down. I'm know when we gave the box over to IBM the process was done in well under 6 hours, which is our normal maintenance window. That time takes into account shutting down our lpars and restarting them plus the POR time. So maybe the IBM person is taking into account the time to update one or more HMCs plus the SEs. Thanks.. Paul Feller AGT Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Wednesday, December 18, 2019 5:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SE/HMC driver update duration [EXTERNAL] I don’t know that a couple days are accurate, unless the CE just doesn’t want to work more than 8 hours. I will tell you though that it was a lengthy process. Probably 8-10 hours if I remember right when we made that jump a year or so ago. We normally allot 5-6 hours of time for IBM to complete before our maintenance window, and in this particular case, we almost blew through our window of work because the updates ran so long. WE now schedule a 12 hour window for IBM to do their work just because of this. My team mate, might see this post and offer up a bit more information. _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jake Anderson Sent: Wednesday, December 18, 2019 3:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SE/HMC driver update duration **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Hello We are updating our HMC/SE driver level. Our CE says the update takes 2 days to complete. I am trying to understand what are the factors which delays or takes time to complete the process. Regards Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Please note: This message originated outside your organization. Please use caution when ope
Re: SE/HMC driver update duration [EXTERNAL]
Jake are you updating one or more HMCs as well as the SEs? I would say if you are updating the Driver level on the SEs then you need to update the HMCs that talk to them. Updating an HMC can take a little time. As Dave said the update to the SEs can take some time. The dynamic process takes longer than if you turn over the box to IBM. I've had IBM do it both ways. In our case we can move workload around between two CECs so we could take one CEC down. I'm know when we gave the box over to IBM the process was done in well under 6 hours, which is our normal maintenance window. That time takes into account shutting down our lpars and restarting them plus the POR time. So maybe the IBM person is taking into account the time to update one or more HMCs plus the SEs. Thanks.. Paul Feller AGT Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Wednesday, December 18, 2019 5:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SE/HMC driver update duration [EXTERNAL] I don’t know that a couple days are accurate, unless the CE just doesn’t want to work more than 8 hours. I will tell you though that it was a lengthy process. Probably 8-10 hours if I remember right when we made that jump a year or so ago. We normally allot 5-6 hours of time for IBM to complete before our maintenance window, and in this particular case, we almost blew through our window of work because the updates ran so long. WE now schedule a 12 hour window for IBM to do their work just because of this. My team mate, might see this post and offer up a bit more information. _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jake Anderson Sent: Wednesday, December 18, 2019 3:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SE/HMC driver update duration **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Hello We are updating our HMC/SE driver level. Our CE says the update takes 2 days to complete. I am trying to understand what are the factors which delays or takes time to complete the process. Regards Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Please note: This message originated outside your organization. Please use caution when opening links or attachments. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SE/HMC driver update duration
I don’t know that a couple days are accurate, unless the CE just doesn’t want to work more than 8 hours. I will tell you though that it was a lengthy process. Probably 8-10 hours if I remember right when we made that jump a year or so ago. We normally allot 5-6 hours of time for IBM to complete before our maintenance window, and in this particular case, we almost blew through our window of work because the updates ran so long. WE now schedule a 12 hour window for IBM to do their work just because of this. My team mate, might see this post and offer up a bit more information. _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Jake Anderson Sent: Wednesday, December 18, 2019 3:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SE/HMC driver update duration **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Hello We are updating our HMC/SE driver level. Our CE says the update takes 2 days to complete. I am trying to understand what are the factors which delays or takes time to complete the process. Regards Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SE/HMC driver update duration
Hello We are updating our HMC/SE driver level. Our CE says the update takes 2 days to complete. I am trying to understand what are the factors which delays or takes time to complete the process. Regards Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
