True. The effect of DVCDN is reversed by DVCUP.
Sent via the Samsung Galaxy Note® 4, an AT&T 4G LTE smartphone -------- Original message -------- From: Charles Mills <charl...@mcn.org> Date: 8/1/2016 7:55 AM (GMT-06:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Blue Screen Of Death, mainframe-style My recollection of DVCDN is that it would not have affected anything that would span an IPL. In other words, a vanilla re-IPL would have solved any "damage" done by DVCDN. If this story is not a myth then at least it is missing some key detail. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gerhard Adam Sent: Saturday, July 30, 2016 2:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Blue Screen Of Death, mainframe-style > He tries to restart the big machine, but that fails almost immediately. Turns out that the second command in the startup sequence is one that directs output to the printer known as 00E -- which the mainframe no longer knows how to use. What does that sentence even mean? Any printer at any address would've been "known" much later in the IPL process and there was nothing "known" at the actual point of IPL. Again, the story sounds like a fairy tale. ---------------------------------------------------------------------- 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
