Start TCP/IP Server (STRTCPSVR)
| Where allowed to run: All environments (*ALL) Threadsafe: Conditional |
Parameters Examples Error messages |
The Start TCP/IP Server (STRTCPSVR) command is used to start the TCP/IP application servers that are shipped with the operating system or the TCP/IP product. 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 in normal operating mode. Servers can not be started when the system is in restricted state.
All servers have an autostart (AUTOSTART) parameter on the associated configuration command (for example, Change FTP Attributes (CHGFTPA)). This parameter 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 attribute, unless *AUTOSTART is specified for the Server application (SERVER) parameter. If a server has *YES for the AUTOSTART attribute, then the STRTCPSVR command will start the server when SERVER(*AUTOSTART) is specified. Additional servers can automatically be added to list of servers that STRTCPSVR will support by using the Add TCP/IP Server (ADDTCPSVR) command.
Restrictions:
- This command is conditionally threadsafe. This command calls different programs to process each type of TCP/IP server. If the programs being called are threadsafe, this command is threadsafe.
| Top |
Parameters
| Keyword | Description | Choices | Notes |
|---|---|---|---|
| SERVER | Server application | Single values: *ALL, *AUTOSTART Other values (up to 300 repetitions): Character value |
Optional, Positional 1 |
| RESTART | Restart server | *NONE, *HTTP, *DNS, *OMPROUTED, *QOS, *DHCP | Optional |
| HTTPSVR | HTTP server | Single values: *ALL Other values: Element list |
Optional |
| Element 1: Server instance | Name, *ADMIN | ||
| Element 2: Instance startup values | Character value, *NONE | ||
| DNSSVR | DNS server | Single values: *ALL Other values: Element list |
Optional |
| Element 1: Server instance | Character value | ||
| Element 2: Instance startup values | Character value, *NONE | ||
| TCMSVR | TCM server | Single values: *NONE Other values: Element list |
Optional |
| Element 1: Instance name | Character value, *ALL | ||
| Element 2: Instance startup values | Character value, *NONE | ||
| TOMCATSVR | ASFTOMCAT server | Single values: *NONE Other values: Element list |
Optional |
| Element 1: Server instance name | Character value, *ALL | ||
| NTPSRV | SNTP service | *ALL, *CFGFILE, *CLIENT, *SERVER | Optional |
| INSTANCE | Instance | Single values: *DFT, *ALL, *AUTOSTART Other values: Element list |
Optional |
| Element 1: Server instance | Character value | ||
| Element 2: Instance startup values | Character value, *NONE |
| Top |
Server application (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, DNS, and TCM server instances are started.
- *AUTOSTART
- All of the TCP/IP application servers that are defined with *YES for the AUTOSTART attribute are to be started.
Other values (up to 300 repetitions)
- *BOOTP
- The Bootstrap Protocol (BOOTP) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*BOOTP) will result in a diagnostic message if the BOOTP server job has already been started.
- *DBG
- The Debug (DBG) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*DBG) will result in a diagnostic message if the DBG server has already been started.
- *DDM
- The Distributed Data Manager (DDM) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*DDM) will result in a diagnostic message if the DDM server job has already been started.
- *DHCP
- The Dynamic Host Configuration Protocol (DHCP) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*DHCP) will result in a diagnostic message if the DHCP server has already been started.
- *DIRSRV
- The Lightweight Directory Access Protocol (LDAP) server is started. The LDAP server is also known as the directory services (DIRSRV) server. See the parameter documentation for the INSTANCE (INSTANCE) parameter for information on starting server instances. Subsequent use of the STRTCPSVR command specifying SERVER(*DIRSRV) will result in a diagnostic message if the LDAP server has already been started.
- *DLFM
- The DataLink File Manager (DLFM) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*DLFM) will result in a diagnostic message if the DLFM server has already been started.
- *DNS
- One or more instances of the Domain Name System (DNS) server are started. See the parameter documentation for the DNS server (DNSSVR) parameter for more information on DNS server instances. Subsequent use of the STRTCPSVR command specifying SERVER(*DNS) will result in a diagnostic message if the DNS server has already been started.
- *DOMINO
- The Lotus Domino (DOMINO) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*DOMINO) will result in a diagnostic message if the DOMINO server has already been started.
- *EDRSQL
- The Extended Dynamic Remote SQL (EDRSQL) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*EDRSQL) will result in a diagnostic message if the EDRSQL server has already been started.
- *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 command specifying SERVER(*FTP) will start one additional FTP server.
Note: Having more than one FTP server job running can improve the performance of initiating a session when multiple users attempt to connect to the server in a short period of time.
- *HTTP
- One or more instances of the World Wide Web HyperText Transfer Protocol (HTTP) server is started. See the parameter documentation for the HTTP server (HTTPSVR) parameter for more information on HTTP server instances. Subsequent use of the STRTCPSVR command specifying SERVER(*HTTP) will result in a diagnostic message if the HTTP server has already been started.
- *IAS
- The Integrated Web Application (IAS) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*IAS) will result in a diagnostic message if the IAS server has already been started.
- *INETD
- The Internet Daemon (INETD) is started. Subsequent use of the STRTCPSVR command specifying SERVER(*INETD) will result in a diagnostic message if the INETD server has 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 usage of the STRTCPSVR command specifying SERVER(*LPD) will start one additional LPD server.
Note: LPD works most efficiently when two or more servers are running. Running only one server will work, 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 LPR requests.
- *MGTC
- The Management Central (MGTC) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*MGTC) will result in a diagnostic message if the MGTC server has already been started.
- *NETSVR
- The NetServer (NETSVR) server is started.
- *NTP
- The Simple Network Time Protocol (SNTP) services servers are started. See the parameter documentation for the SNTP service (NTPSRV) parameter for more information on specifying which SNTP services to start. Subsequent use of the STRTCPSVR command specifying SERVER(*NTP) will result in a diagnostic message if the indicated SNTP services server has already been started.
Note: If both client and server SNTP services have been started, running the ENDTCPSVR command specifying SERVER(*NTP) will end both client and server services. To change which SNTP services are active, run the ENDTCPSVR command specifying SERVER(*NTP), which will end all active SNTP services. Then run the STRTCPSVR command again, specifying SERVER(*NTP), and either NTPSRV(*CLIENT) or NTPSRV(*SERVER).
- *OMPROUTED
- The OMPROUTE Daemon (OMPROUTED) server is started. The OMPROUTE Daemon handles the Open Shortest Path First (OSPF) and Routing Information Protocol (RIP) server jobs. Specifying SERVER(*OMPROUTED) and INSTANCE(*OSPF) will start only the OSPF server job. Specifying SERVER(*OMPROUTED) and INSTANCE(*RIP) will start only the RIP server job. Subsequent use of the STRTCPSVR SERVER(*OMPROUTED) command results in a diagnostic message if the server job has already been started.
- *ONDMD
- The On Demand Server (ONDMD) is started. Subsequent use of the STRTCPSVR command specifying SERVER(*ONDMD) will result in a diagnostic message if the ONDMD server has already been started.
- *POP
- The Post Office Protocol (POP) version 3 mail servers are started based on the number of servers configured with the Change POP Server Attributes (CHGPOPA) command. Subsequent use of the STRTCPSVR SERVER(*POP) command results in a diagnostic message if the 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.
- *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 command specifying SERVER(*REXEC) will start one additional REXEC server.
- *ROUTED
- The Router Daemon (ROUTED) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*ROUTED) will result in a diagnostic message if the RouteD server has already been started.
- *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.
- *SNMP
- The Simple Network Management Protocol (SNMP) agent server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*SNMP) will result in a diagnostic message if the SNMP server has already been started.
- *SRVSPTPRX
- The Service and Support Proxy (SRVSPTPRX) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*SRVSPTPRX) will result in a diagnostic message if the SRVSPTPRX server has already been started.
- *SSHD
- The Secure Shell (SSH) Daemon server is started. Subsequent use of the STRTCPSVR SERVER(*SSHD) command results in a diagnostic message if the server has already been started.
- *TCM
- One or more instances of the Triggered Cache Manager (TCM) server is started. See the parameter documentation for the TCM server (TCMSVR) parameter for more information on specifying which TCM server instances to start. Subsequent use of the STRTCPSVR command specifying SERVER(*TCM) will result in a diagnostic message if the indicated TCM server instance has already been started.
- *TELNET
- The TELNET server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*TELNET) will start one additional TELNET server.
Note: Having more than one TELNET server job running reduces the chances of having connection attempts refused.
- *TFTP
- The Trivial File Transfer Protocol (TFTP) servers are started based on the number of servers configured with the Change TFTP Attributes (CHGTFTPA) command. Subsequent use of the STRTCPSVR SERVER(*TFTP) command results in a diagnostic message if the TFTP server jobs have already been started.
- *VPN
- The Virtual Private Network (VPN) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*VPN) will result in a diagnostic message if the VPN server has already been started.
- *WEBFACING
- The WebFacing (WEBFACING) server is started. Subsequent use of the STRTCPSVR command specifying SERVER(*WEBFACING) will result in a diagnostic message if the WebFacing server has already been started.
| Top |
Restart server (RESTART)
Specifies whether to restart the selected server when the STRTCPSVR command is run.
The SERVER parameter value specified must be one of the following:
- *DNS
- *HTTP
- *OMPROUTED
- *QOS
or this parameter is ignored.
- *NONE
- Do not restart any server.
- *HTTP
- Restart the HTTP server using the values specified on the HTTP server (HTTPSVR) parameter. If the server is not currently running when the STRTCPSVR command is run, this parameter is ignored and the server is started.
- *DNS
- A Domain Name System (DNS) server job that is already running will reprocess its configuration file and initialize with any changes that it found. If the DNS processing server is not currently running or cannot be successfully interrupted for the restart, a diagnostic message will be issued.
- *OMPROUTED
- The OMPROUTE Daemon (OMPOUTED) server job that is already running will reprocess its configuration or index file and initialize itself with any changes that are found. The INSTANCE parameter can be used to only reprocess the OSPF files (*OSPF) or only the RIP files (*RIP). If the OMPROUTED processing server is not currently running or cannot be successfully interrupted for the restart, a diagnostic message will be issued.
- *QOS
- The Quality of Service (QoS) server job that is already running will reprocess its configuration file and initialize with any changes that it found. If the QoS processing server is not currently running or cannot be successfully interrupted for the restart, a diagnostic message will be issued.
| Top |
HTTP server (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. (This server is also known as the IBM HTTP Server).
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.
For more information on the HTTP Server, visit the HTTP Server homepage: http://www.ibm.com/eserver/iseries/software/http
Single values
- *ALL
- All defined instances of the HTTP server will be started.
Element 1: Server instance
- *ADMIN
- The Administration Server will be started. The Administration Server is an instance of the HTTP server that allows administration of certain system functions using a Web browser.
- name
- Specify the name of the HTTP server instance to be started.
Element 2: Instance startup values
- *NONE
- No additional startup values are defined.
- character-value
- Specify the 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.
Note: The user must have input/output system configuration (*IOSYSCFG) special authority to specify overrides. If instance startup values are specified and the user does not have *IOSYSCFG authority, the start request will be rejected.
Note: IBM recommends that you use these overrides with caution; they are intended only for special circumstances. To specify startup values, IBM recommends you use the IBM HTTP Server Administration web-based interface rather than this command. Startup parameter values override specific server instance values, configuration directive values, global server values, and default values.
Instance startup values for the HTTP Server (powered by Apache).
- -netccsid [nnn]
- Overrides the DefaultNetCCSID directive
- -fsccsid [nnn]
- Overrides the default DefaultFsCCSID directive
- -d [serverroot]
- Set the initial value for the ServerRoot variable to serverroot. The default is /QIBM/UserData/HTTPA/logs.
- -f [configuration]
- Use the values in the configuration on startup. If the configuration does not begin with a /, then it is treated as a path relative to the ServerRoot. The default is conf/httpd.conf.
- -C [directive]
- Process the given "directive" (just as if it had been part of a configuration file) before actually reading the regular configuration files.
- -c [directive]
- Process the given "directive" after reading all the regular configuration files.
- -vv [verbose level service trace]
- Turn on verbose level service tracing .
- -vi [informational level service trace]
- Turn on informational level service tracing.
- -ve [error level service trace]
- Turn on error level service tracing.
- -V [no value is provided]
- Display the base version of the server, its build date, and a list of compile time settings which influence the behavior and performance of the server, then exit.
- -l [no value is provided]
- Display a list of all modules compiled into the server, then exit.
- -t [no value is provided]
- Test the configuration file syntax (i.e., read all configuration files and interpret them) but do not start the server. If the configuration contains errors, display an error message and exit with a non-zero exit status, otherwise display "Syntax OK" and terminate with a zero exit status. This command checks to see if all DocumentRoot entries exist and are directories.
- -M [no value is provided]
- Display a list of all modules compiled into the server plus those that are defined by the LoadModule directive in the configuration. The output will be generated in a spooled file for the server job.
| Top |
DNS server (DNSSVR)
Specifies the Domain Name System (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 values
- *ALL
- All defined instances of the DNS server will be started.
Element 1: Server instance
- character-value
- Specify the name of the DNS server instance to be started.
Element 2: Instance startup values
- *NONE
- No additional startup values are defined.
- character-value
- 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.
Note: The user must have input/output system configuration (*IOSYSCFG) special authority to specify overrides. If instance startup values are specified and the user does not have *IOSYSCFG authority, the start request will be rejected.
The list of instance startup values for the DNS Server follows:
- -d [n]
- where n is a number from 1 to 11. This sets the debug level of the server to start.
| Top |
TCM server (TCMSVR)
Specifies the Triggered Cache Manager (TCM) server instance to be started as well as any additional startup values to be used by the TCM server to control the server instance.
If multiple TCM 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 values
- *NONE
- No defined instances of the TCM server will be started.
Element 1: Instance name
- *ALL
- All defined instances for the TCM server will be started.
- character-value
- Specify the name of the TCM server instance to be started.
Element 2: Instance startup values
- *NONE
- No additional startup values are defined.
- character-value
- Specify the 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 instance name.
Note: The user must have input/output system configuration (*IOSYSCFG) special authority to specify overrides. If instance startup values are specified and the user does not have *IOSYSCFG authority, the start request will be rejected.
| Top |
ASFTOMCAT server (TOMCATSVR)
Specifies the Tomcat server instance 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.
Single values
- *NONE
- No defined instances of the Tomcat server will be started.
Element 1: Server instance name
- *ALL
- All defined instances for the Tomcat server will be started.
- character-value
- Specify the name of the Tomcat server instance to be started.
Note: The user must have input/output system configuration (*IOSYSCFG) special authority to specify overrides. If instance startup values are specified and the user does not have *IOSYSCFG authority, the start request will be rejected.
| Top |
SNTP service (NTPSRV)
Specifies the Simple Network Time Protocol (SNTP) services to be started.
Single values
- *CLIENT
- The SNTP client is started.
- *SERVER
- The SNTP server is started.
- *ALL
- Both the client and server are started.
- *CFGFILE
- The values of the keywords Client Autostart (AUTOSTART) and Server Autostart (SVRAUTOSTR) in the Change SNTP Attributes (CHGNTPA) command configuration file are used to determine what services to start. If the value is set to *YES, that service is started.
| Top |
Instance (INSTANCE)
Specifies the server instance to be started as well as any additional startup values to be used by the server to control the server instance. This parameter may be specified if the SERVER parameter is *DIRSRV, *DNS, *HTTP, *OMPROUTED, or *TCM. It may also be specified for user-defined servers which support multiple server instances.
If multiple server instances are supported, you can choose to start all instances, or start one specific instance by specifying the instance name to be started.
Single values
- *DFT
- The default server or servers will be started. If the SERVER parameter is *DIRSRV, the QUSRDIR server instance will be started. If the SERVER parameter is *HTTP or *DNS, all defined server instances will be started. If the SERVER parameter is *OMPROUTED, both the *OSPF and *RIP server jobs are started. If the SERVER parameter is *TCM, no defined server instances will be started.
- *ALL
- All defined instances of the server will be started.
- *AUTOSTART
- Server instances that are defined as being automatically started will be started. This feature may not be supported by all servers.
Element 1: Server instance
- character-value
- Specify the name of the server instance to be started. Up to 32 characters may be specified.
Element 2: Instance startup values
- *NONE
- No additional startup values are defined.
- character-value
- 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. Up to 300 characters may be specified.
Note: The user must have input/output system configuration (*IOSYSCFG) special authority to specify overrides. If instance startup values are specified and the user does not have *IOSYSCFG authority, the start request will be rejected.
| Top |
Examples
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) STRTCPSVR SERVER(*HTTP) INSTANCE(HTTP1)
These commands start 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') STRTCPSVR SERVER(*HTTP) INSTANCE(HTTP1 '-p 81 -sslport 443')
These commands start the TCP/IP HTTP application server instance named HTTP1, 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) STRTCPSVR SERVER(*DNS) INSTANCE(DNS1)
These commands start 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') STRTCPSVR SERVER(*DNS) INSTANCE(DNS1 '-d 5')
These commands start the TCP/IP DNS application server instance named DNS1, and specifies that the server instance should turn on debug level 5.
Example 9: Starting Directory Services Instances
STRTCPSVR SERVER(*DIRSRV) INSTANCE(*AUTOSTART)
This command starts all instances of the Directory Services server that have been configured to be automatically started.
| Top |
Error messages
*ESCAPE Messages
- CPF3894
- Cancel reply received for message &1.
- TCP1A11
- &1 failed.
- TCP1A77
- &1 completed successfully; however errors occurred.
| Top |