Start TCP/IP (STRTCP)

Where allowed to run: All environments (*ALL)
Threadsafe: Conditional

The Start TCP/IP (STRTCP) command initializes and activates TCP/IP processing, starts the TCP/IP interfaces, starts the TCP/IP server jobs, and starts the TCP/IP Point-To-Point (PTP) profiles. A STRTCP command must be issued before any TCP/IP processing can be performed on the system. This includes Simple Network Management Protocol (SNMP) agent processing.

The TCP/IP interfaces that are started are those that have set the AUTOSTART parameter to a value of *YES using the Add TCP/IP Interface (ADDTCPIFC) or Change TCP/IP Interface (CHGTCPIFC) commands, or the Systems Director Navigator.

The Change IPL Attributes (CHGIPLA) command with the STRTCP parameter set to a value of *YES can be used to automatically submit the STRTCP command at the completion of IPL.

The TCP/IP application server jobs that can be started are:

Bootstrap Protocol (BOOTP)
DataLink File Manager (DLFM)
Debug Server (DBG)
Directory Services (DIRSRV)
Distributed Data Management (DDM)
Domain Name Server (DNS)
Domino
Dynamic Host Configuration Protocol (DHCP)
Extended Dynamic Remote SQL (EDRSQL)
File Transfer Protocol (FTP)
Hypertext Transfer Protocol (HTTP)
Internet Daemon (INETD)
Integrated Web Application (IAS)
Line Printer Daemon (LPD)
Management Central (MGTC)
NetServer (NETSVR)
On Demand (ONDMD)
Open Shortest Path First (OSPF) Routing Protocol
Post Office Protocol (POP)
Quality of Service (QoS)
Remote Execution (REXEC)
Router Daemon (ROUTED)
Service and Support Proxy (SRVSPTPRX)
Simple Mail Transfer Protocol (SMTP)
Simple Network Management Protocol (SNMP) agent
Simple Network Time Protocol (NTP)
Triggered Cache Manager (TCM)
Trivial File Transfer Protocol (TFTP)
Virtual Private Network (VPN)
Virtual terminal support (TELNET)
WebFacing (WEBFACING)

The Start TCP/IP command only starts a TCP/IP application job if the AUTOSTART attribute in the application's configuration is set to *YES when the command is issued. No TCP/IP application jobs are started in the QSYSWRK subsystem if any of the following is true:

The TCP/IP licensed program product is not installed.
All of the TCP/IP applications have an AUTOSTART configuration attribute value of *NO.
STRSVR(*NO) is specified for the STRTCP command. See the description of the STRSVR parameter below.

Use the commands or interfaces listed below to change the configuration for an application so that it starts automatically when the Start TCP/IP command is issued.

For the SNMP agent use the Change SNMP Attributes (CHGSNMPA) command specifying AUTOSTART(*YES)
For the RouteD server use the Change RouteD Attributes (CHGRTDA) command specifying AUTOSTART(*YES)
For the BOOTP server use the Change BOOTP Attributes (CHGBPA) command specifying AUTOSTART(*YES)
For the TFTP server use the Change TFTP Attributes (CHGTFTPA) command specifying AUTOSTART(*YES)
For the DNS server use the Change DNS Attributes (CHGDNSA) command specifying AUTOSTART(*YES)
For the DHCP server use the Change DHCP Attributes (CHGDHCPA) command specifying AUTOSTART(*YES)
For the DDM server use the Change DDM TCP/IP Attributes (CHGDDMTCPA) command specifying AUTOSTART(*YES)
For the TELNET application use the Change TELNET Attributes (CHGTELNA) command specifying AUTOSTART(*YES)
For the FTP application use the Change FTP Attributes (CHGFTPA) command specifying AUTOSTART(*YES)
For the SMTP application use the Change SMTP Attributes (CHGSMTPA) command specifying AUTOSTART(*YES)
For the LPD application use the Change LPD Attributes (CHGLPDA) command specifying AUTOSTART(*YES)
For the HTTP server application use the Change HTTP Attributes (CHGHTTPA) command specifying AUTOSTART(*YES).
For the Post Office Protocol (POP) version 3 mail servers use the Change POP Mail Server Attributes (CHGPOPA) command specifying AUTOSTART(*YES)
For the REXEC server application use the Change REXEC Attributes (CHGRXCA) command specifying AUTOSTART(*YES)
Change DBG server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change DIRSVR server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change IAS server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change SRVSPTPRX server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change INETD daemon attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change MGTC daemon attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change ONDMD server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change OMPROUTED server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change NETSVR attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change DLFM server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change EDRSQL server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change NTP server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change QoS server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change TCM server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change DOMINO server attributes, including the AUTOSTART parameter, using Systems Director Navigator.
Change WEBFACING server attributes, including the AUTOSTART parameter, using Systems Director Navigator.

When the STRTCP command is issued the QTCPCTL system job will handle all requests for activating and deactivating TCP/IP interfaces.

Note: The STRTCP command does not need to be issued to use socket applications that run over an SNA network.

Attention: Before attempting to start an X.25 interface, ensure that the remote system information (RSI) for non-DDN X.25 interfaces that use a permanent virtual circuit (PVC) is configured. Use the Add TCP/IP Remote System (ADDTCPRSI) command to do this.

Incoming data from a remote system on the X.25 network is not processed unless an RSI entry for the PVC is configured on the X.25 interface before the interface is started.

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
STRSVR	Start application servers	YES, NO	Optional
STRIFC	Start TCP/IP interfaces	YES, NO	Optional
STRPTPPRF	Start point-to-point profiles	YES, NO	Optional
STRIP6	Start IPv6	YES, NO	Optional

Top

Start application servers (STRSVR)

Specifies whether or not TCP/IP application servers are started by the STRTCP command.

*YES: The STRTCP command starts all TCP/IP application servers with a configuration attribute of AUTOSTART(*YES) when TCP/IP is activated.
*NO: The STRTCP command does not start any TCP/IP application servers when TCP/IP is activated.

Note: This parameter can be used when TCP/IP application servers using AnyNet are already active on your system and you intend to also activate TCP/IP. STRTCP STRSVR(*NO) activates TCP/IP processing without starting additional TCP/IP servers.

When TCP/IP or AnyNet is already active, use the Start TCP/IP Server (STRTCPSVR) command to start additional TCP/IP application servers.

Top

Start TCP/IP interfaces (STRIFC)

Specifies whether or not to activate all TCP/IP interfaces that specify AUTOSTART(*YES) when TCP/IP is activated.

*YES: When the STRTCP command is issued the QTCPWRK system job will attempt to activate all TCP/IP interfaces for which AUTOSTART(*YES) is specified.
*NO: The AUTOSTART(*YES) interface parameter will be ignored. No TCP/IP interfaces will be automatically started.

Note: Specifying STRIFC(*NO) only inhibits the activation of TCP/IP interfaces. It has no effect on interfaces for other AnyNet protocols such as IP over SNA or IP over IPX.

Top

Start point-to-point profiles (STRPTPPRF)

Specifies whether or not to activate all point-to-point profiles that specify a configuration attribute of AUTOSTART(*YES) when TCP/IP is activated.

*YES: As part of the running of the STRTCP command, the Start Point-to-Point TCP/IP (STRTCPPTP) command will also be run. The STRTCPPTP command will attempt to start all of the point-to-point profiles with a configuration attribute of AUTOSTART(*YES).
*NO: The STRTCPPTP command will not be run.

Top

Start IPv6 (STRIP6)

Specifies whether or not to activate the IPv6 portion of the TCP/IP protocol stack.

*YES: As part of the running of the STRTCP command, the IPv6 portion of the TCP/IP protocol stack will be started. If STRIFC(*YES) is specified, then an attempt will be made to start all of the IPv6 lines and IPv6 interfaces with a configuration attribute of AUTOSTART(*YES).
*NO: The IPv6 protocol will not be started.

Top

Examples

Example 1: Starting TCP/IP

STRTCP

This command initializes and activates TCP/IP processing, starts the TCP/IP interfaces, and starts the TCP/IP server jobs.

Example 2: Starting TCP/IP and TCP/IP Servers

STRTCP   STRSVR(*YES)

Because *YES is the default value for the STRSVR parameter, the result of issuing this command is identical to the Example 1.

Example 3: Starting TCP/IP But Not the TCP/IP Servers

STRTCP   STRSVR(*NO)

This will start TCP/IP processing without starting any of the TCP/IP application server jobs.

Example 4: Starting TCP/IP in Restricted State

STRTCP   STRSVR(*NO)  STRIFC(*NO) STRPTPPRF(*NO) STRIP6(*YES)

This will start TCP/IP processing (both IPv4 and IPv6), even if the system is in restricted state. TCP/IP application servers and IP interfaces will not be started.

Example 5: Starting TCP/IP without starting IPv6 processing

STRTCP  STRSVR(*YES)  STRIFC(*YES) STRPTPPRF(*YES) STRIP6(*NO)

This command initializes and activates TCP/IP processing (IPv4 only), starts the TCP/IP interfaces (IPv4 only) that have the AUTOSTART parameter set to *YES. Starts the TCP/IP servers that have the AUTOSTART parameter set to *YES. Starts the Point to Point profiles that have the AUTOSTART parameter set to *YES.

Top

Error messages

*ESCAPE Messages

CPF9848: Cannot open file &1 in library &2 member &3.
CPF9849: Error while processing file &1 in library &2 member &3.
TCP1A12: Error occurred submitting interface job.
TCP1A14: Error occurred starting TCP/IP servers.
TCP1A77: &1 completed successfully; however errors occurred.
TCP1D03: &1 member record length not correct.
TCP1D04: Error occurred processing member &1 of &2/&3.
TCP9999: Internal system error in program &1.

Top