RE: ENDTCPSVR default of *ALL

What I really wanted to do was shut down all the *HTTP servers and missed
the correct parameter.


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Wednesday, December 19, 2018 7:47 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: ENDTCPSVR default of *ALL

IBM has a history of changing defaults. Mostly to stop users from shooting
themselves in the foot. (You know, people like you.) One example is that
default on SAVLIB was changed from *no on saving access paths a long time
ago. People may have been upset that their save time jumped but, by golly,
they didn't have to wait a week to use their system upon a restore while it
was rebuilding access paths.

Besides, starting with ENDTCPSVR *ALL is bad practice as some services take
a long time to stop and if you don't wait you corrupt your system.
Like *CIMOM; muck that up and you just lose telnet (like 5250). A rather
important thing to a few IBM i shops. *MGTC can also be a persnickety
child.


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: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 12/19/2018 08:36 AM
Subject: ENDTCPSVR default of *ALL
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Every now and then my fingers get faster than my brain. ENDTCPSVR command
default is *ALL meaning ALL the TCP servers so, NFS, CIMOM, FTP, HTTP,
etc.
but it also includes Telnet and a few others that are, well, important...



About once a year it happens, and it just did. Fortunately, it was one of
my own systems and I was the only one on the system but still, it's a
mistake that should not be made. I wish IBM would make the default *NONE.
Maybe a request in the future but in the past, I've been told they don't
change defaults since that might mess things up for some folks.



More of a warning than anything else pointing out that even very
experienced
system admins make mistakes and the systems need to be built to protect
itself.



Sounds more like the beginning of an *EXIT program than anything else.



--

Jim Oberholtzer

Agile Technology Architects