I was the systems manager at GMSF and we were running SVS under VM. We had a monitoring program called EXHIBIT written by my colleague Gerhard Postpischil ז״ל and the operators could dial into it. The operators had a hard time remembering to do #CP RESET instead of harmful commands beginning with D.,
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Sebastian Welton <[email protected]> Sent: Thursday, March 6, 2025 4:57 AM To: [email protected] Subject: Re: Stupid outages you caused (was: Cost of an outage) External Message: Use Caution My first time working with VM, which I had never seen before nor used and was primarily there for the MVS guests. I was given a quick once over of the systems and left to it. For the first week, I would come in to work in the morning, logon to the MVS guest and then logoff. System programmers would then suddenly materialise as the systems had all stopped. I was quite happy as the mainframe was still running and VM was active, I would pop off to breakfast while they went problem solving. After about a week, which was also spent reading some VM manuals I actually realised I should do #CP DISC and not #CP LOGOFF. I never told them why the system crashed but it didn't happen again until some builders nearby cut through the power cables!. Sebastian. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
