Filename:   README.TXT
Product:    NetWare(R) for SAA* 2.0
Date:       February 1995

=============================================================================
TCP/IP and TN3270 Interoperability Issues with NetWare 4.1
==========================================================
  If you are installing NetWare for SAA 2.0 on NetWare 4.1 and plan to use
  the TCP/IP protocol (such as NetWare for SAA TN3270) or a client emulator
  that supports TCP/IP, you must update CLIB.NLM by downloading the latest 
  updates from NetWire(R). The file you will need is SAATCP.TXT located in
  NOVLIB forum, library 9. SAATCP.TXT identifies the files you need to
  download.

=============================================================================
CONTENTS
========

1.0  Installation Notes
2.0  Diskette Organization
3.0  Operation Notes
4.0  Known Problems and Issues
5.0  Trademarks

=============================================================================
1.0  INSTALLATION NOTES
=======================

  This is the release of NetWare for SAA 2.0 to customers and third parties.

  ODI Driver Support
  ------------------
  NetWare for SAA 2.0 updates your NetWare 3.12 system with the new ODI(tm)
  compliant drivers. These drivers are located on Diskette 1 of the
  Communication Executive diskettes, under the SYSTEM.3X directory.
  
  If you are using Ethernet or token ring drivers that are not included in the
  updated drivers shipped with NetWare for SAA 2.0, do NOT install NetWare for
  SAA 2.0 on your server until you are certain that the driver used with the 
  LAN adapter has been tested and approved for use with NetWare 4.1. To verify
  that your driver has been certified for use with 4.1, either call the Novell
  Labs(tm) FaxBack System (see below) or contact the LAN adapter vendor. You
  may have to upgrade your LAN driver prior to installing NetWare for SAA 2.0. 
   
    WARNING: Failure to do so will cause compatibility problems and loss 
    of connections to the server.

  NetWare for SAA 2.0 installs the following drivers on NetWare 3.12 
  to support the new Media Support Module(tm) (MSM(tm)) and following
  Topology Specific Module(tm) (TSM(tm)) NLMs: 

  ETHERTSM    NLM     2.33
  MSM31X      NLM     2.32
  FDDITSM     NLM     2.33
  RXNETTSM    NLM     2.8      
  TOKENTSM    NLM     2.33          
  3C503       LAN     4.10
  E21N4X      LAN     1.22
  HP3AT16P    LAN     2.30
  MADGEODI    LAN     4.6
  NE1000(tm)  LAN     3.24
  NE1500T(tm) LAN     3.27
  NE/2(tm)    LAN     3.25
  NE2000(tm)  LAN     3.29            
  NE2100(tm)  LAN     3.27
  NE/2_32(tm) LAN     3.23
  NE3200(tm)  LAN     3.27          

  NI6510      LAN     5.70
  NTR2000(tm) LAN     3.33                
  SMC8000     LAN     6.2

  TCARCH      LAN     1.13
  TCE32MCH    LAN     1.43
  TCNSH       LAN     1.13
  TCTOKH      LAN     1.23     
  TOKEN       LAN     3.24                

  For the latest information regarding Novell Labs product certification,
  contact Novell Labs FaxBack System at the following telephone numbers:

  (801) 429-2776 - International and domestic
  (800) 414-5227 - Domestic only


  COMMEXEC Object Creation in the NetWare Directory Tree
  ------------------------------------------------------
  During the initial installation on a NetWare 4.1 server, a COMMEXEC object 
  is created in the Directory tree.  You will be prompted for the
  Administrator name and password so that this object can be created.  A help
  screen is available to assist you with this step (press <F1>).

  IBM* MPA Board Configuration
  ----------------------------
  The IBM MPA board can support two PUs on a half-duplex line. On a
  full-duplex line, only one PU is supported. This is a hardware limitation
  of the adapter.

  Novell(R) recommends that you configure the IBM MPA board so that it both uses
  and reserves interrupt 3 (int=3) for its use alone. Thus, other adapters
  installed on the same system should not use interrupt 3.

  License Installation
  --------------------
  License installation occurs once during the initial installation, but you
  can also install additional licenses later with the License Management
  utility (LICENSE.NLM).  Licensing is handled slightly differently in
  NetWare for SAA 2.0, because the licenses are independent of NetWare for
  SAA itself. The License Management utility is provided on the License 
  Diskette.

  NetSoft* NS/Router Support
  --------------------------
  NetSoft NS/Router files are packaged with the NetWare for SAA 2.0 product.
  The NetSoft/Router is a Microsoft* (MS*) Windows-based utility that
  provides AS/400* connectivity using either the IPX/SPX(tm) or TCP/IP 
  transport protocol with a third-party emulation package. NetSoft NS/Router
  supports the extended version of IBM AS/400 PC Support's ENHAPPC DLL. See
  the NetWare for SAA 2.0 Planning and Administration Guide for AS/400 for
  more information.

  QLLC/X.25 Adapter Configuration Information
  -------------------------------------------
  When using CSCON or NetWare for SAA Administrator to configure the
  QLLC/X.25 adapter information, note that the "Logical adapter name" must
  match the "Interface Name" configured in the Internetworking Configuration 
  utility (INETCFG)--not the "Board Name."

  Also note that the field "QLLC call support layer target name" in CSCON or
  NetWare for SAA Administrator must match INETCFG's "Call Destination" 
  field. The "Call Destination" field is case-sensitive. Be sure to match the
  case of this field when you enter the call support layer (CSL) target name
  in CSCON's Configure PU Profile panel.

  QLLC/X.25 Permanent Virtual Circuit Link Support
  ------------------------------------------------
  To support QLLC/X.25 Permanent Virtual Circuit (PVC) links on a VM/CMS 9370
  system, the host must be configured to retry QSM and QXID indefinitely.
  (The equivalents for QSM and QXID for SDLC links are SNRM and XID 
  respectively.)
 
  NetWare SNA Links(tm) Support
  -----------------------------
  If you are using NetWare SNA Links 1.0, you will need to upgrade
  your NetWare MultiProtocol Router product(tm) to 3.0.

=============================================================================
2.0 DISKETTE ORGANIZATION
=========================

  Although you may be receiving this release on CD-ROM, it is organized into 
  directories representing diskettes.  The diskette contents are outlined 
  below:

  COMMEXEC Diskette 1-        NetWare system files and drivers for 3.12 
                              support, and corresponding message files.

  COMMEXEC Diskette 2-        NetWare Btrieve(tm) system, public, and message
                              files.

  COMMEXEC Diskette 3-        NLM applications, including the Communication
                              Executive, plus related NLMs and their 
                              corresponding message files; database files and
                              License Management utility files, and NMACON
                              files.

  COMMEXEC Diskette 4-        CSCON and PRFCON files, corresponding message
                              files, MIB files, and NMS(tm) files.  
  
  COMMEXEC Diskette 5-        NetWare system files for NetWare 3.12 and 
                              NetWare 4.1 support; message files, NetWare 
                              TN3270, and NetWare MultiProtocol Router
                              support modules. 

  COMMEXEC Diskette 6-        AppleTalk(tm) files and system files.

  NWSAA Diskette    1-        Database files, NMS and conversion NLMs, and 
                              corresponding message files.

  NWSAA Diskette    2-        NetWare for SAA NLMs with corresponding message
                              files, trace files, and OS/2* configuration
                              files.

  NWSAA Diskette    3-        Files for CPI-C, APPC, and LUx on MS Windows.

  NWSAA Diskette    4-        Files for AS/400; files for CPI-C, APPC, and
                              LUx on DOS and NetWare; and message files.

  NWSAA Diskette    5-        SAACON and SAACOPY files.

  NWSAA Diskette    6-        MS Windows AS/400 connectivity utility files.
  NWSAA Diskette    7-        All README files that are distributed with the
                              product, including NetWare for SAA 2.0,
                              NetWare Appletlk.nlm 4.50b Update, NetWare
                              HostPrint(tm) Update for NetWare for SAA 2.0,
                              NetWare TN3270 for NetWare for SAA 2.0, 
                              NetWare for LAT* 1.0.01 Update, NetWare for
                              SAA 2.0 for NetWare Management System(tm),
                              NetWare for SAA Administrator 1.0, and NetWare
                              for SAA Services Manager 3.0.
  HostPrint 1.1 
  Update Diskette   1-        NetWare HostPrint modules for compatibility
                              with NetWare for SAA 2.0.
 
  ADMIN Diskette    1-        MS Windows NetWare for SAA Administrator files.

  NWSAA Services 
  Manager Diskette  1-        MS Windows NetWare for SAA Services Manager
                              files.

  NWLAT Diskette    1-        Updates for NetWare for LAT. 

  NWSAA LICENSE 
  Diskette          1-        A NetWare for SAA license diskette that 
                              contains your purchased licenses for dependent
                              and independent sessions. Insert this diskette
                              into your A: drive when prompted to do so by
                              the installation program. 
     

  NetWare Link/X.25(tm) 3.0 Support Diskettes
  -------------------------------------------
  If you plan to use QLLC support, install the following NetWare 
  Link/X.25 diskettes:
   
  LINKX25 Diskette  1-        Configuration and database files.

  LINKX25 Diskette  2-        WAN drivers, X.25 NLMs, media support modules,
                              and system files.


=============================================================================
3.0 OPERATION NOTES
===================

  Authentication Support
  ----------------------
  NetWare for SAA 2.0 utilizes NetWare Directory Services(tm) for
  authentication purposes.  Thus, if you are on a NetWare 4.1 server, you can
  log into the directory once and have access to multiple servers.  This
  feature requires the cooperation of the client emulator software. Contact
  your client emulator vendor concerning support for long names and NetWare
  Directory Services.

  Installing or Upgrading NetWare 
  -------------------------------
  If you have just installed or upgraded NetWare, you must restart the 
  server before installing NetWare for SAA so that the server can be fully
  initialized.

  Multiple PUs Running on the Same SDLC Link
  ------------------------------------------
  If you plan to run multiple PUs on the same SDLC link, you will need to set
  the "secondary inactivity timer value" according to your SDLC line
  condition. This will prevent a timeout occurrence on the line that would
  disconnect the link. The default timer value is 30 seconds.

  Usage: Load SDLCS.NLM /tx (where x is the timer value in seconds)

  NetSoft NS/Router Configuration File Parameter Modification
  -----------------------------------------------------------
  After installing the NetSoft NS/Router with the IBM Client Access/400* for
  MS Windows, double-click the icon "NS/Router Configurator" to create and 
  save a user-defined configuration file. After saving the file you need to
  modify a parameter value in that file with an ASCII-type editor.

  Search for the heading [E400RTR]. Below this heading you will see a default
  parameter PeekMessage=1. Modify this to PeekMessage=0.

  Protocol Boundaries with NetWare for SAA 2.0
  --------------------------------------------
  Only the new protocol boundaries released with NetWare for SAA 2.0 work
  with NetWare for SAA 2.0.  The previous LUx, APPC/PC, and CPI-C protocol
  boundaries for DOS, MS Windows, and NLMs are incompatible with the new
  release. YOU MUST USE THE NEW PROTOCOL BOUNDARIES.  In most cases, the new
  protocol boundaries make the change to NetWare for SAA 2.0 transparent to
  applications. 
       
  Upgrading from NetWare for SAA 1.3, or 1.3b, to NetWare for SAA 2.0
  -------------------------------------------------------------------
  The installation process automatically upgrades from NetWare for SAA 1.3
  to NetWare for SAA 2.0, including converting the configuration files.

  NetWare for SAA 2.0 requires an X.25 WAN driver that is compatible with the
  new CSL (Call Support Layer) NLM provided with this product. If you are
  upgrading from previous versions of NetWare for SAA (1.3 or 1.3b), you must
  use a driver that is compatible with the new CSL.NLM, such as the 
  SYNCPLUS.LAN driver provided with this product.

=============================================================================
4.0 KNOWN PROBLEMS AND ISSUES 
==============================

  3270 Sessions Dropping on NetWare 3.12
  --------------------------------------
  PROBLEM: The number of 3270 sessions you are able to run with NetWare for
  SAA 2.0 on NetWare 3.12 depends upon the 32MB NetWare server memory, the
  SPX(tm) connection configuration, and your 3270 emulator package.

  The maximum amount of short-term memory allocation is limited to 32MB on
  NetWare 3.12.  If your emulator supports one LU per SPX session, your
  server is limited to 1,500 SPX connections. 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 your
  total NetWare for SAA sessions.

  The maximum number of packet receive buffers on NetWare 3.12 is 2,000.If 
  your server is using many SPX connections and is configured for 2,000
  packet receive buffers, keep in mind that these 2,000 packet receive
  buffers are shared for all connections. Sharing buffers may slow
  performance if the server traffic is high and the number of SPX connections
  approaches the maximum.

  WORKAROUND: 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 reaches this maximum,
  then all NetWare for SAA sessions over SPX will be lost and no new SPX
  sessions can be started.  To avoid this problem, either load SPXCONFG.NLM
  and increase the maximum number of SPX connections to 2,000 (NetWare 3.12
  maximum support) or upgrade to NetWare 4.1.

  Differing Board Name Configurations
  -----------------------------------
  PROBLEM: After an upgrade from NetWare for SAA 1.3 to NetWare for SAA 2.0, 
  and an upgrade to Netware MultiProtocol Router 3.0 or NetWare Link/X25 3.0, 
  the "Board Name" is converted to a new name within INETCFG. This name is 
  different from the NetWare for SAA 2.0 configured "Board Name." 

  WORKAROUND: In CSCON, create a NetWare for SAA 2.0 adapter definition that
  matches the new board name specified in INETCFG, and set the adapter to 
  "In Service." Set the current adapter to "Out of Service," and modify the
  Host PU profiles to use the new adapter. Be sure to also modify Host PU 
  profiles for Downstream PUs accordingly. (See Chapter 5 and Chapter 7 in
  the NetWare for SAA 2.0 Administration Guide for Mainframes and Peer 
  Nodes.)

  Capitalizing Server Names for API Clients
  -----------------------------------------
  PROBLEM: If you enter the server name in lowercase letters when configuring
  the DOS or MS Windows API client for either LU6.2 or LUx, NetWare for SAA
  fails to find the server because server names are in upper case.

  WORKAROUND: Enter the server name in uppercase letters during API client
  configuration.

  Client Failure when AS400PCS.NLM Is Loaded with SECURITY=ON
  -----------------------------------------------------------
  PROBLEM: If the server address you are connected to after loading IPX/SPX 
  on the client begins with 0 and the server you've loaded AS400PCS with is
  set to SECURITY=ON, you will receive the error code N6005, if you attempt
  to start the DOS or MS Windows client router.

  WORKAROUND: Set SECURITY=OFF, or modify the internal server address so
  that it doesn't begin with 0, for example, change it from 012345 to 12345.
 
  USERID Required when AS400PCS.NLM Is Loaded with SECURITY=ON
  ------------------------------------------------------------
  PROBLEM: If AS400PCS.NLM is loaded with SECURITY=ON the NS/Router Windows
  client will prompt the user for a NetWare user ID even if the user is
  logged into the NetWare server. You are required to enter the full path
  if you are a NetWare 4.1 client.

  WORKAROUND: Set SECURITY=OFF.

  Drivers Loaded Prior to Running SERVER.EXE
  ------------------------------------------
  Be sure that DOS LAN drivers and memory drivers are NOT loaded prior to
  running SERVER.EXE from your machine. Some of these drivers have conflicts
  with NetWare.
   
  Ignore AX Register on DOS for APPC/PC
  -------------------------------------
  When an APPC/PC verb is successfully executed on the DOS platform,the AH 
  register is not updated. When the APPC/PC verb is issued, AH contains the
  verb format. However, the DOS APPC/PC PB does not zero out AH if the verb
  is accepted. As a result, the AX register does not return zero,as
  documented, upon verb acceptance, but returns a nonzero value instead.

  WORKAROUND: Ignore the AX register--as do most APPC/PC applications.
  Examine the primary and secondary return codes in the verb record to 
  determine the success or failure of the verbs. These return codes are set
  correctly.

  Inaccurate Data from NetView* Query Server RUNCMD
  -------------------------------------------------
  PROBLEM: The IBM NetView Query Server run command returns some inaccurate
  data for NetWare 4.1 servers. Rather than returning the MAXIMUM number of
  licensed connections, this command returns the ALLOCATED number of licensed
  connections. Query Server may also report an inaccurate value for maximum
  number of volumes supported.

  Incorrect Secondary Error Code Format for SLI_OPEN
  -------------------------------------------------- 
  PROBLEM: When SLI_OPEN fails, the secondary error codes are NOT returned
  in Intel* format (Little-Endian), as documented in LUX_RC.H, for errors
  that result from SNA sense codes generated by the host. For example, 
  SLI_OPEN might fail with a primary return code of 0x0F00 
  (LUX_SESSION_FAILURE, as documented) and a secondary return code of 
  0x08570002 (LUX_SSCP_PLU_SESSION_NOT_ACTIVE byte swapped).

  Internal IPX Address
  --------------------
  Do not change the internal IPX address or reinstall NetWare Directory
  Services on a NetWare 4.1 server while the Communication Executive is
  installed, because the Communication Executive uses the internal IPX
  address.

  PB Trace File for AS/400
  ------------------------
  PROBLEM: Information about the PB trace utility appearing on page 11-17
  of the NetWare for SAA 2.0 Planning and Administration Guide for AS/400
  is incorrect.

  WORKAROUND: Use the following correct information:
 
  The name of the trace file created by PB trace (see Steps 3 and 4) is
  "NWSAAAPI.TRC," not "NWSAAAPI.INI."

  To format this file as a readable file, you type "PBFORMAT" and press
  <ENTER>. Do not type "PBFORMAT NWSAAAPI.FMT."

  Reestablishing Sessions with Other Servers
  ------------------------------------------ 
  PROBLEM:  In a NetWare 4 environment, you may have difficulty in 
  reestablishing sessions with other servers when a server in that 
  Directory tree has failed. When the server remains down, you might
  experience a delay in retrying the client application for up to 45
  seconds.

  WORKAROUND: When a server has been reloaded, retry the client application--
  for example, CSCON or the 3270 application--and the connection should be
  reestablished.

  SAAUP Console Command
  ---------------------
  When the SAAUP console command finishes executing and NetWare for SAA is
  loaded and running, the current screen is for AS400PCS.NLM, not the main
  console. The user must manually switch back to the console screen or
  another one if desired.

  Server Suspension during CSDOWN
  -------------------------------
  PROBLEM: If LUx NLM applications are running on the server when you perform
  a CSDOWN operation, the server might become suspended in CCM.NLM.

  WORKAROUND: Unload any running LUx NLM applications before entering CSDOWN.

  SDLC Informational Warning Message
  ----------------------------------
  The following message might appear on the NetWare console when you are
  using an SDLC connection:

  "Unable to get an ECB for receiving incoming data from the host Please
  increase minimum packet receive buffers in the STARTUP.NCF and increase
  maximum packet receive buffers in AUTOEXEC.NCF. SDLC frame receive 
  overrun."
        
  This is an informational message that lets you know that the system
  allocated additional event control blocks (ECBs) in memory for the SDLC
  adapter. You can ignore this message if you have minimum packet receive
  buffers=500 in your STARTUP.NCF file and maximum packet receive 
  buffers=2000 in your AUTOEXEC.NCF file.

  Spontaneous Unloading of CMSPX.NLM under NetWare 3.12
  -----------------------------------------------------
  PROBLEM: Under NetWare 3.12, CMSPX.NLM unloads itself spontaneously when
  the number of SPX connections reaches the configured limit minus 1.

  WORKAROUND: Set the limit on SPX to 2000, the maximum allowed. Doing so
  enables the system to support the maximum number of sessions allowed under
  NetWare 3.12, plus additional sessions for applications.
   
  Timeout Error ERR_CCT_SPXCVERROR during running LUx Sessions
  ------------------------------------------------------------
  PROBLEM: Under certain circumstances, such as heavy network traffic when
  running more than 4 LUx sessions from a DOS or MS Windows workstation you
  might receive the following error: ERR_CCT_SPXCVERROR. 

  WORKAROUND: Increase the SPXS ABORT TIMEOUT parameter in the NET.CFG text 
  file that resides on each workstation running the LUx sessions. By
  increasing this parameter you increase the amount of time that SPX will
  wait before terminating the session. If you are running on Windows also
  increase the IPX SOCKETS parameter. This parameter increases the maximum
  number of open IPX sockets at your workstation.
  
  For DOS: SPX ABORT TIMEOUT = 2500
  For Windows: SPXS ABORT TIMEOUT = 7500
               IPX SOCKETS = 25

  Truncated Responses to NetView RUNCMDs
  --------------------------------------
  PROBLEM: Under certain circumstances, when a NetView run command processed
  by a NetWare for SAA server generates a response greater than 256 bytes,
  not all the data in the response is sent to NetView. Some commands such as
  DIR can generate lengthy responses.

  This problem occurs only if the Host PU profile named in CSCON is
  different from the PU specified in the SP= argument of the run command.
       
  WORKAROUND: Use the Host PU profile assigned as the NetView host (the
  "Upstream Management Mode") as the only receiver of NetView run commands.
  The name of this Host PU profile appears on the Configure Network
  Management panel in CSCON. Make sure that the SP= argument specifies this
  Host PU profile name.

  Unexpected OS Error from RUI_INIT and SLI_OPEN
  ----------------------------------------------
  PROBLEM: If you are using LUx for MS Windows clients, you might receive an
  unexpected OS error when the RUI_INIT or SLI_OPEN verb is issued.

  This error occurs if packets are lost during the client's attempt to
  establish a session with the NetWare for SAA server, and can be minimized
  or eliminated by the prevention of packet loss. Check LAN adapters to make
  sure they are functioning properly.

  WORKAROUND: Reissue the RUI_INIT or SLI_OPEN verb when the error occurs. If
  you still cannot establish a session, apply available updates from the
  NOVLIB forum, to your MS Windows Transport Level Interface (TLI) dynamic
  link libraries (DLLs).

  Uninformative Error Message for Trace Filename Length
  -----------------------------------------------------
  PROBLEM: When using CSStatus, if you enter a trace filename that exceeds
  the maximum length of seven letters, you receive the message "STAT012B-263,
  Program should continue normally."

  WORKAROUND: Ignore the message and enter a filename of seven characters
  or fewer.

  Unloading AS400PCS.NLM from the NetWare 3.12 Console
  ----------------------------------------------------
  When AS400pcs.nlm is unloaded on the NetWare 3.12 console, the following
  CLIB error message will appear: "clib error". Since no problems result from
  this message, simply ignore it.

  Using the TP_VALID Verb in APPC/PC Applications
  -----------------------------------------------
  PROBLEM: If an APPC/PC application on any platform issues a TP_VALID verb
  with an invalid CREATE_TP pointer or an invalid CREATE_TP structure, the
  internal control block for the transaction program (TP) is discarded. As a
  result, any subsequent verbs correctly issued for that TP are rejected
  with a return code of BAD_TP_ID.

  WORKAROUND: Ensure that applications always issue TP_VALID with a correct
  TP_ID and unmodified CREATE_TP pointer and structure.

=============================================================================
5.0 TRADEMARKS
==============
 
  Novell, Inc. has attempted to supply trademark information about company 
  names, products, and services mentioned in this README file.

  Novell and NetWare are registered trademarks of Novell, Inc.

  IPX, IPX/SPX, Media Support Module, MSM, NE/2, NE/2-32, NE1000, NE1500T,
  NE2000, NE2100, NE3200, NetWare 4, NetWare Btrieve, NetWare Directory
  Services, NetWare HostPrint, NetWare Management Systems (NMS), NetWare
  MultiProtocol Router, NetWare Link/X25, NetWare SNA Links, NLM, Novell Labs,
  NTR2000, ODI, SPX, and Topology Specific Module, and TSM are trademarks of
  Novell, Inc.

  NetWire is a registered service mark of Novell, Inc.

  AppleTalk is a registered trademark of Apple Computer, Inc. LAT is a
  trademark of Digital Equipment Corporation. Intel is a registered trademark
  of Intel Corporation. AS/400, IBM, NetView, and OS/2 are registered
  trademarks, Client Access/400 and SAA are trademarks of International
  Business Machines Corporation. Microsoft and MS are trademarks of Microsoft.
  NetSoft is a trademark of NetSoft Corporation.
 
=============================================================================
  Copyright (c) 1991, 1992, 1993, 1995 Novell, Inc.  All rights reserved.
 
  **This concludes the README.TXT file for NetWare for SAA 2.0**
