Configuring LUs

When a user configures a 5250 emulator to access an AS/400, the emulator is configured with the local and remote APPC LU alias name. The LU alias names are mapped to LU names that are used for the conversation with the AS/400.

SNA Server allows you to define a default local and remote APPC LU for each user group accessing the AS/400. Setting default values relieves the user from having to remember APPC LU names; these values should be specified, if possible.

When creating local APPC LUs, it is recommended that you use the name of a user or group as the local LU alias. When the session from a particular user or group is active, the LU alias name is displayed in SNA Server Manager. Matching local LU alias names with user names allows you to tell which 5250 users are connected to the AS/400. This also makes it easy to keep track of which local LU a particular user should use.

To use this method, create a separate local APPC LU with an LU alias that matches the user name of each person or group being added to the SNA Server subdomain. After the LU is created, assign the LU to the user as the default local APPC LU along with a default remote APPC LU.

In SNA Server, you can also specify an implicit incoming remote LU that defines the properties to use when SNA Server receives a request to start a session with a local LU and the remote LU named in the request is not recognized by SNA Server. Along with the incoming remote LU, an implicit incoming mode is specified that defines the session characteristics when the mode named in the request is not recognized by SNA Server.

Specifying implicit incoming remote LU/mode pairs is useful if you want to accept incoming requests that arrive by many different remote LUs without having to explicitly define each remote LU in SNA Server. When the implicit incoming remote LU and mode are specified, the remote LU does not need to be recognized by the server. As long as the local LU specified in the session request is recognized, the connection can be initiated.