On Tue, 7 Oct 2003 14:43:04 -0500, Little, Chris wrote:
> using set run on made things worse. as soon as i disconnect, the guest
> stops responding.
Sorry, I'd expect the opposite. It should behave like this:
When RUN is set ON, the following differences in virtual machine
management occur:
1. If your virtual machine is runnable, it executes instructions even
if a CP-initiated read is outstanding at your terminal
2. CP does not automatically initiate another terminal read when an
outstanding read is satisfied
3. If none of your configuration virtual processors are runnable, CP
does not automatically initiate a terminal read.
Initially, RUN is set OFF for all users except the primary system
operator.
RUN may not be set ON when a trace set is active. This ensures that
the virtual machine is not running during the terminal read that may
result when a trace trap springs. Similarly, RUN is automatically set
OFF when a trace set is activated.
> > You might also want to make sure
> > the guest's console is spooled so that you can see if
> > anything nasty is
> > happening while you're not looking.
> > Mark Post
How about Mark's hint?
---
Albert
