I didn't explain something very well in my initial post.. In the 2nd paragraph, where I talk about a CMS guest..
I meant to say that I could have a guest running CMS who could captures MSGs or SMSGs sent to it -- and have a RECYCLE EXEC it ran if it received a message of 'recycle' from a Linux (or any other type of) guest.. The RECYCLE EXEC would: - Accept an argument of the userid to be recycled - Issue a CP SIGNAL SHUTDOWN userid (userid = the userid who sent the msg) - Go into a loop and wait for CP Q USERID userid to get an RC45 (either the Linux guest will logoff or the SIGNAL timeout will log it off) - CP XAUTOLOG userid once the above loop ends Let's say we set up a user called RECYCLVM who is a CMS guest who waits for a MSG of 'RECYCLE'... (via WAKEUP) .. it would call RECYCLE EXEC passing the userid of the user who sent the message. So now a Linux guest can issue: 'vmcp msg recyclvm recycle' I know I can do that fairly easily - but I think z/VM itself could do it fairly easily too. Whether it's worth the development effort -- umm..... Maybe the process above is cheapest ;-) Thanks - Scott On Wed, Oct 29, 2008 at 6:17 PM, Scott Rohling <[EMAIL PROTECTED]>wrote: > Is there a 'native' way to have your guest brought down and autologged? I > suppose I'm looking for a CP command which instead of allowing the guest to > say.. IPL - actually signals it off (respecting signal times) and brings it > immediately back. This would be nice for Linux guests -- say their > directory is updated to allow more memory ... if they could issue 'vmcp > recycle' at their convenience - it could be very handy. > > I know can I can have a CMS guest sit there - wait for a msg/smsg - and do > it fairly easily.. The Linux guest would issue "msg recyclvm recycle" for > example. The recycle routine on recyclvm would issue the signal shutdown > -- wait for the guest to go down - and then immediately xautolog it. > > Just looking for ideas.. thanks! > > Scott Rohling > > >
