;---------------------------------------------------------------

;

:Sun MTP Client Configuration File

;---------------------------------------------------------------

[Systems]

Accounts=TCP,abc.mycompany.com,9111,Customer Accounting System

Payroll=TCP,def.mycompany.com,9111,Employee Payroll System

Ordering=TCP,ghi.mycompany.com,9111,Internal Ordering System

Test=TCP,555.555.55.5,9111,Test System

SnaSyst=MSSNA,RLUALIAS,LLUALIAS,MODENAME,MS SNA Connected System

[General]

DefaultSystem=Accounts

;TraceDir=C:\tmp

;TraceMask=0

;MsgDir=C:\tmp

;MaxRequests=20

;MaxSystems=3

;EnableConnect=false

Adding Systems to the KIXCLI.INI File

Each line in the Systems section defines a Sun MTP region. Add an entry in the Systems section for each region that you plan to use. The format of each region entry is different, depending on the transport protocol used to connect to that system (TCP/IP or SNA). The use of SNA as a transport is only supported on the Microsoft Windows versions of Sun MTP Client, not on the Solaris version.

Required Fields for a TCP/IP-Connected System

All fields are required. Even if you do not enter a comment, you must type a comma delimiter after the port number field.

The fields in each entry are described in the following table:

In CODE EXAMPLE 3-1, the first line in this section, Systems defines a system that will be known locally as Accounts. This system uses the TCP transport to connect to a Sun MTP region that is running on host abc.mycompany.com and listening for TCP connections from Sun MTP Clients on port 9111. The last field contains a description of the system, Customer Accounting System.

Required Fields for an SNA-Connected System

All fields are required. Even if you do not enter a comment, you must type a comma delimiter after the port number field.

The fields in each entry are described in the following table:

In CODE EXAMPLE 3-1, the last line in the Systems section defines a system that is known locally as SnaSyst. This system uses Microsoft SNA or IBM Communications Manager to connect to Sun MTP using the local LU LLUALIAS, where Sun MTP has a remote LU Alias of RLUALIAS. The APPC mode to be used is MODENAME. The last field contains a description of the system, MS SNA Connected System.

Defining Client Behavior in the KIXCLI.INI File

Entries in the General section of the KIXCLI.INI file control the behavior of Sun MTP Client and are optional. These entries take the form of Attribute=value pairs, and are described below.

DefaultSystem=System_name

Sets which default system to use by Sun MTP Client; system must be defined in the Systems section. If DefaultSystem is not specified, it defaults to the first entry in the Systems section of the KIXCLI.INI file. For example, Accounts in CODE EXAMPLE 3-1 is the default system even if this entry is commented out.

TraceDir=C:\TMP

Controls the destination directory for Sun MTP diagnostic trace files. Each trace file is given the name *.trc, where * is a file name root identifying the task or process concerned. If TraceDir is not specified, it defaults to $INSTROOT/BIN.

TraceMask=0

A decimal integer that controls the generation of a diagnostic trace by Sun MTP Client. This entry should be left commented out or set to zero, unless you are asked to obtain a diagnostic trace by your authorized Sun service provider.

When using diagnostic trace, be aware of the following:

• Trace files *.trc can quickly use large quantities of disk space. Therefore, you should disable trace and delete unwanted trace files as soon as possible.
• Generation of diagnostic traces degrades the performance of Sun MTP Client.

MsgDir=C:\TMP

As part of its normal function, Sun MTP Client generates messages, which are written to the file KIXCLI.MSG in the MsgDir directory. If MsgDir is not specified, it defaults to $INSTROOT\BIN. The message file, KIXCLI.MSG, is overwritten each time Sun MTP Client is started.

MaxRequests=20

Defines the maximum number (default 20) of concurrent requests allowed by Sun MTP Client. A request is defined as an ECI unit-of-work, an EPI, or terminal emulator session. This parameter is designed to limit any problems that an errant application may cause, such as an ECI application that erroneously loops, continually starting new units-of-work, but never completing them.

MaxSystems=3

Defines the maximum number (default 3) of systems to which Sun MTP Client can be simultaneously connected.

EnableConnect=false

Allows you to configure the action taken by Sun MTP Client when the right mouse button is pressed from the Systems display.

true Displays the menu for connecting or disconnecting from a Sun MTP region. (Default)

false Does not display the connect/disconnect menu. This facility is provided for environments in which users should not be able to select a system. This is the recommended value for production installations.

---

Enabling and Disabling a Diagnostic Trace

For support purposes, you may be asked by your authorized Sun service providerto obtain diagnostic information by running a diagnostic trace of Sun MTP Client.

1. Stop Sun MTP Client.

2. Ensure that the TraceDir attribute in the Sun MTP Client configuration file, KIXCLI.INI, is uncommented, and that the directory specified exists, is writable, and has sufficient space for diagnostic trace output.

3. Ensure that the TraceMask attribute in the Sun MTP Client configuration file, KIXCLI.INI, is uncommented and set to the value requested by your authorized Sun service provider.

4. Delete any unnecessary existing diagnostic trace files *.trc from the TraceDir.

5. Restart Sun MTP Client.

1. Stop Sun MTP Client.

2. Edit the KIXCLI.INI file, and set the TraceMask back to zero (or comment out the TraceMask line) to disable diagnostic trace.

3. Copy the trace file(s) *.trc to another location before restarting Sun MTP Client.

---

Configuring Sun MTP for a TCP/IP Connection to Sun MTP Client

Before using Sun MTP Client to connect to a Sun MTP region, the region must be configured to accept incoming TCP/IP connections. Access to the region by the PC Client is provided by specifying a port by number or name when starting the Sun MTP server on the host. The name is used to look up a well-known port number in /etc/services or NIS tables.

1. On the host, define the well-known port in /etc/services or NIS tables, for example: cicstcp 1435/tcp.

The well-known port can be used for one region. If additional regions running on the same machine will listen for a TCP connection, each Sun MTP server must identify a port that is unique on that machine.

2. Define the TCPRTERM environment variable in your Sun MTP setup file.

This sets the maximum number of concurrent inbound requests for TCP/IP connections from Sun MTP Client and remote Sun MTP or CICS regions. If there are more requests than available sessions, Sun MTP queues the extra requests, which may affect performance.

Each $TCPRTERM configured requires 32KB of shared memory.

3. Define the TCPSTERM environment variable in your Sun MTP setup file.

This sets the maximum number of concurrent outbound requests for TCP/IP connections to remote Sun MTP or CICS regions. If there are more requests than available sessions, Sun MTP queues the extra requests, which may affect performance.

Each $TCPSTERM configured requires 32KB of shared memory.

4. Define the KIXMAXIST environment variable in your Sun MTP setup file.

This sets the maximum number of autoinstalled Sun MTP Client and remote Sun MTP or CICS regions. A request from a remote region is rejected if there are no available entries to install the region.

See also Enabling Sun MTP to Receive Connections and the Sun Mainframe Transaction Processing Software Configuration Guide for additional information.

---

Configuring Sun MTP and SNA for an SNA-Connected Sun MTP Client

For information about configuring Sun MTP and SNA for a Sun MTP Client, refer to the chapter describing Intersystem Communication (ISC) in the Sun Mainframe Transaction Processing Software Configuration Guide.