My recollection is that at some release upgrade in the past (V5R1 maybe?) STRTCP(*YES) was added to the IPL attributes. This caused some problems at the time because STRTCP was also in QSTRUP, causing various TCP error messages and random individual server conflicts. Seems like some of the NFS server daemons would just shut down if they were started twice, or something like that.
IIRC I was told at the time that LINDs and CTLDs that were set to vary on at IPL could or would also start TCP, so the decision was made to "fix" things so that STRTCP would only get called once, from the IPLA.
Regards,
Scott Ingvaldson
Senior IBM Support Specialist
Midwest Region Data Center
Fiserv.
-----Original Message-----
From: Jerry Adams [mailto:Jerry@xxxxxxxxxxxxxxx]
Sent: Tuesday, October 13, 2009 3:06 PM
To: Midrange Systems Technical Discussion
Subject: RE: Survey: STRTCP(*YES) or STRTCP(*NO) in IPL attributes
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.
--
Read my blog at
http://projectdream.org
--
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.
midrange.com
