Ref: 99980094
Title: SW/200-TCP-NCS/2 Version 20100
Date: 4/25/88

Copyright 3Com Corporation, 1991.  All rights reserved.

This release memo lists the new features and fixed bugs since SW/
200-TCP-NCS/2 Version 20000.


.h1;Compatibility

SW/200-TCP-NCS/2 Version 20100 can operate with the following
3Com products and software releases:

    NCS/150 running SW/150-TCP-NCS Version 11000 or later
    NCS/AT running SW/AT-NCS Version 11000 or later
    NCS/2 running SW/2-NCS Version 10000 or later
    CS/1 running SW/1-TCP Version 20000 or later
    CS/1 running SW/20-TCP Version 20000 or later
    CS1-SNA running SW/1-T-SNA Version 13000 or later
    CS/50 running SW/50-TCP Version 13010 or later
    CS/100 running SW/100-TCP Version 20000 or later
    GS/3-IP running SW/3-IP Version 10000 or later
    GS/1-IP running SW/20-IP-X.25 Version 10000 or later
    IVECS running SW/IVECS-TCP Version 13010 or later
    Personal computer running TCPTerm version 10010 or later
    Personal computer running SW/1-PCS Version 10010 or later

The following table illustrates the hardware and firmware
compatability requirements of SW/200-TCP-NCS/2 Version 22000.

               Hardware/Firmware Compatibility
------------------------------------------------------------------
Product                Software                     Firmware

CS/210       SW/200-TCP-NCS/2 Version 20100   F2MMON 01D or later

CS/200       SW/200-TCP-NCS/2 Version 20100   C1MMON 01C or later

CS/200-B     SW/200-TCP-NCS/2 Version 20100   D2MMON 00B or later

.h1;Installation

Refer to the NCS/2 Installation and Operation Guide for
instructions for installing SW/200-TCP-NCS/2 Version 20100 from
the distribution diskette to the NCS/2.

The CS/200 or CS/210 must be bound to the NCS/2 by the BInd
command before it can be booted from the NCS/2.  Refer to the NCS/
2 Installation and Operation Guide for information on the binding
procedure.

                        ** NOTE **

If you need to press the Reset switch on the CS/210, do so
only when the prompt (e.g., Monitor prompt, Remote prompt) is
displayed on the screen.  Pressing the Reset switch before
the prompt appears may yield unpredictable results.

.h1;New Features

The following features, which were not present in SW/200-TCP-NCS/
2 Version 20000 or earlier, have been implemented in SW/200-TCP-
NCS/2 Version 20100:

1.  SW/200-TCP-NCS/2 Version 20100 can be used on the CS/210,
which supports 31/2-inch floppy disk drive.  The CS/210 can
be booted either from the local diskette or an NCS.  It can
also store to and retrieve from the local diskette the
macros, configurations, and global parameters.

Firmware configuration can be done on the CS/210 to determine
whether it will be booted from the local diskette or an NCS.
The boot source determines the origin of the macros,
configurations, and global parameters are requested from.
For more information about firmware configuration, refer to
the Series/200 Installation Guide dated June 1988.

2.  The LongBReakAction port parameter now works for ports
configured as Host and ports configured as Terminal.

3.  The XmitBinary parameter, which is a Telnet port parameter,
now works for ports configured as Host and ports configured
as Terminal.

4.  The SHow SESsion command has a new option, M.  This option
displays the Internet address and the TCP port number of the
foreign side of a connection.  The new syntax for the SHow
SESsion command is as follows:

    SHow (!<port number>) SESsion M

For example, if you enter this command:

    sh (!1) ses m

the screen display generated is similar to the following:

    CONCTD from 192.003.013.004:002:024

This display shows that port 1 of the host server is
connected from the terminal server whose Internet address is
192.003.013.004.  The number 024 is the number of the
physical port on this terminal server used in this
connection.  The number immediately following the Internet
address ("002" in this example) has no meaning and should be
disregarded.  This feature works only if the server is a
Communications server manufactured by Bridge.

5.  The FlowControlFrom and FlowControlTo parameters can be set
to ENQ_ACK.  Hewlett-Packard terminals and hosts use this
flow control method.

6.  Sysgen is available for the CS/200 and CS/210 running SW/200-
TCP-NCS/2 Version 200100.  Refer to the sections on the CS/
200 in the Configuration Guide (February 1988 edition) for
Sysgen information on the CS/200 and CS/210.

.h1;Bugs Fixed

The following is a list or problems that existed in SW/200-TCP-
NCS/2 Version 20000 but have been fixed in SW/200-TCP-NCS/2
Version 20100:

1.  The "SHow NAmes*" command is no longer allowed when Nstype is
set to DOMAIN.  Previously, the system might crash when
responding to this command.

2.  Previously, when there were more than three of four permanent
virtual circuits on a single server, the reliability of these
circuits was reduced.  This problem no longer exists.

3.  A problem that eliminated "keep-alive" TCP packets could
cause one end of a connection to remain indefinitely when the
server on the other end had been rebooted.  This has been
fixed.

.h1;Limitations

The following is a list of limitations of SW/200-TCP-NCS/2
Version 20100:

1.  At the time when the CS/200 or CS/210 running SW/200-TCP-NCS/
2 makes a conection, the routes are established using the
default gateway.  Changing the default gateway after
connection does not affect the already established routes.

You can, however, use the ZeroArp command to clear out the
gateway table stored in the server.

2.  Macros are cached in local memory on the CS/200.  If you
change or delete a macro, there is no guarantee that the
change will flush the macro cache.  This can cause unexpected
results when macros are executed.  To ensure proper execution
of macros, use the ZeroMacro command to explicitly flush the
local cache after changing or deleting a macro.

If the CS/200 receives file service, which includes macro
file service, from an NCS, it is recommended that you flush
the macro cache in each Communications Server bound to the
NCS every time a macro is changed or deleted on the NCS.  If
an NCS/150 is providing the file service, use the REMOTE
command to access each CS/200 bound to the NCS/150, and then
use the ZeroMacro command on each CS/200 to flush the macro
cache.  If an NCS/2 or NCS/AT is providing the file service,
use the oneachserver utility on the NCS.  For example, at the
utility prompt of the NCS/AT or the NCS/2, enter the
following command:

    oneachserver -B zm

.h1 Known Problems

The following is a list of known problems in SW/200-TCP-NCS/2
Version 20100:

1.  If the remote end of an inactive session is disconnected, the
SHow SESsions and SHow AllSessions commands still show that
the local end is connected.  The disconnection message
appears only if a user resumes that session.  This problem
does not occur on an active session.

2.  When you use the IEN116 Name Server, a network manager
command (e.g., SHow (<name>) VERSion) does not operate
correctly if <name> is not defined on a primary name server
and a secondary name server if defined.  In this case, the CS/
210 may crash.

3.  When an invalid name is passed to the domain name resolver,
"(primary)" is appended to the error message although it is
not necessary.

For example, if the following command with the invalid name
is entered:

    sh na a...b

the following message appears:

    Resolving...Resolver: improper name (primary)

4.  Sometimes the "improper name" error message is not ended with
a return character.  As a result, the prompt appears on the
same line as the error message.

For example, if the following command with the invalid name
is entered:

    connect a..b

the following appears on the screen:

    Connecting...Revolver: improper namesCS/200T)

In this example, "CS/200T> is the prompt.

5.  The "SHow NAmes *" command is not allowed.  A name must be
supplied to the command.

6.  Pressing the Break key during disk access may yield
unpredictable results.  For example, after entering the "sh
macros" command, it you press the Break key before the system
returns the results and then you enter the "sh confs"
command, a list of macro names is still displayed, instead of
a list of configuraiton file names.

7.  After a fatal error occurs on the CS/210, the attempt to
upload the image from the CS/21- to the NCS yields
unpredictable results if the firmware configuration parameter
Auto-rebott has been set to "Upload then reboot."  To avoid
this problem, perform firmware configuration to set the
parameter to either "Reboot only" or "Boot monitor."  Setting
the parameter to "Boot monitor" allows you to save a memory
dump on a diskette after the CS/210 has crashed.

.h1;Sample Macros With Conditional Statements

The SW/200-TCP-NCS/2 distribution diskette includes a package of
files that provide sample macros containing conditional
statements.  If you want to examine these sample macros, or you
want to edit and define these macros on your system, follow the
instructions below:

1.  Follow the instructions in the NCS/2 Installation and
Operation to log in to the NCS/2.  A command prompt appears
on the screen after you have logged in.

2.  Before defining the sample macros on your system, be sure
that the names of these macros do not conflict with those of
the existing macros.

    *   connect
    *   connect.menu
    *   disc
    *   error
    *   exit
    *   get
    *   login
    *   m1
    *   m2
    *   master
    *   master.menu
    *   motd
    *   newlogin
    *   res
    *   setup
    *   term.menu
    *   term.sel

If there are conflicts in macro names, you must rename your
current macros.

3.  Type the following command to enter utility mode:

    ut

4.  After the utility prompt appears, use the following command
to change directory:

    cd /usr/ncs/local

5.  Type the following to unpack the sample macros into
individual files:

    cmac_src_unpac

This message, which is followed by a list of the macro names,
appears:

    unpacking conditional macro source into /usr/ncs/local/
    cmac.src

If the message above does not appear and the system displays
the "command not found" message, enter the following command:

    rehash

Then after the utility prompt appears again, repeat this
step.

6.  After the prompt appears, use the following command to change
directory:

    cd cmac.srs

7.  Use a text editor (e.g., vi) to edit each file in the
cmac.src directory.  Editing is necessary because some sample
macros contain host names and terminal control sequences that
are not applicable to your site.

After you have edited a macro, you must delete unnecessary
spaces in the file so that each macro file does not exceed
256 characters.

8.  After you finish editing the macros in the cmac.srs
directory, use the following command to change directory:

    cd /nsr/ncs/locl

9.  After the prompt appears, type the following command:

    mac_mkinstall

This command creates a shell script file that can be used to
define the modified macros.  The following message is
displayed for each macro in cmac.src:

    installing <name>

where <name> is the name of the macro.

10. After the prompt appears, type the following command to
define the macros:

    install.newmacs

The following message is displayed for each macro defined:

    macro <name> created

where <name> is the same of the macro.

11. The process of creating the macros is finished when the
utility prompt appears again.  The macros are now on the NCS/
2, ready to be invoked.

If you encounter problems with the sample macros and wish to
undefine them all, type the following command at the NCS/2
utility prompt.

/usr/ncs/locl/cmac_uninstall

.h1;Documentation

Refer to the following manuals for information on the CS/200, CS/
210, and network planning:

*   Series/200 Installation Guide (6/88)
    (Part Number: 09-0060-02)

*   Connection Service User's Guide (11/87)
    (Part Number: 09-0063-02)

*   Connection Service User's Quick Reference Guide (12/85)
    (Part Number: 09-0062-00)

*   Network Management Guide (9/87)
    (Part Number: 09-0067-02)

*   Configuration Guide (2/88)
    (Part Number: 09-0093-01)

*   Getting Started Guide (2/87)
    (Part Number: 09-0043-01)

*   LAN Planning Guide (2/88)
    (Part Number: 09-0085-01)

*   NCS/2 Installation and Operation Guide (2/88)
    (Part Number: 09-0110-01)

If you have any questions, please contact an authorized 3Com
service representative for help.

