Jeremy Nicoll wrote, in part:
> I - very much the junior - said:
>STOP!

And -- without knowing Jeremy in the slightest--I will say that this is one of 
the marks of a good sysprog: willingness to risk looking stupid, rather than 
having everyone look stupid. In aviation, this is called CRM and is considered 
a Very Good Thing (as it should be): 
https://en.wikipedia.org/wiki/Crew_resource_management

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Jeremy Nicoll
Sent: Thursday, March 6, 2025 4:59 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stupid outages you caused (was: Cost of an outage)

On Wed, 5 Mar 2025, at 23:01, Phil Smith III wrote:
> What stories can y'all share about times you or someone you worked 
> with took down a system ...

Well, I remember a senior colleague's lucky escape ...

Quite early in my sysprog career, before PR/SM came along and gave us our own 
test LPARs, a lot of our testing was done on the programmers'
test system on one specific 2h lunchtime slot per week.

Despite that system being thought of a development one only, it wasn't unheard 
of for some production batch work to run there, and in any case it shared its 
JES2 spool with the production system.  Back in those days we didn't run a 
sysout archiving tool.

My colleague was demonstrating how we could test JES2 function using a 
secondary JES2 (ie one started as an ordinary STC, as far as I remember, under 
the primary JES2).  Commands to the secondary one just had to be prefixed by a 
different subsystem commmand character from any used for primary subsystems.

At the end of our tests my colleague, while continuing to explain the purpose 
of successive commands didn't pay enough attention to what they were typing as 
they entered the command to purge everything from the spool and was about to 
hit enter when I - very much the junior - said:
STOP! and asked: shouldn't that have the secondary JES's command character?

Swearing ensued, but not as much as would have done if the command had been 
issued.
      

--
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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to