Re: Power down schedule

Have you verified that the ENDTCP actually worked or is the QTCPIP job in
the QSYSWRK sybsystem still sitting there with a status of END ?
I have seen several times on V4R4 and V4R5 (admittedly when the PTF cum
level is a little old), especially with the model 150, cases where TCP/IP
hangs and will not end.  This prevents ENDSYS *IMMED or PWRDWNSYS *IMMED
from working, and you must force a power down or IPL from the front panel.
It often seems to be related to a PPP job (line QTPPANSnnn) first hanging
and being unable to end with either ENDJOB *IMMED or ENDJOBABN *IMMED.





ken shields <kjs@idirect.com>
Sent by: midrange-l-admin@midrange.com
2001/09/22 23:05
Please respond to midrange-l


        To:     midrange-l@midrange.com
        cc:
        Subject:        Re: Power down schedule


I normally ENDTCP, and power off the M36   mschine, I don't ENDSBS.
Unless the scheduler is part of the tcp group.
Ken

Eduard van den Braken wrote:
>
> You probably ended the subsystem with de scedular !
>
> Groetjes (Greetings)
>
> ===========================================================
> Name: Eduard van den Braken
> E-mail: e.vd.braken@hccnet.nl
> Town: Leusden -- the Netherlands
> Homepage: http://home.hccnet.nl/e.vd.braken/
> ===========================================================
>
> ----- Original Message -----
> From: "ken shields" <kjs@idirect.com>
> To: "MIDRANGE-L" <MIDRANGE-L@midrange.com>
> Sent: Saturday, September 22, 2001 4:58 AM
> Subject: Power down schedule
>
> >   I have set the power off schedule, as an example; to 5:00 pm to-day,
> > Ended all sub-systems, signed off the console, but it does nor power
> > down.
> > Model 150, V4R4
> > Sounds dumb, but what have I not done?
> > --
> > Best Regards
> > Ken Shields