FWIW i use the QSTRUP method...why? that way i can change the QSTRUPPGM
sys value to a temp program that does not start TCP for performing system
admin tasks that require multiple IPLs (i.e. hardware
replacement/maintenance, etc) without having to worry about users and
external applications trying to "tap into" the system. when i have
completed the tasks then i can change the sys value back to the real start
up program and do a quick IPL and we're back up and running. i just feel
that this is a "cleaner" method but that's JMO
Thanks,
Tommy Holden
From:
"Evan Harris" <spanner@xxxxxxxxxx>
To:
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Date:
10/14/2009 03:30 AM
Subject:
RE: Survey: STRTCP(*YES) or STRTCP(*NO) in IPL attributes
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
In what normal case would you want TCP and related servers generally
available and the machine visible on the network when any applicable
application servers or related jobs hadn't been started or run yet ?
In my opinion the server should come up in single user mode until the
startup process is run. Better to have network access, related servers and
any required production applications enabled as part of a single startup
process than to have two disconnected processes.
For that reason my preference is to have STRTCP in QSTRUP rather than
somewhere else.
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger Harman
Sent: Wednesday, 14 October 2009 12:23 p.m.
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Survey: STRTCP(*YES) or STRTCP(*NO) in IPL attributes
That's the way I used to do it - with the delays, etc. I may go back to
that just for finer control. Also considering externalizing the startup
process so it's configurable by database.
In looking at the help on CHGIPLA, it says the STRTCP command is run
when the IPL completes and the controlling subsystem is started. Pretty
much the timing I figured and that's why I had the DLYJOB's in there as
you mentioned.
nelsonp@xxxxxxxxxxxxx 10/13/2009 3:21:14 PM >>>
For all my customers, I've left the starting of the various TCP servers
in
QSTRUP with a monmsg to trap any response that the server is already
started.
Same goes with STRTCP(*YES). I also have DLYJOB statements in the
program.
There's no harm caused, so why not leave the statements in the program,
for
those just in case circumstances?
Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger Harman
Sent: Tuesday, October 13, 2009 4:53 PM
To: midrange-l@xxxxxxxxxxxx
Subject: 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.
at
http://archive.midrange.com/midrange-l.
midrange.com
