*******************************************************************
    **
    **  (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1998.
    **                    ALL RIGHTS RESERVED.
    **
    *******************************************************************
 
         Welcome to IBM* DB2 Universal Database* (DB2*) Extenders
                            Version 5.2 PTF
 
    This PTF adds new functions to and fixes problems in DB2 UDB Extenders
    V5.2 for AIX client and AIX server in a partitioned database server
    environment.

 
    1.0 NEW FUNCTIONS 
    _________________

    QBIC support is now available in DB2 UDB Extenders V5.2 for AIX client
    and AIX servers in a partitioned database server environment.
    This support includes the DMBRedistribute API and
    REDISTRIBUTE nodegroup command, which are used to redistribute
    QBIC feature data in a partitioned database server environment.
    Use the API or command:

    o Whenever you add or remove a node from a nodegroup, that is,
      you run DB2's redistribution API or command-line processor command.

    o If you redistributed prior to using QBIC, and then plan to create a 
      QBIC catalog. In this case, you need to use the API or command 
      before an image is cataloged into the QBIC Catalog. However this could 
      happen immediately after an image is stored in a user table. So it is
      recommended that you use the API or command right after you create 
      the first QBIC catalog.

    In addition, a new environment variable, DB2MMCATALOGDELAY, has been
    added. The environment variable is used to set the time interval, in 
    seconds, for QBIC automatic cataloging. The range is 1 through an extremely
    large number; the default value is 60.


    2.0 FIXES
    _______
 

    o If a database connection did not exist, commands issued through the
      db2ext command-line processor, returned incorrect messages.

    o The DBiBrowse API and DBaPlay API returned an SQL error code. For
      example, the QBICDEMO sample program returned this SQL error code when
      the DBiBrowse API was executed in the program.

    o QBIC administrative APIs sometimes returned SQL error codes and messages
      for a previously executed API.

    o If the QbQuerySetFeatureData API was specified using a client file as the
      source for feature data, the API failed. For example, if a user specified
      AVERAGE FILE to the QBICDEMO sample program, (this runs an average
      color query based on feature data in a client file), the
      QbQuerySetFeatureData( ) API in the program failed.

    o Potential hang when disabling the last extender.

    o The DBvBuildStoryBoardFile API returned errors such as trap and unable to
      extract a frame from last scene.

    o The DBvOpen API returned errors such as unknown packet type.

    o The FindTrackName UDF and FindInstrument UDF returned SQLSTATE=38624,
      source content of type BLOB_LOCATOR.

    o The Content UDF and Replace UDF did not work properly if specified with
      source content of type BLOB_LOCATOR.

    *  are trademarks or registered trademarks of IBM Corporation.
    ** are trademarks or registered trademarks of their respective owners.