Re: Some more ethernet questions

["Jim Franz" <franz400@xxxxxxxxxxxx>]

IBM has been changing recommendations about QSTRUP in almost
every release. The Knowledge Base has the following articles, which
not only explains what is going on, but also best practices for getting
tcp functions up & running. I look for this on every release upgrade.
Changing the IPL Start-Up Program - V5R1M0
Changing the IPL Start-Up Program - V4R4M0/V4R5M0
Changing the IPL Start-Up Program - V4R2M0/V4R3M0
Changing the IPL Start-Up Program - V3R7M0/V4R1M0
Changing the IPL Start-Up Program - V3R2M0
scan for qstrup to see them all.
jim
----- Original Message -----
From: "Philipp Rusch" <Philipp.Rusch@rusch-edv.de>
To: <midrange-l@midrange.com>
Sent: Thursday, March 21, 2002 8:34 PM
Subject: Re: Some more ethernet questions


> Damn, Neil is always one step ahead,
> I thought the sun is rising earlier with us in germany than in canada ?
>
> :-), ... Philipp
>
> Neil Palmer schrieb:
>
> > Starting at V4R2 the STRTCP command automatically runs STRHOSTSVR.
> > At V4R3 IBM were recommending that instead of adding STRTCP to the
startup
> > program, you add an autostart job entry to subsystem QSYSWRK using an
IBM
> > supplied job description:
> > ADDAJE SBSD(QSYSWRK)  JOB(STRUPTCPIP)  JOBD(QSYS/QTOCSTRTCP)
> >
> > Starting with V5R1 TCP/IP startup is controlled via an IPL attribute
> > (CHGIPLA).
> >
> > A quick way to see what TCP/HOST/NFS servers are started when TCP starts
> > is to RUNQRY *NONE QATOCSTART
> > You can use UPDDTA (or WRKDBF, etc.) to change the *YES/*NO values in
that
> > file if you want.  Make sure you keep the *YES/*NO in uppercase.
> > The other way to change ALL the startup values requires use of OpsNav as
> > not all can be set from CFGTCP, #20
> >
> > ...Neil
> >
> > Hello from germany,
> >
> > answers inline :
> >
> > Rosewood schrieb:
> >
> > > Thanks to a lot of help from you guys, all has been going well.  If
any
> > > of yall come through Wichita, KS some time (and im over 21 then) look
me
> > > up, Ill buy ya a beer.
> > >
> > > I have a few more questions.
> > >
> > >   1:  How do I get TCP/IP to run on IPL?  PS - The agents that use
these
> > > AS400s don't need nor use them for HTTP/POP/SMTP/FTP ETC servers - can
> > > these different ones not be started up always as well ? (I think I got
> > > that figured out from TCPADM screen).
> >
> > There is a startup program which is call when the system starts its
> > controlling
> > subsystems, this is done during a sucessful IPL procedure.
> > The location/name of the program that is called is controlled by a
system
> > value
> > (WRKSYSVAL  QSTRUPGM), the object defined there has to be a valid
> > CL-PGM. There is an IBM-supplied template for this, which you can
retrieve
> > to have a starting point for your own self-made startup program.
> > (RTVCLSRC QSYS/QSTRUP, I put this source on QGPL/QCLSRC(QSTRUP))
> > I usually do NOT modify this and recompile, instead, I always leave the
> > original
> > from IBM in place (because of release changes) and in the first line of
my
> > own
> > startup PGM  I do a CALL on this one to have the "IBM-things" done
before
> > I
> > add on my "specials". Like this, you never loose modifications on an
> > upgrade of
> > your OS/400, you just have to change the sysval again ...
> > How is TCPIP being started then ?
> > For me the code in my QSTRUPTCP called PGM is looking like this
> >
> >     PGM
> >     CALL (QSYS/QSTRUP)
> >     MONMSG (CPF0000)
> >     STRTCP
> >     MONMSG (CPF0000)
> >     STRHOSTSVR (RCDPCL *TCP)
> >     MONMSG (CPF0000)
> >     . . . .
> >
> >     MONMSG (CPF0000) is only to avoid any messages to keep the system
from
> > starting up correctly, because some job is waiting for an answer in
> > QSYSOPR  ...
> >
> > HTH, greetings, Philipp Rusch
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>