RE: Survey: STRTCP(*YES) or STRTCP(*NO) in IPL attributes

I used to have it in our startup but took it out in 2004. I've been
wrestling with this same issue since we got our new system but have left
it at IPLA.

Does anyone know at what point TCP/IP is started via the IPL attributes
in relation to the startup program getting called? I guess I'm
wondering if you can be certain TCP/IP is running before starting other
things in the startup program.

Jerry@xxxxxxxxxxxxxxx 10/13/2009 1:06:08 PM >>>

I let the IPL start TCP. I looked at my QSTRUP procedure and the
STRTCP is there but commented out. Apparently I did that a shade over
two years ago, but for the life of me I cannot recall why. Anyway, I
haven't had any problems with TCP starting too soon; i.e., causing
conflicts or such.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lukas Beeler
Sent: Tuesday, October 13, 2009 1:39 PM
To: Midrange Systems Technical Discussion
Subject: Re: Survey: STRTCP(*YES) or STRTCP(*NO) in IPL attributes

On Tue, Oct 13, 2009 at 20:22, Ingvaldson, Scott
<scott.ingvaldson@xxxxxxxxxx> wrote:

In this day and age does anyone really have a "very vanilla
environment?

We do, at our prod machines internally and at all our customers
machines.

I spent a lot of time a few years back getting
STRTCP(*YES) to work properly so that it wasn't starting twice and
creating miscellaneous server conflicts. I'm curious what everyone

else

thinks and does.

We use STRTCP(*YES) at the around 100 machines that are under our
control, and have never seen any issues with it. Or at least not in
the past 4 years.