RE: Client Access

For the second problem you may just want to compile the startup program
with USRPRF(*OWNER) and make QSECOFR the owner.

Note that if the host server jobs are running, a SAVLIB of QIWS - even
with Save While Active, will fail to save the following 7 programs in
QIWS:
QNPSERVD, QZDASRVSD, QZHQSRVD, QZRCSRVSD, QZSCSRVSD, QZSOSGND,
QZSOSMAPD.
Of source this is only a problem if you do a SAVLIB *IBM in the nightly
backup.

So in your nightly backup, before starting the SAVLIB of QIWS you may
want to do an ENDHOSTSVR(*ALL) first, and a STRHOSTSVR *ALL after the
QIWS library is saved.
If you have an active PC5250 (TCP/IP) connection this will not kill your
connected PC5250 sessions, but during the brief period when the host
server jobs are not active you won't be able to start any new PC5250
connections.


Neil Palmer                                AS/400~~~~~      
NxTrend Technology - Canada   ____________          ___  ~     
Thornhill, Ontario,  Canada   |OOOOOOOOOO| ________  o|__||=   
Phone: (905) 731-9000  x238   |__________|_|______|_|______)   
Cell.: (416) 565-1682  x238    oo      oo   oo  oo   OOOo=o\   
Fax:   (905) 731-9202       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
mailto:NPalmer@NxTrend.com    AS/400  The Ultimate Business Server      
http://www.NxTrend.com

> -----Original Message-----
> From: Larry Bolhuis [SMTP:lbolhui@ibm.net]
> Sent: Thursday, May 21, 1998 11:05 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Client Access
> 
> 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
+---