5761XE1 V6R1M0 IBM System i Access for Windows

In this directory are fixes for V6R1M0 System i Access for Windows Data
Transfer that are not in the SI31251 service pack:

APAR SE32981: CA400EXP-DTRANSFER-MSGCWBDB0052 RETRIEVING A LIST OF LIBRARIES AND FILES FAILED
              ON JAPANESE SYSTEM I ACCESS
  	When a user clicks the "Browse" button on "Data Transfer From 
        System i" of Japanese System i Access in order to retrieve a 
        list of libraries and files, it fails with CWBDB0052. CWB0111 
        is also issued in the History Log. This happens after install 
        of SI30128. 
        The same problem happens also on "Data Transfer To System i".


This fix ONLY applies to V6R1M0 service pack SI31251.  Please do not attempt to
apply this fix to any other release of System i 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 cwbdc.dll file from the ftp site and the
se32981 directory.

The file size and install location are as follows:

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

Note: The default path System i 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.