Novell is now a part of Micro Focus

NetWare for SAA v1.2 Rules of Thumb

Articles and Tips: article

Alan Troup
Technical Writer
Novell Sunnyvale

01 May 1992


This AppNote contains information about configuring NetWare for SAA v1.2 for optimal reliability and performance. It discusses the host connections and LAN protocols supported by the product. It also gives hardware and software recommendations for NetWare for SAA and for the NetWare 3270 LAN Workstation products (DOS, Windows, and Macintosh).

Introduction

NetWare for SAA running on a NetWare v3.11 server provides IBM host connectivity for NetWare LANs. This Application Note contains information to aid you in configuring NetWare for SAA for optimal reliability and performance. It discusses the host connections and LAN protocols supported by NetWare for SAA. In addition, it gives hardware and software recommendations for NetWare for SAA and for the NetWare 3270 LAN Workstation products (DOS, Windows, and Macintosh).

Supported Configurations

NetWare for SAA is a set of NetWare Loadable Modules (NLMs) that run using the NetWare v3.11 operating system. NetWare for SAA can be installed to run on a single server along with other services such as messaging, file, and print services. This configuration is referred to as an "integrated" NetWare for SAA server. The product can also be installed on a separate server dedicated to communications, in which case it is referred to as a "dedicated" NetWare for SAA server.

NetWare for SAA Connection Types

NetWare for SAA supports up to 508 concurrent mainframe host sessions from a single server. Two of these are used by NetWare for SAA, leaving 506 user sessions. The sessions can be any combination of display, printer, or Advanced Program-to-Program Communications (APPC) sessions. NetWare for SAA supports the following types of host connections:

  • Synchronous Data Link Control (SDLC)

  • Token Ring

  • Quality Logical Link Control (QLLC), or X.25

The various types of host connections possible with NetWare for SAA are illustrated in Figure 1.

NetWare for SAA supports physical unit (PU) 2.0 and PU 2.1 connections to mainframe hosts and to AS/400 minicomputers, and PU 2.1 connections between LAN workstations. Only one PU 2.1 connection can be made to an AS/400 using PC Support (for a maximum of 253 sessions).

NetWare for SAA is sold in 16-, 64-, and 254-session configurations. Each configuration provides you with the number of dependent (PU 2.0) sessions you purchased. In addition, you also get an equal number of independent (PU 2.1) sessions.

Two NetWare for SAA products can be installed on the same server to increase the number of supported sessions. For example, you can install two 64-session products to get 128 independent and dependent sessions, or a 16-session and a 64-session product to get 80 independent and dependent sessions.

Figure 1: NetWare for SAA allows numerous types of host connections to IBM mainframes and minicomputers.

Multiple PU Configurations

NetWare for SAA will support two concurrent host connections to either the same host or to two different hosts from a single NetWare for SAA server. The two host connections can include a connection to an AS/400 minicomputer and a second connection to a mainframe.

You can install adapters for two host connections of the same type (for example, two Token Ring host connections), or you can install adapters for host connections of different types (for example, one SDLC and one Token Ring host connection).

You must install one adapter card for each host connection. However, you need not purchase multiple host adapters to use multiple copies of NetWare for SAA. For example, you can purchase a 16-session version and a 64-session version and combine them to get 80 sessions over one PU to the host.

Using an SDLC Host Link

NetWare for SAA can be connected via an SDLC host link to a 37xx communications processor, a 9370 host processor, or an AS/400 minicomputer. Two SDLC cards can reside in one server, allowing concurrent access to two remote hosts. NetWare for SAA supports the following SDLC adapters:

  • NetWare for SAA Synchronous Adapter

  • Novell Synchronous Adapter (purchased and supported from Microdyne Corporation)

  • Novell Synchronous/V.35 Adapter (purchased and supported from Microdyne Corporation)

The NetWare for SAA Synchronous Adapter is recommended because it supports speeds up to 64 Kbps in either a PC or a Micro Channel architecture configuration. The NetWare for SAA Synchronous Adapter ships with two cables. Use the RS-232 cable for speeds up to 19.2 Kbps, and use the V.35 cable for speeds above 19.2 Kbps up to 64 Kbps.

Using a Token Ring Host Link

NetWare for SAA can be connected via a Token Ring host link to a 3172 controller, a 3174 controller, a 37xx communications processor, a 9370 host processor, or an AS/400. Either the IBM Token Ring Adapter 16/4 for Industry Standard Architecture (ISA) configurations or the IBM Token Ring Adapter 16/4/A for Micro Channel bus configurations must be used. These are the only two cards supported by NetWare for SAA for the host connection.

Two Token Ring cards must be used for configurations involving two host connections. The adapter supporting the workstation LAN connections can be any Novell-tested LAN adapter for NetWare v.311

If you are using the Token Ring topology for both LAN connections and host connections, we recommend installing a Token Ring adapter for each connection - one card to handle the LAN traffic and one card for each host connection. Alternatively, you can install a single adapter for the LAN and one for the host, but the one-adapter-per-connection configuration provides optimal performance.

Using a QLLC Host Link

NetWare for SAA can be connected via a QLLC host link to an X.25 network. Driver support is shipped with the appropriate third-party adapter card. For update information, contact Novell Product Information at 1-800-NETWARE.

LAN Configurations and Protocols Supported

Workstations can access the NetWare for SAA server using any of the LAN topologies supported by NetWare v3.11: Arcnet, Ethernet, Token Ring, LocalTalk, TokenTalk, and EtherTalk. A NetWare v3.11 server running NetWare for SAA can coexist with NetWare v2.x servers on the same network, as shown in Figure 2.

Figure 2: A server running NetWare for SAA can coexist with a NetWare v2.x server on the same network.

NetWare for SAA supports the Sequenced Packet Exchange/Internetwork Packet Exchange (SPX/IPX), Transmission Control Protocol/Internet Protocol (TCP/IP), and AppleTalk network transport protocols. NetWare for SAA can be accessed from workstations located anywhere on an enterprise network comprised of multiple interconnected LANs.

Connecting to an AS/400

There are two types of configurations possible for connecting to IBM AS/400 minicomputers with NetWare for SAA: 5250 emulation and 3270 emulation.

5250 Emulation

If you are using IBM's AS/400 PC Support program, you can install the NetWare Router for AS/400 PC Support on the workstation to work along with NetWare for SAA. Doing so allows you to run any PC Support application, including the PC Support Work Station Function (5250 emulation). The NetWare for SAA server then routes the 5250 data stream between the workstations and the AS/400.

With this configuration, you do not need to run NetWare 3270 LAN Workstation software on your workstations. Instead, the workstations require only the DOS portion of IBM AS/400 PC Support and the DOS portion of the NetWare AS/400 Router. The NetWare AS/400 Router software for the server and the workstations is included with NetWare for SAA.

The 5250 emulation method has the following advantages over a direct IBM PC Support solution:

  • Requires less memory on the workstation by the AS/400 PC Support software. The NetWare AS/400 Router uses about 5KB of RAM, whereas IBM's Router uses about 60KB.

  • Provides a cost-effective way to connect remote LAN workstations to an AS/400. NetWare for SAA allows access to the AS/400 by remote NetWare clients over the internet.

  • Supports a variety of topologies and LAN adapters. NetWare for SAA supports token ring, ARCnet and Ethernet topologies, and all Novell-certified adapters.

  • Does not interfere with client applications. IBM's LAN Support program has problems coexisting with client applications. The NetWare AS/400 Router communicates to the server via the IPX/SPX protocol and does not require IBM's LAN Support.

When connected to an AS/400 minicomputer running IBM AS/400 PC Support, NetWare for SAA supports up to 253 concurrent independent sessions over a single profile (host link). These sessions must be Advanced Program-to-Program Communications (APPC) sessions. However, you can make a PU 2.0 connection from the same NetWare for SAA server if you want more than 253 sessions. NetWare for SAA supports SDLC or Token Ring connections to the AS/400 running PC Support.

Here are some notes regarding the NetWare for SAA and AS/400 connectivity solution.

  • This NetWare solution is compatible with all APPN networks.

  • IBM's AS/400 PC Support is purchased separately, from IBM.

  • The NetWare Access Server cannot be used to provide connectivity to AS/400 applications for remote users dialing into the network.

  • Wall Data's Rumba/400 can be used to access the AS/400 using PC Support from a Windows workstation. It is available from Wall Data, Inc. and from IBM Corporation.

3270 Emulation

If you are not using IBM's PC Support program, you can still access AS/400 applications using 3270 emulation through the IBM AS/400 3270 Remote Attachment Feature. IBM 3278/79 (LU Type 2) display and IBM 3287 (LU Type 1) printer emulation is supported. Workstations in this configuration require the NetWare 3270 LAN Workstation for DOS, Windows, or Macintosh, or a third-party 3270 emulation product.

When connected to an AS/400 using the 3270 Remote Attachment feature, NetWare for SAA supports up to two profiles (host links) and up to 64 sessions per profile (a total of up to 128 sessions). The sessions can be any combination of display, printer, or Advanced Program-to-Program Communications (APPC) sessions. NetWare for SAA supports Synchronous Data Link Control (SDLC) and Token Ring connections to the AS/400.


Note: IBM AS/400 Remote Attachment is normally a standard feature on AS/400s.

Performance Comparisons

Figure 3 shows the percentage of improvement in file transfer performance of a NetWare for SAA configuration compared to a NetWare SNA Gateway configuration. Both configurations included a COMPAQ 486L/33 MHz server using an NE2000 Ethernet LAN connection and a 4Mbps Token Ring connection to an IBM 9370 host using an IBM 16/4 Token Ring Adapter.

In addition, the following items apply to both configurations:

  • Files were sent using the SEND.EXE program, included with the NetWare 3270 LAN Workstation for DOS product

  • IBM's IND$FILE was used on a 9370 running the VM/CMS operating system

Figure 3: File transfer performance improves between 30 and 45 percent with NetWare for SAA.

Integrated vs. Dedicated Server CPU Utilization

Figure 4 shows the CPU utilization measured during NetWare for SAA testing at Novell. This data can be used in your NetWare for SAA configuration planning when you consider whether to install NetWare for SAA on an existing NetWare v3.11 server or on a server dedicated to NetWare for SAA.

The data in Figure 4 is a measure of CPU utilization on a server dedicated to NetWare for SAA. This CPU utilization will be incremental to the CPU utilization you are currently experiencing on your NetWare server.

The data was measured using MONITOR.NLM. To get accurate information, use the "-p" parameter, as follows:

  1. Enter the following command at the NetWare system console prompt (:):

    load monitor -p

  2. Start CSCON.

  3. Select "Processor Utilization" from the "Available Options" menu.

  4. Press <F3<. The NetWare for SAA CPU utilization number is listed under "SNAP."


Note: Because SAAStatus is constantly updated, it may place additional overhead on theCPU. The CPU utilization data shown in Figure 4 was measured whileSAAStatus was inactive.

Figure 4: CPU utilization test results for the COMPAQ 486 SystemPro server.

Number of Workstations

16

32

64

80

128

253

506

Number of LUs

16

32

64

80

128

253

506

Maximum CPU Utilization

5.5%

5.6%

5.8%

6.0%

7.0%

11.6%

15.3%

System Memory Requirements

The following paragraphs contain system memory requirements when running NetWare for SAA with NetWare v3.11 in a dedicated or integrated configuration.

Dedicated NetWare for SAA Server

If you are using NetWare Runtime v3.11, which ships with NetWare for SAA, the minimum system memory requirement is 6MB. The table below shows the recommended memory size for the number of NetWare for SAA sessions you plan to run.


Sessions

Memory Required

16

6 MB

64

8 MB

80

8 MB

128

10 MB

253

12 MB

506

16 MB

Integrated NetWare for SAA Server

If you are using NetWare v3.11 in an integrated configuration, use the following steps to determine the minimum memory requirements for running NetWare for SAA:

  1. Calculate the memory requirement for each volume.

    For each DOS volume: M = .023 X VOLUME SIZE (in MB) / BLOCK SIZE (default is 4)

    For each volume with added Name Space: M = .032 X VOLUME SIZE (in MB) / BLOCK SIZE (default is 4)

  2. Add memory requirements for all volumes:

    TOTAL VOLUME MEMORY = Msys + Mvol1 + Mvol2

  3. Add 2MB for the operating system and round the value to the next higher integer. If the total is under 3MB, use 4MB for your NetWare v3.11 memory requirement.

  4. Add 4MB to the value determined in Step 3 to run NetWare for SAA. In addition, add 20KB for each session, and round up to the nearest megabyte value. For example, to get the value for Step 4 for 64 sessions:

    • Multiply 20KB x 64 sessions to get 1.28MB

    • Round 1.28MB up to the nearest megabyte to get 2MB

    • Add 4MB to 2MB to get a total of 6MB for Step 4.

Adjusting the Size of Memory Pools

NetWare's SET MAXIMUM ALLOC SHORT TERM MEMORY parameter controls the amount of memory the operating system can allocate to the Alloc Short Term Memory pool. This pool stores information such as service request buffers and user connection information.

When running NetWare for SAA, you normally do not need to increase the Alloc Short Term Memory pool beyond the 2MB default. But in an environment with a lot of communication activity, set the memory pool to 3MB to start with. If you see warning messages from the server indicating that the Alloc Short Term Memory pool has reached its limit, increase in increments of 1MB. This parameter can support values up to 16MB.

As you increase the Alloc Short Term Memory pool, you may notice shortages in other memory pools such as cache buffers. If these shortages occur, you will need to increase physical system memory as well. Use the NetWare v3.11 MONITOR.NLM program to view the amount of memory allocated to the Alloc Short Term Memory pool.

System Volume Space Requirements

Running NetWare for SAA with the NetWare Runtime v3.11 requires a minimum of 20MB of free system volume space for the NetWare v3.11 operating system files and NetWare for SAA files. Running NetWare for SAA with NetWare v3.11 in an integrated configuration requires 10MB of free system volume space for the NetWare for SAA files, in addition to the space required for NetWare v3.11.


Note: The system log file must be deleted periodically or the file willgrow and use up the disk space. Likewise, the audit trail filesmust be archived onto floppy disks periodically and then deletedfrom the hard disk, or these files will use up the disk space.To delete these files, use the DOS DELETE command.

Server Hardware Recommendations

NetWare for SAA requires a server platform with certain characteristics. Each server must have the following:

  • At least 6MB of RAM

  • An 80386 or 80486 processor

NetWare for SAA should operate on any NetWare v3.11 server platform tested and approved by Novell's Independent Manufacturer Support Program (IMSP). The greater the processor speed, the better the performance. Below is a list of recommended processor speeds:


For 16 to 64 sessions

20 MHz or greater

For 64 to 254 sessions

25 MHz or greater

For 254 to 506 sessions

33 MHz or greater

The following is a list of systems that were tested in-house and passed successfully:

  • ALR PowerCache 486/25

  • COMPAQ DeskPro 386/20

  • COMPAQ DeskPro 386/20e

  • COMPAQ DeskPro 386/25

  • COMPAQ DeskPro 386/25e

  • COMPAQ SystemPro 386/33

  • COMPAQ 486/33 L

  • IBM PS/2 70 386

  • IBM PS/2 70 486

  • IBM PS/2 80-071

  • IBM PS/2 80-111

  • IBM Model PS/2 95

LAN Interface Cards

Any network interface card tested and approved by IMSP for NetWare v3.11 should operate as a LAN card when running NetWare for SAA.


Note: The Token Ring connection to the host requires one of the IBMadapters referenced in "Using a Token Ring Host Link."

NetWare 3270 LAN Workstation Products

There are three NetWare 3270 LAN Workstation products to cover three of the five platforms supported by NetWare for SAA. These are the NetWare 3270 LAN Workstation for DOS, Windows, and Macintosh. For the other two platforms, UNIX and OS/2, third-party software supports NetWare for SAA.

NetWare 3270 LAN Workstation for DOS

For IBM Model 5 terminal support, your PC must have one of the following sets of adapters and monitors:

  • An EGA display adapter that supports 28-row, 132-column display mode and a Sony MultiScan or compatible monitor. A compatible monitor's horizontal scan rate must be equivalent to the Sony MultiScan monitor's horizontal scan rate.

  • A VGA display adapter that supports 28-row, 132-column display mode and a Sony MultiScan monitor, a NEC MultiSync 3D monitor, or a monitor that is compatible with either of these monitors. A compatible monitor's horizontal scan rate must be equivalent to the horizontal scan rate of either of the above monitors.

  • Display adapters compatible with the monochrome UltraPAK or color EGA adapter made by Tseng Laboratories and any standard monitor. Compatible display adapters must support color video mode (hex 24) and/or monochrome video mode (hex 51).

Software Recommendations. The following is a list of operating systems and applications tested with NetWare 3270 LAN Workstation for DOS software.

  • DR DOS 5.0 or 6.0

  • IBM DOS 3.30 or 5.0

  • MS-DOS 3.30 or 5.0

  • IBM DisplayWrite 4 2.0

  • Lotus 1-2-3

  • Microsoft Word 5.0

  • NetWare 3270 File Transfer (included with NetWare 3270 LAN Workstation for DOS)

  • Spectrum Concept's XCOM 6.2 File Transfer

If you're not sure that your hardware or software is compatible, call Novell Product Information at 1-800-NETWARE for a current listing of compatible hardware and software.

Configuration Notes. If you run the above applications in graphics mode, you must configure the Display Adapter Memory for EGA/VGA Graphics under the DOS Session Options of the NetWare 3270 LAN Workstation for DOS software.

To restore the colors of a Lotus 1-2-3 graphics display after hot-keying back from a host session, enter "/s" to take you to a DOS prompt and then type "exit."

Connecting/ROOM from Helix Software can be used to reduce RAM consumption by the emulation software.

NetWare 3270 LAN Workstation for Windows

A workstation running NetWare 3270 LAN Workstation for Windows must be an Intel 80386- or 80486-based PC with at least 2MB of memory and a graphics adapter and monitor as required by Windows 3.0.

Be sure to use the NetWare shell drivers and the NetWare IPX drivers for Windows that are included with NetWare 3270 LAN Workstation for Windows.

Also be sure that the VNETWARE.386 and the VIPX.386 parameters are included on the NETWORK line in the [386enh] section of your SYSTEM.INI file, as shown below:

Network=*vnetbios, vnetware.386, vipx.386

Windows version 3.1 will be supported in a future update following the availability of Windows 3.1.

Rumba, from Wall Data, is available for Windows 3270 emulation to NetWare for SAA. Rumba/400, also from Wall Data, is available for Windows 5250 emulation to NetWare for SAA.

NetWare 3270 LAN Workstation for Macintosh

All Macintosh platforms (with at least 2MB of RAM) are supported. The following Macintosh keyboards are supported:

  • Standard

  • Extended

  • ISO layout (Standard and Extended)

  • Plus

  • Portable

The following 3270 keyboards are supported:

  • Standard

  • Enhanced

  • APL/APL2

Novell recommends the Macintosh operating system software version 6.0.3 and above, including System 7.

The following transport protocols are supported: AppleTalk Phase 1 and 2 network protocols and TokenTalk, EtherTalk and LocalTalk physical links. These protocols use the AppleTalk Data Stream Protocol (ADSP) to communicate with NetWare for SAA, ensuring that all client-to-server network traffic is reliably routed through the AppleTalk network.

The maximum number of Macintosh workstations that can simultaneously access NetWare for SAA is 200.

Emulation Solutions for Other Platforms

Rumba/PM, from Wall Data, is available for OS/2 3270 emulation to NetWare for SAA. LINKix 3270, from Cleo Communications, is available for UNIX 3270 emulation to NetWare for SAA.


Editor's Note:This AppNote is adapted from the NetWare for SAA v1.2 "Rules of Thumb" publication, part number 100-001240-001.

* Originally published in Novell AppNotes

Disclaimer

The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.

© Copyright Micro Focus or one of its affiliates