Additional information available:

CLEAREXITHELPLOOPSETSHOWSPAWN
USE SYSTEMZERO

commands

The values you defined during installation and configuration of the
Gateway are used as the initial values for the Gateway parameters.
Once the Gateway is up and running, you can redefine and manage
Gateway components with SNANCP commands.  The values you specify using
SNANCP commands stay in effect until one of the following happens:

      o  You change the values with further SNANCP commands

      o  You reboot the Gateway (possibly after editing the
         configuration file)


An SNANCP command consists of four parts:  a command verb, a component
identifier, one or more parameters, and one or more qualifiers.

For each command, you must supply a command verb and a component
identifier.  Optionally, you may supply one or more parameters from
the parameter list, and qualifiers from the qualifier list.

Separate SNANCP command line elements by spaces or tabs.  To continue
a long command to the next line, use the standard line continuation
convention (a hyphen as the last character in the line.) For example:

        SNANCP> SET LINE SYN-0 STATE ON DUPLEX HALF -
        _SNANCP> SIGNALLING NORMAL MODEM TYPE NORMAL

Use an exclamation point to designate a comment line.

SNANCP allows you to abbreviate commands and keywords to their
shortest unique form.

The command HELP gives you help on various SNANCP topics.

Additional information available:

ComponentsParametersQualifiers

The gateway is made up of a number of layered components which provide
different protocol handling services.  Management of the Gateway
components is done using SNANCP commands; management of DECnet
components of the gateway system is done using NCP commands.

The following items are Gateway components:  line, circuit, PU, LU,
access name, and server.

Define the Gateway components in the following order:  line, circuit,
PU.  When you define a PU, you also define the LUs associated with it.

You can define access names and servers at any time.

When using some of the SNANCP commands, you can specify KNOWN in place
of a specific component name.  The command then applies to all the
components defined.  To apply the command to all components that are
active, specify ACTIVE instead.

Additional information available:

Access namesCircuitsLinesLUsPUsServers

Access names represent a list of parameters that can be used to
establish a session with an application running on the IBM system.
You can define an access name at any time.

An access name is identified by a string of 1 to 16 alphanumeric
characters, for example, NCCF.

Circuits represent the data link protocol on the line.  You must
define a line before you define a circuit to attach to that line.

A circuit is identified as SDLC-n for circuits using the SDLC
protocol, or as CHAN-n for circuits using IBM channel protocol.

Lines are the physical links that the Gateway will use to transfer
data to the IBM system.  The link may be a synchronous link or a
channel-attached link, depending on the communication hardware
involved.

For synchronous links, each line supports single circuit.  For
channel-attached links, the line can support more than one circuit,
all sharing the same link.

A line is identified as SYN-n for synchronous links, or as CQ-n for
channel-attached links.

LUs (Logical Units) allow end users to access other LUs in an SNA
network.  A certain number of LUs are defined in an SNA host for use
by different types of applications.  When defining a PU, you define
LUs for the Gateway as a subaddress of the PU.

An LU is identified as pu-id.nnn, where 'nnn' is the logical unit
number or session address.  For example, SNA-0.1.

PUs (Physical Units) provide the low-level communications services for
the node.  You must define a circuit before you can define a PU for
that circuit.  The Gateway is a PU type 2 to the IBM SNA network.

A PU is identified as SNA-n.

Servers provide the services needed by the DECnet/SNA access routines.
For example, you need the SNA-ACCESS server if you want to use the
DECnet/SNA VMS DDXF, DECnet/SNA VMS 3270 Terminal Emulator, DECnet/SNA
VMS Application Programming Interface, DECnet/SNA VMS APPC/LU6.2
Programming Interface, DECnet/SNA VMS 3270 Data Stream Programming
Interface, or DECnet/SNA VMS Printer Emulator access routines.

The server id is one of the following:  DHCF, RJE, or SNA-ACCESS.

Each component has a set of parameters which define additional options
for that component (for example, when defining a LU you can specify
parameters which control access to the LU, specify the logging level
for the LU or add note text for the LU).  You can enter as many
parameters as you like, in any order; separate each parameter with a
space.  Some parameters have default values.

Use the CLEAR command to set a component's parameters to the default
values, or to delete the component.

Use the HELP command, under topic SET, to list a component's
parameters and the parameter's default values.

Some components have special parameters which are termed qualifiers.
When included in a command, the qualifier identifies a named
subcomponent of the component.

For example, the command SET LU SNA-0.1 changes parameters associated
with the LU named SNA-0.1.  By contrast, the command SET LU SNA-0.1
AUTHORIZATION FRED changes parameters associated with the
authorization entry named FRED, which is in turn associated with the
LU named SNA-0.1.

Qualifiers are listed in the help text where applicable.