Notes on the Hung User Problem
 
IND Q  - To find it.  User will be in Q0, which is normally for service
         virtual machines like PVM, AUTOLINK, YVETTE, etc.  If a user
         shows up there, chances are we're in the loop state.
 
LOCATE userid
D the VMDBK+358 - This is the console RDEV block.  It should be zero.
                  If it's not, you don't have this loop condition.
 
QDEAD  - A Steve Estes quick and dirty exec that does a Q L0000-LFFFF
         and looks for any logical devices which don't have a host
         associated with them.  If the user above is shown, then you
         definitely have the loop condition.  Now see if it's the simple
         case or a more complicated case.
 
QDEAD userid - My enhancement to Steve's exec that, while looping
               through the CP response, also looks for any logical
               devices in use by that user.  This is to catch any ghost
               logical devices the user might have gotten logged on to
               as, but then disconnected from.  I think this would have
               caught Yorktown's case where they got a STK017 after
               zapping free a user. You should only find one logical
               devices in use by the userid, that one being the one
               that's dead.  If there are others, try dropping them
               via SMSG PVM or SMSG YVETTE or whatever.
 
KLDEV Lnnnn  - A Leoda exec that finds and displays the RDEVBK for the
               given logical device (it finds it by going through the
               radix tree control block structure anchored by HCPLSOLX.
               Make sure it's the console for the user in question.
               Look at +8 - It should point to a VDEV.
               Look at +9E.2 and +A0.2 - It should be the same logical
                                         device number as above.  If
                                         it's not, you don't have the
                                         simple case.  You have a more
                                         complicated case and you could
                                         cause a STK017 if you zap
                                         things.
 
LOCATE userid 009 - Make sure the VDEV address is the same as the
                    VDEV address you saw at LDEVBLOK + 8.
 
D the VDEV.60 - Look at +14 - It should point to the user's VMDBK.
                Look at +58 - It should be zero, but it's supposed to
                              point at the LDEVBLOK.  If it's not zero,
                              it could also be a more complicated case.
                              If it's pointing to a RDEV that's not the
                              LDEVBLOK above, then watch out.  There's
                              two of those suckers floating around and
                              you want only one.  Try dropping the
                              second one somehow.
 
If all the above looks right, then it should be ok to zap the LDEVBLOK.
You want to zap the LDEVBLOK + 8 to zero.  That was the pointer to the
VDEV.