MKS Implementer 2006 Administration Guide

Network Control Programs
Network Configuration
Network Control Program (NCP) is a software product that runs on an IBM mainframe. NCP
serves as a communications controller between two iSeries systems in a network. This is also
described as using Virtual Telecommunications Access Method (VTAM), IBM’s application
program interface.
Implementer users that use NCP must set up communications differently because of certain
communications parameters that are changed by NCP. These parameters are usually set to
the OS/400 defaults by most iSeries users; however, if you use NCP, the following
parameters do not usually use the OS/400 defaults:
remote location name
local location name
mode name
remote network identifier
Find the values for these four parameters on your system by displaying the description of the
APPC device description on the local system that connects to the remote system. Then,
specify the same values for these fields for the remote system in Network Configuration.
Network Configuration
The system-wide communication parameters used by Implementer are defined in Network
Configuration, option 46 on the Implementer Menu. Network Configuration allows you to
define and maintain information about the remote systems you deploy software changes to
using either SNA or TCP/IP distribution. Establishing a network configuration is only
required if you distribute to remote systems—you must define each remote system you
distribute to in Network Configuration.
If you use TCP/IP for distribution between host and remote systems, you must define the
TCP/IP address and port in Network Configuration. TCP/IP has additional setup
requirements as described in “Setting Up for TCP/IP Distribution” on page 173.
Implementer must be installed on the host system and the Implementer Receiver must be
installed on each remote system before you establish communications between the systems.
Once the systems are defined in Network Configuration, you can define the environments for
each remote system.
TIP If you have multiple remote environments, consider defining an environment
group to target with all remote distributions.
167