output of ind q when the guest "freezes" (note, the guest is s99lxd02):
ind q S99LXD02 Q0 IO 00353503/00353486 MAINT Q1 R00 00001226/00001202 TCPIP Q0 R 00001671/00000746 SLES8-31 Q3 IO 00010925/00013077 S99WBF01 MP02 Q3 PS 00000000/00000000 S99WBF01 Q3 IO 00059978/00071598 SLES8-31 MP02 Q3 PS 00000000/00000000 S99MPRT1 MP02 Q3 PS 00000000/00000000 S99MPRT1 Q3 IO 00047904/00057496 SLES8-64 MP02 Q3 PS 00000000/00000000 SLES8-64 Q3 PS 00012579/00015066 DBTEST1 MP02 Q3 PS 00000000/00000000 S99KDD01 Q3 IO 00030705/00034903 DBTEST1 Q3 IO 00043527/00052140 S99KDD01 MP02 Q3 PS 00000000/00000000 S99KTR01 Q3 IO 00081825/00097167 S99KTR01 MP02 Q3 PS 00000000/00000000 DBTEST1 MP03 Q3 PS 00000000/00000000 S99KAHD1 Q3 IO 00072132/00084420 S99KAHD1 MP02 Q3 PS 00000000/00000000 S99KDT01 MP02 Q3 PS 00000000/00000000 S99KDT01 Q3 R 00188935/00196608 > -----Original Message----- > From: Phil Smith III [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 09, 2003 4:06 PM > To: Linux on 390 Port; [EMAIL PROTECTED] > Subject: Re: unresponsive linux guest > > > "Little, Chris" <[EMAIL PROTECTED]> wrote: > >no, the state was "RUNNING". i'll hit PA1 twice, put it > into VM READ, > >hit enter, and voila, it works. > > >also, when i disconnect it will function for a moment then become > >non-responsive. > > Are you forming E-lists? If that guest is larger than most, > it could be in E3 waiting for storage to open up. Do an IND > Q (INDICATE Q) on a privileged user and see if it's in E3. > > ...phsiii >
