MKS Implementer 2006 Administration Guide

Setting Up Communications Entries
3 Press ENTER to access the third Network Configuration Maintenance panel and continue
entering the information.
To determine the description of the communication lines, on the host system use the
Display Line Description (DSPLIND) command for:
attached non switched controllers for the control unit
connection type for the line type
4 Press ENTER to update the changes.
To configure Network Configuration for TCP/IP distribution
If you use TCP/IP for distribution between host and remote systems, complete these steps
for each remote system you distribute to. In addition, if you use the Remote Initiated Move
Update Host feature, you must complete these steps for the host system.
1 Follow the previous steps to create or change the system.
2 From the Network Configuration Maintenance panel, press ENTER twice to display the
fourth Network Configuration Maintenance panel.
3 Complete the fields on this panel as follows:
In the TCP/IP Address field, specify an IP address, a system name in a DNS server,
or a system name in a host table. The default value is blank.
In the Port field, specify a valid number between 1 and 65535. The default number is
30005. MKS recommends you use a number higher than 1024 to avoid conflict with
standard services such Telnet, FTP, and Web servers.
The port you define on the host system must match the port defined on the remote
system. The port value must also match the port value you specify in the
Communications Control (ICOMCTL) command you define on both the host and
remote systems as described in “Setting Up for TCP/IP Distribution” on page 173.
4 Press ENTER to update the system record.
Setting Up Communications Entries
Implementer uses communications to distribute requests from the host system to one or more
remote systems. You have three options for setting up Implementer for communications and
distribution between systems:
use pre-existing communications entries
add communications entries using an existing mode description
add communications entries using an Implementer-specific mode description
169