RE: TCP/IP start automatically on IPL

Mark,

No, I meant what I wrote.  I have always been a little leery of using
autostart on my TCP/IP servers, so I would issue something like the
following commands in my startup program as below:

STRTCP STRSVR(*NO)

STRTCPSVR SERVER(*TELNET)
STRTCPSVR SERVER(*FTP)

This way my startup program was self-documenting and I didn't have to
worry about some rogue programmer changing the autostart value of a
particular server to *YES when I didn't want to start that server.  Kevin
didn't ask about the host servers so I didn't mention them in my reply.

I'm assuming you meant to write 'then' as opposed to 'the'.

Regards,
Andy Nolen-Parkhouse

> bounces@midrange.com] On Behalf Of MWalter@hanoverwire.com
> Subject: RE: TCP/IP start automatically on IPL
> 
> 
> With all due respect I think you mean STRTCP the STRHOSTSVR.
> 
> 
> Thanks,
> 
> Mark 


> Kevin,
> 
> Your easiest avenue would probably be to modify your startup program to
> STRTCP and then STRTCPSVR for the appropriate servers.  Current
> releases
> will startup TCP without these modifications, but at V3R2 you need to
> do
> it yourself.  My recollection of this release is that you may need to
> tinker with some DLYJOB commands in your startup program so that
> supporting programs are completely initialized before the TCP commands
> are issued.
> 
> Regards,
> Andy Nolen-Parkhouse