STRTCPSVR (Start TCP/IP Server)

STRTCPSVR Command syntax diagram

 

Purpose

The Start TCP/IP Server (STRTCPSVR) command is used to start the TCP/IP application servers. This command starts TCP/IP jobs for the application servers specified with the server (SERVER) parameter. The number of server jobs started by this command is specified, where appropriate, in the configuration for each TCP/IP application. The STRTCPSVR command can only be used when TCP/IP is fully operational. The interface server job, QTCPIP, must be available. If TCP/IP processing was started by running the STRTCP (Start TCP/IP) command when the system was in restricted state, the QTCPIP server job was not started, and the STRTCPSVR command will fail.>

Each type of TCP/IP server has an autostart (AUTOSTART) parameter maintained in a control file which indicates if the server should be started when the Start TCP/IP (STRTCP) command is entered. The STRTCPSVR command ignores the value of a server's autostart parameter unless SERVER(*AUTOSTART) is specified. Some of the supported servers can have the autostart value changed through a configuration CL command (for example, Change FTP Attributes (CHGFTPA)).

Use iSeries Navigator, the ability to start a server automatically whenever TCP/IP starts can be accomplished by turning on the capability from a property panel.

Additional servers can automatically be added to list of servers that STRTCPSVR will support by using the ADDTCPSVR (Add TCP/IP Server) CL command.>

 

Optional Parameters

SERVER
Specifies the TCP/IP application servers to be started by this command.

Single Values

*ALL: All of the TCP/IP application servers and all HTTP and DNS instances are started.

*AUTOSTART: All of the TCP/IP application servers that are defined as AUTOSTART *YES are started.

TCP/IP Application Servers

Additional servers could also be available if they were added with the ADDTCPSVR command. Press F4 when prompting the SERVER parameter for a complete list of supported parameter values. >

*SNMP: The Simple Network Management Protocol (SNMP) agent server is started. Subsequent use of the STRTCPSVR SERVER(*SNMP) command results in a diagnostic message if the SNMP server has already been started.

*ROUTED: The RouteD server is started. Subsequent usage of the STRTCPSVR SERVER(*ROUTED) command results in a diagnostic message if the RouteD server has already been started.

*BOOTP: The Bootstrap Protocol (BOOTP) server job is started. Subsequent usage of the STRTCPSVR SERVER(*BOOTP) command results in a diagnostic message if the BOOTP server has already been started.

*TFTP: The configured minimum number of Trivial File Transfer Protocol (TFTP) servers are started. Subsequent use of the STRTCPSVR SERVER(*TFTP) command results in a diagnostic message if the TFTP servers have already been started.

*DNS: The Domain Name Server (DNS) server is started. Subsequent use of the STRTCPSVR SERVER(*DNS) command results in a diagnostic message if the DNS server has already been started.

*DHCP: The Dynamic Host Configuration Protocol (DHCP) server is started. Subsequent use of the STRTCPSVR SERVER(*DHCP) command results in a diagnostic message if the DHCP server has already been started.

*DDM: The server that listens for distributed data management (DDM) and distributed relational database architecture (DRDA) connect requests and dispatches pre-started jobs to service them is started. Subsequent use of the STRTCPSVR SERVER(*DDM) command results in a diagnostic message if the DDM server has already been started.

*TELNET: The TELNET server is started. Subsequent use of the STRTCPSVR SERVER(*TELNET) command starts one additional TELNET server.

Note: Having more than one TELNET server running reduces the chances of having connection attempts refused.

*FTP: The File Transfer Protocol (FTP) servers are started based on the number of servers configured with the Change FTP Attributes (CHGFTPA) command. Subsequent use of the STRTCPSVR SERVER(*FTP) command starts one additional FTP server.

Note: Having more than one FTP server running can improve the performance of initiating a session when multiple users attempt to connect to the server in a short period of time.

*SMTP: The Simple Mail Transfer Protocol (SMTP) client and server jobs are started. Additional SMTP client and server jobs cannot be started. Subsequent use of the STRTCPSVR SERVER(*SMTP) command results in a diagnostic message if the SMTP server jobs have already been started.

*LPD: The line printer daemon (LPD) servers are started based on the number of servers configured with the Change LPD Attributes (CHGLPDA) command. Subsequent use of the STRTCPSVR SERVER(*LPD) command starts one additional LPD server.

Note: LPD works most efficiently when two or more servers are running. Running only one server works, but no jobs can be received while a current job is running. If a large print job is running, new jobs have to wait before LPD is ready to accept any new line printer requester (LPR) requests.

*HTTP: The World Wide Web HyperText Transfer Protocol (HTTP) servers are started based on the number of servers specified in the Change HTTP Attributes (CHGHTTPA) command. Subsequent use of the STRTCPSVR SERVER(*HTTP) command results in a diagnostic message if the HTTP server has already been started.

*POP: The Post Office Protocol (POP) version 3 servers are started based on the number of servers configured with the Change POP Attributes (CHGPOPA) command. Subsequent use of the STRTCPSVR SERVER(*POP) command starts one additional POP server.

*REXEC: The Remote EXECution (REXEC) servers are started based on the number of servers configured with the Change REXEC Attributes (CHGRXCA) command. Subsequent use of the STRTCPSVR SERVER(*REXEC) command starts one additional REXEC server.

Note: Having more than one REXEC server running can improve the performance of initiating a session when multiple users attempt to connect to the server in a short period of time.

*NSMI: The Network Station Manager inventory (NSMI) server is started. Subsequent use of the STRTCPSVR SERVER(*NSMI) command results in a diagnostic message if the NSMI server has already been started.

*DCE: The Distributed Computing Environment (DCE) servers are started based on the configuration specified using the iSeries Navigator. Subsequent use of the STRTCPSVR SERVER(*DCE) command starts any additional DCE servers that are configured, but are not started.

*DIRSRV: The Directory Services (DIRSRV) servers are started based on the configuration specified using the iSeries Navigator. Subsequent use is ignored because only one DIRSRV server is allowed.

*USF: The Ultimedia System Facilities (USF) server is started. Subsequent use of the STRTCPSVR SERVER(*USF) command results in a diagnostic message if the USF server has already been started.

*NSLD: The Network Station Login Daemon (NSLD) server is started. Subsequent use of the STRTCPSVR SERVER(*NSLD) command results in a diagnostic message if the NSLD server has already been started.

*INETD: The Internet daemon (INETD) super-server is started. Subsequent use of the STRTCPSVR SERVER(*INETD) command results in a diagnostic message if the INETD server has already been started.

*MGTC: The Management Central (MGTC) server is started. Subsequent use of the STRTCPSVR SERVER(*MGTC) command results in a diagnostic message if the MGTC server has already been started.

*ONDMD: The OnDemand Client for iSeries (ONDMD) server is started. Subsequent use of the STRTCPSVR SERVER(*ONDMD) command results in a diagnostic message if the ONDMD server has already been started.

*NETSVR: The NetServer (NETSVR) server is started. Subsequent use of the STRTCPSVR SERVER(*NETSVR) command results in a diagnostic message if the NETSVR server has already been started.

*DLFM: The DataLink File Manager (DLFM) server is started. Subsequent use of the STRTCPSVR SERVER(*DLFM) command results in a diagnostic message if the DLFM server has already been started.

*VPN: The Virtual Private Network (VPN) server is started. Subsequent use of the STRTCPSVR SERVER(*VPN) command results in a diagnostic message if the VPN server has already been started.

*EDRSQL: The Extended Dynamic Remote SQL (EDRSQL) server is started. Subsequent use of the STRTCPSVR SERVER(*EDRSQL) command results in a diagnostic message if the EDRSQL server has already been started.

*HOD: The Host On Demand (HOD) server is started. Subsequent use of the STRTCPSVR SERVER(*HOD) command results in a diagnostic message if the HOD server has already been started.

*ODPA: The On-Demand Platform Authentication (ODPA) server is started. Subsequent use of the STRTCPSVR SERVER(*ODPA) command results in a diagnostic message if the ODPA server has already been started.

*QOS: The Quality of Service (QoS) server is started. Subsequent use of the STRTCPSVR SERVER(*QOS) command results in a diagnostic message if the QoS server has already been started.

*NTP: The Simple Network Time Protocol (SNTP) server is started. Subsequent use of the STRTCPSVR SERVER(*NTP) command results in a diagnostic message if the SNTP server has already been started.

*TCM: The Trigger Cache Manager (TCM) server is started. Subsequent use of the STRTCPSVR SERVER(*TCM) command results in a diagnostic message if the TCM server has already been started.

*DOMINO: The Domino server is started. Subsequent use of the STRTCPSVR SERVER(*DOMINO) command results in a diagnostic message if the Domino server has already been started.

*LQP: The Lotus QuickPlace (LQP) server is started. Subsequent use of the STRTCPSVR SERVER(*LQP) command results in a diagnostic message if the LQP server has already been started.

*WEBFACING: The 5250 WebFacing server is started. Subsequent use of the STRTCPSVR SERVER(*WEBFACING) command results in a diagnostic message if the 5250 WebFacing server has already been started.

*DBG: The Debug server is started. Subsequent use of the STRTCPSVR SERVER(*DBG) command results in a diagnostic message if the DBG server has already been started.

*ASFTOMCAT: The Apache Software Foundation (ASF) Tomcat server is started. Subsequent use of the STRTCPSVR SERVER(*ASFTOMCAT) command results in a diagnostic message if the Apache Software Foundation (ASF) Tomcat server has already been started.>

RESTART
Specifies whether to restart the selected server when the STRTCPSVR command is run. If the selected server is not currently running when the STRTCPSVR command is run, this parameter is ignored and the selected server is started.

The SERVER parameter specified must be *ALL, *HTTP, *DNS, *DHCP, or *QOS, or this parameter is ignored.

*NONE: Do not restart any server.

*HTTP: Restart the HTTP server if it is already running. This forces the HTTP server to read in the HTTP configuration and use any configuration values or attributes that changed since it was last started.

*DNS: Restart the DNS server if it is already running. This forces the DNS server to read in the DNS configuration and use any configuration values or attributes that changed since it was last started.

*DHCP: Restart the DHCP server if it is already running. This forces the DHCP server to read in the HTTP configuration and use any configuration values or attributes that changed since it was last started.

*QOS: Restart the Quality of Service (QoS) server if it is already running. This forces the QoS policy rules to be reloaded from the QoS policy file.

HTTPSVR
Specifies the HTTP server instance to be started as well as any additional startup values to be used by the HTTP server to control the server instance.

If multiple HTTP server instances have been defined, you can choose to start all instances, or start one specific instance by specifying the instance name to be started.

Single Value

*ALL: All defined server instances for the HTTP server will be started.

Element 1: Server Instance Name

server-instance-name: The specified server instance will be started.

*ADMIN: The administration HTTP server will be started. The administration server is an instance of the HTTP server that allows administration of certain iSeries functions using a web browser.

Element 2: Instance Startup Values

*NONE: No additional startup values are defined. The previously defined startup values for the HTTP server will be used to start the specified server instance.

instance-startup-values: Specifies additional startup values to be used for this server instance. These values will be used to override previously-defined server startup values for the specified server instance. Supported override startup values can be found in the 'Hypertext Transfer Protocol (HTTP) Server' chapter in the TCP/IP Configuration and Reference Link to PDF book.

The user is required to have *IOSYSCFG special authority to specify overrides. If instance startup values are specified and the user does not have *IOSYSCFG authority then the start request will be rejected.

DNSSVR
Specifies the DNS server instance to be started as well as any additional startup values to be used by the DNS server to control the server instance.

If multiple DNS server instances have been defined, you can choose to start all instances, or start one specific instance by specifying the instance name to be started.

Single Value

*ALL: All defined server instances for the DNS server will be started.

Element 1: Server Instance Name

server-instance-name: The specified server instance will be started.

Element 2: Instance Startup Values

*NONE: No additional startup values are defined. The previously defined startup values for the DNS server will be used to start the specified server instance.

instance-startup-values: Specifies additional startup values to be used for this server instance. These values will be used to override previously-defined server startup values for the specified server instance.

The user is required to have *IOSYSCFG special authority to specify overrides. If instance startup values are specified and the user does not have *IOSYSCFG authority then the start request will be rejected.

TCMSVR
Specifies the TCM instance name to be started as well as any additional startup values to be used by the TCM server to control the instance.

If multiple TCM instance names have been defined, you can choose to start all instances, or start one specific instance by specifying the instance name to be started.

Single Value

*NONE: No defined instances for the TCM server will be started.

Element 1: Instance Name

instance-name: The specified instance will be started.

Element 2: Instance Startup Values

*NONE: No additional startup values are defined. The previously defined startup values for the TCM server will be used to start the specified instance name.

instance-startup-values: Specifies additional startup values to be used for this instance. These values will be used to override previously-defined server startup values for the specified instance name.

The user is required to have *IOSYSCFG special authority to specify overrides. If instance startup values are specified and the user does not have *IOSYSCFG authority then the start request will be rejected.

TOMCATSVR
Specifies the Tomcat server instance name to be started.

If multiple Tomcat server instance names have been defined, you can choose to start all instances, or start one specific instance by specifying the instance name to be started.

*NONE: No defined instances for the Tomcat server will be started.

server-instance-name: The specified instance will be started.

*ALL: All defined server instances for the Tomcat server will be started.

The user is required to have *IOSYSCFG special authority to specify overrides. If instance startup values are specified and the user does not have *IOSYSCFG authority then the start request will be rejected.>

Examples for STRTCPSVR

Example 1: Starting All TCP/IP Servers with AUTOSTART(*YES) 

STRTCPSVR  SERVER(*AUTOSTART)

This command starts all of the TCP/IP application servers that have the AUTOSTART attribute in the application configuration set to *YES.

Example 2: Starting All TCP/IP Servers 

STRTCPSVR  SERVER(*ALL)

This command starts all of the TCP/IP application servers that have been configured. For example: If the Change FTP Attributes (CHGFTPA) command was previously used to configure two FTP servers, both servers are started when STRTCPSVR is issued. This example is also true for other TCP/IP application servers.

Where appropriate, the number of servers to start is based on the number of servers configured for the server being started.

Example 3: Starting the TELNET Server 

STRTCPSVR  SERVER(*TELNET)

This command starts the TCP/IP TELNET application server. If the TELNET server was previously started, one additional TELNET server job is started.

Example 4: Restarting the HTTP Server 

STRTCPSVR  SERVER(*HTTP) RESTART(*HTTP)

This command restarts the TCP/IP HTTP application server for all instances of the HTTP server. If the HTTP server was not currently running, then all defined instances of the HTTP server would be started.

Example 5: Starting an HTTP Server Instance 

STRTCPSVR  SERVER(*HTTP) HTTPSVR('http1')

This command starts the TCP/IP HTTP application server instance named 'http1' using the startup values previously defined for this server instance.

Example 6: Specifying Startup Values for an HTTP Instance 

STRTCPSVR SERVER(*HTTP) HTTPSVR(HTTP1 '-p 81 -sslport 443')

This command starts the TCP/IP HTTP application server instance named HTTP, and specifies that the server instance should listen on port 81 for unsecure requests and on port 443 for secure requests. The ports defined here will override any previously defined ports to be used by this server instance.

Example 7: Starting a DNS Server Instance 

STRTCPSVR  SERVER(*DNS) DNSSVR('dns1')

This command starts the TCP/IP DNS application server instance named 'dns1' using the startup values previously defined for this server instance.

Example 8: Specifying Startup Values for a DNS Instance 

STRTCPSVR SERVER(*DNS) DNSSVR(DNS1 '-d 5')

This command starts the TCP/IP DNS application server instance named DNS1, and specifies that the server instance should turn on debug level 5.

Error messages for STRTCPSVR

*ESCAPE Messages

CPF3E30
Errors occurred starting DDM TCP/IP server.
CPF3E31
Unable to start DRDA/DDM TCP/IP server.
TCP1A0C
TCP/IP LPP must be installed or at correct version level.
TCP1A11
&1 failed.
TCP1A21
STRTCPSVR not allowed. TCP/IP is not active.