This might be too simplistic, but my first thought would be to write a Command
Analyzer Retrieve Exit Program
<https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/apis/xcartv.htm>
to
be called whenever the ENDTCPSRV command is run. The program could check
for 1) is SERVER(*ALL) in effect and 2) is the command being run
interactively. If Yes to both checks then prompt to verify the user really
wants *ALL. If the user did not mean to use *ALL then the exit program
could send an escape above the command analyzer to stop the request. This
would not require a CHGCMDDFT, would not disrupt any batch jobs that use
ENDTCPSRV and really do mean *ALL, but would detect interactive use that
may not have been intended. CL programs being run interactively and using
ENDTCPSRV SERVER(*ALL) intentionally would be impacted, though perhaps a
check of the jobs call stack might help here. It's been a while since I
wrote this type of exit program so I can't recall exactly what the call
stack looks like when the exit program is called.

You could of course use the Command Analyzer Change Exit Program
<https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/apis/xcachg.htm>
rather
than the Retrieve, but it has some additional considerations.

While on the subject of Command Analyzer exit programs, one I found handy
was an exit program off of CHGCMDDFT. I was at an account where multiple
development teams where sharing the same system and someone would
occasionally use CHGCMDDFT (which other developers sometimes found just a
bit disruptive). The exit program would do things like 1) log who changed
what when and 2) send an email to interested parties notifying them of the
change. In this particular case I also had to add a filter for one specific
command. There was some software product that, as part of its processing,
would use CHGCMDDFT on one of its own commands. I, and others, got rather
sick of emails related to this command rather quickly.

Bruce

On Wed, Dec 19, 2018 at 10:24 AM Rob Berendt <rob@xxxxxxxxx> wrote:

And the writing could be as simple as CRTDUPOBJ with CHGCMDDFT


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 11:08 AM
Subject: RE: ENDTCPSVR default of *ALL
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Now that is a good idea......Thanks Buck.

Why I never thought of it, I don't know.........


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Buck
Calabro
Sent: Wednesday, December 19, 2018 10:06 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: ENDTCPSVR default of *ALL

On 12/19/2018 8:36 AM, Jim Oberholtzer wrote:

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...

I wrote STR/ENDAPACHE for this very reason.

--
--buck

http://wiki.midrange.com
Your updates make it better!

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at https://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:
https://amazon.midrange.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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://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: https://amazon.midrange.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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://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: https://amazon.midrange.com




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.