I guess I should have asked for a definition of "very vanilla environment."
IIRC the system with the problem is probably only running TELNET, SNMP, DDM, FTP, SMTP, HTTP, MGTC, NETSVR, DOMINO, HOSTSERVERS, NFS and ANYNET. It has one IP interface that connects directly to the switch and uses the network DNS. I don't believe that Domino is set to autostart.
What condition would make this system a "non-vanilla environment?"
Even if this is truly a "non-vanilla environment" does that constitute the requirement of STRTCP(*NO) in the IPL attributes? I have not heard this recommendation before, certainly not from IBM. STRTCP(*YES) is the shipped default. My first thought is that STRTCP(*NO) could wreak havoc on LINDs and interfaces that have Online at IPL(*YES). My concern is that this solution could potentially be worse than the original problem.
Regards,
Scott Ingvaldson
Senior IBM Support Specialist
Midwest Region Data Center
Fiserv.
-----Original Message-----
From: Lukas Beeler [mailto:lukas.beeler@xxxxxxxxxxxxxxxx]
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
midrange.com
