
October 24, 1993

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

These notes explain

A. Contents of the accompanying floppy disks and the CD

B. What to do if you encounter a software bug

C. Workarounds for known problems in SNA Server

D. Additions and corrections to the SNA Server documentation 



A. Contents of the accompanying floppy disks and the CD
-------------------------------------------------------

These are the accompanying 3.5" floppy disks:

* (4) SNA Server system disks for Windows NT(TM)
* (1) SNA Server IBM drivers disk
* (2) SNA Server client disks for Windows(TM) version 3.x
* (1) SNA Server client disk for MS-DOS(R)
* (1) SNA Server client disk for OS/2(R)

Note that the XCOPY command can be used to copy the files 
from a 3.5" disk to a 5.25" disk, if 5.25" disks are required 
for installation (disk labels need not be preserved).

The accompanying CD includes the preceding list of software, 
plus four additional directories: DISKS, USERDOCS, SDK, and 
COLLATRL.

 * DISKS directory.  This contains the directory structure 
   and all the files of the 3.5" disks, in case your 3.5" 
   disks are damaged, and for convenience in creating 5.25"
   disks.

 * USERDOCS directory.  This contains electronic versions of 
   the printed documents provided with the package:

   - "SNA Server Installation Guide"
   - "SNA Server Administration Guide"
   - "SNA Server Reference"
   - "SNA Server 3270/5250 Applet User's Guide"

   In addition, the USERDOCS directory contains electronic 
   versions of the SDK documentation (hard copies can be 
   ordered from Microsoft):

   - "SNA Server CSV Programmer's Guide"
   - "SNA Server APPC Programmer's Guide"
   - "SNA Server CPI-C Programmer's Guide"
   - "SNA Server LUA Programmer's Guide"
   - "SNA Device Interface Specification"
   - "3270 Emulator Interface Specification"
   - "Windows HLLAPI Specification"

   All documents are provided in Microsoft Word for Windows 
   (version 2.0) format, as well as in PostScript(R) format.  
   A README.TXT file with printing instructions is provided 
   in the USERDOCS directory.

* SDK directory.  This contains software development files:

   - Header and library files for all SNA Server APIs and 
     interfaces (see the preceding list of programmer's 
     guides)
   - Sample code
   - A README.TXT file with information about the sample 
     code as well as updates to the SDK documentation

   Note that the SDK information is available on the CD 
   only, and there is no special SDK version of the product 
   (as each product CD contains all the SDK materials).
 
 * COLLATRL directory.  This contains files for:

   - SNA Server Technical Data Sheet:  SNADATAS.DOC
     (in Word for Windows version 2.0 format)
   - SNA Server Companion Product Catalog:  ISVCATAL.DOC
     (in Word for Windows version 2.0 format)
   - SNA Server overview/marketing/training presentations: 
     SNATECH.PPT, SNAMKTG.PPT, WINSNA.PPT and SNATR1-7.PPT
     (in Microsoft PowerPoint(R) version 3.0 format)



B. What to do if you encounter a software bug
---------------------------------------------

If you discover a bug in the product, please collect as 
much of the following information as possible:

* Specific procedure for reproducing the bug

* In case of a Windows NT trap, the DRWTSN32.LOG file: 
  <WindowsNTRoot>\DRWTSN32.LOG

* In case of a Windows NT 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 with this information.  You 
can also report software bugs to Microsoft via the MSSNA 
forum on Compuserve.

If Compuserve is not accessible to you, you can email
questions to the Microsoft email alias mssna@microsoft.com, 
which is accessible via Internet, MCI-Mail and X.400.  This 
is not a product support source, but a way to send 
suggestions, concerns, or praise directly to Microsoft people 
working on SNA Server.



C. Workarounds for known problems in SNA Server
-----------------------------------------------

C.1. Installing from CD may cause file corruption
-------------------------------------------------

If SNA Server has been installed from the CD and the system 
fails randomly or does not appear to work at all, the 
problem may be an SNA Server system file that was corrupted 
as it was copied from the CD.  This is believed to result 
from a bug in the Windows NT CD-ROM driver software, but no 
definitive diagnosis is available at this time.

The SNA Server CD includes a utility called CHECKSUM.EXE, 
which can be used to check whether any files are corrupted. 
Run this utility from the command prompt in the SNA Server 
root directory; any corrupted files will be listed as 
output.  Any such files can then be copied manually from the 
CD to the appropriate directory on the hard disk.

The workaround is to install from the floppy disks, which is 
known to work reliably.


C.2. Removing token ring cable may stop Windows NT
--------------------------------------------------

If you encounter a system failure in Windows NT associated 
with removing and reattaching the token ring cable, obtain a 
software update for the Windows NT version 3.1 IBM Token 
Ring NDIS driver from Microsoft Support Services (Windows NT 
bug #3758).  The workaround is to remove the token ring 
cable only when the system is powered off.


C.3. Stopping 802.2 connection on a multiprocessor 
     system may hang SNA Server
---------------------------------------------------

If you are running SNA Server on a symmetric multiprocessor 
computer with an 802.2 connection to a mainframe or AS/400(R), 
SNA Server may hang when stopping the active connection to 
the host.  To correct this, obtain a software update for the 
Windows NT version 3.1 DLC.SYS device driver from Microsoft 
Support Services (Windows NT bug #4463).  The workaround is 
to use a single-CPU system for 802.2 connections.


C.4. Windows NT memory leak after thousands of logged messages
--------------------------------------------------------------

If a component continually logs into the Windows NT event 
log, Windows NT may eventually run out of memory.  The only 
realistic scenario where this may occur with SNA Server is 
running an APPC or CPI-C transaction program that performs 
thousands of TP_STARTED and TP_ENDED verbs over time.  The 
Windows NT EVENTLOG.EXE module has a very small memory leak. 
To correct this problem, obtain a software update from 
Microsoft Support Services (Windows NT bug #4415).  A 
workaround is to set the logging level to "Audit logging 
disabled" in SNA Server Admin.


C.5. Occasional access violation when stopping SNA Server
---------------------------------------------------------

A very uncommon access violation can occur with SCREG.EXE 
when you stop an SNA server (via SNA Server Admin or by 
stopping the SnaServer service in the Windows NT Control 
Panel).  When this happens, a pop-up message appears, 
identifying SCREG.EXE as the cause of the access violation.  
To correct this problem, obtain a software update for 
Windows NT version 3.1 from Microsoft Support Services 
(Windows NT bug #3716).  The workaround is to restart 
Windows NT.


C.6. SNA Server compatibility with Windows for Workgroups
-----------------------------------------------------------

Windows for Workgroups is available in versions 3.1 and 3.11.  
There are certain limitations in using the SNA Server 
Windows-based client software with IBM PC Support functions 
(for AS/400 connectivity) with Windows for Workgroups:

* If you are running the real mode (MS-DOS) redirector 
  provided with Windows for Workgroups, and running the 
  PC Support functions in MS-DOS (that is, Windows for 
  Workgroups is not loaded), and you are not running over 
  the IPX/SPX transport, then you must add the entry 
  MAXCMDS=10 to the [networks] section of the SYSTEM.INI 
  file, and start the redirector with the following command:
  NET START FULL

With Windows for Workgroups version 3.1, you must use the 
following configuration when using PC Support functions or 
other software that requires the PC Support router API:

* Use the SNA Server MS-DOS-based client, not the 
  Windows-based client, and
* Run Windows for Workgroups in standard mode, not enhanced 
  mode.

With Windows for Workgroups version 3.11, the following
rules apply for AS/400 connectivity:

* You can use the PC Support functions by starting all the
  necessary SNA Server MS-DOS-based client components 
  (SNABASE, ROUTER) from an MS-DOS command prompt of Windows 
  (or in MS-DOS by exiting from Windows for Workgroups).  
  Windows programs cannot access the router API in this 
  configuration; you must use only the IBM PC Support 
  functions (such as the "WSF" function for 5250 emulation).

* When using SNA Server client software to communicate with 
  an AS/400, you should use applications (including 5250 
  emulators) that use the Windows APPC API, and avoid 
  applications that use the IBM PC Support router API.  

  Note that using the Windows APPC API means that terminate-
  and-stay-resident software is avoided, making the local 
  system environment simpler and more robust.

  Many 5250 emulators do not require the IBM PC Support 
  router, but instead use the Windows APPC API.  Examples 
  of 5250 emulators that do not require the PC Support 
  router are the SNA Server 5250 Applet and other 5250 
  emulators listed in the SNA Server Companion Product 
  Catalog.


C.7. Limit of active connections with LAN Manager clients
---------------------------------------------------------

When you run SNA Server client software on a system running 
MS-DOS or Windows version 3.x with the LAN Manager 
redirector, unexpected behavior may occur if you exceed the 
number of maximum supported active network connections (some 
systems are known to fail).  Check the number of network 
connections you have active before starting SNA Server 
client software--the standard maximum number for total 
connections is 10, and SNA Server requires a minimum of 2.  
The workaround is to delete a few network connections before 
starting the SNA Server client software.  Note that this is 
not an issue with Windows for Workgroups or NetWare(R).

The "numresources" entry in the [workstation] section of 
LANMAN.INI can be increased to allow a greater number of 
connections.  For example:

[workstation]
   numresources = 13

SNA Server typically requires two to four numresources, and 
each network connection requires one; the number specified 
in LANMAN.INI should be adjusted accordingly.  For more 
information, see your LAN Manager administrative 
documentation.


C.8. Removing SNA Server components on Windows NT
-------------------------------------------------

SNA Server device drivers (such as the IBM SDLC driver) 
should not be removed with the Network option of the 
Windows NT Control Panel.  Doing so may result in unexpected 
behavior, for which the only known solution is to remove and 
reinstall SNA Server.  Instead, use the SNA Server Setup 
program to remove the component.


C.9. Interoperability with certain APPN Network Nodes
-----------------------------------------------------

When establishing a connection between an SNA server and 
certain implementations of APPN Network Node, there is a 
possible problem with XID exchange.  The problem only occurs 
with APPN Network Nodes, not PU 2.0 nodes or PU 2.1 nodes 
that are LEN or APPN END nodes.  There are no released 
implementations of APPN Network Nodes that present the 
problem--the problem was found in testing prerelease 
versions of certain vendors' APPN routers at the Interop 
show.

The problem consists of the following:

* The partner system is a (new) APPN Network Node other 
  than a 37x5, a 3174, a mainframe, or an AS/400 build 
  based on the IBM APPN reference implementation.
* The connection stays Pending and never becomes Active.
* A connection trace indicates that the partner Network Node 
  rejects the XID offered by SNA Server.

A software update that corrects the problem (SNA Server bug 
#1579) is available from Microsoft Support Services or the 
MSSNA forum on Compuserve.


C.10. 3270/5250 model type limitations with certain monitors
------------------------------------------------------------

With the SNA Server 3270 and 5250 Applets, certain emulated 
screen sizes are not workable for many monitors, due to the 
limitations of the font used.  For example, with the 3270 
Applet, 3178/79 display model 5 emulation may not display 
correctly; with the 5250 Applet, the 132x27 character screen 
size may not display correctly.  The workaround is to resize
the screen to remove the font repainting problem, use a 
smaller model type, or use a video adapter/monitor with a 
higher resolution.


C.11. Only one IBM MPA/A adapter supported per system
-----------------------------------------------------

Although you can install two IBM MPA/A adapters in a Micro-
Channel computer, SNA Server supports only one--this adapter 
must be installed as the "first adapter."  If you need more 
than one SDLC or X.25 adapter per system, the workaround is 
to use one of the third-party adapters listed in the SNA 
Server Companion Product Catalog.


C.12. 3270 Applet file transfer abort button problem
----------------------------------------------------

If you start a 3270 file transfer when the host session is 
not in a state in which a file transfer command is supported 
(such as in an SPF window on TSO), the abort button on the 
file transfer status dialog does not work and the 3270 
Applet appears stopped.  However, the file transfer will time 
out after the configured time-out period (the default is 120 seconds) 
and the emulator will return to normal state.

The abort button works correctly on successfully started
file transfers.


C.13. Compaq Netflex adapter appears as Ethernet
------------------------------------------------

After installing and configuring an SNA Server 802.2 DLC 
link service and connection over a Compaq(R) Netflex adapter, 
the SNA Server Admin program shows the 802.2 connection 
as Ethernet, even though the Netflex adapter is token ring. 
This is a problem of appearance only, since the Netflex 
adapter automatically detects the media type, and any 
network software (including SNA Server) will continue to 
work correctly.

The workaround for this is as follows:

1. Before running SNA Server Setup to install an 802.2 DLC 
   link service, start REGEDT32.

2. Change to HKEY_LOCAL_MACHINE/System/CurrentControlSet/
   Services/Netflx02/Parameters/MediaType.

3. Change MediaType from 1 (Ethernet) to 0 (Token Ring).

After this change, SNA Server Setup will properly detect the 
Netflex adapter as a token ring adapter.


C.14. NMVTs not supported from a downstream client
--------------------------------------------------

If an SNA Server is configured to support a downstream 
system, and that system sends an NMVT (such as an Alert), 
the NMVT will not be passed on to the configured NMVT 
connection.  This is a bug in SNA Server that will be 
fixed in a future release.  All other NMVT and NetView
features work as documented.


C.15. 5250 applet configuration dialog problem
----------------------------------------------

If you are using the 5250 applet on a Windows version 3.x
client, note that the "Session Configuraion" menu option
under the "Session" pull down will work only once after
the 5250 applet is started.  Subsequent attempts to enter
into the dialog fail - the dialog is simply not displayed.
However, all changes made in the dialog work as expected.

This is a known bug and a software update which corrects
this situation will be made available through Microsoft
Support Services.

The workaround is to restart the 5250 applet, after which
the dialog will work again (once).


C.16. Pop-ups indicating user-limit exceeded queue up
-----------------------------------------------------

SNA Server is available in 10-, 64- and 250-user versions.
The server software checks how many actual worksations are
connected to the server and will only allow the licensed
number of workstations access to the server at one time.

If the server is operating at the limit, the subsequent
workstations attempting to connect to the server will not
be allowed access and will receive a pop-up telling the
user that the licensed server limit has been exceeded.
The pop-up is also displayed at the server.  If the client
keeps retrying the connection, the pop-ups will be queued
up both at the client and at the server which may be an
annoyance to the user and the administrator.

The workaround is to disconnect the client application 
and thus prevent it from retrying the server connection
or to upgrade to a server with a greater license limit.



D. Additions and corrections to the SNA Server documentation
------------------------------------------------------------

D.1. Additions to the "SNA Server Installation Guide"
-----------------------------------------------------

D.1.1. SNA Server memory requirements
-------------------------------------

The memory figures listed here represent the minimum needed; 
more memory may be required for optimum performance, when 
heavy demands are placed on a server, or when several server 
applications are used at the same time.

Minimum total RAM requirement - server:

 SNA Server on Windows NT...........................16 MB
 SNA Server on Windows NT Advanced Server...........20 MB

 The above numbers are 4 MB above the required minimums 
 for Windows NT and Windows NT Advanced Server.  Microsoft 
 highly recommends that the server be equipped with enough 
 RAM for optimum performance.  32 MB total system RAM has 
 proven to be sufficient for all uses in our testing.

Minimum total RAM requirement - Windows NT client...14 MB

This is 2 MB above the required minimum for Windows NT.

Actual RAM occupancy - MS-DOS and Windows v3.x clients:

 SNA Server client running MS-DOS
 - Base support for IBM PC Support functions........100KB
 - Base support for ISV 3270 emulator................50KB
 - Base support for APPC/LUA-RUI/CSV application.....50KB
 SNA Server client running Windows version 3.x
 - 3270 Applet......................................525KB
 - 5250 Applet......................................490KB
 - 3270 and 5250 Applet loaded at the same time.....830KB
 - Base support for ISV 5250 emulator...............185KB
 - Base support for ISV 3270 emulator...............185KB
 - Base support for APPC/CPIC/LUA/CSV application...185KB

 The above numbers represent actual RAM used when loaded.
 The base support does not include the application itself 
 (such as the IBM PC Support components) or the SNA Server 
 API DLLs loaded by the application.

 Downstream clients obviously require no SNA Server 
 client components; the RAM requirement is the actual 
 memory taken by the 3270 emulator or other downstream 
 application.

Hard disk requirements:

 SNA Server server only............................8.0 MB
 SNA Server including clients.....................18.0 MB  
  (for over-the-network client setup)
 SNA Server client running Windows NT..............7.5 MB
 SNA Server client running Windows.................2.0 MB
 SNA Server client running MS-DOS..................1.0 MB
 SNA Server client running OS/2....................1.5 MB


D.1.2.  Removal required of old beta versions of SNA Server
-----------------------------------------------------------

Before installing SNA Server, be sure to remove any prior 
installation of the SNA Server beta (or Comm Server), both 
on the server and on the clients.  To do this, run the copy 
of SETUP.EXE located in the existing SNA root directory, (by 
default, C:\SNA\SETUP.EXE) and select "Remove SNA Server."

Note that this step deletes the existing SNA Server 
configuration that you had been using.  It is recommended 
that you allow this deletion for any beta installation, and 
then recreate your configuration after installing this 
release (rather than using the configuration created with a 
beta release).

SNA Server can read and convert Comm Server configuration 
files, and allows Comm Server client software to connect to 
SNA Server.  For more information, see the "SNA Server 
Installation Guide."


D.1.3. Installing SNA Server client software on a shared
       network directory
---------------------------------------------------------

SNA Server clients running the Windows version 3.1 operating 
system can be set up to run the SNA Server client software 
from a shared network directory.  Such a client may, but 
does not have to, run its operating system (Windows 3.1) 
from a shared network directory.  If a shared directory is 
used for the Windows system, it should be a different 
directory than the one used for the SNA Server client 
software.

When installing SNA Server client software for systems that 
will run the software from a shared network directory, be 
sure to log on with a user name that has read and write 
access to the Windows system directories, wherever they are 
located.  You must be logged on in this way in order to 
carry out steps 3-8 of the following procedure:

1. On the server from which the SNA Server client software 
   will be run, create and share a directory for the 
   software.

2. At one of the computers that will run SNA Server client 
   software from the shared network directory, connect to 
   the shared directory, specifying an appropriate drive 
   letter (such as g: or x:).

3. On the same computer as step 2, start SNA Server Setup in 
   one of two ways:

   * Alternative A: Insert the SNA Server CD or the 
     appropriate floppy disk in the drive of the client 
     system.  Then, in Program Manager, choose the File 
     menu Run command, and type the following:

     <drive>:setup /a

     In this command, substitute the letter for the floppy 
     disk drive or CD-ROM drive for <drive>.  

   * Alternative B: Find out the server name of an installed
     SNA server.  Then, in Program Manager, choose the File 
     menu Run command, and type the following:

     \\<servername>\clients\win3x\setup /a

     In this command, substitute the server name of the SNA 
     server for <servername>.  

   With the /a (administrative) option, SNA Server Setup 
   installs the software needed for Windows clients to run 
   SNA Server from a shared network directory; at the same 
   time, Setup creates the first client.

4. Carry out the installation.  When prompted for the 
   destination for the SNA Server client software, type the 
   network drive letter assigned in step 2.

5. On any other Windows client that will run the SNA Server 
   client software from the shared network directory, 
   connect to the shared directory created in step 1, 
   specifying an appropriate drive letter (such as 
   g: or x:).

6. On the client chosen for the previous step, start SNA 
   Server Setup in one of the two ways explained in step 3, 
   and type one of the following:

   For installing from a floppy disk or CD-ROM drive, type

   <drive>:setup /n

   For installing from a shared network directory, type

   \\<servername>\clients\win3x\setup /n

   With the /n (network) option, SNA Server Setup creates a 
   client based on Windows version 3.1 that runs SNA Server 
   client software from a shared network directory.

7. Carry out the installation.  When prompted for the 
   location of SNA Server files on a network server, type 
   the network drive letter assigned in step 5.

8. Repeat steps 5-7 for each additional client that will run 
   the client software from the shared network directory.


D.1.4. Removing an SNA Server client from a network drive
------------------------------------------------------

When removing SNA Server client software from computers that 
run SNA Server from a shared network directory, be sure to 
log on with a user name that has read and write access to 
the Windows system directories, whether they are on the 
local system or in a shared network directory.  You must log 
on in this way to do either of the following:

* To remove the capability for a particular client system to 
  run SNA Server from a shared network directory, on the 
  client, follow the usual procedure for removing an SNA 
  client.  See the instructions in the SNA Server Setup Help 
  and/or the "SNA Server Installation Guide."

* To remove SNA Server client software from a shared network 
  directory (so that no clients can run from that   directory), 
  from a client, start SNA Server Setup with the /a option, 
  using one of the methods described in step 3 of the 
  previous procedure.  Then follow the instructions in Setup 
  for removing SNA Server client software.  For background 
  information about Setup, see the SNA Server Setup Help 
  and/or the "SNA Server Installation Guide."


D.1.5. IBM SDLC and token ring adapter notes
--------------------------------------------

Device drivers provided by SNA Server report any interrupt, 
port address, or DMA conflicts they detect to the Windows NT 
System event log.

If you are using an IBM SDLC or MPCA card in an ISA or EISA 
bus system, you should do the following:

* Disable SERIAL.SYS (which is enabled by default) to 
  prevent an interrupt conflict.  To do this, use the 
  Devices option in the Windows NT Control Panel.
* Disable any COM ports that use interrupts that conflict 
  with the IBM SDLC adapters.  This is normally done through 
  EISA configuration programs, CMOS setup programs, or 
  jumpers on the motherboard.

The IBM SDLC adapter has a known hardware conflict with the 
Microsoft Windows Sound System adapter--both attempt to use 
the same I/O address on the bus, which makes these adapters 
incompatible on the same PC.  The Sound System adapter must 
be removed from the PC in order for the IBM SDLC adapter 
to work.

If you are using an IBM token ring adapter in an ISA or EISA 
bus system, you should do the following:

* By default, Windows NT loads PARALLEL.SYS during 
  initialization.  To avoid interrupt conflicts between 
  PARALLEL.SYS and IBMTOK.SYS, the IBM Token Ring device 
  driver, be sure to choose an interrupt other than 7 on 
  your IBM Token Ring card, or disable the Parallel driver 
  services by using the Devices option in the Windows NT 
  Control Panel.
* Disable any parallel ports that use interrupts that 
  conflict with the IBM Token Ring cards.  This is normally 
  done through EISA configuration programs, CMOS setup 
  programs, or jumpers on the motherboard.


D.2. Additions to the "SNA Server Administration Guide"
-------------------------------------------------------

D.2.1. Remote Control Point and Network names
---------------------------------------------

A common cause of connection difficulties with a new 
configuration is that the same names have been specified for 
both local and remote Control Point and Network names.  

In SNA Server Admin, the local Control Point and Network 
names are set in a different dialog box than the remote 
Control Point and Network names.  The local Control Point 
Name and Network Name apply to all connections, and are set 
in the Server Properties dialog box.  The remote Control 
Point Name and Network Name for a particular connection are 
set in the Connection Properties dialog box.  For more 
information, see the "SNA Server Administration Guide."


D.2.2. APPC LU Name need not be unique
--------------------------------------

The definitions for APPC LU Name shown in Chapter 5 of the 
"SNA Server Administration Guide" state that "The name 
cannot be the same as any other APPC LU name in your 
installation."  This should be amended to read "The LU Name 
can be used multiple times on a server, as long as each LU 
has a unique LU Alias on that server."


D.2.3. Multidrop SDLC configuration notes
-----------------------------------------

The following modifications should be made to Chapter 3 of 
the "SNA Server Administration Guide," regarding multidrop 
SDLC configuration:

* In all places where it says that multidrop can be used 
  with peer or downstream systems, the word "peer" should be 
  ignored.  Multidrop configurations can be set up for 
  downstream systems, but not peer systems.

* The note at the end of "Steps for Configuring Multidrop 
  Connections" is incorrect and should be ignored.  The note 
  states that SNA Server copies changes between multidrop 
  connections that share the same link service, which is not 
  true.


D.2.4. Default connection for the APPC DISPLAY verb
---------------------------------------------------

The "SNA Server Administration Guide" claims that you must 
define a connection for the APPC DISPLAY verb.  Actually, 
SNA Server will randomly select a default connection for the 
DISPLAY verb to use if one is not explicitly configured.


D.2.5. NetView(R) support notes
-------------------------------

The following sections provide information about the NVAlert 
and NVRunCmd services that was not provided in the "SNA 
Server Administration Guide."


D.2.5.1. Startup settings for NVAlert and NVRunCmd
--------------------------------------------------

By default, the NVAlert and NVRunCmd services have a Startup 
setting of "Manual." To arrange for them to start up every 
time the Windows NT system is started, use the Services 
option in the Control Panel to change the Startup settings 
to "Automatic."


D.2.5.2. Code page settings for NVAlert and NVRunCmd
----------------------------------------------------

You can control the host code page and local code page used 
by NVAlert and NVRunCmd.  NVAlert and NVRunCmd use the same 
host code page as is set in the SNA Server 3270 Applet; the 
default is United States (037).

To change the host code page for NVAlert and NVRunCmd:

1. On the server on which NVAlert and NVRunCmd are run, 
   start the SNA Server 3270 Applet by double-clicking the 
   icon.
2. From the Session menu, choose Session Configuration.
3. In the 3270 Settings dialog box, select the intended Host 
   Code Page.
4. Choose OK.  The new host code page takes effect for 
   NVAlert and NVRunCmd when they are restarted.

NVAlert and NVRunCmd use the same local code page as is set 
in Windows NT.  To change the local code page, see the 
instructions for the Language field in the International 
option of the Control Panel, as described in your Windows NT 
documentation.


D.2.5.3. Security context for NVRunCmd
--------------------------------------

The NVRunCmd service runs by default in the local system's 
security context.  As a result of this, some commands may 
generate responses different from those generated by a user 
logged on at the same Windows NT-based system.  Examples of 
such commands are NET USE and CHDIR typed without options.  
When run via NVRunCmd, these commands generate a display 
relative to the context for NVRunCmd, not the context for a 
logged-on user.


D.2.5.4. NVALERT.INI Notes
--------------------------

In the description of the format of NVALERT.INI found 
in Appendix C of the "SNA Server Administration Guide," 
some changes should be made on pages 252 and 254.

The following changes should be made on page 252:

* For all occurrences of xx, the value that should be
  specified is 00.
* The paragraph at the bottom of the page ("For the xx and 
  yy variables...") should read as follows:

  For the yy variable, replace yy with a Data ID code 
  point, as described on p 9.161 of the IBM SNA Formats 
  manual (IBM doc GA27-3136-12) or other NetView 
  documentation.

On page 254, in the table, the line for UserDetData should 
read as follows:

UserDetData = 00, 95, %C


D.2.6. Changing the primary SNA server
--------------------------------------

If you want to designate a different server as the primary 
SNA Server in a domain, do the following:

1. On the original primary SNA server, in SNA Server Admin, 
   use the File menu Backup command to back up the 
   configuration file.

2. Exit from SNA Server Admin.

3. At the Windows NT command prompt, type

   NET STOP SNABASE

4. On the server that will become the primary SNA server, 
   run SNA Server Setup and, in the Change SNA Server Role 
   dialog box, select the Primary Configuration Server 
   option.

5. On the primary SNA server (configured in step 4), start 
   SNA Server Admin.

6. From the File menu, choose Restore, and select the backup 
   configuration file saved in step 1.


D.2.7. Changing the domain of an SNA server that uses
       NetWare support
-----------------------------------------------------

To change the domain of a Windows NT-based SNA server that 
uses NetWare support:

1. On the SNA server, at a command prompt, type

   NET STOP SNABASE

2. Use the Control Panel to change the domain of the SNA 
   server.

   For information, see your Windows NT documentation.

3. At a command prompt, type

   REGEDT32

   This starts the Registry editor.

4. Change to the following location in the Registry:

   HKEY_LOCAL_MACHINE
     SYSTEM
       CurrentControlSet
         Services
           SnaBase
             Parameters

5. Change the value for SnaDomain to the new domain name.

   The SNA server is now a member of the new domain.

6. Close the Registry editor.

7. At a command prompt, type

   NET START SNABASE


D.3. Corrections to the "SNA Server 3270/5250 Applet 
     User's Guide"
-----------------------------------------------------

D.3.1. Keyboard mapping notes
-----------------------------

In the Appendix, the character tables for ASCII, ANSI, and 
the IBM Extended Character Set are incorrect, and should not 
be used.  The tables in the online help are correct.

In the Appendix, in the 3270 Applet Keyboard Map, the 
following corrections should be made to the respective 
lines:

  3270 keyboard    Enhanced 101 keyboard
  --------------------------------------
  DUP              CTRL ALT INSERT
  SYSTEM REQUEST   CTRL+S

In the Appendix, in the 5250 Applet Keyboard Map, the 
following correction should be made:

  5250 keyboard    Enhanced 101 keyboard
  --------------------------------------
  SYSTEM REQUEST   CTRL+S
                   ALT+NUM(*)


D.4. Additions to the "SNA Server Reference"
--------------------------------------------

D.4.1. Missing error messages
-----------------------------

Error messages 684, 685, and 3032 are included in SNA Server,
but are not listed in the "SNA Server Reference."

Message 684

A buffer pool audit has been triggered by
value
value
value

EXPLANATION
This audit contains information about the size of the buffer 
pool, how many headers and elements each process is using, 
etc.

ACTION
None, unless there is some other problem.  In that case, 
report this log along with any others.

Message 685

An attempt was made to extend a buffer pool, but the related 
pool had reached its maximum size.  The component is 
terminating, and an audit of the buffer pools just before 
termination is attached.

Audit Information Here

EXPLANATION
This error is almost always due to an SNA component 
(including possibly an emulator) losing buffers.

ACTION
Contact your support personnel.

Message 3032

A Windows CPI-C application tried to start a conversation 
before issuing WinCPICStartup.

EXPLANATION
An illegal sequence of API calls has taken place.

ACTION
Change the program logic to issue the WinCPICStartup call
before any other CPI-C call.


D.4.2. Notes regarding Registry and environment variables
---------------------------------------------------------

In Appendix C of the "SNA Server Reference," on page 185, 
there is a table that tells how to set Registry and 
environment variables.  The second-to-last line in the table 
should read:

MS-DOS                            Add or change lines in the 
with SNA Server client            SNA.INI file


In addition, the following variables should be added to 
Appendix C of the "SNA Server Reference."  (In Appendix C, 
note that the mentions of DWORD should be replaced with 
REG_DWORD.)

D.4.2.1. Unique5250Names
------------------------

This variable can be set on an SNA server only and is found 
in the following location in the Registry:

HKEY_LOCAL_MACHINE
  SYSTEM
    CurrentControlSet
      Services
        SnaServr
          Parameters

This is the variable name and description:

Unique5250Names:REG_SZ:NO

  When this variable is set to NO, SNA Server will not 
  ensure that session IDs generated by 5250 emulators are 
  unique.  Otherwise, SNA Server will substitute a unique 
  session ID if any 5250 emulator generates a duplicate ID. 

  When a 5250 user establishes a session with an AS/400, a 
  unique device name is required.  Unless an override is 
  sent, the AS/400 will generate the name by taking the 
  Local LU and appending a two-byte session ID sent by the 
  emulator.  A session ID generated by an emulator is 
  usually not unique, since the emulator does not have 
  information about the session IDs used by other active 
  emulators.  Therefore, by default, SNA Server alters the 
  session IDs as they are sent out to ensure uniqueness.  
  This is the recommended behavior, but it can be disabled 
  by setting this Registry variable to NO.


D.4.2.2. BufferAuditInterval
----------------------------

This variable can be set on an SNA server or a Windows 
NT-based client, and is found in the following location in 
the Registry:

HKEY_LOCAL_MACHINE
  SYSTEM
    CurrentControlSet
      Services
        SnaBase
          Parameters

This is the variable name and description:

BufferAuditInterval:REG_DWORD:<interval in seconds>

  This variable causes SNA Server to carry out audits of the 
  buffer pool at regular intervals, and sets the interval 
  length in seconds.  (SNA Server rounds the number of  
  seconds upward to the nearest five seconds.)  The range 
  for <interval in seconds> is 1 through 0xFFFFFFFE.

  Normally (that is, when this variable is not set) SNA 
  Server only carries out buffer audits when a buffer pool 
  is extended.

  When SNA Server carries out a buffer audit, the 
  information is placed in message 684 in the application 
  event log.


D.4.2.3. OtherServers
---------------------

This variable can be set on a client running Windows NT, 
Windows version 3.1, or MS-DOS.

For a client running Windows NT, the OtherServers variable 
is found in the following location in the Registry:

HKEY_LOCAL_MACHINE
  SYSTEM
    CurrentControlSet
      Services
        SnaBase
          Parameters

For a client running Windows NT, the variable is specified 
as follows.  When specifying the variable, substitute one or 
more server names for <server1> [<server2>][ ...].  Separate 
multiple server names with spaces.

OtherServers:REG_MULTI_SZ:<server1> [<server2>][ ...]

For a client running Windows version 3.1, the OtherServers 
variable is set in WIN.INI.  For a client running MS-DOS, 
the OtherServers variable is set in SNA.INI.  With both 
these operating systems, the variable is specified as 
follows.  When specifying the variable, substitute one or 
more server names for <server1> [<server2>][ ...].  Separate 
multiple server names with spaces.

OtherServers=<server1> [<server2>][ ...]

The variable has the following effect (regardless of 
operating system):

  This variable specifies one or more SNA servers outside of 
  the client's domain, to which the client's requests for 
  LUs will be sent, if the requests cannot be satisfied by 
  SNA servers in the client's domain.  If this variable is 
  not set, only SNA servers in the client's domain will 
  receive the client's requests for LUs.


<end of README.TXT>
