|
|
|
|
This chapter provides instructions for configuring SNA resources to support user applications that use any of the following communication: 3270, RJE, 5250, LU0, and LUA. The SNA resources required by such applications include LUs, session definitions, and user definitions.
For 3270, RJE, LU0, LUA, and dependent APPC communication, you must configure dependent LUs. For independent APPC and 5250 communication, you can use the default control point LU (defined automatically when you configure the local node) or define independent LUs.
Before you can configure the resources described in this chapter, you must perform the following configuration:
Configure the node as described in Configuring the Node.
Configure connectivity as described in Defining Connectivity Components. For 3270, RJE, LU0, LUA, and dependent APPC communication, you must configure the link to support dependent LU traffic. For independent APPC and 5250 communication, the link must support independent LU traffic.
You do not need to configure a direct link to the host if you are using upstream PU concentration or DLUR. For more information, see Configuring PU Concentration and Defining DLUR PUs.
The following list describes the configuration tasks required for each type of user application:
For 3270 communication, configure the following resources:
For a 3270 display or printer, define a dependent LU as described in Defining LU Types 0-3.
To enable 3270 displays to select from a pool of LUs, define an LU pool as described in Defining LU Pools. If a display uses a dedicated LU, you can skip this step.
Define emulator users (or groups of users) and 3270 emulator sessions as described in Configuring 3270 Users and Sessions.
SNAP-IX provides 3270 emulation software that enables you to log on to and use SNA host systems from your Solaris computer. Using this software, you can transfer files between the local and host computers, and control display and printer emulation sessions. You can customize some of the 3270 emulation features, such as key mapping and display attributes. SNAP-IX 3270 emulation also enables you to use HLLAPI applications.
For 5250 communication, configure the following resources:
Configure the node for APPC communication:
If you can use the local node's control point LU, you do not need to configure a local LU. If you need a local LU definition (for example, to use session security), define the local LU as described in Defining Local LUs.
If the local node is a LEN node, you must define the AS/400 system as a remote node as described in Defining Remote Nodes.
If the local node is an APPN end node or network node, you can use the control point LU on the AS/400 system as a partner LU, so you do not need to configure any other partner LUs.
You do not need to define any modes, because 5250 uses the standard mode QPCSUPP.
Define emulator users (or groups of users) and 5250 emulator sessions as described in Configuring 5250 Users and Sessions.
SNAP-IX provides 5250 emulation software that enables you to log on to and use IBM AS/400 systems from your Solaris computer. Using this software, you can control display and printer emulation sessions. You can customize some of the 5250 emulation features, such as key mapping and display attributes.
SNAP-IX provides support for remote job entry (RJE), enabling you to submit jobs to a host computer for processing. The RJE workstation daemon handles transfer of jobs to the host, and also handles the output returned from the host.
You can prepare jobs for submission to the host and add them to the queue for an RJE workstation at any time, regardless of whether the RJE workstation is running. When the workstation runs, it submits any outstanding jobs to the host (in the order in which they were submitted). It also routes any output received from the host to the appropriate destination, as determined by the configuration.
For RJE communication, configure the following resources:
Define a dependent LU as described in Defining LU Types 0-3.
Define RJE workstations as described in Configuring RJE Workstations.
To support an LU0 or LUA application, configure the following resources:
Define a dependent LU as described in Defining LU Types 0-3.
To enable an LU0 or LUA application to select from a pool of LUs, define an LU pool as described in Defining LU Pools. If the application uses a dedicated LU, you can skip this step.
An LU0 or LUA application uses the LU 0-3 resources of the node to communicate with a host application. You do not need to define any additional resources.
For information about managing SNAP-IX from a host NetView program, see Managing SNAP-IX from NetView.
To enable 3270 communications, you must define emulator users or groups of users as described in Configuring 3270 Emulator Users, and 3270 emulator sessions as described in Configuring 3270 Sessions.
If your SNAP-IX system includes 3270 emulation programs running on Windows clients, note that this section describes the configuration required on the Solaris server in order to support these programs. On the client, you may also need to perform configuration for the particular 3270 emulation program you are using, which is not part of the SNAP-IX configuration. Refer to the 3270 emulation program's documentation for more information.
You must add emulator user definitions for each user who requires access to a 3270 emulator.
Adding an individual user gives access to only that user. Any sessions added to the user are available only for that user.
You can also add a group of users in a single operation. Adding a group of users gives access to all members of the group. Any sessions added to the group are available for all users in the group. This means that you do not have to define each user individually, reducing the time needed to configure users.
If there are several users with sessions using the same LUs or LU pools, you should first define one user and add all the session definitions. To add the other users, you can copy the first user definition.
Emulator user information can be accessed by the SNAP-IX 3270 emulation program or by a Windows client running an emulation program that is compatible with Microsoft's SNA Server product.
To configure an emulator user or group, use one of the following methods:
Select Emulator users and sessions from the Windows menu on the Node window, then choose one of the following options from the Selection menu:
New user
New user group
Issue the following command:
define_emulator_user
The following parameters are required for each 3270 emulator user definition:
The name of the emulator user.
For users running the emulation program on Solaris systems, thisis the name used to log in on that computer. The name is set up by the administrator of the Solaris system.
For the Win32 client running on Windows 95 or Windows NT, this name matches a login name defined on the Windows 95 or Windows NT system.
When adding a user group, supply the name of the group to which the user belongs.
For users running the emulation program on Solaris systems, thisname is set up by the administrator of the Solaris system.
For the Win32 client running on Windows 95 or Windows NT, you can find the group name through the Windows Program Registry.
For a user group, the remaining fields in the dialog apply to all members of the group.
You can set up a default user definition that is used by all users who do not have their own individual or group definitions. To do this, specify a user or group name of DEFAULT.
This field is relevant only to users of the SNAP-IX 3270 program.
If the user has a style file, enter the file name. If there is no style file, the user runs the emulation program with a default style.
The style file determines the appearance and behavior of the emulation screens and keyboard for the emulator user. These may be different for different users.
When entering the style file name, you should omit the .stu extension.
If the user specifies a style file on the command line, that file takes the place of the file specified in this field.
The user's privileges for accessing and modifying the style file. This field is used only by the SNAP-IX 3270 emulation program.
The user cannot specify a style file at the command line when starting the emulation program, and cannot modify the style file settings from within the emulator.
The user can specify a style file from the command line and can modify its settings.
The user can specify a style file at the command line, but cannot modify its settings.
The user can specify a User style file from the command line.
How many sessions to define for the user and which LU or pool to use for each session.
The user permissions for SNAP-IX 3270 emulator users:
If you select this option, also specify the maximum number of 3270 sessions a user can use from a single 3270 emulator. By default, the maximum number of sessions is set to 10.
The user can change 3270 sessions to use different LUs from those configured.
The user can view RTM data.
The user can send alerts to NetView.
After performing the emulation user configuration, you can define 3270 sessions for users or groups as described in Configuring 3270 Sessions.
A 3270 session definition must be added as the child of an emulator user or group definition. You can configure a single 3270 session to use a display or printer LU, or assign it an LU pool (enabling it to use any available LU in the pool). You can also configure several 3270 display sessions that use the same LU pool, in a single operation.
Emulator session information can be accessed by the SNAP-IX 3270 emulator program
To configure 3270 sessions, use one of the following methods:
Select Emulator users and sessions from the Windows menu on the Node window, then choose New.
Issue the following command:
define_emulator_user
You can configure a single session or multiple sessions for 3270 emulation:
To configure a single session, supply the following information:
A name to identify the session.
The SNAP-IX Solaris 3270 emulation program uses sessions with names in the range SESS0001-SESS0010. To define a session that is initially available to the user, choose a name in this range. If the user has remap permission, you can define a session to which the user can remap, choosing a name that is not in that range (for example, SESS0011).
Specify whether the session is a display or printer session.
The name of the LU or pool to be used by the session. Assign printer LUs for printer sessions, and display LUs or pools of display LUs for display sessions.
The LU should be defined on a host link station, and an LU pool should be defined in the LU Pools window.
If a session record specifies the name of an individual LU from a pool, but that LU is unavailable when the session is activated, the session can use any other available LU from the pool.
To configure multiple sessions, supply the following information:
The first five characters for the session name. A unique name is constructed for each session, using this base name and a session number.
If you want to add several 3270 sessions for use with the SNAP-IX 3270 emulation program, you can specify a base name of SESS. The first 10 sessions are automatically given the names SESS0001 -SESS0010.
The name of an LU pool from which the sessions can be assigned LUs.
|
|
|
 |
|