Ref: 99980101
Title: SW/1-A/BSC/SDLC Version 22000
Date: 8/17/88

Copyright 3Com Corporation, 1991.  All rights reserved.

Enclosed is a distribution diskette containing SW/1-A/BSC/SDLC
Version 22000 (part number: 83-0000-00) to be used with an MCPU-
based CS/1.

This release memo gives instructions for copying the distribution
diskette.  It also describes the features added and bugs fixed
since Version 20060 and the software's limitations and known
problems.

.h1;Compatibility

SW/1-A/BSC/SDLC Version 22000 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 1000 or later

The following table illustrates the hardware and firmware
compatibility for SW/1-A/BSC/SDLC Version 22000.

            Hardware/Firmware Compatibility
-----------------------------------------------------------------
Product      Software                     Firmware
                                 SIO-16     MCPU        EC/2

CS/1    SW/1-A/BSC/SDLC-       No PROMs    M1 MMON      M1 IECM
        Version 22000                   01K or later 01F or later

If you have an SIO-16 board in the CS/1, the following
configurations must be used:

*   For the CS/1 with one or more SIO-16 boards, an EC/2 board
must be installed.  In addition, the MCPU PROM must be M1
MMON Revision 01G or later.

*   For the CS/1 with three or four SIO-16 boards, the MCPU board
must be upgraded to 12 MHz.

.h1;Copying the Software

Before you use SW/1-A/BSC/SDLC Version 22000 on the CS/1, follow
the steps below to make a copy of the distribution diskette.
Press the Return key after each command.

1.  Attach a terminal to the console port of the CS/1.

2.  Press the Reset switch on the CS/1.

3.  Make a copy of the distribution diskette using the following
command:

    > co <n>

where n is the number of copies to be made.

The following message appears on the screen:

    insert master and hit return key

Insert the SW/1-A/BSC/SDLC Version 22000 diskette in the disk
drive.  After you press the Return key, the following
messages appear on the screen if the read completes
successfully:

    reading ... OK
    insert copy 1 and hit return key
In actual display, the number in the message may vary
according to the number of copies you have made.  If the
message "read error" appears instead of the message "OK",
contact your network supplier or 3Com for help.

4.  Remove the SW/1-A/BSC/SDLC Version 22000 diskette from the
disk drive.  Insert a blank, 48-TPI, double-sided, double-
density diskette in the disk drive.  Press the Return key.

5.  If an error message appears, remove and replace the diskette.
If error continue to occur, contact your network supplier or
3Com for help.

If the copy complete successfully, the following messages
appear on the screen:

    writing ... verifying ... OK
    copy completed

Remove the diskette from the disk drive, and label it "SW/1-A/
BSC/SDLC Version 22000."  Store the distribution diskette in
a safe place.  You can now use the newly created diskette to
upgrade your system.

If your system is currently using SW/1-A/BSC/SDLC Version 20030
or earlier, it is recommended that you rebuild the macros, port
configuratioins, and clearinghouse names.  Otherwise, copy the
configuration, macro, and the name information from the SW/1-A/
BSC/SDLC version 20050 or 20060 diskette to the Version 22000
diskette using the following procedure:

1.  Insert your current working diskette in the disk drive.  Then
type the following command:

    > r 216 3000 B200

2.  After the system prompt appears again, remove the diskette
and insert in the disk drive the newly created SW/1-A/BSC/
SDLC Version 22000 diskette.

You must wait for the disk drive's motor to stop before you
go on to the next step (approximately 20 seconds).  This is
necessary because the SW/1-A/BSC/SDLC Version 22000 diskette
and earlier versions of the CS/1 software diskettes have
different disk formats.

3.  Type the following command:

    > w 216 3000 B200

4.  After the system prompt appears again, remove the diskette
from the disk drive.

5.  For each system being upgraded, repeat steps 1 through 4.
After completing step 4, besure that the motor of the disk
drive has stopped before you start upgrading another system.

.h1;New Features

This section describes the new features that have been added
since SW/1-A/BSC/SDLC Version 20060.

The following is a list of the new features that are also
supported in SW/1-TCP Version 20000.  For further information on
these features, refer to the Connection Service User's Guide for
XNS and TCP/IP Protocols.

*   Version 22000 supports macros containing conditional
statements.

*   Version 22000 supports Universal Time for network
communiations spanning different time zones.  Two new global
parameters have been implemented to support this feature.

The DaylightSavingsTime parameter specifies the displacement,
in minutes, from non-Daylight Savings Time.  The TimeZone
parameter specifies in minutes how far west the server is
from Greenwich.

However, the Network Control Servers do not yet support this
feature.

*   A new global parameter, AUditTrailType, is implemented. It
specifies the format of the time-stamp for audit trail
messages.  The two formats are Local time and Universal time.

*   A new parameter, NetMapBroadcast, has been added.  It
determines whether the CS/1 broadcasts its netmap packets.

*   A new parameter, MacType, has been added.  Its possible
values are IEEE and Enet.

For communication with Ethernet hosts and devices, set this
parameter to Enet.  For communication with 802.3 hosts and
devices, set this parameter to IEEE.

                            ** NOTE **

If you use the configurations, macros, and global files
copied from the SW/1-A/BSC/SDLC Version 20060 or earlier
diskette, you must use the SETD command to set the value of
the AUditTrailType, TimeZone, DaylightSavingsTime,
NetMapBroadcast, and MacType parameters.

The following is a list of the features of SW/1-A/BSC/SDLC
Version 22000 that hve not been described in any 3Com manuals:

*   The SHow AllSessions command displays a list of names (and an
optional list of physical addresses.

The command also shows the address of the other end of the
connection when it is a passive-end connection or an
interconnection.

*   The Sysgen program now can be used to disable any User
Interface commands listed on the UI Command Privilege Levels
menu.  The privilege level has four possible values: User,
Local Network Manager, Global Network Manager, and Disable.
The new option is useful, for example, to disable the REMOTE
command to improve network security.

*   A host can initiate the flushing of a virtual circuit between
itself and a CS/1 running SW/1-A/BSC/SDLC Version 22000.
Previously, only the terminal could initiate a flush of the
virtual circuit.

*   The time between the disconnection of a current session and
the connection of a call queued to a CS/1 port has been
increased to at least 30 seconds.  This feature ensures that
slow DTR toggling by the host does not affect the queued
calls.

*   A new User Interface command, PIng, is available.  The syntax
is as follows:

    PIng <address> [<timeout>]

You can specify <address> as a physical address or a
clearinghouse name.  The timeout specified is the number of
seconds that the CS/1 should wait for a response.  The
default value is 20.

This command uses the ECHO protocol to query whether the
station with the physical address or clearinghouse name
specified as <address> is alive.  This is done by sending an
echo request packet.  All Communications Servers running
version 22000 or later respond to the echo request by ending
an echo response packet.  If the host reponds within time
specified, the following is displayed:

    Host is alive

Otherwise, the following is displayed:

    Host not responding

*   You can execute macros with Global Network Manager privilege
in remote mode or using the following syntax:

    DO <address> <macro-name>

The macro's execution is not completed if the macro contains
an infinite loop or takes a long time to execute.  The macro
is aborted after one minute of execution to prevent it from
locking up the remote capabilty of the Communications Server.

If you want to execute such a macro, enter the DO <macro-
name> command after connecting to the network management
virtual port (!136) on the Communications Server.

*   The SIO-16 board now supports control signals RTS (Request to
Send) and CTS (Clear to Send).  Previously, only the DTR
(Data Terminal Ready) and DCD (Data Carrier Detect) control
signals were supported.

If you want to use the RTS/CTS instead of the DTR/DCD
signals, you must use the SETDefault command to set the
FlowControlTo and FlowControlFrom parameters to CTS_RTS pm
tje SIO-16 port.  Then you must alter the wiring of the
modular DB-25 (terminal/host) adapter.

The table below shows the correspondence between RS-232-C
names and 3Com names for the signals available on the DB-25
connector.

                   Correspondence between
                RS-232-C Names and 3Com Names
          -----------------------------------------
          RS-232-C     3Com          Function
            Name       Name

             BA        TXD/      Transmit Data
             BB        RXD/      Receive Data
             CA        RTS       Request to Send
             CB        CTS       Clear to Send
             CC        DSR       Data Set Ready
             AB        GND       Signal Ground
             CF        DCD       Data Carrier Detect
             CD        DTR       Data Terminal Ready

.h1;Bugs Fixed

The following is a list describing the problems that existed in
SW/1-A/BSC/SDLC Version 20060 or earlier and how they have been
fixed in Version 22000:

*   Previously, if the ECHOMask included control characters, some
characters (e.g., backspace) did not function normally in
Command mode.  Now, if you include a control character in the
ECHOMask, type "res", and then enter the ECM character,
editing in Command mode then returns to normal.

*   If the SPP retransmission count exceeds 200 within an hour,
it is considered an error and an audit trail record of type
ER is sent to an NCS.  Previously, the count was always set
to zero.

*   Previously, when a host was flow-controlled, a terminal, even
in Command mode, would not function after you had entered
four characters from the keyboard.  It would lock up until
the host terminated the flow control or the network manager
used the Listen command on the port.

Now, if the same situation occurs, you can enter the ECM
character to continue the operation of the terminal, because
the ECM character is processed as an out-of-bank signal.

This feature exists only if you have M0 ASYN Rev. 18C or
later on the SIO board or it you have an SIO-16 board.

*   Previously, hourly statistics were entered in the wrong hour
slot.  This problem has been fixed.

*   The lowest value allowed for the SPP Minimum Window Size, a
Sysgen parameter, was 3.  Now the lowest value is 1.

*   Previously, the SHow VERSion command occasionally displayed
the wrong boot source.  Now, if the CS/1 is booted from a
local diskette, the BootServerAddress address cannot be
changed and the SHow VERSion command displays the boot source
correctly.

If a CS/1 that is booted from a local diskette is bound to an
NCS, and the BEcome Primary command is used on the NCS, the
BootServerAddress is no longer changed to the address of the
NCS.  Instead, the NCS displays the following error message
after you enter the BEcome Primary command:

    Informing <address> ... Booted from floppy: cannot set BSA

*   Previously, if the FlowControlFrom and FlowControlTo
parameters were both set to None, resetting one of the
parameters to Xon_Xoff or ENQ_ACK would cause the other to be
automatically set to Xon_Xoff or ENQ_ACK.  This problem has
been fixed so that these parameters can be set independently.

*   Previously, clearinghouse request retries were transmitted as
PEP packets, which the NCS/AT did not understand.  Now they
are transmitted as BTP packets, which are understandable to
all NCSs from 3Com.

*   The X.25 host no longer hangs when a connection is initiated
from a CS/1 to the host across a GS/1-X.25 with the following
command:

    Connect <host address> ECM

This is because after the RESume command is entered, the CS/1
now can send back the response to the "read parameter" packet
from the X.25 host.

*   The on-screen help menu at the Global Network Manager
privilege level now includes the DO <address><macro-name>
command.

*   It is now legal to use a combination of a clearinghouse name
and port number to define a permanent virtual circuit.  The
following is an example:

    SETD (!<port-id>) pvc = "host7!128"

The combination of the clearinghouse name and port number
should be a string containing no more than 12 characters.

*   The ReaD command now works properly for the port configured
as the last virtual port on the CS/1.

Previously, this command replaced the in-memory default
parameters of the last virtual port with those from a
specified file on the system diskette but failed to
automatically copy the new in-memory parameter table to the
system diskette.  Now the ReaD command performs both of these
functions correctly.

*   Version 22000 attempts to establish connections to permanent
virtual circuits  according to the order in which the
connection requests are received.  Previously, priority was
always given to the connection attempt to the lowest-numbered
permanent circuit.

*   The StopBits parameter can now be set to any of its possible
values.  Previously, if you attempted to set this parameter
to 1.5, an error message appeared.

*   The optional parameter, (<address>), is now included in the
syntax of all commands displayed in the Global Network
Manager help menu.  Previously, this was omitted from some
commands in the display.

For example, the syntax for the UNSave command is displayed
in the Global Network Manager hlep menu as follows:

    UNSave (<address>) <filename>

.h1;Known Problems

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

1.  Due to a memory limitation, the SHow CONFigruationS and SHow
MACros commands no longer display output in alphbetical
order.

2.  On the SIO-16 ports, the help menu of the BAud parameter
displays Low_Autodbaud and Hi-AutoBaud as options of this
parameter.  The SIO-16 boards, however, support only single-
range autobaud.  Whether you set the BAud parameter to
Low_AutoBaud or Hi_AutoBaud it does not affect the baud rate,
which ranges from 50 to 38.4K.

.h1;Limitations

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

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

2.  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

3.  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 cach.  This can cause unexpected results
when macros are executed.  To ensure proper execution of
macros, use the Zero-Macro 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 of 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 oneach
server utility on the NCS/AT.  For example, at the utility
prompt of the NCS/AT, enter the following command:

    oneachserver -B zm

5.  The Sysgen program is not available on the NCS/1 for SW/1-A/

.h1;Documentation

The following manuals are provided with SW/1-A/BSC/SDLC Version
22000:

*   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

The following manuals provide related information:

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

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

*   NCS/150 Installation and Operation Guide (4/85)
    Part Number: 09-0071-00

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

