I'm unsure what you mean by "Functioning again". The START/STOP is simply spooling of the console.
On Thu, Aug 27, 2009 at 10:14 AM, Huegel, Thomas <[email protected]> wrote: > Or use FOR zosmachine CMD SPOOL CONSOLE START. > > ------------------------------ > *From:* The IBM z/VM Operating System [mailto:[email protected]] *On > Behalf Of *Michael Coffin > *Sent:* Thursday, August 27, 2009 9:08 AM > *To:* [email protected] > *Subject:* Re: Console TERM STOP > > Well, according to those results you are logged on to that virtual > machine (on LDEV L0003), so you COULD #CP SPOOL CONSOLE START, or from a > CLASS C user issue CP SEND CP zosmachine SPOOL CONSOLE START (where > zosmachine is the name of the virtual machine). > > -Mike > > -----Original Message----- > *From:* The IBM z/VM Operating System [mailto:[email protected]] *On > Behalf Of *Daniel Allen > *Sent:* Thursday, August 27, 2009 9:54 AM > *To:* [email protected] > *Subject:* Console TERM STOP > > When I do a 'Q CONSOLE' for a z/OS machine running under z/VM 5.4, here are > the results: > > q console > CONS 1320 ON LDEV L0003 TERM STOP HOST TCPIP FROM 10.30.22.48 > 1320 CL T NOCONT NOHOLD COPY 001 READY FORM STANDARD > 1320 TO D00A PRT DIST D00A FLASHC 000 DEST OFF > 1320 FLASH CHAR MDFY 0 FCB LPP OFF > 1320 3270 NOEOF CLOSED NOKEEP NOMSG NONAME > 1320 SUBCHANNEL = 0000 > > How can I get it functioning again ? > > I really do not want to IPL the z/OS machine, if possible. > > -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
