====================================================================== Readme File for iSeries Access for Windows Version 5 Release 2 Modification Level 0 (c) Copyright IBM

Corporation 1996, 2002. 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 APARs for the iSeries Access for Windows client. Information APARs contain documentation on available PTFs and service packs, configuration tips, known problems, support statements and more. An archive of iSeries Access for Windows Information APARs is available on the iSeries Access web site (www.ibm.com/eserver/iseries/access/casp.htm). See the addendum (www.ibm.com/eserver/iseries/access/v5r2.htm) 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 iSeries Access for Windows V5R2M0 and Microsoft Windows 1.2 Personal Communications Support 1.2.1 Personal Communications 5250 Emulation and PC5250 1.2.2 Personal Communications Screen Customizer 1.2.3 Personal Communications Session Manager 1.3 OLE DB MDAC 1.4 TCP/IP over twinax 1.5 MAPI support 2.0 RESTRICTIONS 2.1 Microsoft Windows fixes 2.2 Directories for iSeries Access files 3.0 INSTALLATION NOTES AND KNOWN PROBLEMS 3.1 Management Central Connectivity Updates 3.2 Memory requirements 3.3 Information not available at time of publication ------------------------------------------------------------------------------------------------------------------------------------------1.0 SUPPORT LEVEL INFORMATION

---------------------------------------------------------------------1.1 iSeries Access for Windows v5r2m0 and Microsoft Windows ---------------------------------------------------------------------For information on various Microsoft Windows operating systems and the iSeries Access for Windows version and service level required for the operating systems, refer to www.ibm.com/eserver/iseries/access/supportedos.htm 1.2 Personal Communications Support ---------------------------------------------------------------------1.2.1 Personal Communications 5250 Emulation and PC5250 If you are using any of the following, which already provide 5250 emulation: Personal Personal Personal Personal Personal Personal Communications Communications Communications Communications Communications Communications version version version version version version 4.1 4.1 4.2 4.3 5.0 5.5 for for for for for for Windows Windows Windows Windows Windows Windows 95 NT 95/NT 95/NT 95/98/NT/2000

you will not be allowed to install the PC5250 display and printer emulation provided with iSeries Access for Windows. If you are using Personal Communications version 5.5 at the CSD1 level or above, you can launch the 5250 emulator of Personal Communications from iSeries Access for Windows. When you install iSeries Access for Windows (without the PC5250 component) and Personal Communications version 5.5 at the CSD1 level or above, (it does not matter which one you install first), a program will automatically run that populates the iSeries Access for Windows folder with PC5250 icons. These icons point back to the Personal Communications 5250 emulator. Warning! It is strongly recommended that Personal Communications 5.5 not be installed on the same box 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 CSDs, does not properly check for the existence of the iSeries Access for Wind ows 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 will be removed and attempting to launch 5250 sessions from iSeries Access for Windows will lead to unexpected results. If you are currently in the above situation, you should remove both products and then reinstall only one. 1.2.2 Personal Communications Screen Customizer ----------------------------------------------------------------------

V5R2M0 iSeries Access for Windows is not compatible with any version of the Personal Communications Screen Customizer product. 1.2.3 Personal Communications Session Manager ---------------------------------------------------------------------Personal Communications version 5.5 supports a new front-end function called Session Manager. With Session Manager, be aware of the following different behaviors from prior releases: - PCOMM no longer prompts (or allows) a user to create an icon when exiting a new session. It relies on Session Manager to dynamically present all the .ws and .bch files, in the current user's personal directory, as icons in a window. - Users are no longer prompted to start existing sessions from icons which launch pcsws.exe without a .ws profile. You may wish to edit the properties of these icons to change the Shortcut Target to invoke pcsfe.exe (Session Manager) instead of pcsws.exe. Without changing this target, users of these icons are only allowed to create new sessions, not start existing ones. - Applications which call pcsws.exe without parameters may not invoke the expected behavior. You may wish to evaluate the expected results of all applications which call pcsws.exe without parameters. The PCOMM Session Manager is shipped with the PC5250 component of V5R2M0 iSeries Access for Windows. 1.3 OLE DB MDAC ---------------------------------------------------------------------iSeries Access for Windows V5R2M0 OLE DB provider (IBMDA400) requires that Microsoft Data Access Components (MDAC) version 2.5 or later be installed on your system. The MDAC install file can be downloaded from the www.microsoft.com/data web site. To determine what version of MDAC you have, check the version of the msado15.dll file or use the Component Checker, available from the Microsoft web site. 1.4 TCP/IP over twinax ------------------------------------------------------------------If you are running TCP/IP over twinax, and are migrating from Client Access for Windows 95/NT (5763-XD1), install the following Client Access for Windows 95/NT service packs before installing iSeries Access for Windows. If you do not do this, your TCP/IP over twinax driver will be disabled, and you will need to reinstall it. V3R1M3: V3R2M0: Service pack SF51967 Service pack SF51617

If you are currently using an older version of Client Access, you will need to reinstall the TCP/IP over twinax driver after iSeries Access for Windows is installed. 1.5 MAPI support

--------------------------------------------------------------------V5R2M0 iSeries Access for Windows does not support MAPI. If you were using MAPI for the purpose of having your mail application access the SDD (Directory), it is recommended that you now use an LDAP directory instead. iSeries Navigator provides support for configuring so that SDD information is published to LDAP. 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). Critical fixes that must be downloaded are listed at "www.ibm.com/eserver/iseries/access/v5r2.htm". 2.2 Directories for iSeries Access files --------------------------------------------------------------------Members of the Users group (Restricted Users) in Windows 2000 or later are provided 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 now are saved, by default, in a different area than older Client Access versions. Prior to V5R1, these files had been stored under the directory in which Client Access was installed. They now are stored in a location that Microsoft documents as being less restrictive. Files stored by users in previous Client Access versions are not moved during an upgrade to V5R1M0 or V5R2M0, but new files are, by default, stored in the new less restrictive location. Examples of such files include the following: - history log and trace files - Saved Data Transfer requests This change is in effect on all versions of Windows when running the V5R1M0 or later client. The less-restrictive path is not the same across all versions of Windows. Because this path may be changed by your Administrator at any time, the locations of these files may not always be the same. For more information, see the topic "Saving and Finding iSeries Access for Windows Files" in the Online Users' Guide. 3.0 INSTALLATION NOTES AND KNOWN PROBLEMS ---------------------------------------------------------------------3.1 Management Central Connectivity Updates ---------------------------------------------------------------------Warning! Connection failures could occur when using Management Central in a network which includes both V5R1 and V5R2 OS/400 releases. To avoid connection error conditions, you must update all V5R1 OS/400 servers and V5R1 Client Access Express for Windows PC software (See the PTF and service pack cover letters for installation details):

- Client Access Express for Windows V5R1M0: Service pack S101907 or higher (for 5722XE1) - OS/400 V5R1M0: Cum package C1302510 (marker PTF TC01302) or higher, or individually install the following 5722SS1 PTFs: V5R1M0: S101375 V5R1M0: S101376 V5R1M0: S101377 V5R1M0: S101378 V5R1M0: S101838

3.2 Memory requirements ------------------------------------------------------------------iSeries Access for Windows requires more memory than previous versions. Refer to iSeries Access for Windows - Getting Started, for a list of requirements you need to run iSeries Access for Windows on your PC. You can access this PDF through the Information Center by this path: iSeries Access-> iSeries Access for Windows-> Get started 3.3 Information not available at time of publication ---------------------------------------------------------------------See the addendum (www.ibm.com/eserver/iseries/access/v5r2.htm) to this Readme File for information that was not available at the time of publication. [END OF DOCUMENT]