Matthew,
I tried to keep the initial post small, believe it or not, and
left out a lot of detail, so the answer is YES - I think.
My recollection is that when we explicitly vary the drives offline for
maintenance they are always varied offline to ALL LPARs in the SYSPLEX. In
Production that is 2 LPARs, and we do not share drives across SYSPLEXes
(at this particular location), so each SYSPLEX has only it's own devices
genned.
Similarly, when there is an 'error', we see the devices being implicitly
varied offline to all LPARs automatically on the SYSLOG.
We had a recurrence of the issue today (hence my post) and I see from the
the SYSLOGs that in this particular case we had an error, the drive was
varied offline to both LPARs automatically, and somebody then varied the
drive back online to only one of the LPARs (LPAR2) but not the other
(LPAR1) where we saw the problem this morning.
However, we have previously had occasions where the error went unnoticed
and drive has remained offline to both LPARs and the problem manifested
itself in exactly the same way.
I am interested to know the reason behind your (not stupid at all)
question.
Steve O.
----------------------------------------------------------------------
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
