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.
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*}
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 – 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.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.
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
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
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 – 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.1 – Identifier
Name Identifies the name given to the Access Name entity when it was created.
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.