02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix B: Environment Examples<br />

428<br />

This is the first Network Configuration Maintenance panel<br />

Field Description<br />

System Specify the system name to send changes to (can only be defined when<br />

you define a new system).<br />

Description Specify a brief description of the system.<br />

Target release Specify the OS/400 release level of the remote (target) system.<br />

*CURRENT: Remote system is at same operating system level as host<br />

system.<br />

*PRV: Remote system is at an earlier release of the operating system.<br />

Name: Specify the version name, for example, V5R2M0.<br />

SNA Communications options<br />

The following options allow you to define how to distribute to the remote system.<br />

Remote location name Specify the name of the remote location that changes are sent to. If you<br />

use Network Control Program (NCP), this is the NCP system name. It is<br />

not the name displayed in Display Network Attributes (DPSNETA). The<br />

value *SYSTEM uses the current system name.<br />

Local location name Specify the name of the local location where changes are sent from.<br />

Mode name Specify the name of the system object that contains controlling information<br />

for an APPC session. Enter a specific mode name, or *NETATR to use the<br />

default identifier in the network attributes. If you created a communication<br />

mode for <strong>Implementer</strong>, use IMPMODD.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!