|
Oliver, Information below is from the V5R1 NetServer manual: <start quote> In V4R4, AS/400 Support for Windows Network Neighborhood (AS/400 NetServer) requires that TCP/IP is active. As a result, AS/400 NetServer is now automatically started and ended as a TCP server when the Start TCP/IP (STRTCP) or End TCP/IP (ENDTCP) commands are evoked. Additionally, AS/400 NetServer can be started and ended as an individual TCP/IP server with the use of the Start TCP/IP Server (STRTCPSVR SERVER(*NETSVR)) and End TCP/IP Server (ENDTCPSVR SERVER(*NETSVR)) commands. You can specify whether the AS/400 NetServer starts automatically when TCP/IP is started by selecting the Start when TCP/IP is started check box on the AS/400 NetServer General Next Start dialogue. This value affects TCP/IP start behaviour (it is not an AS/400 NetServer property), so the changes will take effect immediately. When using iSeries Operations Navigator in the Client Access Express for Windows client (Express client), you can find this dialog by: 1. Follow the path Network->Servers->TCP/IP->AS/400 NetServer 2. Right click on the AS/400 NetServer icon 3. Select Properties 4. Select the General tab 5. Press the Next Start button <end quote> Regards, Andy Nolen-Parkhouse > On Behalf Of oliver.wenzel@cibavision.novartis.com > Subject: Correct startup sequence for QSTRUP > > Hello, > > we have switched to V5R1 in mid-May. In our QSTRUP, I have disabled > STRTCP, > as that is now started automatically. > I now have the problem that NETSERVER doesn't start, as the sbs QSERVER is > not yet active. > > It's just a matter of a few seconds, as QSERVER starts at 22:12:19 (from > QSTRUP) and the netserver failure message > is from 22:12:15. > > How do I get QSERVER started before STRTCP? > > Thanks, > > Oliver
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.