RE: Leaving IBM i on vs. sleep mode and fire it up now and then

Rob,

I agree with the sentiment more because those dang things won't end until
the communications time out hits anyway. Very annoying.

However you missed a big one, and since you're on your way to using remote
image catalogs you'll find this out the hard way.

Add the NFS server to your list. That thing ends almost as hard as *CIMON.



--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Tuesday, January 17, 2017 8:25 AM
To: Midrange Systems Technical Discussion
Subject: Re: Leaving IBM i on vs. sleep mode and fire it up now and then

IBM's response in my ticket:
We don't recommend customer to use ENDTCP to end CIMOM, may destroy the
server or result in odd situation.
It's better to use ENDTCPSVR *CIMOM, as they use for *MGTC. ENDTCPSVR will
give CIMOM time to end, not *immed kill the server.
Next time please ask customer to follow this procedure:
ENDHOSTSVR *ALL
ENDTCPSVR *MGTC
ENDTCPSVR *CIMOM
WRKACTJOB (to confirm CIMOM ends. If CIMOM doesn't end after 10 minutes(the
time is related to the load), then collect CIMOM log as this time, and use
ENDJOBABN, and contact us) ENDTCP ENDSBS *ALL *CNTRLD DELAY(120)


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Rob Berendt <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/17/2017 09:16 AM
Subject: Re: Leaving IBM i on vs. sleep mode and fire it up now and
then
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



... on multiple lpars...


Rob Berendt