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.
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
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 – 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
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
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.
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
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.
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.
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.
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.
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*}
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, { }.
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
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.
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
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
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.
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
5.5.1 – Identifier
Name Identifies the name given to the Access Name entity
when it was created.
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.
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.
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
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.
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
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
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.
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
6.4.1 – Identifier
Name Identifies the name given to the Authorization entity
when it was created.
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.
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
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}
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.
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
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 ("").
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
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
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
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
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 ("").
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
7.7.1 – Identifier
Name Identifies the name given to the LU entity when it
was created.
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.
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.
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.
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.
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}
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.
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
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.
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
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}
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.
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
8.5.1 – Identifier
Name Displays the name given to the Partner LU by the
Peer Server when it was created.
8.5.2 – Status
Definition Displays how the Partner LU was created. Values are
"Static" and "Dynamic."
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.
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.
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
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.
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.
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.
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
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.