Yes - a perhaps less flagrant a violation would be a NODROP option to tell it to not drop dialed devices when it does the reset. Another possibility would be to have some type of special device definition that would retain the connection across a reset, thus eliminating the need for an option on the IPL command.
Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Jim Bohnsack Sent: Friday, August 03, 2007 8:29 AM To: [email protected] Subject: Re: PROFILE EXEC to bring up second level VM I "think" that you would be introducing an architectural violation. I am pretty sure that a real s/360 thru z9 ipl does a channel reset on all channels (chpids). Jim Michael Coffin wrote: > Whoops, you are correct Richard. I mis-spoke. The PROFILE EXEC > actually attaches a real 3270 (I still have a couple of COAX connected > PC's with 3270 cards that I keep around for this) and doesn't use a > DIALed 3270. > > Looking down the road to the day that I don't have the COAX connected > cards, it sure would be nice if the IPL process could skip doing a reset > on any device passed in the LOADPARM operand (or maybe have a new > option, NORESET so you could IPL 2007 CLEAR LOADPARM 1120 NORESET and > have it not reset device 1120). > > -Mike > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Schuh, Richard > Sent: Thursday, August 02, 2007 3:05 PM > To: [email protected] > Subject: Re: PROFILE EXEC to bring up second level VM > > > Correct me if I am wrong, but if you dial before the IPL of the VM > system, the IPL will drop the connection. "IPL dev STOP" will get you > past the IPL reset and give you the opportunity to dial the system. Then > a BEGIN resumes the IPL simulation. > > How would you tell it to SLEEP after the IPL command/reset? > > Regards, > Richard Schuh > > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Michael Coffin > Sent: Thursday, August 02, 2007 11:53 AM > To: [email protected] > Subject: Re: PROFILE EXEC to bring up second level VM > > Ditto. I usually set up my 2nd level systems to be XAUTOLOGged and dial > into the SPECIAL 3270 port that will become the system console (just put > a little SLEEP in the profile exec to give you time to dial the port). > It also eliminates the "am I on first or second level CP" question when > you are dialed, particularly when doing things like SHUTDOWN! :) > > -Mike > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Schuh, Richard > Sent: Thursday, August 02, 2007 11:38 AM > To: [email protected] > Subject: Re: PROFILE EXEC to bring up second level VM > > > I also take the approach of keeping the logon terminal separate from the > OPERATOR console of the 2nd level system. I got in the habit of doing > this in the dark ages when it was sometimes (frequently) necessary to > trace the 2nd-level system's CP. It does have the advantage of > separating the first and second level systems from each other. > > > Regards, > Richard Schuh > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Jim Bohnsack > Sent: Thursday, August 02, 2007 5:59 AM > To: [email protected] > Subject: Re: PROFILE EXEC to bring up second level VM > > Rich--I take a different approach from the other respondents. I define > 3270 type terminals with SPECIAL statements in the directory entry of > the id I use a 2nd level test machine, i.e.: > > * GRAFS TO MAKE THE SYSTEM ACCESSABLE: > * > SPECIAL 1E20 3270 > SPECIAL 1E21 3270 > SPECIAL 1E22 3270 > SPECIAL 1E23 3270 > > In the PROFILE EXEC, I have the following: > > SAY 'When you see IPL STOP, DIAL TST53 on another terminal' > SAY '...and come back to this screen and enter B' > 'CP IPL 301 CLEAR STOP LOADPARM 1E20' > > I really like this better than trying to keep track of which level of VM > > I'm talking to. You need to have an 'ENABLE ALL' in the PROFILE EXEC of > > the OPERATOR id that comes up. > > Jim > > Rich Smrcina wrote: > >> OK, I seem to be having a recall problem... >> >> Here is the essence of a PROFILE EXEC that I'm using to bring up z/VM >> 5.3 under z/VM 5.2: >> >> 'CP SET RUN ON' >> 'CP TERMINAL HOLD OFF' >> IPLCMD='TERM CONMODE 3270'||'15'X||'IPL C20' >> 'CP 'IPLCMD >> >> It all works fine until I DISC the z/VM 5.3 OPERATOR and close the >> session. Then z/VM 5.3 stops. When I log back in to the virtual >> machine it is all good, it picks up right where it left off. >> >> What's missing from the PROFILE EXEC to keep it running when the >> > console > >> goes away? >> >> > > > -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
