Anda di halaman 1dari 10

============================================================================ Readme File for iSeries Access for Windows Service Packs 5722-XE1 V5R3M0 Cumulative Service Pack

Level ------------SI10817 ------------(c) Copyright IBM Corporation 2004. All rights reserved. ======================================================================== Co-requisite PTF SI11224 is automatically included with any shipment or web download of SI10817. SI11224 exists only for packaging reasons. All service pack level references will be to SI10817. NOTICE: ------Application of this PTF may disable or render ineffective programs that use system memory addresses not generated by the IBM translator, including programs that circumvent control technology designed to limit interactive capacity to purchased levels. This PTF may be a prerequisite for future PTFs. By applying this PTF you authorize and agree to the foregoing. ----------------Table of Contents ----------------1.0 INSTALLATION INSTRUCTIONS 1.1 INSTALLING FROM AN iSeries SYSTEM 1.2 INSTALLING FROM A LOCAL OR NETWORK DRIVE 1.3 COMBINING THE SERVICE PACK WITH AN iSeries ACCESS FOR WINDOWS INSTALLATION IMAGE 2.0 RECOMMENDATIONS/RESTRICTIONS 2.1 iSeries SERVER FIXES 3.0 AUTHORIZED PROGRAM ANALYSIS REPORT (APAR) ABSTRACTS - SERVICE PACK LEVEL = SI10817 (January 2004) 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 iSeries SYSTEM -------------------------------------The following method would be used if you have received the iSeries Access for Windows service pack through the iSeries 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 iSeries system with the LODPTF and APYPTF iSeries commands, it can be installed on individual PC's with the "Check Service Level" or "Install Service Pack" shortcuts

in the iSeries Access for Windows Service folder. Check Service Level, controlled by the iSeries Access for Windows Properties Service tab, will detect that the Service source directory has been updated, and will present the user with the option to install the service pack at startup time as well. The APYPTF will update the iSeries Access for Windows install image directory (\QIBM\ProdData\Access\Windows\Install\Image) on the iSeries. Any client that installs iSeries Access for Windows (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. Running setupsp.bat from the iSeries Access for Windows install image directory (\QIBM\ProdData\Access\Windows\Install\Image) will launch the service pack install wizard. View setupsp.bat via Notepad or Wordpad to see instructions on how to invoke setupsp.bat to record or run a silent service pack install. RMVPTF will restore your iSeries 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 iSeries Access for Windows service pack as a set of install image files via a download from IBM's FTP site. Install the service pack by running the "SETUP.EXE" program from your PC. This program is part of the install image files shipped with a service pack. If you change the iSeries Access for Windows 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 iSeries Access for Windows Service folder. Before running this program, copy the service pack install image files to a local drive on your PC or to any accessible network drive. Once the install setup program has completed, you can then remove the install image files from that drive. 1.3 COMBINING THE SERVICE PACK WITH AN iSeries ACCESS FOR WINDOWS INSTALLATION IMAGE -----------------------------------------------------------------------------------The following method could be used if you downloaded the service pack image from the iSeries Access for Windows web page location: The iSeries Access for Windows service pack PTFs are combined with the original iSeries Access for Windows installation image in QIBM\ProdData\Access\Windows\Install\Image NOTE: this directory is a symbolic link to QIBM\ProdData\CA400\Express\Insta ll\Image There is one physical directory - either of these paths will access the direc

tory. This means that a user can install (or upgrade) iSeries Access for Windows from this combined image directory and get the latest applied service level automatically in one integrated step - since the original installation image files have been replaced by updated versions via the service pack PTF. Selectively installing components from this combined image directory will also automatically get the latest applied service level for that component. If you tailored the iSeries Access for Windows install image to another direc tory (for instance, on another server), using the Create Tailored Installation Ima ge (cwbinimg.bat) tool, you can use the PTFFORM.EXE download in the FTP directory to duplicate the function of applying the iSeries PTF by following these steps: 1. Download PTFFORM.EXE (from the tailored/ FTP directory) to a temporary di rectory. 2. Run PTFFORM.EXE to expand the service pack files and copy them into an iSeries Access for Windows installation image directory, replacing any ex isting files. 3. Delete PTFFORM.EXE after it has completed its processing. Now you have combined this service pack level with the iSeries Access for Win dows installation image, so that users can install iSeries Access for Windows plus this service pack in one integrated step. Note that this procedure also works if the installation image has already been combined with a prior service pack level. This procedure will replace the prior service level in the combined image with this new level. Alternatively, if you have a full copy of the original iSeries Access for Win dows install image in a directory, you can combine PTFFORM.EXE with this full imag e, using the same 3-step procedure detailed above. Then you can run Create Tailored Installation Image (cwbinimg.bat) from this full image direct ory, to create tailored image directories that will automatically have the service pack merged in. 2.0 RESTRICTIONS ----------------2.1 iSeries SERVER FIXES -------------------------In addition to installing the iSeries Access for Windows Service Pack, all servers should stay current on the latest Cumulative PTF Package, HIPER G roup PTF, and Database Group PTF. Refer to IBM eServer iSeries Technical Support: Recommended fixes at

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 = SI10817 Build date = January 2004 --------------------------------REQUIRED PROGRAMS ----------------Non-APAR fixes. OPTIONAL COMPONENTS ------------------INCOMING REMOTE COMMAND ----------------------No fixes. iSeries NAVIGATOR ----------------APAR SE11922: CA400EXP-OPNAV-OUTPUT-INCORROUT TOP OF PDF FILE IS CUT OFF W Customer has an AFPDS SPLF with the following attributes PAGESIZE(66 132) DEVTYPE(*AFPDS) FNTCHRSET(CZ6200 T1V10037 8) PAGRTT (90). The top of the PDF file is cut off when the PDF file is generated through operations navigator. PDF file is not cut off when sent through infoprint server without using operations navigator. Copied spooled file now maintains all attributes of original spooled file. APAR SE12158: CA400EXP-OPNAV-INCORROUT CPD0082 IS RECEIVED BY CHANGING THE SCH EDULE DATE OF A J MSGCPD0082 is received by changing the schedule date of a job within a jobqueue. So expand workmanagement -> jobqueues -> active jobqueues -> open jobqueue where a job is in -> right click on this job and change the schedule date with format DMY -> MSGCPD0082 is reported. User profile Parameters: - LOCALE = *SYSVAL - SETJOBATR = *NONE - CCSID = *SYSVAL - STRSEQ = *SYSVAL System Values: - QLOCALE = /QSYS.LIB/EN_US.LOCALE - QSETOBJATR = *NONE - QCCSID = 65535 - QTIMSEP = 1 (:) - QDATFMT = DMY - QDATSEP = 1 (/) According to information center in the above situation the following information will be retrieved from the system values QCCSID, QTIMSEP, QDATFMT, QSRTSEQ, and QDATSEP. This is due to the fact that QSETOBJATR in the userprofile is set to *NONE. Here is an abstract from info center: "The date format is day/month/year (DMY).

This is because the user profile SETJOBATR parameter value was *NONE. The system search ended with the value for QDATFMT being used." This problem was caused by the date not being set in the correct format when the job's date format is DMY. A change is made to put the date in DMY order when changing these values through job properties. APAR SE12162: CA400EXP-OPNAV Navigator Can Crash on Fix Wizard Adding Fix When Management Central users select endpoints or system groups to perform fix activity, the users are prompted to enter fix information and press the add button. There can be times when this will cause the iSeries Navigator to crash. CIRCUMVENTION: This problem does not always occur, but when it does, it only occurs when the user selects systems or system groups to perform fix tasks. A circumvention to the problem would have the user find the specific fix in the inventory for a system and perform the task that way. So if the user wanted to install a particular fix on a system, instead of selecting the system, launching the install wizard, and then specifying the fix, the user could expand the fixes inventory for that system, find the particular fix, and launch the install wizard from there. If the user needs to perform that fix on several systems or system groups, the task could be done to one system, and then use the "Start Based On..." function against the task to run it again against each of the remaining systems that require the fix activity. APAR SE12164: CA400EXP-OPNAV Job monitor causes out of storage condition when monitoring QZRCSRVS jobs If a Management Central job monitor monitors a QZRCSRVS job for metrics "Job Status" or "Message Log", it can cause these jobs to continually get created on the server until an out of storage condition exists on the server. It may not be obvious that you have created a job monitor with these characteristics. For example, when creating a job monitor, the user could specify "All" for the job name on the General property page. If the user also selected "Available Metrics" on the Metrics page, they have created a "bad" monitor. CIRCUMVENTION: Do not create a job monitor specifying QZRCSRVS job on the General page and "Available Metrics" on the Metrics page. APAR SE12240: CA400EXP-OPNAV-UNPRED UNABLE TO SCHEDULE CHANGE TO VIRTUAL Unable to schedule change to virtual number of processors processor pool units will work, but virtual number of processors will not change. APAR SE12426: CA400EXP-OPNAV Snapshot or Create Fix Can Show Wrong Err Msg or Crash When Management Central users create a package definition, they can create a snapshot that is associated with that package. If the source system cannot be contacted when that snapshot is created or updated, the wrong error message is displayed. The incorrect error message reads: "Snapshot was not created or updated because the source system has an operating system level prior to V4R4M0." If the user is trying to generate a fix for a package, the user may see an error message "The fix could not be created or

updated at this time." The GUI can then crash. CIRCUMVENTION: If the error message "Snapshot was not created or updated because the source system has an operating system level prior to V4R4M0." is displayed, verify that a connection exists to the source system. APAR SE12610: Client Access iSeries Navigator System status appears greyed out When using iSeries Navigator (V5R2 or later), the System Status option is disabled (greyed out). It never becomes enabled. The option appears in the following places: 1.) System task pad 2.) System context menu 3.) Work Management task pad 4.) Work Management context menu 5.) Can be optionally added to the "My Tasks" task pad I've tried refreshing the display. I've tried navigating into Work Management to force a refresh. Nothing appears to work. The System Status menu option/icon is greyed out because we do not have a valid signon to the iSeries system. This option is not valid in early releases and we need a valid signon to determine what release iSeries we are connecting to. The code has been changed to force a signon, in all cases except when "System Status" appears in the "My Tasks" task pad. In this instance, after signing onto the system in question, the 'Refresh' button will enable the function. CIRCUMVENTION: This circumvention will only work in some instances. Expand the System tree. Expand the work management tree. Click on 'Active jobs'. This will force everything to be refreshed and the System Status menu item / task pad item will become active in some instances. APAR SE12695: CA400EXP-OPNAV-NETWORK-PERFM Duplicate MX records in DNS configu ration Duplicate MX records appear in BIND 8 DNS configuration that was migrated from BIND 4. The duplicate MX records will be removed the first time that the DNS configuration is saved after this PTF is applied. DATA ACCESS ----------DATA TRANSFER ------------DATA TRANSFER BASE SUPPORT -------------------------APAR SE12420: CA400EXP-DTRANSFER UPLOAD REQUEST LARGER THAN 4K RESULTS IN CWBTF0013 When a request size exceeds 4K (e.g. when a file with several fields is used), a CWBTF0013 error may occur. DATA TRANSFER EXCEL ADD-IN -------------------------Non-APAR fixes. ODBC

---APAR SE12051: CA400EXP-ODBC INTERNAL DRIVER ERROR WHEN USING COM+ Application uses R520 iSeries Access for Windows ODBC driver connected to OS400 R520 in a Microsoft COM-plus distributed transaction. The first attempt to enlist a new odbc connection in a distributed transaction may fail with internal driver error. The error occurs when a new odbc connection happens to be assigned the same handle as an earlier connection. The error is on the following API: SQLSetConnectAttr SQL_ATTR_ENLIST_IN_DTC=1207 A detail trace of the error will show: odbcmts.xaMapper.CreateRm Exit rc=30027. The error does not occur with R510 iAW. APAR SE12232: CA400EXP-ODBC-UNPRED MEMORY LEAK IN CLIENT ACCESS ODBC DRIVE The Client Access ODBC driver (cwbodbc.dll) does not deallocate memory after applications call the SQLGetInfoW function for SQL_DRIVER_VERSION. This affects Client Access versions 510 and 520. APAR SE12311: CA400EXP-ODBC-INCORROUT PROBLEMS WITH SYNONYM TYPE IN SQLTAB There are a couple of problems surrounding the use of the table type 'SYNONYM' on the SQLTables function with the iSeries Access ODBC dri ver. The first problem only occurs if an application calls the SQLTables function listing only a table type of 'SYNONYM' and there are no results to be returned. If the application binds result columns and tries to fetch the results, the ODBC driver returns an error, 'Invalid cursor state'. Instead it should return an error message MSGSQL0100, 'No results found' error. Additionally, if an application requests a table type of 'SYNONYM' and there are results, the iSeries Access ODBC driver returns tables of type 'TABLE' and 'ALIAS' instead of 'SYNONYM'. As a result of the same problem, if a table type of 'TABLE' or 'ALIAS' are specified, both ALIAS and TABLE types are returned. APAR SE13115: CA400EXP-ODBC-INCORROUT - FETCH PROBLEMS WITH PARTIAL BLOCKS When the ODBC client retrieves data from the server, there are some conditions where a full block of rows can not be retrieved. If that condition occurs, the ODBC driver is incorrectly returning partial rowsets back to the application. OLE DB PROVIDER --------------APAR SE11854: CA400EXP - OLEDB - INSERTING DBCS CHARS INTO UNICODE COLUMN CA/Express client connects to iSeries DB2/400 via IBMDA/400 (OLEDB). The table columns are Unicode (graphic w/CCSID 13488). When the user inserts DBCS characters into the last position in a column, the characters are replaced with garbage characters. .NET DATA PROVIDER -----------------Non-APAR fixes. LOTUS 123 FILE FORMAT SUPPORT ----------------------------No fixes. AFP WORKBENCH VIEWER -------------------Non-APAR fixes.

TOOLBOX FOR JAVA ---------------Includes JTOpen 4.2 (12/23/2003) and the equivalent of 5722JC1 SI11115. 5250 DISPLAY AND PRINTER EMULATION ---------------------------------APAR SE11237: CA400EXP-TERMEMUL DISPLAYING SUBFILES CONTAINING FIELDS DEFI Displaying subfiles containing fields defined as DSPATR(HI) and DSPATR(BL) causes PC5250 flickering problems. This occurs with PC5250 included in version 520 of CAExpress, but we noticed the same problem with PC5250 5.0 standalone version. No matter about version/release of OS/400. The problem does not ocur with different emulators and with local workstatio ns. It looks like PCOMM (XE1 version and standalone) is somewhat failing to correctly refresh the screen for blinking fields causing the subsequent no-blinking field to randomly flash/flicker. APAR SE11890: OSP-PAR ISERIES ACCESS FOR WINDOWS COPY AND PASTE WITH PC525 When using copy and paste with PC5250 and the clipbook, the same data is pasted in repeatedly even when new data is copied. APAR SE12600: CA400EXP-PC5250 SESSION HANG WITH HYPER THREADING CPU The user uses multiple 5250 sessions. When one session is closed with 'x' button, all other sessions hang. This problem occurs on a PC which supports Hyper threading CPU. When this problem occurs, the user has to end all PCSxxxxx processes to recover. PRINTER DRIVERS --------------AFP PRINTER DRIVER -----------------No fixes. SCS PRINTER DRIVER -----------------No fixes. OPERATIONS CONSOLE -----------------Non-APAR fixes. PROGRAMMER'S TOOLKIT -------------------HEADERS, LIBRARIES, AND DOCUMENTATION ------------------------------------No fixes. VISUAL BASIC WIZARDS -------------------Non-APAR fixes. JAVA PROGRAMMER'S TOOLS ----------------------No fixes. EZ-SETUP

-------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 (if the service pack was originally installed with the Enable Service Pack Uninstall option): 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 Change or Remove Programs button (if necessary), then find and click on the IBM iSeries Access for Windows SI10817 item, and then click on the Change/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 iSeries Access for Windows. The same tool is used for installing service packs. Setup.exe has a 2 minute timeout to initialize to the first wizard panel, which could expire when installing service packs over very slow communication lines. If installing from a CD or a faster connection is not possible, then the service pack could be installed in this manner: 1) A setting exists on the iSeries Access for Windows Properties Service tab that will copy the service pack image to the PC's temporary directory, install the service pack, then remove the copied files. To use this support you will need to specify this setting ("Copy install image to PC before installing"). 2) Run Check Service Level (either from the IBM iSeries Access for Windows Service folder shortcut or when Check Service Level runs at system boot on its defined schedule) STATUS: No status information is displayed while the files are copied. To determine if the transfers are progressing, look in the 'CA400CKV' temporary directory (beneath the PC temporary directory, for example C:\Documents and Settings\username\Local Settings\Temp). You should see new files appear periodically. 3) Proceed through the Service Pack install wizard to complete the install.

4.3 SERVICE PACK CONTROL ------------------------To prevent users from installing the Service Pack, an administrator can use the SP.TXT file. If the administrator places a file named SP.TXT (with a 'N' in the first position of the first line) in the service pack installation image directory, the service pack will not be installed. 5.0 DATA TRANSFER CONSIDERATIONS --------------------------------The following sections describe additional support or known problems that you may notice while using the Data Transfer function. 5.1 TRANSFERRING DATA WHEN THE FILE OR DATA CCSID IS 65535 ----------------------------------------------------------WHY DOES MY DATA LOOK LIKE GARBAGE WHEN I PERFORMED A DOWNLOAD? By default, the Data Transfer function will not convert data between EBCDIC and ASCII if the data is tagged with a CCSID of 65535. In older versions of the Win 95/NT Client Access product, the 65535 conversion was controlled by the CWBTFR.INI file. This process has been changed, and the conversion is now controlled by the Data Transfer user interface. Once the setting has been made in the user interface, it is then stored in the transfer request. This is only true for .TTO 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 iSeries 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 iSeries National Language Support Manual.