
                          IBM (R) VisualAge (TM) C++
          Distributed Application Development Toolkit for OS/2 (TM)
         ----------------------------------------------------------

Welcome to IBM VisualAge C++ Distributed Application Development Toolkit
for OS/2 (DADT for OS/2).

This file contains information you need to install DADT for OS/2,
and additional information not included in the product documentation.

This README file is divided into the following categories:

   -  Before You Install
       -Software Requirements
       -Hardware Requirements
   -  Getting Help
   -  Installing DADT for OS/2
   -  Late-Breaking News
   -  Updates
   -  Trademarks
   -  Your Comments are Appreciated


Before You Install
------------------

   Software Requirements
   ---------------------

     - IBM OS/2 WARP 3.0 (CSD LEVEL XR03001 or higher)
     - IBM VisualAge C++ for OS/2 version 3.0 (CSD LEVEL CTC301, CTO301, or higher)
     - If you are using MQ as a middleware technology, then you need:
             IBM MQSeries for OS/2 Version 2.0, 5871-AAA
     - If you are using TCP/IP as a middleware technology, then you need:
             TCP/IP for OS/2 Version 2.0, 5801-AAA (CSD LEVEL UN64092 or higher)

   Hardware Requirements
   ---------------------

     - Processor:  80486
     - Display:    SVGA
     - RAM:        Non-visual development - 16M
                   Visual development     - 32M
     - Disk Space: 19.7M for all components of DADT for OS/2
                   By component:
                       7.3M for Base component
                       0.3M for DADT WorkFrame Files component
                       7.7M for Execution Environment component
                       0.3M for Online Information component
                       2.6M for Documentation (PS) component
                       1.5M for Sample Programs component
     - Disclaimer: Product may work on lower levels (as specified by
                   IBM VisualAge C++ for OS/2 version 3.0,
                   but it has not been verified).


Getting Help
------------

   Online Information
   ------------------

   All DADT for OS/2 online documents are available in the Online
   Information component.  If you choose to install this component
   and accept the default installation path, the online documents
   will be found in the <drive:>\dadt\help directory.

   To view any of the online documents from a command line, change
   to the \help subdirectory and run the VIEW command.  For example,
   to view the DADT for OS/2 User's Guide, run the following command:

   VIEW DADTADUG.INF

   The DADT for OS/2 User's Guide provides instructions for getting
   started and using the toolkit.

   Documentation
   -------------

   All DADT for OS/2 PostScript** documents are available in the
   Documentation component.  If you choose to install this component
   and accept the default installation path, the PostScript documents
   will be found in the <drive:>\dadt\doc directory.

   The DADT for OS/2 User's Guide provides instructions for getting
   started and using the toolkit.

   Sample Programs
   ---------------

   All sample-related README files are available in the Sample Programs
   component.  If you choose to install this component and accept the
   default installation path, the README files will be found in the
   <drive:>\dadt\examples directory.  Two README files are provided:

   The README file provides information to help you develop and run
   a sample distributed application.

   The README.MQI file provides information to help you configure your
   systems to use the MQSeries middleware, which is supported by the
   DADT for OS/2 Distribution Class Library.

   The README.TR file provides information to help you generate your
   own event files.

   Technical Support
   -----------------

   There is no technical support for DADT for OS/2.

   Defect Reporting
   ----------------

   Any possible problems encountered with DADT for OS/2 can be
   reported using any of the following methods:

     o  INTERNET: dadt@vnet.ibm.com

     o  HTTP:     http://www.software.ibm.com/ad/cset/distadt/

     There is no charge for contacting us electronically,
     other than what you normally pay for your electronic access.

     o  FAX:      1-416-448-6057 (attn: Dept. 201)

     o  MAIL:     Dept. 21/201
                  IBM Canada Ltd.
                  844 Don Mills
                  North York, Ontario
                  Canada M3C 1V7

Installing DADT for OS/2
------------------------

The installation command for a basic installation is 'INSTALL'.  You
can invoke the installation program in one of two ways:

   o  Use the Developer Connection Catalogue to install (refer to
      The Developer Connection documentation for details).

   o  Use the following command-line installation procedure:

     1. Insert the product CD-ROM into a drive.  In this example,
        the A: drive is used.  Assume that the DADT for OS/2 install image
        is contained in the directory \DADT.

     2. Change to the A: drive, and change into the \DADT directory.

     3. Run the INSTALL command.

     4. Select <Continue> on the Information window and follow the prompts.

     NOTE: If additional components are required at a later time, you can
           use the above steps to install these components.

To delete components of DADT, follow the steps below:

     1. Insert the CD-ROM you used to install DADT for OS/2 into a drive.
        In this example, the A: drive is used.  Assume that the
        DADT install image is contained in the directory \DADT.

     2. Change to the A: drive, and change into the \DADT directory.

     3. Run the INSTALL /A:D command.

     4. Select <Continue> on the Information window and follow the prompts.

The following components are REQUIRED for a development/execution environment:

   - Base
   - DADT WorkFrame Files
   - Execution Environment
   - Online Information

The following component is REQUIRED for an execution environment (ie. running
.EXE produced by the development/execution environment):

   - Execution Environment
   - Online Information

All other components are OPTIONAL.


Late-Breaking News
------------------

This section includes last-minute information about the following components:

   - Base
   - DADT WorkFrame Files
   - Online Information
   - Documentation
   - Sample Programs


 Base
 ====

     Header file import:
     -------------------

     - syntax errors occurring as part of importing header files are displayed
       but a 0 return code is returned

     - the current directory must not be read-only since a temporary file
       is created during import.

     It is assumed that the header file is written in standard C++ and that
     the file is error free.In addition there are some features of C++ that
     are not supported. These are:
       - no initialization values on parameters
       - no templates
       - preprocessor directives are ignored
       - no function variables
       - no typedefs

     Code generation:
     ----------------
     Even though some of the C++ language features can be imported, some are
     not supported by the code generator:
       - "operator" methods in classes
       - DCE files (ie. IDL) are not generated
       - arrays as parameters
       - classes for distributed objects without default constructors

     Event trace:
     ------------
     In order to view the trace output file the event monitor must first be
     closed. This is performed from the
       - event monitor must be closed from the OS/2 "Window List" prior to
         viewing the output file.
       - many of the trace viewer input windows are system modal and must
         be closed before any other commands can be performed.


 DADT WorkFrame Files
 ====================

     WorkFrame integration:
     ----------------------

     - The distribute action on the class header file may produce warnings
       but still produces a 0 return code.

     - WorkFrame (at the CTW300 level) occasionally corrupts the DADT
       project templates that are referenced by ALL projects (application and
       partition level) created using the DADT Project Smarts support.
       The symptom of this problem is that all project actions are
       disabled (both Project and Selected pulldowns). This effectively
       renders the project unusable. If the template corruption is only
       partial, the symptom is erratic action behavior (typically actions
       will fail indicating incorrect argument list was specified).

       WorkFrame (at the CTW301 level) has fixed this problem.
       For users at CTW300 level that experience this, a workaround is to
       uninstall the "DADT WorkFrame Files Component" and immediately
       reinstall it. This involves only 5 files, so the procedure is
       relatively quick.

       You can determine your WorkFrame/2 level by executing SYSLEVEL command ,
       looking for the "AD Common WorkFrame/2" section


 Execution Environment
 =====================

     Please refer to the Base component section.


 Online Information
 ==================

     None.


 Documentation
 =============

     None.


 Sample Programs
 ===============

     None.


Updates
-------

You can receive up-to-the-minute product information and retrieve
the latest product updates by accessing our World Wide Web (WWW) server.
We encourage you to drop by for a visit -- often!  You can reach us at:

     http://www.software.ibm.com/ad/cset/distadt/

Trademarks
----------

The following terms are trademarks of International Business Machines
Corporation in the United States or other countries or both:

     C Set ++
     IBM
     IBMLink
     OS/2
     VisualAge

Other terms used in this README, which may be denoted by a double asterisk (**),
may be trademarks or service marks of other corporations.


Your Comments are Appreciated
-----------------------------

We'd like to hear from you.  If you have any comments about the
product, please let us know.  Simply provide your name, your
organization's name, and your telephone number so that we can
contact you.

To contact us, use any of the following methods:

     o  INTERNET: dadt@vnet.ibm.com

     o  HTTP:     http://www.software.ibm.com/ad/cset/distadt/

     There is no charge for contacting us electronically,
     other than what you normally pay for your electronic access.

     o  FAX:      1-416-448-6057 (attn: Dept. 201)

     o  MAIL:     Dept. 21/201
                  IBM Canada Ltd.
                  844 Don Mills
                  North York, Ontario
                  Canada M3C 1V7

All submissions become property of IBM Corporation.
