Starting Sun MTP Client and Sun MTP

This chapter describes how to start Sun MTP Client and how to start Sun MTP on the host.

What should I start first? Although you can start the processes in either order, you cannot connect to a region that is not started. When you start the region, the server listens for TCP and SNA requests. If you start an application automatically, it fails if the region is not started.

---

Starting Sun MTP Client on Windows

Sun MTP Client for Windows systems is designed to run as a Windows Service. Normally, it is not necessary to start Sun MTP Client; it starts for you. However, there are cases where you may want to control the starting and stopping of Sun MTP Client.

When the software is installed, a service is created that is started each time your machine is booted. However, this may not be the mode of operation that you require. Whether or not the service is started is determined using the Control Panel, Services option. If the Sun MTP Client service has the automatic flag set, it is started when your machine boots. To modify this setting, press the Startup button, then select the options you require.

Sun MTP Client can be started using the Control Panel, Services option. This operation is performed in the same way as for all services, by selecting the required service and pressing the Start button.

In addition to using the Control Panel to start and stop Sun MTP Client, you can use the Sun MTP Client Administrator (see Administering Sun MTP Client on Solaris).

---

Starting Sun MTP Client on Solaris

Sun MTP Client for Solaris is designed to run as a daemon process. It can be started manually from the shell, using the kixcli command, but this is not the normal method of operation. Normally, you should run Sun MTP Client as a daemon started from inittab. This means that ECI/EPI facilities are available whenever the machine is running.

To create an inittab entry, consult your operating system documentation for the exact syntax for your platform. The following is an example of an inittab entry:

kixcli:2:once:/opt/kixcli/bin/kixcli >/dev/console 2>&1

---

Enabling Sun MTP to Receive Connections

The connection on the Sun MTP host is established by starting the Sun MTP server, unikixmain, on the host with the -P option. When started in this way, in addition to starting transaction servers, it starts the unikixtcp server, which listens on the port number for incoming requests.

The server also provides the -L option for setting the number of file descriptors.

-L connections

Number of socket connections that the Sun MTP server can support for TCP connections. This number represents the maximum number of connections that can be opened by a process. Reduce the number to restrict the number of TCP Clients that can be attached or raise it if Clients are being rejected.

The default is the current system soft limit for files.

-P port#

Port name or number for the Sun MTP server to use as a listening port for CICS Clients running ECI and EPI applications over a TCP/IP connection. There is no default port so you must supply one, either by name or by number, for example:

-P cicstcp
-P 5100

The port number must match the port number of a system identified in the Client INI file. For example, to listen for requests from the Payroll system listed in CODE EXAMPLE 3-1, type port number 9111 as the argument to the -P option. Note that cicstcp is the name defined in /etc/services in Configuring Sun MTP for a TCP/IP Connection to Sun MTP Client.

You can start unikixmain directly or use the shell script, kixstart, to start it indirectly. kixstart passes any command line options to unikixmain. The Sun Mainframe Transaction Processing Software Configuration Guide describes the procedure for starting Sun MTP and the Sun Mainframe Transaction Processing Software Reference Guide describes all the options for unikixmain.