On Sep 18, 2006, at 4:46 PM, Shane Ginnane wrote:
----------------------------
SNIP--------------------------------------------------------
After we went 4 char device addresses we had this happen twice in a
few
weeks - different operator, different shift.
I knocked up a cmdx exit to restrict all vary ranges to 32
(consecutive)
devices. The DASD management folks whinge and moan whenever they
are moving
a lot of devices, but if I'm feeling particularly magnanimous I'll
deactivate the exit on the sandpit for them, and they do their work
there.
Hasn't caused any major ructions, and has saved a couple of
incidents I
know of.
It seems like we have gone forward and then reverse.
30 years ago there was a restriction as to how many devices and paths
(IIRC 16) you could vary on or off at one time. IIRC our IBM SE wrote
a STC that (among other things) allowed the operator to vary on(off)
256 devices (paths) on at one time. This was an MP environment, it
was a great STC as you could do many other things with an outstanding
WTOR (too many to mention here). We also had an major issue with comm
task taking a hit once an hour (or so) and he had to intercept (IIRC)
the D23. Just with that one STC we saved many an IPL and lots of
operator aggravation. Hats off to Jim Garner.
Ed
Shane ...
(this customer has no automation software deployed)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
