=========================================================================
    Readme File for AS/400 Client Access for Windows 95 Service Packs
            5763-XD1 V3R1M2 Cumulative Service Pack Level
                            -------------
                               SF40828
                            -------------
       (c) Copyright IBM Corporation 1996.  All rights reserved.
=========================================================================

    IMPORTANT: Be sure to check Informational APAR II09221 for the
    latest list of OS/400 PTFs that must be installed on the AS/400
    prior to attempting any Client Access functions. Some of the
    fixes contained in this service pack PTF may not work if these
    OS/400 PTFs are not installed on the AS/400.  If you have
    internet access, the text of Informational APAR II09221
    is available at "http://www.as400.ibm.com/client/ii09221.txt"

Summary of new fixes:
      Win95 shutdown problem with NetSoft and PC/5250 is fixed. See
      APAR SA59667.


---------------------------------
Table of Contents
---------------------------------
1.0  OS/400 PROGRAM TEMPORARY FIXES (PTFs) REQUIRED
2.0  INSTALLATION INSTRUCTIONS
 2.1  INSTALLING FROM A MANAGING AS/400 SYSTEM
 2.2  INSTALLING FROM A LOCAL OR NETWORK DRIVE
 2.3  INSTALLING FROM DISKETTE
 2.4  INSTALL/UNINSTALL CONSIDERATIONS
  2.4.1  REMOVING THE SERVICE PACK
 2.5  NETSOFT ROUTER CONSIDERATIONS
  2.5.1  INSTALLING SERVICE PACKS ON SDLC-ATTACHED PC's
  2.5.2  INSTALLING SERVICE PACKS ON ASYNC-ATTACHED PC's
  2.5.3  INSTALLING WINDOWS 95 32-BIT TWINAX SUPPORT
  2.5.4  INSTALLING SERVICE PACKS ON TWINAX-ATTACHED PC's
 2.6  DATA TRANSFER CONSIDERATIONS
  2.6.1  TRANSFERRING DATA WHEN THE FILE CCSID IS 65535
 2.7  PC5250 CONSIDERATIONS
  2.7.1  STATUS POP-UP WINDOW
 2.8  IBM PERSONAL COMMUNICATIONS CONSIDERATIONS
  2.8.1  ROUTER STATE
 2.9  ANYNET CONSIDERATIONS
  2.9.1  ANYNET OVER ETHERNET
3.0 WINDOWS NT 4.0 Support
  3.1 ENABLING TWINAX DRIVERS
  3.2 ENABLING SDLC DRIVER
4.0 Graphical Access Considerations
  4.1 Saving changes to GA400.INI
5.0  AUTHORIZED PROGRAM ANALYSIS REPORT (APAR) ABSTRACTS
      - SERVICE PACK LEVEL = SF37523 (February 1997)
      - SERVICE PACK LEVEL = SF39220 (March 1997)
      - SERVICE PACK LEVEL = SF39669 (April 1997)
      - SERVICE PACK LEVEL = SF40828 (June 1997)

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

1.0  OS/400 PROGRAM TEMPORARY FIXES (PTFs) REQUIRED
---------------------------------------------------
   For a list of OS/400 PTFs that must be installed on the AS/400
   prior to attempting any Client Access functions, please reference
   Informational APAR II09221.

2.0  INSTALLATION INSTRUCTIONS
------------------------------

2.1  INSTALLING FROM A MANAGING AS/400 SYSTEM
---------------------------------------------
   Note:
   The following method would be used if you have received the Client
   Access service pack through the AS/400 PTF ordering process either
   as an individual PTF order or as part of an OS/400 PTF cumulative
   package.

   Once this service pack has been applied to the managing AS/400
   system with the LODPTF and APYPTF AS/400 commands, it can be
   installed on individual PC's with the "Install Service Pack"
   program icon in the Client Access Accessories folder.

   The "Client Access Login Service Check" program icon created in
   the Windows 95/NT Startup folder will also detect that the
   managing AS/400 system has been updated, and will present the user
   with the option to install the service pack at startup time as
   well.

2.2  INSTALLING FROM A LOCAL OR NETWORK DRIVE
---------------------------------------------
   Note:
   The following method would be used if you have received the Client
   Access service pack as a set of install image files.

   Install the service pack by the running the "SETUP.EXE" program
   from your PC. This program is part of the install image files
   shipped with a service pack.

   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.

2.3  INSTALLING FROM DISKETTE
-----------------------------
   Note:
   The following method would be used if you have received the Client
   Access service pack as a set of install diskettes.

   Install the service pack by inserting diskette 1 into your
   diskette drive and running the "SETUP.EXE" program. Follow the
   setup program instructions, inserting additional diskettes as
   required.

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

2.4.1  REMOVING THE SERVICE PACK
--------------------------------

   To remove this service pack from your PC:

   1. Click the Windows 95 Start button, click on Settings, and then
      click on Control Panel.
   2. Double-click on the Add/Remove Programs icon.
   3. Click on the Install/Uninstall tab, click on IBM Client Access
      for Windows 95 Service Pack SFxxxxx item, and then click on the
      Add/Remove button.
   4. Follow the instructions on the screen.

2.5  NETSOFT ROUTER CONSIDERATIONS
----------------------------------
   The following sections describe additional support and known
   problems that you may notice while using the NetSoft router to
   install service packs with some connectivities.

2.5.1  INSTALLING SERVICE PACKS ON SDLC-ATTACHED PC's
-----------------------------------------------------
   If you have an SDLC-attached PC, and the only connectivity that
   you have to the AS/400 for that PC is SDLC, then you will be
   unable to install the service pack to your PC using conventional
   means (by clicking on the "Install Service Pack" program icon in
   Client Access Accessories folder).

   The suggested way of installing the service pack in this case is to
   take one of the options below.

   1) A parameter has been added to Check Version, cwbckver.exe,
      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 new support you will need to get the
      latest Check Version, cwbckver.exe, on the PC and change the
      parameters of the 'Client Access Login Service Check' icon in
      the 'StartUp' folder.

      SET UP STEPS

      1. Make sure you have the new Check Version installed
         on the PC before using the new parameter.  If it is not
         installed the parameter will be ignored.
      2. Right mouse click on the 'Start' button in the task bar.
      3. Select the 'Explore' menu choice.
      4. Double-click on the 'Programs' folder.
      5. Double-click on the 'StartUp' folder.
      6. Right mouse click on the 'Client Access Login Service
         Check' icon.
      7. Select the 'Properties' menu choice.
      8.  Click on the 'Shortcut' tab.
      9. In the 'Target:' entry field will be something similar to:
         "C:\Program Files\IBM\Client Access\cwbckver.exe"  LOGIN

      After the 'LOGIN' parameter add ' 0 LOCAL'.  The 'Target:'
      entry field should now look like:
      ...\cwbckver.exe"  LOGIN 0 LOCAL

     PARAMETERS Explained

     LOGIN parameter tells Check Version to do the login service
           check.
     0     is the number of seconds to wait after check version
           starts before checking the service level on the managing
           system.
     LOCAL parameter tells Check Version to copy the service pack
           install image files from the managing system to a
           temporary directory on the PC.  The files will be copied
           to the 'CA400' directory in the Windows 95 Temp
           directory (For example, C:\Windows\Temp\CA400 ).  If the
           CA400 directory does not exist check version creates it.
           If check version creates the directory it will also
           delete it when it is finished.

    POSSIBLE ERRORS:
      - A message is issued if there is not enough disk space to
        copy all the files.  If you get this message you will need
        to free disk space on the hard drive specified in the message.
      - A message is issued if one of the files could not be
        successfully copied.
        If you select OK, check version will attempt to copy the
        remaining files and install the service pack.
        If you select Cancel, check version will stop copying files
        and delete any of the files it has already copied.

    STATUS:
      No status information is displayed while the files are
      copied.  To determine if check version is progressing look
      in the 'CA400' temporary directory (For example
      C:\Windows\Temp\CA400). You should see new files appear
      periodically.

    NOTES:
      1. The LOCAL parameter also works for upgrades to a new
         release.  To use check version to automatically upgrade you
         will need to use the LOCAL parameter to avoid the time out.

   2) Find another Windows 95 PC connected to the AS/400 that uses a
      different connectivity (such as token ring), and create a set
      of service pack install diskettes.  To do this choose
      "Accessories" from the Client Access folder, then choose
      "Create Install Diskettes", and then choose "Service
      Pack (SP)". When this is completed, use these diskettes to
      install the service pack onto your SDLC-attached PC (by running
      SETUP.EXE from diskette 1).

   3) Find another non-Windows 95 PC connected to the AS/400 and copy
      the files from QCA400\WIN32\SERVICE\CDROM directory to a set of
      diskettes, and then create a temporary directory on your
      SDLC-attached PC's hard drive, and copy the files from the
      diskettes to that directory. Run SETUP.EXE from that directory.

2.5.2  INSTALLING SERVICE PACKS ON ASYNC-ATTACHED PC's
------------------------------------------------------
   If you have an Async-attached PC, and the only connectivity that
   you have to the AS/400 for that PC is Async, then you will be
   unable  to install the service pack to your PC using conventional
   means (by clicking on the "Install Service Pack" program icon in
   Client Access Accessories folder).

   The suggested way of installing the service pack in this case is
   to take one of the options below.

   1) A parameter has been added to Check Version, cwbckver.exe,
      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 new support you will need to get the
      latest Check Version, cwbckver.exe, on the PC and change the
      parameters of the 'Client Access Login Service Check' icon in
      the 'StartUp' folder.

      SET UP STEPS

      1. Make sure you have the new Check Version installed
         on the PC before using the new parameter.  If it is not
         installed the parameter will be ignored.
      2. Right mouse click on the 'Start' button in the task bar.
      3. Select the 'Explore' menu choice.
      4. Double-click on the 'Programs' folder.
      5. Double-click on the 'StartUp' folder.
      6. Right mouse click on the 'Client Access Login Service
         Check' icon.
      7. Select the 'Properties' menu choice.
      8.  Click on the 'Shortcut' tab.
      9. In the 'Target:' entry field will be something similar to:
         "C:\Program Files\IBM\Client Access\cwbckver.exe"  LOGIN

      After the 'LOGIN' parameter add ' 0 LOCAL'.  The 'Target:'
      entry field should now look like:
      ...\cwbckver.exe"  LOGIN 0 LOCAL

     PARAMETERS Explained

     LOGIN parameter tells Check Version to do the login service
           check.
     0     is the number of seconds to wait after check version
           starts before checking the service level on the managing
           system.
     LOCAL parameter tells Check Version to copy the service pack
           install image files from the managing system to a
           temporary directory on the PC.  The files will be copied
           to the 'CA400' directory in the Windows 95 Temp
           directory (For example, C:\Windows\Temp\CA400 ).  If the
           CA400 directory does not exist check version creates it.
           If check version creates the directory it will also
           delete it when it is finished.


    POSSIBLE ERRORS:
      - A message is issued if there is not enough disk space to
        copy all the files.  If you get this message you will need
        to free disk space on the hard drive specified in the message.
      - A message is issued if one of the files could not be
        successfully copied.
        If you select OK, check version will attempt to copy the
        remaining files and install the service pack.
        If you select Cancel, check version will stop copying files
        and delete any of the files it has already copied.


    STATUS:

      No status information is displayed while the files are
      copied.  To determine if check version is progressing look
      in the 'CA400' temporary directory (For example
      C:\Windows\Temp\CA400). You should see new files appear
      periodically.


    NOTES:
      1. The LOCAL parameter also works for upgrades to a new
         release.  To use check version to automatically upgrade you
         will need to use the LOCAL parameter to avoid the time out.


   2) Find another Windows 95 PC connected to the AS/400 that uses a
      different connectivity (such as token ring), and create a set
      of service pack install diskettes.

      To do this choose "Accessories" from the Client Access folder,
      then choose "Create Install Diskettes", and then choose
      "Service Pack (SP)". When this is completed, use these
      diskettes to install the service pack onto your Async-attached
      PC (by running SETUP.EXE from diskette 1).

    3) If you don't have access to another PC with an AS/400
       connection, then the service pack can still be installed.

       To do this, follow these steps:
       a) Make a connection to the AS/400 (from your
          Async-attached PC).
       b) Assign a Network drive to the AS/400, using Explorer.
       c) Create a temporary directory on your local hard drive,
          and copy all of the files in the QCA400\WIN32\SERVICE\CDROM
          directory to that directory.
       d) Run SETUP.EXE from that temporary drive.

2.5.3  INSTALLING THE WINDOWS 95 32-BIT TWINAX SUPPORT
------------------------------------------------------
   After you have installed Client Access Service Pack SF39220, a new
   subdirectory with the update software will be created on your computer.
   This TWINAX directory will be created under the directory in which Client
   Access was installed.  The path is normally
   "C:\Program Files\IBM\Client Access\twinax", where C: is the drive where
   Client Access is installed.  Print off the README.TXT in the TWINAX
   directory.  Follow the README.TXT instructions to go through the
   installation process (INSTALL.EXE).

   Refer to informational APAR II10307 for additional information.

2.5.4  INSTALLING SERVICE PACKS ON TWINAX-ATTACHED PCs
------------------------------------------------------
   If you have a twinax-attached PC and you are not currently able to connect,
   then you will be unable to obtain the service pack using conventional means
   (by clicking on the "Install Service Pack" program icon in Client Access
   Accessories folder).  The suggested way of obtaining the service pack in
   this case is to take one of the options below.

   1) Find another Windows 95 PC connected to the AS/400 that uses a different
      connectivity (such as token ring), and create a set of service pack
      install diskettes.  To do this choose "Accessories" from the Client
      Access folder, then choose "Create Install Diskettes", and then choose
      "Service Pack (SP)". When this is completed, use these diskettes to
      install the service pack onto your twinax-attached PC (by running
      SETUP.EXE from diskette 1).
   2) Find another non-Windows 95 PC connected to the AS/400 and copy the
      files from QCA400\WIN32\SERVICE\CDROM directory to a set of diskettes,
      and then create a temporary directory on your twinax-attached PC's hard
      drive, and copy the files from the diskettes to that directory. Run
      SETUP.EXE from that directory.
   3) Additional means of obtaining service packs are described in
      informational APAR II09523.

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

2.6.1  TRANSFERRING DATA WHEN THE FILE CCSID IS 65535
-----------------------------------------------------
   If you are using the Data Transfer function and the CCSID of the
   AS/400 file is 65535 the transfer will not normally convert
   between ASCII and EBCDIC.  A transfer from the PC to the AS/400
   will give the following message: "CWBTF0005 - Data in this field
   is incorrect or does not match PC data type."

   Transfers from the AS/400 to the PC will complete but the data
   will not be converted and will appear as hexadecimal data on
   your PC.

   To force ASCII to EBCDIC conversion when the AS/400 file has a
   CCSID of 65535 you must do the following:

   Use a PC editor such as Notepad or Wordpad to create a file called
   CWBTFR.INI in your windows directory (Usually C:\WINDOWS for
   Windows 95 and C:\WINNT for Windows NT 4.0).  Then Add the
   following lines to force translation for files with CCSID 65535:

   [Client Access Data Transfer]
   ForceTranslation=1;     for translation of 65535 data

   The AS/400 job CCSID will be used for the conversion.  Data
   Transfer will also convert from the PC CCSID to the AS/400 job
   CCSID for transfers to the AS/400 when fields are tagged with the
   65535 CCSID.

   If the CWBTFR.INI file is not found, or the correct section and
   value names are not present in the CWBTFR.INI file, Data Transfer
   will default to not translate 65535 data.

   WARNING: Enable this fix only if you are confident the data
            contained within columns tagged with the 65535 CCSID are
            in a defined CCSID that matches the user profile CCSID of
            the jobs that will access it.  Accessing 65535 CCSID data
            from a job CCSID that does not match the data may corrupt
            data within the database file.  If you don't enable this
            fix by providing a CWBTFR.INI file, transfers will
            continue to behave as they did before applying this PTF.

            Columns tagged with the 65535 CCSID are designed to not
            be converted when transferring to/from the PC.  Use of
            this fix, which forces a conversion to take place, is to
            be done only when it is not possible to change the column
            or file CCSID from 65535. Every attempt should be made to
            appropriately tag the data with the correct CCSID.

            For more information on the 65535 CCSID, see topic
            2.2.3.2 in the AS/400 National Language Support book,
            SC41-1301-00.

            Conversions from CCSID 65535 fields are prone to errors
            under multi-language situations where AS/400 user job
            CCSIDs do not match.

2.7  PC5250 CONSIDERATIONS
--------------------------

   The following sections describe additional support or known
   problems that you may notice while using the PC5250 function.



2.8  IBM PERSONAL COMMUNICATIONS CONSIDERATIONS
-----------------------------------------------
   The following sections describe additional support or known
   problems that you may notice while using an IBM Personal
   Communications connection.

2.8.1  ROUTER STATE
-------------------
   If you use the IBM Personal Communications connection type, the
   connection must first be made through IBM Personal Communications.
   Client Access will start this connection for you when IBM Personal
   Communications has not been started, only if the following are
   true:

   - The directory that IBM Personal Communications is installed to
     is in the PATH environment variable.
   - The connection to the desired AS/400 is defined correctly in the
     IBM Personal Communications default configuration file.

   If either of the above is not true, the IBM Personal
   Communications connection must be started manually before using
   Client Access functions.

2.9  ANYNET CONSIDERATIONS
-------------------------
   The following sections describe additional support or known
   problems that you may notice while using an AnyNet connection.

2.9.1  ANYNET OVER ETHERNET
---------------------------
   When using AnyNet over an Ethernet connection, check the SSAP AA
   value for the Ethernet line description on the AS/400.  This value
   should be set to 1480.  If it is set to 1496 (the default), you
   will have problems getting a communications connection to the
   AS/400 using Client Access.

3.0 WINDOWS NT CONSIDERATIONS
------------------------------

3.1 Enabling Twinax Drivers
---------------------------

   The twinax drivers are installed when Client Access is installed
   on your Windows NT system.  Before you can use the drivers you
   must enable them, to enable them a user with administrator
   authority needs to do the following:

   Go to My Computer -> Control Panel -> Devices.  Scroll down the
   list of devices until you find IBMTwx, IBMTwxNM, IBMTwxSN.
   For each device select the device and press the start button.
   Do your Netsoft and Client Access configurations and try to make
   a connection.

   If the connection is successful return to the Devices window and
   again find the IBMTwx, IBMTwxNM, IBMTwxSN devices,  this time
   for each device select the device, press the startup button and
   choose automatic as the startup type.

   If the connection does not work it is probably because of a IRQ,
   IO address, or shared memory conflict.  Use the following
   information to resolve conflicts.

   The default settings for the ISA twinax driver are as follows:
    IRQ           - 0x00000005
    IO Address    - 0x0000271A
    Shared Memory - 0x000DC000

   If these values are not correct for your card or if they conflict
   with another card you may need to change the settings.  To do
   this use the regedit program and edit the following key:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMTwx\parameters

   The default settings for the PCMCIA card driver are as follows:
    InterruptNumber         - 0x0000000A
    IOBaseAddress           - 0x00000300
    MemoryMappedBaseAddress - 0x000CC000

   If these values are not correct for your card or if they conflict
   with another card you may need to change the settings.  To do
   this use the regedit program and edit the following key:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMTwxSN1\Parameters
                                                                
3.2 Enabling SDLC Drivers
---------------------------
   The SDLC drivers are installed when SNA communications are
   installed on your Windows NT system.  Before you can use the
   drivers you must enable them, to enable them a user with
   administrator authority needs to do the following:
   Go to My Computer -> Control Panel -> Devices.  Scroll down
   the list of devices until you find VNSSDLCI.  Select the
   VNSSDLCI device and press the startup button, change the startup
   type from manual to automatic and restart your Windows NT system.

4.0 Graphical Access Considerations
-----------------------------------
   4.1 GA400.INI
   ----------------
   If you have made any changes in the Graphical Access configuration
   file GA400.INI, applying this service pack will overlay those
   changes.  You will need to make the changes again after applying
   the service pack.

5.0  AUTHORIZED PROGRAM ANALYSIS REPORT (APAR) ABSTRACTS
--------------------------------------------------------
   The following lists the APARs fixed at each of the service pack
   levels.  Each service pack PTF is cumulative, that is, the most
   recent service pack PTF released contains all the fixes from prior
   service pack levels in addition to the APARs listed for a
   particular service pack. The fix abstracts are listed by
   installable component within a service pack level.


 ---------------------------------
   Service Pack Level = SF40828
      Build date = June 1997
 ---------------------------------

Base Support
------------
APAR = SA61787
  When the Client Access Login Service Check (Check Version) connects
  to an AS/400 via either NetSoft or TCP/IP, the conversations are
  not deallocated when CheckVersion completes.

  The Check Version task starts a communications link with the AS/400
  by mapping a UNC drive.  UNC drives can only be disconnected by the
  operating system. The drive should eventually be disconnected, and
  the conversations should then end.  However, the operating system
  does not seem to have a predictable algorithm for disconnecting a
  UNC drive. We have seen times ranging from 15 minutes to well over
  an hour.

  Rather than mapping a UNC drive to the AS/400, Check Version will map
  a drive by explicitly assigning it a drive letter.  This type of
  drive assignment can be disconnected by Check Version when it is done
  with the drive.  When the drive is disconnected, any conversations
  started by Check Version will end.

APAR = SA62241
  The Client Access for Windows 95 Create Install Diskettes
  program does not create installation diskettes for a secondary
  language correctly.  When Setup is executed from the
  diskettes that are created for a secondary language, the
  text displayed on the screen is actually the text for the
  primary language.

APAR = SA62760
  Customer runs RMTCMD to execute a program on the AS/400.
  The program runs normally but when it tries to return
  a message back to the PC, the PC fails with CWB0111.

APAR = SA62966
  Some Windows NT 4.0 workstation configurations cause the Client
  Access for Windows 95/NT installation program to fail to create
  the Client Access icons.  The Client Access installation
  appears to be successful, but no icons are created.

  This PTF can be used to create Client Access icons on Windows NT PCs
  which have Client Access installed, but do not have Client Access
  icons in the Start Menu/Programs.

  The following steps describe how to install this PTF fix to the PC.
  This fix is installed by creating a connection to the AS/400 containing
  the PTF and running Client Access Install Service Pack (Check Version).
  This starts the Service Pack Setup program located on the managing
  AS/400.  The last step is to create the Client Access icons by running
  the Client Access CWBICONS program.

   1. Apply the Service Pack (PTF) with the fix onto your managing
      AS/400 system.

   2. Configure a connection to the managing AS/400 system.  Because
      you don't have icons to use, you need to run the AS/400
      Connections program directly from the Windows NT Explorer.

      a) Open the Windows NT Explorer.

      b) Select the directory where Client Access is installed.

      c) Find and run CWBCONN (CWBCONN.EXE).  Double-clicking
         will run the program.

   3. The Add Connection Wizard will be displayed.  Follow the
      Add Connection Wizard steps to add a connection to the
      managing AS/400.  This process is described in the
      Client Access Setup Guide.

   4. Run the Client Access Install Service Pack (Check Version) program.
      Because you don't have icons to use, you need to run the
      program directly from an MSDOS Command Prompt window.

      a) Open an MSDOS Command Prompt window.

      b) Change the current directory to the path where Client
         Access is installed.

      c) Start the Check Version program by entering the command

         cwbckver CSDINSTALL

      d) The Check Version program will start the Service Pack
         Install program from the managing AS/400 system.

      e) Install the Service Pack by following the Setup wizard
         instructions.

   5. After the Service Pack is installed on the PC and the computer
      has been restarted the Client Access icons can be created by
      using the CWBICONS command.

      a) Open the Windows NT Explorer.

      b) Select the directory where Client Access is installed.

      c) Find and run CWBICONS (CWBICONS.BAT).  Double-clicking
         will run the program.

      The Setup program will start and create the icons for all
      of the Client Access components that are installed on the PC.
      When CWBICONS finishes you should see the Client Access icons
      in the Start Menu/Programs.

APAR = SA63394
  Using VB with DAO to return multiple result sets from a stored
  procedure.  Instead of doing a SQLFreeStmt with the SQL_UNBIND
  option the application is unbinding each of the columns
  individually and rebinding them between result sets.  If one
  of the result sets has fewer columns than the previous result
  set, the ODBC driver will incorrectly indicate an error to the
  application.  VB returns a 3146 error code to the application.

APAR = SA63505
  When using Client Access for WindowsNT with the Netsoft router,
  Chkver may hang.  This failure typically occurs when the
  communication connection to the AS/400 has been dropped.

APAR = SA63941
  The 16-bit Client Access support, or thunking layer, is not
  consistently providing translation. Applications which work
  in the Client Access for Windows 3.1 client as well as the
  Client Access for Windows 95 clients at V3R1M0 and V3R1M1 do
  not work in V3R1M2. The most visible example is the 16-bit
  ODBC driver, needed to run 16-bit ODBC applications over APPC
  connections. During the ODBC connection the driver sets a
  default SQL library using the first library from the "Default
  Libraries" in the data source. The library name is not being
  translated and nulls are sent up in its place. This eventually
  results in an error MSGSQL5010 being received by the driver
  when the SQL statements cannot be processed. To circumvent this
  aspect of the error, remove all libraries from the "Default
  Libraries" in the data source.

AFP WorkBench Viewer
-------------------
 None

5250 Display and Printer Emulator
---------------------------------
APAR = SA60494
  Customer wrote an RPG application program which writes some
  records on a display file. Using PC5250 emulator the program issues
  the first screen, then the session freezes and the job must
  be closed using ENDJOB. The problem can be circumvented by DFRWRT(*NO)
  in the display file, but the program becomes too slow. No error
  messages are logged by the AS400 or the pc.

APAR = SA61796
  Application written using DDS windows fails using PC5250
  Emulator with MSGCPF5192 RC10050135 when restoring a previous
  screen. Application works fine on Graphical Access or CM/2.

APAR = SA62205
  When in a subfile screen using a dds keyword and the arrow key
  is pressed to send cursor to input field, an invalid page fault occurs
  in module pcsktk52.dll. If he disables the dds keyword csrinponly, he
  is able to work around the problem since the cursor is no longer
  jumping to the input fields when pressing an arrow key.

APAR = SA62202
  Host print causes incorrect output on a TELNET session. There
  are some characters missing from the resulting spoolfile. We
  received the following messages.
  MSGCPD4008 f/QWPOERRS x/00bd T/QWSPRINT x/0385
  MSGMCH0601 f/00214F000000 x/4698 t/QWSPRINT
             Space offset X'FFFFE5E6' is outside current limit for
             object WS FM RB - 0000000C.

APAR = SA62957
  When designing drop down screens with SDA, the first menu options
  should be barfly 1, the second group of menu options should be
  barfly 2, etc. But with PC5250, the barfly is not correct if the
  space bar is used, versus the enter key. Therefore, the option is
  not executed. This happens on both Windows 3.1 and Windows 95.

APAR = SA62972
  5250 print, SCS mode, is improved as follows: 1) the host
  CPI(FGID) will be used as the CORing base instead of the
  default of 10 CPI, 2) if the page fits by changing to Landscape
  without changing the CPI, the host supplied CPI is used.
  The above is done when the butoPageOrientation mode is on,
  and the host does not explicitly set the orientation. No data
  is lost or truncated, and the data is made to better fit the paper.

APAR = SA60551
  OV/400 documents printed through a PC5250 printer session (in CA/400
  for Windows 95) are printing the first page only.  This occurs with
  multiple page documents and multiple letter documents (ie, documents
  that use OV/400's Data/Text Merge function to print a letter for each
  record in the database). NOTE: This only seems to occur if the OV/400
  document is setup in one of the following ways:
         1) The document uses a different paper source for the
            first page than it does for the following pages
            (for example, the first page comes from drawer 1
            for letterhead and the following pages come drawer
            2 for regular paper).
         2) There is a page format on a following page that
            specifies different page formatting settings (eg,
            paper source or page rotation) than are specified
            for the first page.

APAR = SA59479
  PC5250 printer sessions under CA/Win95 (CA400WINOPT) are
  printing a blank page before every AS/400 generated spooled file
  when configured to use Host Print Transform. Virtual Print or
  Network Print generated spooled files (ie, *USERASCII spooled files)
  are not preceded by a blank page.

  This is similar to APAR SA56374 (which has been fixed in PTF SF33616),
  but that APAR addresses blank pages printing when using PC5250 with
  only the Windows printer driver. In other words, the printer session
  profile is not setup for Host Print Transform or a Printer Definition
  Table.

APAR = SA58860
  Pressing the backspace key in PC5250 session when the cursor is
  in a protected field, like on an OS/400 menu, may cause the
  session to hang or disconnect.

APAR = SA63192
  When running an application from the AS/400 that requires an
  FTP connection to another system, the following error occurs.

  PCSCM caused an Invalid Page Fault in
  Module PCSTLNET.DLL at 0137:00d03a64

APAR = SA63095
  Customer selects a specific value for the host CPI and font
  from the Printer Control (Text) panel of a printer emulation
  session.  These settings do not seem to have any effect.

  The values for CPI, LPI, Font, MPL, and MPP are overridden
  by the OS/400 print file.  These fields will be grayed out
  on the panel so as not to give the user the feeling that
  the values are actually being used.

Data Transfer
-------------
APAR = SA58487
  Data Transfer from AS/400 under Client Access for Windows 95.
  When selecting to "Return records with missing fields" on a
  Join, resulting data does not contain records with missing
  fields. It contains only those joined records that meet the
  Join condition (as if user never selected "Return records
  with missing fields")

  The problem has been fixed for joins of two files when the
  Return records with missing fields option is selected.
  This type of join is referred to as an outer join.  The
  problem of outer joins of three or more files is not
  addressed by this PTF.

  All inner joins (joins without Return records with missing
  fields checked) continue to work.

APAR = SA63379
  Using RTOPCB or RFROMPCB on Hebrew CA400WINOPT. Hebrew messages
  are displayed in the ANSI code page instead of the correct
  ASCII code page. This also happens for other languages.

APAR = SA64343
  Customer is working with CAWIN95/NT R312. Decimal separator
  is ignored when transferring a file from the AS/400 to the PC.
  If the transfer request is saved to a file, the decimal
  separator is not ignored. This should work without having to
  save the transfer request.

APAR = SA64465
  There is a problem with Data Transfer uploading data
  when double-byte characters are involved.           
                                                    
  The first record transfers correctly (characters are
  converted from ANSI to EBCDIC) but the second       
  record and later records are sent to the AS/400 in  
  ANSI (not converted to EBCDIC).                     

APAR = SA63168
  Client Access data transfer hangs when attempting to transfer a
  null (empty) file.                                             

Graphical Access
----------------
APAR = SA64475
  Provides the following fixes and improvements to Graphical
  Access as follows:
    - Adjust positioning of Help text for a command in the command
      line so the section headings are not cut off on the left.
    - Improved performance over SNA APPC connections.

Printer Drivers
---------------
 None

SNA Communications Support
---------------------------
APAR = SA64448
  When configuring an Anynet connection through the NS/Administrator,
  if the IP address that is entered has leading zeros in any of the
  parts of the address, the router will fail to connect.

APAR = SA64449
  Trying to allocate conversations to too many configured machines
  at the same time causes the NS/Router to hang.

APAR = SA64450
  When using the NetSoft Configuration Wizard to build a twinax
  connection, the event log shows a TWINAX-3 RC=5 error.

APAR = SA64451
  You are not allowed to enter a comma to pause the modem dialing
  with a SDLC connection.

APAR = SA63308
  Client Access Windows 95 32-bit Twinax support is English only.

  Client Access Windows 95 32-bit Twinax installation program and
  readme documentation will be provided in the following
  languages: English, French, German, Italian and Spanish.

APAR = SA59667
  Windows 95 hangs on shutdown after running a PC5250 emulation
  session over Netsoft.

APAR = SA63494
  When attempting to connect with the Win95 VXD twinax - you will
  intermittently get Open Twinax station failed, rc=000000FD.
  Repeated attempts may connect.  This is happening with pcmcia,
  pci and isa twinax cards.

  A timer in the MAC driver (PDLWATWV.VXD) was found to be
  incorrectly set. This has been corrected. The new version of
  the MAC driver is (01.064).

APAR = SA61980
  When customer closes his last PC/5250 session, system will
  return message:  PCSWS caused an invalid page fault in
  module KERNEL32.DLL at 0137:bff9a28c.
  This PC/5250 icon was created from the "Start or Configure
  Session" icon in the CA/400 Accessories folder.

Operations Navigator
--------------------
 None

Toolkit
-------
 None.


 ---------------------------------
   Service Pack Level = SF39669
      Build date = April 1997
 ---------------------------------

 Base Support
 ------------
APAR = SA62521
 ODBC application program issues an ODBC Connect call, supplying
 an AS/400 userID/password on the connect. This userID becomes
 the current user for the connection to the AS/400, and in the
 case of Windows 95, the password is cached into the Windows 95
 password cache (if caching of AS/400 passwords is currently
 enabled).

APAR = SA61653 (Network Drives)
 Microsoft Windows 95 OEM Service Release 2 (OSR2) is an OEM
 Service Release of Windows 95.  Currently, there is no retail
 version of Windows 95 OSR2 available.  It is available from
 some PC Manufacturers who preload it on the new PCs they
 sell to the public.

 An OSR2 Version of Windows 95 can be identified by checking
 the properties of "My Computer" for "4.00.950 B" or checking
 for the version "4.00.1111" at a MS-DOS prompt.

 OSR2 may have the Universal Serial Bus (USB) Supplement
 installed.  This can be verified by selecting
 "Add/Remove Programs" in the Control Panel and checking
 if "USB Supplement to OSR2" is displayed.

 Problems have been found with Network Drives on OSR2 and
 OSR2 with USB, pertaining to some applications that use the
 Windows ResumeThread() and SuspendThread() functions.
 Also, Network Drives fails to run on OSR2 with the USB
 Supplement installed.  The message "CWBNW6101 - Unable
 to start Network Drives" is displayed.

APAR = SA62048 (Install)
 Silent Install BootOption=3 statement in the response file
 doesn't cause the PC to be rebooted.  This is only the response
 file for the service pack silent install.

APAR = SA62530 (Install)
 Customer is experiencing the same problem as reported in APAR
 SA54223 but at R311 release of Client Access/400 For Windows 95.

 If CA400WINOPT is installed on the PC and the Primary Logon for
 Windows 95 is set to "MS Client For Netware Networks", the PC
 will hang when the user attempts to logon while the PC is not
 attached to the LAN.

 If user Cancels the logon the PC does not hang, and if the Win95
 Primary Logon is set to "Windows Logon" the user can login
 without causing a hang condition.

 No AS/400 network resources have been defined in Win95 (no drive
 or printer is mapped to reconnect at logon) and CHECKVER is not
 in Startup either.

 Problem remains whether CA400WINOPT is at SP level NONE or with
 SF36801 applied.

APAR = SA62981 (Install)
Two accessories icons and two service icons appear when upgrading
from M1 to M2 when installing the product in a language
other than English. Both M1 and M2 have to be in the same
language.
For each case, one icon will be a folder and the other one
will be a shortcut to the folder.  The shortcut icons should not
be left there.  The shortcut Accessories and Service
icons do not work.

APAR = SA62518
When running under Windows NT the ODBC driver is not always
detecting the Microsoft Query application as a caller.
Because of this a workaround for a bug in MS Query is not
getting activated and the application does not work.

APAR = SA62522
Passing a value of NULL for the pcbValue parameter on the
SQLBindParameter API can cause an incorrect conversion of
DBCS character data by the ODBC driver.

The resulting string sent to the AS/400 can contain mismatched
SO/SI characters.

AFP WorkBench Viewer
-------------------
 None

5250 Display and Printer Emulator
---------------------------------
APAR = SA62973
 The PC5250 emulator packaged with CA/400 for Win95/NT will
 not run over Netsoft's standalone router or Portfolio
 Enterprise products.
APAR = SA60677
 The user does a setup of a Panasonic 2624 using Win95 PC5250
 session and gets a PCSWS error, which indicates this program has
 performed an illegal operation and will be shut down.  The
 details state PCSWS caused a stack fault in module KERNEL32.DLL
 at 0137:BFF783DF.  This happened when selecting file then print
 control then text then hitting enter.

APAR = SA58210
 Using PC5250 CA400WINOPT or CAWIN, pasting text from the
 clipboard into a blank officevision document will only paste
 the first line from the clipboard. For example, if copying 4
 lines of text with 70 characters on each line, only the first
 line of text will be pasted into the officevision document.
 The paste function does not insert new lines to make room for
 the additional text. It stops at the end of document character.

APAR = SA61263
 DDS Keyword WDWTITLE *BOTTOM doesn't run using CA400WINOPT
 PC5250.

APAR = SA59637
 MSGERR100 with error description 'Error allocating <several
 hundred megabyte up to several gigabyte number here> of memory
 from the Windows global memory heap.'  A Retry or Cancel will
 result in output printing.  The problem happens with
 dotmatrix printers setup with PC5250 CA400WINOPT product.
 The message breaks just prior to output printing.

APAR = SA61174
 MSGERR100 with error description 'Error allocating <several
 hundred megabyte up to several gigabyte number here> of memory
 from the Windows global memory heap.'  A Retry or Cancel will
 result in output printing.  The problem happens with
 dotmatrix printers setup with PC5250 CA400WINOPT product.
 The message breaks just prior to output printing.

APAR = SA59466
 With EAB and NOXLATE session parameters set, the PC5250 EHLLAPI
 Copy Field to String (34) API will return incorrect field
 attributes.  It appears to always return zero, even for
 underlined and reverse image fields.

APAR = SA60676
 When performing local screen prints from a Win95
 PC5250 display emulation screen, the PC will run
 out of system resources and eventually lock up the
 PC.

Data Transfer
-------------

APAR = SA62545 (NLS)
 Data transfer function in CA/400 for Windows 95 does not
 handle DBCS Graphic field 4396 to 932 conversion.

APAR = SA61870
 Data Transfer will hang when the WHERE or JOIN BY clauses have
 T1/T2 types of file name delimiters, and the file name contains
 a T with numeric values,

APAR = SA61708
 When sending PC data from a DBCS PC to a physical file with
 all of its fields of O-type (DBCS), there is no problem.
 But if sending data to the physical file that one of its
 fields is A-type (SBCS), an error occurs, for example:

 CWBDB0036 - Server Returned SQL error
 SQL0332   - Character conversion between CCSID 949 and CCSID 883
             not valid.

 949 is the ASCII mixed CCSID for Korean.
 833 is the EBCDIC SBCS CCSID for Korean.

 Error SQL0332 is displayed in the joblog of on the AS/400.

APAR = SA62518
 Unique national language characters are not being displayed
 correctly in error messages displayed by Data Transfer.

APAR = SA62979
 The first blank in a field that is entirely blank if not being
 removed.
 Therefore, the ASCII text file might look like this:

 ABCD<crlf>
  <crlf>
 EFGHI<crlf>

 Instead of

 ABCD<crlf>
 <crlf>
 EFGHI<crlf>

APAR = SA58432
 Data Transfer in the Client Access for Windows 95 product is
 much slower than the File Transfer program in the Client
 Access for Windows 3.x product.

APAR = SA62124
Old *.TTO Files, which are created with
the DOS Clients, don't work with rfrompcb
and cwbtf. The datatransfer ends with
errormessages, e.g.: MSGCWBDB0099.

APAR = SA62508

 After making changes to a Rumba Transfer Request (.RTO), Data
 Transfer does not correctly save the use FDF option to the RTO
 file.  This only occurs when modifying the use FDF option for
 transfers from the PC to the AS/400.


Graphical Access
----------------
APAR = SA62980
 Provides the following fixes and improvements to Graphical
 Access as follows:

   - Display Spooled File improved so it maintains the
       horizontal scroll position during forward and
       backward scrolling.

   - Support system names of longer than 8 characters for
       SNA connection.

   - Correct operation of Field Minus key on Numeric-Only
       fields.

   - Remove partial instruction line from list box for
       Display Open Files.

   - On resizing graphical window from the bottom,
       move up bottom push buttons so they remain operational.

   - Correct instruction line in InfoSeeker screen that
       displays content of a book.

   - Correct character presented for CCSID 1112 (Latvia,
       Lithuania) for special character code points 4A, 70,
       80, DF, and EA.

   - Correct character presented for CCSID 1122 (Estonia)
       for special character code points 70, 80, B0, EA.



Printer Drivers
---------------
 None


SNA Communications Support
---------------------------
APAR = SA61298
 RUNRMTCMD fails with error MSGCPD3B54 with sense code of 082D.
 If the user varies off the CTL and back on it will work, but if
 the user disconnects they will have to vary the CTL back off and
 on to get it to work again.

APAR = SA62976
 Customer has a CPIC and an ODBC application.
  1) Start CPIC application
  2) Start another application (ODBC application)
    - ODBC application fails to start

 Reverse is also true.  If the ODBC application is started first,
 the CPIC application fails.

APAR = SA62977
 While running a CPIC application, we would from time to time
 get a PRODUCT_SPECIFIC_ERROR, when trying to set side info.
 Then the connection will drop.

APAR = SA62978
 Running CA/400 on WinNT, using SNA over Ethernet.
 When we are in NS/Router's Midrange Workspace and attempt
 to connect to the system, the userid/password box appears and
 the default userid in the box is the current user (in our case,
 Administrator). Take note that the maximum length for a userid
 on the AS/400 is 10, 'Administrator' is 13. If we change the
 id, we can only enter ten characters. If we don't, and just hit
 enter, we get the following error:

 Dr. Watson: application error in engappc.exe
 Exception: Access violation (0xc0000005),
 Address: 0x0040375d


Operations Navigator
--------------------
 None

Toolkit
-------
 None.



 ---------------------------------
   Service Pack Level = SF39220
      Build date = March 1997
 ---------------------------------

 Base Support
 ------------
APAR = SA61992 (Network Drives)
 Client Access Optimized for Windows 95/NT network drives may
 create a reference to a folder or subdirectory such
 that it cannot be deleted later.  The user will receive
 the following error messages:
 DOS PROMPT:  Sharing violation reading drive X:
 Explorer:    Cannot remove folder xxxx: There has been a
              sharing violation.  The source or destination
              folder may be in use.
 This error only effects QDLS and QSYS.LIB file systems.
 The problem is with how network drives handle the working
 directory handle (WDH) cache.  If a folder or object in
 folder is referenced, netdrives may create a WDH to that
 folder.  This WDH will "lock" the folder if the folder
 exists in a "persistent content" file system such
 as QDLS or QSYS.LIB.  Network drives is only deleting the
 WDH when the drive is disconnected.  The WDH should be
 deleted before attempting the delete folder operation.

APAR = SA62199
 The following errors happen on Windows NT when using Lotus
 SmartSuite applications.

 When saving a Lotus 1-2-3 or a Freelance Graphics file to a
 directory on the AS/400 for the first time, it says that
 the file already exists.

 When creating a new Lotus Approach file to an AS/400 a damaged
 file error occurs.

APAR = SA62207
 While copying large files or a large number of files using
 network drives on Windows NT, a message box with the following
 message will be displayed:

 System Process - Lost Delayed-Write Data

 The system was attempting to transfer the file from buffers
 to <system file name>. The write operation failed, and only
 some of the data may have been transferred to the file.

APAR = SA61843 (Install)
 After a Client Access for Windows 95/NT service pack is
 installed by using Client Access Login Service Check or
 Check Service Pack Level or Install Service Pack, the
 Check Version task does not end.

 Even though the service pack setup.exe install has
 completed, the Check Version task still is present
 on the task bar.

APAR = SA61877 (Install)
 The following problem occurred while installing
 V3R1M2 Client Access for Windows 95/NT Service Pack
 SF37523 from diskettes:

 After inserting Diskette 7, the customer is prompted
 to re-insert Diskette 2 for AS/400 Operations Navigator
 fix files.

APAR = SA62190 (Install)
 After an upgrade from V3R1M0 or V3R1M1 Client Access
 for Windows 95 to V3R1M2 Client Access for Windows 95/NT,
 the following files are missing from the
 AFP Workbench Viewer component:

 ...\ClientAccess\AFPViewr\Font
  cpdef.cht
  cpdef.jpn
  cpdef.kor
  csdef.cht
  csdef.jpn
  csdef.kor
  icoded.cht
  icoded.jpn
  icoded.kor

 ...\ClientAccess\AFPViewr\Font\Maps
  833.cp

APAR = SA62195 (CWBBACK Windows  NT)
 Running CWBBACK on Windows NT 4.0 without administrator
 authority causes error message CWBCF0005 but the backup
 continues to run.  When CWBBACK is finished it displays
 a message indicating backup was successfull.  If this
 backup is later restored it will corrupt the registry.
 CWBBACK does work if the user signed on has administrator
 authority, but if CWBREST.EXE is then performed to restore
 the configuration on an account that does not have
 administrator authority, CWBREST fails, leaving the
 Client Access configuration in a corrupted or
 unpredictable state.



AFP WorkBench Viewer
-------------------

5250 Display and Printer Emulator
---------------------------------
 None

Data Transfer
-------------
 None

Graphical Access
----------------
 None

Printer Drivers
---------------

APAR = SA62208
 Margin values set from an application are either ignored or
 incorrect when printed.

APAR = SA62194
 The SCS printer driver will not print on a user defined form.

APAR = SA62191
 A user defined form created in the Manage Forms dialog is not
 saved if the SCS printer driver document properties are accessed
 from within an application.  The user can create a new form and
 use it in the current session but the form will not be saved
 after the user interface is closed.

APAR = SA62192
 Setting the EBCDIC Code Page value in the SCS Driver document
 properties sometimes doesn't work.  No error messages are
 displayed.  When it does work, printing to the AS/400 may fail
 because the code page specified in the spooled file is
 incorrect.



SNA Communications Support
---------------------------
   APAR = SA60677
    Adds Windows 95 32-bit twinax support.
    This support can be used with the following Twinax adapters:
    - The Enhanced 5250 Display Station Emulation Adapter
      (Feature Code 2911   Part/Number 30F5383)
    - The 5250 Emulation Adapter/A
      (Feature Code 3494   Part/Number 64G3494)
    - The IBM System 36/38 Workstation Emulation Adapter/A
      (Feature Code 6279   Part/Number 69X6279)
    - The 5250 Emulation PCMCIA Adapter
      (Feature Code 2808   Part/Number 92G5360)
    - The IBM 5250 Emulation PCI Adapter
      (Feature Code 0207   Part/Number 88H0207)

Operations Navigator
--------------------
APAR = SA62189
 This fix is required if you will be using groups under AS/400
 Operations Navigator.

Toolkit
-------
 None.

-------------------------------------
   Service Pack Level = SF37533
      Build date = February 1997
-------------------------------------

 Base Support
 ------------
APAR = SA61407
 Additional information about the problems described in this
 APAR can be found in INFO APAR II10147.

 This APAR makes Windows NT registry changes for
 the following problems:
 1) "CWBNACFS.DLL cannot run." Message Box
 2)Slow logon, or CTRL+ALT+DEL to get to the desktop
 3) Only printers displayed in Network Neighborhood
 4) Can't assign network drive
 5) Netware logon scripts fail to run after installing
    Client Access for Windows 95/NT

1) "CWBNACFS.DLL cannot run." Message Box
------------------------------------------
 Right clicking on an icon on the desktop results in a
 message box displaying the following error message:
 "CWBNACFS.DLL cannot run. Unable to get handle to
 CwbRdr".

2) Slow logon, or CTRL+ALT+DEL to get to desktop
-------------------------------------------------
 After installing Client Access for Windows 95/NT,
 logging onto Windows NT takes 2-3 minutes, or you
 have to press CTRL+ALT+DEL to get to the desktop.

3) Only printers displayed in Network Neighborhood
---------------------------------------------------
 Only AS/400 printers are displayed in Network
 Neighborhood after clicking on a configured AS/400


4) Can't assign network drive
------------------------------
 Customer cannot assign network drive to an AS/400
 using Network Neighborhood or Explorer.

5) Netware logon scripts fail to run after installing
    Client Access for Windows 95/NT
------------------------------------------------------
 After installing Client Access for Windows 95/NT, the
 Novell Netware server logon scripts do not run on
 client PC while logging into Windows NT.

APAR = SA61404
 When using an OEM TCP/IP stack on Windows 95,
 uploading a relatively large chunk of data, such as during
 a copy of a large file to a network drive, causes Client
 Access to hang.

APAR = SA61415 (ODBC)
 Attempting to specify a translation DLL will result in an error
 message.  (Driver unable to load translate DLL.)

APAR = SA61416 (ODBC)
 Trying to execute a parenthesized SELECT statement results in an
 error.

APAR = SA59977 (ODBC)
 An access violation was caused by the ODBC driver when
 an application attempted to set a parameter marker to
 SQL_NULL_DATA.  The problem only occurs when using
 the SQL_LEN_DATA_AT_EXEC macro.  When SQL_NULL_DATA is
 specified on the SQLPutData, an access violation is raised
 when the statement is executed (the last SQLParamData).

APAR = SA60455 (ODBC)
 The ODBC driver has a memory leak when an application executes
 a stored procedure that returns a result set.  This happens
 using either the SQLExecDirect API or the SQLPrepare and
 SQLExecute APIs.
 A block of memory will be lost each time the procedure is
 executed.  After many iterations of this sequence the program
 can get a memory or resource allocation error.

APAR = SA60752 (ODBC)
 'Driver Not Capable' error returned for call to
 SQLExtendedFetch for SQL_FETCH_FIRST under certain conditions.

APAR = SA60452 (RMTCMD)
 When using RMTCMD.EXE some international characters such
 as the german umlaut are not getting converted properly.

APAR = SA59340
 Multithreaded applications running under Windows 95 may
 hang or fail when run with a Client Access network drive
 assigned.  Only applications that use SuspendThread() and
 ResumeThread() are affected.  Applications that use other
 Windows 95 synchronization objects (events, for example)
 will work when a network drive is assigned.

 Powersoft Optima++ is an example of an application that
 fails.

 The error occurs when one thread suspends itself and another
 thread attempts to resume it with a ResumeThread() call.
 If a Client Access network drive connection has been
 established since the last boot of Windows 95, the
 ResumeThread() api call will fail.  GetLastError() returns
 return code 0x78 (120).  This is defined as:

   ERROR_CALL_NOT_IMPLEMENTED  "This function is only valid in
                                Windows NT mode" (winerror.h)

 "This function is only valid in Win32 mode" is returned
 by FormatMessage().

 The error does not occur if a network drive has not
 been connected since the last boot of Windows 95.

AFP WorkBench Viewer
-------------------
 None

5250 Display and Printer Emulator
---------------------------------
APAR = SA61421
Using PC5250 in CA/400 for Windows NT on a Latin-2 version for
NT, national characters cannot be typed in.

Data Transfer
-------------

APAR = SA60791
When performing a data transfer from the PC to the AS400, hex
value 09 will not be correctly translated to hex 05.  Rather,
the 09 will be translated to a hex 40.

APAR = SA60892
Client Access/400 for Windows 95 data transfer function
preserves trailing blanks when downloading data to an ASCII
test file.  This is inconsistent with the behavior of
previous Client Access file transfer functions. This is
inconsistent with Client Access documentation.
File transfer function of previous clients would drop
trailing blanks.  Equivalent functionality should be added to
Client Access/400 for Windows 95.

APAR = SA61002
CAWINOPT Data Transfer from AS400. Data Options -> Details...
gets you to Receive Request Details.  On Select page, you
double-click the fields you want to select and they are
dynamically added to the Select Clause below. Once that
clause is a certain length (approximately 260 characters),
any further selections in this manner truncate that string
in order to fit the new selection.
Manually typing in the field names does not pose this
problem (in neither the Select Clause nor the Select: on the
previous panel).  However, with a typed-in 260+-length
clause, any further addition made to it via the method above
will truncate the clause down to the approx. 260 length.
This problem also occurs for the Order By clause on the same
Receive Request Details panel.

APAR = SA60648
The BIFF files transferred by Data Transfer do not contain the
correct font information.  When DBCS data exists in the file,
it is not displayable because the font specified is Arial and
the Arial font does not contain DBCS characters.

Graphical Access
----------------
APAR = SA61420
Provides the following fixes and improvements to Graphical
Access as follows:

  o  In Traditional Chinese, Work With Panels are now properly
       shown graphically after having prompted for a command.

  o  In Traditional Chinese, command prompting pushbuttons
       for individual parameters are now properly generated.

  o  In Korean, menu options beginning with a "1"
       are now properly formatted.

  o  In Hebrew, bitmaps are now properly positioned on
       pushbuttons.

  o  Required fields are shown with a green background rather
       than blue, to be consistent with early versions.

  o  WRKQRY is correctly presented graphically. One screen
       was presented nongraphically and one had text in
       the position to field.

  o  In Japanese, Display Spooled File now has a correct
       data ruler.

  o  In Japanese, Work with Spooled Files, a partial row of
       characters at the bottom of the scrollable area
       has been removed.

  o  On the Programmer Menu, extra text characters to the
       right of menu options have been removed.

  o  The View Topics choice under the Functions pull-down
       of Help screens, now properly supports deselecting
       and reselecting topics.

  o  DBCS code points for hexadecimal "68nn" were changed
       to match IBM standards.

  o  In DBCS language help, the words representing hypertext
       links were changed to green to distinguish them
       from headings.

  o  Operation of DUP and Field Exit keys corrected.

OfficeVision
-------------
  o  Removed the generation of additional blank lines in
       the editor during typing of continuous wrapping text.

  o  Corrected handling of numeric field editing.


Printer Drivers
---------------

APAR = SA61400

Using the AFP printer driver version 5.00 for Windows NT, if
the customer prints a document that contains a blank page,
the following page in the document will always print out
completely black.

APAR = SA61401
When using the IBM AFP Printer driver version 5.00 for Windows
NT, print options changed from certain applications do not get
saved.  Every time the print options are opened the settings are
set back to the defaults for the printer.

APAR = SA61402
Printing with the AFP printer driver version 5.00 for windows
NT, the inlined form definition dialog doesn't allow the
user to select Envelope Feed as a source drawer.

APAR = SA61403
When printing with the AFP printer driver version 5.01 for
Windows NT, output types of overlay, medium overlay , or
page segment do not produce any output.


APAR = SA60407
Windows applications which attempt to print to a printer which
is using the IBMSCS printer driver on Windows NT, receive an
error message when attempting to print.

SNA Communications Support
--------------------------

APAR = SA61212
Incoming Remote command (IRC) does not work with a Netsoft 802.2
connection.

APAR = SA61216
When discounting and reconnecting to a different system the
screen will turn blue and the system will lock up.  Must reboot
to get the system up and running again.

APAR = SA61214
The XCSCST, XCSCSP, and XCSCSV CPIC commands do not work.

APAR = SA57948
 Customer is running CA400WINOPT with Async connection and
 Netsoft Router, his PC5250 Emulation session Drops after
 he issues the following commands "CALL QUSCMDLN or STRSST"
 There are no error messages on the pc or on the AS/400.

Operations Navigator
--------------------

APAR = SA61399
The AS/400 Operations Navigator's Permissions function
does not work from a double-byte PC running with
English or its native DBCS language.

APAR = SA61408
In the Operations Navigator application, the View pulldown on
the main menu contains an item called "Arrange Icons".  This
option cascades into two additional items, "By Name" and
"By Description".

The problem is there is currently no support for "By Name" and
"By Description".  The items are always grayed out.  This causes
confusion for end users.  This PTR removes the "Arrange Icons"
item and its subitems.

APAR = SA61409
When clicking on the ellipses to show the Sort Sequence table
dialog box for Job Properties, the application fails.

APAR = SA61410
Selecting "Properties" for a batch job from the pop-up menu brings
up the following error message:

Title: Cwbunnav
Program has performed an illegal operation and it will
be ended.

APAR = SA61411
In the Operation Navigator's window, all DBCS characters
in grey areas above list windows are displayed incorrectly.

APAR = SA61412
Message CPA1318 was displayed correctly but it
has invalid characters at the end of the message.

APAR = SA61413
Click on an individual printer icon on the left (tree) view.
After the printer output for that printer appears in the right (list)
view, select the printer icon in the left view and select to
change properties.  After pressing OK on the properties
dialog, the program fails.

APAR = SA61414
With a fully qualified AS/400 system name the following error occurs:
Select Users and Groups -> All Users ->  right mouse click
on a user, select user objects.
Click on any one of the options: Output, Jobs, Messages
Nothing happens, although the user has jobs, output, and
messages available.

APAR = SA61417
Some data, in DBCS environments, are truncated and some dialogs
to be to large.

APAR = SA61418
When a double-byte version of Windows is being used the context
menu for ODBC Data Source objects in the AS/400 Operations Navigator
application does not come up, and the File menu shows only "Exit".

APAR = SA61419
When using the "User" objects within Operations Navigator,
clicking on a user profile in list view and selecting "Message",
causes error message "Cannot get AS/400 DATA" to be displayed.

APAR = SA61422
Fixes Library,Table,View Permissions and Library Properties
for quoted alternative names with special chars. that are less
than 10 characters and quoted lowercase Library names and quoted
names in which the short name is less than 10 characters.

APAR = SA61423
The data that is displayed in list boxes in various Operations
Navigator dialog boxes (for example, Hold Printer Output)
does not always fit within the list box.

APAR = SA61405
An invalid creation date on AS/400 Operations Navigator's File
Systems property pages for File Systems is displayed.

Also fixes the problem where end-users can try to change the
Attributes on File Systems.

 Toolkit
 -------
   None.
