It would drive anyone crazy to be prompted for every single 'destructive'
command, but we do put a couple of prompts along with our automation 'shut
the whole thing down' command. We took a cue from V XCF OFF and make the
operator type in the target sysid. That is not an iron clad solution. No
solution will ever be iron clad. But inserting even a small loop can help
enormously vs. the type-it-and-watch-helplessly alternative.
.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
Ted MacNEIL
<eamacn...@yahoo.
CA> To
Sent by: IBM IBM-MAIN@bama.ua.edu
Mainframe cc
Discussion List
<ibm-m...@bama.ua Subject
.edu> Re: Operator Validation before
Executing Command
07/27/2009 03:09
PM
Please respond to
IBM Mainframe
Discussion List
<ibm-m...@bama.ua
.edu>
>Management would like all destructive
commands to have a WTOR which the operator would be asked "Do you really
want to execute this command" and provide the opportunity to reply "NO" to
abort the command.
I worked for a Beta shop of MDF (Amdahl's partioning) in the early 1980's.
We had issues regarding there was no prompt to ask the operator, when
restarting a domain, "are you sure".
So, we asked Amdahl to put one in.
They ended up taking it back out.
The reason:
Once an operator had been committed to taking the domain down they were
conditioned to automatically reply YES to the prompt.
Changing the sequence only changes the responses, but the conditioning is
still there.
1. Amdahl removed the prompt.
2. Once somebody has made up their mind, you can't do anything about it.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
