× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




ENDNFSSVR SERVER(*ALL)
ENDJOBTIMO(30)

It's counterpart is:

STRNFSSVR

--
Jim Oberholtzer
Agile Technology Architects


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

I don't see NFS in the list of (7.1) server applications on the ENDTCPSVR.


Gord

On Tue, Jan 17, 2017 at 9:32 AM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

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
--
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:12 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>



I meekly disagree with the great doctor here. I have had corruption
by not ending *CIMOM first.
<snip>
But to take the time to end all the IBM subsystems and jobs and IP
interfaces and all that just isn't needed.
</snip>

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: DrFranken <midrange@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/17/2017 09:08 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>



I'd make it a fair bet that I'm in the 99.99th percentile when it
comes to number of PWRDWNSYS run career to date. I would guess I've
used *CNTRLD less than a handful of times.

The only time I can remember *IMMED with all applications up and
running and users on though was when the machine was getting water
poured on it from above. We chose potential application corruption
over potential total system failure. Yes we pissed off MAPICS but the
hardware lived.

I think the bottom line is what's still running when you use *IMMED. I
would NEVER recommend that with any open applications. Shut down
QINTER and QBATCH and end web servers and the many myriads of things
customers run today. But to take the time to end all the IBM
subsystems and jobs and IP interfaces and all that just isn't needed.

I have written a number of programs for customers to do PWRDWNSYS.
These take into account what they normally have running and bring
those things down neatly before eventually using *IMMED. Or as Jim
mentioned the alternative is an exit program. Issue with the exit
program in my mind is when I want it down NOW I may not want an exit
program lollygagging around so you may need code in that program to
check for a NOW NOW NOW flag of some sort.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 1/16/2017 8:01 PM, Richard Schoen wrote:
I guess you've never experienced the never ending *CNTRLED shutdown
:-)

Whatever works for you. Just stay away from the white button.

In 28 years with AS/400 and IBM i I've never had an issue with
PWRDWNSYS


*IMMED, but I am no longer in charge of the hardware so I guess it no
longer matters.

Why do you still need the V5R4 box ? Still compiling back to V5R3
or
V5R2 ?

Regards,


Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD




--
Gord Hutchinson
TST Overland Express
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.