Wow. I never had occasion to look at SAD wait state codes before. Leave it to IBM to document the hell out of an abnormal outcome of an abnormal operation. I'll have to say, though, that In my entire career I cannot recall any instance where PSW Restart ever actually solved a problem. It's a magnificent mechanism, but we all know the old saw about trying the same action over and over while expecting a different result.
I think hung SAD is 99.9% hardware or bioware. Get a big stick. Use it to push buttons and/or poke inattentive operators. https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieah700/sadmpw.htm -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jim Mulder Sent: Monday, September 9, 2019 8:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: How to restart SADMP The first thing to do with a "stuck" SADMP is to display the PSW, using the "Display and Alter" function on the HMC to display the PSW of the only operating logical processor in the partition. If the SADMP was initiated manually, this will be logical processor 0, If it was initiated by AutoIPL, it can be a different logical processor. Usually, the PSW will contain a SADMP wait state code which is documented in the MVS System Codes manual. To restart SADMP, you use the "PSW Restart" function on the HMC the restart the only operating logical processor. If you have to re-IPL SADMP, you will lose the 4MB of z/OS read-only nucleus starting at virtual address 01000000, since that is where SADMP's code and work areas are located. Usually, the read-only nucleus is not needed for diagnosing the dump of z/OS (except in the rare case where the problem was an overlay of the read-only nucleus). So re-IPLing SADMP usually provides a reasonably useful dump of z/OS. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY "IBM Mainframe Discussion List" <IBM-MAIN@LISTSERV.UA.EDU> wrote on 09/09/2019 07:07:35 PM: > From: "Jesse 1 Robinson" <jesse1.robin...@sce.com> > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 09/09/2019 10:55 PM > Subject: Re: How to restart SADMP > Sent by: "IBM Mainframe Discussion List" <IBM-MAIN@LISTSERV.UA.EDU> > > I don't recall having SAD stall in any kind of 'restartable' state. > In general, if you restart (reIPL) SAD, you'll likely get a dump of > SAD itself because that's the 'OS' in control. The resulting dump may > help you figure out what's wrong with SAD but will probably not help > much with the original problem that inspired SAD in the first place. > > I suggest configuring SAD to use only disk, not tape. Over the years > most problems I've encountered have involved tape. Also do not prompt > the operator to enter *anything*; that's the other common cause of > failure. A 'properly' configured SAD should run from start to finish > without any manual intervention. > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of NandhaKumar S > Sent: Monday, September 9, 2019 11:46 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):How to restart SADMP > > Hi Team, > > How to restart SADMP if it’s stuck after Loaded SAD profile? IBM > suggested the Procedure-B to restart the SADMP But I don’t want to > Re-IPL the SADMP. > > Let me know if someone have faced this issue. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
