THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
This document can help you configure NetWare for SAA for optimal performance and reliability by identifying supported host connections and local area network (LAN) protocols. This booklet also provides AS/400 information, hardware and software recommendations, system memory requirements, and information on drivers. Because NetWare for SAA runs on NetWare 4.1 and NetWare 3.12, information specific to each operating system is identified where appropriate.
For the latest information regarding Novell Labs Product Certification of data link adapters and LAN adapters, systems, and drivers, contact Novell Labs through the FaxBack System at the following telephone numbers:
801-429-2776 (international and domestic)
800-414-5227 (domestic only)
The following topics are covered in this document
- Overview
- Server Connections
- AS/400 Connections
- Client Connections
- Server Hardware Requirements and Recommendations
- System Memory Requirements
- Recommended Drivers
- Calculating Integrated Server Memory Requirements
Overview
--------
NetWare for SAA is a set of NetWare Loadable Module applications that uses the NetWare 4.1 or NetWare 3.12 operating system. NetWare for SAA provides comprehensive integration between NetWare and IBM mainframes and AS/400 systems. Because NetWare for SAA runs on NetWare, it can run alongside file and print services on a single NetWare server.
This solution is ideal for a small branch office, because it eliminates the cost of a dedicated communications server and simplifies LAN maintenance and management. In large corporate LANs, NetWare for SAA can be installed to run on a server dedicated to communications (using NetWare Runtime software) to devote the server's full capability to NetWare for SAA.
New and Changed Features
------------------------
NetWare for SAA 2.0 includes a number of new and improved capabilities. In addition, NetWare for SAA provides NetWare integration, NetView support, convenient packaging, and license serialization.
Read the following brief descriptions to learn the general differences between NetWare for SAA 1.3 and NetWare for SAA 2.0.
- NetWare Directory Services (NDS) Support.
You can now take advantage of the naming aspect (long name support) of the NetWare 4.1 NDS distributed naming service. NDS allows a NetWare user to be anywhere in the Directory tree.
- MS Windows Based Configuration Option.
NetWare for SAA now comes with the NetWare for SAA Administrator, a Windows based configuration utility that you can use to configure all NetWare for SAA connections except peer connections and AS/400 connections.
- TN3270 Support
NetWare for SAA 2.0 supports the TELNET 3270 protocol through the NetWare TN3270 NLM, allowing workstations to access mainframe applications or services using standard tn3270 emulators through Transmission Control Protocol/Internetwork Protocol (TCP/IP).
- Bundled APPC APIs
Several Advanced Program-to-Program Communication (APPC) application programming interfaces (APIs) are shipped with NetWare for SAA 2.0. Included are APPC/PC APIs for DOS, MS Windows, and NetWare.
- CPI-C
NetWare for SAA 2.0 Common Programming Interface for Communications (CPI-C) is at 1.2 of the SAA CPI-C standard. Among the enhancements to previous versions of NetWare for SAA CPI-C support is support for non-locking verbs.
- LUx Support
NetWare for SAA 2.0 includes an integrated LUx dynamic link library (DLL) for MS Windows. This is in addition to the support that was available earlier on DOS and NetWare. Application developers can use Novell's LUx API to develop application programs that run on a DOS, MS Windows, or NetWare platform and communicate with host application programs that support the SNA logical unit (LU) types 0, 1, 2, and 3.
- Application Subsystem
In NetWare for SAA 1.3, APPC configuration information (such as addressing information for the partner LU) was collected at the client. NetWare for SAA 2.0 integrates the configuration of local LUs, partner LUs, modes, and transaction programs (TPs) into the Communication Services Configuration utility (CSCON). As a result, resources can be configured by a central operator and shared among client applications. Moreover, the CSStatus utility has been enhanced so that these resources can be controlled by a central operator.
- Attach Manager
In NetWare for SAA 1.3, CPI-C applications accepting incoming Attach messages had to be started by the operator. NetWare for SAA 2.0 provides an integrated Attach Manager that will start a configured local TP- a DOS or MS Windows application, or a NetWare NLM when an incoming Attach message is received.
- Multiple PU Profiles
NetWare for SAA 1.3 was limited to two service physical unit (PU) profiles. Two copies of NetWare for SAA were loaded into memory, supporting one profile each. NetWare for SAA 2.0 loads one copy of the product into memory, but up to 32 active PU profiles are supported. This number might be limited by the resources of your server.
- Common PU Profiles
NetWare for SAA 1.3 required you to configure either a PU2.0 profile for dependent sessions or a PU2.1 profile for independent sessions.
NetWare for SAA 2.0 provides both independent and dependent sessions from
the same profile to a VTAM host.
- Multiple Data Link Adapter Support
NetWare for SAA 1.3 supported only one adapter per profile. NetWare for SAA 2.0 supports as many data link adapters as can fit into your server. In addition, the Default Peer PU profile can access multiple data link adapters simultaneously for peer-to-peer connections.
- More Detailed Process and Interface
For NetWare for SAA 1.3, you configured everything in a service profile with a single step. For NetWare for SAA 2.0, the configuration process has been split into several steps: You configure adapters first, then PU profiles, and finally LU assignments and access control lists (ACLs).
- Enhanced LU Pooling Capability
In NetWare for SAA 1.3, LU pools had to contain LUs of the same type. LU pooling was done within a single PU profile. In NetWare for SAA 2.0, LU pool assignment can span Host PU profiles in a server. Mixed LU types and models can now be configured within a pool.
- Load Balancing
In NetWare for SAA 2.0, you can configure dynamic server based load balancing of dependent LUs across servers.
- Hot Standby Profiles
In NetWare for SAA 2.0, you can set up Host PU profiles on a Hot Standby server to go online automatically if a specified mission-critical server goes offline.
- Enhanced Downstream PU Configuration
In NetWare for SAA 1.3, downstream PUs had to be on the same physical media as the host system and the NetWare for SAA server. In NetWare for SAA 2.0, you can configure downstream PUs on a physical medium that's different from that of the host link. Downstream PUs are supported on token ring, Ethernet, Qualified Logical Link Control (QLLC), and custom links.
- Downstream LUs from Multiple Profiles
In NetWare for SAA 1.3, downstream LUs had to be assigned from the same PU profile. In NetWare for SAA 2.0, downstream LUs in a downstream PU can be assigned from multiple Host PU profiles.
- Licensing Flexibility
In NetWare for SAA 1.3, the sessions you purchased were built into the product. Installing or upgrading sessions required you to install or upgrade the entire NetWare for SAA product.
In NetWare for SAA 2.0, a licensing scheme has been developed so that sessions are no longer dependent on software installation. You can install additional licenses later, to upgrade servers on which NetWare for SAA 2.0 is already installed. You can increase licenses as required without removing previously installed licenses.
- Improved Online Documentation
In NetWare for SAA 1.3, the documentation was available in ElectroText format. For NetWare for SAA 2.0, the documentation is available in the improved DynaText format. The two formats are not interchangeable, but can coexist on the same system.
- Enhanced AS/400 Support
NetWare for SAA 2.0 contains many new features tailored specifically for users of IBM Client Access/400 (formerly IBM PC Support). These new features include the following:
| * Client router software included with NetWare for SAA 2.0. NetWare for SAA includes two router programs: the NetWare AS/400 Router for DOS and the NetSoft NS/Router for MS Windows. These programs support standard IBM Client Access/400 applications as well as other vendors' workstation applications for AS/400 system access.
| * TCP/IP and IPX/SPX support between workstations and servers.
| The NetWare AS/400 Router for DOS and the NetSoft NS/Router for MS Windows can use either TCP/IP or Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX) protocol to connect workstations to NetWare for SAA servers.
| * Connections to multiple SAA servers from a single client.
| With NetWare for SAA 2.0, IBM Client Access/400 users are no longer limited to connecting to a single server, but can now connect to multiple servers simultaneously.
| * Connections to AS/400 systems from multiple data link adapters.
| IBM Client Access/400 users can connect to an AS/400 system through all data link adapters for a given NetWare for SAA server.
Previous releases of NetWare for SAA required users to specify a PU profile name when loading AS400PCS.NLM. Specifying a single PU profile name limited workstation users to the data link adapter associated with the PU
profile. As a result, IBM Client Access/400 users could establish a connection only to AS/400 systems that were reachable through the single data link adapter.
With NetWare for SAA 2.0, users do not need to specify a PU profile name
when loading AS400PCS.NLM. AS400PCS.NLM always uses the Default
Peer PU profile, which can access all in-service data link adapters.
| * Server-based centralized configuration.
| With NetWare for SAA 2.0, you can define the AS/400 system information on the server using CSCON.
| Once an AS/400 system is defined on a server, you can define a symbolic AS/400 system name to be used by all workstations. With this feature, you can modify or update AS/400 system information by making the changes on the NetWare for SAA server. You do not need to update configuration information on each workstation.
| * Interactive client configuration utility. NetWare for SAA 2.0 includes a DOS based client configuration utility, CFGNRTR.EXE, that you can use to configure the NetWare AS/400 Router for DOS.
| * Enhanced LU6.2 status information. With an improved status display and control facilities, users can monitor and manage all active sessions and conversations to a specific local LU.
| * Increased NetWare Security. NetWare for SAA 2.0 allows the network
administrator to limit the access of NetWare users and define the number of sessions a user is allowed.
Packaging
---------
NetWare for SAA is sold by number of host sessions. You can buy a version with 16, 64, 128, 254, 508, or 1016 sessions. With each version you get the number of dependent sessions and an equal number of independent conversations. For example, when you buy a 64 session version, you
get 64 dependent sessions and 64 independent conversations.
You can combine any number of NetWare for SAA packages to increase the number of sessions. If you are running multiple Host PU profiles, you can divide the total number of sessions among the Host PU profiles equally or unequally. Licenses are not tied to a specific Host PU profile.
Server Connections
------------------
NetWare for SAA 2.0 can connect to a variety of upstream hosts or peers.
Integrated or Dedicated Configuration. The NetWare for SAA server can be configured for integrated or dedicated services. An integrated configuration uses the multiuser version of NetWare. A dedicated configuration uses the limited-user NetWare Runtime version, which comes bundled with NetWare for SAA.
Server connections include hosts, peers, and AS/400 systems. A host connection is a connection from NetWare for SAA to a host, through which the host views the NetWare for SAA server as either a node type 2.0 or 2.1 PU. A peer connection is a connection to any device that recognizes a NetWare for SAA server as a node type 2.1. A PU node type 2.1 node can establish sessions with other PU2.1 nodes without the mediation of a system services control point (SSCP).
NetWare for SAA 2.0 supports token ring, Ethernet, Synchronous Data Link Control (SDLC), QLLC (X.25), and custom data link host and peer connections. An AS/400 connection is a type of peer connection.
Host Connections
----------------
NetWare for SAA can support multiple concurrent host connections to the same host or to different hosts from a single NetWare for SAA server. If you are connecting to different hosts, those hosts need not be the same type. For example, you can have one connection to an AS/400 system and another connection to a mainframe.
If you have multiple hosts, the connections to the hosts can be of the same link type for example, two token ring host connections. The connections can also be of different types for example, one SDLC and one token ring host connection.
You can configure NetWare for SAA host connections as follows:
- Indirectly, through 317x cluster controllers and 37x5 front-end processors.
- Directly through a channel-attached data link to a System/370 mainframe
without the intervention of a front-end processor or cluster controller.
- Directly to 9370 systems and IBM OS/2 SNA Gateways.
- Directly to an AS/400 system being used as a host system. NetWare for SAA can also connect directly to an AS/400 system being used as a peer system. The most popular solution is the use of IBM Client Access/400 (formerly IBM PC Support), discussed under "AS/400 Connections" below.
NetWare for SAA supports up to 2000 dependent concurrent mainframe host sessions from a single server. The sessions can be any combination of display, printer, or APPC sessions.
Using a Token Ring Host Link
NetWare for SAA can connect through a token ring host link to a 3172 controller, a 3174 controller, a 37xx communications processor, a 9370 host processor, or an AS/400 system. Any token ring adapter compliant with version 4.1 of the Open Data-Link Interface (ODI) architecture and tested by Novell Labs can be used.
In a high traffic environment, Novell recommends using more than one adapter in your NetWare for SAA server. Install a token ring adapter to handle the LAN traffic and another adapter for each host connection. NetWare for SAA can run with a single adapter for both the LAN and the host, but separating the LAN and host traffic provides optimal performance.
Using an Ethernet Host Link.
NetWare for SAA can connect through an Ethernet host link to a 3172 controller, a 37xx communications processor, a 9370 host processor, or an AS/400 system.
Any ODI 4.1-compliant Ethernet adapter tested by Novell Labs can be used.
In a high traffic environment, Novell recommends using more than one adapter in your NetWare for SAA server. Install an Ethernet adapter to handle the LAN traffic and another adapter for each host connection. NetWare for SAA can run with a single adapter for both the LAN and the host, but the one-adapter-per-connection configuration provides optimal
performance.
Using an SDLC Host Link
NetWare for SAA can connect through an SDLC host link to a 37xx communications processor, a 9370 host processor, or an AS/400 system. You can connect to two hosts with either one or two adapters installed.
Using a QLLC/X.25 Host Link
NetWare for SAA can connect through a QLLC host link to an X.25 network. The required call support layer (CSL) software is bundled with NetWare for SAA.
Using a Channel-Attached Host Link
NetWare for SAA can connect through a channel-attached data link to a mainframe computer.
Backward Compatibility with NetWare for SAA 1.3B
------------------------------------------------
Your configuration database is converted automatically to the new configuration database format when you install NetWare for SAA 2.0. The NetWare for SAA 2.0 conversion utility attempts to convert the existing configuration database so that all connections continue to work with NetWare for SAA 2.0.
Peer Connections
----------------
A peer connection is a connection to another PU2.1 node. A PU type 2.1 node can establish sessions with other PU2.1 nodes without the mediation of an SSCP. Using the Default Peer PU profile or a Peer PU profile, a NetWare for SAA server can connect to any of the following peers: another NetWare for SAA server, an IBM OS/2 Gateway, an AS/400 system using IBM Client
Access/400 (formerly IBM PC Support), an IBM 37xx communications controller, and an IBM 317x cluster controller.
NetWare for SAA supports up to 2000 concurrent independent user sessions from a single server to different peer nodes. If you are using a client- based LU6.2 application, you will need to upgrade your LU6.2 client software supplied by Novell to the latest version that is included with NetWare for SAA 2.0.
Backward Compatibility with NetWare for SAA 1.3B
------------------------------------------------
Your server configuration database is converted automatically to the new configuration database format when you install NetWare for SAA 2.0. For client-based LU6.2 applications, an additional conversion utility is provided to convert the client-based configuration database.
This client utility must be run by an administrator or user for each desktop running an LU6.2 application. The NetWare for SAA 2.0 conversion utility attempts to convert the existing configuration database so that all connections continue to work with NetWare for SAA 2.0.
AS/400 Connections
------------------
An AS/400 connection is a peer connection between the NetWare for SAA server and an AS/400 system that supports IBM Client Access/400, IBM PC Support, or LU6.2 based 5250 emulators.
NetWare for SAA supports up to 2000 sessions to an AS/400 system.
Connecting to an AS/400 System
NetWare for SAA 2.0 can improve AS/400 connectivity because it provides:
- A Single Transport Protocol. By enabling the NetWare AS/400 Router for DOS and NetSoft NS/Router for MS Windows to communicate over IPX/SPX and TCP/IP protocols, the NetWare shell can now run side by side with IBM Client Access/400 applications. This feature eliminates the need for the IBM LAN Support program.
- Connectivity for Remote LAN Workstations to an AS/400. NetWare for SAA allows access to the AS/400 by NetWare clients over multiple router connections, and by remote users with NetWare Connect. The IBM Client Access/400 router requires source routing bridges and does not support Novell IPX routers.
- Support for a Variety of Topologies and LAN Adapters. NetWare for SAA supports token ring, ARCnet, and Ethernet topologies, and all adapters tested by Novell Labs. IBM supports only IBM token ring adapters and a few Network Driver Interface Specification (NDIS) Ethernet adapters.
- Reduced Workstation Memory Requirements. The NetWare AS/400 Router
for DOS uses about 7KB of RAM, whereas the IBM Router can use as much as 60KB. In addition, NDIS Ethernet drivers require considerable memory.
NetWare for SAA supports token ring, Ethernet, SDLC, QLLC, and custom connections to the AS/400. Over token ring and Ethernet lines, NetWare for SAA can connect to up to 128 AS/400 systems that are accessible to each IBM Client Access/400 client. Using Advanced Peer-to-Peer Networking (APPN), NetWare for SAA can access up to 253 AS/400 systems simultaneously.
Individual Client Access/400 users can simultaneously access up to 32 AS/400 systems.
IMPORTANT: When planning your network, you must calculate the number of sessions each IBM Client Access/400 user will need. Generally, each active IBM Client Access/400 application on a workstation takes one session. For example, starting shared folders initiates one session. If you also bring up two 5250\x110011 emulation sessions using the Client Access/400
Workstation Function (WSF), you initiate two more sessions. In this case, you would need three active LU6.2 sessions.
AS/400 and Client Access/400
IBM Client Access/400 consists of many programs working together to provide a variety of AS/400 system functions on your workstation. The programs communicate with one another through a router program that does the following:
- Establishes a connection between your workstation and the AS/400 system
- Serves as an interpreter between IBM Client Access/400 programs running on the workstation and those running on the AS/400 system
Recommended Routers. NetWare for SAA 2.0 provides the NetWare AS/400 Router for DOS for use in DOS environments, and the NetSoft NS/Router for AS/400 for use in MS Windows environments.
Novell recommends that you use the NetSoft NS/Router for AS/400 if
- You want connectivity between MS Windows and an AS/400 system
- You are using IBM Client Access/400 for MS Windows version 3.1
- You are using a third-party emulator and/or applications that support the extended version of the IBM Client Access/400 EHNAPPC DLL
Novell recommends using the NetWare AS/400 Router for DOS if
- You are using a DOS workstation for AS/400 connectivity
- You use the DOS or extended DOS version of IBM Client Access/400
Backward Compatibility with NetWare for SAA 1.3B
------------------------------------------------
If you used IBM PC Support with NetWare for SAA 1.3B and upgrade to NetWare for SAA 2.0, your configuration database is converted automatically to the new configuration database format when you install NetWare for SAA 2.0. The NetWare for SAA 2.0 conversion utility attempts to convert the existing configuration database so that all connections continue to work with NetWare for SAA 2.0.
The conversion utility does not create server database records that take advantage of the server based centralized configuration capability, however. Therefore, Novell strongly recommends that you define AS/400 system information on the server after you install NetWare for SAA 2.0
so that you can take advantage of this capability.
You will also need to install the latest version of the NetWare AS/400 Router for DOS, or the NetSoft NS/Router for MS Windows on each IBM Client Access/400 and IBM PC Support desktop accessing the AS/400.
Client Connections
------------------
Workstations can access the NetWare for SAA server using any of the LAN topologies supported by NetWare: ARCnet, Ethernet, token ring, LocalTalk, TokenTalk, and EtherTalk.
NetWare for SAA supports the IPX/SPX, TCP/IP, and AppleTalk protocols. NetWare for SAA can be accessed from workstations located anywhere on an enterprise network composed of multiple interconnected LANs.
For downstream PUs, NetWare for SAA supports the SNA protocol.
3270 Workstation Client Options
-------------------------------
NetWare for SAA supports numerous 3270 emulators that run on the five major desktop platforms: DOS, MS Windows, Macintosh, OS/2, and UNIX.
The 3270 emulation applications use either IPX/SPX, AppleTalk, or TCP/IP protocols to communicate with NetWare for SAA and provide the display and keyboard portions of 3270 emulation. All the protocol processing associated with the host connection is managed by NetWare for SAA on the NetWare server.
The 3270 software provides 3270 terminal and printing emulation for a workstation to a host.
This connection is established through NetWare for SAA. For more information on 3270 workstation client support and on third-party product features and compatibility, refer to the NetWare for SAA Solutions Guide.
NetWare TN3270
--------------
The NetWare TN3270 server NLM included with NetWare for SAA enables workstations running tn3270 client software on a TCP/IP network to use NetWare for SAA to establish host sessions.
NetWare for SAA communicates with the client using the tn3270 and the TELNET protocols over a TCP/IP session. The NetWare for SAA server uses standard SNA protocols to communicate with the host. No tn3270 software, TELNET software, or TCP/IP software is required on the host for NetWare for SAA to support tn3270 clients.
Downstream PU Connections
-------------------------
Downstream PUs can be connected and configured because of the NetWare for SAA 2.0 PU concentrator feature, which provides service for downstream PUs. In this configuration, the downstream PU looks like a PU2.0 to the NetWare for SAA server but like a set of LUs to a host. NetWare for SAA provides a host connection and LU allocation on behalf
of the downstream PU.
NetWare for SAA can support up to 2000 downstream PUs per server on a token ring or Ethernet network, and up to 32 downstream PUs per server on a QLLC/X.25 network. The downstream PUs can be IBM AS/400 systems, IBM OS/2 SNA Gateways, IBM OS/2 Communications Manager clients, other NetWare for SAA 1.3 and 2.0 servers, or IBM 317x cluster controllers.
Server Hardware Requirements and Recommendations
------------------------------------------------
Select hardware for a NetWare for SAA server according to the environment in which you plan to run it:
- On the NetWare 4.1 or NetWare 3.12 platform
- In a dedicated or integrated configuration
The following sections recommend hardware and memory configurations.
For the latest information regarding Novell Labs Product Certification of data link adapters, LAN adapters, systems and drivers, contact Novell Labs through the FaxBack System, or contact the vendor.
Requirements and Recommendations NetWare 4.1 Platform
NetWare for SAA running on a 4.1 platform requires the following:
- At least 16 MB of RAM.
- A 386, 486, or Pentium processor. NetWare for SAA should operate on any NetWare server platform tested and approved by Novell Labs.
The greater the processor speed, the better your server performs. Below is a list of processor speeds recommended to improve performance for the following number of sessions:
- For 16 to 64 sessions 25MHz or greater
- For 64 to 128 sessions 33MHz or greater
- For 128 to 508 sessions 50MHz or greater
- For 508 and above sessions 66MHz or greater 486 or Pentium processor
Requirements and Recommendations - NetWare 3.12 Platform
NetWare for SAA running on a NetWare 3.12 platform requires the following:
- At least 10 MB of RAM.
- A 386, 486, or Pentium processor. NetWare for SAA should operate on any NetWare server platform tested and approved by Novell Labs.
The greater the processor speed, the better your server performs. Below is a list of processor speeds recommended to improve performance for the following number of sessions:
- For 16 to 64 sessions 20 Mhz or greater
- For 64 to 128 sessions 25 Mhz or greater
- For 128 to 254 sessions 33 MHz or greater
- For 254 to 508 sessions 50 MHz or greater
- For 508 and above sessions 66MHz or greater 486 or Pentium processor
System Memory Requirements
--------------------------
NetWare for SAA 2.0 supports up to 2000 sessions in both the NetWare 4.1 and NetWare 3.12 environments. However, memory constraints and connection types may limit the actual number of connections supported.
The following sections identify the amount of system memory required for running NetWare for SAA 2.0 with NetWare in a dedicated or integrated configuration. In addition to the memory requirements given in this section, there are several rules of thumb to follow:
- Number of Host Links. Adding additional host links increases the amount of memory required for buffering. The amount required depends on the type and speed of the host links you are using.
- Host Link Speed. A slower host link, such as an SDLC dial-up link, requires additional memory for buffering. Again, the amount of memory required depends on the type and speed of the host link.
- Processor Speed. The slower the processor speed of the server, the more memory is required for buffering.
- Host Speed. A slower host requires additional memory on the server for buffering.
Dedicated Server Memory Requirements NetWare 4.1 Platform
If you are using NetWare Runtime, which is shipped with NetWare for SAA, the minimum system memory requirement is 16 MB.
The following table shows the minimum memory required if you are using the default values for the number of NetWare for SAA sessions you plan to run. Minimum memory means the total system memory required for NetWare Runtime 4.1 and NetWare for SAA 2.0 running the listed number of sessions. These numbers were obtained from a traffic model of expected peak customer usage.
MINIMUM MEMORY REQUIREMENTS
Sessions 3270 TN3270 AS/400
-------- ---- ------ ------
16 16MB 18MB 18MB
32 16MB 18MB 18MB
64 17MB 19MB 19MB
80 17MB 19MB 19MB
128 18MB 20MB 20MB
254 20MB 22MB 22MB
508 25MB 26MB 28MB
1016 36MB 33MB 38MB
2000 56MB 49MB -
This memory information was obtained in Novell's test laboratory on the following host-and-server configuration. Your configuration may be different.
Tested SERVER Configuration Information NetWare 4.1 Platform
System: COMPAQ DESKPRO 486/66M
Host Link Adapter: NTR2000 IBM Token Ring 16/4 (8 bit)
Tested Host Configuration Information NetWare 4.1 Platform
Host Link Speed: 16 MB
Response/Request Unit Size: 4096
Data Size: LU type 2 Model 2 Screen, 1920 bytes (Data is sent to each client.)
Dedicated Server Memory Requirements - NetWare 3.12 Platform
Important 3270 Client Information. The number of 3270 sessions you are able to run with NetWare for SAA 2.0 on NetWare 3.12 depends upon the 32-MB NetWare server memory, the SPX connection configuration, and your 3270 emulator package.
The maximum amount of short-term memory allocation is limited to 32 MB on NetWare 3.12.
If your emulator supports 1 LU per SPX session, then your server is limited to 1500 SPX connections. You should contact your 3270 emulator vendor to identify the number of sessions supported per SPX connection. By supporting multiple sessions per SPX connection, you can increase the total number of NetWare for SAA sessions supported.
The total number of SPX connections that can be supported on NetWare 3.12 is configured with SPXCONFG.NLM. The default number is 1000 SPX connections. If the number of SPX connections ever reaches this maximum, then all NetWare for SAA sessions over SPX will drop and no new SPX sessions can be started. If you experience this condition, you can do either of the following:
- Load SPXCONFG.NLM and increase the maximum number of SPX connections
to 2000 (NetWare 3.12 maximum support).
- Upgrade to NetWare 4.1.
Minimum Memory Required. If you are using NetWare Runtime 3.12, which is shipped with NetWare for SAA, the minimum system memory requirement is 10 MB.
The following table shows the minimum memory required if you are using the default values for the number of NetWare for SAA sessions you plan to run (assuming one SPXS connection per session). Minimum memory means the total system memory required for NetWare Runtime 3.12 and NetWare for SAA 2.0 running the listed number of sessions.
These numbers were obtained from a traffic model of expected peak customer usage.
Minimum Memory Requirements
Sessions 3270 TN3270 AS/400
16 10MB 12MB 12MB
32 10MB 12MB 12MB
64 11MB 12MB 13MB
80 11MB 12MB 13MB
128 12MB 13MB 14MB
254 16MB 14MB 17MB
508 20MB 17MB 22MB
1016 30MB 22MB 32MB
1500 32MB - -
2000 - 32MB -
This memory information was obtained in Novell's test laboratory on the following host-and-server configuration. Your configuration may be different.
Tested SERVER Configuration Information NetWare 3.12 Platform
System: COMPAQ DESKPRO 486/33M
Host Link Adapter: IBM Token Ring 16/4 (8 bit), NTR2000
Tested HOST Configuration Information NetWare 3.12 Platform
Host Link Speed: 16MB
Response/Request Unit Size: 4096
Data Size: LU type 2 Model 2 Screen, 1920 bytes (Data is sent to each client.)
Integrated Server Memory Requirements
-------------------------------------
Summary of Calculations
Below is a summary of memory requirements for NetWare for SAA 2.0 based upon a sampling of tests. The numbers may vary according to your environment. Use the procedure provided under "Calculating Integrated Server Memory Requirements" below, to determine the amount of memory required for your environment.
- Base memory required for NetWare for SAA running under NetWare 4.1:
| * NetWare 4.1 base = 12 MB
| * NetWare for SAA base = 3 MB
| * NetWare 4.1 + NetWare for SAA = 15 MB base memory required
- Session memory required under NetWare 4.1:
| * SPX session for 3270 = 20 KB
| * NetWare TN3270 session for tn3270 = 16 KB
| * AS/400 client session = 20 KB
- Base memory required for NetWare for SAA running under NetWare 3.12:
| * NetWare 3.12 base = 6 MB
| * NetWare for SAA base = 3 MB
| * NetWare 3.12 + NetWare for SAA = 9 MB base memory required
- Session memory required under NetWare 3.12:
| * SPX session for 3270 = 20 KB
| * NetWare TN3270 session for tn3270 = 10 KB
| * AS/400 client session = 20 KB
The SPX connections and LU types configured and the third-party emulators used will vary the memory requirement per session from 7 KB to 20 KB. The more SPX connections used, the more memory your server will require.
Using the REGISTER Command with NetWare 4.1 Memory in ISA Computers
Use the following NetWare REGISTER command if your server uses the Industry Standard Architecture (ISA) bus and the NetWare 4.1 operating system does not recognize installed memory above 16 MB:
REGISTER MEMORY START ADDRESS LENGTH
To have the memory registered automatically when the NetWare server is started, add this command to AUTOEXEC.NCF, just after the lines for NetWare server name and the IPX internal network number. For additional detailed information, review the NetWare 4.1 Utilities Reference.
Adjusting the Size of Memory Pools for NetWare 3.12
The NetWare 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. The NetWare SET MAXIMUM ALLOC SHORT TERM MEMORY parameter can support values up to 32 MB. The default is 2 MB, but if your server runs in an environment with high communication activity, set the memory pool to 3 MB to start with. If you receive system warning messages from the server indicating that the Alloc Short Term Memory pool has reached its limit, increase the parameter in increments of 1 MB.
Increasing Other Memory Pools for NetWare 3.12
----------------------------------------------
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 must increase physical system memory as well. Use the NetWare MONITOR.NLM program to view the amount of memory allocated to the Alloc Short Term Memory pool.
System Volume Space Requirements
On a NetWare 4.1 Platform
Running NetWare for SAA with NetWare Runtime 4.1 requires a minimum of 120 MB of free system volume space for NetWare operating system files and NetWare for SAA files.
Running NetWare for SAA with NetWare 4.1 in an integrated configuration requires 20 MB of free system volume space for the NetWare for SAA files in addition to the space required for NetWare.
On a NetWare 3.12 Platform
Running NetWare for SAA with NetWare Runtime 3.12 requires a minimum of 40 MB of free system volume space for NetWare operating system files and NetWare for SAA files.
Running NetWare for SAA with NetWare 3.12 in an integrated configuration requires 20 MB of free system volume space for the NetWare for SAA files in addition to the space required for NetWare.
For Upgrading to NetWare 4.1
----------------------------
If you are running NetWare for SAA on a NetWare 3.12 server and are planning to upgrade to NetWare 4.1, a minimum of 85 MB of free system volume space is required. This is because NetWare does not first delete some of the old public files before installing NetWare 4.1.
For DynaText and CBT Files
--------------------------
If you will be installing the DynaText online versions of NetWare or NetWare for SAA manuals or the NetWare computer based training (CBT) files, the following free system volume space is required in addition to that required for the software files:
- NetWare 4.1 DynaText 50MB
- NetWare 3.12 DynaText 33MB
- NetWare for SAA 2.0 DynaText 12MB
- NetWare 4.1 CBT 4MB
- DynaText software 6MB
RECOMMENDED DRIVERS
-------------------
Warning: Use of an incompatible driver may cause problems and loss of connections to the server.
Many drivers are bundled with NetWare for SAA for your convenience. All drivers provided with NetWare for SAA are compliant with version 4.1 of the ODI architecture. If you are using a driver that is not bundled with NetWare for SAA 2.0, make sure that it is ODI 4.1 compliant before installing NetWare for SAA 2.0.
Important: Problems can occur if you do not use ODI-4.1 compliant drivers.
For the latest information regarding Novell Labs product certification of data link adapters and LAN adapters, systems, and drivers, contact Novell Labs through the FaxBack System or contact the vendor. You may have to upgrade your LAN driver before installing NetWare for SAA 2.0.
Token Ring Drivers
- IBM Token Ring 16/4 Adapter
- Novell Token Ring NTR2000 Adapter
Ethernet Drivers
- Novell NE1000 Adapter
- Novell NE2000 Adapter
- Novell NE/2 Adapter
- Novell NE3200 Adapter
- Novell NE/2-32 Adapter
Synchronous Data Link Control (SDLC) Drivers
- IBM Multiprotocol Adapter
- Microdyne Synchronous EXOS Adapter
- Microdyne Synchronous/V.35 EXOS Adapter
- Microdyne NetWare for SAA Synchronous Adapter for PC
- Microdyne NetWare for SAA Synchronous Adapter for PS/2
LAN Drivers
NetWare for SAA 2.0 updates your NetWare 3.12 system with the new ODI 4.1 compliant drivers.
X.25 WAN Drivers
NetWare for SAA 2.0 requires an X.25 wide area network (WAN) driver that is compatible with the new call support layer (CSL) NLM provided in NetWare for SAA 2.0. If you are upgrading from previous versions of NetWare for SAA, you will need to use a driver that is compatible with the new CSL.NLM, such as the SYNCPLUS.LAN driver provided in NetWare for SAA 2.0.
Calculating Integrated Server Memory Requirements
If you are using NetWare 4.1 or NetWare 3.12 in an integrated configuration (standard NetWare, not NetWare Runtime), follow these steps to determine the minimum memory requirements for running NetWare for SAA.
STEP 1: Calculate the following seven variables (V1 through V7).
V1. Enter the total number of megabytes of disk connected to _______MB
the server. (For example, enter 1 for each megabyte, and enter 1024 for each gigabyte.)
V2. Calculate the number of megabytes of usable disk space _______MB
connected to the server. (If you are mirroring or duplexing, multiply V1 X 0.5. Otherwise, copy V1.)
V3. Enter the server's volume block size (4, 8, 16, 32, or 64). _______KB
V4. Calculate the number of disk blocks per megabyte.
(Divide 1024 /V3.) _______Blocks/MB
V5. Calculate the total number of disk blocks.
(Multiply V2 X V4.) _______Blocks
V6. Enter the maximum number of clients (users) attached _______Clients
to the server (For example, enter 24 for 24 users.)
V7. If suballocation is enabled, enter the maximum number _______Files
of files that will reside on the server.
STEP 2: Calculate your individual memory requirements.
Line 1. Enter the base memory requirement for the core _______KB
operating system. (Enter 5120 for NetWare 4.1, or 2048 for NetWare 3.12.)
Line 2. Calculate the memory requirement for Media Manager. _______KB
(Multiply V1 X 0.1.)
Line 3. If file compression is enabled, enter 250. Otherwise, _______KB
enter 0.
Line 4. If suballocation is enabled, calculate the required _______KB
memory. (Multiply V7 X 0.005.) Otherwise, enter 0.
Line 5. Calculate the memory required to cache the file _______KB
allocation table (FAT). (Multiply V5 X 0.008.)
Line 6. Calculate the memory requirement for file cache, using _______KB
the following table. (This calculation uses a memory requirement of 0.4 MB per client per cache. The value decreases as the user community increases and data is shared repetitively in time and space within a cache.) Then divide the result by 1024 for a result in kilobytes.
Fewer than 100 clients V6 X 400
Between 100 and 250 clients 40,000 + [(V6 - 100) X 200]
Between 250 and 500 clients 70,000 + [(V6 - 250) X 100]
Between 500 and 1000 clients 95,000 + [(V6 - 500) X 50]
Line 7. Enter the total memory (in kilobytes) required for support _______KB
NLMs. A total of 2,000 KB is recommended for Btrieve (700), CLIB (500), INSTALL (600), and PSERVER (200).
Line 8. Enter the total memory (in kilobytes) required for other _______KB
services. Other services include NetWare for Macintosh, OracleWare, NetWare Management System (NMS), and so on.
STEP 3: Calculate your total memory requirement.
Line 9. Total Lines 1 through 8 for your server memory _______KB
requirement (in kilobytes).
Line 10. Divide Line 9 by 1024 for a result in megabytes. _______MB
Using this result, round up to the server's nearest memory configuration. NetWare will enhance server performance by using all leftover memory for
additional file cache.
STEP 4: Calculate your NetWare for SAA server memory requirement.
Line 11. If Line 10 is less than 12 MB for NetWare 4.1, use 12 MB ______MB for your NetWare 4.1 memory requirement. If it is less than 6 MB for NetWare 3.12, use 6 MB.
Line 12. Add 3 MB to that total to run NetWare for SAA. _______MB
Line 13. Multiply the number of sessions you will be using by _______KB
the following number of kilobytes per session, depending on your configuration:
20 KB for NetWare 4.1 SPX sessions
16 KB for NetWare 4.1 TN3270 sessions
20 KB for NetWare 4.1 AS/400 sessions
20 KB for NetWare 3.12 SPX sessions
10 KB for NetWare 3.12 TN3270 sessions
20 KB for NetWare 3.12 AS/400 sessions.
Line 14. Round that total up to the nearest megabyte. _______MB
Line 15. Add the total from Line 12 to the total from Line 14 ______MB to get the total minimum memory required on the server for NetWare and your NetWare for SAA sessions.
Example 1 Determining the Memory Requirement for 64 SPX 3270 Sessions under NetWare 4.1
1. Use 12 MB for your NetWare memory requirement.
2. Add 3 MB to run NetWare for SAA to get a total of 15 MB.
3. Multiply 20 KB by 64 sessions to get 1.28 MB.
4. Round 1.28 MB up to get 2 MB.
5. Add 2 MB to 15 MB to get a total of 17 MB minimum memory required.
Example 2 Determining the Memory Requirement for 64 SPX 3270 Sessions under NetWare 3.12
1. Use 6 MB for your NetWare memory requirement.
2. Add 3 MB to run NetWare for SAA to get a total of 9 MB.
3. Multiply 20 KB by 64 sessions to get 1.28 MB.
4. Round 1.28 MB up to get 2 MB.
5. Add 2MB to 9MB to get a total of 11MB minimum memory required.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
