z/VM'ers,

After a few searches and actually scanning the CP commands and utilities 
manual, hopefully I can get some help with this z/VM related question.  If I 
have a z/linux guest called "ztrash01", I can logon to z/VM as ztrash01, IPL 
xxx, logon to Linux and shutdown -h now, and if I'm still logged on as console 
from my 3270 terminal session, enter logoff.  No problem.

The "why" I want to do the following is to potentially stress test some 
applications by forcing off a z/Linux guest (crash) and then eventually trying 
to automate and re-IPL, but first I gotta be able to do some basic z/VM CP 
commands below.

I read the LOGON in the CP commands and Utilities reference, but I'm doing 
something wrong (other than trying to trash and stress test my guest).

I'm still playing with test systems, but from a z/VM CP perspective, for now 
the Linux guest "ztrash01" is shutdown and halted, but "ztrash01" is still 
logged onto z/VM.

1. If I'm logged on as "operator" to z/VM, I can issue CP command "q n" and see 
that guest ztrash01 is logged onto z/VM and DSC (disconnected).
2. Still as operator, I can issued CP command "force ztrash01 logoff immed" and 
this logs the guest, ztrash01, off of z/VM (FORCED BY OPERATOR)
3. Still as operator, a "q n" verifies that the guest is gone (i.e. logged off 
z/VM)
4.  Now, as operator, instead of going to another z/VM terminal session and 
logging on as "ztrash01", still as operator, I would like to cause the guest 
"ztrash01" to logon (and eventually IPL).

To cause the IPL of guest "ztrash01" at LOGON, I believe I can put that in the 
PROFILE EXEC (e.g. IPL xxx) at the end, but how (if at all) can I cause the 
guest to be logged on (opposite of FORCE) while being logged on to z/VM as 
operator?

Thanks in advance,
Tom B.



----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to