1 – SNA Access Server
The SNA Access Server entity provides an interface to the Peer Server for client applications in the TCP/IP and DECnet-Plus networks. By means of its two subentities: Port and Object, the Access Server manages client connections and provides ports through which the clients can communicate with their partners in the SNA network.
1.1 – create
The create verb generates a new instance of the SNA Access Server entity or subentity. Create sets the entity state to off, sets the entity's attributes to their default values, and allocates resources for the entity. create sna access server The create sna access server command creates the SNA Access Server entity. The create command allocates resources for the single entity and sets its characteristic attributes to their defaults. Ex, ncl> create sna access server
1.1.1 – Characteristic
Maximum (0-1024) Specifies the number of concurrent
Connections client connections supported by the
Peer Server. Set this number
according to the number of SNA
sessions required by client
applications during peak usage.
The default is 1024.
1.2 – delete
delete sna access server The delete sna access server command deletes the single instance SNA Access Server entity. The entity must be in the Off entity state and have no Object or Port subentities before it can be deleted. Ex, ncl> delete sna access server
1.3 – disable
disable sna access server The disable sna access server command discontinues the service provided by the SNA Access Server. Current Port subentities, if any, are unaffected and the entity goes into the Shut entity state. The server enters the Off entity state when all the Ports are deleted. Ex, ncl> disable sna access server
1.4 – enable
enable sna access server The enable sna access server command enables the Access Server for operation and use. The Server entity enters the on entity state. Ex, ncl> enable sna access server
1.5 – set
set sna access server The set sna access server command lets you modify the number of concurrent client connections supported by the Peer Server. This is done through the Maximum Connections characteristic. Ex, ncl> set sna access server maximum connections = 512
1.5.1 – Characteristic
Maximum (0-1024) Specifies the number of concurrent
Connections client connections supported by the
Peer Server. Set this number
according to the number of SNA
sessions required by HP SNA
applications during peak usage.
The default is 1024.
1.6 – show
show sna access server The show sna access server command displays the attributes for the SNA Access Server entity. The SNA Access Server manages client connections and provides ports through which TCP/IP and DECnet-Plus applications can communicate with their partners on the IBM side. Ex, ncl> show sna access server all
1.6.1 – Status
UID Displays the entity's unique identifier, which is
generated when the Peer Server creates the entity.
State Displays the operational state of the SNA Access
Server entity. The operational states are
Off The Access Server is disabled and not
available for use.
On The Access Server is enabled and available
for use.
Shut The Access Server is acting on a disable
command. It enters the off state at the
end of active sessions, if any.
Active Displays the current number of active client
Connections connections to the SNA Access Server module.
Peak Displays the peak number of client connections
Connections that have been active at any one time.
1.6.2 – Characteristics
Maximum (0-1024) Displays the number of concurrent
Connections client connections supported by the
Peer Server.
Version Displays the version number of the
SNA Access Server software that is
executing.
1.6.3 – Counters
Creation Displays the time when the entity was created.
Time
Connections Displays the total number of client connections
Created created to and from the SNA Access Server module.
Connection Displays the total number of client connection
Failures creation failures.
Inbound Displays the total number of client connections
Connections accepted by the SNA Access Server module from
Accepted non-SNA applications. The Peer Server
increments this counter each time the SNA Access
Server entity generates an Inbound Connection
Accepted event.
Outbound Displays the total number of client connections
Connections started by the SNA access server module and
Accepted accepted by non-SNA applications. The Peer Server
increments this counter each time the SNA Access
Server entity generates an Outbound Connection
Accepted event.
Inbound Displays the total number of client connections
Connections rejected by the SNA Access Server module from
Rejected nonSNA applications. The Peer Server increments
this counter each time the SNA Access Server
entity generates an Inbound Connection Rejected
event.
Outbound Displays the total number of client connections
Connection attempted by the SNA access server module and
Rejected rejected by nonSNA applications. The Peer Server
increments this counter each time the SNA Access
Server entity generates an Outbound Connection
Rejected event.
Transport Displays the number of times that an SNA Access
Abnormal Server Port entity was disconnected as a result
Terminations of failures within DECnet or TCP/IP. Such failures
include any client connection termination that is
not initiated from either the SNA Access Server
module or the nonSNA application. The Peer
Server increments this counter each time the SNA
Access Server entity generates a Transport Abnormal
Termination event.
SNA Abnormal Displays the number of instances when an SNA Access
Terminations Server Port entity was disconnected as a result of
failures within the SNA network. Such failures
include any session termination that is not
initiated from either the SNA Access Server module
or the remote CP. The Peer Server increments this
counter each time the SNA Access Server entity
generates an SNA Abnormal Termination event.
Protocol Displays the total number of Gateway Access Protocol
Violation (GAP) violations that have occurred with nonSNA
Errors applications. This is a measure of internal
functioning. Refer problems involving this counter
to your customer support representative. The Peer
Server increments this counter each time the SNA
Access Server entity generates a Protocol Violation
Error event.
Resource Displays the total number of resource allocation
Allocation failures (for example, failures caused by
Failures insufficient memory).
1.7 – SNA Access Server Object Subentity
The SNA Access Server Object entity describes an endpoint in the non-SNA network to connect to when the SNA network sends an unsolicited SNA Session startup request (BIND) to the Peer Server. The SNA Access Server Object contains parameters that describe how to connect to a remote application using TCP/IP, DECnet-Plus, or a local transport for applications that run on the same system as the Peer Server. Objects are not needed to handle inbound sessions to the SNA network (3270 Terminal emulator sessions for example).
1.7.1 – create
create sna access server object
The create sna access server object command creates an object and
defines values for the parameters that define the connection. The
create command also sets the characteristics to their default
values and allocates resources for the entity.
Depending on the transport type, different parameters are used
during creation.
o For decnet, the node name and number or task are used.
o For tcpip, the internet node name and service or port are used.
o For local transport, the task or command name and local
username are used.
The following three examples illustrate the use of the create
command for (i) decnet, (ii) tcpip, and (iii) a local transport.
i) In the following example, a connection is made to the DECnet-Plus
node .lkg.axp object number 143. Instead of an object number,
you may specify a named DECnet object (or Session Control
application).
ncl> create sna access server object cpicprog node = .lkg.axp, -
_ncl> number = 143, transport = decnet
ii) In this example, a connection is made to the tcpip port number
7004 on the Internet node xxx.yyy.dec.com. Instead of using a
numbered port, you may use a TCP service name. The mapping of
name to number occurs on the local machine at the time of
connection.
ncl> create sna access server object dspiprog -
_ncl> internet node = xxx.yyy.dec.com, number = 7004, -
_ncl> transport = tcpip
iii) In this example, a process is started on the local machine by
running the command line specified in the command attribute
under the local username that has been set. If a username has
not been set, the program is run under the root username.
ncl> create sna access server object localprog -
_ncl> command = "/usr/local/app1.ksh", local username = barney, -
_ncl> transport = local
1.7.1.1 – Characteristics
Transport tcpip | Specifies the type of transport
decnet | protocol used to reach the object.
local The choices are decnet, tcpip, and
local.
Node dns-fullname Specifies the DECnet-Plus node to
which to connect. Applies to DECnet
transport only.
Number (0-255) Specifies the number of the object.
Applies to decnet transport only.
Task Simplename Specifies the task name of the object.
This characteristic is used only when
the number characteristic is non-zero.
If this characteristic is specified
for objects with a non-zero number
characteristic, the value is ignored.
Local Simplename Specifies the name of the user to run
Username the application as. Applies to local
transport only.
Command alpha-string Specifies the command to be passed to
the local object. Applies to local
transport only.
Internet alpha-string Specifies the name of the Internet
Node node to which to connect in the named
or "dotted" number format. Applies to
tcpip transport only.
Port (0-32767) The integer that identifies the TCP
port number on the remote node. The
port characteristic should not be
set when the service characteristic
is set. Applies to tcpip transport
only.
Service Simplename The name of the service on the remote
node. Applies to tcpip transport
only.
1.7.2 – delete
delete sna access server object The delete sna access server object command deletes the named instance of the Object entity. Ex, ncl> delete sna access server object obj-1
1.7.3 – set
set sna access server object
The set sna access server object command lets you modify the
values for the characteristics of the Object entity. The Object
entity of the SNA Access Server is the end-user address (called
an Object) to which the Peer Server connects in response to an IBM
request.
The following three examples illustrate the use of the set command
for (i) decnet, (ii) tpcip, and (iii) a local transport.
i) In the following example, a connection exists to the DECnet-Plus
node .lkg.axp. The following set command establishes a
connection to object number 153. Instead of an object number,
you may specify a named DECnet object (or Session Control
application).
ncl> set sna access server object cpicprog node = .lkg.axp, -
_ncl> number = 153, transport = decnet
ii) In this example, a connection is made to the Internet node
xxx.yyy.dec.com. The following example connects to port
number 1009. Instead of using a numbered port, you may use a
TCP service name. The mapping of name to number occurs on the
local machine at the time of connection.
ncl> set sna access server object dspiprog -
_ncl> internet node = xxx.yyy.dec.com, number = 1009, -
_ncl> transport = tcpip
iii) In this example, a process exists on the local machine. The
following set command establishes an object for the specified
username by running the command line specified in the command
attribute. If a username is not set, the program is run under
the root username.
ncl> set sna access server object localprog -
_ncl> command = "/usr/local/app1.ksh", -
_ncl> local username = barney, transport = local
1.7.3.1 – Characteristics
Transport tcpip | Specifies the type of transport
decnet | protocol used to reach the object.
local The choices are decnet, tcpip, and
local.
Node dns-fullname Specifies the DECnet-Plus node to
which to connect. Applies to DECnet
transport only.
Number (0-255) Specifies the number of the object.
Applies to DECnet transport only.
Task Simplename Specifies the task name of the object.
This characteristic is used only when
the number characteristic is non-zero.
If this characteristic is specified
for objects with a non-zero number
characteristic, the value is ignored.
Local Simplename Specifies the name of the user to run
Username the application as. Applies to local
transport only.
Command alpha-string Specifies the command to be passed to
the local object. Applies to local
transport only.
Internet alpha-string Specifies the name of the Internet
Node node to which to connect in the named
or "dotted" number format. Applies to
tcpip transport only.
Port (0-32767) The integer that identifies the Port
on the remote node. Applies to tcpip
transport only.
Service Simplename The name of the service on the remote
node. Applies to tcpip transport
only.
1.7.4 – show
show sna access server object The show sna access server object command displays the values of the attributes for the SNA Access Server Object entity. The Object entity of the SNA Access Server is the end-user address (called an Object) to which the Peer Server connects in response to an IBM request. Ex, ncl> show sna access server object obj-1 all
1.7.4.1 – Characteristics
Transport tcpip | Displays the type of transport
decnet | protocol used to reach the object.
local The choices are tcpip, decnet, and
local.
Node dns-fullname Displays the name of the DECnet node
to which to connect.
Number (0-255) Displays the number of the object.
Applies to DECnet transport only.
Task Simplename Displays the task name of the
object. This characteristic is used
only when the Number characteristic
is non-zero. If this
characteristic is specified for
objects with a non-zero Number
characteristic, the value is
ignored.
Local Simplename Displays the name of the user that
Username is running the local object. Applies
to local transport only.
Command alpha-string Displays the command to be passed to
the local object. Applies to local
transport only.
Internet alpha-string Displays the name of the internet
Node node to which to connect. Applies to
tcpip transport only.
Port (0-32767) The integer that identifies the
TCP/IP Port on the remote node.
Applies to tcpip transport only.
Service Simplename The name of the TCP/IP service name
on the remote node. Applies to tcpip
transport only.
1.7.4.2 – Identifier
name Displays the string that you provided to identify
the entity.
1.8 – SNA Access Server Port Subentity
The SNA Access Server Port entity represents an access point to the services of the SNA Access Server module. Ports are created dynamically by the Peer Server to handle client connections.
1.8.1 – show
show sna access server port The show sna access server port command displays the attributes for the SNA Access Server Port entity. Ex, ncl> show sna access server port 37 all status
1.8.1.1 – Identifier
Name Displays the name created by the Peer Server for this
Port.
1.8.1.2 – Status
Protocol Displays the protocol state of the client
State connection.
Connecting The SNA Access Server is initiating a connection
Inbound to an IBM system.
Connecting The SNA Access Server is initiating a connection
Outbound to a nonSNA access routine.
Disconnect- The SNA Access Server is terminating the
ing connection.
In Session The SNA Access Server has established the
connection and the session partners have
exchanged a BIND request and a positive response.
Not In Connection has been established; the BIND request
Session and its positive response have not yet been
exchanged.
Off The initial state of a port when the Access Server
first creates it
Client Displays the name of the SNA LU Services
LU Session entity using this port.
Protocol Displays the negotiated Gateway Access protocol
Version version (GAP) in use over this client connection.
Authorization Displays the identifier of the SNA LU Services
Authorization entity that granted access to this
port.
Node Displays the name of the user's node (relevant
only if the underlying transport is decnet).
User Name Displays the name of the user connected by the
client connection.
Terminal Name Displays the name of the user's terminal.
Process Displays the user's process identifier. Note
Identifier that the identifier is always displayed as zero
if the GAP protocol version is less than V3.0.
Program Name Displays the name of the program on the
remote node that is using this port.
Local Transport Displays the client connection identifier used
Identifier on the Peer Server node.
Remote Transport Displays the client connection identifier used
Identifier on the nonSNA application's node.
Internet Displays the name of the connected node
Node (relevant only if the underlying transport is
TCP/IP).
Transport Displays the name of the underlying transport.
2 – SNA LU Services
The SNA LU Services module contains the SNA Logical Services functions for the Peer Server. SNA LU Services contains the following subentities: LU, Access Name, Authorization, and Partner LU. The LU entity supports the Session subentity.
2.1 – create
create sna lu services The create sna lu services command creates a single instance of the SNA LU Services entity, allocates resources for the entity, and initializes the entity's attributes to their default values. Ex, ncl>create sna lu services default transmission group = tg-1
2.1.1 – Characteristics
Default Simplename Specifies the Transmission Group
Transmission that should be used when processing
Group a Primary LU connection if the
Partner LU entity associated with the
connection has no Transmission
Group defined. This allows Partner
LU entities to name the remote
network ID and the LU name for the
remote LU but does not require that
the Transmission Group be named.
The default is to have no Default
Transmission Group name set.
2.2 – delete
delete sna lu services The delete sna lu services command deletes a single instance of the SNA LU Services module. Before the entity can be deleted, all subentities of this entity must have been deleted. Ex, ncl> delete sna lu services
2.3 – set
set sna lu services The set sna lu services command lets you set the default transmission group characteristic for the SNA LU Services entity. Ex, ncl> set sna lu services default transmission group = tg-1
2.3.1 – Characteristic
Default Simplename Specifies the Transmission Group that
Transmission should be used when processing a
Group primary LU connection if the Partner
LU entity associated with the
connection has no Transmission Group
defined. This allows Partner LU
entities to name the remote network id
and the LU name for the remote LU but
does not require that the Transmission
Group be named.
2.4 – show
show sna lu services The show sna lu services command displays the values of the attributes for the SNA LU Services entity. Ex, ncl> show sna lu services default transmission group
2.4.1 – Status
Uid Displays the unique identifier for the SNA LU
Services entity.
Active Displays the number of active LU-LU sessions.
Sessions
Queued Displays the total number of queued session
Sessions requests. SNA LU Services queues sessions
when the session limit for the Peer
Server LU is reached in either direction
(PLU or SLU) when the session initiation
requests queueing. On the Peer Server the
session limit for an LU is established with the
Maximum Active Sessions characteristic.
Active SSCP- Displays the number of currently active
LU Sessions SSCP-LU sessions.
2.4.2 – Characteristics
Version Displays the version number of the
SNA LU Services module.
PU Type independent Displays the type of physical unit on
which SNA LU Services operates. The
type defines the services and its
subentities.
Default Simplename Displays the Transmission Group that
Transmission should be used when processing
Group a Primary LU connection if the
Partner LU entity associated with the
connection has no Transmission
Group defined. This allows Partner
LU entities to name the remote
network ID and the LU name for the
remote LU but does not require that
the Transmission Group be named.
2.4.3 – Counters
Creation Displays the date and time this entity was
Time created.
Total Displays the number of LU-LU sessions started
Started by the SNA LU Services entity.
Sessions
Total Displays the number of sessions terminated
Terminated since the SNA LU Services entity was
Sessions created.
Session Displays the number of session requests that
Start the SNA LU Services entity could not honor.
Failures SNA LU Services increments this counter each
time the SNA LU Services entity generates a
Session Start Failure event.
ACTLUs Displays the number of ACTLU requests
Received received.
DACTLUs Displays the number of DACTLU requests
Received received.
Resource Displays the total number of resource allocation
Allocation failures, such as failures caused by
Failures insufficient memory.
Protocol Displays the number of protocol violations
Violation detected for all the sessions supported by
Errors the SNA LU Services entity. SNA LU Services
increments this counter each time the SNA
LU Services entity generates a Protocol
Violation Error event.
2.5 – Access Name Subentity
An SNA LU Services Access Name entity contains information that is required to establish a connection to the SNA network. The use of access names offers the client applications a way of connecting to the SNA network without having to know the exact IBM application names or logon mode names required. The use of access names is optional.
2.5.1 – add
add sna lu services access name
The add sna lu services access name command adds a set of additional
LU names to the LU List characteristic of an existing Access Name.
The LU names may be complete names or contain wild cards (? or *).
The only characteristic that this command takes is the LU List,
which adds new LU names to an Access Name entity's LU List.
Ex, ncl> add sna lu services access name cics -
_ncl> lu list = {lu001,lu002,lu1*}
2.5.1.1 – Characteristics
LU List list of sna Optional characteristic that specifies
network the entire set or a member of the set
names of LUs accessible using this Access
Name entity. The default is No
names. The elements of the list must
be separated by commas, and the list
must be enclosed in braces, { }.
2.5.2 – create
create sna lu services access name
The create sna lu services access name creates a single instance
of the Access Name entity, allocates resources, and initializes
attributes to their default values.
Ex, ncl> create sna lu services access name cics -
_ncl> lu list = {lu003, lu004, lu20*}, partner lu = cics17
2.5.2.1 – Characteristics
LU List sna-network- Specifies the set of SNA LU
name[,...]} Services LU entities accessible
using this Access Name entity.
When users specify this access name,
the Peer Server can assign the user
to any available LU in the set. This
characteristic is optional. You can
use wild cards to specify the entire
set of LUs (for example, L1*) or to
specify one of the members in the set
of LUs (for example, L1786, L19*,
L18*).
Logon Mode sna-network- Specifies the Logon Mode entity
name that LU Services should use if
the user does not specify a logon
mode. This characteristic is
optional.
User Data text-string Specifies optional user-level data
(surrounded by quotation marks) to
pass to the remote LU. This data may
include, for example, user name
identification information. This
characteristic is optional. The user
data is entered as ASCII text and
is translated to EBCDIC before being
sent to the remote LU.
Partner LU sna-network- Specifies the instance name of the
name Partner LU entity that defines the
remote LU. For a secondary LU
connection, the Partner LU
contains the name of the IBM
application that the connection is
to communicate with. For a primary
LU connection, the Partner LU
attribute names a Partner LU
entity in the Peer Server. The
Partner LU entity contains the
actual qualified SNA Network Name
and the Transmission Groups to use
when establishing a connection to
the remote application or terminal.
This characteristic is optional.
2.5.3 – delete
delete sna lu services access name The delete sna lu services access name command removes the Access Name and deallocates its resources. Ex, ncl> delete sna lu services access name acnam-1
2.5.4 – set
set sna lu services access name
The set sna lu services access name command lets you set the
characteristics of the SNA LU Services Access Name entity. Refer to
the create sna lu services access name command for more information
about the Access Name subentity.
Ex, ncl> set sna lu services access name lusvc2 -
_ncl> logon mode = user08, partner lu = prtlu1
2.5.4.1 – Characteristics
LU List sna-network- Specifies the set of SNA LU
name[,...]} Services LU entities accessible
using this Access Name entity.
When users specify this access name,
the Peer Server can assign the user
to any available LU in the set. This
characteristic is optional. You can
use wild cards to specify the entire
set of LUs (for example, L1*) or to
specify one of the members in the
set of LUs (for example, L1786,
L19*, L18*).
Logon Mode sna-network- Specifies the Logon Mode entity
name that LU Services should use if
the user does not specify a logon
mode. This characteristic is
optional.
User Data text-string Specifies optional user-level data
(surrounded by quotation marks) to
pass to the remote LU. This data may
include, for example, user name
identification information. This
characteristic is optional. The user
data is entered as ASCII text and
is translated to EBCDIC before being
sent to the remote LU.
Partner LU sna-network- Specifies the instance name of the
name Partner LU entity that defines the
remote LU. For a secondary LU
connection, the Partner LU attribute
contains the name of the IBM
application that the connection is
to communicate with. For a primary
LU connection, the Partner LU
attribute names a Partner LU
entity in the Peer Server. The
Partner LU entity contains the
actual qualified SNA Network Name
and the Transmission Groups to use
when establishing a connection to
the remote application or terminal.
This characteristic is optional.
2.5.5 – show
show sna lu services access name The show sna lu services access name command displays the values of the attributes for the SNA LU Services Access Name entity. Access names are optional; they serve as shortcuts for supplying several parameter values with one name. Ex, show sna lu services access name cics logon mode, lu list
2.5.5.1 – Identifier
Name Identifies the name given to the Access Name entity
when it was created.
2.5.5.2 – Characteristics
LU List sna-network- Displays the set of SNA LU
name[,...]} Services LU entities accessible
using this Access Name entity.
When users specify this access name,
the Peer Server can assign the user
to any available LU in the set. This
characteristic is optional. You can
use wild cards to specify the entire
set of LUs (for example, L1*) or to
specify one of the members in the set
of LUs (for example, L1786, L19*,
L18*).
Logon Mode sna-network- Displays the Logon Mode entity
name that SNA LU Services should use if
the user does not specify a Logon
Mode. This characteristic is
optional.
User Data text-string Displays optional user-level data
(surrounded by quotation marks) to
pass to the remote LU. This data may
include, for example, user name
identification information. This
characteristic is optional. The user
data is entered as ASCII text and
is translated to EBCDIC before being
sent to the remote LU.
Partner LU sna-network- For a secondary LU connection, the
name Partner LU attribute contains the
name of the IBM application that the
connection is to communicate with.
For a primary LU connection, the
Partner LU attribute names a Partner
LU entity in the Peer Server. The
Partner LU entity contains the
actual qualified SNA Network Name
and the Transmission Groups to use
when establishing a connection to
the remote application or terminal.
This characteristic is optional.
2.6 – Authorization Subentity
The Authorization subentity of the SNA LU Services entity is created to describe connection parameters that are optionally matched to an incoming client connection to validate access to Peer Server LUs. You can create multiple instances of the Authorization entity each with different characterisitics. If the information passed by a user matches the characteristics of an Authorization entity associated with the specified LU, then SNA LU Services allows the user to access the LU. An Authorization entity can describe DECnet, TCP/IP, or local connections. For a TCP/IP connection, the internet node characteristic is used instead of node.
2.6.1 – create
create sna lu services authorization
The create sna lu services authorization command creates an SNA LU
Services Authorization entity. The command allocates and sets the
characteristics to their defaults.
Ex, ncl> create sna lu services authorization programmers -
_ncl> node=star, user=prg_*, password=axp, transport=decnet
2.6.1.1 – Characteristics
User Simplename Specifies the user name that the user
must supply to be granted access to
the LU. If the null user name is
specified, SNA LU Services does not
perform any user name checking when
using this Authorization entity. The
user name can contain wild card
characters.
Password Simplename Specifies the password that the user
must supply to be granted access to
the LU. If the null password is
specified, SNA LU Services does not
perform password checking when using
this Authorization entity. Note that
you cannot display this
characteristic.
Node full name Specifies the DECnet node that the
user must supply to be granted access
to the LU. If you do not specify the
node name (0:), SNA LU Services does
not perform node name checking when
using this Authorization entity.
Applies only if the transport is
DECnet.
Terminal Simplename Specifies the terminal that the user
must use to be granted access to the
LU. If the null terminal name is
specified, SNA LU Services does not
perform any terminal name checking
when using this Authorization entity.
The terminal name can contain wild
card characters.
Transport decnet | Specifies the transport that must
tcpip | underlie a connection for the
local connection to be authorized.
Internet alpha-string Specifies the node name of the
Node internet node that the user must use
to be granted access to the LU. You
can use wild cards when specifying
the node name, Further, SNA LU
Services performs no node checking
if no node name is specified.
2.6.2 – delete
delete sna lu services authorization The delete sna lu services authorization command deletes the Authorization entity and deallocates its resources. Ex, ncl> delete lu services authorization auth-1
2.6.3 – set
set sna lu services authorization The set sna lu services authorization command lets you set the characteristics of the SNA LU Services Authorization entity. Ex, ncl> set sna lu services authorization luauth1 password = secret
2.6.3.1 – Characteristics
User Simplename Specifies the user name that the user
must supply to be granted access to
the LU. If the null user name is
specified, SNA LU Services does not
perform any user name checking when
using this Authorization entity. The
user name can contain wild card
characters.
Password Simplename Specifies the password that the user
must supply to be granted access to
the LU. If the null password is
specified, SNA LU Services does not
perform password checking when using
this Authorization entity. Note that
you cannot display this
characteristic.
Node full name Specifies the DECnet node that the
user must supply to be granted access
to the LU. If you do not specify the
node name (0:), SNA LU Services does
not perform node name checking when
using this Authorization entity.
Applies only if the transport is
DECnet.
Terminal Simplename Specifies the terminal that the user
must use to be granted access to the
LU. If the null terminal name is
specified, SNA LU Services does not
perform any terminal name checking
when using this Authorization entity.
The terminal name can contain wild
card characters.
Transport decnet | Specifies the transport that must
tcpip | underlie a connection for the
local connection to be authorized.
Internet alpha-string Specifies the node name of the
Node internet node that the user must use
to be granted access to the LU. You
can use wild cards when specifying
the node name. Further, SNA LU
Services performs no node checking
if no node name is specified.
2.6.4 – show
show sna lu services authorization
The show sna lu services authorization command displays the values of
the attributes for the SNA LU Services Authorization entity. The
password characteristic cannot be displayed.
Ex, ncl> show sna lu services authorization payroll internet node, -
_ncl> terminal, user
2.6.4.1 – Identifier
Name Identifies the name given to the Authorization entity
when it was created.
2.6.4.2 – Characteristics
User Simplename Displays the user name that the user
must supply to be granted access to
the LU. If the null user name is
specified, SNA LU Services does not
perform any user name checking when
using this Authorization entity. The
user name can contain wild card
characters.
Node full name Displays the DECnet node that the
user must use to be granted access to
the LU. If you specify the node name
(0:), SNA LU Services does not
perform node name checking when
using this Authorization entity.
Applies only if the transport is
DECnet.
Terminal Simplename Displays the terminal that the user
must use to be granted access to the
LU. If the null terminal name is
specified, SNA LU Services does not
perform any terminal name checking
when using this Authorization
entity. The terminal name can
contain wild card characters.
Transport decnet | Displays the transport that must
tcpip | underlie a connection for the
local connection to be authorized.
Internet character Displays the node name of the
Node string Internet node. Applies only if the
transport is tcpip.
2.7 – LU Subentity
A logical unit is a named access point into an SNA network. The SNA LU Services LU entity defines one logical unit that is owned and managed by the Peer Server. Each logical unit has a corresponding SSCP-LU session which is also owned and managed by the entity. An LU can participate in one or more LU-LU sessions, each of which is supported by a corresponding Session subentity
2.7.1 – add
add sna lu services lu
The add sna lu services lu command adds a set of additional
Authorization entities to the authorization list characteristic of an
existing LU. The names of the Authorization entities may be complete
names or contain wildcards (? or *).
Ex, ncl> add sna lu services lu l1905 -
_ncl> authorization list = {programmers, managers}
2.7.1.1 – Characteristics
Authorization list of Specifies the set of Authorization
List simple names entities securing this LU. Each
value in the list is the name of an
Authorization entity that defines a
set of user characteristics. By
associating particular Authoriz-
tion entities with this LU, you
authorize the users identified in
those entities to use this LU. In
order to activate the authorization
check, you must set the access
attribute of the LU to restricted.
There is no default.
2.7.2 – create
create sna lu services lu
The create sna lu services lu command creates one instance of
an LU entity . The command also allocates resources for the entity
and initializes attributes to their default values. An LU entity
can be defined so that is has the capability to represent a secondary
LU, a primary LU, or either a primary or secondary LU. You must define
secondary LUs for non-SNA applications that communicate with primary
LUs on an IBM system. You must define primary LUs for non-SNA
applications that communicate with secondary LUs owned by an IBM
system.
Ex, ncl> create sna lu services lu lu01 access = restricted,
_ncl> capability = primary
2.7.2.1 – Characteristics
Dependent LU Simplename Specifies the Transmission Group on
Transmission which the LU acts as a dependent
Group LU.
Dependent 1-byte Specifies the LU address on the
LU Address decimal transmission group on which the LU
acts as a dependent LU.
Maximum (0-65535) Specifies the maximum number of
Active sessions allowed on this LU. If
Sessions this LU is going to support
HP SNA 3270 terminal emulation
or any other application
requiring single sessions on an LU,
set the capacity to 1. Otherwise, you
can set the capacity to 0, indicating
unlimited sessions. If you later
find that you want to restrict the
number of sessions on this LU, you
can change this characteristic to the
maximum number of sessions you want
to allow.
Capability primary | Specifies whether this LU can act as
secondary | a primary LU, secondary LU, or both.
both The setting you choose depends on the
capability of the HP SNA
applications that will use this LU.
If this LU is for applications that
emulate a primary LU, set the
capability as primary. If this LU is
for non-SNA applications that
emulate a secondary LU, set the
capability as secondary. If you want
this LU to be used for both types of
non-SNA applications, set the
capability to both.
Object Simplename Specifies the name of an SNA
Access Server Object entity that
the SNA Access Server should use
to initiate a connection to an
access routine in response to an
IBM-initiated session request. When
the IBM side requests a session using
this LU, the Peer Server uses the
information provided in the Object
entity to determine how to connect
to the access routine.
Destination Simplename Specifies an optional parameter that
Unit the Peer Server name passes to
HP SNA access routine products
to identify a resource within the
HP SNA access routine. It applies
to IBM-initiated connections only.
The HP SNA access routine determines
the use of this characteristic.
This characteristic is used in
conjunction with Object
characteristics to identify the
non-SNA resource the Peer Server must
connect to.
Access restricted| Specifies whether SNA LU Services
unrestricted should check authorization when a
non-SNA user or application
accesses this LU. If you set this LU
as restricted, you must also define
the specific authorization
information required by using
Authorization entities, and you must
name those entities in the
Authorization List characteristic
for this LU.
Authorization {simple- Specifies the set of authorization
List name[,...]} entities securing this LU. Each value
in the list is the name of an
Authorization entity that defines a
set of user characteristics. By
associating particular Authorization
entities with this LU, you authorize
the users identified in those
entities to use this LU. In order to
activate the authorization check, you
must set the access characteristic to
restricted.
Old Name [pu-name] Specifies an alternative name for
session- this LU, usable by applications that
number pair support only the older style of LU
identification. One application that
uses this older form is the HP SNA
3270 Terminal Emulation product. An
Old Name characteristic must be
defined for a Peer Server LU only
when the application does not support
using an access name for LU
specification. If the name supplied
contains a period (.), you must
enclose it with quotes ("").
2.7.3 – delete
delete sna lu services lu The delete sna lu services lu command deletes an SNA LU Services LU entity instance and deallocates resources that were allocated for it. The LU must be in the off state for the delete to succeed. Ex, ncl> delete sna lu services lu lu001
2.7.4 – disable
disable sna lu services lu The disable sna lu services lu command disables the ability of the LU to establish a new LU-LU session without affecting current sessions. Any passively connected user Ports are terminated and the LU enters the Off entity state. You can also use the disable command to suspend the operation of an entity temporarily. An LU cannot be disabled if its dependent LU protocol state is in the active state. Ex, ncl> disable sna lu services lu lu002
2.7.5 – enable
enable sna lu services lu The enable sna lu services lu command puts the LU in a state wherein it is able to become active. The LU's entity state is set to on. Sessions can be started on a dependent LU when it is activated by the SSCP. For a dependent LU, the enable succeeds if the transmission group that is named exists in the SNA CP Services definition and the dependent LU address is unique. Ex, ncl> enable sna lu services lu lu002
2.7.6 – set
set sna lu services lu
The set sna lu services lu command lets you set the
characteristics for the SNA LU Services LU entity.
Ex, ncl> set sna lu services lu l1905 access = restricted, -
_ncl> capability = primary
2.7.6.1 – Characteristics
Dependent LU Simplename Specifies the Transmission Group on
Transmission which the LU acts as a dependent
Group LU.
Dependent 1-byte Specifies the LU address on the
LU Address decimal transmission group on which the LU
acts as a dependent LU.
Maximum (0-65535) Specifies the maximum number of
Active sessions allowed on this LU. If
Sessions this LU is going to support
HP SNA 3270 terminal emulation
or any other application
requiring single sessions on an LU,
set the capacity to 1. Otherwise,
you can set the capacity to 0,
indictaing unlimited sessions. If you
later find that you want to restrict
the number of sessions on this LU,
you can change this characteristic
to the maximum number of sessions you
want to allow.
Capability primary | Specifies whether this LU can act as
secondary | a primary LU, secondary LU, or both.
both The setting you choose depends on
the capability of the HP SNA
applications that will use this LU.
If this LU is for applications that
emulate a primary LU, set the
capability as primary. If this LU
is for non-SNA applications that
emulate a secondary LU, set the
capability as secondary. If you want
this LU to be used for both types of
non-SNA applications, set the
capability to both.
Object Simplename Specifies the name of an SNA
Access Server Object entity that
the SNA Access Server should use
to initiate a connection to an
access routine in response to an
IBM-initiated session request.
When the IBM side requests a session
using this LU, the Peer Server uses
the information provided in the
Object entity to determine how to
connect to the access routine.
Destination Simplename Specifies an optional parameter that
Unit the Peer Server name passes to
HP SNA access routine products
to identify a resource within the
HP SNA access routine. It applies
to IBM-initiated connections only.
The HP SNA access routine determines
the use of this characteristic.
This characteristic is used in con-
junction with Object characteristics
to identify the non-SNA resource the
Peer Server must connect to.
Access restricted| Specifies whether SNA LU Services
unrestricted should check authorization when a
non-SNA user or application
accesses this LU. If you set this
LU as restricted, you must also
define the specific authorization
information required by using
Authorization entities, and you must
name those entities in the
Authorization List characteristic
for this LU.
Authorization {simple- Specifies the set of authorization
List name[,...]} entities securing this LU. Each value
in the list is the name of an
Authorization entity that defines a
set of user characteristics. By
associating particular Authorization
entities with this LU, you authorize
the users identified in those
entities to use this LU. In order to
activate the authorization check, you
must set the access characteristic to
restricted.
Old Name [pu-name] Specifies an alternative name for
session- this LU, usable by applications that
number pair support only the older style of LU
identification. One application that
uses this older form is the HP SNA
3270 Terminal Emulation product. An
Old Name characteristic must be
defined for a Peer Server LU only
when the application does not support
using an access name for LU
specification. If the name supplied
contains a period (.), you must
enclose it with quotes ("").
2.7.7 – show
show sna lu services lu The show sna lu services lu command displays the values of the attributes for the SNA LU Services LU entity. Ex, ncl> show sna lu services lu lu01 all counters
2.7.7.1 – Identifier
Name Identifies the name given to the LU entity when it
was created.
2.7.7.2 – Status
UID Displays the unique identifier for the LU entity.
State Displays the operational state of this LU entity.
Off You have issued a disable command for this
LU. The LU is in the inactive or pending
inactive state.
On You have issued an enable command for
this LU. The LU is operational and is either
supporting sessions, is ready to support
sessions, or is in the pending active state.
Protocol Displays the protocol state of this LU.
State
Active This LU is enabled and is ready to be used in
sessions.
Inactive This LU is not enabled. You must issue an
enable command before SNA LU Services can
activate the LU.
In Use This LU is active and is in session, has a
link to a non-SNA application, or both.
Active Ports Displays the number of SNA ACCESS
Server Port entity instances that are using
this LU, which may or may not be involved in
an active LU-LU session.
Active Displays the number of active LU-LU sessions
sessions on this LU. You can limit this number by
setting the Maximum Active Sessions
characteristic of the LU entity.
Peak Active Displays the highest number of LU-LU sessions
Sessions active at any one time on this LU.
Queued Displays the number of outstanding queued
Sessions session requests for this LU.
Peak Queued Displays the highest number of LU-LU sessions
Sessions queued at any one time on this LU.
Activation Displays the time at which the LU was last
Time activated by the SSCP.
Dependent LU Displays an indication of whether the
Protocol State dependent LU has been activated by the SSCP.
2.7.7.3 – Characteristics
Dependent LU Simplename Displays the Transmission Group on
Transmission which the LU acts as a dependent
Group LU.
Dependent 1-byte Displays the LU address on the
LU Address decimal Transmission Group on which the LU
acts as a dependent LU.
Maximum (0-65535) Displays the maximum number of
Active sessions allowed on this LU. A
Sessions value of 0 means unlimited sessions.
Capability primary | Displays whether this LU can act as a
secondary | primary LU, secondary LU, or both.
both
Object Simplename Displays the name of an SNA Access
Server Object entity that the SNA
Access Server should use to initiate
a connection to a non-SNA access
routine in response to an
IBM-initiated session request.
Destination Simplename Displays an optional parameter that
Unit the Peer Server name passes to
non-SNA access routine products
to identify a resource within the
non-SNA access routine. It applies
to IBM-initiated connections only.
Access restricted| Displays whether SNA LU Services
unrestricted should check authorization when a
non-SNA user or application
accesses this LU.
Authorization {simple- Displays the set of Authorization
List name[,...]} entities securing this LU. Each
value in the list is the name of an
Authorization entity that defines
a set of user characteristics.
Old Name [pu-name] Displays an alternative name for
session- this LU, usable by non-SNA
number pair applications that support only the
older style of LU identification.
2.7.7.4 – Counters
Creation Displays the date and time this entity was
Time created.
SSCP-LU Displays the total number of bytes sent on the
Octets Sent SSCP-LU session.
SSCP-LU Octets Displays the total number of bytes received
Received on the SSCP-LU session.
SSCP-LU Displays the total number of RUs sent on the
RUs Sent SSCP-LU session.
SSCP-LU RUs Displays the total number of RUs received on
Received SSCP-LU session.
Total Octets Displays the total number of bytes sent by the
Sent LU for all sessions (LU-LU and SSCP-LU).
Total Octets Displays the total number of bytes received by
Received the LU for all sessions (LU-LU and SSCP-LU).
Total RUs Displays the total number of RUs sent by the
Sent LU for all sessions (SSCP-LU and LU-LU).
Total RUs Displays the total number of RUs received by
Received the LU for all sessions (SSCP-LU and LU-LU).
ACTLUs Displays the number of ACTLU requests
Received received.
Started Displays the number of times an LU-LU
Sessions successfully started on this LU.
Terminated Displays the number of LU-LU sessions that
Sessions have terminated on the LU since it was created.
SNA LU Services increments this counter each
time the LU entity generates a Session
Terminated event.
DACTLUs Displays the number of DACTLU requests
Received received.
BIND Displays the number of BIND requests that
Failures have been rejected on this LU.
Authorization Displays the total number of access violations
Failures caused by lack of authorization. Access
violations occur when the Access characteristic
of an LU entity is set to Restricted and valid
authorization information has not been
supplied in the session request.
2.8 – Partner LU Subentity
The SNA LU Services Partner LU entity is an internal definition that corresponds to a remote LU. Partner LUs contain information that describes an LU in the SNA network that is to be connected to when the non-SNA application acts as the Primary LU (PLU). The real IBM LU name and network ID are contained in the Partner LU definition, along with a list of Peer Server Transmission Groups that can be used to connect to the remote LU. The Partner LU database is not used for Dependent LU sessions (3270 TE or RJE, for example). An instance of the Partner LU entity must exist to describe each LU in the SNA network that is to be connected to by non-SNA PLU applications.
2.8.1 – add
add sna lu services partner lu
The add sna lu services partner lu command lets you add a set of
additional transmission group entries to the list of transmission
groups for the Partner LU. Be sure to use braces to confine a list
of values. Remember to separate list values and two or more
characteristics with commas.
Ex, ncl> add sna lu services partner lu l1905 -
_ncl> transmission group = {tg03}
2.8.1.1 – Characteristics
Transmission list of Specifies a list of the Transmission
Group Simplenames Groups to be used to connect to the
remote LU.
2.8.2 – create
create sna lu services partner lu The create sna lu services partner lu command creates an SNA LU Services Partner LU entity instance. The create command allocates resources for the entity and initializes entity attributes to their default values. Ex, ncl> create sna lu services partner lu cics17
2.8.2.1 – Characteristics
Destination Simplename Specifies the name of the remote LU
Name as known to the SNA network.
Destination Simplename Specifies the network id of the
Network network in which the remote LU
resides.
Transmission list of Specifies a list of the Transmission
Group Simplenames Groups to be used to connect to
the remote LU.
2.8.3 – delete
delete sna lu services partner lu The delete sna lu services partner lu command removes the entity and deallocates its resources. Ex, ncl> delete sna lu services partner lu cics17
2.8.4 – set
set sna lu services partner lu
The set sna lu services partner lu command lets you set the
attributes for the SNA LU Services Partner LU entity.
Ex, ncl> set sna lu services partner lu l1905 -
_ncl> transmission group = {tg01, tg02}
2.8.4.1 – Characteristics
Destination Simplename Specifies the name of the remote LU
Name as known to the SNA network.
Destination Simplename Specifies the network ID of the
Network network in which the remote LU
resides.
Transmission list of Specifies a list of the Transmission
Group Simplenames Groups to be used to connect to
the remote LU.
2.8.5 – show
show sna lu services partner lu The show sna lu services partner lu command displays the attributes for the SNA LU Services Partner LU entity. The SNA LU Services Partner LU has no counter attributes. Ex, ncl> show sna lu services partner lu cics17 all characteristics
2.8.5.1 – Identifier
Name Displays the name given to the Partner LU by the
Peer Server when it was created.
2.8.5.2 – Status
Definition Displays how the Partner LU was created. Values are
"Static" and "Dynamic."
2.8.5.3 – Characteristics
Destination sna-network- Displays the name of the remote LU
Name name as known in the SNA network.
Destination sna-network- Displays the network ID of the
Network name network in which the remote LU
resides.
Transmission list of Displays a list of the Transmission
Group Simplenames Groups to be used to connect to
the remote LU.
2.9 – LU Session Subentity
The SNA LU Services LU Session entity is created dynamically by the Peer Server in response to LU-LU session initiation requests. It is deleted dynamically when the corresponding session terminates. Multiple instances of this entity can exist.
2.9.1 – show
show sna lu services lu session
The show sna lu services lu session command displays the values of
the attributes for the SNA LU Services LU Session entity. The SNA LU
Services LU Session entity has no characteristic attributes.
Ex, ncl> show sna lu services lu lu01 session 2 transmission group, -
_ncl> lfsid
2.9.1.1 – Identifier
Name Identifies the name given to the Session entity by
the Peer Server when it was created by the Peer
Server.
2.9.1.2 – Status
SID Displays the 8-byte identifier assigned to the
session by the CP of the initiating LU. This
identifier is used in control messages.
LFSID Displays the session identifier for a given
session.
Protocol State Displays the operational state of this LU-LU
session:
Active The LU-LU session BIND negotiation was
successful, and the two LUs are now exchanging
data on this session.
BINDing The primary and secondary LUs are negotiating
the BIND for the LU-LU session.
Initiating The Peer Server has started internal session
startup operation.
Ready The session has initiated and is waiting for a
BIND request from either the SNA or non-SNA
session partner.
Terminating The LUs have unbound the session, and the Peer
Server and the remote CP are now terminating
the session.
UNBINDing The two LUs are exchanging UNBIND commands to
end the session.
Port Displays the name of the SNA Access Server
Port entity supporting this session. Each
Port entity represents a non-SNA application
link.
Remote LU Displays the name of the external LU that the
Peer Server LU is in session with.
Remote Network Displays the name of the network in which the
remote LU resides.
Initiating Displays the name of the LU that requested the
LU session.
Role Displays the role (primary or secondary) this
LU is assigned in he LU-LU session.
Transmission Displays the name of the Transmission Group
Group that the LU-LU session is using.
Logon Mode Displays the logon mode used to establish this
session.
Primary Displays the maximum RU size that can be
RU Size sent by the primary LU on this session.
Primary Displays the primary LU's send pacing window
Send Pacing size for this session.
Primary Displays the primary LU's receive pacing
Receive Pacing window size for this session.
Secondary Displays the maximum RU size that can be
RU Size sent by the secondary LU on this session.
Secondary Displays the secondary LU's send pacing
Send Pacing window size for this session.
Secondary Displays the secondary LU's receive pacing
Receive Pacing window size for this session.
LU Type Displays the LU type specified in the BIND for
this session.
Session Type Displays whether the session is a dependent
or independent LU session.
2.9.1.3 – Counters
Creation Displays the date and time this entity was
Time created.
Octets Sent Displays the total number of bytes sent on this
session by the LU.
Octets Displays the total number of bytes received
Received on this session by the LU.
RUs Sent Displays the total number of RUs sent on this
session by the LU.
RUs Displays the total number of RUs received on
Received this session by the LU.
2.9.2 – stop
stop sna lu services lu session The stop sna lu services lu session command starts the protocol procedures that terminates the LU-LU session. The stop command completes without waiting for the session to complete. Ex, ncl> stop sna lu services lu lu01 session 2 severity = cleanup
2.9.2.1 – Arguments
Severity The type of termination of the LU-LU session
that you want to initiate. The argument values
are as follows:
Cleanup This is the severest form of termination. The
session is ended without acknowledgment
from the Remote LU or the Remote SSCP. Use
this form as a last resort.
Forced This type is also a severe form of termination.
The session is being ended immediately and
unconditionally.
Orderly This type of termination ends the session as
soon as the PLU can do so. It is the least
severe form of termination.
3 – SNA CP Services
The SNA CP Services entity contains all the information that pertains to the Control Point, Path Control, and DLC Manager components. The module represents the SNA T2.1 node component that manages the T2.1- specific node component. Its only subentity is the Transmission Group entity.
3.1 – create
create sna cp services
The create verb creates the SNA CP Services entity. The create sna
cp services command also allocates resources for the entity and sets
its characteristics to their default values.
Ex, ncl> create sna cp services cp name = xcp01, -
_ncl> network id = usdec101
3.1.1 – Characteristics
Network ID Simplename Specifies the network id of the
T2.1 node. The required name must
conform to SNA naming conventions.
You should consult with the SNA
administrator about this name.
CP Name Simplename Specifies the network name of the
CP. The required name must
conform to SNA naming conventions.
You should consult with the SNA
administrator about this name.
Maximum (1-2048) Specifies the maximum number of
Active TGs Transmission Groups that can be
concurrently active. This optional
value can be set at any time. The
default value is 4.
3.2 – delete
delete sna cp services The delete sna cp services command deletes the SNA CP Services entity. Before you can delete the SNA CP Services entity, you must first delete all its Transmission Group subentities. Ex, ncl> delete sna cp services
3.3 – set
set sna cp services The set sna cp services command lets you set the characteristics for the SNA CP Services entity. The SNA CP Services entity contains all the information that pertains to the Control Point, Path Control, and DLC Manager components. Ex, ncl> set sna cp services maximum active tgs = 250
3.3.1 – Characteristic
Maximum (1-2048) Specifies the maximum number of
Active TGs Transmission Groups that can
be concurrently active. If you
specify a value less than the number
of currently active Transmission
Groups, you cannot activate new
Transmission Groups until the number
of currently active Transmission
Groups falls below this value. This
value can be set at any time.
3.4 – show
show sna cp services The show sna cp services command displays the values of the attributes for the SNA CP Services entity. The SNA CP Services entity contains all the information that pertains to the Control Point, Path Control, and DLC Manager components. Ex, ncl> show sna cp services cp name, network id
3.4.1 – Status
UID Display the UID associated with the SNA CP
Services entity.
Active PUs Displays the number of active PUs.
Active TGs Displays the number of active Transmission
Groups.
3.4.2 – Characteristics
Version Displays the version number of the
SNA CP Services software that is
executing.
Network ID Simplename Specifies the network ID of the
T2.1 node. The required name must
conform to SNA naming conventions.
You should consult with the SNA
administrator about this name.
CP Name Simplename Specifies the network name of the
CP. The required name must
conform to SNA naming conventions.
You should consult with the SNA
administrator about this name.
Maximum (1-2048) Specifies the maximum number of
Active TGs Transmission Groups that can be
concurrently active. This optional
value can be set at any time.
3.4.3 – Counters
Successful TG Displays the total number of successfully
Activations completed Transmission Group activation
procedures.
TG Activation Displays the total number of Transmission
Failures Group activations procedures that have failed
to complete due to an XID exchange error.
TG Deactivations Displays the total number of times
Transmission Groups have been deactivated.
TG Connections Displays the total number of times a
Lost Connection Lost event has been generated.
COLD ACTPUs Displays the total number of COLD ACTPUs
Received received.
ERP ACTPUs Displays the total number of ERP ACTPUs
Received received.
ACTPUs Rejected Displays the total number of negative responses
sent to ACTPU requests.
DACTPUs Displays the total number of DACTPUs received.
Received
Protocol Displays the total number of SNA protocol
Violations violations detected by the Peer Server.
Resource Displays the number of resource allocation
Allocation failures (for example, insufficient memory).
Failures
Creation Time Displays the time that the SNA CP Services
entity was created.
3.5 – SNA CP Services Transmission Group Subentity
The SNA CP Services Transmission Group subentity represents a link between a Peer Server local link station and an adjacent SNA system link station. The connection type can be permanent in which the datalink connection remains active when unused, or temporary in which the connection is automatically terminated and restarted in response to local session or remote link activation requests.
3.5.1 – create
create sna cp services transmission group The create sna cp services transmission group command creates the SNA CP Services Transmission Group subentity, which represents a link between a Peer Server local link station and an adjacent SNA system link station. The connection type can be permanent in which the datalink connection remains active when unused, or temporary in which the connection is automatically terminated and restarted in response to session or link activation requests. During creation you can specify that the Transmission Group be an Intranode type. An Intranode Transmission Group provides routing of PIUs for sessions between NAUs that reside on the same (local) node. Only one Intranode Transmission Group instance may exist. Ex, ncl> create sna cp services transmission group data link = sdlc
3.5.1.1 – Characteristics
Intranode yes | no Specifies whether this Transmission
Group is an Intranode Transmission
Group. The default is no. If you
specify yes, note the characteristics
that do to apply.
Connection permanent | Permanent means that the Transmission
Type temporary Group is activated when it is enabled
and remains active until it is
disabled. Temporary means that
the Transmission Group is activated
when a local session is created or
when a remote link station is
activated, and deactivated when there
are no sessions. The default is
permanent.
Dependent yes | no Specifies whether Dependent LUs
LU Support exist for the Transmission Group.
This attribute controls the
acceptance of ACTPU, DACTPU, ACTLU,
and DACTLU RUs as well as the LFSID
address space assignments for the
Transmission Group. The default is
no. Characteristic does not apply if
Intranode is yes.
Segmentation session | Specifies the kind of segmentation to
Support station | be performed by the Peer Server when
none communicating with the adjacent link
station. The default is session.
Characteristic does not apply if
Intranode is yes.
Bind Pacing (1-32767) Specifies the amount that the
Window adaptive BIND pacing algorithm
Increment increases the receiver window size
when a larger window size is
requested by the BIND sender and
when there are adequate
resources. This parameter is valid
when receiver BIND pacing is in
effect for the Transmission Group.
The default is 1. Characteristic
does not apply if Intranode is yes.
Disconnect (0-3600) Specifies the amount of time (in
Timer seconds) a temporary Transmission
Group should delay after zero
sessions are active before
deactivating the link station.
The default is 30.
XID Retry (1-60) Specifies the interval (in seconds)
Timer specified for XID send expiration
(retry). The default is 3.
Characteristic does not apply if
Intranode is yes.
Data Link Simplename Specifies the local entity name for
data link and instance used by the
Transmission Group (TG). In the ex-
ample, qllc link qllc-0 station ncp,
ncp is the name of the local entity
used by the TG.
Node ID 1- to 8-hexa- Specifies the node identifier value
decimal char- for the Peer Server. This value is
acters (pre- used in XID exchange if the value is
ceded by %x) specified. The default is hexadecimal
00000000. Characteristic does not
apply if Intranode is yes.
Required 1- to 8-hexa- Specifies the node identifier value
Adjacent decimal char- of the adjacent node. If specified,
Node ID acters (pre- value must match that of the adjacent
ceded by %x) node. Characteristic does not apply
if Intranode is yes. If you do not
specify this characteristic, no
checking is done by the Peer Server.
Required Simplename Specifies the network id of the
Adjacent adjacent node. If specified, this
Network ID value must match the network ID
supplied by the adjacent node at
connect time or the connection will
fail. The value must be a valid SNA
network name. Characteristic does not
apply if Intranode is yes. If you do
not specify this characteristic, no
checking is done by the Peer Server.
Required Simplename Specifies the cp name of the adjacent
Adjacent node. If specified, the CP Name must
CP name match the name supplied by the
adjacent link station at connect time
or the connection will fail. The
value must be a valid SNA network
name. Characteristic does not apply
if Intranode is yes. If you do not
specify this characteristic, no
checking is done by the Peer
Server.
3.5.2 – delete
delete sna cp services transmission group The delete sna cp services transmission group command deletes the SNA CP Services Transmission Group entity instance. To succeed with the delete command, the entity must be in the Off state. Ex, ncl> delete sna cp services transmission group tg-1
3.5.3 – disable
disable sna cp services transmission group The disable sna cp services transmission group command makes the SNA CP Services Transmission Group unavailable for use by disabling its normal operation. If the disable command is issued with the Immediate argument set to no, the Transmission Group enters the Shut entity state (this is the default action). Similarly, if the disable command is issued without specifying Immediate=Yes, the entity state is then Shut. Current sessions remain unaffected, but new sessions (whether initiated locally or remotely) cannot be established. When the last session ends, the Transmission Group changes from the Connected protocol state to the Idle protocol state, and, finally, to the Reset protocol state (the Idle protocol state status is not displayed). The entity state modulates from Shut to the Off. The Transmission Group then reports the Deactivated event. If the disable command is issued with the Immediate argument set to Yes, all active sessions terminate without regard to their status. The entity state then changes to Off and the protocol state is set to Reset. The Transmission Group then reports the deactivated event. Ex, ncl> disable sna cp services transmission group tg-1
3.5.3.1 – Arguments
Immediate yes | no Determines the performance of the
disable command according to the
following:
If no (the default), the possible
entity states* of the Transmission
Group are
Off The Transmission Group is
disabled and not available
for use.
Shut The Transmission Group is
waiting for all active
sessions to end. This is the
result of issuing the disable
command without immediate
yes.
If yes, all currently active sessions
are aborted. The only possible
resulting entity state* is
Off The Transmission Group is
disabled and not available
for use.
*Refer to the show sna cp services transmission group command Status
Attributes listings for the Protocol States and the entity States
for the Transmission Group.
3.5.4 – enable
enable sna cp services transmission group The enable sna cp services transmission group command makes a Transmission Group available for use, setting the entity state to On and the protocol state to Connecting, unless the Connection Type is Temporary, in which case the protocol state is set to Idle. If the Transmission Group Connection Type is Temporary, the connection is not initiated. However, the Transmission Group can be activated either locally by a session initiation request from the non-SNA network or remotely when the link station is activated from the adjacent node. If the connection type is permanent, the Transmission Group initiates a datalink connection with the adjacent link station. Ex, ncl> enable sna cp services transmission group tg-1
3.5.5 – set
set sna cp services transmission group
The set sna cp services transmission group command lets you set the
characteristics for the SNA CP Services Transmission Group subentity.
You can set the attributes for SNA CP Services Transmission Group only
when the entity is disabled.
Ex, ncl> set sna cp services transmission group tg-1 -
_ncl> connection type = temporary
3.5.5.1 – Characteristics
Intranode yes | no Specifies whether this Transmission
Group is an Intranode Transmission
Group. The default is no. If you
specify yes, note the characteristics
that do to apply.
Connection permanent | Permanent means that the Transmission
Type temporary Group is activated when it is enabled
and remains active until it is
disabled. Temporary means that
the Transmission Group is activated
when a local session is created or
when a remote link station is
activated, and deactivated when there
are no sessions. The default is
permanent.
Dependent yes | no Specifies whether Dependent LUs
LU Support exist for the Transmission Group.
This attribute controls the
acceptance of ACTPU, DACTPU, ACTLU,
and DACTLU RUs as well as the LFSID
address space assignments for the
Transmission Group. The default is
no. Characteristic does not apply if
Intranode is yes.
Segmentation session | Specifies the kind of segmentation to
Support station | be performed by the Peer Server when
none communicating with the adjacent link
station. The default is session.
Characteristic does not apply if
Intranode is yes.
Bind Pacing (1-32767) Specifies the amount that the
Window adaptive BIND pacing algorithm
Increment increases the receiver window size
when a larger window size is
requested by the BIND sender and
when there are adequate
resources. This parameter is valid
when receiver BIND pacing is in
effect for the Transmission Group.
The default is 1. Characteristic
does not apply if Intranode is yes.
Disconnect (0-3600) Specifies the amount of time (in
Timer seconds) a temporary Transmission
Group should delay after zero
sessions are active before
deactivating the link station.
The default is 30.
XID Retry (1-60) Specifies the interval (in seconds)
Timer specified for XID send expiration
(retry). The default is 3.
Characteristic does not apply if
Intranode is yes.
Data Link Simplename Specifies the local entity name for
data link and instance used by the
Transmission Group (TG). In the
example, qllc link qllc-0 station
ncp, ncp is the name of the local
entity used by the TG.
Node ID 1- to 8-hexa- Specifies the node identifier value
decimal char- for the Peer Server. This value is
acters (pre- used in XID exchange if the value is
ceded by %x) specified. Default is hexadecimal
00000000. Characteristic does not
apply if intranode is yes.
Required 1- to 8-hexa- Specifies the node identifier value
Adjacent decimal char- of the adjacent node. If specified,
Node ID acters (pre- this value must match that of the
ceded by %x) adjacent node. Characteristic does
not apply if Intranode is yes. If you
do not specify this characteristic,
no checking is done by the Peer
Server.
Required Simplename Specifies the network id of the
Adjacent adjacent node. If specified, this
Network ID value must match the network ID
supplied by the adjacent node at
connect time or the connection will
fail. The value must be a valid SNA
network name. Characteristic does not
apply if Intranode is yes. If you do
not specify this characteristic, no
checking is done by the Peer Server.
Required Simplename Specifies the cp name of the adjacent
Adjacent node. If specified, the CP Name must
CP name match the name supplied by the
adjacent link station at connect time
or the connection will fail. The
value must be a valid SNA network
name. Characteristic does not apply
if Intranode is yes. If you do not
specify this characteristic, no
checking is done by the Peer
Server.
3.5.6 – show
show sna cp services transmission group
The show sna cp services transmission group command displays the
values of the attributes for the SNA CP Services Transmission Group
entity. The SNA CP Services Transmission Group subentity represents
a link between a Peer Server local link station and an adjacent SNA
system link station. The connection type can be permanent in which
the data link connection remains active when unused, or temporary in
which the connection is automatically terminated when unused.
Ex, ncl> show sna cp services transmission group tg-1 -
_ncl> connection type, node id
3.5.6.1 – Identifier
Name The unique Simplename of the Transmission Group
entity that is maintained by the Peer Server.
3.5.6.2 – Status
UID Displays the unique identifier that the
Peer Server associates with the
Transmission Group.
State Displays the operational state of
the Transmission Group subentity.
Setting the state is a result of
execution of the enable/disable
commands. The states are
Off The Transmission Group is disabled
and not available for use.
On The Transmission Group is enabled
and available for use.
Shut The Transmission Group is waiting
for the end of active sessions, if any.
Protocol Displays the protocol state of the
State Transmission Group. These states are
Connected The Transmission Group is active.
The Transmission Group enters this
state from the connecting state after
successful XID exchange.
Connected The link station is active and the
Pending Transmission Group connection type
Disconnect is temporary. A transition to zero
sessions has started the disconnect timer.
Connected - The link station is active and capable
PU Active of supporting dependent LUs. The
Transmission Group enters this state
from the connected state when an
ACTPU is successfully processed.
Connecting An enabled Transmission Group is
being activated locally by a session
initiation request from a non-SNA
network or remotely when a link
station is activated from an adjacent
node.
Disconnecting The link station is in the process of
deactivating. This is for permanent
Transmission Groups. The entity state
remains on.
Disconnect For temporary Transmission Groups, the
Reset link station is in the process of de-
activating. The entity state is off.
Idle The link station is available but
inactive. This state is entered when
the Transmission Group is enabled. A
temporary Transmission Group is
activated locally by a session
initiation request from a non-SNA network
or remotely when a link station is
activated from an adjacent node.
Reset Resets the link station. This is the
creation state.
INIT_SELF Displays whether the adjacent link
Supported station supports receipt of INIT_SELF.
This attribute is relevant only if the
Transmission Group is active.
BIND Displays, if the Transmission Group is
Supported active, whether the Peer Server can
send Rq (BIND) RUs to the adjacent
link station.
Adjacent Node Displays whether the adjacent node
BIND Assembly can assemble BIND segments.
BIND Pacing Displays, if the Transmission Group is
Support active, the type of BIND pacing that
the Transmission Group supports.
Dependent LU Displays, if the Transmission Group is
BIND Pacing active, whether BIND pacing applies
to dependent LUs.
SSCP Displays whether the adjacent node
Mediated requires ACTPU.
Sessions
Adjacent Displays the node id of the adjacent
Station node. This value is supplied during
Node ID connection.
Adjacent Displays the network id of the
Network ID adjacent node.
Adjacent Displays the non-network qualified
Station name of the CP of the adjacent link
CP Name station.
Adjacent Displays the network name of the PU
Station at the adjacent link station. This
PU Name attribute is either blank or it contains
the non network qualified PU name of
the adjacent link station.
Adjacent Displays the local name of the Adjacent
Station ALS Link Station at the XID sender.
Name
3.5.6.3 – Characteristics
Intranode yes | no Displays whether this Transmission
Group is an Intranode Transmission
Group. The default is no. If you
specify yes, note the characteristics
that do to apply.
Connection permanent | Permanent means that the Transmission
Type temporary Group is activated when it is enabled
and remains active until it is
disabled. Temporary means that the
Transmission Group is activated when
a local session is created or a rem-
ote link station is activated, and
deactivated when there are no
sessions. The default is permanent.
Dependent yes | no Displays whether Dependent LUs
LU Support exist for the Transmission Group.
This attribute controls the
acceptance of ACTPU, DACTPU, ACTLU,
and DACTLU RUs as well as the LFSID
address space assignments for the
Transmission Group. The default is
No. Characteristic does not apply if
Intranode is yes.
Segmentation session | Displays the kind of segmentation to
Support station | be performed by the Peer Server when
none communicating with the adjacent link
station. The default is session.
Characteristic does not apply if
Intranode is yes.
BIND Pacing (1-32767) Displays the amount that the adaptive
Window BIND pacing algorithm increases the
Increment receive window size when a larger
window size is requested by the BIND
sender and when there are adequate
resources. This parameter is valid
when receive BIND pacing is in
effect for the Transmission Group.
The default is 1. Characteristic does
not apply if Intranode is yes.
Disconnect (0-3600) Displays the amount of time (in
Timer seconds) a temporary Transmission
Group should delay after zero
sessions are active before
deactivating the link station.
The default is 30.
XID Retry (1-60) Displays the interval (in seconds)
Timer specified for XID send expiration
(retry). The default is 3.
Characteristic does not apply if
Intranode is yes.
Data Link Simplename Specifies the local entity name for
data link and instance used by the
Transmission Group (TG). In the ex-
ample, qllc link qllc-0 station ncp,
ncp is the name of the local entity
used by the TG.
Node ID 1- to 8-hexa- Displays the node identifier value
decimal char- for the Peer Server. This value is
acters (pre- used in XID exchange if the value is
ceded by %x) specified. The default is hexadecimal
00000000. Characteristic does not
apply if Intranode is yes.
Required 1- to 8-hexa- Displays the node identifier value of
Adjacent decimal char- the adjacent node. If specified, this
Node ID acters (pre- value must match that of the adjacent
ceded by %x) node. Characteristic does not apply
if Intranode is yes.
Required Simplename Displays the network id of the
Adjacent adjacent node. If specified, this
Network ID value must match the network ID
supplied by the adjacent node at
connect time or the connection will
fail. The value must be a valid SNA
network name. Characteristic does not
apply if Intranode is yes.
Required Simplename Displays the CP Name of the adjacent
Adjacent node. If specified, the CP Name must
CP Name match the name supplied by the
adjacent link station at connect time
or the connection will fail. The
value must be a valid SNA network
name. Characteristic does not apply
if Intranode is yes.
3.5.6.4 – Counters
Creation Displays the time that the Transmission
Time Group subentity was created.
Successful Displays the number of Transmission
Activations Group activation procedures that
Transmission Group completed
successfully.
Activation Displays the number of Transmission
Failures Group activation procedures that
failed due to an XID exchange error.
Deactivations Displays the number of times the
Transmission Group has been
deactivated.
Connections Displays the number of times the
Lost Transmission Group reported the
connections lost event.
Octets Sent Displays the number of octets that the
Transmission Group sent.
Octets Displays the number of octets that the
Received Transmission Group received.
BTUs Sent Displays the number of BTUs that the
Transmission Group sent.
BTUs Displays the number of BTUs that the
Received Transmission Group received.
COLD ACTPUs Displays the number of COLD ACTPUs
Received that the Transmission Group received.
ERP ACTPUs Displays the number of ERP ACTPUs
Received that the Transmission Group received.
ACTPUs Displays the number of negative
Rejected responses sent to ACTPU requests.
DACTPUs Displays the number of DACTPUs
Received that the Transmission Group received.
Protocol Displays the number of SNA protocol
Violations violations that the Transmission
Group detected.
4 – LLC2
The LLC2 entity represents the LLC2 protocol on the Peer Server and its accessibility by client applications. The LLC2 module controls the operation of the LLC Type 2 data link protocol for local area networks (LANs). The Peer Server supports a single instance of the LLC2 entity. The subordinate entities of the LLC2 entity are the Port and the SAP (service access point). The Port subentity exists when an LLC2 connection is established to an adjacent link station. Ports are dynamically created and deleted as connections are made and broken. An instance of the SAP subentity must exist for each LLC2 port. The SAP subentity is the access point to the underlying LAN station. There is one SAP for each protocol on the LAN adapter. The SAP entity has the Link subentity, which represents a remote LAN station and its associated SAP.
4.1 – create
create llc2 The create llc2 command creates an LLC2 entity, which provides support for LLC Type 2 data link protocol for local area networks. There is only one instance for each node. Ex, ncl> create llc2
4.2 – delete
delete llc2 The delete llc2 command deletes the single LLC2 entity. You cannot delete the entity while subentities (Ports and SAPs) exist. Ex, ncl> delete llc2
4.3 – show
show llc2 The show llc2 command displays the attributes of the LLC2 entity. Ex, ncl> show llc2 all
4.3.1 – Characteristic
version Displays the version number of the SNA LLC2
software that is executing.
4.4 – SAP subentity
An instance of the SAP subentity must exist for each LLC2 port. The SAP (service access point) subentity is the access point to the underlying LAN station. There is one SAP for each protocol on the LAN adapter.
4.4.1 – create
create llc2 sap The create llc2 sap command creates an instance of the LLC2 SAP subentity for each protocol that LLC2 uses. The create command also allocates resources for the subentity and sets its characteristics to their default values. Ex, ncl> create llc2 sap sna-0
4.4.2 – delete
delete llc2 sap The delete llc2 sap command deletes a named LLC2 SAP instance. You can delete a SAP instance only when it has no active Link subentities and it is disabled. Ex, ncl> delete llc2 sap sna-0
4.4.3 – disable
disable llc2 sap The disable llc2 sap command disables a named LLC2 SAP instance. Ex, ncl> disable llc2 sap sna-0
4.4.4 – enable
enable llc2 sap The enable llc2 sap command enables a named LLC2 SAP instance. Ex, ncl> enable llc2 sap sna-0
4.4.5 – set
set llc2 sap The set llc2 sap command lets you set the attributes for the LLC2 SAP subentity. Ex, ncl> set llc2 sap sna-0 lan station token ring station trn-0
4.4.5.1 – Characteristics
LAN Station Local entity Specifies the name of the LAN station
entity used by the name SAP. You must
specify this value before trying to
enable the SAP.
Local LSAP 2 characters Specifies the local link service
Address (hexadecimal) access point (LSAP) to be
used. The address must be unique.
For use with the Peer Server, this
value is normally set to 04.
4.4.6 – show
show llc2 sap The show llc2 sap command displays the attributes for the LLC2 SAP subentity. Ex, ncl> show llc2 sap sna-0 all
4.4.6.1 – Identifier
Name Displays the simplename assigned when the LLC2 SAP was
created.
4.4.6.2 – Status
State Displays the entity state of the LLC2 SAP entity.
Possible values are:
off The SAP is disabled.
on The SAP is enabled.
LAN Port Displays the name of the LAN Port that is
opened and enabled when this SAP is successfully
enabled. The status has a null value if the SAP
is not enabled.
Maximum PDU Displays the largest frame size, in octets, that
Size can be used to send or receive data on this SAP.
UID Displays the entity's unique identifier that was
assigned when the entity was created.
4.4.6.3 – Characteristics
LAN Station Local entity Displays the name of the LAN station
entity used by the name SAP. You must
specify this value before trying to
enable the SAP.
Local LSAP 2 characters Displays the local link service
Address (hexadecimal) access point (LSAP) to be used.
4.4.6.4 – Counters
Creation Displays the time that the entity was created. Time Times SAP Displays the number of times the SAP state has State Changed changed from on to off, or from off to on.
4.5 – SAP Link subentity
The Link subentity of the SAP represents a remote LAN station and its associated SAP.
4.5.1 – create
create llc2 sap link The create llc2 sap link command creates a link to a remote LAN station that operates over a particular service access point (SAP). Ex, ncl> create llc2 sap sna-0 link link-2
4.5.2 – delete
delete llc2 sap link The delete llc2 sap link command deletes a named LLC2 SAP Link instance. You can delete a SAP Link instance only when it is disabled and the transmission group that uses it is disabled. Ex, ncl> delete llc2 sap sna-0 link link-2
4.5.3 – disable
disable llc2 sap link The disable llc2 sap link command disables a named LLC2 SAP Link instance. Ex, ncl> disable llc2 sap sna-0 link link-2
4.5.4 – enable
enable llc2 sap link The enable llc2 sap link command makes a named LLC2 SAP Link instance available for connections. Ex, ncl> enable llc2 sap sna-0 link link-2
4.5.5 – set
set llc2 sap link The set llc2 sap link command lets you set the attributes for the LLC2 SAP Link subentity. Ex, ncl> set llc2 sap sna-0 link link-2 acknowledge timer = 2000
4.5.5.1 – Characteristics
Acknowledge (1-60000) Specifies the time (in milliseconds)
Timer that the link waits for an
acknowledgment before initiating
recovery action. The default is 1000.
Holdback Timer (0-60000) Specifies the delay (in milliseconds)
before an acknowldgment must be sent.
The default is 500.
Maximum (1-65531) Specifies the largest frame size (in
Data Size octets) that the link can use to send
or receive data. This value does not
include the size of the frame header.
The default is 1028.
Local Receive (1-127) Specifies the size of the window used
Window Size by the link for receiving frames. The
default is 127.
Retry Maximum (1-255) Specifies the maximum number of times
that the link retransmits a frame
before assuming a fatal error and
taking more drastic recovery action.
The default is 10.
Remote Mac LAN Specifies the unique destination MAC
Address address address to be used by the link. The
default is 00-00-00-00-00-00.
Remote LSAP 2 character Specifies the unique address of the
Address (hexa- destination LSAP (local service
decimal) access point) to be used by the link.
For use with the Peer Server, this
value is normally set to 04.
4.5.6 – show
show llc2 sap link The show llc2 sap link command displays the attributes for a link that operates over a particular service access point (SAP). Ex, ncl> show llc2 sap sna-0 link link-2 all
4.5.6.1 – Identifier
Name Displays the Simplename assigned to the link when it
was created.
4.5.6.2 – Status
Active Maximum Displays the negotiated maximum frame size
Data Size (excluding the header) that can be sent and
received on this link. The value is the
smallest maximum data size of the Link, the
SAP, and the adjacent link.
State Displays the entity state of the llc2 link.
Possible values are:
off The link is disabled.
on The link is enabled.
Protocol Displays the state of the LLC2 protocol with
State respect to the remote station. Possible
states are:
error The protocol is in a recognized error state.
disconnecting The protocol is being disconnected.
halted The protocol has halted.
initializing The protocol is being initialized.
inoperative The protocol cannot be started because the LAN
station cannot provide a connection to a remote
station.
resetting The protocol is being reset.
running The protocol is running normally.
Remote LLC Class Displays the class of the remote LLC.
Possible classes are:
1 Class 1 LLC. Only type 1 operation is
supported.
2 Class 2 LLC. Both type 1 and type 2
operations are supported.
unknown The class has not yet been established. The
class is established during XID exchange
between the local and remote LLC
implementations.
Remote Receive Displays the window size used by the remote
Window Size station for receiving frames. The local
station uses this value as its window for
transmitting frames.
UID Displays the unique identifier of the entity,
which is generated when the entity is created.
4.5.6.3 – Characteristics
Acknowledge (1-60000) Displays the time (in milliseconds)
Timer that the link waits for an
acknowledgment before initiating
recovery action.
Holdback Timer (0-60000) Displays the delay (in milliseconds)
before an acknowledgment must be sent.
Maximum (1-65531) Displays the largest frame size (in
Data Size octets) that the link can use to send
or receive data. This value does not
include the size of the frame header.
Local Receive (1-127) Displays the size of the window used
Window Size by the link for receiving frames.
Retry Maximum (1-255) Displays the maximum number of times
that the link retransmits a frame
before assuming a fatal error and
taking more drastic recovery action.
Remote MAC LAN Displays the unique destination MAC
Address address address to be used by the link.
Remote LSAP 2 characters Displays the unique address of the
Address (hexa- destination LSAP (local service
decimal) access point) to be used by the link.
4.5.6.4 – Counters
Data Octets Displays the number of data octets received in
Received I-frames and UI-frames from the remote end of the
link. This value does not include retransmissions.
Data Octets Displays the number of data octets sent in
Sent I-frames and UI-frames to the remote end of the
link. This value does not include retransmissions.
Data PDUs Displays the number of I-frames and UI-frames
Received received from the remote end of the link. This
value does not include retransmissions.
Data PDUs Displays the number of I-frames and UI-frames sent
Sent to the remote end of the link. This value does
not include retransmissions.
REJs Received Displays the number of REJ (reject) frames
received.
REJs Sent Displays the number of REJ (reject) frames
transmitted.
RNRs Received Displays the number of RNR (receive not ready)
frames received.
RNRs Sent Displays the number of RNR (receive not ready)
frames transmitted.
XIDs Received Displays the number of XID frames received.
XIDs Sent Displays the nubmer of XID framed transmitted.
FRMRs Received Displays the number of FRMR (frame reject) frames
received.
FRMRs Sent Displays the number of FRMR (frame reject) frames
generated as a result of invalid incoming frames.
Polls Received Displays the number of command frames received
with the P-bit set.
Times Acknowledge Displays the number of times the local acknowledge
Timer Expired timer has expired.
Times Poll Displays the number of times the local poll timer
Timer Expired has expired.
Times Reject Displays the number of times the local reject
Timer Expired timer has expired.
Times Busy Displays the number of times the local busy timer
Timer Expired has expired.
Times Link Displays the number of times the link's state
State Changed changed from on to off, or from off to on.
Times Link Displays the number of times the link's protocol
Running state status attribute was set to running. When
the link enters the running state, the protocol
has been successfully initialized or reset.
Times Link Displays the number of times the link's protocol
Initializing state status attribute was set to initializing.
Times Link Displays the number of times the link's protocol
Resetting state status attribute was set to resetting.
Times Link Displays the number of times the link's protocol
Halted state status attribute was set to halted.
Times Link Displays the number of times the link's protocol
Inoperative state status attribute was set to inoperative.
Times Link Displays the number of times the LLC2 fails to
Setup Failed initialize correctly after the maximum number of
retries.
Creation Time Displays the time at which the entity was created.
4.6 – Port subentity
The Port subentity exists when an LLC2 connection is established to an adjacent link station. Ports are dynamically created and deleted as connections are made and broken.
4.6.1 – show
show llc2 port The show llc2 port command displays the attributes of the LLC2 Port entity. Ex, ncl> show llc2 port llc2-port-000 all
4.6.1.1 – Identifier
name A unique value assigned to the Port by the LLC2
entity. The value is in the form LLC2-port-nnn,
where nnn is an unsigned integer.
4.6.1.2 – Status
Client Displays the name of the client that opened the
port.
Link Displays the name of the SAP Link entity
associated with this port.
State Displays the entity state of the port. Possible
state values are:
open The port is assigned to a client and is enabled.
open disabled The port is assigned to a client but is disabled.
5 – QLLC
The QLLC entity represents the QLLC protocol on the Peer Server and its accessibility by client applications. The Peer Server supports a single instance of QLLC. The subordinate entities of the QLLC entity are the Port and the Link. Ports exists when a QLLC connection is established to an adjacent link station. Ports are dynamically created and deleted as client connections are made and broken. A Link must exist for each X.25 communication line. The Link defines the local link station to the Peer Server and contains the management attributes for the operation of all supported station components. It also contains information that permits the identification of the associated X.25 server component. The Link entity has the Station subentity that represents the remote DTE (Data Terminal Equipment address) of a station that operates over a particular X.25 logical link.
5.1 – create
create qllc The create qllc command creates a QLLC entity, which provides support for communication over X.25 networks. There is only one instance for each node. There is one QLLC Link for each local X.25 DTE address (only one link can exist on the Peer Server). For each remote X.25 DTE address that can be reached using a QLLC link, QLLC uses a subordinate Station entity. For each QLLC connection between a QLLC link and a QLLC station, QLLC creates a dynamic PORT entity to represent the connection to the network. Ex, ncl> create qllc
5.2 – delete
delete qllc The delete qllc command deletes the single QLLC instance. You cannot delete the QLLC entity while subentities (Links and Ports) exist. Ex, ncl> delete qllc
5.3 – show
show qllc The show qllc command displays the attributes for the qllc entity. Ex, ncl> show qllc all counters
5.3.1 – Status
UID Displays the entity's unique identifier, which is
generated when the Peer Server creates the entity.
Connections Displays the number of connections that are
currently active.
5.3.2 – Characteristic
Version Displays the version number of the SNA QLLC
software that is executing.
5.3.3 – Counters
Resource Allocation The total number of resource allocation Failures failures; for example, insufficient memory. Creation Time The time that the QLLC entity was created.
5.4 – Link subentity
The Link subentity defines the local link station to the Peer Server and contains the management attributes for the operation of all supported station components. It also contains information that permits the identification of the associated X.25 server component. An instance of this subentity must exist for each X.25 communication line.
5.4.1 – create
create qllc link The create qllc link command creates an instance of the QLLC Link subentity for each local X.25 DTE address. The Link subentity is the access point into the X.25 protocol for QLLC connections to remote system. The create command also allocates resources for the subentity and sets its characteristics to their default values. Ex, ncl> create qllc link qllc-0 dte address = 12345678901
5.4.1.1 – Characteristics
Subsequent 1-8 characters Specifies an octet string that is
Protocol (hexadecimal) used to filter incoming X.25 calls
Identifier for a specific protocol. This value
corresponds to the Data Call value
in the X.25 configuration.
It is only needed to handle incoming
connections. The default value is
hexadecimal C3 (QLLC Protocol).
Filter Name Simplename Specifies the name of the Filter to
be used for incoming QLLC (X.25)
connections. This name must be
specified for links that will use
both incoming or outgoing connec-
tions. The name must also match
an X25 Access Filter that exists in
the node's X.25 configuration. The
default is filter_qllc.
Template Name Simplename Specifies the name of the Template
to be used for creating an outbound
QLLC connection. This name must
match an X25 Access Template in the
node's X.25 configuration. The
default is template_qllc.
DTE Class Simplename Specifies the name of the DTE class
to be used for creating an outbound
connection. This name must match an
X25 Access DTE Class names that
exists in the local node's X.25
configuration. The default is
class_qllc.
5.4.2 – delete
delete qllc link The delete qllc link command deletes an instance of the QLLC Link subentity and deallocates resources for the subentity. The Link subentity must be in the off state and must have no Station subentities. Ex, ncl> delete qllc link qllc-0
5.4.3 – disable
disable qllc link The disable qllc link disables an instance of the QLLC Link subentity. You can only disable a previously enabled entity. The disable command stops the operation of the Link subentity. For the disable command to be successful, all Station subentities on the Link must have been disabled. At the completion of the command the subentity is in the off entity state. Ex, ncl> disable qllc link qllc-0
5.4.4 – enable
enable qllc link The enable qllc link command places the QLLC Link subentity in its enabled state (on). Ex, ncl> enable qllc link qllc-0
5.4.5 – set
set qllc link The set qllc link command lets you set the attributes of the QLLC Link subentity. The QLLC Link subentity defines the data link attributes that are shared by its Station subentities. Ex, ncl> set qllc link qllc-0 dte address = 12345678901
5.4.5.1 – Characteristics
Subsequent 1-8 characters Specifies an octet string that is used
Protocol (hexadecimal) to filter incoming X.25 calls for a
Identifier specific protocol. This value corres-
ponds to the Call Data value in the
X.25 configuration. It is only needed
to handle incoming connections. The
default value is hexadecimal C3 (QLLC
Protocol).
Filter Name Simplename Specifies the name of the Filter to be
used for incoming QLLC (X.25) connec-
tions. This name must be specified for
links that will use both incoming or
outgoing connections. The name must
also match an X25 Access Filter that
exists in the node's X.25
configuration. The default
is filter_qllc.
Template Simplename Specifies the name of the Template to
Name be used for creating an outbound QLLC
connection.This name must match an X25
Access Template in the node's X.25
configuration. The default is
template_qllc.
DTE Class Simplename Specifies the name of the DTE class to
be used for creating an outbound
connection. This name must match an
X25 Access DTE Class names that exists
in the local node's X.25 configuration.
The default is class_qllc.
5.4.6 – show
show qllc link The show qllc link command displays the attributes for the QLLC Link subentity. The QLLC Link subentity defines the data link attributes that are shared by its Station subentities. Ex, ncl> show qllc link qllc-0 all status
5.4.6.1 – Identifier
Name Displays the name of the Link.
5.4.6.2 – Status
UID Displays the entity's unique identifier, which is
generated when the Peer Server creates the entity.
State Displays the operational state of this QLLC Link
subentity.
inoperable The Link cannot be enabled.
off You have issued a disable command for this Link.
The Link is in the Inactive or Pending Inactive
state.
on You have issued an enable command for this Link.
5.4.6.3 – Characteristics
Subsequent 1-8 characters Displays an octet string that is used
Protocol (hexadecimal) to filter incoming X.25 calls for a
Identifier specific protocol. This value corres-
ponds to the Call Data value in the
X.25 configuration. It is only needed
to handle incoming connections.
Filter Simplename Displays the name of the Filter to be
Name used for incoming QLLC (X.25) connec-
tions. This name must be specified
for links that will use both incoming
or outgoing connections. The name
must also match an X25 Access Filter
that exists in the node's
X.25 configuration.
Template Simplename Displays the name of the Template to
Name be used for creating an outbound QLLC
connection.This name must match an X25
Access Template in the node's X.25
configuration.
DTE Class Simplename Displays the name of the DTE class to
be used for creating an outbound
connection. This name must match an
X25 Access DTE Class names that exists
in the local node's X.25 configuration.
5.4.6.4 – Counters
Creation Time Displays the time that the QLLC Link subentity
was created.
5.5 – Link Station subentity
The QLLC Link Station subentity represents the remote DTE (Data Terminal Equipment address) of a station that operates over a particular X.25 logical link.
5.5.1 – create
create qllc link station The create qllc link station command creates an instance of the Station subentity of a QLLC Link entity for each remote DTE address and allocates resources for the subentity. There is a station subentity for each remote DTE (data terminal equipment) address with which a virtual circuit can be associated. The create command sets the characteristic attributes to their default values. Ex, ncl> create qllc link qllc-0 station stn-0
5.5.1.1 – Characteristics
Usage Type outgoing | Specifies the type of connections that
incoming | can run over this station. If set to
both incoming, then only IBM initiated X.25
connections are allowed. If set to
outgoing, then the Peer Server will
initiate connections. If set to both
both either end can initiate
connections. The default is outgoing.
Retry (0-255) Specifies the maximum number of times
Maximum to retry when an error occurs. The
default is 4.
Retry (1-600) Specifies the time in seconds to wait
Timeout between retries. The default is 10.
Contact yes | no Specifies whether the secondary
Terminal station awaits receipt of a QRR command
or of the first data frame before
establishment of the link connection is
acknowledged. The default is no.
Capability primary | Specifies the capability of the
secondary| Station subentities of this
negotiable Link entity. Negotiable stations can
become either primary or secondary.
The default is negotiable.
Call User 2 characters Specifies the hexadecimal string that
Data (hexadecimal) identifies the type of X.25 to be made
to create a QLLC connection. The
default value is hexadecimal C3 (QLLC
protocol).
Remote DTE DTEaddress Specifies the X.25 DTE address of the
Address remote station. If the Peer Server
initiates the connection, this is the
address that will be called. For an IBM
initiated connection, if the Usage Type
parameter is set to Incoming, this
address will be matched against the
caller's address and if not matched,
the call will be rejected.
Maximum BTU (128-4095) Specifies the size that SNA messages
Size will be segmented into before being
sent to the X.25 network. (The X.25
network may further segment packets
based on the level 2 profile
information being used.)
The default is 512.
5.5.2 – delete
delete qllc link station The delete qllc link station command deletes the Station subentity. The Station subentity must be in the off state before it can be deleted Ex, ncl> delete qllc link qllc-0 station stn-0
5.5.3 – disable
disable qllc link station The disable qllc link station command stops the operation of the Station subentity of the Link. If a connection exists, the disable command halts protocol operation. When execution of the command completes, the Station entity enters the off entity state. Ex, ncl> disable qllc link qllc-0 station stn-0
5.5.4 – enable
enable qllc link station The enable qllc link station command enables the Station for use. An enabled Station can accept incoming connection requests or initiate outgoing connection requests. The Link entity must be enabled before you issue this command. An association may be made between the station subentity and the X.25 service provider by selecting an X.25 logical channel on which the QLLC protocol operates. Ex, ncl> enable qllc link qllc-0 station stn-0
5.5.5 – set
set qllc link station The set qllc link station command let you set the attributes for QLLC Link Station subentity. The QLLC Station subentity contains the data link attributes that are configured for this connection. Ex, ncl> set qllc link qllc-0 station stn-0 capability = primary
5.5.5.1 – Characteristics
Usage Type outgoing | Specifies the type of connections that
incoming | can run over this station. If set to
both incoming, then only IBM initiated X.25
connections are allowed. If set to
outgoing, then the Peer Server will
initiate connections. If set to both
then either end can initiate connec-
tions. The default is outgoing.
Retry (0-255) Specifies the maximum number of times
Maximum to retry when an error occurs. The
default is 4.
Retry (1-600) Specifies the time in seconds to wait
Timeout between retries. The default is 10.
Contact yes | no Specifies whether the secondary
Terminal station awaits receipt of a QRR command
or of the first data frame before
establishment of the link connection is
acknowledged. The default is no.
Capability primary | Specifies the capability of the
secondary| Station subentities of this
negotiable Link entity. Negotiable stations can
become either primary or secondary.
The default is negotiable.
Call User 2 chars Specifies the hexadecimal string that
Data (hexa- identifies the type of X.25 to be made
decimal) to create a QLLC connection. The
default value is hexadecimal C3 (QLLC
protocol).
Remote DTEaddress Specifies the X.25 DTE address of the
DTE Address remote station. If the Peer Server
initiates the connection, this is the
address that will be called. For an
IBM initiated connection, if
the Usage Type parameter is set to
Incoming, this address will be matched
against the caller's address and if not
matched, the call will be rejected.
Maximum BTU (128-4095) Specifies the size that SNA messages
Size will be segmented into before being
sent to the X.25 network. (The X.25
network may further segment packets
based on the level 2 profile
information being used.)
The default is 512.
5.5.6 – show
show qllc link station The show qllc link station displays the attributes of the QLLC Link Station subentity. The QLLC Station subentity contains the data link attributes that are configured for this connection. Ex, ncl> show qllc link qllc-0 station stn-0 maximum btu size
5.5.6.1 – Identifier
Name Displays the name of the Station.
5.5.6.2 – Status
UID Displays the UID that is associated with the
station.
Client Displays the name of the user of this station,
an instance of the SNA CP Services Transmission
Group entity.
XPI State Displays the internal state of the XPI interface
(the service interface to X.25) that QLLC uses.
State Displays the operational state of the link
station. Possible values are:
off The station has been disabled.
on The station has been enabled.
5.5.6.3 – Characteristics
Usage Type outgoing | Displays the type of connections that
incoming | can run over this station. If set to
both incoming, then only IBM initiated X.25
connections are allowed. If set to
outgoing, then the Peer Server will
initiate connections. If set to both
then either end can initiate
connections.
Retry Maximum (0-255) Displays the maximum number of times
to retry when an error occurs.
Retry Timeout (1-600) Displays the time in seconds to wait
between retries.
Contact yes | no Displays whether the secondary station
Terminal awaits receipt of a QRR command or of
the first data frame before establish-
ment of the link connection is
acknowledged.
Capability primary | Displays the capability of the Station
secondary| subentities of this Link entity.
negotiable Negotiable stations can become either
primary or secondary.
Call User Data 2 chars Displays the hexadecimal string that
(hexa- identifies the type of X.25 to be made
decimal) to create a QLLC connection.
Remote DTE DTEaddress Displays the X.25 DTE address of the
Address remote station. If the Peer Server
initiates the connection, this is the
address that will be called. For an IBM
initiated connection, if the Usage Type
parameter is set to Incoming, this
address will be matched against the
caller's address and if not matched,
the call will be rejected.
Maximum BTU (128-4095) Displays the size that SNA messages
Size will be segmented into before being
sent to the X.25 network. (The X.25
network may further segment packets
based on the level 2 profile
information being used.)
5.5.6.4 – Counters
Octets Sent Displays the total number of octets in all
information packets sent by this station.
Octets Received Displays the total number of octets in all
information packets received by this station.
Data PDUs Sent Displays the total number of information
packets sent to this station.
Data PDUs Received Displays the total number of information
packets received by this station.
QXID Frames Sent Displays the total number of QXID messages
sent by this station.
QXID Frames Received Displays the total number of QXID messages
received by this station.
QTEST Frames Sent Displays the total number of QTEST messages
sent by this station.
QTEST Frames Displays the total number of QTEST messages
Received received by this station.
Outgoing Calls Displays the total number of outgoing call
Accepted made by this station.
Incoming Calls Displays the total number of incoming calls
Accepted received and accepted by this station.
Clears Received Displays the total number of clears received
by this station.
Retry Exceeded Displays the total number of unsuccessful
outgoing calls.
Protocol Error Displays the total number of QLLC protocol
errors detected on this station.
Local Error Displays the total number of times that the
client has not reacted according to the QLLC
protocol.
Receive Over Size Displays the total number of oversized frames
received.
QFRMR Frames Displays the total number of times a
Received frame-reject type frame was received.
QFRMR Frames Sent Displays the total number of times a
frame-reject type frame was sent.
XPI Error Displays the number of X.25 interface
Indication errors reported.
Creation Time Displays the time at which the entity was
created.
5.6 – Port subentity
show qllc port The show qllc port command displays the attributes for the QLLC Port subentity. A Port subentity is created dynamically for each connection to a remote station. Each Port is created when a connection is established and deleted when the connection is terminated. To show all the existing ports issue the show qllc port * command. Ex, ncl> show qllc port 1 all counters
5.6.1 – Identifier
Name A unique value assigned to the Port by the QLLC
entity.
5.6.2 – Status
UID Displays the entity's unique identifier, which is
generated when the Peer Server creates the entity.
Station Displays the name of the QLLC Link Station subentity
that the client specified in the connection request.
Client Displays the name of the user of this station, an
instance of the SNA CP Services Transmission Group
entity.
Protocol Displays the currently defined state of the QLLC
State entity. The possible state values are:
outgoing call An X.25 outgoing call is being made on this port.
inoperable The initial state for a QLLC link connection.
closed An X.25 connection is established, but a QLLC link
connection has not yet taken place. The XID
negotiation is executed in this state.
opening The QLLC link connection is being established. If
negotiation is enabled, the role must change to
primary or secondary within this state.
opened The normal operation state. Data link PDUs are
exchanged in both directions across the X.25 logical
channel connection.
closing The QLLC link is in the process of closing.
recovery A secondary station may enter this state to recover
after a QLLC protocol error was detected.
Predicate Displays a substate of the current protocol state.
For more information, please refer to the IBM
documentation.
Role Displays whether the Peer Server is primary or secondary
in the QLLC connection that this Port represents.
Maximum Displays the size that SNA messages will be segmented
BTU Size into before being sent to the X.25 network. (The X.25
network may further segment packets based on the
level 2 profile information being used.)
Remote Displays the X.121 coded DTE address of the remote
DTE Address station to which this port is connected.
5.6.3 – Counters
Octets Displays the total number of octets in all information
Sent packets sent in on QLLC connection represented by
this port.
Octets Displays the total number of octets in all information
Received packets received in on QLLC connection represented by
this port.
Data PDUs Displays the total number of data packets sent on the
Sent QLLC connection.
Data PDUs Displays the total number of data packets received on
Received the QLLC connection.
Creation Displays the time that the QLLC Port subentity was
Time created.
6 – SDLC
The SDLC entity provides support for communication links. There is only one instance per node. For each physical line, SDLC creates a Link subentity, which manages all stations on the line. For each logical station, SDLC creates a Station subentity that is subordinate to the Link entity, which manages the station. For each enabled Station that establishes a connection, SDLC creates a Port entity.
6.1 – create
create sdlc The create verb generates a new instance of the SDLC entity or subentity. Create sets the entity state to off and sets the entity's attributes to their default values. There are no attributes for the create sdlc command. Ex, ncl> create sdlc
6.2 – delete
delete sdlc The delete sdlc command deletes the single SDLC instance. You cannot delete the SDLC entity while subentities (Links, Stations) exist. Ex, ncl> delete sdlc
6.3 – show
show sdlc The show sdlc command displays the attributes for communication lines or links. There is only one instance per node. Ex, ncl> show sdlc all counters
6.3.1 – Status
UID Displays the entity's unique identifier, which
is generated when the Peer Server creates the
entity.
Connections Displays the number of connections that are
currently active.
6.3.2 – Characteristics
Version Displays the version number of the SDLC software
that is executing.
6.3.3 – Counters
Creation The time that the SDLC entity was created. Time Resource The total number of resource allocation failures; Allocation for example, insufficient memory. Failures
6.4 – Link subentity
The SDLC Link subentity instance exists for each physical line and manages all stations on the line.
6.4.1 – create
create sdlc link
The create sdlc link command creates an instance of the SDLC Link
subentity for each physical line, which manages all stations on the
line. Creation also allocates resources for the subentity, and set
its characteristics to their default values.
Ex, ncl> create sdlc link sdlc-1 line modem connect line line-0, -
_ncl> capability primary
6.4.1.1 – Characteristics
Line local entity Specifies the Modem Connect Line on
name which the SDLC protocol operates.
For more information about Modem
Connect Line refer to the
DECnet-Plus Network Control
Language Reference.
Capability primary | Specifies the capability of the
secondary | Station subentities of this Link
negotiable entity. Negotiable stations can
become either primary or secondary.
The default is negotiable.
Configuration pointtopoint | Specifies whether the Link supports
multipoint only a point-to-point connection or
can also support a multipoint
connection. Multipoint supports one
or more than one connection. The
default is pointtopoint. The Peer
Server does not support multipoint
primary connections.
Connection nonswitched | Specifies whether the Link supports
Type switched switched or nonswitched connections.
The default is nonswitched.
Receive (1-32764) Specifies the maximum frame size
Frame Size (excluding the header) that can be
received on the line represented by
this Link. The default is 1000.
Reply Timer (100-60000) Specifies the time (in milliseconds)
to wait for an acknowledgment before
starting the recovery procedure. The
default is 3000.
Retry (0-128) Specifies that, when the Link is
Maximum secondary, this is the maximum
number of times a frame is
retransmitted before assuming a
fatal error. When the Link is
primary, this is the number of times
that a retry will be attempted. The
default is 15.
Poll Pause (0-60000) The time in milliseconds to pause
when the end of the polling list is
reached. Used only when the Link is
primary. The default is 200.
Service (1-255) Specifies the maximum number of
Limit regular scans of the service order
table for secondary Stations that
will be made before a special scan
is made. Used when the Link is
multipoint primary. The default is
4. Not used at this time.
TWA Send no | yes Specifies whether the Link provides
Priority priority for outbound services when
configured for Two-Way Alternating
(half-duplex) data transfer in the
multipoint primary mode. Yes
means that PIUs that arrive for
transmission while data is being re-
ceived are transmitted immediately.
No, the default, means that outbound
transmission is strictly determined
by the position of station service
order entries in the Service Order
Table. This attribute is not
relevant to SDLC point-to-point
operations. Not used at this time.
6.4.2 – delete
delete sdlc link The delete sdlc link command deletes an instance of the SDLC Link subentity and deallocates resources for the subentity. The Link subentity must be in the off state and must have no Station subentities. Ex, ncl> delete sdlc link sdlc-0
6.4.3 – disable
disable sdlc link The disable sdlc link command disables an instance of the SDLC Link subentity. You can only disable a previously enabled entity. The disable command stops the operation of the Link subentity. To be successful with this command, all Station subentities on the Link must have been disabled. At the completion of the command the subentity is off. Ex, ncl> disable sdlc link sdlc-0
6.4.4 – enable
enable sdlc link The enable sdlc link command places the SDLC Link subentity in its enabled state (on). An association may be made between the Link subentity and the Modem Connect Line entity of the physical line on which the protocol operates. For more information about Modem Connect Line refer to the DECnet-Plus Network Control Language Reference. Ex, ncl> enable sdlc link sdlc-0
6.4.5 – set
set sdlc link The set sdlc link command let you set the attributes for the SDLC Link subentity. The SDLC Link subentity defines the data link attributes that are shared by its Station subentities. Ex, ncl> set sdlc link sdlc-0 capability = primary
6.4.5.1 – Characteristics
Line local entity Specifies the Modem Connect Line on
name which the SDLC protocol operates.
This attribute is settable only
when the Link is disabled. For
more information about Modem
Connect Line refer to the
DECnet-Plus Network Control Language
Reference.
Capability primary | Specifies the capability of the
secondary | Station subentities of this Link
negotiable entity. Negotiable stations can
become either primary or secondary.
This attribute is settable only when
the Link is disabled. The default is
negotiable.
Configuration pointtopoint | Specifies whether the Link supports
multipoint only a point-to-point connection or
can also support a multipoint
connection. Multipoint supports one
or more than one connection. This
attribute is settable only when the
Link is disabled. The default is
pointtopoint. The Peer Server does
not support multipoint primary
connections.
Connection nonswitched | Specifies whether the Link supports
Type switched switched or nonswitched connections.
This attribute is settable only when
the Link is disabled. The default is
nonswitched.
Receive (1-32764) Specifies the maximum frame size
Frame (excluding the header) that can be
Size received on the line represented by
this Link. This attribute is settable
only when the Link is disabled. The
default is 1000.
Reply Timer (100-60000) Specifies the time (in milliseconds)
to wait for an acknowledgment before
starting the recovery procedure. The
default is 3000.
Retry (0-128) Specifies that, when the Link is
Maximum secondary, this is the maximum
number of times a frame is
retransmitted before assuming a
fatal error. When the Link is
primary, this is the number of times
that a retry will be tried. This
attribute is settable only when the
Link is disabled. The default is 15.
Poll Pause (0-60000) The time in milliseconds to pause
when the end of the polling list is
reached. Used only when the Link is
primary. The default is 200.
Service (1-255) Specifies the maximum number of
Limit regular scans of the Service Order
Table for secondary Stations that
will be made before a special scan
is made. Used when the Link is
primary. Is settable only when the
Link is disabled. The default is 4.
Not used at this time.
TWA Send no | yes Specifies whether the Link provides
Priority priority for outbound services when
configured for Two-Way Alternating
(half-duplex) data transfer in the
multipoint primary mode. Yes
means that PIUs that arrive for
transmission while data is being
received are transmitted immediately.
No, the default, means that outbound
transmission is strictly determined
by the position of station service
order entries in the service order
table.
This attribute is not relevant to
SDLC point-to-point operations. This
attribute is settable only when the
Link is disabled. Not used at this
time.
6.4.6 – show
show sdlc link The show sdlc link command displays the values of the attributes for the SDLC Link subentity. The SDLC Link subentity defines the data link attributes that are shared by its Station subentities. Ex, ncl> show sdlc link sdlc-0 all status
6.4.6.1 – Identifier
Name A Simplename that is unique among the SDLC Link
entities maintained by the SDLC module. The network
manager specifies Name when the Link is created.
6.4.6.2 – Status
UID Displays the entity's unique identifier, which is
generated when the the entity is created.
State Displays the operational state of this SDLC Link
subentity. Possible states are
Inoperable The Link cannot be enabled.
Off You have issued a disable command for
this Link. The Link is in the
inactive or pending inactive state.
On You have issued an enable command for
this Link.
Role Displays the role this Link has taken. Values for
Role are:
Idle No role has been assumed yet.
Primary The role is that of a primary Link.
Secondary The role is that of a secondary Link.
6.4.6.3 – Characteristics
Line local entity Displays the Modem Connect Line on
name which the SDLC protocol operates.
You must specify a value in
order to enable the link. For more
information about Modem Connect
Line refer to the DECnet-Plus
Network Control Language Reference.
Capability primary | Displays the capability of the
secondary | Station subentities of this Link
negotiable entity. Negotiable stations can
become either primary or secondary.
The default is negotiable.
Configuration pointtopoint | Displays whether the Link supports
multipoint only a point-to-point connection or
can also support a multipoint
connection. Multipoint supports one
or more than one connection. The
default is pointtopoint. The Peer
Server does not support multipoint
primary connections.
Connection nonswitched | Displays whether the Link supports
Type switched switched or nonswitched connections.
The default is nonswitched.
Receive (1-32764) Displays the maximum frame size
Frame (excluding the header) that can be
Size received on the line represented by
this Link. The default is 1000.
Reply Timer (100-60000) Displays the time (in milliseconds)
to wait for an acknowledgment before
starting the recovery procedure. The
default is 3000.
Retry (0-128) Displays that, when the Link is
Maximum secondary, this is the maximum
number of times a frame is
retransmitted before assuming a
fatal error. When the Link is
primary, this is the number of times
that a retry will be tried. The
default is 15.
Poll Pause (0-60000) Displays the time in milliseconds to
pause when the end of the polling
list is reached. Used only when the
link is primary. The default is 200.
Service (1-255) Displays the maximum number of
Limit regular scans of the Service Order
Table for secondary Stations that
will be made before a special scan
is made. Used when the Link is
primary. The default is 4. Not
used at this time.
TWA Send no | yes Displays whether the Link provides
Priority priority for outbound services when
configured for Two-Way Alternating
(half-duplex) data transfer in the
multipoint primary mode. Yes
means that PIUs that arrive for
transmission while data is being
received are transmitted immediately.
No, the default, means that outbound
transmission is strictly determined
by the position of station service
order entries in the service order
table.
This attribute is not relevant to
SDLC point-to-point operations. Not
used at this time.
6.4.6.4 – Counters
Group Polls The number of unnumbered group polls received on
this link.
Frame Receive The number of times the physical layer encountered
Errors an error trying to receive a frame.
Underlying The number of times the Link's underlying Line was
Lines deleted after the Link had established a connection
Deleted to it.
Creation Time The time that the SDLC Link subentity was created.
6.5 – Link Station Subentity
For each logical station on a line, SDLC creates a Station subentity that is subordinate to the Link entity, which manages the station.
6.5.1 – create
create sdlc link station The create sdlc link station command creates an instance of the Station subentity of the SDLC Link entity for each logical station on a line and allocates resources for the subentity. The create command sets the characteristic attributes to their default values. Ex, ncl> create sdlc link sdlc-0 station stn-0 address = c2
6.5.1.1 – Characteristics
Address 2 characters Specifies the address defined for
hexadecimal the secondary Station. The default
is 40.
Group 2 characters Specifies the group poll address for
Address hexadecimal this Station. A value of 0 indicates
that the Station is not in a group.
The default value is 0.
Transfer twa | tws Specifies the link level transmit/-
Mode receive capability of the Station.
The default is twa. TWA is Two Way
Alternate; TWS is Two Way
Simultaneous.
Modulo normal | Specifies that the Station supports
extended normal response mode (window size
ranges from 1 to 7) or normal
response mode extended (window
size ranges from 1 to 127). This
attribute is ignored for connections
that perform XID3 negotiation. The
default is normal.
Window Size (1-127) Specifies the maximum number of
received I-frames that may be
outstanding before this station
requires an acknowledgment response.
This value allows for the detection
of erroneous sequence numbers in
received frames. The default is 7.
Send Frame (1-32764) Specifies the maximum frame size
Size (excluding the header) this Station
can send. This value may be reduced
during preconnection XID
negotiation or by the Station's
client. The default is 265.
Inactivity (0-7200) Specifies the time (in seconds) to
Timer wait for a command before initiating
recovery action. This is used when
the Link is secondary. The default
is 30.
Pass Limit (1-254) Specifies the maximum number of
BLUs that can be sent to the second-
ary Station before starting data
transmission to the next Station in
the Link Service Order Table. This is
used when the Link is primary. The
default is 1. Not used at this time.
Select (1-60000) Specifies the time (in milliseconds)
Pause to pause before sending a response
with the final bit set. This is used
when the Link is secondary. The
default is 50.
Retry (0-255) Specifies the time (in seconds) to
Sequence pause after completing a retry
Pause sequence before beginning a new retry
sequence. This is used when the
Link is primary. The default is 0.
Not used at this time.
Retry (0-127) Specifies the maximum number of
Sequence retry sequences allowed. This is
Limit used when the Link is primary. The
default is 0. Not used at this time.
Immediate no | yes Specifies whether a Station
Poll subentity will be repolled when there
Retry is a reply time-out before proceeding
to next Station on the Link's Service
Order Table. The default is no. Not
used at this time.
6.5.2 – delete
delete sdlc link station The delete sdlc link station command deletes the Station subentity. The Station subentity must be in the off state before it can be deleted. Ex, ncl> delete sdlc link sdlc-0 station stn-0
6.5.3 – disable
disable sdlc link station The disable sdlc link station command stops the operation of the Station subentity of the Link. If a connection exists, the disable command halts protocol operation. When execution of the command completes the Station entity enters the off entity state. Ex, ncl> disable sdlc link sdlc-0 station stn-0
6.5.4 – enable
enable sdlc link station The enable sdlc link station command enables the Station for use. You must enable the link to be successful with this command. An association may be made between the Link subentity and the Modem Connect Line entity of the physical line on which the protocol operates. An enabled Station can accept incoming connection requests or initiate outgoing connection requests. For more information about Modem Connect Line refer to the DECnet-Plus Network Control Language Reference. Ex, ncl> enable sdlc link sdlc-0 station stn-0
6.5.5 – set
set sdlc link station The set sdlc link station command let you set the attributes for SDLC Link Station subentity. The SDLC Station subentity contains the data link attributes that are configured for this connection. Ex, ncl> set sdlc link sdlc-0 station stn-0 address = 62
6.5.5.1 – Characteristics
Address 2 characters Specifies the address defined for the
hexadecimal secondary Station. You can set this
attribute only when the Station is
disabled. The default is 40.
Group 2 characters Specifies the group poll address
Address hexadecimal for this Station. A value of 0
indicates that the Station is not in
a group. The default value is 0.
Transfer twa | tws Specifies the link level transmit/-
Mode receive capability of the Station.
The default is twa. TWA is Two Way
Alternate; TWS is Two Way
Simultaneous. This attribute is
settable only when the Station is
disabled.
Modulo normal | Specifies that the Station supports
extended normal response mode (window size
ranges from 1 to 7) or normal
response mode extended (window
size ranges from 1 to 127). This
attribute is ignored for connections
that perform XID3 negotiation. The
default is normal. This attribute is
settable only when the Station is
disabled.
Window Size (1-127) Specifies the maximum number of
received I-frames that may be
outstanding before this station
requires an acknowledgment response.
This value allows for the detection
of erroneous sequence numbers in
received frames. This attribute is
settable only when the Station is
disabled. The default is 7.
Send Frame (1-32764) Specifies the maximum frame size
Size (excluding the header) this Station
can send. This value may be reduced
during pre-connection XID
negotiation or by the Station's
client. This attribute is settable
only when the Station is disabled.
The default is 265.
Inactivity (0-7200) Specifies the time (in seconds) to
Timer wait for a command before initiating
recovery action. This is used when
the Link is secondary. The default is
30. This attribute is settable only
when the Station is disabled.
Pass Limit (1-254) Specifies the maximum number of
BLUs that can be sent to the second-
ary Station before starting data
transmission to the next Station in
the Link service order table. This is
used when the Link is primary. The
default is 1. This attribute is
settable only when the Station is
disabled. Not used at this time.
Select (1-60000) Specifies the time (in milliseconds)
Pause to pause before sending a response
with the final bit set. This is used
when the Link is secondary. The
default is 50.
Retry (0-255) Specifies the time (in seconds) to
Sequence pause after completing a retry
Pause sequence before beginning a new retry
sequence. This is used when the
Link is primary. The default is 0.
Not used at this time.
Retry (0-127) Specifies the maximum number of
Sequence retry sequences allowed. This is used
Limit when the Link is primary. The default
is 0. This attribute is settable only
when the Station is disabled. Not
used at this time.
Immediate no | yes Specifies whether a Station subentity
Poll will be repolled when there is a
Retry reply time-out before proceeding to
the next Station on the Link's
service order table. This attribute
is settable only when the Station is
disabled. The default is no. Not
used at this time.
6.5.6 – show
show sdlc link station The show sdlc link station command displays the values of the attributes for the SDLC Link entity's Station subentity. The SDLC Station subentity contains the data link attributes that are configured for this connection. Ex, ncl> show sdlc link sdlc-0 station stn-0 address, protocol state
6.5.6.1 – Identifier
Name Displays the unique name assigned to the Station
subentity by the network manager when the Station
is created.
6.5.6.2 – Status
UID Displays the entity's unique identifier, which is
generated when the Peer Server creates the entity.
State Displays the operational state of the Station
subentity. Setting the state is a result of
execution of the enable/disable commands.
The states are
Off The Station is disabled and not available for use.
On The Station is enabled and available for use.
Protocol The protocol state for the SDLC connection on this
State Station entity. The possible states are
Inactive This Station is not enabled. You must issue
an enable command before the SDLC entity can
activate the Station.
Normal The subentity can accept incoming connection
Disconnect requests or initiate outgoing connection
Mode requests.
Normal An SDLC logical link connection has been
Response established.
Mode
Pending This Station is enabled but other Peer Server
Active resources, must be active before the Station can
become active.
Pending You have issued a disable command for this
Inactive Station; no new sessions can use this Station.
The state will change to Inactive as soon as
all active sessions and non-SNA application
links on this Station have terminated.
6.5.6.3 – Characteristics
Address 2 characters Displays the address of the
hexadecimal secondary Station. The default is
40.
Group 2 characters Displays the group poll address for
Address hexadecimal Station. A value of 0 indicates the
Station is not in a group. The
default value is 0.
Transfer twa | tws Displays the link level transmit/-
Mode receive capability of the Station.
The default is twa. TWA is Two Way
Alternate; TWS is Two Way
Simultaneous.
Modulo normal | Displays whether the Station
extended supports normal response mode
(window size ranges from 1 to
7) or normal response mode
extended (window size ranges from 1
to 127). This attribute is ignored
for connections that perform XID3
negotiation. The default is normal.
Window Size (1-127) Displays the maximum number of
received I-frames that may be
outstanding before this station
requires an acknowledgment response.
This value allows for the detection
of erroneous sequence numbers in
received frames. The default is 7.
Send Frame (1-32764) Displays the maximum frame size
Size (excluding the header) this Station
can send. This value may be reduced
during pre-connection XID
negotiation or by the Station's
client. The default is 265.
Inactivity (0-7200) Displays the time (in seconds) to
Timer wait for a command before initiating
recovery action. This is used when
the Link is secondary. The default is
30.
Pass Limit (1-254) Displays the maximum number of
BLUs that can be sent to the second-
ary Station before starting data
transmission to the next Station in
the Link service order table. This is
used when the Link is Primary. The
default is 1.
Select (1-60000) Displays time (in milliseconds) to
Pause pause before sending a response with
the final bit set. This is used when
the LINK is secondary. The default
is 50.
Retry (0-255) Displays the time (in seconds) to
Sequence pause after completing a retry sequ-
Pause ence before beginning a new retry
sequence. This is used when the
Link is primary. The default is 0.
Not used at this time.
Retry (0-127) Displays the maximum number of
Sequence retry sequences allowed. This is used
Limit when the Link is primary. The
default is 0. Not used at this time.
Immediate no | yes Displays whether a Station
Poll subentity will be repolled when there
Retry is a reply time-out before proceeding
to next Station on the Link's service
order table. The default is no.
6.5.6.4 – Counters
Creation The time that the Station subentity was created.
Time
Connections The number of times a connection was established for
Established this Station.
Connections The number of times the SDLC connection was lost.
Lost
Connections The number of times an established connection was
Reset lost and subsequently re-established for this
Station by the snrm or snrme.
Polls The number of Information and Supervisory frames
sent by the primary or received by the secondary
station with the P-bit set.
Reply The number of times the local reply timer has
Timeouts expired after the transmission of a frame with
the P-bit set.
Secondary The number of times a primary station encountered a
Protocol protocol violation committed by an adjacent
Errors secondary station.
SNRM Frames The number of times a SNRM or SNRME frame was
sent by the primary or received by the secondary
station.
DISC Frames The number of times a DISC frame was sent by the
primary or received by the secondary station.
DM Frames The number of times a DM frame was sent by the
primary or received by the secondary station.
Octets Sent The total of the number of octets in I-frames and
UI-frames sent.
Octets The total of the number of octets in I-frames and
Received UI-frames received.
BLUs Sent The total of the number of I-frames and UI-frames
sent.
BLUs The total of the number of I-frames and UI-frames
Received received.
BLUs Resent The total of the number of I-frames and UI-frames
resent because of timeouts or rejects.
FRMR Frames The total number of FRMR-frames sent.
Sent
FRMR Frames The total number of FRMR-frames received.
Received
REJ Frames The number of SDLC REJ-frames sent.
Sent
REJ Frames The number of SDLC REJ-frames received.
Received
RNR Frames The number of times RNR-frames have been sent.
Sent
RNR Frames The number of times RNR-frames have been received.
Received
TEST Frames The total number of TEST-frames sent.
Sent
TEST Frames The total number of TEST-frames received.
Received
TESTs Received The total number of TEST-frames received with a
Invalid CRC bad CRC.
XID Frames The total number of XID frames sent.
Sent
XID Frames The total number of XID frames received.
Received
6.6 – Port Subentity
For each Enabled Station that establishes a connection, SDLC creates a Port entity.
6.6.1 – show
show sdlc port The show sdlc port command displays the attributes for the SDLC Port subentity. A Port subentity is created dynamically for each connection to a remote station. Each Port is created when a connection is established and deleted when the connection is terminated. Use the command show sdlc port * to display a listing of the existing Ports. Ex, ncl> show sdlc port 1 all counters
6.6.1.1 – Identifier
Name A unique value assigned to the Port by the SDLC
entity. The value is an unsigned integer.
6.6.1.2 – Status
UID Displays the entity's unique identifier, which
is generated when the Peer Server creates the entity.
Station Displays the name of the SDLC Link Station subentity
that the client specified in the connection request.
Client Displays the name of the client that connected to
this Port's Station.
Role Displays whether the station role is to be primary
or secondary when it becomes active.
Address Displays the address of the secondary station.
Transfer Displays the link-level transmit/receive capability
Mode for the connection, which is set to the transfer mode
characteristic of the SDLC Station. Might be altered
during XID negotiation.
Modulo Displays the Response Mode supported by the Station.
Normal Response Mode supports Send and Receive Window
Sizes of 1 to 7. Normal Response Mode Extended
supports Send and Receive Window Sizes of 1 to 127.
Send Window Displays the negotiated maximum number of transmitted
Size I-frames that may be outstanding before the adjacent
station requires an acknowledgment response. The
value is initialized as the SDLC Station window size
and might be reduced during preconnection XID
negotiation.
Receive Displays the negotiated maximum number
Window Size of received I-frames that may be outstanding
before this station requires an acknowledgment
response. The value is initialized as the SDLC
Station Window Size and might be reduced
during preconnection XID negotiation.
Send Frame Displays the negotiated maximum size of frames
Size (excluding header) sent by the connection. This
value is initialized as the SDLC receive frame
size. The value might be reduced during
preconnection XID negotiation.
Receive Displays the negotiated maximum size of frames
Frame Size (excluding header) received by the connection.
This value is initialized as the SDLC Station send
frame size. The value might be reduced during
preconnection XID negotiation.
6.6.1.3 – Counters
Creation Displays the time that the SDLC Port subentity
Time was created.
Polls Displays the number of frames sent by the primary or
received by the secondary with the P-bit set.
Octets Sent Displays the total number of octets sent in I-frames
and UI-frames.
Octets Displays the total number of octets received
Received in I-frames and UI-frames.
BLUs Sent Displays the total number of I-frames and
UI-frames sent.
BLUs Displays the total number of I-frames and UI-frames
Received received.
BLUs Resent Displays the total number of I-frames and UI-frames
retransmitted due to timeouts or rejects.