C H A P T E R 3 |
Configuring Sun MTP Client and Sun MTP |
There are two procedures you must perform before using Sun MTP Client to connect to Sun MTP.
Sun MTP Client can connect a machine running Windows or Solaris to multiple Sun MTP regions simultaneously (see FIGURE 1-1). Each of these regions must be defined to Sun MTP Client in the Systems section of KIXCLI.INI, a control file. The location of this file is platform dependent:
The default version of the file is illustrated in CODE EXAMPLE 3-1.
Before running Sun MTP Client, you must edit this file to define the Sun MTP regions, as described in Adding Systems to the KIXCLI.INI File. In addition, you can modify some of the behavior of Sun MTP Client by entries in the General section of the file as described in Defining Client Behavior in 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.
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:
Name (up to 8 characters) by which the region is known by Sun MTP Client. |
|
Set to the characters, TCP, to indicate the definition of a TCP/IP-connected system. |
|
TCP/IP port number on which the region is listening for TCP connections from Sun MTP Client. On the UNIX host, the Sun MTP server, unikixmain, must be started with the -P option and this port number (see Starting Sun MTP Client on Windows). |
|
Comment (up to 60 characters), which can be zero length. However, you must type a comma to delimit the port number field. |
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.
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.
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.
Note - Use the semicolon character to comment out any entries you do not need. As shipped and illustrated in CODE EXAMPLE 3-1, most of the entries in the General section are commented out. |
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.
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.
Note - On Windows NT you can also run a diagnostic trace from the Control panel of the admin program, KIXCTLG. |
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.
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.
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.
Copyright © 2003, Sun Microsystems, Inc. All rights reserved.