The identifier for this special build is "special_17206", "U810940_17206"
It has been delivered through PMR 03148 branch 033,000

This includes the fix for 
   APAR IY95759
and is built on top of 
   version DB2 v9.1.0.2  fixpack 2  build "s070210", "U810940"

This build can be applied only on the above level of code unless
the build is a full image. This build will be supported for 90 days
after the release of the official fixpack containing the APAR(s).

Please note that even though this special build received a certain
level of testing, IBM still recommends that you put this change through
your standard quality and assurance testing procedures.

-----------------------------------------------------------------------------

Instructions for installing the fix:

Stop all database instances.
   (eg. db2stop force, ).
Shut down the administration server instance
   (eg. db2admin stop force)
Shut down the Fault Monitor.
Stop all applications accessing DB2.

On each node where db2 is installed, perform the following as root:

 1. issue "slibclean"
 
 2. backup the original files under the install directory
    where <directory> is what is shown in the list of files at the bottom of
    this README.  For example, if replacing bin/db2level on version 9, the
    file to be backed up and replaced is /opt/IBM/db2/V9.1/bin/db2level.
    NOTE: In V9, you may have selected a different install path. If this is
    the case, then replace the files under that path.    

 3. copy the new files into place and use the chmod/chown commands to ensure the
    same permissions and ownership are maintained.  Below are permissions and 
    ownership for files which are commonly shipped for special builds.
     -r--r--r--   bin:bin libdb2.a
     -r--r--r--   bin:bin libdb2e.a     

    NOTE: if a file provided does not exist on your system, it does not need
    to be copied / installed.

 4. once you have copied your files into their install path, you need to
    re-run db2chgpath which is in DB2DIR/install - that will reset all the
    RPATHs, including the one in the file(s) they you have copied in there.

 5. issue db2iupdt on each instance (use dasupdt for the DAS Administrative
    instance if it exists.

To switch back to the original level, simply follow the same procedure
replacing the new files with the originals.

cksum output for files provided:
2550559156 31748 ./instance/native/install/libdb2install_install.a
1471985983 17990415 ./lib32/libdb2.a
2938114416 29112 ./lib32/libdb2install.a
3601559911 20530842 ./lib64/db2o.o
3732107787 56040115 ./lib64/libdb2.a
1902496286 80097668 ./lib64/libdb2e.a
3181218878 90828 ./lib64/libdb2install.a
3181218878 90828 ./das/lib/libdb2install.a