Updated: March 15,1996 | Go To TechNet Home Page |
SNA Server Setup Program
Setup and Configure SNA Server Clients
Operate the DEMO SDLC Link Service
Setup and Configure ODBC/DRDA
Operate the ODBC/DRDA Demo
Using SNA Server Diagnostic Tools
Modifying or Removing SNA Servers
Modifying or Removing SNA Clients
The SNA Server Setup program installs SNA Server, using the information you provide in various dialog boxes. Once the initial files are installed, you add and configure the link services for your SNA server. Setup then creates a configuration file on the primary SNA server. The connections, LUs, groups, and user access rights that you configure with the SNA Server Admin will also be stored in the configuration files. Setup is a graphical interface that allows you to install, configure and remove SNA Server, link services, and SNA Server client software.
To use Setup, you must be logged on as an Administrator on the Windows NT Server, because Setup requires the ability to access the Windows NT Registry.
Setup installs the following software components on an SNA server: SnaBase, SnaServer, Link Services, and SnaNMVT, NVRunCmd, and NVAlert. Of the components listed in this section, only SnaBase is automatically started when the Windows NT system is started. To start any other service automatically, use the Control Panel to configure the startup type for the service, as described in your Windows NT documentation.
For information on creating diskette images, refer to the SNA Server 2.11 README.WRI file.
A welcome to SNA Server Setup dialog box appears.
Licensing for the Microsoft BackOffice family of server products requires a Server License and a license for each client computer to access the server, which is called a Client Access License. These licenses are acquired separately prior to using the product. For SNA Server, Windows NT Server, and SQL Server, the Client Access License can be used in either of two licensing modes (Per Server and Per Seat) offering customers the flexibility to choose the option that best meets their needs.
SNA Server version 2.11 Setup presents a Choose Licensing Mode dialog box. You will be required to select a licensing option and accept the terms of the license agreement for Setup to complete. In this dialog box, you must indicate whether you want SNA Server version 2.11 to be installed in the Per Server or Per Seat licensing mode. Every box of SNA Server 2.11 comes with one client access license, therefore if you are unsure, for purposes of installing the SDLC Demo Link Service you can choose "per seat".
You can record identifying information in your SNA Server software when the software licensing dialog appears.
By entering the Product ID (PID), you make it available for display through the SNA Server version number utility, SNAVER, so that if you call for product support, you can readily identify your software when requested.
In the Confirm License Information dialog box, choose the OK button. The Installation Path dialog box, shown in the next section, appears.
You can use the default installation path offered by Setup (C:\SNA), or change the path.
In the Installation Path dialog box, choose the Continue button.
Setup copies the files needed by SNA Server and creates the Registry entries for all sub-services.
If Setup detects more than one client/server protocol on your computer, you must specify which protocols you are using.
You will only see the Select Client/Server Protocols dialog box if there is more than one client/server protocol on your computer.
If you did not select Microsoft Networking (Named Pipes) as one of your client/server protocols, you must specify the name of the network domain. If your operating system is Banyan VINES (and not Microsoft Networking), you must also specify the Banyan StreetTalk group name.
In the appropriate box, type the network domain name.
For a TCP/IP network, you can specify the name in any of several forms: the domain name used in the Windows NT domain or the host name plus the TCP domain name. If you are using Banyan VINES (and not Microsoft Networking), the StreetTalk Group Name dialog box appears.
When installing an SNA server, the server is designated as primary, backup, or member.
The primary SNA server contains the domain-wide configuration file. The configuration file reflects the SNA Server resources for the domain, including all SNA servers, link services, LUs, and 3270 users. There can be only one primary server in the domain. Typically, the primary server is the first server installed.
A backup SNA server is a server on which the configuration file is replicated by SNA Server. There can be more than one backup server in a domain. SNA Server will load the copy of the configuration file located on a backup SNA server if the primary SNA server goes down; in this case, servers and connections can be started and stopped, but the configuration cannot be changed or saved.
A member SNA server does not contain the configuration file. One or more SNA servers can operate as member servers.
Setup copies the files to the selected location. If you are installing from floppy disks, you will be prompted to insert floppy disks as they are needed.
Setup can create an icon in the SNA Server program group linked to the SNA Server on-line Table of Contents and on-line documents.
Link services define the protocol used between the SNA Server software and the communications adapters installed in a computer. Link services are written to the SNADIS interface. You can install any of the link services listed in the Link Service Installation dialog box.
DEMO SDLC Link Service is capable of emulating a 3270 host or an AS/400, depending on the script file you choose and the SNA Server configuration. Script files are provided for emulations of sessions with a 3270 host or an AS/400 computer.
DEMO SDLC Link Service is installed in the same way as an SDLC link service, but rather than selecting and configuring an SDLC card type, you specify a script file that contains the messages the DEMO SDLC Link Service needs to send to SNA Server. A link service can be installed when installing SNA Server, or after SNA Server setup is complete.
3270 Demo Scripts
Choose this option for an emulation of 3270 flash. (Flash is a test transaction program which runs on the host, continuously sending screenfuls of data at the emulator. This program can be used to simulate a live host session and provides a means to demo NetView RTM data displayed in Windows NT Performance Monitor.)
Choose this option for an emulation of 3270 logon and logoff to a mainframe computer.
5250 Demo Script
Choose this option for a demonstration of a 5250 emulation session on an AS/400 computer. This demo script provides demonstrations of both a 5250 loop script and a SQL Query to a database on an AS/400.
The supplied demo link scripts are automatically copied to the SNARoot\SYSTEM directory by Setup.
From the SNA Server Setup Finished dialog box, you should proceed directly to SNA Server Admin to configure the connections and LUs for your link services.
The following section of this Test Drive document explains how to continue with the configuration of SNA Server.
After you have used Setup to install SNA Server, the link services and client software, you use SNA Server Admin to configure connections, LUs, and assign user rights to the LUs. Later, if you need to change or create additional link services, you can run Setup again to configure these link services.
The SNA Server Admin program provides a graphical interface that allows you to configure connections between PCs and remote computers - IBM mainframes, AS/400 systems, or other PCs - within an IBM SNA network.
Two important elements are used in every SNA configuration: connections and logical units (LUs). A connection is the data communication path between computers on the SNA network. An LU is a preset unit containing all the configuration information needed for a user, program, or downstream system to establish a session with a host or peer computer. Connections are configured first, and then one or more LUs can be assigned to each connection.
Multiple connections can share a single link service. Multiple LUs can share a single connection.
After LUs are configured, they can be grouped together in LU pools, to maximize access to resources. A user, LUA application, or downstream system using the pool can get LU access as long as one of the pooled LUs is available.
You can start SNA Server Admin from the Setup program or by clicking the SNA Server Admin icon.
The SNA Server Admin display is structured around several windows that appear inside the main window. The windows can be shrunk to icons, and then restored to windows. The windows are as follows:
Note that the SNA Server name is highlighted (in our example, the name is "PLARSEN").
The following Connection Properties dialog box appears:
Confirm that the link service for SDLC1 is SnaDemo1. During Setup, we associated SnaDemo1 with the 3270 Continuous Demo script file.
The SDLC Setup dialog box appears:
Although the default values are not modified, steps 5-6 must be performed to properly configure the demo link connection.
The Insert LU dialog box appears:
The New 3270 LU Properties dialog box appears:
The Add Users and Groups dialog box appears:
The Assign User LU/Pool Sessions dialog box appears.
To configure 3270 Logon Demo Link Service, follow the directions above for the 3270 Continuous Demo Link Service. The Connection Name in our example, and will be by default, "SDLC2". The Link Service Name should be "SnaDemo2".
To assign host LUs to the 3270 Logon Demo Link, follow the directions above, except be sure to choose a different LU name, such as "LOGON".
No additional users or groups need to be added.
To assign the "LOGON" LU to everyone, follow the directions above.
The New Pool dialog box appears:
The Assign Pool LUs dialog box appears:
The Assign User LU/Pool Sessions dialog box appears.
Note that the SNA Server name is highlighted (in our example, the name is "PLARSEN").
The following Connection Properties dialog box appears:
Confirm that the link service for SDLC3 is SnaDemo3. During Setup, we associated SnaDemo3 with the AS/400 Demo script file.
The SDLC Setup dialog box appears:
New functionality has been added to SNA Server Admin to automatically assign a new APPC (Remote) LU when the Connection Properties dialog box is closed, if the connection has been configured for Peer System.
The user is prompted to automatically create a new APPC Remote LU when the user completes configuring of a peer link. The prompt dialog appears automatically:
The APPC Remote LU Properties dialog appears:
The LU Name and Uninterpreted LU Name text boxes are automatically filled in. Leave other settings at the default values.
No additional users or groups need to be added.
The Group Properties dialog box appears:
The SNA Server configuration is saved to \\SNAroot\SYSTEM\CONFIG\COM.CFG.
The SNA Server configuration is backed to \\root\SNASRVR.SNA.
The Microsoft SNA Server Installation Guide, Microsoft SNA Server Administration Guide, Microsoft SNA Server 2.11 Enhancements Guide, gives detailed information on the installation and configuration procedures.
Client software must be installed on the client computer in order to use SNA Server. You can install the client software either locally, via disk, or over the network.
You must be ready to specify whether the SNA Server(s) the client will be communicating with is in the local or a remote domain. Local indicates that the primary server containing the configuration file is located in the same SNA domain. Remote indicates that the server resides in a different domain. For remote, you will need to indicate the primary server name. In our example, the SNA Server name is "PLARSEN".
The SNA Server Setup welcome dialog box appears.
The Path Selection dialog box appears.
The SNA Server Client Setup program will detect which LAN protocols are installed on your workstation. The Select Client/Server Protocols dialog appears:
The SNA Client Mode dialog appears:
Choosing the "Install Administration Program" check box will cause Setup to install a local copy of the SNA Server Admin program. Admin allows users with sufficient privileges to administer SNA Server located anywhere on the network.
The SNA Server Setup welcome dialog box appears.
The Path Selection dialog box appears.
The SNA Server Client Setup program will detect which LAN protocols are installed on your workstation. The Select Client/Server Protocols dialog appears.
The SNA Client Mode dialog appears.
The Microsoft SNA Server Installation Guide and SNA Server 2.11 Enhancements Guide give detailed information on the installation procedure.
Choose the "FLASH" session, which we associated with the 3270 continuous demo script file.
The host SSCP screen appears.
The host logon screen appears.
The host logon sequence completes and the ready prompt appears:
The VM logon screen appears.
A VM Ready prompt is displayed.
Successive screens flash non-interactively.
The 3270 applet disconnects from the host.
Choose the "LOGON" session, which we associated with the 3270 continuous demo script file.
The host LOGON screen appears.
A password prompt is displayed on a VM system screen.
A VM READY prompt is displayed.
A blank host system screen is displayed.
The 3270 applet disconnects from the host.
The Sign-On dialog box with the user ID/password selection appears:
The AS/400 logon screen appears. If the logon screen does not appear:
The AS/400 Main Menu appears.
10 -- 5250 Loop Demo
This will start a demonstration of 5250 flash. The 5250 Applet will cycle between the User Tasks and Display Messages screens indefinitely. (This is similar to 3270 Flash.)
Press the ESC key to stop this emulation and return to the AS/400 Main Menu.
20 -- SQL Query Demo
This will start a demonstration of running a SQL Query on an AS/400 database.
Press the ENTER key after each screen of information to step through the demonstration and return to the AS/400 Main Menu.
90 -- Sign Off
This will return you to the AS/400 Sign On screen. Entering any other number or characters other than those listed above will have no effect on the demonstration.
The 5250 applet disconnects from the host.
The Microsoft SNA Server 2.11 Enhancements Guide gives detailed information on the installation and configuration procedures.
SNA Server version 2.11 includes the StarSQL ODBC/DRDA drivers for Windows and Windows NT clients. With these drivers, applications designed to use the ODBC interface and Structured Query Language (SQL) can access databases located on IBM hosts that use the DRDA protocol to manage distributed data, without requiring a host-based database gateway. These drivers allow ODBC-enabled applications (such as Microsoft® Excel and Microsoft® Access) to query, create, delete, and update tables in the following host databases:
The drivers are installed as an integral part of the SNA Server client software for Windows. Windows NT clients have the option of installing the software. SNA Server's Client Setup program will install an updated ODBC Administrator program to ensure that the latest ODBC 2.10 drivers exist on the local PC.
In order to access a host-based database, the user must specify the host database as an ODBC data source by using the ODBC Administrator installed by the SNA Server Client Setup program. Typically, an ODBC-enabled application provides a method for accessing the ODBC Administrator, which is also available as a Program Manager program item or Control Panel option, depending on the operating system and the ODBC driver(s) that have been installed.
The Data Sources dialog box appears:
The Add Data Source dialog box appears:
The StarSQL Data Source Setup dialog box appears.
To set up the data source, perform the following procedure.
The Data Sources dialog box (shown in figure X.1) appears.
The StarSQL Data Source Setup dialog box (shown in figure X.2) appears.
If you are adding a new data source, you must set up the connection. If you are configuring an existing data source, you can change the connection setup. In our example, you can leave this check box unmarked.
The StarSQL Connection Setup dialog box appears.
The actual method you use to select a data source and initiate a connection to a database on an IBM host depends on the application you are using. For example, to select a data source using Microsoft Query (provided with such applications as Microsoft Access and Microsoft Excel), choose the New Query or Open Query command from the File menu.
When you select a StarSQL data source, the StarSQL connection dialog box may appear, depending on host security.
To connect to the data source, enter your user ID and password. To change settings for the data source, choose the Options button. When you are finished entering the information, choose the Connect button to establish the connection, or choose the Cancel button if you do not want to connect to the host database.
SNA Server ODBC/DRDA drivers support virtually all ODBC-enabled applications and programming environments. Examples of these include:
In addition to these, many other applications support the ODBC programming interface and so can access host-based databases through the ODBC/DRDA drivers.
ODBC is a call-level interface for applications that accesses multiple databases by using a single set of function calls, providing a standard database access through a common client-side interface.
Applications interact with the ODBC Driver Manager, which is a Windows Dynamic-Link Library (DLL). The Driver Manager (ODBC.DLL) interprets the application calls to the database using the ODBC/DRDA driver included with SNA Server client software. The Driver Manager loads and unloads the driver, performs status checking, and manages multiple connections between applications and data sources. The ODBC/DRDA driver manages the data source and processes the ODBC calls and SQL statements. The driver interprets the calls and issues the appropriate DRDA commands.
ODBC supports transaction commit and rollback, asynchronous processing, canceled queries, primary and foreign keys, and four levels of transaction isolation.
The ODBC/DRDA driver also supports the ability to pass SQL strings to the remote database without translation or modification. You can use native SQL features specific to the IBM databases you access as well as the ODBC extensions.
The Microsoft SNA Server 2.11 Enhancements Guide, gives detailed information on the installation and configuration procedures.
The DEMO SDLC Link Service contains an AS/400 Demo script file. In addition to terminal emulation capabilities, this script file also provides the ability to demonstrate the basic capabilities of the ODBC/DRDA driver.
Before you can demonstrate the ODBC/DRDA driver with Microsoft Excel, you must setup Excel using the Complete/Custom option in order to install Microsoft Query. To demonstrate the 32-bit ODBC/DRDA driver, you must install Microsoft Excel for Windows NT.
To demonstrate a SQL query by using the ODBC/DRDA driver and the DEMO SDLC Link Service, follow this procedure:
Microsoft Query starts and the Select Data Source dialog box appears:
The ODBC Data Sources dialog box appears.
The StarSQL connection dialog box appears:
The Add Tables dialog box appears:
You are returned to the Microsoft Query window.
The pane fills with the selected data.
Query exits and Excel displays the Get External Data dialog box.
The Microsoft SNA Server 2.11 README.WRI file, gives detailed information on the demo instructions.
When a service appears to be having difficulty, it may be helpful to gather status information before making the decision about starting, stopping, resetting, or modifying the service.
Under the Status column, the LU will show active, inactive, not configured, or N/A.
This is a Windows NT utility that provides information on the sequence and type of events that led up to a particular state or situation. To assist in testing configurations and diagnosing problems, Windows NT keeps event log files, which are stored in WindowsRoot\SYSTEM32\CONFIG\*.EVT.
You may specify parameters for event logs that include the server on which event logs are to be stored, the types of events to be recorded, and any additional servers to which pop-up error messages should be routed.
SNA Server Trace (SNATRACE) turns on tracing for SNA Server and Windows NT-based clients. For other clients, tracing is turned on with special commands or with lines in an initialization file. Trace files record activity between or within components of the SNA Server. The files provide detailed information about the exact sequence of events occurring within an SNA server or between an SNA server and another system on the network The trace files containing diagnostic information are located at SNAroot\TRACES\*.TRC
First, decide which software components you need information about to determine what type of trace you will need to run.
You can enable or disable trace options on an SNA server or a Windows NT-based client.
The SNA Server Trace Options dialog box appears:
If the selected service is SNA Applications, select options for API tracing:
For the selected service, select options for message tracing:
To disable message tracing, choose the Clear button.
To minimize the writing of trace information to disk and cause the information to be held in a memory buffer until it is efficient to write it to disk, select this box.
To cause trace information to be written to disk, clear this box.
The Performance Monitor is a graphical tool that allows you to measure the performance of computers in the network. The Performance Monitor oversees SNA objects as configured by the user. You can select counters that you want to measure. It is important to note that before any SNA Server counters can be measured, one or more SNA servers must be operating.
The Response Time Monitor (RTM) is an IBM function that measures the length of time host responses take during a 3270 session. The SNA Server Administration Tool allows you to specify the times at which RTM should send data and define the triggers that will cause RTM to register that the host has responded. Note that the emulator that your 3270 users have must support RTM for these settings to be meaningful.
RTM Data Sent at. Select one or both options.
RTM Timers Run Until. Select the point on which the host is to register response.
RTM Thresholds Specify the cutoff times in tenths of a second at which RTM saves its count response and restarts count.
The Performance Monitor application appears:
The Add to Chart dialog box appears:
Choose the Instance you want to monitor. In our example, choose "LOGON".
View the response time in Performance Monitor by advancing the 3270 Applet one screen at a time. The response is registered graphically by Performance Monitor.
The Microsoft SNA Server Administration Guide, Microsoft SNA Server Planning Guide, gives detailed information on the diagnostic tools.
When you run the SNA Server Setup program after the initial installation, Setup detects the existing configuration and presents you with a Setup Options dialog box. From Setup Options, you can:
When removing SNA Server device drivers, such as the Demo SDLC Link Service, always use SNA Server Setup. Do not use the Network option of the Windows NT Server Control Panel to remove such drivers as doing so may cause unexpected system events.
A welcome to SNA Server Setup dialog box appears:
The Setup Options dialog box appears:
You can configure any of the installed link services, or add a link service. If you no longer need a link service, you can remove it.
The Link Service Configuration dialog box appears.
You can change the configuration role for an SNA server. Under Options in the Setup Options dialog box, choose the Role button. The Change SNA Server Role dialog appears. Choose the appropriate new role.
You can change client/server protocol selections after installing SNA Server.
The Select Client/Server Protocols dialog appears.
You can remove SNA Server at any time. However, removing SNA Server deletes all of the SNA Server files and directories from your computer, including link service files. To use SNA Server again, you must run Setup to reinstall the files from the beginning.
To remove SNA Server from an entire domain, do the following in the order given:
The Confirm Removal dialog box appears:
SNA Server Setup removes SNA Server and unbinds the Link Services from the Networks portion of the Windows NT Server Control Panel.
The Microsoft SNA Server Installation Guide, Microsoft SNA Server Planning Guide, gives detailed information on the modifying or removing SNA Servers.
Once a client is installed, you may want to change the options selected during Setup, such as changing the server operation from local to remote. When Setup is run, it determines whether a version of the SNA Server is already installed. If so, Setup assumes that you want to modify or remove the client software.
The Setup Options dialog box appears.
The Setup Complete dialog box appears.
Once a client is installed, you may want to remove it.
The Setup Options dialog appears:
The Confirm Removal dialog appears:
The Microsoft SNA Server Installation Guide, Microsoft SNA Server Planning Guide on your TechNet CD, gives detailed information on the modifying or removing SNA Server Clients.
Click Here to Search TechNet Web Contents | TechNet CD Overview | Microsoft TechNet Credit Card Order Form At this time we can only support electronic orders in the US and Canada. International ordering information. |
Go To TechNet Home Page | ©1996 Microsoft Corporation | Go To Microsoft Home Page |