Yup, that pretty much covers it. If CMS wasn't running, you'd have to keep hitting enter to see if any messages arrived, etc. (Anyone remember using the old tty interface? I had an exec that would SLEEP so I would get messages and allow me to enter some commands)
Bob Bates Enterprise Hosting Services w. (469)892-6660 c. (214) 907-5071 "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Jack Woehr Sent: Friday, February 06, 2009 2:18 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: lOGON WITH OUT ipL'ing Michael Coffin wrote: > The "hang" you are referring to is the VM READ that occurs after you > IPL CMS, right? > Yah, you and Richard Schuh have confirmed what dawned on me finally today :) So why does CMS alternate between "VM READ" and "RUNNING" if I just sit there popping CR's into the terminal? My guess: D'oh, CMS is "RUNNING" and then you hit CR which "interrupts" it (because this is the historical CP handling of terminals, that programs "run" and are "interrupted" by the terminal) and that's when you get VM READ and then you hit CR and CMS is "RUNNING" again? -- Jack J. Woehr # I run for public office from time to time. It's like http://www.well.com/~jax # working out at the gym, you sweat a lot, don't get http://www.softwoehr.com # anywhere, and you fall asleep easily afterwards.
