|
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.