TCP startup on IPL
Joe W. Holt
Can anyone tell me how to have tcp start with the appropriate servers
after an IPL. I submitted jobs in the QSTRUP program that should do it
but apparently when I returned this morning my tcp network was down but
the ipl was successful? I know how to set the appropriate servers to go
active, just really need to have strtcp work.
--
*******************************
Joe W. Holt
IS Specialist
ppl...@oklahoma.net
*******************************
Phillip Lyles
>Can anyone tell me how to have tcp start with the appropriate servers
>after an IPL. I submitted jobs in the QSTRUP program that should do it
>but apparently when I returned this morning my tcp network was down but
>the ipl was successful? I know how to set the appropriate servers to go
>active, just really need to have strtcp work.
Hi,
Don't know if this is your problem or not but we had our start-up set to
first start tcp and then start the host server, we had to add a 5 minute
delay between the two jobs to get host server up. Hope this helps.
Phillip Lyles
prl...@surry.net
Paul Nicolay
Hi Joe,
Just add STRTCP and MONMSG CPF0000 behind the start of subsystem QSERVER.
In addition, I also add a delay of about 10 minutes so that QSERVER can
complete succesfully. Otherwise the startup of TCP/IP seems to behave a
bit strangly from time to time.
This all results in the following startup sequences;
...
STRSBS SBS(QSERVER)
MONMSG (CPF0000)
DLYJOB DLY(600)
MONMSG (CPF0000)
STRTCP
MONMSG (CPF0000)
DLYJOB DLY(120)
MONMSG (CPF0000)
STRHOSTSVR *ALL
MONMSG (CPF0000)
...
Remember to give QPGMR *USE authority to STRHOSTSVR as well.
Kind regards,
Paul
___________
Joe W. Holt <ppl...@oklahoma.net> wrote in article
<341E8B9F...@oklahoma.net>...
> Can anyone tell me how to have tcp start with the appropriate servers
> after an IPL. I submitted jobs in the QSTRUP program that should do it
> but apparently when I returned this morning my tcp network was down but
> the ipl was successful? I know how to set the appropriate servers to go
> active, just really need to have strtcp work.
>
> --
> *******************************
> Joe W. Holt
> IS Specialist
> ppl...@oklahoma.net
> *******************************
>
>
>
The contents of this message express only the sender's opinion.
This message does not necessarily reflect the policy or views of
my employer, Merck & Co., Inc. All responsibility for the statements
made in this Usenet posting resides solely and completely with the
sender.
Mark Phippard
Joe,
There are a couple of things.
1) Authority. QSTRUP runs under QPGMR which generally doesn't have
authority to the STRTCP and STRHOSTSRV commands. I changed my startup
program to be owned by QSECOFR and run with adopted authority. You can
also change the authority to the commands.
2) Timing. The QSERVER subsystem must be completely started before STRTCP
can execute, and STRTCP must be completely finished before STRHOSTSRV can
execute. (All of these processes do a little bit asynchronously, so they
are not necessarily finished when the command completes). Simply add a
DLYJOB for 60 to 300 seconds before each of these commands in the startup
program.
HTH,
Mark Phippard
SoftLanding Systems
Reeve Waldock
Joe,
I'm sorry but I don't all the details to hand although the QSTRUP procedure
runs via QPGMR and the servers require more authority. We had the same
problem only a few days ago - our short term fix is to use a job scheduled
entry, from QSECOFR, since all IPLs are scheduled. I'm currently looking
into using adopted authorities...
Hope this may help!
Reeve Waldock.
Nick V. Kosmas
I'm having the same problem and found a solution on the AS/400 web site.
Per APAR # II10239, you must grant *USE authority to QPGMR user for the
STRHOSTSVR command, using the grant object authority command. The command
in the APAR was as follows: GRTOBJAUT OBJ(QSYS/STRHOSTSVR) OBJTYPE(*CMD)
USER(QPGMR) AUT(*USE).
I've issued that command and will be testing it tonight.
I hope this helps,
NickK
Reeve Waldock wrote in article <01bcc45c$5f863ec0$da5095c1@vectra66>...
Reeve Waldock
Joe,
We've had a similiar problem at our site. I'm pretty sure the problem lies
with authority but until I've fixed the problem we're going to continue to
use a JSE set to run after the scheduled IPL to start the servers.
Joe W. Holt
Thanks Nick, Reeve
I will definitely try that asap. I really appreciate the responses.
Joe Holt
Nattapong Mongkolprasit
Reeve, as far as I understand from your message, you can IPL but TCP/IP does
not start, automatically, but if you start it manually afterthat, it works
well, right?
If the authority of QPGMR is not relevant. I doubt that you might be using
IPCS card instead of normal LAN card. If you are using IPCS card, you need to
provide a delay time after File Server on IPCS is starting up. You have to put
the following:
QSYS/DLYJOB DLY(xxx) ; Where xxx is number of delay
second
Time delay depends upon model of your IPCS, memory installed on IPCS and type
of your server. It varies from 60 to 180 seconds. You may find out the exact
time by first vary of your Network Server, then check the time to vary on until
its status is ACTIVE.
You have to put this line below STRSBS SBS(*ALL) or after every subsystems had
been started.
----------