Re: Client Access

[Chuck Lewis <CLEWIS@xxxxxxxxxx>]

Thanks Larry -

I had thought of a delay job, but really wasn't sure of the mechanics of
STRTCP/STRHOSTSVR; how long the first ACTUALLY takes and does it "delay" things 
until
done and then STRHOSTSVR executes. It sounds like it musst kick things off, 
release
its' place "in line" and then STRHOSTSVR fires off while STRTCP jobs are still
starting...

Chuck

Larry Bolhuis wrote:

> Chuck,
> >
> > Tim we started using TCP/IP a while back with NT machines and I already had 
>the
> > STRTCP command in our startup CL. Once we started using NT I found out that 
>you
> > needed STRHOSTSVR also. I know that STRTCP needs to happen  first so I 
>placed
> > STRHOSTSVR after it and it didn't work. I moved STRHOSTSVR to the end of 
>the CL
> > hoping that this would work (maybe there was a "timing" problem with TCP/IP 
>not
> > having time to get fully started...) but this has not worked either.
> >
>
>   You have a timing problem and possibly also a security one.  I place
> the STRHOSTSVR at the end of the startup job, and add a DLYJOB command
> just prior to the STRHOSTSVR command to allow the TCP/IP stack to
> initialize.  Depending on CPU Model between 30 and 60 seconds seems to
> work-Longer on smaller systems.  The second issue is that QPGMR must be
> authorized to the STRHOSTSVR command since that is the user profile that
> runs the startup job.
>
>   Larry Bolhuis
>   Arbor Solutions, Inc
>   lbolhui@ibm.net



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---