Ref: 99960065
Title: ESD REL.NOTE:SW/20-A/BSC/SDLC-NCS/1 VER.22010 PART#:86-0196-00
date: 03-01-89

Copyright 3Com Corporation, 1991.  All rights reserved.

3Com Corporation
Software Release
SW/20-A/BSC/SDLC-NCS/1 Version 22010
March 1, 1989

Part Number: 86-0196-00
             Revision 01

TO:  CS/1 Users
FROM: 3Com Corporation
SUBJECT: SW/20-A/BSC/SDLC-NCS/1 Version 22010
DATE: March 1, 1989

Enclosed is a distribution tape cartridge containing SW/20-A/BSC/SDLC-
NCS/1 Version 22010 (part number: 83-0166-03).  This software, which
is an updated version of SW/20-A/BSC/SDLC Version 22000, is to be used
by an MCPU20-based CS/1 that is booted from an NCS/1.

This release memo describes the bugs fixed since Version 22000, and
the software's limi tations and known problems.

Compatibility

SW/20-A/BSC/SDLC-NCS/1 Version 22010 can operate with the following
products and software releases:

 CS/1 running SW/20-A/BSC/SDLC Version 22000 or later
 CS/1-SNA running SW/1-SNA Version 13010 or later
 GS/1-X.25 running SW/1-X.25 Version 14030 or later
 CS/200 running SW/200-A/BSC/SDLC Version 22000 or later
 CS/210 running SW/200-A/BSC/SDLC Version 22000 or later
 IVECS running SW/IVECS-A Version 20060 or later
 NCS/150 running SW/150-NCS Version 10010 or later
 NCS/AT running SW/AT-NCS Version 11000 or later
 IB/1, IB/2, and IB/3 running SW/20-IB Version 11000 or later
 Personal computer running SW/PCS-XNS Version 10000 or later

Table 1 illustrates the hardware and firmware compatibility for SW/20-
A/BSC/SDLC-NCS/1 Version 22010.

Table 1  Hardware/Firmware Compatibility

 Product Boards  PROMS

 CS/1    SIO-16  No PROMS

 CS/1    MCPU20  M3 MMON 00D or later

 CS/1    EC/2    M1 IECM 01F or later

If an Ethernet controller is used with the MCPU20-based CS/1, it must
be an EC/2 board with 512 kilobytes of RAM.  Also, the MCPU20 board
must operate with a 96-TPI disk drive.

Installing the Software

For instructions on installing SW/20-A/BSC/SDLC-NCS/1 Version 22010 on
the NCS/1, refer to "Installing Software" in the NCS/1 Installation
and Operation Guide.

Bugs Fixed

The following is  a list of problems that existed in SW/1-A/BSC/SDLC -
NCS/1 Version 22000 or earlier and have been fixed in SW/1-A/BSC/SDLC-
NCS/1 Version 22010:

Setting the EOM parameter to disabled no longer causes problems when
you trans  fer data to an X.25 host.  Previously, if you set this
parameter to disabled, it caused  the End of Message bit to be turned
on on every SPP packet.  This caused data forwarding problems.

Setting the ECMchar parameter to disabled on CS/1s using the SIO-16
board no  longer causes null characters to be transmitted in separate
packets.  Previously if  you set the ECMchar parameter to disabled,
each null character was sent to the CS/1
in a separate packet, increasing network traffic and data corruption.

Known Problems

The following is a list of Version 22010's known problems:

Due to a memory limitation, the SHow CONFigurationS and SHow MACros
commands no longer display output in alphabetical order.

On the SIO-16 ports, the help menu of the BAud parameter displays
LowAutoBaud  and HiAutoBaud as options of this parameter.  The SIO-16
boards, however,  support only single-range autobaud.  Setting the
BAud parameter to LowAutoBaud  or HiAutoBaud
does not affect the baud rate, which ranges from 50 to 38.4K.

Limitations

The following is a list of Version 22010's limitations:

The display generated by the SHow AllSessions command is limited to a
maximum  of 50 lines.

Only three echo requests may be outstanding at any given time.  If
more than three  users simultaneously enter the PIng command, the
following message appears:

 Can't Ping now - try later

Macros are cached in local memory on the CS/1.  If you change or
delete a macro,  there is no guarantee that the change will flush the
macro cache.  This can cause  un expected 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/1s on the network receive file service, including macro file
service, from  an NCS, you should 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  or NCS/1 is providing the file
service, use the REMOTE command to access each CS/1 bound to the NCS,
and then use the ZeroMacro command on each CS/1 to flush the macro
cache.  If an NCS/AT is providing the file service, use the utility on
the NCS/AT.

For example, at the utility prompt of the NCS/AT, enter the following
command:

 oneachserver -B zm

The Sysgen program is not available on the NCS/1 for SW/20A/BSC/SDLC
Ver  sion 22010.

The MacType parameter should not be set to IEEE.

Documentation

The following manuals are provided with SW/20-A/BSC/SDLC-NCS/1 Version
22010:

 Connection Service User's Guide for XNS and TCP/IP Protocols (6/88)
 Part Number: 09-0145-00

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

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

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

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

For more information on your CS/1 and network planning, refer to the
following manuals:

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

 CS/1 Installation Guide (10/87)
 Part Number: 09-0117-00

 NCS/1 Installation and Operation Guide (3/86)
 Part Number: 09-0065-00

If you have any questions, contact your network supplier or 3Com for
help.
^Z
