5722XE1 V5R3M0 IBM iSeries Access for Windows

In this directory are fixes for V5R3M0 iSeries Access for Windows Data
Transfer that are not in the SI30707 service pack:

APAR SE35276: CA400EXP-IDB2DATA-INCORROUT .NET EXCEPTION 'SYSTEM.INDEXOUTOFRANGEEXCEPTION' WHEN DATA CONTAINS A NULL
  An application using the iSeries Access for Windows .NET provider to access data on the
  iSeries encounters an exception when getting data. The application is using
  the DataAdapter.Fill method to get data from the iSeries but the data has an embedded null.
  This results in an exception in the application, 'System.IndexOutOfRangeException'. If
  the same is done using the iSeries Access OLEDB IBMDASQL provider no exception is
  encountered.

This fix ONLY applies to V5R3M0 service pack SI30707.  Please do not attempt to
apply this fix to any other release of iSeries Access for Windows, or any other
service pack level.

If you need to contact Service about problems with these modules, you should
mention that you are using the cwbtfutl.dll file from the ftp site and the
SE35276 directory.

The file size and install location are as follows:

  cwbdc.dll    159791 bytes   (Windows install path)\system32

Note: The default path iSeries Access for Windows is installed to is:
  C:\Program Files\IBM\Client Access

This fix is applied by replacing the file or files on a PC with those that
contain fixes.  If you later re-install a service pack or the entire
product, the testfix file(s) will be overwritten.

File replacement instructions
------------------------------------------------------------------------------
For each file in this fix:
1) Locate the file on your client workstation, in the location noted above.
2) Back up the old file by copying it and adding ".bak" to its name.
   For example: filename.dll would be copied to filename.dll.bak
3) Copy the fix version of the file into the same directory.  If this file
   is in use and cannot be replaced, copy it to the directory by adding ".new"
   to its name.
   For example: filename.dll would be copied to filename.dll.new
4) If one or more of the files in this fix could not replace the old one,
   shutdown the PC and re-start it in safe mode with no networking; then
   copy each .new file to the actual fix filename.
   For example: filename.dll.new would be copied to filename.dll
5) You may need to shutdown and re-start Windows normally for the fix to
   fully take effect.