Very Computer

Once a week, when our three AS/400s re IPL, as part of their startup
sequence I have included a call to STRHOSTSVR *ALL to start all host
services, in particular the client access host connection service.

Only one of the three AS/400s actually allows connection after startup has
finished, the other two need the STRHOSTSVR command to be typed in again to
allow PC access.

The Machine that does work is running a beta of V4R2 and the two that don't
are running V3R6 and V3R7.

Does anyone have any insight or experience of this problem.

TIA:

Dave Stubbs

::Once a week, when our three AS/400s re IPL, as part of their startup
::sequence I have included a call to STRHOSTSVR *ALL to start all host
::services, in particular the client access host connection service.
::
::Only one of the three AS/400s actually allows connection after startup has
::finished, the other two need the STRHOSTSVR command to be typed in again to
::allow PC access.
::
::The Machine that does work is running a beta of V4R2 and the two that don't
::are running V3R6 and V3R7.
::
::Does anyone have any insight or experience of this problem.
::
::TIA:
::
::Dave Stubbs
::
::
Dave,

We had that problem until recently (V3r2 & V3r7) - found out it was a
security problem with STRHOSTSVR command.  Changed it to allow
QPGMR to have authority and now works fine. Hope this helps.

Terry

Hi David,

Usually this is due to a needed delay between starting things or the
security of the start commands. For more information, see
http://tnt400.com/bo400ng/AS400Q0076.htm

Brian Singleton
NEWS/400
www.tnt400.com

Have you written before the STRHOSTSVR cmd STRTCP?

Cheers,
Dennis

Quote:> Once a week, when our three AS/400s re IPL, as part of their startup
> sequence I have included a call to STRHOSTSVR *ALL to start all host
> services, in particular the client access host connection service.

If you don't want to waste time, put STRTCP at top of your startup CL,
STRHOSTSVR at the end.

Walter