   ============================================================================
       Readme File for System i Access for Windows Service Packs
            5761-XE1 V6R1M0 Cumulative Service Pack Level
                            -------------
                               SI29455
                            -------------
       (c) Copyright IBM Corporation 2007.  All rights reserved.
========================================================================

NOTICE:                                                                        
-------                                                                        
   Application of this PTF may disable or render ineffective programs that
   use system memory addresses not generated by the IBM translator,            
   including programs that circumvent control technology designed to limit
   interactive capacity to purchased levels. This PTF may be a prerequisite 
   for future PTFs. By applying this PTF you authorize and agree to the 
   foregoing. 

   This PTF is subject to the terms of the license agreement which
   accompanied, or was contained in, the Program for which you are obtaining
   the PTF.  You are not authorized to install or use the PTF except as part 
   of a Program for which you have a valid Proof of Entitlement.

   SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
   AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
   AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF 
   MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
   REGARDING THE PTF.

   The applicable license agreement may have been provided to you in printed
   form and/or may be viewed using the Work with Software Agreements (WRKSFWAGR)
   CL command.                                                      
   
-----------------
Table of Contents
-----------------
1.0  INSTALLATION INSTRUCTIONS
 1.1  INSTALLING FROM A System i
 1.2  INSTALLING FROM A LOCAL OR NETWORK DRIVE
 1.3  COMBINING THE SERVICE PACK WITH A System i ACCESS FOR WINDOWS INSTALL IMAGE 
2.0  RECOMMENDATIONS/RESTRICTIONS
 2.1  iSeries SERVER FIXES
 2.2  APPLICATION DEVELOPMENT FUNCTION WITHIN System i NAVIGATOR
 2.3  iSeries NAVIGATOR DATABASES COMPONENT 
3.0  AUTHORIZED PROGRAM ANALYSIS REPORT (APAR) ABSTRACTS
      - SERVICE PACK LEVEL = SI29455 (November 2007)
4.0  INSTALL/UNINSTALL CONSIDERATIONS
 4.1  REMOVING THE SERVICE PACK
 4.2  UNABLE TO INSTALL FROM THE SERVICE SOURCE?
 4.3  SERVICE PACK CONTROL
5.0  DATA TRANSFER CONSIDERATIONS
 5.1  TRANSFERRING DATA WHEN THE FILE OR DATA CCSID IS 65535

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

1.0  INSTALLATION INSTRUCTIONS
------------------------------

1.1  INSTALLING FROM A System i
--------------------------------------
   The following method would be used if you have received the System i
   Access for Windows service pack through the System i PTF ordering process
   either as an individual PTF order or as part of an i5/OS PTF cumulative 
   package.

   Once this service pack has been applied to a System i with the LODPTF and
   APYPTF System i commands, it can be installed on individual PC's with the 
   "Check Service Level" shortcut in the System i Access for Windows Service 
   folder.

   Check Service Level, controlled by the System i Access for Windows 
   Properties Service tab, will detect that the Service source directory has 
   been updated, and will present the user with the option to install the 
   service pack at startup time as well.

   The APYPTF command will update each of the System i Access for Windows 
   install image directories (\QIBM\ProdData\Access\Windows\image32, 
   \QIBM\ProdData\Access\Windows\image64a and 
   \QIBM\ProdData\Access\Windows\image64i) on the System i.  Any client that 
   installs System i Access for Windows (or selected features) from one of 
   these images will automatically receive this service pack level (no extra 
   steps or reboots).  In this scenario, the service pack cannot be uninstalled
   on the client PC because it is merged in with the base release.

   NOTE: The System i contains three System i Access for Windows install 
   images, one for each processor architecture supported by System i Access for
   Windows:    
   \QIBM\ProdData\Access\Windows\image32 for 32-bit (X86) based PCs, 
   \QIBM\ProdData\Access\Windows\image64a for AMD64 based PCs and 
   \QIBM\ProdData\Access\Windows\image64i for Itanium based PCs.
   
   Running setup.exe from the System i Access for Windows install image 
   directory that matches your PC's processor type (\image32 for 32-bit (X86) 
   based PCs, \image64a for AMD64 based PCs or \image64i for Itanium based PCs)
   will launch the install wizard for that specific architecture.
   
   Running cwblaunch.exe from the System i Access for Windows install image 
   root directory (\QIBM\ProdData\Access\Windows) will determine your PC's 
   processor architecture and accordingly launch the install wizard from the
   appropriate image directory.  

   RMVPTF will restore your System i install image to the prior service level 
   (or the base release if there was no prior service pack applied). 
     

1.2  INSTALLING FROM A LOCAL OR NETWORK DRIVE
---------------------------------------------
   The following method would be used if you have received the System i Access
   for Windows service pack as a set of install image files via a download from
   IBM's FTP site.

   Install the service pack by running the "SETUP.EXE" program from your PC.
   This program is part of the install image files shipped with a service pack.
   If you change the System i Access for Windows Properties Service tab Source
   Directory to the directory containing these install image files, you can 
   also use the "Check Service Level" shortcut in the System i Access for 
   Windows Service folder.

   Before running this program, copy the service pack install image files to a
   local drive on your PC or to any accessible network drive. Once the install
   setup program has completed, you can then remove the install image files 
   from that drive.


1.3  COMBINING THE SERVICE PACK WITH A System i ACCESS FOR WINDOWS INSTALL IMAGE 
--------------------------------------------------------------------------------
   The following method could be used if you downloaded the service pack patch 
   from the System i Access for Windows web page location: 
      http://www-03.ibm.com/systems/i/software/access/

   The System i Access for Windows service pack PTFs are combined with the 
   original System i Access for Windows installation images in 
   \QIBM\ProdData\Access\Windows\image32, 
   \QIBM\ProdData\Access\Windows\image64a and 
   \QIBM\ProdData\Access\Windows\image64i.

   This means that a user can install (or upgrade) System i Access for Windows 
   from one of these combined image directories and get the latest applied 
   service level automatically in one integrated step - since the original 
   installation images files have been replaced by updated versions via the 
   service pack PTF.

   If your install image resides on a local or network drive, you can combine
   the service pack with the image by applying a patch. You will need to create
   an administrative install image and then use the UPDATE.EXE download in the
   FTP directory to patch the administrative image with the latest service pack
   updates. To create the administrative install image follow these steps:
   
   1. Open a command prompt window.
   2. Change directories to the folder containing the System i Access for 
      Windows install image. This can be the image on the System i, the image
      on the System i Access for Windows DVD or an image on a local or network 
      drive.
   3. Run the following command:
         SETUP.EXE /a
      The installation wizard will start.
   4. If your install image has multiple language sources, you will be prompted
      to choose one as your Primary Language.
   5. In the Network Location dialog, choose the target directory for your
      administrative image and click Install.
      
   The administrative image will be generated under the chosen directory. You 
   only need to perform this process once. The resulting administrative image 
   can be subsequently patched as many times as needed.
   
   Once you have an administrative image, you can patch it by following these 
   steps:
   
   1. Download UPDATE.EXE from the FTP directory to a directory on your PC or 
      server.
   2. Open a command prompt window.
   3. Change directories to the folder containing UPDATE.EXE.
   4. Run the following command:
         UPDATE.EXE /v"/a X:\admin_image\cwbinstall.msi"
      where X:\admin_image denotes the drive and directory containing the 
      administrative image.
      The installation wizard will start.
   5. Follow the instructions in the wizard to start the update process.
   4. The target administrative image will be automatically updated to the new
      service level from the UPDATE.EXE patch.
   5. After completion, you can delete the downloaded UPDATE.EXE file, as it is
      no longer needed.
      
   A user that installs from the patched administrative image will get the 
   latest applied service level automatically. Users that originally installed
   from the administrative image can reinstall by running SETUP.EXE from the 
   patched image or by using the "Check Service Level" shortcut in the System i
   Access for Windows Service folder to get the latest service level. 
   
   NOTE: Users that originally installed System i Access for Windows from the
   System i, from the System i Access for Windows DVD or from any other source
   that contains a non-administrative image, will not be able to reinstall from
   an administrative image. Only installations that were initially done from an
   administrative image can be updated by reinstalling from a patched 
   administrative image.


2.0  RECOMMENDATIONS/RESTRICTIONS
---------------------------------

 2.1  System i SERVER FIXES
--------------------------
   In addition to installing the System i Access for Windows Service Pack, 
   all servers should stay current on the latest Cumulative PTF Package, HIPER Group PTF, 
   and Database Group PTF. Refer to
   IBM eServer System i Technical Support: Recommended fixes at
   http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes

 2.2  Application Development function within System i Navigator
---------------------------------------------------------------
   The Application Development folder within System i Navigator
   is added when the System i Navigator Network component 
   is installed.  
   Application Administration can be used to restrict 
   the display of the Application Development folder 
   to certain users or groups of users. 

 2.3 System i NAVIGATOR DATABASES COMPONENT 
------------------------------------------
   The Import Data and Export Data wizards in System i Navigator use the CPYFRMIMPF 
   and CPYTOIMPF CL commands, respectively.  The commands may function check with a 
   MCH3402 message when executed by System i Navigator.  The first time the wizards execute 
   the command it will succeed, but later attempts may fail if the database host server job 
   is reused for a later use of the wizard.  
   The commands may fail with a CPF4248 message with reason code 3 for an ASCII or Unicode CCSID.  
   This is an error in writing data to the error record file (ERRRCDFILE parameter on the 
   CPYFRMIMPF command) if the data file is ASCII or Unicode.
   Lastly, a problem with system names that contain double quote characters has been identified. 
   Apply the latest PTFs for CPYFRMIMPF and CPYTOIMPF on the server if you plan to use the 
   Import Data and Export Data wizards.  At a minimum apply SI17635, SI17385 and SI20204 for 
   product 5722SS1 V5R3M0.

   In V5R4M0, SQL Assist was changed so that 'smart statement selection' can be used to
   pre-prime the SQL statement at the cursor position into the SQL Assist dialog.  In V5R3M0
   and earlier, the user had to manually select the SQL statement that SQL Assist would use.  
   The new design is similar to using 'smart statement selection' to execute an SQL statement.
   However, when 'smart statement selection' is enabled, the user will be unable to position 
   the cursor at an arbitrary place in the script and start with a default SQL statement in 
   SQL Assist.  The SQL statement nearest the cursor position will be shown in the SQL Assist dialog.  
   If the user wishes to use SQL Assist to insert a new statement into the script, disable 
   'smart statement selection' with the 'Options/Smart Statement Selection' menu item.  
   SQL Assist will appear with a default statement, or with the text that was explicitly selected 
   as it would in V5R3M0.

3.0  AUTHORIZED PROGRAM ANALYSIS REPORT (APAR) ABSTRACTS
--------------------------------------------------------
   This a list of APAR fixes included in this service pack.
   Each service pack is cumulative; the current service pack
   includes all the fixes from the prior service pack levels.
   The APAR abstracts are listed by installable component
   within a service pack level.

---------------------------------
Service Pack Level = SI29455
Build date = November 2007
---------------------------------

  REQUIRED PROGRAMS
  -----------------
  APAR SE30715 : CA400EXP-INSTALL-INCORROUT General Availability Updates.
    V6R1M0 GA fixes. Build 20071122.
  
  OPTIONAL COMPONENTS
  -------------------
  No fixes.

  System i NAVIGATOR
  -----------------
  No fixes.

  DATA ACCESS
  -----------
  No fixes.     

  AFP WORKBENCH VIEWER
  --------------------
  No fixes.

  TOOLBOX FOR JAVA
  ----------------
  Includes JTOpen 6.1 (11/1/2007) and the equivalent of PTF 5761JC1 SI29061.
  
  
  5250 DISPLAY AND PRINTER EMULATION
  ----------------------------------
  PC5250 Version 5.9 Level 20071102

  SECURE SOCKETS LAYER (SSL)
  --------------------------
  No fixes.

  PRINTER DRIVERS
  ---------------
  No fixes.

  OPERATIONS CONSOLE
  ------------------
  No fixes.
                                                                               
  PROGRAMMER'S TOOLKIT
  -------------------- 
  No fixes. 


4.0  INSTALL/UNINSTALL CONSIDERATIONS
-------------------------------------
   The following sections describe additional support and known
   problems that you may notice while using the Install/Uninstall
   function.

4.1  REMOVING THE SERVICE PACK
------------------------------
   Currently, service packs cannot be removed. If you need to backtrack a 
   service pack, you have to uninstall System i Access for Windows and install
   it again from an image that doesn't contain the service level -the System i
   Access for Windows DVD, for instance.
   
   Only service packs that are installed from the UPDATE.EXE patch download
   can be uninstalled. Patches will be supported in a future service pack.

4.2  UNABLE TO INSTALL FROM THE SERVICE SOURCE?
-----------------------------------------------
   If you experience problems while installing a service pack over 
   slow communication lines, and if installing from a DVD or a faster
   connection is not possible, then the service pack could be 
   installed in this manner:

   1)  A setting exists on the System i Access for Windows Properties
       Service tab that will copy the service pack image to the
       PC's temporary directory, install the service pack, then
       remove the copied files.  To use this support you will
       need to specify this setting ("Copy install image to PC
       before installing").

   2)  Run Check Service Level (either from the IBM System i Access
       for Windows Service folder shortcut or when Check Service 
       Level runs at system boot on its defined schedule)

       STATUS:
        No status information is displayed while the files are
        copied.  To determine if the transfers are progressing, look
        in the 'CA400CKV' temporary directory (beneath
        the PC temporary directory, for example
        C:\Documents and Settings\username\Local Settings\Temp).  
        You should see new files appear periodically.

   3)   Proceed through the install wizard to complete the install.
  
4.3  SERVICE PACK CONTROL
-------------------------
  To prevent users from installing the Service Pack, an 
  administrator can use the SP.TXT file.  If the administrator
  places a file named SP.TXT (with a 'N' in the first position of 
  the first line) in the service pack installation image directory,
  the service pack will not be installed.

5.0  DATA TRANSFER CONSIDERATIONS
---------------------------------
  The following sections describe additional support or known
  problems that you may notice while using the Data Transfer function.

5.1  TRANSFERRING DATA WHEN THE FILE OR DATA CCSID IS 65535
-----------------------------------------------------------
  WHY DOES MY DATA LOOK LIKE GARBAGE WHEN I PERFORMED A DOWNLOAD?
  By default, the Data Transfer function will not convert data between
  EBCDIC and ASCII if the data is tagged with a CCSID of 65535.  In
  older versions of the Win 95/NT Client Access product, the 65535
  conversion was controlled by the CWBTFR.INI file.  This process
  has been changed, and the conversion is now controlled by the
  Data Transfer user interface.  Once the setting has been made in the
  user interface, it is then stored in the transfer request.  This is
  only true for .TTO, .TFR, .DTT, and .DTF files.  .RTO and .DT files are still
  controlled by the CWBTFR.INI file.  The conversion setting for .RTO
  and .DT files can be modified in the Data Transfer user interface, 
  but the setting will not be saved.

  The setting to control the conversion is found in the File, 
  Properties information.

  WARNING:  This feature is designed as a workaround for people that 
            can not change the CCSID of their files.  In order for this
            translation to work properly, you must be confident the
            data in the file matches the CCSID of your user profile.
            The design of the System i is that data with a 65535 CCSID
            are not to be converted.  This feature will attempt to do a
            conversion of the data from the job CCSID to the PC CCSID.
            This conversion may not work if the data in the file does
            not match the user profile/job CCSID.

  The correct solution to this problem is to appropriately tag the data
  with the correct CCSID.  One way of doing this is by using CHGPF.

  For more information on the 65535 CCSID, please reference the
  System i National Language Support Manual.
