README.TXT -- Notes on NetWare for SAA 1.3 Rev. B
=================================================
August 11, 1993

This release supports automatic updating from releases NetWare
for SAA 1.2 and 1.3 and 1.3 Rev. A to NetWare for SAA 1.3 Rev B.
It also supports automatic updating from NetWare 3.11 and NetWare 3.12
to NetWare 4.0x.

Table of Contents
-----------------

     1.0 Disk Organization
     2.0 Installation Process
     3.0 New Features
     4.0 Warning Notes
     5.0 Compatibility


1.0  Disk Organization
----------------------

     This is the combined release of COMMEXEC and NWSAA 1.3 Rev B.
     The software on the release diskettes is organized as follows:


     COMMEXEC Diskette 1 -          System Files: NLMs and LAN drivers
     COMMEXEC Diskette 2 -          BTRIEVE v6.1 update for NetWare 3.11
     COMMEXEC Diskette 3 -          COMMEXEC NLMs
     COMMEXEC Diskette 4 -          CM, SMA and other CS NLMs, Database 
                                    files, CSCON and related files
     COMMEXEC Diskette 5 -          MIBS for use with NMS
     Installation Diskette 1 of 3 - NWSAA NLMs, LAN drivers, MIBS
     Installation Diskette 2 of 3 - PB_NWSAA, AS400PCS, LUX, CPIC files
     Installation Diskette 3 of 3 - Database files, SAACON, OS2CON, TRACE,
                                    SAACOPY, and EEAS client
     NetView Support Files -        Code Point files
     NetWare LU6.2 for Client       Support for LU6.2 on MS Windows
         Support Files -
     License  Diskette -            License for LUs(sessions)
     SNMP 2.1 Update Diskette -     For NetWare 3.11 only
     NetWare HostPrint 1.0 Update - NetWare for SAA 1.3 update diskette 
     NetWare SNA Links 1.0 Update - NetWare for SAA 1.3 update diskette 
     NACS Compatibility Modules -   NACS 3.0 update for COMMEXEC 1.3 
     Miscellaneous Drivers -        EICON,SDLC and misc. 3rd party drivers
     README Diskette -              Includes README files for all update 
                                    diskettes and NetWare for SAA 1.3


2.0  Installation Process
-------------------------

2.1  NetWare 3.11

     The following NetWare 3.11 files located on Disk 1 are checked for
     appropriate versions.  If you want to preserve any of the following
     files, make sure you backup the files from the system directory before
     installing the COMMEXEC.


          NMAGENT  NLM     33665 08-12-91  11:12a
          SPXFIX2  NLM      1790 04-08-93   4:21p
          STREAMS  NLM     53579 12-14-92   3:00p
          TLI      NLM     12695 12-14-92   3:21p
          SPXS     NLM     24196 08-11-93   8:11a
          IPXS     NLM      8121 10-02-92  12:24p
          MONITOR  NLM    117775 10-26-92   9:21a
          TOKENDMA LAN      8822 01-29-93   8:45p
          LSLENH   NLM     11641 11-16-92   8:29a
          CLIB     NLM    305867 05-19-93   5:27p
          PATCHMAN NLM      9632 02-04-93  10:38a
          MSM31X   NLM     16118 02-09-93   2:19p
          TOKENTSM NLM      7418 01-29-93   8:40p
          ETHERTSM NLM      7418 01-29-93   8:40p
          NE1000   LAN      4468 01-20-93   3:18p
          NE2000   LAN      7294 01-20-93   3:17p
          NE3200   LAN      9719 02-08-93   8:26a
          NE2      LAN      4974 01-20-93   3:19p
          NE2_32   LAN      5210 01-26-93  10:14a
          TOKEN    LAN     10122 04-02-93   9:22a
          NTR2000  LAN     10130 04-02-93   9:22a
          CSL      NLM     24225 04-29-93   4:17p

     Note that the NE2-32.LAN driver has been renamed to NE2_32.LAN.  If
     you are already using this driver, make the appropriate change to the
     AUTOEXEC.NCF file.

2.2  NetWare 4.0x

     When installing COMMEXEC to a remote NW4.0x server, the CSADMIN 
     password does not get set to "NWSAA."  Use the NWADMIN or NETADMIN
     tool to set the password to the desired value before using CSADMIN
     as a login ID for CSCON.

     If you already have STREAMS.NLM loaded on your 4.01 server 
     please be sure to unload it and reload it after installing COMMEXEC 
     and NWSAA.  A new version of STREAMS is copied over during the
     installation.  To ensure that the new STREAMS.NLM gets loaded, bring
     the server down (with the DOWN command) and then restart it (with the
     SERVER command).

2.3  Upgrading from NWSAA 1.2 to NWSAA 1.3

     When upgrading from NWSAA 1.2 to NWSAA 1.3, the upgrade automatically
     creates a default adapter name.  Execute CSCON and change the
     logical adapter name entry so that it matches the "Name=" parameter
     in the AUTOEXEC.NCF file.


3.0  New Features
-----------------
     
3.1  COMMUNICATION EXECUTIVE
     
     1. Support for NetWare 4.0x was added.

     2. CSNAME is no longer case sensitive. Applications using the NetView 
        interface may specify a target Communication Server name that 
        contains upper and lowercase letters.

     3. Modified the CMAT.NLM, CMSPX.NLM and CMSPX.NLM to support the 
        CSUNBIND command. In NetWare 4.0x, CSUNBIND is the only method
        for unloading a connection manager module while there are active
        connections.

     To bind a transport protocol manually, issue the following command
     at the NetWare console:

         CSBIND [spx | appletalk | tcp-ip]

     To unbind a transport protocol manually, issue the following command
     at the NetWare console:

         CSUNBIND [spx | appletalk | tcp-ip]


3.2  INSTALLATION UTILITY

     1. CSL database file format changes and conversion support was added
        for third party drivers. Previously there were incompatibilities 
        with the NewPort X.25 drivers.

     2. The installation program checks for the versions of NLMs. If it is
        not the correct version, the program alerts the user so he can
        take appropriate action, such as backing up system files, installing
        SNMP, or continuing with the installation process.

     3. Support was added for automatically upgrading the Communication
        Executive environment from 3.x to 4.x.

3.3  NETWORK MANAGEMENT

     1. SNMP alert support -- This feature converts the existing set of 
        alerts generated by CE/NWSAA to SNMP traps. The traps are forwarded 
        to an SNMP agent for distribution to the SNMP console. This feature
        includes the NMS Trap MIB and help files for CE/NWSAA SNMP traps. 
        These are for customers that have NetWare Management Services 
        (NMS) but not NetWare for SAA Services Manager.
 
     2. NetWare for SAA Services Manager management application support 
        for BUSTECH Channel attached driver was added.

     3. NetWare for SAA Services Manager management application support 
        for the NWSAA Synchronous Adapter (Remote III) was added.

     4. NetWare for SAA Services Manager management application support 
        for the NTR2000 was added. The 3.23 version of the driver has a 
        different short name and this short name was added to the NMA table.

     5. Added support for IBM Token Bus PS/2 Adaptor as an MLID driver for
        Network Management.

     6. A feature was added to restrict the flow of NetView alerts if a 
        high-water mark is exceeded.  This is configurable through the
        NVCMDS.DB.

     7. Added support to detect if a registered EndPoint server goes down.
        A NetView alert is generated.

     8. There is now a RUNCMD retry limit, retry timer, and response
        timer which are configurable through NVCMDS.DB.

3.4  NWSAA

     NWSAA log information is no longer kept in SYS:SYSTEM\SYSTEM.LOG.  
     Each NWSAA profile has its own log file named 
     SYS:SYSTEM\<profile_name>.LOG.  You should periodically erase the 
     .LOG files so that they will not consume too much disk space.

3.5  SDLC

     Two new alert messages were added for the frame reject condition.
     These alerts were not previously displayed in SDLC configurations.

3.6  QLLC

     DLM.NLM was changed to support QLLCS with downstream PUs during 
     reconnect.

3.7  DLM

     Support was added so that QLLCS will work with downstream PUs during 
     the reconnection process. 

3.8  TRACE

     TRFORMAT.EXE now decodes LUX information.  This was done as an ETF 
     to NetWare for SAA 1.2 and is included as part of the NetWare for 
     SAA 1.3 release.

3.9  HOST PRINT

     Changes were made to not reset the printer formatting parameters,
     such as horizontal tab settings at the end of each print job. These
     parameters are now preserved from one host print job to the next.

3.10 Workstation Connection Manager

     Changes were made to include HELP files to WEEAS for OS/2 access 
     support.

3.11 NetWare Access Server (NAS)

     NetWare for SAA 1.3 Rev. B now supports PC Support with the NetWare
     Access Server (NAS).  Please refer to section 5.2.

3.12 LUX support.  

     Support for LUX was added in this release.


4.0  Warning Notes
------------------

4.1  OS Ring Protection

     Under NetWare 4.0x, NWSAA 1.3 can only be loaded and executed in the 
     OS Domain at Ring 0.


4.2  Multiprotocol Router Installation

     If NetWare for SAA is already installed on a NetWare 3.11 server, 
     and you plan to install Multiprotocol Router 2.1, DO NOT COPY OVER 
     THE BTRIEVE.NLM THAT IS INCLUDED IN THE MPR PRODUCT. It is an older 
     version.  


4.3  Using CSLOAD/CSUNLOAD with Downstream PUs

     If NetWare for SAA is unloaded (using CSUNLOAD) and then reloaded
     immediately (using CSLOAD) when 100 or more downstream PUs
     are connected to it, NetWare for SAA may abend with the following 
     error:   FSM_XID3_NEG_PROTO.  This error occurs only if the 
     downstream PUs are also running NetWare for SAA on a server. To 
     avoid this problem, wait for about two minutes between unloading 
     and reloading NetWare for SAA.

4.4  Using OS/2 2.0 as a Downstream PU

     When running an OS/2 2.0 workstation configured as a downstream PU, 
     RUNCMDSs sent to the OS/2 2.0 workstation potentially caused the
     NetWare server to be unreliable when running with the "Communication
     Manager/2 version 1.0 Service Pack" product.  This problem is 
     resolved by an IBM APAR, #II07032.


4.6  Order of Loading Protocol Stacks

     Load the protocol stacks that will be required by the Communication 
     Executive prior to loading the COMMEXEC.NLM. If you do load the
     COMMEXEC.NLM, and it has been configured to require other protocol
     stacks (SPX, Appletalk, or TCP/IP), and the protocol stack has
     not been loaded, then the error message "CE: unable to build stream
     driver <XXX>..." will be displayed.  


4.7  CSSTATUS

     Loading CSSTATUS immediately after loading COMMEXEC (e.g., in
     the AUTOEXEC.NCF file) may cause the server to abend.  To avoid
     this problem, place some other command between the two load commands
     in your AUTOEXEC.NCF file.


4.8  (Eicon SDLC-card related)

     The Eicon driver takes up to 15 seconds to load and initialize.
     This means that it may be necessary to insert a command or procedure 
     in the AUTOEXEC.NCF file to delay the execution of subsequent CSLOAD
     commands (for profiles that use the EICON driver) in the AUTOEXEC.NCF 
     file. The EICON driver must be loaded after loading the Communication 
     Executive.  The public domain NLM called DELAY.NLM is one example of 
     a method you could use to delay execution of the CSLOAD command.
     Another alternative is to issue the CSLOAD command manually from 
     the NetWare console.

4.9  Installing NWSAA While CSL.NLM is Loaded

     Problems have been experienced if NWSAA is installed and you are
     implementing a QLLC connection to a host with the Newport X.25 driver,
     or SNALinks has been installed while the CSL.NLM is loaded.  The 
     symptom is that the Newport X.25 driver will not be able to read its 
     configuration database.  We have observed that NetWare 4.01 may generate
     spurious server-down events when objects are created in the directory.  
     These events may cause the CSL.NLM to enter a state where it will no
     longer allow drivers to get their configuration and load.  To avoid 
     this problem, make certain that CSL is unloaded and reloaded again
     after performing any operations such as loading the Newport X.25 
     driver, running CSCON, or NETADMIN.

4.10 4.0x Issues with STREAMS.NLM

     The 4.0x installation for NWSAA copies a new STREAMS.NLM module to
     the server.  If this module does not get loaded into memory, you
     may experience an ABEND while performing a DOWN operation.  To avoid
     this problem, make certain that you DOWN the server after installation
     to ensure that the new STREAMS.NLM gets loaded.

5.0  Compatiblity
-----------------

5.1  Multiprotocol Router 2.1

     NetWare for SAA 1.3 Rev. B is compatible with Multiprotocol Router
     2.1.  Multiprotocol Router 2.1 is the only version NetWare for SAA
     1.3 Rev. B has been fully tested with at this time.

5.2  AS/400 Router and IBM PC Support

     If you are running IBM PC Support Workstation Emulation over the
     NetWare Access Server, only IBM regular mode PC Support can be used.
     This is because the Access Server uses Extended Memory drivers to
     allow multiple sessions.  Extended DOS PC Support is not supported
     by the NetWare Access Server. 

     Virtual folders are not supported in either regular or extended mode
     when running IBM PC Support in conjunction with the Access Server.
    

   
