
   I N F O C o n n e c t    C o n n e c t i v i t y    S e r v i c e s

                        Version 3.0 (007)

                    Welcome to INFOConnect 3.0

If you're a first time user of INFOConnect, you'll want to read this whole
document.

If you're familiar with INFOConnect 2.0, you can skip this introduction and
jump right to the WHAT'S NEW? sections.

All users should read the RESTRICTIONS and KNOWN PROBLEMS sections at
the end of this file.

NOTE:   This Connectivity Services package must be installed via the
        installation shell INSTALL.EXE executable contained on the
        release media root directory.


***************************************************************************
                      INTRODUCING INFOConnect 3.0
***************************************************************************

INFOConnect is a user-oriented open connectivity platform that enables
communication between workstations and hosts, servers or other workstations.
INFOConnect provides:
-       Applications and Accessories such as terminal emulators and
        file transfer capability
-       Connectivity supporting a wide variety of transports
-       Development Kit providing a open communications,
        transport independent development platform
-       "Plug and play" flexibility between components and packages
-       SNMP Agent for monitoring workstation utilization and communications
        connection statistics locally and remotely using an internet manager.

This section gives you an overview of the install process for a standalone
workstation user.

If you are a LAN Administrator, read this section first for an overview of
the install process.  If you would like to copy INFOConnect to the LAN for
users to install, read the WHAT'S NEW? section.  Or if you would like to
install a shared copy of INFOConnect to the LAN, read the WHAT'S NEW?
section for some highlights of the PUBLISH and SUBSCRIBE installation
process.

If you are a user on a LAN who has been told to install INFOConnect from the
LAN or to SUBSCRIBE to INFOConnect on the LAN, read this section first for
an overview of the install process.  Then read the WHAT'S NEW? section for
more information on how INFOConnect install works with your LAN.

Connectivity Services is the first package to be installed in the
INFOConnect 3.0 family of components.

These are the steps you go through during the install:

1.      Install INFOConnect Connectivity Services first.
        Thereafter, the order of packages is not important.

2.      Say YES to "Do you want to continue with the installation of another
        package?" until all packages are installed.

3.      Say NO to "Do you want to continue with the installation of another
        package?" only when all packages are installed.

4.      Quick Config automatically takes place after installation.

Here is a basic overview of the steps listed above:

Install all packages first, one by one, using this install program.
You don't need to exit the install and then start a new install for another
package! At the end of install of Connectivity Services, you will see a
screen which says "Package installation is complete.".  At the bottom of
that screen, it will ask you a question: "Do you want to continue with the
installation of another package?".  You should say YES if you have more
packages to install.  Continue to install packages, without ever exiting
this program, until you have installed all of the packages which you
received.

When there are no more packages to install, answer NO to the question
"Do you want to continue with the installation of another package?".
Once you answer NO, INFOConnect will automatically begin the Quick
Configuration of all of the packages which you have just installed.

When Quick Configuration has completed, you will see a dialog box which
tells you that it is done.  Please be patient! If you have installed many
packages, it may take some time.

During the installation of Connectivity Services, some files are stored into
your WINDOWS and WINDOWS\SYSTEM directories.  As these files are being
copied, a dialog box is shown with the name of the file and the destination
directory so that you can see what file is currently being processed.  It is
necessary to store a few critical files into the WINDOWS and WINDOWS\SYSTEM
directories so that Windows can find them.

If you do not have write privileges into the WINDOWS and WINDOWS\SYSTEM
directories, such as when a shared copy of Windows is installed on a Local
Area Network, then the installation program must be executed with the Local
switch.  Use the following command line syntax:

        a:\install.exe /L

where a: is the drive (floppy or LAN) from which you are installing.

After you have installed the basic INFOConnect package, the INFOConnect
Installation program is available as menu item under Install Packages on the
INFOConnect Manager menu bar.  This allows you to easily install new
packages if your communications requirements change, to Deinstall a product
that you no longer use, or to start Quick Configuration again if you would
like to do some additional configuration on already installed products.

INFOConnect 3.0 packages may be deinstalled by use of the Install Packages
menu item.  INFOConnect may be deinstalled entirely by using the following
command line syntax:

        a:\install /U

where a: is the drive (floppy or LAN) from which you are installing.

See the 'WHAT'S NEW' section for more details about removing INFOConnect
from the workstation.

Consult the INFOConnect Connectivity Services Installation, Configuration,
and Operations Guide for detailed information on INFOConnect.


***************************************************************************
                        PROBLEM REPORTING
***************************************************************************

For technical assistance with INFOConnect, call DCA at
        (513) 745-0515.

DCA maintains an electronic bulletin board.  To access the DCA bulletin
board, you must have a modem and an ANSI terminal or emulator such as the
INFOConnect VT emulator.  The bulletin board supports line speeds from 300
to 14.4K baud.  Set your communications equipment at 8 data bits, 1 stop
bit, and no parity.  The bulletin board numbers are: (513) 745-0241 or (513)
745-0193.


***************************************************************************
                         WHAT'S NEW?
***************************************************************************

WHAT'S NEW for 3.0?????? LOTS!!!

INFOConnect has an improved user interface:
Path configuration is easier now.
All sorts of changes have been made to improve usability!
Read on for some of the highlights....

Consult the INFOConnect Connectivity Services Installation, Configuration,
and Operations Guide for detailed information on INFOConnect.


***************************************************************************
                      WHAT'S NEW FOR INSTALL?
***************************************************************************

1.      The following installation modes make it easy to install and
maintain INFOConnect on a LAN.  INFOConnect can either be put on the LAN and
users can install from there in Standalone mode, or a shared copy of
INFOConnect can be published to the LAN and users can subscribe to it.

All INFOConnect installation modes are supported against both local and
shared windows.

        Standalone installations:     INSTALL.EXE

        Publish installations:        INSTALL.EXE /A

        Subscribe installations:      INSTALL.EXE /N


See the INFOConnect manual or help file for more information about install
options and a thorough explanation of Publishing and Subscribing to
INFOConnect packages.

2.      The InstMgr icon is gone. The install/deinstall functions have been
moved into the Manager under Install Packages on the menu bar.  If you
previously had an InstMgr icon, it now displays a dialog box directing you
to the manager.

3.      No more duplicate icons! Choosing 'Continue' on the installing icons
step now updates the existing icon.  Choosing 'Skip' bypasses the icon
install process.  If you choose 'Skip', your existing icon does not get
updated.

4.      Two Connectivity Services packages now appear in the package list
under Install Package:

        ICW10-CS        - all Connectivity Services libraries and accessories.
        ICW10-CS-MGR    - all the Connectivity Services .dll files
                        *plus* everything in the ICW10-CS package.

Deinstalling these packages removes Connectivity Services from the
workstation, except for the .cfg (database), .ini files, and the
[INFOConnect] section of the win.ini file.  Not removing these files (.cfg
and .ini) allows you to remove the backplane (Connectivity Services) without
losing the databases and the environment.  It also allows you to deinstall
or reinstall the backplane without disturbing other INFOConnect packages.

5.      The backplane and all INFOConnect packages can be deinstalled
entirely by using the /U option on install:

        install /U     - Standalone deinstall
        install /A /U  - Publish deinstall
        install /N /U  - Subscribe deinstall

6.      Database verification - Because the upgrade from 2.0 to 3.0 is
adding new fields to every record in the database the install process will
take longer for 3.0 than it did for 2.0.  Also, install of Connectivity
Services now verifies your entire database during each upgrade installation.
It does take extra time, but it pays off in the long run through better
database integrity.  So, thanks for being patient.

7.      Users who do a subscribe install to an INFOConnect package published
on a LAN should be aware of the new auto-synchronization feature of
INFOConnect.

If a published package is reinstalled, reconfigured, or deinstalled, that
package is likewise automatically reinstalled, reconfigured, or deinstalled
at the subscriber's workstation the next time INFOConnect is run at the
workstation.

One exception to automatic deinstallation is the Connectivity Services package
itself.  If the published Connectiviity Services package has been deinstalled
the subscriber's workstation will report "Cannot verify publish package
ICW10-CS-MGR IcFindConfig (Publish) failed".

Local configuration changes made by the workstation user may be overwritten
when auto-synchronization occurs.

Syncronization is performed only when changes are made to packages (that is:
when a package is installed or configured).  The administrator is asked if
he wishes to copy the active published database to the workstation master
database when differences in the package install or quick config timestamps
are detected.

As a consequence, if the administrator configures individual components of
the package (Configure Paths or Libraries, or Install Path Templates,
Libraries, or Accessories), he will not be asked if he wishes to synchronize
the databases unless changes have also been made to packages.

To insure that changes will be visable to the workstations, use Configure
Package to Quick Configure any package.  (Typically ICW10-CS-ADM, if changes
have been made to other items.) Then when the Shared Manager is exited, (or
Admin logs out or back in) the query to syncronize the workstation master
database will be displayed.

8.      Users who want to install multiple copies of INFOConnect, administer
for multiple publishes of INFOConnect or publish INFOConnect from a subscriber's
workstation need to use the "/L" install shell command line option.  This
"local" installation option will redirect files destined for the WINDOWS or
the WINDOWS\SYSTEM directory to the package destination directory.  This will
prevent the afore mentioned environments from stepping on each other.
Additionally the standalone or subscribe user who wants to install multiple
copies of INFOConnect must manually manage the [INFOConnect] section in WIN.INI.
See "Where the Files Go", "Installation Command Options" and "Installation
Directory" in the online help for more information.

***************************************************************************
                     WHAT'S NEW FOR THE MANAGER?
***************************************************************************

1.      The icons you're used to seeing across the bottom of your
INFOConnect Manager screen have disappeared.  All the functions are now
accessed from the Manager menu bar.  These functions all bring up child
windows which can be iconized, restored, closed, and opened again.

Here are the old icons and their new menu locations:
        Paths  - Configuration, Paths
        Templates  - Install, Path Templates
        Channel  - Configuration, Libraries
        Libraries  - Install, Libraries
        Accessories  - Install, Accessories

New icons/windows are:
        Session  - no menu bar location, this child window cannot be
                closed; it can be iconized and restored.
        Packages  - this new window replaces the InstMgr
                icon which used to be in the INFOConnect
                program group. Access its functions from either
                Configuration, Packages or Install, Packages

2.      The INFOConnect Manager child window handling is now much more
flexible: child windows can be opened, closed, iconized and restored.  More
importantly, you can switch between windows much easier.

3.      The Application Interface Library (AIL) is an adapter to an
application.  The AIL typically maps to the OSI application layer and is the
point where a session connects to an application.  Each session contains one
AIL.  By using AILs, current INFOConnect applications can continue to
communicate through an updated INFOConnect Manager or across new transports
without change to the applications themselves.

4.      Libraries now can have many different types of objects to configure.
The new Library Configuration window deals with these objects.  This window
sort of provides the same functionality as the Channel Configuration window
in INFOConnect 2.0.  In release 2.0, the only objects were the Library
Channels.  Now the other path related information associated with a library
is formalized in a Library Path Object.  Library can also have other types
of Objects: note the Trace Log Options Object of the Trace Library and the
Global Options Object of the Diagnostic Library.

5.      TRACE - The INFOConnect Trace Log has been enhanced to provide a
finer level of granularity and control.  If you use the Trace log, see the
new on-line help for tracing.  One thing to note: on INFOConnect 3.0,
tracing must be disabled through the Administration Trace menu to deactivate
tracing permanently.  Closing the Trace Log window only stops tracing
temporarily.  When INFOConnect is restarted, tracing is restarted if it was
previously enabled.

6.      A new Diagnostic Library is provided to detect and correct
interoperability problems between applications and libraries.  See the
Diagnostic Library help book for details (icdiags.hlp).

7.      A new Stack Library is provided to connect or 'stack' paths making
it easier to temporarily enable the Trace Library or Diagnostic Library for
a specific session or path.  See the Stack Library help book for details
(icstack.hlp).

8.      The Manager is built using XVT version 3.02.00.  If you have
programs build on earlier versions, you might consider relinking with this
level so Windows loads only the 3.02 set of DLLs.

***************************************************************************
                    OPERATING CONSIDERATIONS
***************************************************************************

1.      Administrators for published INFOConnect packages should limit
the subscribe workstation to read only access of the shared files.

2.      Deinstallation of published INFOConnect packages does not delete
the shared files, but rather builds an IcRemove.BAT file for the administrator
to run after all subscribed workstations have synchronized to the package
removeal.  The administator must delete the IcRemove.BAT file after it has
been successfully run.  The administrator should also note that if the
IcRemove.BAT exists, the file size is not truncated to zero during the file
open.

3.      Subscribe installations support one drive letter remapping. They
do not support MAP ROOT remapping. If the administrator publishes the
Connectivity Services package to N:\INFOCONN\INSTALL using  the
'MAP N:=SERVER/VOLUME:\ABC' command, the subscribe user can install via
G:\INFOCONN\INSTALL /N  using the 'MAP G:=SERVER/VOLUME:\DEF' command.
The subscribe user can not install via G:\INSTALL /N using the
'MAP ROOT G:=SERVER/VOLUME:\INFOCONN' command.  The subscribe user's
root mapping for drive G must map the root mapping associated with the
administrator's drive N. If the administrator publishes additional
packages to another drive mapping, for example using the
'MAP O:=FileServer/Volume:\XXX' command, the subscribe user can either
define the same drive, O (with the same map root) or allow drive letter
substitutions of G for O.  This requires that the MAP ROOT for both
drives N and O be the same.

4.      Because Windows 95 had not been shipped INFOConnect has not 
been qualified with Windows 95.  If you have any problems 
running INFOConnect with a Windows 95 Beta or the released Windows 95 
please notify INFOConnect support using a Contact.

*************************************************************************** 
                          RESTRICTIONS
***************************************************************************

1.      Installation of Connectivity Services does not support a downgrade
of the installation data base to an older level.  As a precaution, database
files are saved as *.cf0 files during the first install of Connectivity
Services.

If you must downgrade to an older level, follow these steps:

        1.      Deinstall Connectivity Services: ICW10-CS-MGR.

        2.      Copy the old database (.cf0 files) as the current
                database (.cfg files) with these commands:

                copy instmgr.cf0 instmgr.cfg
                copy infoconn.cf0 infoconn.cfg

        3.    Reinstall the old level of Connectivity Services which
              matches the .cf0 files you just copied.


***************************************************************************
                        KNOWN PROBLEMS
***************************************************************************


1)  When first upgrading from 2.0/2.01, an error message is displayed
"The database table could not be found." Error number: DB-S-13.  The Quick
Configuration window shows Library TELNET, Table 2 of 2.
        Select OK to ignore the error.

