Use the SNANCP SET command to redefine parameters for the Gateway
components while the system is running.  These parameters will stay in
effect only until the Gateway is rebooted, or until you change them
again.

Additional information available:

ACCESS_NAMECIRCUITLINELOGGINGLUPU
SERVER

The SET ACCESS NAME command lets you create a name that represents a
list of parameters that are needed to access an IBM SNA system.  There
are no default access names and no default parameters for access
names.

An access name is identified by a string of 1 to 16 alphanumeric
characters.  You can choose any unique name which is meaningful to
users.

FORMAT:

        SET access-name-component parameter [...]

ACCESS NAME COMPONENTS:

        ACCESS NAME access-name-id

        Specifies the access name to be created or modified.  The
        access-name-id is a 1-to-16 character alphanumeric string.

        KNOWN ACCESS NAMES

        Defines or changes parameters for all known access names.

Note, do not include an underscore in "ACCESS NAME".

Additional information available:

APPLICATIONDATALOGON_MODELU_LISTNOTE
PU

Example

Format:  APPLICATION ibm-applid

Specifies (in no more than 8 characters) the name of the IBM
application to be accessed.  Ask the IBM system programmer for the
name of the application.

Format:  DATA data-string

Specifies (in no more than 32 characters) user-specific information
for a session.  If the data text contains spaces, enclose the data in
quotation marks.  Not all IBM applications require the data specified
with this parameter.  If you need to specify data for this parameter,
ask the IBM system programmer what it should be.

For security reasons, the data associated with this parameter is not
shown when non-privileged users enter a SHOW ACCESS NAME command.  To
have this information displayed on the screen, you must specify a
privileged username and password with the USE SYSTEM command.

Format:  LOGON MODE mode-name

Specifies (in no more than 8 characters) the name of the logon mode
table entry.  The logon mode table entry is one of potentially several
entries in a logon mode table.  Each entry is a set of rules and
protocols.  These entries are used by IBM applications to define how a
session is to be conducted.  The default table entry may be adequate
for your purposes.  Ask the IBM system programmer for the logon mode
table entry.

Format:  LU LIST lu-list

Specifies the LUs that will be used to access the IBM system.  The LU
List should contain LU numbers, or ranges of numbers, separated by
commas.  An example of a LU LIST is 1-10,54,15-34.  The LU LIST that
you specify replaces any list of LUs already defined for the access
name that you specify.

Note that you can specify the LUs for only one PU at a time with the
SET ACCESS NAME command.  The LU numbers that you list must be within
the range of valid LU numbers defined by the SET PU pu-id LU LIST
command.

Format:  NOTE quoted-string

Lets you specify additional information (no more than 30 characters)
that will appear in the SHOW SUMMARY display.  For example, you can
provide more information about the IBM application to which the access
name refers.  Specify the text of your note within quotation marks.
There is no default for the note parameter.

Format:  PU pu-id

Specifies the PU that will be used to access the IBM system.  Enter
the pu-id in the format SNA-nnn, for example, SNA-0.

SNANCP> SET ACCESS NAME CICS PU SNA-0 LU LIST 1-4 -
_SNANCP> APPLICATION CICS -
_SNANCP> NOTE "access to CICS"

This command defines an access name for CICS by specifying values for
PU, LU LIST, APPLICATION, and NOTE.

The SET CIRCUIT command defines or changes circuits and their
parameters.  Be sure that the circuit state is OFF before using SET
CIRCUIT (except for COUNTER TIMER, NOTE, and LOGGING)

FORMAT:

        SET circuit-component parameter [...]

CIRCUIT COMPONENTS:

        CIRCUIT circuit-id

        Defines or changes parameters for the circuit you specify.
        Enter the circuit-id in the format SDLC-n (for synchronous
        communication links) or CHAN-n (for channel-attached links).

        KNOWN CIRCUITS

        Defines or changes parameters for all known circuits.

Additional information available:

CHANNEL_ADDRESSCOUNTER_TIMERDUPLEXIDLE_TIMER
LINELOGGINGNOTERESPONSE_MODESTATESTATION_ADDRESS
STATION_ID

Example

Format:  CHANNEL ADDRESS addr

For IBM channel links, this parameter specifies the channel address
for the circuit.

Specify this parameter as three hexadecimal digits.  There is no
default channel address; the parameter must be explicitly specified.
Be careful in the specification of this parameter; an incorrect value
can cause other channel devices to fail You cannot set the circuit ON
unless you have assigned it a channel address.

This parameter is applicable only to circuits operating over IBM
channels.

Format:  COUNTER TIMER seconds

Specifies how long (0-65535 seconds) the counter timer should run.  If
event logging is enabled for information level messages, when the
timer expires, the counters are logged to the DECnet host, and the
counters are set to zero.

The default is 0, which means that the timer is not running.

Format:  DUPLEX {FULL|HALF}

Controls how data is transferred.  Specify whether the data transfer
is to be two-way simultaneous (FULL) or two-way alternate (HALF).  On
a circuit in FULL duplex mode, frames can be sent and received at the
same time.  On a HALF duplex mode circuit, each end must wait until
the other end has finished sending before it can send.

The circuit duplex must agree with the DATMODE parameter in the IBM
ACF/NCP GROUP or PU macro.  If the DATMODE parameter is specified as
FULL, the circuit is full-duplex and if the DATMODE parameter is
specified as HALF, the circuit is half-duplex.

The following combinations of circuit duplex and line duplex are
allowed:

      o  A full-duplex line and a half-duplex circuit.

      o  A full-duplex line and a full-duplex circuit.

      o  A half-duplex line and a half-duplex circuit.


Remember, for full-duplex data transfer, not only the circuit but also
the line must operating in full-duplex mode.  If you set the circuit
to FULL, the corresponding line duplex parameter must also be set to
FULL.  See SET LINE command.  However, you can run a half-duplex
circuit over a full-duplex line if you wish.

The default for circuit DUPLEX is HALF.  This parameter is not
applicable to IBM channel links.

Format:  IDLE TIMER seconds

Specifies the number of seconds (15-1800) the circuit should wait for
a poll from the IBM system.  If the idle timer expires, the circuit
will go to the on-timed out state, and, if logging is enabled, an
event message is logged to the DECnet host.  The default is 30
seconds.

This parameter is not applicable to IBM channel links.

Format:  LINE line-id

Allocates a line to the circuit.  You cannot set a circuit ON until
you have allocated a line to the circuit.  Use this parameter to
switch the same circuit between different lines.  SNANCP prompts you
for a line-id if you do not specify one.

Enter the line-id in the format SYN-n for synchronous communication
links, or CQ-n for channel-attached links.

For synchronous links, each circuit must use a different line.  For
channels, more than one circuit can share a common line.

Format:  LOGGING ENABLED keyword...

Determines the severity level of logged events.  One or more of the
keywords INFORMATIONAL, WARNING, and ERROR can be specified; each
level can be separately enabled or disabled.

The keyword ALL can be used as a short way of specifying all three
severity levels.

Fatal messages are always logged.  In other words, the FATAL level is
always enabled; you cannot disable it, and you cannot explicitly
specify it in the LOGGING ENABLED parameter.

Format:  NOTE quoted-string

Lets you specify additional information (no more than 30 characters)
that will be part of the SHOW SUMMARY display.  Specify the text of
your note within quotation marks.  The default is no note.

Format:  RESPONSE MODE {NORMAL|EXTENDED}

Specifies the frame numbering of the circuit as one of the following:
NORMAL (modulo 8) or EXTENDED (modulo 128).

Modulo 128 frame numbering is supported only on IBM ACF/NCP Version 4,
and the setting must correspond to the ACF/NCP LINE macro MODULO.  The
default is NORMAL.

This parameter is not applicable to IBM channel links.

Format:  STATE {ON|OFF}

Specifies the operational state of the circuit as ON or OFF.  The
circuit must be ON for Gateway operations.  The default is OFF.

Format:  STATION ADDRESS addr

Specifies the SDLC station (or tributary) address that the IBM system
uses to address the station on the line.  Enter this address as 2
hexadecimal digits.  The value must correspond with the setting of the
ADDR parameter for the IBM ACF/NCP PU macro.  The default is 01.

This parameter is not applicable to IBM channel links.

Format:  STATION ID hex-id

This parameter is for dial-up lines only.  This SDLC
Exchange-Identification (XID) string is specified as eight hexadecimal
digits.  It is sent to the IBM system when an XID command has been
received.  The first 3 digits must correspond with the setting of the
IDBLK parameter for the IBM VTAM PU macro.  The last 5 digits must
correspond with the setting of the IDNUM parameter for the IBM VTAM PU
macro.  The default is 00000000.

This parameter is not applicable to IBM channel links.

     1.  SNANCP> SET CIRCUIT SDLC-0 STATE OFF
         SNANCP> SET CIRCUIT SDLC-0 STATE ON DUPLEX HALF -
         _SNANCP> LINE SYN-0 NOTE "IBM line L022B"

         The first command creates the SDLC-0 circuit (if it did not
         previously exist) and sets it to the OFF state.  The second
         command modifies the values STATE, DUPLEX, LINE, and NOTE.

     2.  SNANCP> SET CIRCUIT CHAN-0 LINE CQ-0 STATE ON -
         _SNANCP> CHANNEL ADDRESS 080 -
         _SNANCP> NOTE "majnod H01LE, pu H010800"

         This command associates circuit CHAN-0 with line CQ-0, using
         channel address 080, and sets the circuit state to ON.

The SET LINE command defines or changes lines and their parameters.
SNANCP manages lines from the Gateway to the IBM system.

Make sure that the line state is OFF before using SET LINE to define
line parameters (except for COUNTER TIMER, NOTE, and LOGGING.)

FORMAT:

        SET line-component parameter [...]

LINE COMPONENTS:

        LINE line-id

        Defines or changes parameters for the line you specify.  Enter
        the line-id in the format SYN-n (for synchronous communication
        links) or CQ-n (for channel-attached links).

        KNOWN LINES

        Defines or changes parameters for all known lines.

Additional information available:

BUFFER_SIZECLOCKCOUNTER_TIMERDUPLEXFORCED_BURST
INTERLEAVELOGGINGMODEM_TYPENOTEPROTOCOL
RECEIVE_BUFFERSSIGNALLINGSTATE

Example

Format:  BUFFER SIZE bytes

Specifies the maximum size of the buffers used to receive frames
transmitted by the IBM host.

For SYN-n lines, the buffer size must be in the range of 265 to 1482
bytes, and must match the value specified for MAXDATA in the IBM
ACF/NCP PU macro.  Also, the PU SEGMENT SIZE parameter must be set to
the same value.  The default is 265.

For CQ-n lines, the buffer size must be in the range of 265 to 8250
bytes.  The chosen size must exceed the intended maximum RU size by at
least 9 bytes.  Thus, if you wish to be able to use a maximum RU size
of 2K bytes, specify a buffer size of 2057 (=2048+9) bytes.  The
default is 4105 bytes, which corresponds to a 4K RU.

Format:  CLOCK {INTERNAL|EXTERNAL}

Specifies whether clocking is INTERNAL or EXTERNAL.  Clocking
regulates the signals sent between the IBM system and the Gateway.
INTERNAL mode causes the Gateway's line interface to supply a clock
signal.  Use this mode of operation with loopback tests to allow
transmitted messages to be looped back through a passive loopback
connector.  Use INTERNAL mode for the CLOCK parameter only when
testing.  For normal data transfer, use EXTERNAL mode.  When you
specify EXTERNAL mode, the clock signal must be supplied externally to
the synchronous port.  The default is EXTERNAL.

This parameter is not applicable to IBM channel links.

Format:  COUNTER TIMER seconds

Specifies how long (0-65535 seconds) the counter timer should run.  If
event logging is enabled for information messages, when the timer
expires, the counters are logged to the DECnet host, and the counters
are set to zero.  The default is 0, which means that the timer is not
running.

Format:  DUPLEX {FULL|HALF}

Controls how modem signalling works.  The duplex mode of the line can
be HALF (half-duplex) or FULL (full-duplex).  The duplex mode must be
the same as that defined for the IBM modem.  To determine the IBM
modem setting, refer to the DUPLEX and ADDRESS parameters for the IBM
ACF/NCP line macro.

The line DUPLEX parameter sets only the physical characteristics of
the communications path.  Setting the line to FULL (full-duplex) does
not necessarily set the line protocol to full-duplex.  See the SNANCP
SET CIRCUIT command for information on setting the data transfer mode
to full- or half-duplex.  The default is HALF (half-duplex).

This parameter is not applicable to IBM channel links.

Format:  FORCED BURST {ENABLED|DISABLED}

For IBM byte multiplexer channels, this specifies whether the Gateway
should operate in forced-burst mode.  The keyword value is either
ENABLED or DISABLED.

With forced-burst enabled, the Gateway maintains ownership of channel
resources for the transfer of an entire data block.

With forced-burst disabled, the Gateway rearbitrates channel resources
every few bytes transferred.  This allows other devices fair access to
the channel, but may lower the total throughput rate for the Gateway.

The default mode is DISABLED.

For other IBM channel links, the FORCED BURST parameter is accepted
but ignored.  Also, FORCED BURST does not apply to synchronous
communication links.

Format:  INTERLEAVE bytes

For byte multiplexer channels not operating in the forced-burst mode,
the INTERLEAVE parameter specifies the number of data bytes to be
transferred before the Gateway may relinquish channel resources to
other devices on the channel.

The interleave factor ranges from 1 to 30 bytes.  The default is 16
bytes.

For byte multiplexer channels operating in forced-burst mode, and for
other IBM channel links, the INTERLEAVE parameter is accepted but
ignored.  INTERLEAVE does not apply to synchronous communication
links.

Format:  LOGGING ENABLED keyword...

Determines the severity level of logged events.  One or more of the
keywords INFORMATIONAL, WARNING, and ERROR can be specified; each
level can be separately enabled or disabled.

The keyword ALL can be used as a short way of specifying all three
severity levels.

Fatal messages are always logged.  In other words, the FATAL level is
always enabled; you cannot disable it, and you cannot explicitly
specify it in the LOGGING ENABLED parameter.

Format:  MODEM TYPE {NORMAL|DIAGNOSTIC}

Specifies the type of modem as one of the following:  NORMAL (for
transfer of data) or DIAGNOSTIC (for running diagnostics).  Most
modems are used only for transfer of data; however, IBM modems (such
as a 386x) can also be used for running diagnostics.

This parameter must agree with both the type of modem and the setting
of the LPDATS parameter for the IBM ACF/NCP LINE macro.  If LPDATS=NO,
set the modem type to NORMAL.  If LPDATS=YES, set the modem type to
DIAGNOSTIC.  The default is NORMAL.

This parameter is not applicable to IBM channel links.

Format:  NOTE quoted-string

Lets you specify additional information (no more than 30 characters)
that will be part of the SHOW SUMMARY display.  Specify the text of
your note within quotation marks.

Format:  PROTOCOL keyword

Defines the Data Link protocol to be used on this line.  The following
keywords can be used for the protocol name:

      o  SDLC POINT -- defines this line as one end of a
         point-to-point SDLC connection.  You may specify only one
         circuit per POINT line.

      o  SDLC TRIBUTARY -- defines this line as a tributary end of an
         SDLC multipoint group.

      o  CHANNEL BYTE -- defines this line as being attached to a byte
         multiplexer channel.

      o  CHANNEL BLOCK -- defines this line as being attached to a
         block multiplexer channel.

      o  CHANNEL SELECTOR -- defines this line as being attached to a
         selector channel.


The SDLC protocols can only be specified for SYN-n lines; the CHANNEL
protocols can only be specified for CQ-n lines.  The default protocol
is SDLC POINT or CHANNEL BLOCK, as appropriate to the line type.

Format:  RECEIVE BUFFERS number

Specifies the maximum number (16 to 512) of receive buffers to be
allocated to the line.

For synchronous links, you must make the following calculations and
use the larger of the two values as the parameter for RECEIVE BUFFERS:

     1.  2 * MAXOUT + 2

     2.  Maximum RU size / (MAXDATA-9) + 2


The MAXOUT and MAXDATA values are specified in IBM ACF/NCP macros.
Get these values from the IBM system programmer.  The parameter value
for RECEIVE BUFFERS is especially important when you are using
circuits with SDLC EXTENDED RESPONSE MODE.

For channel-attached links, there is no simple formula that you can
use.  Instead, the number of buffers depends on the expected activity
of the line.  Too few buffers can cause performance slowdowns; too
many buffers is simply a waste of resources.

The primary indication of too few receive buffers on a channel link is
that the 'local buffer errors' counter (SHOW LINE CQ-n COUNTERS) will
climb rapidly when the system is very active on the channel.

Format:  SIGNALLING {NORMAL|NRZI|HIGH SPEED}

For SDLC links, SIGNALLING specifies the convention for line signals
as NORMAL or NRZI.  The signalling mode maintains bit synchronization.
The parameter setting must correspond with the setting of the NRZI
parameter for the IBM ACF/NCP LINE macro.

In NORMAL mode, a 1 bit causes a high signal level, and a 0 bit causes
a low signal level.

NRZI (non-return-to-zero inverted) coding causes a polarity change
every time there is a binary 0 in the message.

For channel links, SIGNALLING specifies whether the data transfer mode
is NORMAL (using only service-in and service-out tags) or HIGH SPEED
(using data-in and data-out tags as well).  You should only specify
HIGH SPEED if the channel hardware supports this option.

The default SIGNALLING mode is NORMAL.

Format:  STATE {ON|OFF}

Specifies the operational state of the line as ON or OFF.  The line
must be ON for Gateway operations.

     1.  SNANCP> SET LINE SYN-0 STATE OFF
         SNANCP> SET LINE SYN-0 STATE ON CLOCK EXTERNAL DUPLEX HALF-
         _SNANCP> SIGNALLING NORMAL LOGGING WARNING NOTE "LINE L022B"

         The first command sets the line SYN-0 to the OFF state.  The
         second command modifies the values of STATE, CLOCK, DUPLEX,
         SIGNALLING, LOGGING, and NOTE.

     2.  SNANCP> SET LINE CQ-0 PROTOCOL CHANNEL BYTE

         This command defines line CQ-0 as being connected to a byte
         multiplexer channel.

The SET LOGGING command defines or changes which DECnet host nodes
will log gateway events, and whether the messages will be recorded in
a file or at a logging monitor.

This command controls how and where logging events are reported.  For
information on which events are logged for a certain component, see
the LOGGING parameter description under the SET command for LINE,
CIRCUIT, PU, LU, and SERVER.

FORMAT:

        SET logging-component parameter [...]

LOGGING COMPONENTS:

        LOGGING FILE

        Defines or modifies the specified parameters for the logging
        file.

        LOGGING MONITOR

        Defines or modifies the specified parameters for the logging
        monitor.  The logging monitor is OPCOM (OPerator's
        COMmunications facility).

        KNOWN LOGGING

        Defines or modifies the specified parameters for MONITOR and
        FILE classes of logging, if they are currently defined.

Additional information available:

KNOWN_SINKSNAMESINK_NODESTATE

Example

Format:  KNOWN SINKS

Specifies that this command is to be applied to all currently defined
logging sink nodes.  See also the SINK NODE parameter.

Format:  NAME sink-name

For the LOGGING FILE component, this indicates a file to which the
messages will be logged.  There is no default name for the LOGGING
FILE component.

For the LOGGING MONITOR component, this indicates an additional
monitor process to which the messages will be logged.  Events are
always logged to OPCOM.  If you use the SET LOGGING MONITOR NAME
command, events will be logged to the named monitor process in
addition to OPCOM.

Format:  SINK NODE node-id

Specifies the DECnet host node that will log the event messages.  By
default, the load host is used as the sink node.

Each time that you issue a SET LOGGING command with a different sink
node name, you create a new logging sink rather than changing the sink
node name associated with an existing sink.

Format:  STATE {ON|OFF}

Specifies whether event logging (to the specified sink or sinks) is ON
or OFF.

     1.  SNANCP> SET KNOWN LOGGING KNOWN SINKS STATE OFF

         This sets all logging on all sink nodes OFF.

     2.  SNANCP> SET LOGGING MONITOR SINK NODE DALI STATE ON

         This command causes event messages to be logged by OPCOM on
         DALI.

The SET LU command defines or changes parameters for an LU.  The LU
must have already been defined with a SET PU command.

If you create authorization entries or change authorization
information for an LU that is currently in use, the authorization
information will not affect the current session.  The Gateway will
check new information the next time it attempts to allocate the LU.

The AUTHORIZATION component qualifier cannot be entered on the same
command line as the LOGGING and NOTE parameters.  Use a separate
SNANCP command line to create authorization entries.

FORMAT:

        SET lu-component [component-qualifier] parameter [...]

LU COMPONENTS:

        LU lu-id

        Defines or changes parameters for a specific LU.  Enter the
        lu-id in the format pu-id.nnn, for example, SNA-0.1.

        KNOWN LUS

        Defines or changes the specified parameter(s) for all known
        LUs.

Additional information available:

LOGGINGNOTE

Component QualifiersExample

Format:  LOGGING ENABLED keyword...

Determines the severity level of logged events.  One or more of the
keywords INFORMATIONAL, WARNING, and ERROR can be specified; each
level can be separately enabled or disabled.

The keyword ALL can be used as a short way of specifying all three
severity levels.

Fatal messages are always logged.  In other words, the FATAL level is
always enabled; you cannot disable it, and you cannot explicitly
specify it in the LOGGING ENABLED parameter.

Format:  NOTE quoted-string

The NOTE parameter lets you specify additional information (no more
than 30 characters) that will be part of the SHOW SUMMARY display.
Specify the text of your note within quotation marks.

AUTHORIZATION auth-id

KNOWN AUTHORIZATIONS

Defines or changes a specific authorization entry or all known
authorization entries for the specified LUs.  Authorization entries
allow you to control access to Gateway functions on an LU basis.  The
auth-id is a name you use to identify an authorization entry.  The
auth-id can be used with other SNANCP commands, such as CLEAR and
SHOW, to manipulate the authorization entry.  Enter the auth-id as a
string of up to 16 alphanumeric characters, for example, BAUHAUS.

All access control parameters except PASSWORD support the asterisk
wildcard character.  An asterisk in the pattern matches zero or more
characters in the string against which it is compared.  The comparison
is not sensitive to the case of the characters.

If no authorization entries are defined for a particular LU, then
access to that LU is not restricted.

You can define any of all of the following access control parameters
for an authorization entry.

Additional information available:

NODEUSERTERMINALPASSWORD

Format:  NODE node-name

Specifies the node name which matches this authorization entry.  If
not specified, then all node names match.

The node name is a string of 1 to 6 alphanumeric characters.

Format:  USER user-name

Specifies the user name which matches this authorization entry.  If
not specified, then all user names match.

The user name is a string of 1 to 32 alphanumeric characters.

Format:  TERMINAL term-name

Specifies the terminal name which matches this authorization entry.
If not specified, then all terminal names match.

The terminal name is a string of 1 to 32 characters.  The format
depends on aspects of the VAX/VMS configuration; use the following as
a guide:

        Connection?  Cluster?         Format         Example
        -----------  --------         ------         -------

        Hardwired    Single system    ddcu           TXA3

        Hardwired    VAXcluster       node$ddcu      MANRAY$OPA0

        Terminal     N/A              server$port    TSRV01$PORT_5
         server

Note, do not include any other punctuation such as a colon in the
device name.

Format:  PASSWORD password

Specifies the password to be supplied by the user of this
authorization entry.  If the PASSWORD parameter is not specified, then
no password is required.

The password is a string of 1 to 32 characters.

     1.  SNANCP>SET LU SNA-0.1 NOTE "IBM LUs L022B01-19"

         The command adds a note about the range of LUs to the SHOW
         SUMMARY display for LU SNA-0.1.

     2.  SNANCP> SET LU SNA-0.1 AUTHORIZATION ATEST -
         _SNANCP> NODE TIBBET USER SYSTEM PASSWORD ENOLA
         SNANCP> SET LU SNA-0.1 LOGGING ERROR

         The first command defines the authorization entry for access
         to the LU SNA-0.1.  String values are provided for NODE,
         USER, and PASSWORD.

         The second command specifies non-authorization parameters for
         LU SNA-0.1.  Non-authorization parameters (LOGGING and NOTE)
         cannot be entered on the same command line with authorization
         information.

The SET PU command defines or changes PUs and their associated
parameters.  The SET PU command also defines LUs for a PU.  Make sure
that the PU is inactive before using SET PU to define any parameters
(except COUNTER TIMER, NOTE, and LOGGING).  To make a PU inactive, set
the corresponding circuit to the OFF state.

FORMAT:

        SET pu-component parameter [...]

PU COMPONENTS:

        PU pu-id

        Defines or changes the specified parameters for a specific PU.
        Enter the pu-id in the format SNA-nnn, for example, SNA-0.

        KNOWN PUS

        Defines or changes the specified parameter(s) for all known
        PUs.

Additional information available:

CIRCUITCOUNTER_TIMERLOGGINGLU_LISTNOTEQUERY_THRESHOLD
SEGMENT_SIZESSCP_ID

Example

Format:  CIRCUIT circuit-id

Allocates a circuit to the PU.  The circuit you specify must already
have been defined with the SET CIRCUIT command.  Enter the circuit-id
in the format SDLC-n or CHAN-n.

You must specify this parameter and provide a circuit-id before a PU
can be used.

Format:  COUNTER TIMER seconds

Specifies how long (0-65535 seconds) the counter timer should run.
Each time the counter timer expires, an event message recording all
the counter values is logged to the DECnet host.

The default is 0, which means the timer is not running.

Format:  LOGGING ENABLED keyword...

Determines the severity level of logged events.  One or more of the
keywords INFORMATIONAL, WARNING, and ERROR can be specified; each
level can be separately enabled or disabled.

The keyword ALL can be used as a short way of specifying all three
severity levels.

Fatal messages are always logged.  In other words, the FATAL level is
always enabled; you cannot disable it, and you cannot explicitly
specify it in the LOGGING ENABLED parameter.

In addition, the logging level set for the PU is used as the default
for subsequently-created LUs (LUs are created on their first
appearance in the LU LIST parameter).

Format:  LU LIST lu-list

Defines a range of LU numbers (1-255) that are to be associated with
the PU.  The LU numbers must correspond with the LU addresses defined
in the setting of the LOCADDR parameter for the IBM ACF/NCP LU macro.
Separate each number or range of numbers by a comma.  The list you
specify replaces any LU list already defined for that PU.  Note that
the Gateway will reject any attempt to activate an LU not specified in
the list.  The following is an example of an LU list:

        1-6,8,10,12-15

Format:  NOTE quoted-string

Lets you specify additional information (no more than 30 characters)
that will be part of the SHOW SUMMARY display.  Specify the text of
your note within quotation marks.

Format:  QUERY THRESHOLD seconds

Specifies the number of seconds (0-65535) that must elapse between
REMQS (Request Maintenance Statistics) messages.

The IBM Network Problem Determination Application (NPDA) can send
REQMS messages, asking for the Gateway counters, at regular intervals.
This parameter defines what the interval must be.  For messages sent
at the proper intervals, the Gateway send its counters back to NDPA in
a RECFMS (Record Formatted Maintenance Statistics) message.  The
Gateway returns a negative response to any messages not sent at the
proper intervals.  If the value of this parameter is 0, the Gateway
processes all REQMS messages it receives.  The default for this
parameter is 0.

Format:  SEGMENT SIZE bytes

Specifies the size of the frames (265-1482) to transmit to the IBM
host.  For synchronous links, the SEGMENT SIZE value should match the
value of the MAXDATA parameter for the IBM ACF/NCP PU macro.  The
default is 265.

For channel-attached links, any value specified for this parameter is
effectively ignored.  Instead, the gateway computes a suitable value
from VTAM connection parameters at the time the link is established.

Format:  SSCP ID sscp-id

Identifies the SSCP that may activate this PU.  You should specify no
more than 8 SSCP IDs.  You must use a separate SET PU command for each
SSCP ID you define.  The ID should be 4 hexadecimal digits long.  Each
ID you specify is added to those already defined for that PU.

The SSCP identifier must correspond to the IBM VTAM SSCPID start
option specified for the VTAM hosts to which the Gateway can be
connected.

The Gateway compares the SSCP ID in an SNA activation message with the
SSCP IDs you have specified.  If the SSCP identifier in the activation
message matches any of the identifiers defined, the Gateway accepts
the activation, otherwise the Gateway rejects it.  If you do not
define any SSCP identifiers, the Gateway will accept an activation
message with any SSCP identifier.

SNANCP> SET CIRCUIT SDLC-0 STATE OFF
SNANCP> SET PU SNA-0 CIRCUIT SDLC-0 SSCP ID 0040-
_SNANCP> LU LIST 1-19 SEGMENT SIZE 256 NOTE "IBM PU P022B"

The first command sets the circuit SDLC-0 to the OFF state.  The
associated PU, SNA-0, becomes inactive.  The second command defines
new values for CIRCUIT, SSCP ID, LU LIST, SEGMENT SIZE, and NOTE.

The SET SERVER command defines or changes servers and their
parameters.  Before defining a server or a setting server parameters,
make sure the server is in the OFF state.

FORMAT:

        SET server-component [component-qualifier] parameter [...]

SERVER COMPONENTS:

        SERVER server-id

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

        KNOWN SERVERS

        Defines or changes the parameters for all known servers.

For DHCF, set the server state OFF before you set the maximum links
and PU LU list parameters.

Additional information available:

LOGGINGLU_LISTMAXIMUM_LINKSNOTESTATEPU
TEXT_FILE

Component QualifiersExample

Format:  LOGGING ENABLED keyword...

Determines the severity level of logged events.  One or more of the
keywords INFORMATIONAL, WARNING, and ERROR can be specified; each
level can be separately enabled or disabled.

The keyword ALL can be used as a short way of specifying all three
severity levels.

Fatal messages are always logged.  In other words, the FATAL level is
always enabled; you cannot disable it, and you cannot explicitly
specify it in the LOGGING ENABLED parameter.

Format:  PU pu-id LU LIST lu-list

Allocates and deallocates LUs to DHCF.  This parameter indicates which
LUs are allocated to the DHCF server and with which PU the LUs are
associated.

The PU parameter must always preced the LU LIST parameter.  Enter the
pu-id in the format SNA-nnn, for example, SNA-0.

To specify an lu-list, the LU numbers must be between 1 and 255.
Separate each number or range of numbers by a comma.  For example:
1-6,8,10,12-15.

A SET SERVER PU pu-id LU LIST lu-list command replaces any existing LU
list with the list you specify.

The number of LUs allocated to DHCF cannot exceed the maximum number
of logical links defined with the SET SERVER DHCF MAXIMUM LINKS
command.

Format:  MAXIMUM LINKS number

Specifies the maximum number (1-512) of DECnet logical links that can
be active for the named server.

For SNA-ACCESS, this parameter limits the number of people who can use
the access routines that need the SNA-ACCESS server.  For the 3270 TE,
for example, there must be one logical link for each 3270 TE user.

For RJE, this parameter limits the number of workstations and streams
you can have.  Each workstation uses one logical link when defined.
In addition, one link is needed for each assigned stream when the
workstation is in the 'on' state.

For DHCF, this parameter limits the number of concurrent DHCF
sessions.  Each session uses one logical link when active.

Each server may have a built-in limit on the maximum number of logical
links which it supports.  If you specify a parameter value larger than
this supported maximum, then the supported maximum will be used.
Similarly, if this parameter is not explicitly set, then it will
default to the maximum supported value or to 512 as appropriate.

Format:  NOTE quoted-string

Lets you specify additional information (no more than 30 characters)
that will be part of the SHOW SUMMARY display.  Specify the text of
your note within quotation marks.

Format:  STATE {ON|OFF}

Specifies the operational state of the server as ON or OFF.  The
server state must be ON for you to use the Gateway functions.  The
default is OFF.

Format:  PU pu-id LU LIST lu-list

Qualifies a subsequent LU LIST parameter (see under LU_LIST).  Applies
to DHCF only.

Format:  TEXT FILE file-spec

Specifies a file you want to display on the screen when a DHCF user
connects to the gateway.  You can edit the file to contain whatever
information you would like.  The contents of the file are translated
to EBCDIC and displayed on lines 12-22 of the logon screen.

The format for the file specification is as follows:

        node"access info"::device:[directory]filename.type

The default node is the Gateway load host.  If you omit any part of
the file specification, VAX/VMS defaults will be used.

The same text file is used for the logon screen for all LUs allocated
to be used by DHCF users on the Gateway.

DHCF assumes that the 3270 screen has 80 columns.  If a terminal is
set to use more than or fewer than 80 columns, the logon screen may
not be displayed correctly.

Use the CLEAR SERVER TEXT FILE command to remove a current text file,
before you define a new one.

When you use the SET SERVER TEXT FILE command, DHCF reads the text
file even if the server state is off.  By looking at the SHOW SERVER
DHCF display, you can ensure the logon screen has been included before
you set the server state to ON.

The following component qualifiers apply only to the SNA-ACCESS
server.

LU lu-id

Allocates the specified LU to the SNA-ACCESS server for automatic
activation of a DECnet object (program) to handle outbound session
allocation.

KNOWN LUs

Allocates all known LUs to the SNA-ACCESS server for automatic
activation of a DECnet object (program) to handle outbound session
allocation.

You can define one or more of the following outbound connection
parameters for the specified LUs:

Additional information available:

NODEOBJECT_NAMEOBJECT_NUMBERUSERPASSWORD
ACCOUNT

Format:  NODE node-name

Indicates the name of the DECnet node that will receive the bind
request.

In a VAXcluster, you can use the actual node name or the alias node
identifier for the entire cluster.  The name that you use depends on
the specific object to which you are connecting and your cluster
environment.

Format:  OBJECT NAME string

A string of 1 to 12 characters that identifies the DECnet object that
is to receive the BIND request.

Format:  OBJECT NUMBER number

A number from 0 to 255 that identifies the number of the DECnet object
that is to receive the bind request.

Format:  USER user-name

Indicates the user identification to establish the logical link.  The
user name is a string of 1 to 39 characters.

Format:  PASSWORD password

Indicates the password to establish the logical link.  The password is
a string of 1 to 39 characters.

Format:  ACCOUNT account

Indicates the user account to establish the logical link.  The account
is a string of 1 to 39 characters.

     1.  SNANCP> SET SERVER SNA-ACCESS STATE ON LOGGING ERROR

         This command defines the state of the SNA-ACCESS server as
         on, and sets the logging level to error.

     2.  SNANCP> SET SERVER DHCF STATE ON MAX LINKS 3 PU SNA-0 -
         _SNANCP> LU LIST 15-17 LOGGING WARNING LOGGING ERROR -
         _SNANCP> TEXT FILE NODEA::DISK$DHCF:[DHCF]LOGON.TXT

         This command defines the STATE, MAXIMUM LINK, PU, LU LIST,
         TEXT FILE,

         and LOGGING parameters for the DHCF SERVER.