I don't recall seeing OP's motivation for asking this question. I'm guessing it's to satisfy someone's hypothetical musing. As others have said, most of the once-conventional reasons are gone. Installation or upgrade or repair is likely to require at least one POR, but the odds of needing to interrupt production on a random weekend are now very low.
-- An OSA needs to be loaded with updated microcode. Either offline/online bounce or POR. Our console OSAs are well defined with symmetrical redundancy. It takes a while to work through the procedure, but it's very doable. The non-console OSAs are a menagerie of who knows what. It's easier to POR to catch them all at once. -- If you have two of them, cryptos can be managed like console OSAs. Offline/online, rinse, repeat. -- Error conditions. These are rare and impossible classify. A while back we had an MCL upgrade go south. Primary and alternate SEs got out of sync. Support Center said we had to POR to resync. Ouch. Then the same thing happened again! So we PORed again. Eventually got thru it. You get to explain these cases to the boss one by one. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Brennan Sent: Thursday, January 17, 2019 8:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: The WHY of the POR Last year I was watching the install of a new z14-ZR1 and the CE couldn't get the ICC consoles to work until he did a POR *after* the IP/LU settings were in place. I thought this was rather odd. Most likely there were dynamic ways around the problem, but when there's nothing running on a machine yet, the easiest is to try a POR. On 1/17/2019 12:20 AM, Vernooij, Kees (ITOP NM) - KLM wrote: > Sometimes it helps solve unexplainably unsolvable problems. We had this with > an unwilling PCHID. > > Kees, > > >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of Gibney, Dave >> Sent: 17 January, 2019 0:14 >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: The WHY of the POR >> >> Required is rare. Our last was for OSA related MCL. Before that, it >> was a scheduled power outage to upgrade the UPS. >> Otherwise, what Ed says. Each instance can be different. For us, it >> was also the only way to set the hardware clock. >> >> >>> -----Original Message----- >>> From: IBM Mainframe Discussion List >>> [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Finnell >>> Sent: Wednesday, January 16, 2019 2:46 PM >>> To: IBM-MAIN@LISTSERV.UA.EDU >>> Subject: Re: The WHY of the POR >>> >>> Murphy, squirrels, DR, hardware upgrades, terrorists, weather >>> events- >> pretty >>> much Risk assessment for your environment and your locale. >>> >>> In a message dated 1/16/2019 4:18:42 PM Central Standard Time, >>> johnmattson...@gmail.com writes: >>> I have a simple two lpar z9running zOS 1.13. I have searched >>> online, >> send me >>> to the manual if youhave a good ref. Thanks ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
