September 1994

Release Notes for Microsoft(R) SNA Server version 2.1 
++++++++++++++++++++++++++++++++++++++++++++++++++++++

For important information about SNA Server version 2.1,
see the documents in the document set.  All documents 
can be found on the SNA Server CD in the DOCS directory.
Each of the documents in the 11-document set is available 
in three file formats: as Word for Windows version 2.0 
document files, as PostScript files (for printing), and 
as online Help files.

For information about the location of the document 
files, see the listing in Chapter 1 of the Microsoft 
SNA Server Installation Guide or the README.TXT file in 
the DOCS directory on the CD.  The README.TXT file in the 
DOCS directory also tells how to print the documents.

These release notes explain

A. Supplementary information about SNA Server
B. Additions and corrections to the documentation

A. Supplementary information about SNA Server
-----------------------------------------------

A.1. Notes on the operating system
     and processor for an SNA server
------------------------------------
This version of the server software for SNA Server can
only be installed with one of the following combinations 
of processor and operating system:

Type of
processor   Operating system
---------------------------------------------------------
Intel       Windows NT(TM) Advanced Server version 3.1 or
            Windows NT Server version 3.5

MIPS(R)     Windows NT Server version 3.5
or Alpha
AXP(TM)


A.2. Information in the SNA Server Companion Product Catalog
------------------------------------------------------------
For detailed information about hardware and software available
from independent software vendors for use with SNA Server, see 
the SNA Server Companion Product Catalog, ISVCATAL.DOC, in 
the \COLLATRL directory on the SNA Server CD.  Periodic updates 
to this catalog are distributed on the Microsoft TechNet CD and 
posted on the MSSNA CompuServe(R) forum.


A.3. Updated file needed for computers running Windows NT
     version 3.5 final release (build 807)
--------------------------------------------------------
The procedure in this section applies only to SNA servers 
and clients running Windows NT version 3.5 final release 
(build 807).

--------------------------------------------------------
IMPORTANT
Carry out the following procedure only on computers 
running Windows NT version 3.5 final release (build 807),
on which no CSDs (hot fixes) have been applied to Windows
NT.  (The procedure includes directions for determining 
the exact version of Windows NT on a computer.)   Do not 
carry out the procedure on computers running Windows NT 
version 3.1, or Windows NT version 3.5 with CSDs applied.  
Otherwise, the computer may lose basic network functionality.
--------------------------------------------------------

The following procedure explains how to update the file 
called RDR.SYS by copying it from the SNA Server CD to the 
appropriate directory on the hard disk.  On computers running 
Windows NT version 3.5, build 807, if the updated RDR.SYS file 
is not copied, the SNA Server software will not be supported 
correctly by the operating system.  As a result, sessions 
may not connect and applications may not receive data.

> To copy the updated RDR.SYS file to an appropriate
  Windows NT-based server or client
-------------------------------------------------------------
1.  On the computer to which you plan to copy RDR.SYS, change
    to the following directory:
    \<WindowsNTRoot>\SYSTEM32
2.  Run the Windows version utility by typing

    winver

3.  In the resulting dialog box, check that the second line
    reads "Version 3.50 (Build 807)."

    ----------------------------------------------------------
    IMPORTANT
    Do not continue with this procedure if the version of
    Windows NT is not 3.50, build 807.  Otherwise, you may
    disable the functionality of the network software on 
    the computer.
    ----------------------------------------------------------

4.  Insert the SNA Server CD into a CD-ROM drive that is
    accessible to the computer you are updating.  If the CD-ROM 
    drive is not a local drive on the computer you are updating, 
    establish a network connection from that computer to the drive.
5.  On the SNA server or Windows NT-based client, change to
    the drive containing the Windows NT software.
6.  Change to the following directory:
    \<WindowsNTRoot>\SYSTEM32\DRIVERS
7.  Type
    DIR RDR.SYS
8.  In the resulting listing, check that the date and time on 
    the RDR.SYS file are 09/04/94  08:07a.  Other dates and
    times indicate that the operating system may not be Windows
    NT version 3.5, build 807, which means that this procedure 
    should not be carried out.
9.  Type
    RENAME RDR.SYS RDR.OLD

    This ensures that you have a backup copy of the RDR.SYS file
    that was originally installed.
10. Type the command indicated by the following table:

    Hardware      Command to type
    ----------------------------------------------------
    Intel-based   COPY <CDdrive>:\NT35FIX\I386\RDR.SYS
    Alpha         COPY <CDdrive>:\NT35FIX\ALPHA\RDR.SYS
    MIPS          COPY <CDdrive>:\NT35FIX\MIPS\RDR.SYS

    In the preceding command, <CDdrive> is the drive containing
    the SNA Server CD.  The command copies the appropriate 
    version of RDR.SYS into the current directory, that is,
    the \<WindowsNTRoot>\SYSTEM32\DRIVERS directory.
11. Restart the computer.  To do this, in Program Manager, from
    the File menu, choose Shutdown.  In the resulting dialog
    box, select Shutdown and Restart, and then choose OK.


A.3.1. Updated file needed for Windows NT-based computers
       containing symbols (for debugging)
---------------------------------------------------------------
If you have Windows NT symbols on your computer, that is, if
you have obtained a software development kit (SDK) or similar 
software, and you carried out the previous procedure, you
should also carry out the following procedure.  (If you do not 
have Windows NT symbols on your computer, the following 
procedure does not apply to you.)  If the version of Windows NT 
that you have is not version 3.5, build 807, do not carry out 
the following procedure.

> To copy the updated RDR.DBG file to an appropriate SNA server 
  or Windows NT-based client
------------------------------------------------------
1. Make sure that you carry out the preceding procedure 
   for copying the RDR.SYS file to the SNA server or Windows
   NT-based client.

   ----------------------------------------------------------
   IMPORTANT
   Do not continue with this procedure if you did not carry
   out step one of the previous procedure to ensure that your 
   version of Windows NT is 3.50, build 807.
   ----------------------------------------------------------

2. Insert the SNA Server CD into a CD-ROM drive that is
   accessible to the computer you are updating.  If the CD-ROM 
   drive is not a local drive on the computer you are updating, 
   establish a network connection from that computer to the drive.
3. On the SNA server or Windows NT-based client, change to
   the drive containing the Windows NT software.
4. Change to the following directory:
   \<WindowsNTRoot>\SYMBOLS\SYS
   Note that this is not the same directory as in the preceding
   procedure.
4. Type
   COPY RDR.DBG RDR.OLD

   This ensures that you have a backup copy of the RDR.DBG file
   that was originally installed.
5. Type the command indicated by the following table:

   Hardware      Command to type
   ----------------------------------------------------
   Intel-based   COPY <CDdrive>:\NT35FIX\I386\RDR.DBG
   Alpha         COPY <CDdrive>:\NT35FIX\ALPHA\RDR.DBG
   MIPS          COPY <CDdrive>:\NT35FIX\MIPS\RDR.DBG

   In the preceding command, <CDdrive> is the drive containing
   the SNA Server CD.  The command copies the appropriate 
   version of RDR.DBG into the \<WindowsNTRoot>\SYMBOLS\SYS
   directory.


A.4. Notes on removing earlier
     versions of SNA Server
-------------------------------
When upgrading an SNA Server installation that contains a 
beta release or version 2.0 of SNA Server, note the following 
guidelines:

*  It is strongly recommended that you upgrade all SNA 
   servers in the same domain to version 2.1.  The mixing of 
   version 2.0 with version 2.1 SNA servers in the same 
   domain is supported, but the primary SNA server must be 
   version 2.1, and the version 2.0 SNA servers in such 
   mixed domains must be updated with the latest SNACFG.DLL 
   patch (hotfix) for SNA Server version 2.0.  For additional 
   important information about upgrading a domain of SNA 
   servers from version 2.0 to version 2.1, see the 
   Microsoft SNA Server Installation Guide.

* Before installing this release on a particular computer,
  always remove the beta release or version 2.0 of the SNA 
  Server software first.  It is recommended that you do not 
  save (back up) the configuration file created with a beta 
  release of SNA Server, but instead allow the file to be 
  removed along with the earlier software.  (However, a 
  configuration file created with SNA Server version 2.0 or 
  a beta release will generally work as expected.  The 
  commands in SNA Server Admin that allow you to back up and 
  restore configuration files are the File menu Backup command
  and the File menu Restore command.)

* Always use the SNA Server Setup program to remove SNA Server 
  software.  Do not use commands such as the DELETE command.

* Before removing a beta release or version 2.0 of SNA Server
  software, be sure to stop (exit from) SNA Server Admin, 
  any TN3270 server software, any emulators, and any 
  applications that use the SNA Server software.  Otherwise, 
  the SNA Server software may be in use when you attempt to 
  remove it, and some components may not be removed, resulting 
  in incomplete installation of the new software.  After 
  finishing an upgrade, if you are concerned that the new 
  installation is incomplete, stop any software that might have
  interfered with installation; then use the SNA Server Setup 
  program to remove and reinstall the SNA Server software.

* If you are running version 3.1 of Windows NT or Windows NT
  Advanced Server, after removing the previous SNA Server
  software, restart your computer before installing this release 
  of SNA Server.  Otherwise, the Event Log service will trap
  during installation of SNA Server version 2.1 (installation 
  will not be affected otherwise).  If this happens, choose OK 
  in the Dr. Watson dialog box and continue the installation.  
  Then be sure to restart your computer at the end of the 
  installation.  No other action is required.

For detailed information about the actions carried out by
Setup, see Appendix D of the Microsoft SNA Server Reference.


A.5. Information to have ready when 
     contacting product support
------------------------------------
If you contact product support regarding a problem, please 
collect as much of the following information as possible:

* Specific procedure for reproducing the problem
* In case of a Windows NT trap, the DRWTSN32.LOG file and
  any memory dump files: 
  <WindowsNTRoot>\DRWTSN32.LOG
  <WindowsNTRoot>\MEMORY.DMP
* In case of an SNA Server trap, dump files appended to
  <SnaServerRoot>\TRACES\SNADUMP.LOG
* Windows NT event log files: 
  <WindowsNTRoot>\SYSTEM32\CONFIG\*.EVT
* SNA Server configuration file: 
  <SnaServerRoot>\SYSTEM\CONFIG\COM.CFG
* Applicable trace files collected via SNATRACE.EXE program:
  <SnaServerRoot>\TRACES\*.TRC
* Applicable datascope or sniffer traces

Contact your support provider--Microsoft Support Network or 
CompuServe--with this information.

If CompuServe is not accessible to you, you can email 
questions to the following Microsoft email alias:
mssna@microsoft.com

This alias is accessible via Internet, MCI MAIL(R), and 
X.400.  This is not a product support source, but a way to 
send suggestions, concerns, or compliments directly to the
Microsoft SNA Server team.


A.6. Maximum number of clients when using Banyan(R) VINES(R)
------------------------------------------------------------
Because of a limitation with the Banyan VINES protocol, the 
maximum number of clients that can be supported with VINES 
is 500 per server.  To support this number of clients, settings 
in the VINES software on the server must be changed (default
values allow 150 clients per server).  To change these 
settings:

1. On the SNA server, access the Banyan VINES program group.
2. Activate the Setup icon of the program group.
3. Activate the Network icon of the resulting program group.
3. In the Network Communications dialog box, for Communications
   Heap Size, type 256.
   This setting controls the amount of memory set aside for
   communications.  You can try a value less than 256 to 
   make more memory available to other software; however, the 
   full 256K may be necessary for supporting 500 clients.
4. For Total SPP Connections, type 1000.
   Two SPP connections are used by each client connecting to
   the SNA server.  With 1000 SPP connections, 500 clients
   can connect to the SNA server.
5. Choose OK.


A.7. Setting up the Windows-based (16-bit) client software
     to run with Windows NT version 3.5
------------------------------------------------------------
With SNA Server version 2.1, you can use the client software
for the Windows(TM) operating system version 3.x (the 16-bit 
client software) on Windows NT version 3.5.  This allows you 
to run emulators written for Windows version 3.x (16-bit 
emulators) on Windows NT version 3.5.  However, when running 
such software, use the following guidelines:

* If you install 16-bit client software on a computer running
  Windows NT version 3.5, do not install the 32-bit client 
  software (the client software for Windows NT) on the same 
  computer.

* Do not run the 16-bit client software or 16-bit emulators
  in a separate memory space.  That is, when using the Run 
  command in the File menu of Program Manager, do not select 
  the Run in Separate Memory Space check box; when using a 
  command to start such software, do not use the /SEPARATE 
  option.

  Running 16-bit emulators in a separate memory space is
  not supported because the SnaBase component of the client 
  software (WNAP.EXE) must run in the same memory space as 
  the emulator (or other client-based application).  Therefore, 
  when the emulator starts, it starts an instance of WNAP.EXE 
  in the same memory space.  Then, if the emulator is stopped 
  and restarted one or more times, multiple instances of 
  WNAP.EXE will be started, causing system difficulties.


A.8. PC Support, the MS-DOS(R) extender, and shared folders
-----------------------------------------------------------
If you want to use the SNA Server MS-DOS-based client to 
connect to an AS/400(R) using IBM(R) PC Support and you want 
to use PC Support functions that require loading the MS-DOS 
extender bundled with PC Support, shared folders will not 
load.  (The choice between the extended and nonextended mode 
is made when installing PC Support.)

As a workaround, you can arrange to share the shared folders 
through Windows for Workgroups on a computer that has PC Support 
installed.  To do this, on the computer running Windows for 
Workgroups, map the AS/400 shared folders to a drive letter
(such as I:).  Then create a Windows for Workgroups share of 
this drive.  Users who can connect through the LAN to the 
Windows for Workgroups share will be accessing the files on 
the AS/400.  If you set up a computer with DOS PC Support, 
Windows for Workgroups, and the suggested share, you can 
eliminate the need to run PC Support and/or shared folders 
on other computers.


A.9. Working with Client Access/400
-----------------------------------
Client Access/400 (CA/400) is a new software product (in
beta as of August 1994) from IBM.  CA/400 adds a Windows 
interface to existing PC Support functionality.  CA/400 
can be used with Microsoft SNA Server version 2.1, 
specifically, with the MS-DOS-based client software and 
the SNA Server MS-DOS-based ROUTER.EXE module (Router).  
Please note the following guidelines when using CA/400:

* If you plan to use CA/400 with Router, be sure to 
  read the information about Router in Chapter 3 of the 
  Microsoft SNA Server Installation Guide.

* When CA/400 is used with SNA Server software, the shared 
  folders component of CA/400 is not supported.

* To run CA/400, you must start the underlying software
  components (for example, the client SnaBase software and 
  the Router) in MS-DOS, before starting the Windows 
  operating system.  The procedure is similar to the procedure
  for starting Router, as described in Chapter 3 of the 
  Microsoft SNA Server Installation Guide.

  > To start both Router and CA/400
  ---------------------------------
    1. On the client, make sure Windows is not started, so
       that only MS-DOS is running.
    2. At the MS-DOS prompt, start the SnaBase by typing
       SNABASE
    3. Change to the PC Support directory.  For example, type:
       CD \PCS
    4. Make sure that ROUTER.EXE and INITRTR.EXE (SNA Server
       MS-DOS-based client components) have been copied to the 
       PC Support directory.
    5. Start SNA Server Router by typing
       ROUTER [<options>]
       where <options> are as described in the Microsoft SNA 
       Server Installation Guide.
    6. Start the other PC Support components that you need.
       If you want to use the extended version of PC Support,
       you must first start RTRMAP.EXE, to allow communication
       between the extended PC Support functions and Router.
       RTRMAP.EXE is provided with PC Support and can be found 
       on the I:\FL2 shared-folders directory on the AS/400.
    7. Start the PCSWIN component of PC Support by typing
       PCSWIN
    8. Start Windows.
    9. Start the CA/400 emulator software by double-clicking
       on the appropriate icon.
       When the emulator software starts for the first time,
       it displays the Customize Communications dialog box,
       which is also available through the Configure command
       in the Communications menu.
   10. In the Customize Communications dialog box, be sure
       that AS/400 PC Support Router is selected.
   11. Proceed with using the CA/400 software as described
       in the product documentation.


A.10. IBM PC/3270 and the Max BTU Length
---------------------------------------
To use the IBM PC/3270 emulator with a downstream connection, 
just as when using other software on a downstream connection, 
it is important to configure a match between the Max BTU Length 
on the SNA Server connection and the Max BTU Length used on the 
downstream system.  One way to do this is to use the PC/3270 
default of 265, and set the Max BTU Length on the SNA Server 
connection to match.

For a downstream 802.2 connection, you will also need to check 
for a match between system access point (SAP) addresses set on 
each system.  With SNA Server, check the Remote SAP Address, 
which appears in the advanced part of the 802.2 Setup dialog 
box.


A.11. Availability of HLLAPI
---------------------------
As with previous releases of SNA Server, the necessary DLLs 
for testing and using HLLAPI are available through independent 
software vendors, and not through Microsoft.  As a convenience 
and to promote the Windows HLLAPI standard, Microsoft provides 
header and library files for Windows HLLAPI, along with 
electronic versions of the Windows HLLAPI Specification, on 
the SNA Server CD.


A.12. Using the DCA ISCA adapter at high speeds
-----------------------------------------------
With SNA Server version 2.1, avoid using the DCA ISCA adapter
at speeds greater than 38,400 bits per second (bps) unless the
processor is a Pentium or faster.  Otherwise, link failures
can occur under heavy loads.

---------------------------------------------------------
Note
A software patch (hot fix) will be available to correct
this limitation with the DCA ISCA adapter, soon after release 
of SNA Server version 2.1.  Contact your product support 
provider for more information.
----------------------------------------------------------


A.13. Using Attachmate Extra! version 4.0
      with Novell TCP/IP
-----------------------------------------
Attachmate Extra! version 4.0 does not work when Novell 
TCP/IP is used to connect to the SNA server.  (Novell TCP/IP 
is included in Novell LAN Workplace for DOS).  To use TCP/IP 
with Attachmate Extra! version 4.0, use other TCP/IP protocols, 
such as Microsoft TCP/IP.


A.14. DFT adapter compatibility
------------------------------
DFT adapters can be used with Intel-based systems only.  DFT 
adapters cannot be used with Alpha AXP systems or MIPS systems,
which have a system bus that cannot be set to INT 2, the only 
setting possible for most DFT adapters.


B. Additions and corrections to the documentation
-------------------------------------------------

B.1. Addition to the Microsoft SNA Server 
     3270/5250 Applet User's Guide
------------------------------------------
When transferring a PC file to a Partitioned Data Set (PDS),
ensure that the Record format is set to Default and the check
boxes for Block Size and Space are NOT checked.


B.2. Additions and Corrections to the Microsoft
     SNA Server Reference
------------------------------------------------

B.2.1. Additional information about the LogonUserName variable
--------------------------------------------------------------
On page 208 of the Microsoft SNA Server Reference, the 
following information should be added under the heading
"For Clients Running Windows version 3.x."

  For clients running Windows version 3.x but not running 
  Microsoft networking (named pipes), the following line can
  be placed in the [WNAP] section of the WIN.INI file to simplify
  the process of starting up the SnaBase and logging on to the 
  SNA servers in the domain.

  LogonUserName=<username>


B.2.2. WatchDogTimeOut variable
-------------------------------
The following variable should be added to Appendix C of 
the Microsoft SNA Server Reference.

WatchDogTimeOut
---------------
This variable affects the timeout interval used with TCP/IP.
The variable can be set on an SNA server, a Windows NT-based
client, or a client running Windows version 3.x.  For an SNA 
server or a Windows NT-based client, the variable is found in 
the following location in the Registry:

HKEY_LOCAL_MACHINE
  SYSTEM
    CurrentControlSet
      Services
        SnaBase
          Parameters

In the Registry, the variable is specified as follows:

WatchDogTimeOut:REG_DWORD:<number>      Default: 60 seconds

For a client running Windows version 3.x, the WatchDogTimeOut
variable is set in the [WNAP] section of WIN.INI, and is 
specified as follows:

WatchDogTimeOut=<number>

Regardless of operating system, the variable specifies the
number of seconds for the timeout for sessions over TCP/IP.  
When activity ceases across an established session (that is, 
when no messages are being sent), the local system waits the 
specified interval and then sends a message to see if the 
remote system responds.  If the remote system does not respond, 
the local system closes down the session.  For SNA servers, 
closing a session frees the LU(s) used for that session.

This variable can have different values on servers and clients.
In other words, a local system uses the local value regardless 
of the value on remote systems.

Decrease <number> to create a faster response to system failures 
within a TCP/IP network.  Increase <number> to minimize overhead
on TCP/IP networks where system failures are infrequent, or where 
a single system failure does not require an immediate response.

The range is 30-3600 seconds (3600 seconds equals 1 hour).  This 
range is enforced on SNA servers or Windows NT-based clients;
the range is recommended but not enforced on clients running 
Windows version 3.x.  If this variable is not set, it defaults 
to 60 seconds.


B.2.3. NO400D variable
-------------------------------
The following variable should be added to Appendix C of 
the Microsoft SNA Server Reference.

NO400D
------
This variable can disable checking for sense code 400D; it is
useful in situations where VTAM or CICS sends a full-duplex
BIND to set up a session but then uses CD to control direction
on the session.  (This sequence of actions can occur even though
it violates SNA protocols.)

The variable is used on SNA servers (not clients), and is found
in the following location in the Registry:

HKEY_LOCAL_MACHINE
  SYSTEM
    CurrentControlSet
      Services
        SnaServr
          Parameters

When a response other than the default is needed, the 
variable is specified as follows:

NO400D:REG_SZ:YES
  When this variable is set to YES or to any other value, 
  the SNA server will not check for sense code 400D.  When 
  the variable is not set at all, the SNA server checks for 
  sense code 400D.


B.3. Addition to the Microsoft SNA Server 
     APPC Programmer's Guide
-----------------------------------------
The version number of the Windows APPC and CSV APIs 
is 1.0 (not 2.0 or 2.1).  On pages 242 and 286 of the 
Microsoft SNA Server APPC Programmer's Guide, in the 
descriptions of WinAPPCStartup and WinCSVStartup, the 
text should emphasize that the API version number to 
pass is 1.0.  


B.4. Additions and Corrections to the Microsoft 
     SNA Server CPI-C Programmer's Guide
-----------------------------------------------
On page 13 of the Microsoft SNA Server CPI-C Programmer's 
Guide, at the bottom, there is a paragraph about 
"Terminate_Application" or "cmterm."  This paragraph should
be deleted.

The version number of the Windows CPI-C API is 1.0 (not 2.0 
or 2.1).  On page 176, in the description of WinCPICStartup, 
the text should emphasize that the API version number to 
pass is 1.0.  


B.5. Addition to the Microsoft SNA Server 
     LUA Programmer's Guide
-----------------------------------------
The version number of the RUI and SLI APIs is 1.0 (not 2.0 
or 2.1).  On page 148 of the Microsoft SNA Server LUA 
Programmer's Guide, in the description of WinRUIStartup/
WinSLIStartup, the text should emphasize that the API 
version number to pass is 1.0.  

< end of readme.txt >