Elardus, IIRC, the incident was pre-RACF, and the system datasets were protected with passwords on the datasets themselves and somebody forgot to put a password on SYS1.NUCLEUS.
Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Elardus Engelbrecht Sent: Thursday, November 12, 2015 1:23 PM To: [email protected] Subject: Re: IPL wait state Barry Merrill wrote: >... The challenge was accepted, and in short order, "Tim W." observed that >SYS1.NUCLEUS was not protected, so he scratched it. "Tim W." knew that once >the system is up, the dataset SYS1.NUCLEUS is not read again, so the SHARE >demonstration continued without flaw. It was later heard that IBM took the >SHARE MVS demonstration down at 11 p.m. to IPL for a customer benchmark; it >took until 3 a.m. for IBM to find a CE who could correctly decipher the wait >state code and explain that the IPLs kept failing because there was no >SYS1.NUCLEUS on the IPL volume. Wow! Barry! That is one of the best war stories I read on IBM-MAIN! I really enjoyed your story, especially that big blue have a hard time to fix things! Now, DASD were probably not shared, how did that CE found out what the real problem was? Dumps? Inspecting Consoles/SYSLOG printouts? SAD? Ok, was there really any 'security'? I believe RACF was at its infancy at that time! ;-) Barry, do you have any documentation or link of this fun story? Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
