It's always been with QUSRWRK. That process has not changed in quite some
time, might even be nearly the same as it was on the System/38, I don't
quite remember.
Some sites never start QUSRWRK (a mistake in my view) so those critical jobs
wind up running all over and get started as needed by system functions.
Some of the functions never start properly without QUSRWRK.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Monday, March 30, 2015 6:20 AM
To: Midrange Systems Technical Discussion
Subject: RE: IPv6 disable - yes or no , and which method
Dependencies like this are why I'm often loathe to change the startup
program. IBM has been known to change the order of startup at release
change. I believe ?TCP? was started with an autostart job on one subsystem
but then moved to another at one time. Things like this.
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: 03/29/2015 08:52 AM
Subject: RE: IPv6 disable - yes or no , and which method
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
TCP ordinarily starts before/with QUSRWRK and QSYSWRK. Without
significant
work management that's where most of the TCP applications run.
So start TCP and QUSRWRK/QSYSWRK all in the same block of code. Subsystems
first (they start fast anyway, it's the prestart jobs that take a bit) If
you're really after control, then set all the TCP application servers to
not
start automatically but then start them manually in the startup program.
That way it's documented, and you can start/stop what you need, not what
was
set to automatically start by someone else.
Make sure to include STRHOSTSVR (towards the end of the program) in your
start up as well. Depending on how fast TCP starts (you might consider a
60
second delay) the host servers sometimes don't behave.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Friday, March 27, 2015 4:03 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: IPv6 disable - yes or no , and which method
Where in QSTRUP should STRTCP be placed, before or after STRSBS.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Friday, March 27, 2015 4:21 PM
To: Midrange Systems Technical Discussion
Subject: Re: IPv6 disable - yes or no , and which method
Same here. Custom startup for all but the simplest systems these days.
- Larry "DrFranken" Bolhuis
www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com
On 3/27/2015 1:04 PM, Jim Oberholtzer wrote:
Most of my customers choose to start TCP manually in the start up
program where they force IPV6 to not start.
So, your option 3.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
--
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.
--
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
