Re: STRTCPSVR SERVER(*SSHD),MONMSG MSGID(CPF0000)

[DrFranken <midrange@xxxxxxxxxxxx>]

Not a big fan of excessive delays. They are either Juuuuuust a tick too 
short or WAY too long.  To me it makes MUCH more sense to CHGIPLA to NOT 
start TCP and then control all of that in my startup job. First start 
IP. Then start the needed IP interfaces depending on the system being 
the production node or the HA node or perhaps is in a limited startup 
mode I have defined. Then move on to servers etc.

It also means that when folks use CHGxxxA to set some server to start at 
the next IPL, or not, I don't care. I start it in my startup job or 
don't as needed.

With the startup job under change control I now know who's making 
changes and they need to be approved.

        - Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 11/26/2018 11:24 AM, Kendall Kinnear wrote:
> I typically put a 3 to 5 minute delay in the startup program after I do 
> the STRTCP command. Then I go on to run the STRTCPSVR, STRHOSTSVR, and 
> any other commands related to communications.
>
> Kendall Kinnear
>
> On Mon, 26 Nov 2018 10:18:55 -0600, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> 
> wrote:
>
> > My best guess would be that it's trying to start before TCP is ready.  
> > What does the joblog show?
> >
> > If you want to auto-start SSH, what not just set the server to start 
> > with TCP/IP?
> >
> >
> >
> > -----Original Message-----
> > From: Booth Martin [mailto:booth@xxxxxxxxxxxx]
> > Sent: Sunday, November 25, 2018 5:01 PM
> > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > Subject: STRTCPSVR SERVER(*SSHD),MONMSG MSGID(CPF0000)
> >
> > I was asked:
> >
> > STRTCPSVR SERVER(*SSHD)
> > MONMSG MSGID(CPF0000)
> >
> > "it works from command line
> > but not from the startup program"
> >
> > ------------------------------------------=
> >
> > Any idea what he needs to know about this issue?