Ref: 11030039
Title: Maxess 1.3.0 README File
date: 8/1/89

Copyright 3Com Corporation, 1991.  All rights reserved.

                      Welcome to the Maxess SNA Gateway
                      ---------------------------------

                                Version 1.3.0

This README file contains important information which is
also provided in the Maxess SNA Gateway Version 1.3.0
Release Notes.  You will not find most of this information
in the manuals provided as part of the Maxess product package
which you have received.  Please read through this material
completely before installing and using the Maxess software.
If there is any question, the information in this README
file supercedes the information in the product manuals.


Directory
---------

    1. Product Questions and Assistance
    2. Installation and Configurations
    3. Troubleshooting
    4. BIOS Problems and Almost-Compatible PCs
    5. Configuration Suggestions for Maxess Gateway Operation
    6. Installing version 1.3.0
    7. Configuring Maxess for 3Com 3+Share and 3+Open
       Networks
    8. Changes from version 1.2.1 to 1.3.0
    9. Late Documentation


1. Product Questions and Assistance
-----------------------------------

As with any IBM communication product, most problems can be traced
to the original configuration of the software, either on the IBM
Host System or on the remote system, such as the PC in which Maxess
is installed.  The first resource you should use for assistance is
the product manuals and this README file which is also distributed
in hardcopy form as a set of Release Notes.  The second resource is the
IBM Host System Administrator who can assist in diagnosing any
configuration mismatches.  If you still need assistance, contact your
3Com Representative.

PLEASE have the following information available when you call so
that we can more quickly provide assistance:

       A. Your Maxess SNA Gateway serial number.
       B. The computer brand and model in which the Gateway is installed
          and for those which are used as workstations on your network.  Also,
          a description of any additional hardware or system (TSR) software
          which is installed.
       C. The Operating System and version number.
       D. A description of the AUTOEXEC.BAT file and of the CONFIG.SYS
          file, both for the gateway machine and the workstation machines.
       E. A description of your IBM Host system configuration and the
          software version levels which are in use.
       F. A description of the communications equipment between you and
          your IBM Host system (for example, modems, modem eliminators,
          leased/switched lines, and line speeds).


2. Installation and Configurations
----------------------------------

The Maxess SNA Gateway contains many advanced features including
the ability to switch between SNA 3270 Sessions and DOS
applications, with both remaining active.  This is done through
Terminate and Stay Resident (TSR) programs.

When creating or modifying your AUTOEXEC.BAT file, the order in which
TSR programs are loaded relative to the Maxess Multitasking Scheduler
(MMS) is important.  In most cases, other TSR programs should be loaded
before MMS.  Keyboard enhancement programs such as DOSEDIT should be
loaded after MMS.  If you experience problems, try changing the order
in which TSR programs are loaded.  If you add MMS to your AUTOEXEC.BAT
file so that it is permanently in memory, you can still use Maxess
batch load files because MMS will not load additional copies of itself.
This and related information is provided in Chapter 2 of the Maxess SNA
Gateway Administrator Guide and Chapter 7 of the Maxess SNA Gateway 3270
User Guide.


3. Troubleshooting
------------------

    A. DOS Graphics Application screens.... A powerful feature of the
       Maxess SNA Gateway, is the ability to switch between a 3270
       Session and a DOS program with a simple "hot" key.  This allows
       you to have your IBM Host sessions active while you run your
       standard DOS programs.

       However, if you are using a DOS application which uses Graphics
       screens, you cannot "hot" key back to Maxess until the graphics
       program is stopped.  If you attempt to do so, you will hear a beep
       when you type the "hot" key sequence.  Related information is provided
       in Chapter 5 of the Maxess SNA Gateway 3270 User Guide.

    B. Display Adaptors.... Certain machines such as the IBM PS/2 Model 30
       indicate that a color monitor is installed even when a monochrome
       monitor is attached.  Maxess screens will appear with incorrect
       highlighting when a system with a monochrome monitor is configured
       as a color monitor.  If you have such a system, run the Workstation
       Configuration Program (WCP), choose the System/Components screen, and
       change the monitor type to mono. You will only have to do this
       procedure once after the initial installation.

    C. Token Ring Networks.... Pressing the PrintScreen key on a Maxess
       Gateway PC without a printer being attached will cause disconnections
       of 3270 sessions on the network. The PrintScreen function does not
       time out soon enough to prevent the Workstations from timing-out.

    D. Novell NETBIOS.... The Novell implementation of NETBIOS does NOT
       support group names.  Consequently, the ability to specify Gateway
       configuration names in workstation programs is not available
       when using Novell's NETBIOS.  You must specify the private name
       of the Gateway.

    E. Novell NETBIOS..... There are problems with session cleanup causing
       "Duplicate Network Name" errors.  These errors occur frequently when
       Maxess software is running.  To recover from these errors, reboot your
       workstation and restart Maxess.  Because of these Novell NETBIOS errors,
       we recommend that you use another NETBIOS such as the IBM PC adapter
       program (tokruei/netbuei) or the PC LAN Support Program drivers
       (dxma0mod.sys dxmc0mod.sys, and dxmt0mod.sys).

    F. Tempus Link.... This popular file transfer facility works successfully
       with Maxess.  To use Tempus Link with Maxess, you must change the
       Tempus Link interrupt from 13 to some other interrupt (e.g. 60).
       You cannot use Tempus Link resident file transfer software
       concurrently with other HLLAPI programs.  This includes the Maxess
       File Transfer functions SEND and RECEIVE.  Because both Maxess and
       Tempus Link use the same HLLAPI interface, conflicts arise which cause
       one or the other to time out.  You can, however, use the Alt T File
       Transfer function key to transfer files concurrently with Tempus
       Link use.

    G. Network Lock-Ups.... See below for possible BIOS/CPU problems.

    H. HOMEBASE.... You cannot use HOMEBASE V2.5 (TSR from Brown Bag
       Software) with any Maxess software.  When HOMEBASE is installed the
       machine locks up.  To recover, you must cycle the machine's power and
       restart Maxess.  You can use the HOMEBASE de-install program to unload
       HOMEBASE before running Maxess software.


4. BIOS/CPU Problems and Almost-Compatible PCs
----------------------------------------------

Networking software makes extensive use of the machine facilities
contained in the ROM BIOS.  For some older IBM PCs and XTs, this
BIOS was found to contain bugs which prevent reliable operation with
networking software.  Maxess, which makes extensive use of this
networking software, is susceptible to these errors when running on
older machines.

Also, on some very old IBM PCs, the CPU chip was flawed and did not
process Stack segment changes correctly.  This situation is rare;
very few of the machines were delivered, but they will cause problems
if you try to use them on your network.

However, should you want to use an older IBM PC/XT as a workstation or
gateway on a network, the alternatives listed after the problem
descriptions below are open to you.

    A.  CPU Problems.... MMS will test for the presence of a bad
        8088. If found, the message "** BAD 8088 - replace immediately **"
        will be displayed and the program will terminate. You will not be
        able to use this PC as a Maxess workstation or gateway without
        replacing the CPU chip.

    B.  BIOS Problems.... You must have a version of the ROM BIOS dated
        1986 or later to reliably use networking software.  Most software
        will work normally for a time, but you may experience periodic
        errors on the network.  (Some networking software is more sensitive
        to this problem than other).  These errors typically occur under
        heavy network traffic or workstation loading conditions.

On the Maxess UTILITIES Diskette is a device driver called MAXTIMER.SYS.
This driver fixes a bug in some ROM BIOS implementations where pending
interrupts are lost because the BIOS routine does not check the status of
the interrupt controller before issuing an END OF INTERRUPT command. This
bug is known to occur on IBM XTs and on pre-1987 ATs. For these systems,
we recommend that you add the statement:

         DEVICE=MAXTIMER.SYS

to your CONFIG.SYS file, and copy file MAXTIMER.SYS from the Utilities
diskette to your boot drive. MAXTIMER.SYS must be the FIRST device driver
loaded! If MAXTIMER.SYS is not installed and the ROM BIOS date indicates
that this problem may exist, a warning message is displayed when MMS
loads.

Additional Alternatives:

    A.  Update the BIOS ROM to the most recent IBM replacement part
        dated 1986 or later.

    B.  Read the installation instructions for your networking
        software.  Some network products, such as IBM's Token Ring
        support, provide ".SYS" files which effectively "patch" the
        ROM BIOS to avoid some of these problems.  These fix files,
        unfortunately, do not completely eliminate the bugs in all
        areas of the BIOS.

    C.  Contact your PC support representative about installation of a
        replacement ROM BIOS from various non-IBM vendors who will
        have compatible BIOS parts.

Almost Compatible PC Problems.... There are many vendors of so-called
"clone" PCs.  Eeach of these clones has a ROM BIOS installed in order
to operate correctly.  In some cases, in older models of these PCs, the
the ROM BIOS is not 100% compatible with the IBM BIOS or was not written
to support networking products.

The Maxess SNA Gateway may experience problems on certain IBM
"clones" because of these differences.  Check with your original
equipment supplier for (a) the most recent version of the ROM BIOS
which is available, and (b) the equipment compatibility for use with
networking software.


5. Configuration Suggestions for Maxess Gateway Operation
---------------------------------------------------------

The Maxess product has extensive logging and diagnostic facilities
which can be configured by the Gateway Administrator. In the case where
the File Server and the Maxess Gateway are on separate machines and
logging is directed to a File Server disk, an exceptional demand for
network I/O will be placed on the Server.  You may experience problems
with some File Server implementations which are not capable of reliably
processing this volume of server traffic.  To minimize these problems,
3Com recommends that the Activity Log be directed to a local drive
as opposed to a network drive.  The Activity Log file is specified in
the Gateway file MAXESSGW.CFG.  The Maxess SNA Gateway Co-Processor
Board uses a hardware interrupt, a shared memory buffer, and an I/O
port for communication with workstations.  The following are the
default settings of the Co-Processor:

        Interrupt Request (IRQ) Level:  3
                          I/O Address:  33C through 33F
                 Shared Memory Buffer:  D000 through D7FF

If the default Co-Processor Board settings conflict with other
hardware adapters installed in the Gateway workstation, then you must
change either the Maxess board settings or the other adapter's settings.
Workstations that do not have a Maxess Co-Processor Board are not
affected.  See Appendix C of the Maxess SNA Gateway Administrator Guide
for a complete description of Maxess Co-Processor Board settings.

When a Maxess Gateway is installed, it is assumed that the network
adapter in the system uses DMA for NetBIOS data transfers.  This
is controlled by the /d parameter to GRSP (see LOADGW.BAT).  If you
are sure that your network adaptor does not use DMA, you can save
approximately 25K of memory by removing the /d parameter to GRSP.
In some cases you can change the network adaptor to avoid using DMA.
This is preferable, since use of DMA for Maxess data transfers does not
significantly improve performance, and removing the /d parameter saves
memory.  IBM and 3Com Token Ring adaptors do not use DMA.  Most 3Com
Ethernet adaptors can be configured to use or not use DMA.  Consult
your network adaptor documentation if required.  If in doubt, retain
the /d parameter to GRSP.


6. Installing version 1.3.0
---------------------------

If you are installing version 1.3.0 over version 1.2.1, be sure
to delete file 3270.EXE in the installation directory.  The
3270 Program now has several executables, one of which is loaded
from either the MAXESS.BAT or 3270.BAT batch load files.  When you
reload the 3270 Program by typing "3270", the 3270.BAT batch file,
not the old 3270.EXE file, must be found.


7. Configuring Maxess for 3Com 3+Share and 3+Open Networks
----------------------------------------------------------

    A.  The NetBIOS Locator.... The 3Com NetBIOS software uses a program
        called the Locator (LOCATOR.EXE) to manage NetBIOS names.  A Locator
        program must be operating on each LAN.  Typically, the Locator is
        installed with the server as part of the server configuration process.
        However, the Locator can run on a LAN not using a server.  To run the
        Locator on any system on the LAN, execute the LOCATOR.EXE program.

        To minimize NetBIOS outages, run the Locator on a reliable machine not
        subject to frequent rebooting.  A good choice is the machine in which
        the Maxess SNA Gateway Co-Processor board is installed.

        The 3Com NetBIOS software will issue the following error message as
        the NetBIOS software is started if the Locator is not executing:
        "Locator Not Responding."

    B.  Maxess and the LinkPlus Optimizer.... When the Maxess SNA Gateway is
        initialized, a NetBIOS command is issued to register a GROUP name,
        should one exist.  Next, a NetBIOS receive command is issued.  This
        command sets up the NetBIOS driver to post notice when a message for
        this GROUP name is received.  The receive command should return
        immediately.

        However, when the 3+Share or 3+Open DOS netstation software is
        configured for download to the EtherLinkPlus adapter using the
        LinkPlus Optimizer and the Maxess SNA Gateway Co-Processor board is
        installed in the same machine, the receive command does not return
        immediately because the 3Com NetBIOS driver hangs.  The EtherLinkPlus
        board should not be configured for adapter-based protocols when used
        in a machine in which the Maxess SNA Gateway Co-Processor board is
        also installed.

        To avoid this problem, configure 3+Share or 3+Open DOS netstation
        software for host-based protocols when using this software in
        conjunction with a Maxess SNA Gateway Co-Procesor board.

    C.  If you use 3Com's MMINDER or RECVMSG programs, you must replace
        them with modified versions that are located in the 3COM sub-
        directory on the Utilities diskette.  The replacement programs
        will work with or without Maxess.  If you are also using Sidekick,
        you must first load SideKick, then load MMS, and then load MMINDER
        and/or RECVMSG.  If SideKick is not installed, the relative order
        of MMS, MMINDER and RECVMSG installation does not matter.

    D.  NETPOPUP.... The 3+Open DOS LAN Manager NETPOPUP facility is not
        supported with this release of Maxess.


8. CHANGES from version 1.2.1 to 1.3.0
--------------------------------------

    A.  The 3270 Program can now be configured for optimal memory
        usage.  See WCP/3270/Components.

        The new memory requirements for 3270 are as follows:

            Basic Emulation up to 5 sessions    175K
            HLLAPI only service                 146K
            Basic emulation with options
                 or more than five sessions     210K

            Options:
                Logical Unit Printer             26K
                HLLAPI Option                    23K
                File Transfer Option             19K
                On-line Help Option              26K
                RTM Display Option               14K

        The figures above are for one session.  Additional sessions
        require 5K each.

    B.  The memory requirement for the APPC Program has been reduced
        to 90K.

    C.  System colors can now be modified.  See WCP/System/Color.

    D.  The 3270 Suspend feature now save screens to disk and restores
        them when the program is resumed.  Screens are saved in file
        3270SCRN.SAV.  The file is stored in the directory specified by
        the TMP environment variable, if set.  If TMP is not defined, the
        file is stored in the directory specified by environment variable
        MAXESS_PRIVATE.  If neither environment variable is specified,
        the file is stored in the directory in which the 3270 Program
        was found when loaded.

    E.  The UNLOAD utility now takes arguments for unloading Maxess
        Programs and no longer displays an interactive list.  Run
        unload as follows:

        C> unload [mms] [nbri] [3270 [/s]] [appc] [gateway] [*] [?]

        parameters:

            - No parameters displays the usage of UNLOAD.
            - The 'mms' parameter unloads MMS.
            - The 'nbri' parameter unloads NBRI.
            - The '3270' parameter unloads the 3270 Program.
              Use the optional '/s' to suspend sessions.
            - The 'appc' parameter unloads the APPC Program.
            - The 'Gateway' parameter unloads GRSP which shuts down
              the Gateway.
            - The '*' parameter unloads all Maxess programs except the
              Gateway.  If the Gateway is loaded, MMS is not unloaded,
              otherwise, MMS is unloaded.
            - The '?' parameter lists currently resident Maxess programs

        This change allows you to unload and suspend the 3270 Program,
        run a large application, and reload the 3270 Program from a batch
        file, thus making it easy to switch between 3270 emulation and
        large applications.

    F.  The 3270 Program now accepts two additional parameters:  /H[n]
        and /P.  The /H[n] parameter causes automatic hot key, so that once
        the 3270 Program loads, the current 3270 session is displayed.  The
        optional number following the /H parameter causes the nth recording
        to automatically initiate.  The /P parameter bypasses physical
        printer initialization.  These parameters are especially useful when
        resuming suspended sessions.

    G.  The Page Forward, Page Backward, First Page and Last Page keys
        can now be used to change 3270 sessions, in addition to the normal
        Select Session key.

    H.  The Recorder function now has two new functions:  WaitFor and Delay.
        The previous Pause function has been renamed to Suspend.  The
        WaitFor function allows you to specify a string on the string to
        wait for.  The Delay function allows you to specify a number of
        seconds to delay the playback. See the Recorder Topic (Basics) in
        any of the Maxess interactive programs for a detailed description
        of the Recorder function.  An example is also included.

    I.  The WCP/System/Keyboard Options Form now includes an option for
        keyboard type.  This replaces the previous prompt for keyboard
        type during product installation and in WCP.  Note that when
        this option is changed, 3270 keyboard assignments are set to
        default values.

    J.  All keys are now available for reassignment.  This includes keys
        such as the SysReq key on AT class PC's and all Ctrl numeric keys
        which are not normally supported through the BIOS.

    K.  Default 3270 keyboard assignments have been changed as follows:

        3270 Enter              Alt Enter (PC/AT), Pad Enter (Extended)
        Carriage Return         Enter <-'
        SYSREQ                  SysReq (AT and Extended only)

        The Carriage Return key is now a separate key.  Previously, this
        function was performed by the global Enter/Select key.  The 3270
        Carriage Return and 3270 Enter keys can be assigned the same
        physical key sequence as the global Enter/Select key without
        conflict.

    L.  File Transfers can now be done without using the SEND and
        RECEIVE utilities.  Use the File Transfer function key (default
        Alt T) to enter a file transfer command - just as you would from
        DOS.  The SEND and RECEIVE utilities are still available, but
        require the HLLAPI component option.  When entering a File Transfer
        command using Alt T, you can still hotkey to DOS at any time
        (if configured for hotkey) to use DOS services such as DIR.

    M.  The Gateway Resident Services Program (GRSP) has a new optional
        parameter for locating the main Gateway configuration file
        (default MAXESSGW.CFG).  Example:

        C> grsp /c c:\maxess\maxessgw.cfg

        This option allows you to run the LOADGW.BAT batch file from
        a directory other than the Maxess installation directory.

    N.  The Gateway can now be installed in a 3S/400 Server.   See
        the Administrator's Guide for configuration restrictions.

    O.  The previous problem of terminating print jobs when using the
        3Com PRTSC redirector is fixed.  Jobs will now terminate auto-
        matically when completed.

    P.  The /i parameter to LOADFEP is no longer required.  This parameter
        should still be used for GRSP if the Interrupt Request Level of
        the Maxess Co-Processor Board is changed from the default of 3.

    Q.  In Maxess version 1.2.1 the Keystroke Recorder would not record
        keystroke assignments (WCP/System/Keyboard and WCP/3270/Keyboard).
        The Keystroke Recorder in version 1.3.0 now records keyboard
        assignment changes, allowing you to record a standard keyboard
        configuration and play it back when setting up a new workstation.


9.  Late Documentation
----------------------

    A.  The Maxess Multitasking Scheduler (MMS) now accepts an additional
        parameter to cause Maxess programs to remain inactive while pop-up
        TSRs have control.  The new parameter is '/i' which can be placed
        anywhere on the MMS command invokation line.  This parameter should
        be used if TSR conflicts occur and cannot be resolved by changing
        the order that they are loaded.  It may also be required if standard
        applications take over and release interrupt vectors in using
        non-standard techniques.  An example of this is Microsoft Word
        version 4.0.

        WARNING:  The '/i' parameter should NOT be used on a
                  PC that is running a Maxess Gateway.  Use of
                  this parameter will cause the Gateway to suspend
                  operations if a pop-up TSR takes control of the
                  system, which will result in suspending all Maxess
                  workstations that are using the Gateway.

        To use the new parameter, modify file MAXESS.BAT by adding '/i' to
        the line that loads MMS.  Example:

            echo OFF
            MMS /i
            if errorlevel 2 goto done
            NBRI /v 7e /n 3
            if errorlevel 2 goto done
            3270L.EXE %1 %2
            :done

        File MAXESS.BAT is usually rewritten when you change your workstation
        configuration.  Be sure to update it with the '/i' parameter after
        running WCP, if required.  You can avoid this problem by adding
        the line "MMS /i" to your AUTOEXEC.BAT file.  This will cause MMS
        to be loaded with the '/i' parameter when you start your system,
        and the additional load done in file MAXESS.BAT will produce the
        message:

            "*** MMS already resident ***".

    B.  Two additional features are now available with the High Level
        Language Application Program Interface (HLLAPI).  The Query Session
        Status function is now supported, and the Extended Attributes Buffer
        (EAB) Session Parameter is also supported.  This will allow a HLLAPI
        application to determine session attributes and to read extended
        attributes from a 3270 session.

    C.  Two physical key sequences may be assigned to the same function
        by defining the same BIOS code for the two keys.  For example,
        you may wish to assign both the normal Enter key and Pad Enter
        key (extended keyboard) to the 3270 Enter function.  See file
        KEYDEF.DOC for details.

-----------------------------------------------------------------------------
End-of-README-File                                   Copyright (c) 1989 3Com
