======================================================================== Readme File for AS/400 Client Access Express for Windows Service Packs 5722-XE1 V5R1M0 Cumulative Service Pack Level ------------- SI01907 ------------- (c) Copyright IBM Corporation 2000. All rights reserved. ======================================================================== IMPORTANT: If you are a Management Central user, it is very important that you review the information in APAR SE02365 in the "Operations Navigator Base Support" section. There are PTFs for the 5722SS1 product that must be applied to your Central System and all endpoints in order to connect to V5R1M0 Management Central servers after installing this Service Pack. ----------------- Table of Contents ----------------- 1.0 INSTALLATION INSTRUCTIONS 1.1 INSTALLING FROM AN AS/400 SYSTEM 1.2 INSTALLING FROM A LOCAL OR NETWORK DRIVE 2.0 RESTRICTIONS 2.1 OPERATIONS NAVIGATOR 2.2 OPERATIONS CONSOLE 3.0 AUTHORIZED PROGRAM ANALYSIS REPORT (APAR) ABSTRACTS - SERVICE PACK LEVEL = SI01907 (August 2001) 4.0 INSTALL/UNINSTALL CONSIDERATIONS 4.1 REMOVING THE SERVICE PACK 4.2 UNABLE TO INSTALL FROM THE SERVICE SOURCE? 4.3 SERVICE PACK CONTROL 5.0 DATA TRANSFER CONSIDERATIONS 5.1 TRANSFERRING DATA WHEN THE FILE OR DATA CCSID IS 65535 --------------------------------------------------------------------- 1.0 INSTALLATION INSTRUCTIONS ------------------------------ 1.1 INSTALLING FROM AN AS/400 SYSTEM --------------------------------------------- The following method would be used if you have received the Client Access Express 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 an AS/400 system with the LODPTF and APYPTF AS/400 commands, it can be installed on individual PC's with the "Check Service Level" or "Install Service Pack" shortcuts in the Client Access Express Service folder. Check Service Level, controlled by the Client Access Properties Service tab, will detect that the Service source directory has been updated, and will present the user with the option to install the service pack at startup time as well. The APYPTF will update the Express install image directory (\QIBM\ProdData\CA400\Express\Install\Image) on the AS/400. Any client that installs V5R1 Express (or selected components) from this image will automatically receive this service pack level (no extra steps or reboots). In this scenario, the service pack cannot be uninstalled on the client PC because it is merged in with the base release. RMVPTF will restore your AS/400 install image to the prior service level (or the base release if there was no prior service pack applied). 1.2 INSTALLING FROM A LOCAL OR NETWORK DRIVE --------------------------------------------- The following method would be used if you have received the Client Access Express service pack as a set of install image files. Install the service pack by running the "SETUP.EXE" program from your PC. This program is part of the install image files shipped with a service pack. If you change the Client Access Properties Service tab Source Directory to the directory containing these install image files, you can also use the "Check Service Level" or "Install Service Pack" shortcuts in the Client Access Express Service folder. Before running this program, copy the service pack install image files to a local drive on your PC or to any accessible network drive. Once the install setup program has completed, you can then remove the install image files from that drive. 2.0 RESTRICTIONS ----------------- 2.1 OPERATIONS NAVIGATOR ------------------------- 1) Due to technology incompatibilities, occasionally a window can be displayed behind other windows when running the Operations Navigator. If the Operations Navigator looks like it has stopped working, it is possible that the window you are waiting for is being displayed behind another window on your desktop. Press the Alt key and then the Tab key to see a list of all the windows on your system and select window behind the Operations Navigator window, or another window on your desktop. 2) When using Operations Navigator on a Windows 95 PC: For Windows 95, at least the 'a' level service pack must be installed. To determine if you are running Windows 95 A or later, click Start, point to Settings, click Control Panel, then double-click System. If the version number reported is 4.00.950 A or later, no action is required. Your system already contains the appropriate fix. If you do need to install the update, it is available at http://www.microsoft.com/windows95/downloads/contents/ WURecommended/S_WUServicePacks/W95SvcPack1/Default.asp Windows/95 PCs with back level versions of winsock may experience the following runtime errors in Operations Navigator when using Visual Explain (under Database), Windows Administration (under Network), or Disk units (under Hardware Inventory in Configuration and Service): ExceptionInInitializerError NoClassDefFoundError If you experience the above errors, the solution is to update the winsock.dll to version 4.10.1656. This update can be found on the Microsoft download website at: http://www.microsoft.com/windows95/downloads/ Then take the link for "Windows Socket 2 Update" 2.2 OPERATIONS CONSOLE ----------------------- 1) Use of Windows/95 as an operating system for the Local Controlling System is NOT recommended. 2) It is recommended that you restrict LAN topologies for LCS attachment to a single, physical ring/hub/switch fabric. In the event that the LCS is used in a larger network topology, broadcast (DHCP) packet filtering is always recommended. 3) The maximum number of concurrent active sessions via the PCOM 5250 emulator is 26. 4) If an automatic session re-connect to an OS/400 image on an iSeries or AS/400 server on Operations Console start-up fails, simply use the manual re-connect process by right-clicking the connection profile that failed to re-connect and selecting 'Connect'. 3.0 AUTHORIZED PROGRAM ANALYSIS REPORT (APAR) ABSTRACTS -------------------------------------------------------- This a list of APAR fixes included in this service pack. Each service pack is cumulative; the current service pack includes all the fixes from the prior service pack levels. The APAR abstracts are listed by installable component within a service pack level. --------------------------------- Service Pack Level = SI01907 Build date = August 2001 --------------------------------- EXPRESS REQUIRED PROGRAMS ------------------------- APAR = SE01670 CA400EXP-CONNECTIONS-MSGCWBLM0011 CWBLM0011 INTERNAL LICENCE When PCOM v4.3 is installed on the Windows workstation, selecting to start 5250 emulation from within Operations Navigator or other parts of Client Access Express results in an error being displayed. APAR = SE01897 CA400EXP-MIGRATION-UNPRED AFTER MIGRATION TO CLIENT ACCESS 5 When Migrating to v5r1 CA .dll files are not updated so that certain functionality is lost at the new release. In this particular case the problem is with the options available when right clicking on a particular printer through the opperations navigator. The options available after a migration are as follows Explore Open Create shortcut Where at previous releases of CA and after a fresh install of 5.1 the options are Explore Open Create shortcut Printer output ------------------- Sharing > ------------------- Reply... Hold... Release... ------------------- Start... Stop... Restart... Make Available... Make Unavailable... ------------------- Paste ------------------- Properties APAR = SE02319 CA400EXP-TERMEMUL PERSONAL COMMUNICATIONS V4.3 NOT STARTING When PCOM v4.3 is installed on the Windows workstation, selecting to start 5250 emulation from within Operations Navigator or other parts of Client Access Express results in an error being displayed. Within V5R1 Client Access Express, only PCOM v5.0 with CSD1 applied is supported. This fix will change Operations Navigator and Client Access Express to only allow starting 5250 emulation when PCOM v5.0 and CSD1 are installed. Circumvention: Install PCOM 5.0 and PCOM 5.0 CSD1 on the Windows workstation. APAR = SE02320 CA400EXP-TERMEMUL-INCORROUT PCOM 5.0 START/CFG FAILURES The following problems occur only on PCs with both IBM Personal Communications version 5 and the iSeries Access v5r1 client installed. When, in Operations Navigator, a connection name is right- clicked and Display Emulator is selected, the message "The PC5250 emulator could not be started..." is displayed and no PC5250 session is started. When attempting to create a new iSeries Access PC5250 desktop icon by right-clicking on the desktop and selecting New, then AS400 Desktop Icon, then PC5250 Emulator, the message "The PC5250 emulator desktop icon could not be configured..." is displayed. IBM Personal Communications files, such as workstation profiles (.ws) and keymap (.kmp) files, are stored in an unexpected location on your PC, such as C:\. Normally, such files are typically stored within a subdirectory of the Personal Communications install path called "private". In such cases, Personal Communications will usually function normally, but the user may not be satisfied with the location of the related files. The cause of the first two problems, in which Personal Communications fails, is a bad registry entry containing a path that does not exist on the PC. iSeries Access attempts to use this path, and cannot. These problems are fixed by this PTF. If the path stored does not exist, iSeries Access will now use the subdirectory of the Personal Communications install path called "private", which is what Personal Communications itself would use. The non-existent path entry can be changed by use of the Personal Communications Utility called User Preferences. On the Basic tab, the path at which to store its files is shown. The bad path can be deleted by the user. The final problem, in which files are stored but in a path that is unexpected, can be solved by changing the path as described above. You may also wish to move the Personal Communications files from the old to the new path. If you have created PC5250 icons, they probably refer to the workstation profiles stored in the old path. To continue to work, you must change these icons to refer to the workstation files stored in the new location. This applies to both desktop icons and to icons stored in the IBM Personal Communcations folder under Start\Programs. EXPRESS OPTIONAL COMPONENTS --------------------------- DIRECTORY UPDATE ---------------- No fixes. INCOMING REMOTE COMMAND ----------------------- No fixes. MAPI ---- No fixes. EXPRESS ONLINE USER'S GUIDE --------------------------- No fixes. AS/400 OPERATIONS NAVIGATOR --------------------------- IMPORTANT: For Management Central users, there are two required PTFs that must be installed on an iSeries V5R1M0 server: 5722SS1 SI00721 5722SS1 SI00722 It is required that a Client Access Express user apply this service pack (SI01907) before trying to connect to the Management Central server on an iSeries on which the above mentioned PTFs are applied. If there is a mismatch, errors will occur. Additional requirements for your iSeries V5R1M0 server relating to Management Central are are outlined below in APAR SE02365 as well. OPERATIONS NAVIGATOR BASE SUPPORT --------------------------------- APAR = SE02363 CA400EXP-OPNAV - VISUALBASIC PLUGINS FAIL Plugins written in Visual Basic will not operate properly in Operations Navigator. This impacts plugins which use the getObjectNamesFromClipboard and setObjectNamesToClipboard methods in UIServices or plugins which use the getListObjectFromName method in ObjectName. APAR = SE02365 CA400EXP-OPNAV MGMT CENTRAL JAVA PORT REDUCTION/SSL This enhancement will allow you to turn on Secure Sockets Layer (SSL) for Management Central Job Monitors, Message Monitors, and System Values functions in V5R1M0. Prior to this service pack, these functions are disabled if you have the Management Central Properties set to use SSL. If you have installed this service pack and are intending to use Management Central, you will need to apply 5 co-requisite PTFs to your Central System and all endpoints. You must also install the service pack on any PCs you want to use Management Central from. If you don't apply these PTFs, you will not be able to connect to any V5R1M0 Management Central servers. (Connections to V4R5M0 or earlier will not be affected). The 5 PTFs are for the 5722SS1 product and their numbers are: SI01375 SI01376 SI01377 SI01378 SI01838 Additionally, if you would like to use SSL with Management Central, you must do some configuration with Application Administration. In Operations Navigator, under your local connections, run Application Administration for a system you are going to use SSL on. On the Host Applications tab, expand Digital Certificate Manager (DCM), then highlight System Certificate Store. Click on the Customize button. On the Customize Access window, expand All Users under the Users and Groups section. Select user QYPSJSVR, then add it to the Access Allowed section. Click OK on the Customize window, then click OK on the Application Administration window. Repeat this for every system you are going to use with SSL for Management Central, central system and endpoints. BASIC OPERATIONS ---------------- No fixes. WORK MANAGEMENT -------------- No fixes. CONFIGURATION AND SERVICE ------------------------- Non-APAR fixes. NETWORK ------- APAR = SE02364 CA400EXP-OPNAV L2TP AND IGN DIAL WIZARD UPDATES The New Profile Setup dialog was changed for new originator profiles. The "L2TP initiator-on-demand" and the "L2TP remote dial-on-demand" mode selections were removed from the list of operating modes. These two operating modes are not supported on the iSeries server. The AT&T Global Network Dial Connection wizard was updated so that the route redistribution dynamic routing parameter is no longer set when the dial profile is created. The wizard was incorrectly setting the route redistribution parameter when the profile was created and passive routing was configured. SECURITY -------- No fixes. USERS AND GROUPS ---------------- No fixes. DATABASE -------- Non-APAR fixes. FILE SYSTEMS ------------ No fixes. BACKUP ------ No fixes. APPLICATION DEVELOPMENT ----------------------- No fixes. COMMANDS -------- No fixes. PACKAGES AND PRODUCTS --------------------- No fixes. MONITORS -------- Non-APAR fixes. LOGICAL SYSTEMS --------------- Non-APAR fixes. AFP MANAGER ----------- No fixes. APPLICATION ADMINISTRATION -------------------------- No fixes. DATA ACCESS ----------- DATA TRANSFER ------------- DATA TRANSFER BASE SUPPORT -------------------------- No fixes. DATA TRANSFER EXCEL ADD-IN -------------------------- APAR = SE02321 CA400EXP-DTRANSFER EXCEL XP UPLOAD NOT SUPPORTED After installing Microsoft Office XP, the Client Access Express Data Transfer Excel Upload function does not work. When the upload function is selected, a dialog is displayed that indicates that the version of Excel is not supported. ODBC ---- APAR = SE01815 CA400EXP-ODBC-INCORROUT LIBRARY LISTS FOR EXISTING DATA SOUR Data Sources configured with multiple default libraries do not migrate correctly after an upgrade from R440/R450 to R510 Client Access Express. The first library on the list is migrated and appears correctly as the 'SQL default library'. Other libraries are dropped and appear as neither an 'SQL default library' nor as an entry on the 'Library list'. APAR = SE01894 OSP-MSGPWS0006-PAR ODBC - APPLICATION REQUEST FOR STATIC CUR An ODBC application which worked when connecting to OS/400 V4Rx, is receiving a MSGPWS0006 when it sends a request to OS/400 V5R1 for a static cursor when also sending an invalid value for SQL_MAX_ROWS. This did not generate an error at V4. V4 did not support static cursors and it appears that on V4, if the application specified a static cursor the connection automatically used a dynamic cursor instead. Since V5R1 does support static cursors, a static cursor is used on a V5 connection if it is specified by the application. Static cursors are limited to a positive value up to 2GB (2147483647) for SQL_MAX_ROWS. As a compatibility concern the following problem also needs to be addressed: Static cursors are supported by V5R1 clients to V5R1 hosts. An application attempting to use static cursors with the V4R5 client will instead get a dynamic cursor. An option to receive the same behavior is needed in the V5R1 client. Adding 32 to the DEBUG keyword indicates to the driver to convert static cursors to dynamic cursors. The DEBUG keyword can be entered into the registry where the DSNs are stored or it can be passed on the SQLDriverConnect connection string. The problem with specifying a value larger than 2 GB is fixed. APAR = SE02158 CA400EXP-ODBC-INCORROUT INVALID TABLE TYPE ON CATALOG REQUES The V5R1M0 Express Client's ODBC driver is not ignoring table types which it doesn't support when that type is passed on an SQLTables catalog request. The driver returns a return code indicating an error and error text stating 'Invalid table type ignored.' and sets the SQLState to 01000. Table types which cause the driver to fail in this fashion include, 'SYSTEM VIEW' and 'SYSTEM SYNONYM'. The correct behaviour would be to ignore the invalid type, pass back the data only for the table types the driver does support and set the return code and SQLState to succussful values. APAR = SE02205 CA400EXP-ODBC-INCORROUT - NUMERIC COLATTRIBUTE UPDATE LENGTH SQLColAttribute inappropriately updates StringLengthPtr for numeric attributes. APAR = SE02322 CA400EXP-ODBC FAILURE ON PROCEDURE CALL WITH PARAMETER NAMES Client Access Express ODBC driver fails with the error message SQL0104 "Token was not valid." when applications call stored procedures using the ODBC syntax where parameter values are assigned to parameter names. For example: {CALL PROCEDURENAME(PARM1 = 'VALUE1', PARM2 = 3)} APAR = SE02323 CA400WINOPT-ODBC-INCORROUT LOCKED RECORD INDICATES EOF WITH The Client Access ODBC driver returns the incorrect result when an ODBC application fails to fetch a locked record using SQLExtendedFetch and a block size greater than 1. The ODBC driver returns SQL_SUCCESS and rowstatus values of SQL_ROW_NOROW for the locked row and all rows after the locked row. This result indicates EOF and not a locked row. In addition, the next fetch receives SQL_NO_DATA_FOUND even if the lock has been released. The driver should be returning SQL_SUCCESS_WITH_INFO. The row status buffer should be set to SQL_ROW_ERROR for each row not fetched. The error buffer should be filled with at least one error per row with SQLState 01S01 and an appropriate error message (SQL0913 or similar). A second fetch request should be sent to the server to retry the fetch from the locked row. The problem has been observed with R320, R440 and R450 versions of Client Access. The problem may not occur when the block size is very large. With very large block sizes a SQL0913 and SQL_ERROR may be returned. APAR = SE02324 CA400EXP-ODBC-INCORROUT - NUMERIC CONVERSION PROBLEMS When inserting numeric data into a field, if any fractional digits are truncated the result should be an error. The V5R1 driver instead inserts the data and returns a warning. The driver incorrectly assumes that character data is null-terminated when doing conversions to ZONED or PACKED fields. APAR = SE02325 CA400EXP-ODBC-INCORROUT PROBLEMS WITH ERROR HANDLING A stored procedure can be written to signal an error. However, the driver incorrectly reports a native error of 30995. The appropriate SQL code should instead be used. When a communication error is detected while gathering host error message text, there is no indication of it. The user gets back only one error message and there is no text for it. APAR = SE02326 CA400EXP-ODBC-INCORROUT PROBLEMS WITH SQL STMT PARSING SQL statements ending in a quote and followed by another quote in memory are mishandled. For example, if another quote follows '0001' in memory the driver incorrectly treats this as '0001''. When calling a stored procedure that has a return value the driver is restricting the syntax. For example, the driver wouldn't allow the following: {? = CALL MYPROC()} However {?= CALL MYPROC()} would work. Circumvention: Specifying a blank at the end of the SQL statement will avoid the problem with the driver's mishandling of a quote found after the SQL statement in memory. Removing all blanks between the ? and = when calling the stored procedure will avoid the second problem. APAR = SE02327 CA400EXP-INSTALL-INCORROUT - CONCURRENCY SETTING NOT HONORED There is a problem with how concurrency is used. Setting the statement's concurrency to SQL_CONCUR_LOCK is not honored if the DSN option for 'Override ODBC concurrency with SQL_CONCUR_LOCK except if FOR FETCH ONLY specified' is unchecked (default). Setting the statement's concurrency to SQL_CONCUR_READ_ONLY is not honored if the DSN option for 'Override ODBC concurrency with SQL_CONCUR_LOCK except if FOR FETCH ONLY specified' is checked. Note, this only affects SELECT SQL statements that do not specify the FOR FETCH ONLY or the FOR UPDATE clauses. The problem has been fixed. However, there is one restriction. The restriction is that the statement's concurrency can not be changed after the statement is prepared. If the concurrency is changed after the statement is prepared, it will not be used until the next SQL statement is prepared. Note, a host PTF is also required for this support to work. Circumvention: The circumvention is to specify FOR UPDATE or FOR FETCH ONLY in the SELECT SQL statement. Those clauses will always be honored over the statement's concurrency setting. APAR = SE02328 CA400EXP-ODBC-INCORROUT - MISCELLANEOUS ODBC PROBLEMS When calling SQLGetTypeInfo with the SQL_ALL_TYPES option the driver doesn't sort the result set by the SQL data type. Specifying a customized package library setting is not honored. Instead the default package library is used. The SQL Server 2000 application does not work correctly unless calling SQLSetStmtAttr to set the SQL_ATTR_RETRIEVE_DATA option does not return an error. Calling SQLSetConnectAttr to set the SQL_ATTR_CURRENT_CATALOG option currently returns an error. A fix is needed to allow the current catalog to be set to the RDB name. Calling SQLColumns with an empty string for the file name gives incorrect output. An empty result set should be returned. APAR = SE02329 CA400EXP-ODBC-UNPRED - OPTION TO RETURN DB2-DEFINED SQLSTATE Users of IBM Toronto's DB2 Connect ODBC/CLI driver receive different SQL states with the Client Access ODBC driver. In order to help in porting issues between IBM products, the Client Access ODBC driver needs a way to return DB2-defined SQL states. A DSN option has been added to return DB2-defined SQL states. A new keyword, DB2SQLSTATES, has been created to allow a user / application to enable this support. Setting DB2SQLSTATES to 1 indicates to the driver to return DB2SQLSTATES. Leaving DB2SQLSTATES set at 0 (default) indicates to the driver to return the SQL State as it currently does. Note, this only affects errors generated by the server when processing SQL statements and their result sets. This does not affect SQL States returned during the connection attempt. APAR = SE02330 CA400EXP-ODBC-INCORROUT - SQLGETDATA PROBLEMS When SQLGetData is called on a SQL_CHAR field with buffer size less then field size the driver returns the correct information on the first call. On subsequent calls the driver incorrectly returns the same data as on the first call (both the targetValue and the StrLen). This can cause an application to loop. When SQLGetData is called on lob field with a buffer size greater then or equal to the data length all data is returned and SQL_SUCCESS is returned. Some applications such as Microsoft ADO attempt another, unneccessary, SQLGetData. The driver incorrectly returns the data from the previous call along with SQL_SUCCESS. This causes some ADO applications to go into a loop. The driver should return SQL_NO_DATA_FOUND There is also a problem with SQLGetData when called on a LOB locator column, particularly a DBCLOB. The behavior does not match what the ODBC specification states is the correct behavior. APAR = SE02331 CA400EXP-ODBC ERROR IN SQLPARAMDATA Fault in SQLParamData when called for second parameter APAR = SE02332 CA400EXP-ODBC-UNPRED - USABILITY ENHANCEMENTS On the GUI, if the default library is also in the library list it should be automatically removed from the library list. If not, the libraries are not added to the job's library list when connecting. If a value greater than 15 MB is entered in on the GUI for the Large objects (LOB) threshold the driver defaults it to 32K when saving it. APAR = SE02333 CA400EXP-ODBC-INCORROUT - BLOCK FETCH ISSUES When using the "Use blocking with a fetch of 1 row" option, the driver always converts dynamic cursors to use a block factor of 1 row. On fetches forward the driver should attempt to block. In some cases, such as when LOB locators are present, the driver can calculate block factors which exceed host limitations. This can happen when the "Use blocking with a fetch of 1 row" option is turned on or off. The driver should better handle the option when "Use blocking with a fetch of 1 row" is selected. When doing a block fetch and there are locators in the result set, the driver incorrectly returns the same row of data for each row in the block. APAR = SE02334 CA400EXP-ODBC-INCORROUT - ERROR ON PREPARE OF DRDA & DECLARE Calling SQLPrepare for DRDA (CONNECT TO, DISCONNECT, ...) and DECLARE SQL statements causes an "Error in host data stream" error message. APAR = SE02335 CA400EXP-ODBC LAST BLOCK FETCH FOR CATALOG RETURN SWI ODBC driver returns SQL_SUCCESS_WITH_INFO for the last block fetch if a catalog function, e.g. SQLTables, is called. It should return no data found. OLE DB PROVIDER --------------- IMPORTANT: If you have the OLE DB component of Client Access Express installed on a Windows NT or Windows 2000 PC, and this is the first V5R1M0 service pack installed on this PC, you should make sure that an Administrator performs the initial reboot after the Service Pack install. The DLL self-registration that occurs during the reboot requires Administrator authority. In the event that this recommendation is not followed, you can self-register the DLL by running the following command: regsvr32 "C:\Program Files\IBM\Client Access\cwbzzodb.dll" (where the actual Client Access Express install directory is substituted into this command) APAR = SE02336 CA400EXP-OLEDB-UNPRED CHANGE REGISTRY ENTRIES FOR TRACE/LOG The cwbzztrc tool does not work well in multiple user scenarios. This ptf changes the location of the OLE DB Provider's trace and log information, in order to make tracing and logging more consistent in multi-user scenarios. Information will now be stored in the registry at: HKEY_LOCAL_MACHINE\Software\IBM\Client Access\CurrentVersion\ Common\AS400 OLE DB Provider\Service LOTUS 123 FILE FORMAT SUPPORT ----------------------------- No fixes. AFP WORKBENCH VIEWER -------------------- No fixes. AS/400 JAVA TOOLBOX ------------------- This Client Access Express Service Pack will also install the equivalent of 5722JC1 product PTF SI01744. In particular, the following fixes are relevant to Client Access Express: When working with a tree in the list area of the console, there is no change in focus from the item in the Navigation area. This occurs when tabbing from the tree to the list and the list is a tree-list. When you try and select tree items in the list area using the Shift key, you can only select 2 successive items. This occurs when the list is a tree-list. Incorrect conversion of Turkish i's in Command Prompter may prevent some commands from prompting or running. 5250 Display and Printer Emulation ---------------------------------- APAR = SE02343 CA400WINOPT - PC5250 CURSOR POSITIONING PROBLEM After applying SF64217, when a data entry screen is displayed and a prompt screen is called from the data entry screen, Page Down on the prompt screen causes the cursor to go to the upper left corner of the data entry screen that is in the background. APAR = SE02344 CA400WINOPT - FIELD EXIT ON A MANDATORY FILL SIGNED NUMERIC Using PC5250 emulation, when the Field Exit key is pressed on a Signed Numeric field that is not completely filled, the error message "This field must be filled before exiting" is displayed. On dumb terminals, when the Field exit key is pressed on a Signed Numeric field that is not completely filled, the numeric data is right justified and the field is exited, even though the Mandatory Fill parameter is set on this field. That is how PC5250 emulation should work. APAR = SE02345 CA400EXP-TERMEMUL-INCORROUT PC5250 VB SCRIPT MACROS RUNNING VB Script Macros running system request actions fail since SF64474 installation. Previous service pack SF63638 works fine. APAR = SE02346 CA400EXP-TERMEMUL-PC5250 STRPCO COMMAND CAUSES HANG STRPCO command causes PC5250 to hang. PC5250 session comes back after clicking on the desktop or another window and then clicking on the emulation session again. APAR = SE02350 CA400EXP-PC5250 TELNET PRINTER SESSION INCORROUT When plural output are printed using differed form, they are printed in the same form as continuously. This problem happens using CA/400 Express PC/5250 printer session. E.I. 01 queue 2 spool files in the same OUTQ for Pcom printer session. They has differed form. 02 Start pcom printer session. 03 Then 1st spool file has MSGW, put 7 at OPT and hit enter 04 CPA3394 issues, reply I and Enter 05 Enter 06 F5 key 07 Then 1st spool file has MSGW again, put 7 and enter 08 CPA4044 issues, replay I and Enter 09 Enter 10 PF5 key 11 Then 2nd spool file is position at top. 1st one is FIN status on AS/400. But not printed on pcom yet. 12 ** Check printer session, it is still active ** ** 1st spool file must be printed at the time. ** 13 2nd spool file is MSGW status, put 7 and enter 14 CPA3394 issues, replay I and enter 15 Enter 16 PF5 key 17 2nd spool file is FIN status. 18 1st and 2nd spool file are printed at this time in the same form. APAR = SE02351 CA400EXP-CREATE MULTIPLE SESSIONS GIVES PAGE FAULT Creating multiple sessions with Client Access Express PC5250 give page fault errors on Window ME. APAR = SE02352 CA400EXP -PAGE SETUP GREYED OUT AFTER PRINT SCREEN When do a print screen from a Client Access display session it greys out the page setup. You have to then goto file/printer setup and reselect a printer. You then have the option to use page setup until another print screen is done. APAR = SE02353 DBCS HPT FOR SESSION TYPE Need a change of session type (AS/400 provides DBCS HPT for session type 3812, not 5553) APAR = SE02354 CA400EXP-TERMEMUL-UNPRED PC5250 CURSOR JUMPS TO WRONG POSITI After the user makes an incorrect input in the entry mask (DSPF) of his CA5250 application screen and hits the RESET/CTRL key the cursor doesn't jump to field which is incorrect filled in. The problem doesn't occur with the AS/400 workstation. APAR = SE02355 CA400EXP-TERMEMUL-INCORROUT USING END OF FIELD KEY IN SOME O Using Client Access Express V4R5 with either service pack SF64217 or SF65345, remapping and using the END OF FIELD key may hang the session during data entry on some OEM applications. APAR = SE02356 PC5250-PRT-INCORROUT TRAY SELECTION DOES NOT WORK PC5250 does not generate a Select Paper Tray command =X/1b7e46 when she receive PPM command = x/2bd20a48 if the tray number is same as before. It should not be suppressed on Windows environ- ment since other application is also using printer and might specify the paper tray. APAR = SE02357 CA400EXP - PC5250 PRESSING TAB KEY IN DBU HANGS SESSION After applying SF65345 and using PC5250 emulation, if either the Tab key or the F10 key are pressed when in DBU, the session hangs. APAR = SE02358 CA400EXP-TERMEMUL-INCORROUT PC5250 SESSIONS HANG WITH F10 After applying SF65345, when navigating through an OEM application menu and the F10 key is pressed, the PC5250 PC5250 session hangs. APAR = SE02359 CA400EXP - WORDWRAP ON EMULATOR FAILS TO REMOVE NULLS OR When using the DDS keyword for wordwrap on a CAE Emulator nulls are not removed after a word has been wrapped. APAR = SE02360 CA400EXP-TERMEMUL-INCORROUT PC5250 CURSOR POSITIONING DOESN' Cursor positioning doesn't work on PC5250 display sessions, since SF65345 installation APAR = SE02361 CA400EXP - PC5250 PAGE FAULT MESSAGE WITH SF65706 APPLIED When Popup keypad is customized with the Paste Next function the following error is dislayed: "PCSWS caused an invalid page fault in module PCSEDIT.DLL..." APAR = SE02387 CA400EXP-TERMEMUL-INCORROUT PC5250 BELGIAN DUTCH (2963) TOOL PC5250 Belgian Dutch (lang id 2963) Toolbar appears in Spanish language. PRINTER DRIVERS --------------- AFP PRINT DRIVER ---------------- No fixes. SCS PRINT DRIVER ---------------- APAR = SE02338 CA400EXP- UNPRED SCS PRINTER DRIVER HANGS WINNT WIN2000 The 5.03 version of the SCS printer driver shipped with Client Access Express for Windows may cause a hang condition when a user attempts to change the conversion table used by the driver. APAR = SE02339 CA400EXP-INCORROUT SCS FONT CHANGES ON D/T423 Using the IBM SCS printer driver and printing to d/t 4234 printer, the font changes point size. AS/400 OPERATIONS CONSOLE ------------------------- APAR = SE02340 CA400EXP-OPCON-INCORROUT RCP CONNECTION FAILS TO CONNECT TO 27x and 8xx AS/400 Systems require a specific cable connection between the Debug port on the AS/400 and a parallel port on the PC that has been configured to use EPP. The documented requirement is that the PC Parallel Port be EPP 1.9 compliant. Most PCs that meet this requirement fail to connect and in some cases will connect but cause the AS/400 to IPL. APAR = SE02341 CA400EXP-OPCON -MSGACCESS WAS DENIED BECAUSE THE USERNAME/AN When using a PC with Windows 2000 as an RCS to connect to a Windows 2000 LCS that logs onto a domain, Client Access V4R5M0 Operations Console, the RCS receives the following error when trying to connect to the LCS "Access was denied because the username/and or password was invalid on the domain". The code has been changed to call the Microsoft Dial-up networking dialogs to prompt the user for a userid and password. This allows the user to enter the userid, password, and domain they want to validate to. APAR = SE02342 CA400EXP-OPCON-MSGCPF5140 OPERATIONS CONSOLE RANDOMLY DROPS Since upgrading to R450 OS/400 and Client Access Express R450 the customer's nightly CL program that does a delay job every 1 second until a predetermined time then starts a savsys, followed by several savlib commands, then restarts all of the subsystems will fail at various times about once every 10 days. The failure is always accompanied by a msgCPF5140 in the joblog for the CL. The CWBOPCON.LOG file contains a corresponding entry that indicates the PC is initiating a new console connection that starts by doing an END RAS CONNECTION that ends the connection to the system. This process causes the console display session on the AS/400 to end, which in turn ends the interactive CL job, then starts a new console connection/session. This same CL job was run in the same manner on the system at R430 with Client Access for Windows 95/NT R320 Operations Console with no problem. Operations Console was not waiting long enough while detecting if the system was still there. The length of time to wait before detecting the system had been IPLed or powered off has been extended. CLIENT ACCESS EXPRESS TOOLKIT ----------------------------- HEADER, LIBRARY, AND DOCUMENTATION ---------------------------------- No fixes. VISUAL BASIC WIZARDS -------------------- No fixes. TOOLS FOR JAVA -------------- No fixes. EZ-SETUP WIZARD --------------- APAR = SE02362 CA400EXP-OPNAV LANGUAGE MISMATCH IN DOMINO EZ SETUP WIZARD Domino Ez setup wizard remains in the second panel titled "Domino Server Installation -- Insert CD-ROM" when using a Domino CD with a language different to the primary language installed in the AS/400. The following popup message continuously appears: "D0112: The language on your iSeries 400 server does not match the language on the Domino software." --------------------------------- Service Pack Level = SI01037 Build date = May 2001 --------------------------------- EXPRESS REQUIRED PROGRAMS ------------------------- APAR = SE01206 CA400EXP-CONNECTIONS-INCORROUT CLIENT ACCESS EXPRESS CWBCFG APAR = SE01207 CA400EXP-UPDATE DIRECTORY UPDATE FAILS WHEN A DBCS FILE NAME APAR = SE01236 CA400EXP-OPNAV-HWINV-INCORROUT DISK UNITS NOT SHOWN EXPRESS OPTIONAL COMPONENTS --------------------------- DIRECTORY UPDATE ---------------- No fixes. INCOMING REMOTE COMMAND ----------------------- No fixes. MAPI ---- No fixes. EXPRESS ONLINE USER'S GUIDE --------------------------- No fixes. AS/400 OPERATIONS NAVIGATOR --------------------------- OPERATIONS NAVIGATOR BASE SUPPORT --------------------------------- Non-APAR fixes. BASIC OPERATIONS ---------------- No fixes. WORK MANAGEMENT -------------- No fixes. CONFIGURATION AND SERVICE ------------------------- Non-APAR fixes. NETWORK ------- Non-APAR fixes. SECURITY -------- No fixes. USERS AND GROUPS ---------------- No fixes. DATABASE -------- Non-APAR fixes. FILE SYSTEMS ------------ APAR = SE01235 CA400EXP-OPNAV-FILESYS-UNPRED NEW JAVA PROGRAM LABEL GONE BACKUP ------ No fixes. APPLICATION DEVELOPMENT ----------------------- No fixes. COMMANDS -------- No fixes. PACKAGES AND PRODUCTS --------------------- No fixes. MONITORS -------- Non-APAR fixes. LOGICAL SYSTEMS --------------- Non-APAR fixes. AFP MANAGER ----------- Non-APAR fixes. APPLICATION ADMINISTRATION -------------------------- No fixes. DATA ACCESS ----------- DATA TRANSFER ------------- DATA TRANSFER BASE SUPPORT -------------------------- APAR = SE01208 CA400EXP-DTRANSFER V4R4/R5 DTF GIVES INCORRECT FILE OPTIONS DATA TRANSFER EXCEL ADD-IN -------------------------- Non-APAR fixes. ODBC ---- APAR = SE01237 CA400EXP-ODBC-MSGSQL0106 FAILURE WHEN CREATING A TABLE APAR = SE01238 CA400EXP-ODBC INVALID VALUE RETURNED FOR FLOAT DATA TYPES APAR = SE01239 CA400EXP-ODBC ADDITIONAL OPTION TO DISABLE PROMPTING APAR = SE01240 CA400EXP-ODBC-INCORROUT WRONG SQLSTATE VALUE RETURNED OLE DB PROVIDER --------------- APAR = SE01241 CA400EXP-OLEDB-INCORROUT SUPPORT FOR MULTIPLE RESULT SETS APAR = SE01243 CA400EXP-OLEDB-INCORROUT FREE THREADING LOTUS 123 FILE FORMAT SUPPORT ----------------------------- No fixes. AFP WORKBENCH VIEWER -------------------- No fixes. AS/400 JAVA TOOLBOX ------------------- This Client Access Express Service Pack will also install the equivalent of 5722JC1 product PTF SI00131. 5250 Display and Printer Emulation ---------------------------------- This Service Pack includes PCOM5.0 CSD1 plus additional fixes. APAR = SE01205 CA400EXP-OPNAV-INCORROUT DISPLAY EMULATOR (PC5250) VIA OPNAV PRINTER DRIVERS --------------- AFP PRINT DRIVER ---------------- No fixes. SCS PRINT DRIVER ---------------- No fixes. AS/400 OPERATIONS CONSOLE ------------------------- APAR = SE01244 CA400EXP-OPCON OPERATIONS CONSOLE LAN CONNECTION CLIENT ACCESS EXPRESS TOOLKIT ----------------------------- HEADER, LIBRARY, AND DOCUMENTATION ---------------------------------- No fixes. VISUAL BASIC WIZARDS -------------------- APAR = SE01242 CA400EXP-OLEDB-INCORROUT VB WIZARD GENERATES INCORRECT CODE TOOLS FOR JAVA -------------- No fixes. EZ-SETUP WIZARD --------------- Non-APAR fixes. 4.0 INSTALL/UNINSTALL CONSIDERATIONS ------------------------------------- The following sections describe additional support and known problems that you may notice while using the Install/Uninstall function. 4.1 REMOVING THE SERVICE PACK ------------------------------ To remove this service pack from your PC: 1. Click the Windows 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 AS/400 Client Access Express for Windows SIxxxxx item, and then click on the Add/Remove button. 4. Follow the instructions on the screen. 4.2 UNABLE TO INSTALL FROM THE SERVICE SOURCE? ----------------------------------------------- InstallShield is the tool used to provide the install support for Client Access Express for Windows. The same tool is used for installing service packs. Setup.exe has a 2 minute timeout which could expire when installing service packs over slower communication lines. The suggested way of installing the service pack in this case is to take one of the options below: 1) A setting has been added to the Client Access Express Properties Service tab that will copy the service pack image to the PC's temporary directory, install the service pack, then remove the copied files. To use this support you will need to specify this setting ("Copy install image to PC before installing"). STATUS: No status information is displayed while the files are copied. To determine if the transfers are progressing, look in the 'CA400CKV' temporary directory (For example C:\Windows\Temp\CA400CKV). You should see new files appear periodically. NOTES: "Copy install image to PC before installing" also works for upgrades to a new release, to avoid the time out over slower communication lines. 4.3 SERVICE PACK CONTROL ------------------------- To prevent users from installing the Service Pack, an administrator can set the Install Service Pack policy restriction, or can use the SP.TXT file. If the administrator places a file named SP.TXT (with a 'N' in the first position of the first line) in the service pack installation image directory, the service pack will not be installed. 5.0 DATA TRANSFER CONSIDERATIONS --------------------------------- The following sections describe additional support or known problems that you may notice while using the Data Transfer function. 5.1 TRANSFERRING DATA WHEN THE FILE OR DATA CCSID IS 65535 ----------------------------------------------------------- WHY DOES MY DATA LOOK LIKE GARBAGE WHEN I PERFORMED A DOWNLOAD? By default, the Data Transfer function will not convert data between EBCDIC and ASCII if the data is tagged with a CCSID of 65535. In older versions of the Win 95/NT Client Access product, the 65535 conversion was controlled by the CWBTFR.INI file. This process has been changed, and the conversion is now controlled by the Data Transfer user interface. Once the setting has been made in the user interface, it is then stored in the transfer request. This is only true for .TTO and .TFR files. .RTO and .DT files are still controlled by the CWBTFR.INI file. The conversion setting for .RTO and .DT files can be modified in the Data Transfer user interface, but the setting will not be saved. The setting to control the conversion is found in the File, Properties information. WARNING: This feature is designed as a workaround for people that can not change the CCSID of their files. In order for this translation to work properly, you must be confident the data in the file matches the CCSID of your user profile. The design of the AS/400 is that data with a 65535 CCSID are not to be converted. This feature will attempt to do a conversion of the data from the job CCSID to the PC CCSID. This conversion may not work if the data in the file does not match the user profile/job CCSID. The correct solution to this problem is to appropriately tag the data with the correct CCSID. One way of doing this is by using CHGPF. For more information on the 65535 CCSID, please reference the AS/400 National Language Support Manual.