DB2/2 v1.2 Service Pak 7035
==============================

Welcome to DB2/2

This README file contains information for DB2/2 v1.2 Service Pak 7035.
Please see Section 1.2 for Sevice Pak install information.

Part 1 contains important information about this Service Pak. It includes
installation instructions and details changes to the product since the
shipping of DB2/2 v1.2.0 (GOLD, syslevel WR07000).

NOTE (1): If an existing version of DB2/2 is executing it should be
stopped before applying the Service Pak.

NOTE (2): For client/server platforms, this Service Pak should be
applied to both DB2/2 v1.2 server and DB2/2 v1.2 client workstations.

NOTE (3): After installation is complete, you will need to re-bind your
databases. Refer to section 1.2.5.1 for details.

NOTE (4):  If you have  received private fixes from IBM support after
94/11/17, then you should contact IBM support after the service pak
installation, to request an updated version of the private fixes. By
doing this, you are assured that your system is in a consistent state
and no private fixes are lost.


========
CONTENTS

1.0 Part 1 - Service Pak 7035  DECEMBER, 1994
1.1 Introduction
1.2 Service Pak Installation
  1.2.1 Pre-Requiste
  1.2.2 Co-Requistes
  1.2.3 Installation Instructions
  1.2.4 CID Install Instructions
  1.2.5 After installation (IMPORTANT)
    1.2.5.1 Rebinding bind files
    1.2.5.2 Copying files from \os2\install directory
    1.2.5.3 Copying CAEDOSAD.ZIP
1.3 General Information
  1.3.1 Service Information (US/Canada)
    1.3.1.1 Database 2 OS/2 and Distributed Database Connection Services/2 Support
    1.3.1.2 Electronic Customer Support and Corrective Service
    1.3.1.3 Accessing Corrective Service and Customer Support
  1.3.2 The DB2 Family Newsletter
  1.3.3 Submitting Suggestions to IBM
1.4 Defects Fixed
  1.4.1 Database Engine APAR DESCRIPTIONS
    1.4.1.1  APAR JR00056: Incorrect Connection Information
    1.4.1.2  APARs JR08022, JR08150: Memory leak in SQLEFREE API
    1.4.1.3  APAR JR08083: SMP enhancements
    1.4.1.4  APAR JR08111: DB22KILL failed
    1.4.1.5  APAR JR08155: Truncated value of NP,FP in DBM REORGCHK
    1.4.1.6  APAR JR08157: APPC error F015-00000000
    1.4.1.7  APAR JR08180: RUNSTATS returned incorrect results
    1.4.1.8  APAR JR08211: PCDR lost connections
    1.4.1.9  APAR JR08218: SQL1042 When doing ROLLFORWARD AND STOP
    1.4.1.10 APAR JR08257: Floating point exception errors
    1.4.1.11 APAR JR08263: Fix for DB2/2 running on WARP
    1.4.1.12 APAR IX45867: Fortran precompiler problem
  1.4.2 Other Database Engine Fixes
    1.4.2.1 STARTDBM failed
    1.4.2.2 Importing from CD-ROM failed with SQL3025N
    1.4.2.3 Default pipe name
  1.4.3 DOS/Windows Requester APAR Descriptions
    1.4.3.1 APAR JR07968: SQL30080 when trying to use alternate adapter
  1.4.4 Query Manager APAR Descriptions
    1.4.4.1 APAR JR07346: Incorrect data in header text
    1.4.4.2 APAR JR07467: Problem with BREAKS in QM forms
    1.4.4.3 APAR JR07475: Could not use 3 or 9 as mnemonic keys
    1.4.4.4 APAR JR07904: Invisible text while changing row conditions
    1.4.4.5 APAR JR07797: Extra headers for updated records
    1.4.4.6 APAR JR08152: Shift-F9 did not bring up Command line window
    1.4.4.7 APAR JR08198: QRW0541 with TRACE ON
  1.4.5 Database Administration Tools (DBAT) Changes
  1.4.6 First Failure Support Technology (FFST) CSD 485
    1.4.6.1 CM alerts not being received at host
    1.4.6.2 NO INHERIT bit was not set
    1.4.6.3 Trap in EPWCUA.DLL when using software installer to INSTALL
    1.4.6.4 Starting EPW.EXE caused a ghost window in minimized window viewer
    1.4.6.5 Multiple Message Log Formatters Displayed
    1.4.6.6 Trap D in DOSCALL1:DOSSEMSET as called by EPWSVC16
    1.4.6.7 Verify Hang/CMSTOP ABNORMAL did not work on CM 1.11
    1.4.6.8 Make EPWINST use WPS icons on OS/2 2.0 and above
    1.4.6.9 FFST/2 Message Log Formatter caused SYS3175 on OS/2 WARP

1.0 Part 1 - Service Pak 7035  DECEMBER, 1994
1.1 Introduction

This Service Pak introduces performance enhancements for DB2/2 running
on Symmetric Multiprocessor (SMP) environments as well as Uniprocessor
environments. It also provides several other fixes to problems reported
since General Availability of Version 1.2.0.

The effect and descriptions of these changes to the product is the subject of
the following topics.



1.2  Service Pak Installation

This Service Pak can be used to install fixes for all components of DB2/2 v1.2
(Database Engine, DOS/Windows Requester, Query Manager and Database
Administration Tools.)


1.2.1  Pre-Requiste

This Service Pak can be applied to all DB2/2 v1.2.0 (syslevel WR07000)
configurations (server, standalone, client, client with local databases and
OS/2 distributed client feature.)

NOTE: This Service Pak CANNOT be applied to any version of
Client Application Enabler (CAE) and Software Development
Kit (SDK).  CAE and SDK products have separate Select/Service
Paks.


1.2.2 Co-Requistes

In order to run with the new DDCS/2 v2.2 fixes in Service Pak 7036, you
must install BOTH the DB2/2 Service Pak 7035 and the
DDCS/2 v2.2 Service Pak 7036.

For client/server platforms, appropriate Service Paks should be
applied to all DB2/2 server and client workstations. This Service
Pak can be applied to all DB2/2 v1.2 servers and clients.

If this Service Pak is applied to a DB2/2 v1.2 server acting as a host
for DB2/2 v1.0 clients or to DB2/2 v1.2 clients connecting to a
DB2/2 v1.0 server, the Service Pak WR07030 should be applied
to the DB2/2 v1.0 workstations.



1.2.3  Installation Instructions

To start the Presentation Manager Service Pak install, type DB2INST on a command
line, select ACTION from the action bar and then SERVICE from the pull down menu.

If you have just finished installing IBM DB2/2, an IBM DB2/2 Service or Select
Pak, IBM Lan Server/Requester, or IBM CM/2, please shutdown and reboot your
system before installing this DB2/2 Service Pak.

You may have to reboot twice, once after the installation of these products to
process any locked files, and a second time after installing this Service Pak
to process some additional locked files.

NOTE: If you choose to backup your files, please be aware that any files
that already exist in the backup directory you specify will be overwritten.
If you want multiple level of backups please specify different backup
directories.


1.2.4  CID Install Instructions

The Service Pak CID install program (DB2CID.EXE) uses the same syntax as the
DB2/2 CID install program.  Refer to the DB2/2 Installation Guide for a
description.

For DB2/2 CID Service Pak install, please use the sample response file
DB2CID.RSP provided on diskette 1.  This file can be modified to fit your
installation needs.

NOTE: The keywords found in DB2CID.RSP are the ONLY supported CID keywords in
this version of the CID install program.  These keywords are:

     DBBACKUPSYSTEM
     DBSTOPCOMMUNICATIONS
     DBUPDATECONFIGSYS
   * DBUPDATETYPE
     DBUSEREXIT1
     DBINSTALLDATABASETOOLS
     DBINSTALLQUERYMANAGER
     DBINSTALLDOSREQSUPPT
     DBINSTALLWINREQSUPPT
     DBINSTALLDOCUMENTATION
  ** DBINSTALLENGINE
     DBCOPY
     DBINCLUDE
     DBUSEREXIT2
  ** DBREPLACE


For a description of the CID install key words, refer to Appendix B of the
DB2/2 Installation Guide.


* NOTE (1): The CID keyword DBUpdateType can only be equal to 1, which specifies
  to install the Service Pak.  No other values are supported.


** NOTE (2): Two keywords have been added to support the Service Pak install:
   > DBInstallEngine  - install the database engine (1=YES 0=NO).
   > DBReplace - replaces files on the target system if they have a later
              date/time stamp than the ones shipped with the Service
              Pak (1=YES 0=NO).


NOTE (3): If a certain component, say, Query Manager is not installed on
a given system, specifying CID keyword DBInstallQueryManager=Y would have
no effect.  It would just be ignored for that particular system and
no Query Manager fixes would be installed.

NOTE (4): If you choose to backup your files, please be aware that any files
that already exist in the backup directory you specify will be overwritten.
If you want multiple level of backups please specify different backup
directories.



1.2.5 After Installation - IMPORTANT
1.2.5.1 Rebinding bind files

Due to new bind (.BND) files that have been shipped with this Service Pak,
you will need to rebind your DB2/2 bind files to your databases after the
Service Pak installation. This step is necessary for the fixes in this Service
Pak to become effective.


Run "sqlbind x:\sqllib\@sqlubind.lst your_dbname" for each  of your databases
(where your_dbname is the name of your database and
           x: is the drive containing the SQLLIB directory).

The above step only needs to be performed once per database. If multiple
clients use the same database, the database needs rebinding on only one client.


1.2.5.2 Copying files from \os2\install directory

This Service Pak updates the files DB2LVL.ASC and DCFLVL.ASC
in \OS2\INSTALL directory of your workstation's boot drive.
These files are installed by the initial product install and also used
by the remove function.  Without the newer versions of these files,
the remove function will not work.  If you use the product diskettes
to remove the product
then you must TEMPORARILY change the .ASC files on diskette 1
to the new ones installed by the service pak.  If you then use those
diskettes to do a product install you must put the original
versions of the .ASC files back onto the diskettes before installing.
To copy these files to diskette 1 of the product diskettes:

for DB2/2 diskette 1,
 copy Y:\OS2\INSTALL\DB2LVL.ASC A:  (where A: contains DB2/2 DISK 1)
 (Y: is the workstation's boot drive)

for OS/2 DCF diskette 1,
 copy Y:\OS2\INSTALL\DCFLVL.ASC A:  (where A: contains OS/2 DCF DISK 1)
 (Y: is the workstation's boot drive)


1.2.5.3 Copying CAEDOSAD.ZIP

This Service Pak ships a new version of the file CAEDOSAD.ZIP.
This file is not automatically installed. You must manually install
it from Disk 3 of the Service Pak. Please refer to "What's New
Version 1.2" for more information on this file.

1.3 General Information
1.3.1  Service Information (US/Canada)
1.3.1.1 Database 2 OS/2 and Distributed Database Connection Services/2 Support

Call 1-800-992-4777 for information regarding free and chargeable
service options or to receive assistance on

 - IBM DATABASE 2 for OS/2 (DB2/2) Version 1.2 and Version 1.0
 - IBM Distributed Database Connection Services/2
   (DDCS/2) Version 2.2 and Version 2.0


Assistance is also available using the electronic options described below.


1.3.1.2 Electronic Customer Support and Corrective Service

The following electronic support is available:

Customer support is provided via a questions-and-answers (Q&A) forum
provided by the DB2/2 Service Team.  The forum is accessible
through CompuServe, IBMLink, and TALKLink as described below.

Corrective Service is provided in two forms - Select Paks
and Service Paks.  A Service Pak contains all fixes that have
accumulated since the product first became generally available.
A Select Pak is a small group of fixes that have accumulated since
the last Select or Service Pak and can be packaged by components
within a product.

Service Paks will be issued approximately every 6 to 8 months
and Select Paks may be issued approximately every 3 to 4 months
depending on the number, severity and visibility of fixes that have
accumulated.

If you cannot obtain these Select or Service Paks electronically please
call 1-800-992-4777 to request them to be sent to you in the mail.



1.3.1.3  Accessing Corrective Service and Customer Support

CompuServe - call 1-800-848-8199 in Canada or the US for membership information.
 -Execute GO IBMDB2.
 -Use DB2/2 section for questions and answers.
 -Use DB2/2 library for fixes and other files.

US (IBMLink) TALKLINK OS/2 BBS call 1-800-547-1283 for membership information.
 -Go to OS2BBS in TALKLINK.
 -Choose Service Package section (Corrective Service only).
 -Access DB2OS2 FORUM (Q&A and Technical Support).

Canadian IBMLink OS/2 BBS - call 905-474-6666 or 1-800-268-3100 for
membership information.
 -Go to IBMLink from the IIN Menu.
 -Type ICONF on the IBMLink Desktop.
 -Select View from the Conference File Selection List.
 -Select Option 5 Select Files and type: WR* * (NOTE: these two asterisks are
  wildcards) (Corrective Service only).
 -Select DB2OS2 FORUM (Q&A and Technical Support).

The Select and Service Paks are also available on the Technical
Connection CD ROM.  To order call 1-800-992-4777.


The next methods are available for Corrective Service only.

Internet.
 -FTP to anonymous server software.watson.ibm.com (129.34.139.5).
 -Enter 'anonymous' as the userid and your complete e-mail address as the
  password.
 -Go to pubs/db2/os2 directory.

Canadian IBM PS BBS - to dial into the BBS call 905-316-4255 Toronto,
416-492-1823 Toronto, 514-938-3022 Montreal, or 604-664-6464 Vancouver
(8 databits, no parity, 1 stop bit).
 -Go to area 34 OS/2 Database and Host.

US IBM PCC BBS - to dial into this BBS, call 919-517-0001 Raleigh (8 databits,
no parity, 1 stop bit).
 -Go to Directory 4 (the CSD Directory).



1.3.2 The DB2 Family Newsletter

This is a bi-monthly newsletter that reports the latest news for the family
of DB2 products (DB2 and DDCS on all available platforms: OS2, AIX, MVS...)

If you are interested in receiving this newsletter, please mail or fax
your request to

  IBM Canada Ltd.
  Database Technology Planning
  2S/110/1150/TOR
  1150 Eglinton Avenue East
  North York, Ontario
  Canada, M3C 1H7

  Attn: T.D. Sole
  Fax:  (416) 448-2114


1.3.3 Submitting Suggestions to IBM

If you have any suggestions to enhance our products, there are two
vehicles to communicate your requirements to IBM.

* If your organization has an IBM representative, discuss your
  requirements with your IBM representative, and have them submit your
  requirements to the DATABASE TECHNOLOGY PLANNING group at TOROLAB2(DBMREQ).

* Or, send your detailed requirements to the following address:

  IBM Canada Ltd.
  Database Technology Planning
  2S/110/1150/TOR
  1150 Eglinton Avenue East
  North York, Ontario
  Canada, M3C 1H7

  Attn: M.H. Switzer
  Fax:  (416) 448-4414



1.4 Defects Fixed

This section describes changes that have been made to the product as a result
of direct customer feedback. The descriptions contained in this section are for
the fixes that have gone into the product since DB2/2 v1.2.0 GOLD (WR07000)
shipped.

1.4.1 Database Engine APAR DESCRIPTIONS
1.4.1.1  APAR JR00056: Incorrect Connection Information

When a DB2/2 user connnected to DB2/6000 or other DB2 workstation platforms,
the connection information returned was incorrect.
This fix corrects the problem.



1.4.1.2  APARs JR08022, JR08150: Memory leak in SQLEFREE API

Repeated calls to SQLEFREE API could have resulted in the following error:

SQL1022: There is not enough memory available to process this command.

A fix has been implemented to prevent this memory leak.



1.4.1.3  APAR JR08083:  SMP enhancements

This new feature provides DB2/2 v1.2 the ability to scale with increased number
of processors in a symmetric multi-processor (SMP) environment. This enhances
the product's performance when used with OS/2 SMP operating system. DB2/2
performance in uniprocessor environments is also improved as a result of this
fix.


1.4.1.4  APAR JR08111:  DB22KILL failed

When invoked, DB22KILL did not always disconnect all APPC client connections
to the DB2/2 server. This problem has been fixed.



1.4.1.5  APAR JR08155:  Truncated value of NP,FP in DBM REORGCHK

When a DBM REORGCHK was performed, the NP and FP values were truncated
if the number of pages in SYSIBM.SYTABLES exceeded 99999.  NP and FP can
be up to 6 digits long and this fix ensures their values are not truncated.
However, this fix may cause DBM REORGCHK output to misalign and/or
exceed 80 characters in width when NP and FP are large.



1.4.1.6  APAR JR08157: F015-00000000 disconnecting from database accessed via APPC

Previously database applications connecting/disconnecting from a database
accessed via APPC sometimes received the APPC error sense code:
F015-00000000 Insufficient stack size

This problem has been resolved.



1.4.1.7  APAR JR08180: RUNSTATS returned incorrect results

Prior to the implementation of this fix, running statistics (RUNSTATS) returned
incorrect AVECOLLEN (average column length) under certain circumstances.
This fix corrects the problem.



1.4.1.8  APAR JR08211: DOS clients intermittently lost connection to DB2/2 server

When PC DOS Requester (PCDR) clients were connected to a DB2/2
server, the server could get into a state where it would lock out
further PCDR clients from establishing a connection. However, the
server continued to function properly for the  clients still connected
to it.

This problem has been fixed to prevent new PCDR clients from being
locked out by the server.



1.4.1.9  APAR JR08218: SQL1042 when doing ROLLFORWARD AND STOP

If the use of a database was abnormally terminated, e.g. due to a power
failure, the subsequent recovery of the database, using the command
ROLLFORWARD AND STOP, generated the following error message:

SQL1042 An unexpected system error occured.

This message could also be produced after the STOP button was pressed
in the recovery tool, if the backup of the abnormally terminated database
was restored using rollforward from the recovery tool . The error only
occured if the database was configured with USEREXIT=ON and LOGPRIMARY=63.
This has been fixed and the SQL1042 is no longer returned under such
circumstances.



1.4.1.10  APAR JR08257:  Floating point exception errors

This fix adds floating point exception protection to handle floating
point underflow/overflow errors. Floating point exceptions have
the potential to trap the operating system. This fix sets the estimate
number of records involved in a query to default to a system
minimum/maximum when a floating point exception is encountered,
thereby preventing a system trap.



1.4.1.11  APAR JR08263: Fix for DB2/2 running on WARP

Previosly DB2/2 DLLs were not being unloaded appropriately from the
memory in OS/2 WARP 3.0. Prior to this fix, NetViewDM/2 encountered
problems while running concurrently with DB2/2 on WARP.

This fix is necessary for Net View DM/2 users requiring support for DB2/2
in the WARP release of OS/2.



1.4.1.12  APAR IX45867: Fortran precompiler problem

The Fortran precompiler did not have a provision for identifiers that began
with keywords (e.g. end, program, function, subroutine, etc.).
If a Fortran source file with embedded SQL statements had variables
such as endFlag and programName, the Fortran compiler produced a
redeclaration error for the generated Fortran source. This fix corrects
the problem and allows identifiers to begin with keywords.

1.4.2  Other Database Engine Fixes
1.4.2.1  STARTDBM failed
Previously, STARTDBM use to fail if db2npipe was set to an invalid name.
This fix allows Database Manager to start successfully even if db2npipe
is set incorrectly.


1.4.2.2  Importing from CD-ROM failed with SQL3025N
Previously, an error occurred when trying to import data from a CD-ROM drive.
The following error code was returned:

SQL3025N: The datafile parameter is not valid.

This fix has corrected the problem.


1.4.2.3  Default pipe name
Previously, DB2/2 was incorrectly looking at the environment variable DB2NPIPE
for the pipe name.  The fix will make it look at DB2PIPENAME instead.
DB2PIPENAME is used for overriding the default pipe name.


1.4.3 DOS/Windows Requester APAR Descriptions
1.4.3.1 APAR JR07968:  SQL30080 when trying to use alternate adapter

Previously, a DB2/2 DOS Client received SQL30080 RC=15 while attempting to use
an alternate adapter if the workstation was configured for both primary and
alternate adapters.  This fix correct the problem.



1.4.4 Query Manager (QM) APAR Descriptions
1.4.4.1 APAR JR07346:  Incorrect data in header text

Incorrect data was displayed in the header text of a Query Manager report
using a form.  This error occured if a variable column (eg. &N) was
referenced in the header text of the report and the report exceeded 1 page
per break (breaks are used to group the report output by unique column
values). This problem has been fixed.



1.4.4.2 APAR JR07467:  Problem with BREAKS in QM forms

In a Query Manager form, if there were only a few lines on a page
before a BREAK, then a new page would not be started after the break.
This problem has been fixed.



1.4.4.3 APAR JR07475:  Could not use 3 or 9 as mnemonic keys

When creating a Query Manager Menu, users can specify a
mnemonic for each menu action.  This allows them to press just
the mnemonic key to execute the menu action when the menu is
being run.  The problem was that a mnemonic of 3 or 9 did not work
if 3 or 9 was pressed on the number pad.  Instead, page up and page
down were performed.  All other numbers on the keypad worked
fine as mnemonics.  This fix allows 3 and 9 to be used as mnemonic
keys on the number pad.



1.4.4.4 APAR JR07904:  Invisible text while changing row conditions

After creating a prompted query, if you try to change the row
conditions, you get a window titled "Change Left-Side of row
condition".  Prior to this fix, the text in this window was partly
invisible (blanked out). This fix allows the text to be viewed
in its entirety.


1.4.4.5 APAR JR07797:  Extra headers for updated records

Previously, forms produced to display QM output had more than one header
in the output. Extra headers were generated before the entries for updated
records.  This fix ensures no additional headers are received in in the QM
output forms.


1.4.4.6 APAR JR08152:  Shift-F9 did not bring up Command line window

In Query Manager (QM), once in the "main selection" for a database, the
Commands pulldown menu indicates that Shift-F9 can be used to bring up the
command line pop-up window.  Shift-F9 did not bring up the QM Command
line pop-up window.  This fix corrects the problem.



1.4.4.7 APAR JR08198:  QRW0541 with TRACE ON

On a DBCS system (JAPAN), Query Manager (QM) returned QRW0541 RC= 11008
when trying to initialize. This occured if OS/2 System trace was on. This
fix corrects the problem and allows QM to initialize with TRACE ON.



1.4.5 Database Administration Tools (DBAT) Changes

A minor fix has been made to Configuration tool.



1.4.6 First Failure Support Technology (FFST) CSD 485

The FFST/2 CSD 485 is shipped with this Service Pak. The descriptions
of FFST changes since CSD 460 (shipped with DB2/2 v1.2 WR07000)
are described in this section.


1.4.6.1 CM alerts not being received at host

When using the alert generating program to route Communications Manager (CM)
alerts through CM gate-way to Netview host it was found that alerts were not
being received at the host. This fix corrects the problem.


1.4.6.2 NO INHERIT bit was not set

Pipe handles did not have the NO INHERIT bit set.  This fix sets the
NO INHERIT bit.


1.4.6.3 Trap in EPWCUA.DLL when using software installer to INSTALL

When installing a product that uses IBM Software Installer Version 1.1
for OS/2 a trap occured in EPWCUA.DLL. The trap occurred a number of
seconds after the installation had indicated that it was complete and
'hung' the OS/2 prompt from which "a:install" was typed.  This fix
corrects the problem.


1.4.6.4 Starting EPW.EXE caused a ghost window in minimized window viewer

Executing EPW.EXE from anything other than CONFIG.SYS caused
a ghost window to appear in the Minimized Window Viewer.  For example,
if EPW.EXE was not running, executing EPW.EXE from the command line
would produce the ghost window.  Also, If EPW was running, executing EPW OFF,
then EPW ON produced the ghost window as well.  Another time this
problem occured was when FFST/2 was stopped and started via Dos calls
(DosExecPgm) from code.  This fix corrects the problem.

1.4.6.5 Multiple Message Log Formatters Displayed

The problem occured when 1 copy of the message log formatter was open
and another was inadvertantly started.  The user receives a pop-up asking
if they would like to open another message log formatter. The reply is either
OK or CANCEL. If CANCEL was chosen and a second copy was started anyway.
This fix corrects the problem.


1.4.6.6 Trap D in DOSCALL1:DOSSEMSET as called by EPWSVC16

When starting the message log formatter a trap occured when running
the following scenario:  Four 3270 sessions were running over a Token-Ring
network with an ehllapi application running in a loop that searches
continuously for a particular string to appear in a session.  After a
long period (ie. 24 hours) and the log formatter is started a trap D
sometimes occurs in DAOCALL1:DOSSEMSET. This fix corrects the problem.


1.4.6.7 Verify Hang/CMSTOP ABNORMAL did not work on CM 1.11

The problem occured when an X.25/ISDN configuration running on Communications
Manager (CM) 1.11 was stopped abnormally through SSM and then CMSETUP.EXE
was started.  When exiting out of CMSETUP, verification of the configuration
never ended (was hung) and CM would not stop.  This fix corrects the problem.


1.4.6.8 Make EPWINST use WPS icons on OS/2 2.0 and above

This fix installs the FFST OS/2 2.0 icons for OS/2 versions 2.0 or greater.
For OS/2 versions before 2.0, FFST OS/2 1.3 icons are installed.


1.4.6.9 FFST/2 Message Log Formatter caused SYS3175 on OS/2 WARP

After running the Message Log formatter from FFST/2 a SYS3175
error was encounterd. The problem occured on OS/2 WARP while
running FFST/2 concurrently with CM/2 1.11.
This fix corrects the problem.


***********************************************************************
**                                                                   **
**  (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1994.  **
**                    ALL RIGHTS RESERVED.                           **
**                                                                   **
***********************************************************************

