===================================================================

Readme File for iSeries Access for Windows

Version 5 Release 4 Modification Level 0
(c) Copyright IBM Corporation 1996, 2005. All rights reserved.
===================================================================
This document is provided "as is" without warranty of any kind.
IBM disclaims all warranties, whether expressed or implied,
including without limitation, the implied warranties of fitness
for a particular purpose and merchantability with respect to the
information in this document. By furnishing this document, IBM
grants no licenses to any patents or copyrights.
-------------------------------------------------------------------
IMPORTANT: Be sure to review the Information Authorized Problem
Analysis Reports (APARs) for the iSeries Access for Windows
client. Information APARs contain documentation on available
program temporary fixes (PTFs) and service packs, configuration
tips, known problems, support statements and more. An archive of
iSeries Access for Windows Information APARs is available from
the Web site (www.ibm.com/eserver/iseries/access/casp.htm). See
the addendum (www.ibm.com/eserver/iseries/access/v5r4.html) to
this Readme File for information that was not available at the
time of publication.
If your PC has an Internet browser installed and configured, an
Internet browser icon (called Internet Information) is created
in the iSeries Access for Windows program folder. This icon
opens your Internet browser and allows you to link to all the
latest iSeries Access for Windows information, including the
iSeries Access home page.
-------------------------------------------------------------------
TABLE OF CONTENTS
-------------------------------------------------------------------
1.0 SUPPORT LEVEL INFORMATION
1.1 V5R4M0 installation and support
1.2 Personal Communications 5250 Emulation and PC5250
1.2.1 Migrated PC5250 support files
1.3 .NET Framework
1.3.1 IBM.Data.DB2.iSeries .NET Data Provider requirements
1.3.2 PC5250 requirements
1.4 Microsoft XML Parser or Microsoft XML Core Services
1.5 iSeries Access and firewalls
2.0 RESTRICTIONS
2.1 Microsoft provided fixes
2.2 Directories for iSeries Access files
3.0 INSTALLATION NOTES AND KNOWN PROBLEMS
3.1 Action required for installing printer drivers
3.2 Files uninstalled during upgrade
3.3 Programmer's Toolkit APIs that require recompile
3.4 Memory requirements
3.5 Information not available at time of publication
-------------------------------------------------------------------
-------------------------------------------------------------------
-------------------------------------------------------------------
1.0 SUPPORT LEVEL INFORMATION
-------------------------------------------------------------------

1.1 V5R4M0 installation and support

-------------------------------------------------------------------
- Support for upgrading iSeries Access for Windows to V5R4M0 is
provided only when it is installed over V5R3M0 and V5R2M0.
Unpredictable results can occur when installed over earlier
releases.
- iSeries Access for Windows V5R4M0 does not install on
Microsoft Windows 95, Windows 98, Windows ME, or Windows NT.
- Migration is not supported from Client Access for Windows/NT
(5763-XD1) to iSeries Access for Windows V5R4M0.
From 5763-XD1, there are 2 options to move to V5R4M0:
1) Uninstall Client Access for Windows/NT (5763-XD1) and
then install iSeries Access for Windows V5R4M0.
2) Migrate from Client Access for Windows/NT (5736-XD1) to
iSeries Access for Windows V5R2M0 and then upgrade
to iSeries Access for Windows V5R4M0. Settings are
retained when you use this option.
- Refer to www.ibm.com/eserver/iseries/access/supportedos.htm
for detailed information on the various Microsoft Windows
operating systems and the iSeries Access for Windows version
and service level required for each operating system. V5R4M0
supports install onto Microsoft Windows XP, Windows 2000 and
various versions of the Windows Server 2003 family. To upgrade
your PC to one of the supported Windows operating systems, you
will need to use the following steps:
1. Uninstall iSeries Access for Windows
2. Upgrade the Windows operating system
3. Install iSeries Access for Windows

1.2 Personal Communications 5250 Emulation and PC5250

-------------------------------------------------------------------
PC5250 is the display and printer emulation component that
installs (selectively) as part the of iSeries Access for Windows
product. You cannot install PC5250 on the same personal computer
as Personal Communications version 4.1, and later releases,
because these versions of the Personal Communications product
also provide a 5250 emulation component. Regardless of the order
in which you install these two products, whenever you install
iSeries Access for Windows (with or without its PC5250 component)
the iSeries Access for Windows folder is automatically populated
with the PC5250 icons. When you do not install the PC5250
component and also install Personal Communications 4.1 (and
later versions), these PC5250 icons point back to the
Personal Communications 5250 emulator.
Note: Personal Communications version 5.6 and later versions,
allow you to launch the Personal Communications 5250 emulator
from iSeries Access for Windows while earlier versions do not.
 Warning!
It is strongly recommended that Personal Communications 5.5
not be installed on the same personal computer as
iSeries Access for Windows or vice versa, unless a
Personal Communications 5.5 CSD1 or above is installed. The
install code in Personal Communications 5.5 without any CSD,
does not properly check for the existence of the
iSeries Access for Windows PC5250 component. This can lead
to Personal Communications 5.5 install code replacing PC5250
modules in the iSeries Access for Windows Emulator directory.
If this is later followed by an uninstall of
Personal Communications 5.5, the majority of PC5250 runtime
modules are removed and attempting to launch 5250 sessions
from iSeries Access for Windows will lead to unpredictable
results. If you are currently in the above situation, you
should remove both products and then reinstall only one.

1.2.1 Migrated PC5250 support files

-------------------------------------------------------------------
The version of PC5250 that is included in
iSeries Access for Windows requires that certain supporting files
(such as .ws files) are migrated to a new version level.
This migration happens automatically at first touch of the
individual files, unless certain steps are taken to prevent it.
Migrating files can result in users with earlier versions of
PC5250 (which are in earlier versions of iSeries Access for Windows)
not being able to use the migrated files. This can happen, for
example, if multiple users use the same files from a shared
location. Not migrating a file can result in that file being
unusable to PC5250.
Use one of the following paths to control the migration of
supporting files:
1) iSeries Access for Windows Properties > PC5250
2) Application Administration > Central Settings >
Client Applications > Advanced Settings > PC5250
Note: When files are automatically migrated, the original file is
saved with a slightly modified extension (for example, abc.ws
is saved as abc.ows).

1.3 .NET Framework

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

1.3.1 IBM.Data.DB2.iSeries .NET Data Provider requirements

-------------------------------------------------------------------
iSeries Access for Windows .NET Data Provider
(IBM.Data.DB2.iSeries) requires Microsoft's .NET Framework to be
installed on your system. The .NET Framework can be downloaded
from the following Microsoft Web site:
http://www.microsoft.com/net
 Also visit www.ibm.com/eserver/iseries/access/v5r4.html
for additional .NET information that was not available at the
time of publication.

1.3.2 PC5250 requirements

-------------------------------------------------------------------
Beginning with V5R4,iSeries Access for Windows PC5250 support
includes a .NET programming interface. The PC5250 .NET support
can be installed if the Microsoft .NET Framework is not installed
but to use the PC5250 .NET support, the framework must be
installed on your personal computer.
The .NET Framework can be downloaded from the following Microsoft
Web site:
http://www.microsoft.com/net

1.4 Microsoft XML Parser or Microsoft XML Core Services

-------------------------------------------------------------------
iSeries Access for Windows V5R4M0 Data Transfer provides support
for transferring XML files to and from Microsoft Excel 2003 and
Microsoft Excel XP. This support requires that the
Microsoft XML Parser 3.0 or above, also known as the
Microsoft XML Core Services, be installed on your personal
computer. To determine if the XML Parser support is installed,
check for the existence of msxml3.dll or msxml4.dll. If neither
is found, you will need to access www.microsoft.com for
instructions on downloading and installing the XML Parser before
you can use the Data Transfer XML support.

1.5 iSeries Access and firewalls

-------------------------------------------------------------------
For information on firewalls, see the Information on iSeries
Access for Windows and Firewalls topic (http://www.ibm.com/
servers/eserver/iseries/access/toolkit/firewallknowbase.htm).
You call also search the IBM website (www.ibm.com) for documents
containing both the keywords "cwbrxd" and "firewall".

2.0 RESTRICTIONS
-------------------------------------------------------------------

2.1 Microsoft provided fixes

-------------------------------------------------------------------
Fixes provided by Microsoft for Microsoft Windows should be
reviewed and downloaded from the Microsoft Web site
(www.microsoft.com). If there are any critical iSeries Access
fixes that must be downloaded, they are listed at the following
Web site:
www.ibm.com/eserver/iseries/access/v5r4.html

2.2 Directories for iSeries Access files

-------------------------------------------------------------------
Members of the Users group are referred to as Restricted Users
 in Windows 2000, or later operating systems, and have limited
permission. In most circumstances, Restricted Users are not
allowed to modify system-wide registry settings, operating system
files, or program files. Because of this, some iSeries Access
user files are saved, by default, in a location that Microsoft
documents as being less restrictive. Examples of such files
include the following:
- history log and trace files
- Saved Data Transfer requests
The less-restrictive path is not the same across all versions of
Windows. Because this path can be changed by your Administrator
at any time, the locations of these files might not always be
the same. For more information, see the "Saving and Finding
iSeries Access for Windows Files" topic in the online Users' Guide.

3.0 INSTALLATION NOTES AND KNOWN PROBLEMS

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

3.1 Action required for installing printer drivers

-------------------------------------------------------------------
When Driver Signing is set to Warn or Block and Windows
encounters a file that has not been digitally signed, the Windows
operating system enforces an interrupt of installation programs
and issues a Windows Logo Testing warning/error message. In some
previous versions of Windows operating systems, you were not
required to take any action because Windows allowed installation
programs to bypass the setting for Driver Signing Options. Now
when performing a Custom Installation, a Full installation, or
an upgrade of iSeries Access for Windows (with the selection of
the AFP or SCS Printer Driver components), you must take action
because the AFP and SCS printer drivers components are not
digitally signed by Microsoft.
If the AFP or SCS Printer Driver components are not needed,
choose a Custom Installation instead of a Full Installation or
a Selective Upgrade instead of a Basic Upgrade and de-select
the AFP and SCS Printer Driver components. Typical and PC5250
User installation types do not include Printer Drivers.
On 32-bit Windows operating systems, do the following to allow
the installation program to automatically add or update the
Printer Driver:
Set Driver Signing Options to Ignore (instead of Warn or Block)
before the installation or upgrade and then reset the option
after the installation or upgrade, using this path:
Start > Settings > Control Panel > System > Hardware
> Driver Signing Options
After an installation or upgrade on a 32-bit Windows operating
system, if Driver Signing was set to Warn or Block, Printer Driver
files have been copied to a subdirectory under the Client Access
installation directory.

On 64-bit Windows operating systems, only the AFP printer driver

is available for installation. Regardless of the Driver Signing
setting, files are copied to a subdirectory under the
 Client Access installation directory. The printer driver is not
automatically added or updated.

On 64-bit and 32-bit operating systems, if the files are

copied to a subdirectory under the Client Access installation
directory, as described above, then you will need to add or update
your Printer Driver using Microsoft's directions in their help
text. As prompted, specify one of the following directory
locations (assuming that you installed to the default destination
path) for your printer driver:
For AFP: c:\Program Files\IBM\Client Access\CWBAFP directory
For SCS: c:\Program Files\IBM\Client Access\CWBSCS directory

3.2 Files uninstalled during upgrade

-------------------------------------------------------------------
The following components are no longer included with
iSeries Access for Windows. If you currently have these
components installed from a previous release of 5722-XE1, they
will be uninstalled during the upgrade:
- Application Development
The Application Development folder within iSeries Navigator
hierarchy is included when the iSeries Navigator Network
component is installed. Use Application Administration to
restrict the display of the Application Development folder
to certain users or groups of users.
- MAPI
- 56-bit Client Encryption

3.3 Programmer's Toolkit APIs that require recompile

-------------------------------------------------------------------
If your application uses the CWBNL_CP_CLIENT_UNICODE constant
with either of the following APIs to convert iSeries Unicode data,
you must recompile, using the V5R3M0, or later,
Programmer's Toolkit to ensure that you get the correct behavior:
cwbNL_CreateConverter
cwbNL_ConvertCodePages
The CWBNL_CP_CLIENT_UNICODE constant is used to indicate
little-endian UTF-16. Prior to V5R3, this constant was defined
as 1200. Starting with V5R3 and later releases, this constant
was changed to 1202, because 1200 is now used to indicate
big-endian UTF-16. For compatibility with applications created
with the pre-V5R3 Programmer's Toolkit,the APIs listed above will
continue to treat 1200 as little-endian UTF-16. Applications
compiled with the V5R3M0, or later, Programmer's Toolkit will
automatically be rerouted to use the following 2 new APIs which
treat 1200 as big-endian UTF-16 and 1202 as little-endian UTF-16:
cwbNL_CreateConverterEx
cwbNL_ConvertCodePagesEx

3.4 Memory requirements

-------------------------------------------------------------------
 iSeries Navigator requires a minimum of 128 MB of memory, however,
256 MB or greater is recommended. Refer to
iSeries Access for Windows - Install and Setup, for a list of
requirements you need to run iSeries Access for Windows on your
PC. You can access this information through the
Information Center using this path:
Connecting to the iSeries > iSeries Access >
iSeries Access for Windows > Install and Setup > Set up the PC

3.5 Information not available at time of publication

-------------------------------------------------------------------
See the addendum to this Readme File for information that was not
available at the time of publication:
www.ibm.com/eserver/iseries/access/v5r4.html

[END OF DOCUMENT]