5722XE1 V5R4M0 IBM iSeries Access for Windows

In this directory are fixes for V5R4M0 iSeries Access for Windows iSeries
Navigator that are not in the SI25949 service pack:

APAR SE28018: CA400EXP-NETWORK-INCORROUT Incomplete UCW phone list
  An Originator Connection Profile is configured using iSeries
  Navigator, so a connection to a system within China can be
  made. After the ATT/ prefix is added to the profile name, the
  connection does not work reliably.

PREREQUISITE INSTALLS: APAR SE27912 and APAR SE27913
  This fix replaces a file that contains other fixes.  Because of this,
  you should install the above APAR fixes BEFORE installing this one.
  Download the fixes for these at (join the two lines into one in your
  browser):

    ftp://ftp.software.ibm.com/as400/products/clientaccess/win32/v5r4m0/
    files/iNav/Network/SE27912_SE27913

  and follow the instructions in the readme.txt file to install them,
  then install this fix.

This fix ONLY applies to V5R4M0 service pack SI25949.  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 files from the ftp download site, for the above
APARs.  The file sizes and locations are as follows:

  cwbuntpi.jar    840500 bytes   (iSeries Access install)\Classes

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.