Starting iSeries NetServer at initial program load

iSeries™ NetServer™ can be started and ended as an individual TCP/IP server by using the Start TCP/IP Server and End TCP/IP server commands.

iSeries NetServer is now automatically started and ended as a TCP server when the Start TCP/IP (STRTCP) or End TCP/IP (ENDTCP) commands are called. Additionally, iSeries 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 iSeries NetServer starts automatically when TCP/IP is started by selecting the Start when TCP/IP is started option on the iSeries NetServer General Next Start dialog box. This value affects TCP/IP start behavior (it is not an iSeries NetServer property), so the changes will not take effect immediately. When using iSeries Navigator in iSeries Access for Windows^®, you can follow the following steps to find this dialog box:

1. In iSeries Navigator, expand Network > Servers > TCP/IP > iSeries NetServer.

2. Right-click the iSeries NetServer icon.

3. Select Properties.

4. Select the General tab.

5. Press the Next Start button.

The QZLSSERVER job resides in the QSERVER subsystem. The Start Server (QZSLSTRS) and End Server (QZLSENDS) APIs still start and end the server. Because of this, no changes are needed in your start-up program if the QSERVER subsystem is started before TCP/IP is started.

Parent topic: