Alan Altmark wrote:
QUERY only tells you if you have issued the ENABLE command. Like Marcy,
I suspect that the device was in Purgatory for some reason. If the
problem is reproducible, then I would open a PMR. I don't think you
should have to VARY OFF/ON before you ENABLE -- how rude.
OP said the device was 'ENABLE' following a 'CP QUERY'. So this could
very be the problem ! (I'm assuming the QUERY command simply looks at
the RDEVENAB in RDEVFLG in the RDEV block).
I kinda suspect a problem with the 'LOGIN HERE' which might have left
the device in an intermediate state.
I tried myself but couldn't reproduce it ! (either via LOGIN HERE or
FORCE followed by AUTOLOG .. ON ..).
Can a device be 'LOGOFF/FORCE PENDING' ? (never mind - self private joke
- I've had so many of those in my many years dealing with VM that I
couldn't resist - although this message applies to users, not GRAFs)..
What I'd be looking at to reproduce the problem would be to see if, in
your case, pressing enter - and getting the logo - changes anything -
as opposed to being shown the 'LOGOFF or DISCONNECT' message on the
problematic GRAF. Just in case it could make your relation with the ppl
handling the PMR easier !
Basically wondering if the device did clear properly the RDEV->VMDBK
relationship (since it is something I already encountered while trying
to do something similar under VM/SP a looooong time ago!)
(Geez.. I wish we still had the source code for all of this so we could
fix it ourselves !)
--Ivan
