HIPER APAR JR16294

We have discovered a defect in our USEREXIT in OS/2 that will be uncovered
on September 9th, 2001.

Customer Impact:

Inability to perform DB2 UDB backups on OS/2 via a USEREXIT as of
September 9th, 2001.

Problem:

As of September 9th 2001 Database Backups on OS/2 via a USEREXIT for a
database alias of 8 characters will no longer work and as such a backup
will not be taken.  The error or message you see will be dependant on how
you have coded your userexit; If you are using the default userexit, you
will see an invalid parameter error being reported by the userexit.

It is on Sept 9  the 32-bit time value gains a digit to go from 999999999
to 1000000000.  The result is that DB2 will not pass the fifth parameter,
the MODE or sequence #, to the BACKUP USEREXIT.

This problem is only related to the OS/2 platform and does not affect
other USEREXITs (eg. LOG) or Backups taken without USEREXITs.

Solution:

Apply DB2 UDB for OS/2 APAR JR16294

Workaround:

Catalog another database alias to your database using 7 characters or less
and use this database alias for performing your backups.  You must ensure
that the restores are performed using the same database alias as was used
for the backup.  By cataloging a separate alias, you avoid having to
reconfigure all your remote database clients; making it transparent to your
users.

Fix location and installation:

The fix for this problem has been uploaded to the DB UDB FIXPAK FTP site in
the OS/2 directory for each release currently in service.  The patched DLL
are stored in the archive file db22v?_JR16294.zip (? will be replaced by 5,
6 or 7 depending on your DB2 version).

All NLV would use the same patch.  A readme in the same directory (English
only) is available to outline the problem/workaround/patch installation
(JR16294.TXT).


ftp://ftp.software.ibm.com/ps/products/db2/fixes/english/db2os2v5/FP16_WR21262/
ftp://ftp.software.ibm.com/ps/products/db2/fixes/english/db2os2v61/FP8_WR21255/
ftp://ftp.software.ibm.com/ps/products/db2/fixes/english/db2os2v7/FP3_WR21251/


Note that this fix can only be applied to the current FIXPAK level and will
not correct the problem for customers on special/private builds.  They will
need to use the workaround until the next FIXPAK is made available.

Download the correct version of the fix for your installation into a
temporary directory.  Unzip the file JR16294.zip to extract the modified
DLLs and db2level.exe.

For DB2 v5.2, the following files will be extracted from db22v5_JR16294.zip:

   db2eutil.dll
   db2level.exe

For DB2 v6, the following files will be extracted from db22v6_JR16294.zip:

   db2eng.dll
   db2eutil.dll
   db2util.dll
   ddcseng.dll
   db2level.exe

For DB2 v7, the following files will be extracted from db22v7_JR16294.zip:

   db2eutil.dll
   db2level.exe

DB2 will need to be stopped before the fix can be applied.

After DB2 has been stopped, copy the DLLs that were extracted from
JR16294.zip into \sqllib\dll and copy db2level.exe into \sqllib\bin.

When all files have been copied restart DB2.