Years ago we eliminated tape from the SADUMP process altogether. Also eliminated operator intervention. For each LPAR, we have a LOAD (IPL) profile that points to a DASD volume containing SAD IPL text. The SAD parameters run the dump to DASD without prompting the operator at all. When the dump is finished, the operator IPLs z/OS as usual. The process is pretty quick.
. . 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 <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jeremy Nicoll Sent: Thursday, November 19, 2020 8:09 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SADUMP IPL tape *** EXTERNAL EMAIL - Use caution when opening links or attachments *** On Thu, 19 Nov 2020, at 16:01, Dana Mitchell wrote: > They are definitely different. And even within z/OS there will > sometimes be a PTF that changes an internal structure such that it has > an ACTION HOLD telling you that you need to recreate the SADUMP > program But the SADUMP program (at least, 20+ years ago) was a different matter. That was generally placed on specific disk volumes. The SADUMP tape was only used to get the system IPLed and make it load the disk-resident program. Has this process changed? -- Jeremy Nicoll - my opinions are my own. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
