We use CONS=cuu in our SAIPL panels and still get VM shutdown messages
on all screens defined as operator consoles in SYSTEM CONFIG? z/VM 5.2

On Mon, Mar 31, 2008 at 9:39 AM, Schuh, Richard <[EMAIL PROTECTED]> wrote:
> And do not forget, if you have a "cons=addr" in your IPLPARMS on the
> SAPL screen, it overrides your config file specifications for both the
> operator and emergency consoles.
>
> Regards,
> Richard Schuh
>
>
>
>
> > -----Original Message-----
> > From: The IBM z/VM Operating System
> > [mailto:[EMAIL PROTECTED] On Behalf Of Jim Bohnsack
> > Sent: Monday, March 31, 2008 5:30 AM
> > To: IBMVM@LISTSERV.UARK.EDU
> > Subject: Re: AW: Unexpected FORCE starts
> >
> > I don't have an Emergency_Message_Console stmt in my SYSTEM
> > CONFIG but I always get the complete set of shutdown messages
> > on the operator console which is on an address defined as
> > Operator_consoles.  The CP Plng and Admin guide has this as a
> > Usage Note in the Emergency_Message_Console
> > section:
> >
> > If you do not specify an EMERGENCY_MESSAGE_CONSOLES
> > statement, CP sends all emergency messages to the operator
> > consoles that you listed on the OPERATOR_CONSOLES statement
> > in the system configuration file or the RIOGEN
> > macroinstruction in HCPRIO, before IPL. During IPL, CP checks
> > all the consoles in this list to see if they are operational.
> > If they are, CP includes them in the list of operator consoles.
> >
> > Jim
> >
> > Rempel, Horst wrote:
> > > Hello,
> > > as far as I know you have to define your new OSA-ICC
> > console in the =
> > > system config file as Emergency_Message_Console.
> > > Otherwise you will not see the shutdown messages.
> > >
> > > kind regards
> > > Horst Rempel
> > >
> > >
> > > -----Urspr=FCngliche Nachricht-----
> > > Von: The IBM z/VM Operating System
> > [mailto:[EMAIL PROTECTED]
> > > Auftrag von O'Brien, Dennis L
> > > Gesendet: Sonntag, 30. M=E4rz 2008 06:24
> > > An: IBMVM@LISTSERV.UARK.EDU
> > > Betreff: Unexpected FORCE starts
> > >
> > >
> > > We've occasionally had to FORCE start a system after a planned
> > > shutdown, and we can't find any reason why the shutdown
> > wouldn't have
> > > completed successfully.  We're thinking maybe the operator
> > didn't wait
> > > for the shutdown to finish before doing the IPL.  We
> > recently changed
> > > from 3174 console controllers to OSA-ICC.  I've noticed
> > that when the
> > > shutdown is complete, we no longer see the completion
> > message on the
> > > emulator session.  Instead, we see a banner like this:
> > >
> > >  **    OSC Index 3  connected to OSC0180 via IP Addr
> > > xxx.xxx.xxx.xxx:1024    **
> > >  **        LT Index=3D2  CSSID=3D 0 MIFID=3D 7 CU=3D0  UA=3D0   =
> > > LUName=3DLxxxx180
> > > **
> > >  **       Type=3D2094-S54 Mfg=3DIBM SN=3D0000000xxxxx CHPID=3D66 =
> > > Status=3DActive
> > > **
> > >
> > > I'm wondering if this banner appears BEFORE the shutdown
> > has finished.
> > > Does it?  If it does, I suppose I'll have to tell the operators to
> > > check for a PSW wait state on the HMC before they IPL.
> > >
> > >                                                        Dennis=20
> > >
> > > "A society that gets rid of all its troublemakers goes
> > downhill."  --
> > > Robert A. Heinlein
> > >
> > > =20
> > >
> > >
> >
> >
> > --
> > Jim Bohnsack
> > Cornell University
> > (607) 255-1760
> > [EMAIL PROTECTED]
> >
>

Reply via email to