WebSphere MQ Workflow Version 3.4.0 - Service Pack #4 (December 2003) ---------------------------------------------------------------------- INDEX -------------------------------------------------------------- 1. Installing Service Pack #4 1.1 Installing on Microsoft Windows NT/2000/XP 1.2 Installing on IBM AIX 1.3 Installing on Sun Solaris 1.4 Installing on HP-UX 2. Important Notes 2.1 Applying Service Packs to the Web Client 2.2 Documentation error for Portal Client 2.3 No more automatic changes to the CLASSPATH environment variable 2.4 Database problems 2.5 Problems with the configuration checker fmczchk 2.6 Buildtime - Known problems, changes, hints and tips 3. New supported operating systems releases and database releases 3.1 IBM AIX V5.2 for PowerProcessor Chip 3.2 Sun Solaris V9 3.3 Oracle Database 9i Release 2 (9.2.0.1) on IBM AIX and SUN Solaris 3.4 Oracle Database 9i Release 2 (9.2.0.1) on HP-UX 3.5 Microsoft Windows 2003 3.6 Microsoft Terminal Server 4. Enhanced Oracle setup on IBM AIX, SUN Solaris and HP-UX 5. Changes 5.1 Changes in Service Pack #1 5.2 Changes in Service Pack #2 5.3 Changes in Service Pack #3 5.4 Changes in Service Pack #4 6. License Notices -------------------------------------------------------------- 1. Installing Service Pack #4 ============================= 1.1 Installing on Microsoft Windows NT/2000/XP ------------------------------------------------ 1.1.1 Which files must be downloaded? The service pack consists of several self-extracting and self-installing executables. There is one for each National Language version of IBM WebSphere MQ Workflow. To make the distribution of client updates easier, there are three types of self-extracting executables. They update Client, Buildtime, or full installations. The Client and Buildtime packages contain only certain WebSphere MQ Workflow components and they are only applicable if these components or a subset of these components are already installed. Use the full package to update installations that include more than these components. The Client package consists of the API Runtime Library, Program Execution Agent, Runtime Client, Lotus Notes API, Administration Utility, Samples, Java, and the Java Agent component. The Buildtime package includes just the Buildtime component and the associated samples. The following self-extracting executables are available: Full Package: ------------- W340ENA4.EXE - U.S. English language version W340CSA4.EXE - Simplified Chinese language version W340CTA4.EXE - Traditional Chinese language version W340DEA4.EXE - German language version W340ESA4.EXE - Spanish language version W340FRA4.EXE - French language version W340HEA4.EXE - Hebrew language version W340HUA4.EXE - Hungarian language version W340ITA4.EXE - Italian language version W340JPA4.EXE - Japanese language version W340KOA4.EXE - Korean language version W340NLA4.EXE - Dutch language version W340PBA4.EXE - Brazilian Portuguese language version W340PGA4.EXE - Portuguese language version W340PLA4.EXE - Polish language version W340TRA4.EXE - Turkish language version W340RSA4.EXE - Russian language version Client Package: --------------- W340ENC4.EXE - U.S. English language version W340CSC4.EXE - Simplified Chinese language version W340CTC4.EXE - Traditional Chinese language version W340DEC4.EXE - German language version W340ESC4.EXE - Spanish language version W340FRC4.EXE - French language version W340HEC4.EXE - Hebrew language version W340HUC4.EXE - Hungarian language version W340ITC4.EXE - Italian language version W340JPC4.EXE - Japanese language version W340KOC4.EXE - Korean language version W340NLC4.EXE - Dutch language version W340PBC4.EXE - Brazilian Portuguese language version W340PGC4.EXE - Portuguese language version W340PLC4.EXE - Polish language version W340TRC4.EXE - Turkish language version W340RSC4.EXE - Russian language version Buildtime Package: ----------------- W340ENB4.EXE - U.S. English language version W340CSB4.EXE - Simplified Chinese language version W340CTB4.EXE - Traditional Chinese language version W340DEB4.EXE - German language version W340ESB4.EXE - Spanish language version W340FRB4.EXE - French language version W340HEB4.EXE - Hebrew language version W340HUB4.EXE - Hungarian language version W340ITB4.EXE - Italian language version W340JPB4.EXE - Japanese language version W340KOB4.EXE - Korean language version W340NLB4.EXE - Dutch language version W340PBB4.EXE - Brazilian Portuguese language version W340PGB4.EXE - Portuguese language version W340PLB4.EXE - Polish language version W340TRB4.EXE - Turkish language version W340RSB4.EXE - Russian language version 1.1.2 Using the new Russian language support To use the Russian language support that is introduced with service pack 2, perform the following steps: 1. Install the English version of the base package using the installation CDs. 2. Switch the installation language in the installation profile to Russian by entering the following command at a command prompt : fmczchk -c inst:i,Language,RUS 3. Apply the service pack, as described in 1.1.3. 1.1.3 Installing the service pack 1. Make sure that you have stopped all running WebSphere MQ Workflow processes and services before installing the service pack. 2. In the Windows Explorer, double click on the executable for the package-language combination that you require. 3. After the program has unpacked the files to the temporary directory, the installation starts. 1.1.4 Upgrading your MQ Workflow configuration Because this package includes updated DB2 bind files, you have to bind the new files to your MQ Workflow Runtime databases as follows: 1. Open a DOS Command Prompt and run the configuration utility 'fmczutil' 2. Choose the configuration identifier of the configuration you want to update. 3. Select the 'r'for Runtime database menu, then 'b' for bind. All bindings are made for you. This can take several minutes. After you have performed these steps, your system is ready to run. You can restart your MQ Workflow services and processes again. 1.2 Installing on IBM AIX ------------------------- 1.2.1 Which files must be downloaded? Download the package wf340a4u.tar.gz (69 MB) and unpack the file to a temporary subdirectory. You need approximately 132 MB to unpack the file. To create the update installation images, unpack the downloaded file using the command: gzip -dc wf340a4u.tar.gz | tar -vxf - 1.2.2 Installing the service pack 1) Stop all running WebSphere MQ Workflow processes, for example, by shutting down the WebSphere MQ Workflow system using the administration utility "fmcautil". 2) As root, perform the command 'slibclean'. 3) Update your WebSphere MQ Workflow 3.4.0.x installation (with or without hotfixes applied) using smit - "update to latest level" to level 3.4.0.40. Note: Your configuration (profiles, /var/fmc/...) will not be modified by the update. However, the installation profile /usr/lpp/fmc/fmcrc will be updated to reflect the new level "ServiceLevel=4". 4) If you use DB2 as runtime database, you have to bind the new files to your MQS Workflow Runtime databases, because this package includes updated DB2 bind files, as follows: a. As user "fmc", invoke the configuration utility 'fmczutil' b. Select the configuration identifier of the configuration you want to update. c. Select 'r' for Runtime database menu, then 'b' for bind. All bindings will be made for you. This can take several minutes. After you have performed these steps, your system is ready to run. You can restart your queue manager, the trigger monitor, and the administration server as usual by invoking the following programs: strmqm FMCQM & runmqtrm -q FMCTRIGGER -m FMCQM & fmcamain & 1.2.3 Using the new Russian language support The Russian language support message file is automatically added starting with service pack 2. To switch the Workflow language settings use the procedures described in Appendix D of the Installation Guide: 1. Change the system language code by using export LANG=ru_RU 2. Switch the installation language in the Workflow installation profile to Russian ("rus"). To do this, enter the following command at a command prompt: fmczchk -c inst:i,Language,rus Optionally, you can edit the file /usr/lpp/fmc/fmcrc. 1.3 Installing on SUN Solaris ----------------------------- 1.3.1 Which files must be downloaded? Download the package wf340s4u.tar.gz (49 MB) and unpack the file to a temporary subdirectory. You need approximately 172 MB to unpack the file. To create the update installation image, unpack the downloaded file using the command: gzip -dc wf340s4u.tar.gz | tar -vxf - For a client-only installation, use the file wf340s4c.tar.gz (16 MB), which needs about 54 MB to unpack. 1.3.2 Installing the service pack 1) Stop all running WebSphere MQ Workflow processes, for example, by shutting down the WebSphere MQ Workflow System using the admin utility "fmcautil". Make sure that all WebSphere MQ Workflow processes are stopped and there are no product files in use. 2) Update your WebSphere MQ Workflow 3.4.0.x files (with or without having hotfixes applied) to level 3.4.0.40: Issue the following command line as user "root", replacing the path "/tmp/fmc340u4.pkg" from this example with the fully-qualified path and filename of your ".pkg" file: pkgadd -d /tmp/fmc340u4.pkg (full package) or pkgadd -d /tmp/fmc340u4cl.pkg (client package) Accept the installation of this package and overwrite files from the previous package 3.4.0.x. Note: Your configuration (profiles, /var/fmc/...) will NOT be modified by the update. However, the installation profile /opt/fmc/fmcrc will be updated to reflect the new level "ServiceLevel=4". 3) Full installation package only: If you use DB2 as runtime database, you have to bind the new files to your MQ Workflow Runtime databases, because this package includes updated DB2 bind files, as follows: a. As user "fmc", invoke the configuration utility 'fmczutil' b. Select the configuration identifier of the configuration you want to update. c. Select 'r' for Runtime database menu, then 'b' for bind. All bindings will be made for you. This can take several minutes. After you have performed these steps, your system is ready to run. You can restart your queue manager, the trigger monitor, and the administration server as usual by invoking the following programs: strmqm FMCQM & runmqtrm -q FMCTRIGGER -m FMCQM & fmcamain & 1.3.3 Using the new Russian language support The Russian language support message file is automatically added starting with service pack 2. To switch the Workflow language settings use the procedures described in Appendix D of the Installation Guide: 1. Change the system language code by using export LANG=ru 2. Switch the installation language in the Workflow installation profile to Russian ("rus"). To do this, enter the following command at a command prompt: fmczchk -c inst:i,Language,rus Optionally, you can edit the file /opt/fmc/fmcrc. 1.4 Installing on HP-UX ----------------------- 1.4.1 Which files must be downloaded? Download the package wf340h4u.tar.gz (57 MB) and unpack the file to a temporary subdirectory. You need approximately 60 MB to unpack the file. To create the update installation images, unpack the downloaded file using the command: gzip -dc wf340h4u.tar.gz | tar -vxf - For a client-only installation, use the file wf340h4c.tar.gz (15 MB), which needs about 16 MB to unpack. 1.4.2 Installing the service pack 1) Stop all running WebSphere MQ Workflow processes, for example, by shutting down the WebSphere MQ Workflow system using the administration utility "fmcautil". Make sure that all WebSphere MQ Workflow processes are stopped and there are no product files in use. 2) Update your WebSphere MQ Workflow 3.4.0.x files (with or without having hotfixes applied) to level 3.4.0.40 as follows: a. Install the new package using 'sam'. If you prefer, you can use 'swinstall' with the appropriate command-line parameters. b. Select the "software" icon. c. Select "add software to local host". d. Choose 'installation from disk'. e. To install the client-only package, enter the fully-qualified path to the file "FMC340U4CL.PKG" and the filename itself. f. To install the full package, enter the fully-qualified path to the file "FMC340U4.PKG" and the filename itself. g. Choose "Install" from the "Actions" pulldown menu and confirm twice. h. After the installation proceed with step 3. Note: Your configuration (profiles in /var/fmc/...) will NOT be modified by the update. 3) Run the command fmczinsx -o upd to update the installation profile /opt/fmc/fmcrc with the new level "ServiceLevel=4". This value reflects the current service pack level of the installation. 3) Full installation package only: If you use DB2 as runtime database, you have to bind the new files to your MQ Workflow Runtime databases, because this package includes updated DB2 bind files, as follows: a. As user "fmc", invoke the configuration utility 'fmczutil' b. Select the configuration identifier of the configuration you want to update. c. Select 'r' for Runtime database menu, then 'b' for bind. All bindings will be made for you. This can take several minutes. After you have performed these steps, your system is ready to run. You can restart your queue manager, the trigger monitor, and the administration server as usual by invoking the following programs: strmqm FMCQM & runmqtrm -q FMCTRIGGER -m FMCQM & fmcamain & 1.4.3 Using the new Russian language support The Russian language support message file is automatically added starting with service pack 2. To switch the Workflow language settings use the procedures described in Appendix D of the Installation Guide: 1. Change the system language code by using export LANG=ru_RU.iso88595 2. Switch the installation language in the Workflow installation profile to Russian ("rus"). To do this, enter the following command at a command prompt : fmczchk -c inst:i,Language,rus Optionally, you can edit the file /opt/fmc/fmcrc. 2. Important Notes ================== 2.1 Applying service packs to the Web Client -------------------------------------------- It is recommended that you have a separate configuration for the Web Client. This way, you can easily apply service packs to the Web Client as follows: 1. Install the WebSphere MQ Workflow service pack. 2. Back up the Web Client files that you have changed (for example, \installedApps\MQWFWebClient_\cfgs or \installedApps. This is because the complete subtree of your old Web Client configuration will be deleted in the next step. 3. Delete the Web Client configuration using the configuration utility 'fmczutil'. 4. Remove the Web Client's application server in WebSphere. If you are using WebSphere Version 4, you must remove the Web Client enterprise application before you can remove the application server. 5. Create a new Web Client configuration. 6. Merge the changes you made with the new Web Client files. This includes re-installing the samples for the Web Client, such as the AuditTrailHandler and the Groupworklist sample. NOTE: For the AuditTrailHandler, the Web Client needs Xalan-Java 2, which is available from http://xml.apache.org/xalan-j It is recommended that you delete the temporary directory that you created for the compiled JSPs of the Web Client on your application server. When using IBM WebSphere V3, this temporary directory is \temp\\MQWFClient-, for example, d:\WebSphere\AppServer\temp\default_host\MQWFClient-WEBC. When using IBM WebSphere V4, this temporary directory is \temp\\WebClient_Server_-_. When using IBM WebSphere V5, this temporary directory is \temp\\\MQWF_Web_Client_\ fmcohcli.war\forms\. If you want to use https in WebSphere 4.0.2, set the system properties under jvm settings. Set the property 'java.protocol.handler.pkgs' to the value 'com.ibm.net.ssl.internal.www.protocol'. For further update details, see the WebSphere documentation. 2.2 Documentation error for Portal Client ----------------------------------------- Installation Guide, Appendix H, page 411, parts 1a and 3g refer to the Portal Client WAR file as 'MQWFPortalClient.war'. This is incorrect, the actual file name is 'fmcopcli.war'. 2.3 No more automatic changes to the CLASSPATH environment variable ------------------------------------------------------------------- Before service pack 2, the installation of a service pack updated the CLASSPATH variable to contain the latest version of the MQ Workflow JAR file. Starting with service pack 2, you must update the CLASSPATH manually to switch to the latest version. This is to prevent breaking existing Java client configurations. The latest JAR files can be found in \bin\java340 where is the number of the service pack. It is recommended that you add "fmcojagt.jar" to the CLASSPATH. If you have a thin installation, where "fmcojagt.jar" is not installed, then you must add "fmcojapi.jar". 2.4 Database problems --------------------- 2.4.1 DB2 Version 8 If you use DB2 Version 8.1, make sure that you have installed the fix for DB2 APAR IY39361. 2.4.1.1 DB2 Version 8 on Sun Solaris On Sun Solaris, there is a known problem in the setup of the XA communication. IY41550 is the corresponding DB2 APAR number. As long as there is no fix available, the SQL error 998 with a reason code of 09 and a subcode of 02 might occur. You must make sure that the value of the database manager configuration variable "tp_mon_name" is set to "mq" (rather than mqmax). The DB2 instance owner can set this configuration parameter using the following command: db2 update dbm cfg using tp_mon_name mq Furthermore, the Websphere MQ Series library directory has to be checked for the existence of a library or link named "libmqmax.so". If neither the link nor the library exists, then the link can be created by the MQ installation owner using the following command: ln -s /opt/mqm/lib/libmqmax.so /opt/mqm/lib/libmqmax.a 2.4.2 Oracle Database 8i Release 3 (8.1.7) Make sure that you have installed Oracle 8i patchset 8.1.7.1, or higher. With earlier versions of the Oracle DBMS, the runtime servers do not start. On AIX, do not use Oracle 8i patchset 8.1.7.2. 2.5. Problems with the configuration checker fmczchk ----------------------------------------------------- When you use the fmczchk utility to check a server configuration, it might display the error message: FMC34032E: Cannot load TP Monitor library mq.dll: The specified module could not be found (rc = 126). Erroneously, the utility checks for mq.dll (or libmq.a|.so|.sl) instead of mqmax.dll. If you receive this message, check that the mqmax library (for Windows mqmax.dll, for AIX libmqmax.a, for Solaris libmqmax.so, and for HP-UX libmqmax.sl) exists, is accessible and loadable. If so, you can ignore the error message. 2.5.1 Wrong information when running with Microsoft Windows 2003 When using the configuration checker on the operating system Windows 2003 it might display the error message: FMC34032E: Cannot load VB Runtime library msvbvm50.dll: The specified module could not be found (rc = 126). Erroneously, the utility checks on this operating system for the for Windows 2000 necessary library msvbvm50.dll instead of the actual msvbvm60.dll. If you receive this message, check that the actual library msvbvm60.dll exists, is accessible and loadable. If so, you can ignore the error message. Furthermore, the checker utility might display the information message: FMC34101I: The Operating System is Windows 2000 5.02. This leads to no problems but must be recognized, when investigating the checker log file. 2.6 Buildtime - Known problems, changes, hints and tips --------------------------------------------------------- 2.6.1 Refreshing objects tree in Buildtime If you use Buildtime with an MS Jet database, occasionally the objects tree does not refresh properly when you add new objects, such as persons or roles. The problem is caused by the Microsoft Jet database engine and, at the moment, there is no fix available from Microsoft. You can force to refresh objects by selecting the Buildtime menu item, then click 'Refresh Buildtime'. 2.6.2 Problem importing large FDL files into Buildtime When importing large FDL files into Buildtime, Buildtime appears to interrupt the operation before the process finishes. Reasons for the interruption can be: 1. DB2: The tablespace fills up, which causes DB2 to interrupt. This problem has been addressed with APAR IX76273 for DB2 UDB, which has been fixed in DB2 UDB V.5.2. The problem occurs both with database-managed tablespaces and with system-managed tablespaces. The Buildtime database uses system-managed tablespaces. 2. Microsoft Jet engine: The Jet engine creates temporary files on the C drive (for example, jet1855.tmp). If there is not enough space available on the C drive (temp directory), the system runs out of space. 150 MB free space is recommended. You can solve the problem as follows: - If the process does not show any change in CPU time, end the fmcbmain.exe using the task manager. - Split the FDL file into smaller files and import them individually. Following is an example of an FDL file with a size of 2 MB: - 850 persons - 30 roles - 25 organizations - 100 programs - 30 data structures - 80 processes with - 700 activities - 8000 activity container default values - 1800 data mappings plus everything else that belongs to the processes For this scenario, the temporary jet engine file can grow up to a size of 50 MB. 2.6.3 Possible error messages during Buildtime installation If you are running IBM AntiVirus, you might get an InstallShield error message with error code -115 during the installation of the ODBC components. Make sure to stop the NT Service called "AvService" before you start the installation. If you encountered the error already, cancel the MQ Workflow installation, stop AvService, then rerun the MQ Workflow installation. This error also happens with Norton AntiVirus. 2.6.4 Error in Microsoft Jet Database (Buildtime) Using a vertical bar (|) in a name (Datastructure, Datastructure member, etc.) leads to an ODBC error when Buildtime is used with an MS Jet database. For this problem there is already an entry in the Microsoft Knowledge Base: ------------------------------------------------------------ BUG: Use of Vertical Bar (|) Generates Syntax Error Last reviewed: September 9, 1996 Article ID: Q124316 The information in this article applies to: Microsoft Open Database Connectivity Version 2.0 BUG# QJET: 11 (2.00.2317) SYMPTOMS When you use a SELECT, INSERT, UPDATE, or DELETE queries with a vertical bar (|) contained in a character string, you receive an error that there is a syntax error in string in query expression. For example, consider a table test created as follows: CREATE TABLE test (t text(20)) Then use any of the following command: INSERT INTO test VALUES('|') DELETE FROM test WHERE t='|' UPDATE test SET t='|' This returns an error, with SQLSTATE=S1010 and szErrorMsg="[Microsoft][ODBC Access 2.0 Driver] Syntax error in string in query expression". STATUS Microsoft has confirmed this to be a problem in the ODBC Access Driver Version 2.00.2317. Further investigation into the problem is needed and new information will be published in the Microsoft Knowledge Base as soon as it becomes available. ------------------------------------------------------------------------ Additional reference words: 2.00.2317 ODBC MFC MSVC VISUAL C++ Windows NT KBCategory: kbprg KBSubcategory: Last reviewed: September 9, 1996 Copyright 1998 Microsoft Corporation. All rights reserved. Terms of Use. ------------------------------------------------------------------------ 3. New supported operating systems releases and database releases ================================================================= 3.1 IBM AIX V5.2 for PowerProcessor Chip ----------------------------------------- Starting with service pack 2, IBM AIX Version 5.2 can be used. Install the product on IBM AIX 5.2 and follow the IBM AIX installation steps for the service pack. If you choose to install Maintenance Level 01 of AIX 5.2 (5200-01), be sure to also install the latest CRITFIX030x updates. At the time of writing, the following were available on top of 5200-01: IY45484 - CRITICAL FIXES FOR AIX 5.2 AS OF JUNE 2003 CRITFIX0306 IY47002 - CRITICAL FIXES FOR AIX 5.2 AS OF JULY 2003 CRITFIX0307 IY47783 - CRITICAL FIXES FOR AIX 5.2 AS OF AUGUST 2003 CRITFIX0308 3.2 Sun Solaris V9 ------------------ Starting with service pack 2, SUN Solaris 9 can be used. Install the product on SUN Solaris V9 and follow the SUN Solaris installation steps for the service pack. 3.3 Oracle Database 9i Release 2 (9.2.0.1) on IBM AIX and SUN Solaris --------------------------------------------------------------------- Starting with service pack 2, Oracle 9.2.0.1 can be used as the runtime database for WebSphere MQ Workflow on IBM AIX and SUN Solaris. Make sure that you have installed Oracle 9i Release 2. Before you can use this database version in a new configuration, you must set the environment variable 'FMC_CFG_RT_DBVERSION' to '9.2' and then start the configuration utility fmczutil to create a new configuration. 3.4 Oracle Database 9i Release 2 (9.2.0.1) on HP-UX --------------------------------------------------- Starting with service pack 3, Oracle 9.2.0.1 can be used as the runtime database for WebSphere MQ Workflow on HP/UX. Make sure that you have installed Oracle 9i Release 2. Before you can use this database version in a new configuration, you must set the environment variable 'FMC_CFG_RT_DBVERSION' to '9.2' and then start the configuration utility fmczutil to create a new configuration. 3.5 Microsoft Windows 2003 --------------------------- Starting with service pack 3, Windows 2003 can be used. Install the product on Windows 2003 and follow the installation steps for the service pack in "1.1 Installing on Microsoft Windows NT/2000/XP". Note: To run the server component of IBM WebSphere MQ Workflow, install the lasted CSD for WebSphere MQ, namely v5.3 CSD 4. 3.6 Microsoft Terminal Server ------------------------------ Starting with service pack 3, when using the Windows 2000 or Windows 2003 server product, the Microsoft Terminal Server can be used to install the IBM WebSphere MQ Workflow Server and Client components. 4. Enhanced Oracle setup on IBM AIX, SUN Solaris and HP-UX ---------------------------------------------------------- Some enhancements for using Oracle as the runtime database were added in service pack 3. Key changes: - create the Runtime database in an existing Oracle SID - enhanced three-tier setup For a detailed description of these enhancements, refer to the documentation in the "OracleEnhancements.html" file provided with this package. After applying the service pack, this file is located in the 'doc' subdirectory of the MQ Workflow installation directory. 5. Changes ========== Service pack 4 includes all the changes that were made in previous service packs. 5.1 Changes in Service Pack #1 ------------------------------ The following problems are fixed: Nr. PMR/APAR Description 17991 Canceling the suspending of a process instance makes list portlet unusable 18007 fmczchk on UNIX: Warning is displayed (default port 5010 not found) 18184 Some actions from PropertiesView are not executed 18318 Web Client Logon screen: German Language, Umlaut not shown correctly 18332 Question mark appended at process instance name 18363 Error with XML-Msg via SDDS together with MQ531beta 18451 IY39345 FMCZUTIL does not allow 8 character SIDs 18456 IY39437 System Log and Error Log are not deleted automatically. Depending on the FDL settings MESSAGE_RETAIN_PERIOD and ERROR_RETAIN_PERIOD, system log entries and error log entries in the MQWF runtime database are now deleted automatically by the administration server. 18467 IY39760 Rounding problems with float/string conversion 18468 IY39759 Expiration and Notification are not updated with ForceRestart 18472 IY39717 Web Client with JNDI Locator Policy and a remote JNDI Name Service does not work 18477 PMR49020 FMC00100E Internal Error on Workitem::Transfer() call 18486 IY39929 Creating MQWF databases using raw devices (remote) not possible 18507 Buildtime: No Mapping possible. Pressing OK leads to FMCKRequire 18518 PMR31252 An MQWF EXE Server address space controlled by WLM was not terminated 18542 Web Client: 'Suspend Instance' year field cannot be left empty 18543 Remove of deadlocks in a scenario with parallel processing of scheduling and cleanup server. Remove of deadlocks in scenarios with high workload and parallel processing of QryWorkItem and Checkout/CheckinWorkitem. 18544 IY40460 FMCEMAIN fails with FMC12250E error in FMCSYS.LOG when for example refresh on a process instance is called by a user who is not authorized. 18545 Use "MQ" instead of "mqmax" as TP_MON_NAME 18546 Unattended (default) configuration is not DB2 V8 enabled 18559 LDAP Bridge, sample command runbr on UNIX, z/OS: The parameter handling of this command file was not correct. 18587 IY41141 Allow Cookie ID different from JSESSIONID 18596 HP-UX: Configuration switch for Oracle or MQServer fails 18600 BufferPool not customizable in DB2 part 18608 IBM Java 1.4 RTE is not found by Workflow 18622 Transfer item in Portal Client does not work 18623 Web Client does not work with SupportPac WA82 18639 Error pages are not working correctly in Web Client 18657 Empty directory \bin\JAVA3401 if config Web Client WAS4.x/5.0 18658 IY41977 Queries with multiple GDC tables in order statement 18666 PQ72169 Long and Float constants in "IN" predicate of filter strings in queries 18668 Configuration Win: Registry contains a corrupted path for fmcerr.log\fmcsys.log 5.2 Changes in Service Pack #2 ------------------------------ The following problems are fixed: Nr. PMR/APAR Description 17583 A new MQWF SP modifies a System classpath wrong. 18140 Additional support for Oracle 9i Release 2 (9.2.0.1) 18578 IY41133 PEA GIVES CORE WITH LARGE NUMBER OF AUTO ACTIVITIES 18584 IY41200 Admin server shutdown on codepage conversion error. 18591 IY41159 When deploying the WebClient within WebSphere 4.0 using a name service port other than 900, fmczutil fails with "FMC33993E Failed to execute the file 'GenPluginCfg.sh ..." 18601 IY41136 When adding a WebClient to a configuration, the advanced configuration wizard shows "FMC33843E Incorrect Java Agent Cycle 0" 18630 Provide Russian translation for WebClient 18635 IY42398 On Microsoft Windows NT/2000/XP all servers terminate after a database deadlock. 18661 IY41930 Fmczutil aborts configuration after saving the profile when specifiyng an invalid path for the channel definition table. 18664 IY39472 FMCZCHK REPRESENTS XAOPENSTRING INCORRECTLY 18665 IY42006 MQWFPORTALCLIENT.WAR IN APPENDIX H SHOULD BE FMCOPCLI.WAR 18707 Honor MQMD report options for XML input queue 18718 LDAP Bridge: Forward references for PERSON not handled correctly 18723 Cleanup PortalClient.properties 18745 PQ73201 CLIENT API CHANGES ON HOST 390 - CALL SERVICE FOR DETAILS 18779 Support of WPS 4.2 18780 Potential security issue in Web Client 18790 IY43908 On Solaris: password prompt of fmcautil and fmcibie truncates passwords to 8 characters 18793 PMR50519 FMCHEPRO does not contain all API modules (CICS) 18805 IY43934 FMC21913E during verify with asynchronous UPES in blocks 18825 Can't find resource bundles for Web Client samples 18886 WebClient NullPointerException in servlet.log if no custom CommandHandler is enabled 18894 PQ74477 Profile or keyword in profile not found (RC=124) in CICS 18908 IY44826 WEBCLIENT'S SESSIONCONTEXT OBJECT GETS CORRUPTED 18929 IY45044 Create or query a persistent list may return FMC_ERROR_DYNAMIC_QUERY_SIZE_TOO_LONG RC=141) even, if the persistent query works fine in the past. 18950 IY45198 Web application aborts on SUN Solaris. 18951 IY45203 Long DBCS process names truncated incorrectly 18975 IY45519 API call UserSettings() on the service object returns RC=100 on clients before V340, if the server is V340. Set a new profile variable on the server to allow back-level clients to connect to a server with 3.4. without the RC=100 error. With the fmczchk utility, you can change your profile. You need to change all server profiles with back-level clients, if this API is used. The following example sets the needed profile variable for the configuration ID FMC. "fmczchk -c inst:m,FMC_BEHAVE_LIKE_332,1 -yFMC" 18987 IY45592 Global container mapping within subprocesses is not performed 5.3 Changes in Service Pack #3 ------------------------------ The following problems are fixed: Nr. PMR/APAR Description 18795 IY44083 Replace confusing error message of fmczchk utility, when the db2instance environment variable is different to the instance to use for runtime database 18905 PQ74550 Incorrect handling of floating point values on z/OS through Java API 18983 IY45465 WebClient can be deployed to WAS5 default server only 18991 LDAP Bridge: Some generated FDLs containing roles and related people cannot be imported 19006 fmczbstr fails using a Runtime database alias longer than 8 characters 19019 Enhance Oracle setup for remote databases 19028 IY45998 Cannot shutdown PEA with version < 3.2.0 19042 PQ76346 GDC creation on z/OS: Error condition not handled correctly 19082 PMR29000 Improve tracing of C Authentication Exit 19087 IY46077 Multi threading problems in JAVA API on SUN Solaris causing abends of the AppServer 19141 IY46585 Deletion of large numbers of sys and error log entries blocks fmcamain 19154 IY47814 MQWF does not start with certain trace settings 19163 IY46486 Comm. Error (RC=13) on client after recovering from MQ outage 19209 IY47557 Empty activities may cause crash of execution server 19233 Support of Oracle 9i on HP/UX 19263 IY46969 No syntax checking done for user ids returned with Authentication Exit 19266 Empty activities must have at least one positively evaluated outgoing control connector 19275 WMQWF Web Client now shows a link on error pages providing easy access to E-support entries related to the error 19281 IY47023 Locale-specific decimal point not accepted in XML interface 19285 IY47108 RTRecycleThreshold is not working correctly 19300 IY47151 Deadlocks with parallel ObtainProcessMonitor and ProcessNavigation transactions 19340 IY47440 Transfer item in WMQWF Portal Client results in file not found exception. Also fixes problem of 'select' action in MQWFActionPortlet setting portlet to 'not used' view. 19375 IY47814 Intermittent SIGSEV 11 on SUN Solaris when using the Java API in an AppServer environment 19397 PQ77671 Cleanup server fails with SQLCODE -104 19408 PQ77818 Do not use WIH header in TerminateReceive() API calls on distributed platforms. 19439 IY47834 Execution server does not shutdown in case of MQSevereException (e.g. audit trail queue full) 19452 Apply new XML4C V5.3 to MQWF V3.4 19508 IY48343 Deletion of large numbers of sys and error log entries blocks fmcamain for Oracle 19518 fmczccd aborts with Exception = c0000005 19519 IY48507 fmczddba must grant permissions for bind package fmcpqe23 5.4 Changes in Service Pack #4 ------------------------------ The following problems are fixed: Nr. PMR/APAR Description 19558 IY48556 If the runtime database user is a different account than the runtime database administrator, the cleanup server and scheduling servers abend with SQL code -551. 19604 Improve Error reporting for authentication exit 19613 IY48819 OnCTRLColumnOrderChanged Exception after removing a column in standard runtime client 19616 fmczacfg: WebClient can be deployed to WAS5 default server only 19660 IY48694 Notification time is reset by cancel checkout. 19666 IY49073 Oracle db alias not found when listed lowercase in tnsnames.ora 19684 IY49161 MQ REPORT OPTIONS NOT PROCESSED ON XML STARTPROCESS RESPONSE The following MQSeries Report Options from the Message descriptor of incoming XML messages are now honored: MQRO_NEW_MSG_ID MQRO_PASS_MSG_ID MQRO_COPY_MSG_ID_TO_CORREL_ID MQRO_PASS_CORREL_ID The Message/Correl ID setting in the outgoing XML (reply) message is according to the setting of these values. 19694 fmczchk: Visual Basic V6 not handled correctly 19708 Empty activities cause fmcemain to abend 19722 Remove import warning for empty activity 19729 Java Authentication Exit, improve tracing 19768 Syscom Set Second User in audit trail for second notifcation and process notification 19769 Leading underscore for structure names is now also accepted in the MQWF XML API 19772 IY49555 Increase stack size for FDL parser to import larger FDL files. 19774 Admin utility abends when browsing the hold queue 19784 IY49556 Admin Server Crash if Error Retention is time and System Log Retention is not a time interval 19805 IY49615 Oracle: Queries on e.g. work items using a threshold and a sort criteria returns not the sorted top values, it returns threshold values sorted. 19845 IY49681 Subprocesses of iterated blocks are not deleted 19929 PQ80172 Wrong navigation when empty activities do not have valid control connectors. 20008 Updated installation instructions for the Web Client on z/OS 20093 IY50417 If cleanup server and scheduling server are on different systems, cleanup server abends with SQL code 100 after installing service pack 3. 20146 IY50671 Expiration of blocks does not work after installing service pack 3. 20180 IY50421 For Oracle, parallel subprocesses might not terminate if parent process is terminated. 6. License Notices ================== This product internally uses the XML4C parser and therefore is obliged to distribute the following license text: --------------------------------------------------------------------- * The Apache Software License, Version 1.1 * * * Copyright (c) 1999 The Apache Software Foundation. All rights * reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright * the documentation and/or other materials provided with the * distribution. * * 3. The end-user documentation included with the redistribution, * if any, must include the following acknowledgment: * "This product includes software developed by the * Apache Software Foundation (http://www.apache.org/)." * Alternately, this acknowledgment may appear in the software itself, * if and wherever such third-party acknowledgments normally appear. * * 4. The names "Xerces" and "Apache Software Foundation" must * not be used to endorse or promote products derived from this * software without prior written permission. For written * permission, please contact apache@apache.org. * * 5. Products derived from this software may not be called "Apache", * nor may "Apache" appear in their name, without prior written * permission of the Apache Software Foundation. * * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * ==================================================================== * * This software consists of voluntary contributions made by many * individuals on behalf of the Apache Software Foundation and was * originally based on software copyright (c) 1999, International * Business Machines, Inc., http://www.ibm.com. For more * information on the Apache Software Foundation, please see * . */ --------------------------------------------------------------------- ICU License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1995-2001 International Business Machines Corporation and others All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder. ---------------------------------------------------------------------- All trademarks and registered trademarks mentioned herein are the property of their respective owners.