=================================================================

 IBM* VisualAge* PL/I Version 2.0 - Trial version

 This product is a trial version and expires 60 days after you
 install it.  This version does not include static libraries.
 If you would like to order VisualAge PL/I Version 2.0, please
 visit our web site at: http://www.software.ibm.com/ad/pli

 READ.ME file for the Standard and Professional for Windows products

 This file contains information that may not be available in the online
 documentation you receive with the Windows products.

 (C) Copyright IBM Corp. 1997. All Rights Reserved. US Government
 Users Restricted Rights--Use, duplication or disclosure restricted
 by GSA ADP Schedule Contract with IBM Corp.

==================================================================

This file contains information you need to install IBM VisualAge for PL/I,
additional information that might not be in the product documentation,
tips, and know problems. It is divided into the following categories:

  A.  Installing VisualAge PL/I
  B.  Information Updates
  C.  Usage Notes
  D.  Notices and Trademarks

A. Installing VisualAge PL/I
   -------------------------
   You cannot successfully install VisualAge PL/I V2.0 over an existing copy of
   PL/I for Windows.  If you have a previous version, follow the directions for
   uninstalling it before you continue.

   1) If both VisualAge C++ and VisualAge PL/I are intended to be
      installed on the same machine, install VisualAge C++ first, then
      install VisualAge PL/I. Both products ship some common parts
      and environment variables. This ordering is necessary
      to ensure shared environment variables are set appropriately.
      See the individual component considerations below, for more
      information on C++/PL/I coexistence.

   2) You can install from a CD-ROM  and will find the installation
      instructions for VisualAge PL/I in the "Getting Started" book.

   3) You should review the hardware and software requirements listed in
      the "Getting Started" book before starting the installation.

   4) Be certain that you have enough virtual memory available. Your
      paging file should be at least 20MB.


B. Information Updates
   ---------------------


   Using PL/I with Java
   --------------------

   The PL/I and Java sample programs are described in the 'plijava.htm'
   document which can be found in the \ibmpliw\books\ directory.  Point
   your browser to this file for information about these sample programs.
   The PL/I and Java sample programs and assorted parts can be found in
   the \ibmpliw\samples\ directory.  You can use the supplied makefiles
   to compile the sample programs after making the following adjustments:

      A. You can use the sample makefile, makefile.win,
         to compile and link the PL/I and Java sample programs.

         First, copy makefile.win into a working file, like 'mymake.mak'.

         Next, you must make the following change to the makefile:

             Change the 'JAVA_HOME = P:\jdk1.1.2' to refer to the drive
             and directory that you have the Java toolkit or Java
             runtime installed in.

         Now you can run the makefile with a command like the following:
            'nmake /f mymake.mak'

      B. You may now run the sample program by entering 'java wineSamp' from
         the command line.  Should you encounter a NoSuchMethodError you may
         append either '.;' or '.\.;' to the beginning of the CLASSPATH
         environment variable by using the SET CLASSPATH command.


C. Usage Notes
   -----------

   This section includes last-minute information, tips, and caveats
   about each component.  Headings with no material under them means
   that all information is supplied on-line.  This section is subdivided
   as follows:

      1. General
      2. Compiler/Run-time Library
      3. Debugger
      4. Editor
      5. WorkFrame
      6. Product Incongruences
      7. Application Understanding
      8. Remote DL/I

   C.1. General
        -------


   C.2. Compiler/Run-time Library
        ------------------------

        When the new DATE attribute is honored, attempts to
        assign or compare a non-date to a date are flagged
        with an E-level message.
        While this is appropriate when the non-date is a
        variable, it is questionable when the non-date is a
        literal such as '' or 0.
        The compiler will be changed shortly to flag this usage
        with a separate, less severe message.


   C.3. Debugger
        --------

        a) Monitoring of expressions when the debugger is stopped
           at the main entry to the program is NOT supported.
           Unpredictable results may occur, and you may not be able
           to monitor expressions during the rest of the debugging
           session.

        b) Monitor information should NOT be saved in the debugger
           program profiles. If monitor information is saved in the
           program profiles and the program profiles are used
           during RESTART or a subsequent debugging session,
           unpredictable results may occur.

           To prevent monitor information from being saved, select:

           options->debugger settings->program profiles
           ->select information

           and ensure that 'MONITOR' is not selected.

        c) Occasionally, you may see strange behavior in the debugger,
           such as failing to start, shutting down when stepping, etc.
           This can occur when the debugger Program Profile files
           -- which save information about previous debug sessions, such as
           window positions, breakpoints set... -- become corrupted. If the
           debugger exhibits such behavior, these Program Profile files
           should be erased.  These files have an @ sign in the
           extension (e.g., PDEBUG.@wy, or MYPROG.@wp).
           On Windows, their default location is in the DPROFILE subdirectory
           under the main Windows subdirectory (e.g., C:\WINNT\DPROFILE).

        d) The debugger ignores the date attribute.


   C.4. Editor
        ------

        a) The Tools Guide for Windows book states the command to invoke
           LPEX incorrectly. The command correct command is pliiedit. To
           invoke the PL/I LPEX editor on Windows, replace all instances
           of the iedit command in the Tools Guide for Windows with the
           pliiedit command.

        b) LPEX considerations with PL/I and other languages on the same
           machine: If you already have an LPATH environment variable, then
           you need to manually append to the PLILPATH4 environment variable
           the contents of the LPATH environment variable.  For example,
           assume that LPATH contains the following:

               SET D:\PRODUCTA\MACROS;E:\PRODUCTB\MACROS

           Then, as a result of installing VisualAge PL/I, assume the
           content of the PLILPATH4 environment variable is set to:

              SET PLILPATH4=E:\IBMPLIW\MACROS

           At this point, you should manually change the PLILPATH4
           environment variable to:

              SET PLILPATH4=E:\IBMPLIW\MACROS;D:\PRODUCTA\MACROS;E:\PRODUCTB\MACROS

           If you fail to change PLILPATH4 manually, the Editor macros supplied
           with PRODUCTA and PRODUCTB will not be available.

        c) The editor language sensitive parser for MVS JCL does not
           understand the full MVS JCL language.  You may therefore get
           parser error messages for some valid JCL constructs.

        d) The editor defaults to use a "ring" when editing multiple files.
           This means all files being edited within the ring
           share the same window space.  To navigate between files in
           the ring, you can select Windows from the menu bar and then
           select either "Next in ring" or "Previous in ring".  An alternate
           way to navigate between the files is to use the drop-down list
           located just below the tool bar.  The list contains all the
           files in the ring.

           If you desire to not use a ring and thereby have each file being
           edited use its own window space select View from the menu
           bar.  If there is a check mark to the left of "Default to ring"
           then select "Default to ring".  If no check mark shows to
           the left of "Default to ring" then use of a ring is not in effect.
           Therefore, just click again on the View menu bar chose to close
           the menu.  If use of a ring is turned off, future editing
           sessions are affected not those already active.

           If you either double click on the system menu icon in the editor
           window upper left corner or click on the system menu icon
           and choose close then all the edit session for the ring will be
           closed.  You will get a warning to save any unsaved changes.

        e) If you select "File" from the menu bar and then select "Exit", all
           editor sessions terminate.  You will get a warning to save any
           unsaved changes.

        f) For Windows, the BAT files used to invoke the editor from a
           command prompt have been renamed to PLILXPM.BAT and PLIIEDIT.BAT.
           You can choose to rename them back to the original names of
           LXPM.BAT and IEDIT.BAT, if desired.


   C.5. WorkFrame
        ---------

        a) VisualAge PL/I/VisualAge C++ Co-existence

           - If C++ is installed on the same machine as PL/I the
             following problems can occur:

               - Either PL/I Help or C++ Help will not be available (depending
                 on which product is installed last ) from the Help pull-down
                 menu of WF integrated tools such as the Editor, or Debugger.

         b) Project Smarts

            - On Windows NT 4.0 or higher, project smarts will default to placing
              WorkFrame folders in the 'PLI_Projects' subdirectory of the user's
              desktop directory. This allows the user to open the PL/I Projects
              folder on their desktop and double click on the project's .WFP
              file to open the project.


   C.6. Product Incongruences
        ---------------------

        If you have two or more IBM development products or solutions
        on your machine that provide consistent user interfaces through
        one or more of these components:
            WorkFrame          LPEX Editor
        you may find that installing, deleting, or applying a FixPak
        for one solution or product perturbs another.  This may be
        manifested as different behavior, lost customizations, and
        "missing" menu items.

        Although installing multiple solutions with one or more of
        these components results in multiple copies of the component,
        only one copy will be active for all solutions.  Because the
        copies may be at different levels and because each install,
        delete, and fixpack is tailored for a particular solution,
        incongruences may arise.

          o  For example, toolbars are tailored by a particular solution.
             If another solution is installed, the toolbar entries that
             the first solution created may appear to disappear, when in
             reality you are simply using the component installed with
             the second solution.  Or there may be duplicate menu
             entries.  Of particular note in this vein is the WorkFrame
             Help menu when you have both C++ and PL/I installed,
             particularly if you have re-installed one of them:  you
             may get only C++ help, only PL/I help, or both on the menu.
             Most of the PL/I help is identified as such on the menu.

          o  Installing, deleting, and re-installing a solution may also
             cause such problems.  For example, if you install VisualAge
             C++ and VisualAge PL/I, you will find books for both
             solutions in the WF Help pull-down.  If you delete PL/I,
             all of the books will be removed from the Help menu.  Re-
             installing PL/I will re-instate the PL/I entries only.
             The C++ books have not been removed;  the environment
             variable has simply been deleted by the delete of PL/I and
             re-set by the re-install.

          o  It may also be possible with multiple products installed
             to see different versions of books, depending on which
             version is active, which depends on what directory you are
             in and/or how the path statements in CONFIG.SYS are set.

          o  If you experience incongruent behavior after installing,
             deleting, or updating development solutions with the
             aforementioned components, you may have to adjust the
             settings of environment variables in your CONFIG.SYS file,
             including path variables.  The SYSLEVEL command can be used
             to ascertain the levels of the components.


   C.7. Application Understanding
        -------------------------

        - Each time you create or delete a JCL object manually in the Application
          Understanding inventory windows, you must close the window and reopen
          it to refresh the window.  If you are unable to reopen the window, you
          may need to close Application Understanding and restart it.

        - When attempting a particular function (for example, dropping
          and recreating an AU database) and getting the SQL error message
          "SQL1035N-The database is currently in use", you might need to
          reboot your system.

        - The VSE JCL Scanner (also referred to as the VSE JCL Analyzer)
           will be available in the next of release VSE.

   C.8. Remote DL/I
        -------------------------

        To use Remote DL/I with IMS Version 5, you will need to apply the
        PTF for APAR PQ07950.  To use Remote DL/I with IMS Version 6, you
        will need to apply the PTF for APAR PQ07947.

        The DLILOGIN command will not change your userid and password.  If
        you need to change the userid and password used by Remote
        DL/I, you will have to shutdown and log on the system.


D. Notices and Trademarks
   ----------------------
   Licensed Materials - Property of IBM

   (C) Copyright IBM Corp., 1997. All Rights Reserved.
   US Government Users Restricted Rights - Use, duplication or
   disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

   Any reference to an IBM licensed program in this publication is
   not intended to state or imply that only IBM's licensed program
   may be used.  Any functionally equivalent product, program or
   service that does not infringe any of IBM's intellectual property
   rights may be used instead of the IBM product, program, or
   service.  Evaluation and verification of operation in conjunction
   with other products, except those expressly designated by IBM, is
   the user's responsibility.

   IBM may have patents or pending patent applications covering
   subject matter in this document.  The furnishing of this document
   does not give you any license to these patents.  You can send
   license inquiries, in writing, to the IBM Director of Licensing,
   IBM Corporation, 500 Columbus Avenue, Thornwood, NY 10594, USA.

   Microsoft, Windows, Windows NT, the Windows 95 logo, and
   Open Database Connectivity are trademarks or registered trademarks
   of Microsoft Corporation.
