MQSeries Workflow 3.2.2 - Service Pack #5 ----------------------------------------- INDEX ------------------------------------------ 1. Installation of Service Pack #5 1.1 Installation on IBM OS/2 1.2 Installation on Microsoft Windows 1.3 Installation on IBM AIX 1.4 Installation on Sun Solaris 1.5 Installation on HP-Unix 2. Important Notices 3. Changes 3.1 Changes in Service Pack #3 3.2 Change log ------------------------------------------ 1. Installation of Service Pack #5 =========================================== 1.1 Installation on IBM OS/2 ------------------------------------------- 1.1.1 Which files must be downloaded? The Service Pack consists of several self-extracting executables. One for each National Language version of IBM MQSeries Workflow. If you need to update another language than U.S. English ("ENU"), both the U.S. English language version and the language dependent version must be downloaded. Following the list of the self-extracting executables: O322ENU5.EXE - U.S. English language version including the common files of MQSeries Workflow O322CHS5.EXE - Simplified Chinese language version O322CHT5.EXE - Traditional Chinese language version O322DAN5.EXE - Danish language version O322DEU5.EXE - German language version O322ESP5.EXE - Spanish language version O322FIN5.EXE - Finnish language version O322FRA5.EXE - French language version O322HEB5.EXE - Hebrew language version O322HUN5.EXE - Hungarian language version O322ITA5.EXE - Italian language version O322JPN5.EXE - Japanese language version O322KOR5.EXE - Korean language version O322NLD5.EXE - Dutch language version O322NOR5.EXE - Norwegian language version O322PLK5.EXE - Polish language version O322PTB5.EXE - Brazilian Portuguese language version O322PTG5.EXE - Portuguese language version O322TRK5.EXE - Turkish language version 1.1.2 Unpack the files Copy the O322ENU5.EXE to a temporary directory and execute it using the command: O322ENU5 /D . This command unpacks the common files and the U.S. English files. If you need to update another language than U.S. English ("ENU"), you must copy the additionally downloaded file to the temporary directory and execute it by the command: O322xxx5 /D . where 'xxx' is the language abbreviation. 1.1.3 Update your existing MQSeries Workflow installation To install this Service Pack, use the Install & Maintain icon in your MQSeries Workflow folder. Note: First stop any running MQSeries Workflow programs. 1. Double-click on the MQSeries Workflow Install & Maintain icon 2. Select FILE from the menu bar. 3. From FILE select OPEN CATALOG. 4. Select DRIVE. 5. From the Drive list box, select the drive which contains the Service Pack. 6. Use the SEARCH button to search for the catalog file FMCZIxxx.ICF of the Service Pack. It is located in the subdirectory 'xxx' of the directory where you have unpack the downloaded executable. Note: 'xxx' is the language used also with the downloaded executable. 7. Press OPEN. 8. Select ACTION from the menu bar. 9. From ACTION, select UPDATE. 10. Select the UPDATE button. 11. Select if YES for Rollback or NO for No-Rollback Reboot the system to activate the changes done by the Service Pack installation. 1.1.4 Upgrading your existing MQSeries Workflow Configuration As updated DB2 bind files are included in this package, you have to bind the new files to your MQSeries Workflow runtime databases. For every configuration which involves the Runtime Database Utilities component on your system please invoke fmczrdb -y -o:b Now all bindings will be made for you. This may take several minutes. 1.2 Installing the Service Pack on Windows NT/2000/95/98 --------------------------------------------------------------------- 1.2.1 Which files must be downloaded? The Service Pack consists of several self-extracting and self-installing executables. One for each National Language version of IBM MQSeries Workflow. To make the distribution of client updates easier, there are three types of self-extracting executables to update Client, Buildtime or full installations, respectively. The Client and Buildtime packages contain only certain MQSeries Workflow components and they are only applicable if these components or a subset of these components are installed. Use the full package to update installations including more than these components. The Client package consists of the API Runtime Library, Program Execution Agent, Runtime Client, Lotus Notes Client, Admininstration Utility, Notes DB Templates, Samples, Java, CORBA Agent component. The Buildtime package includes Buildtime and Samples. Following the list of the self-extracting executables: Full Package: ------------- W322ENA5.EXE - U.S. English language version W322CSA5.EXE - Simplified Chinese language version W322CTA5.EXE - Traditional Chinese language version W322DAA5.EXE - Danish language version W322DEA5.EXE - German language version W322ESA5.EXE - Spanish language version W322FIA5.EXE - Finnish language version W322FRA5.EXE - French language version W322HEA5.EXE - Hebrew language version W322HUA5.EXE - Hungarian language version W322ITA5.EXE - Italian language version W322JPA5.EXE - Japanese language version W322KOA5.EXE - Korean language version W322NLA5.EXE - Dutch language version W322NOA5.EXE - Norwegian language version W322PLA5.EXE - Polish language version W322PBA5.EXE - Brazilian Portuguese language version W322PGA5.EXE - Portuguese language version W322TRA5.EXE - Turkish language version Client Package: --------------- W322ENC5.EXE - U.S. English language version W322CSC5.EXE - Simplified Chinese language version W322CTC5.EXE - Traditional Chinese language version W322DAC5.EXE - Danish language version W322DEC5.EXE - German language version W322ESC5.EXE - Spanish language version W322FIC5.EXE - Finnish language version W322FRC5.EXE - French language version W322HEC5.EXE - Hebrew language version W322HUC5.EXE - Hungarian language version W322ITC5.EXE - Italian language version W322JPC5.EXE - Japanese language version W322KOC5.EXE - Korean language version W322NLC5.EXE - Dutch language version W322NOC5.EXE - Norwegian language version W322PLC5.EXE - Polish language version W322PBC5.EXE - Brazilian Portuguese language version W322PGC5.EXE - Portuguese language version W322TRC5.EXE - Turkish language version Buildtime Package: ----------------- W322ENB5.EXE - U.S. English language version W322CSB5.EXE - Simplified Chinese language version W322CTB5.EXE - Traditional Chinese language version W322DAB5.EXE - Danish language version W322DEB5.EXE - German language version W322ESB5.EXE - Spanish language version W322FIB5.EXE - Finnish language version W322FRB5.EXE - French language version W322HEB5.EXE - Hebrew language version W322HUB5.EXE - Hungarian language version W322ITB5.EXE - Italian language version W322JPB5.EXE - Japanese language version W322KOB5.EXE - Korean language version W322NLB5.EXE - Dutch language version W322NOB5.EXE - Norwegian language version W322PLB5.EXE - Polish language version W322PBB5.EXE - Brazilian Portuguese language version W322PGB5.EXE - Portuguese language version W322TRB5.EXE - Turkish language version 1.2.2 Installing the Service Pack Make sure that you have stopped all running MQSeries Workflow processes before installing the Service Pack. Double click on the downloaded executable in the Windows Explorer. The program unpacks the files to the temporary directory and starts the installation right after unpacking. 1.2.3 Upgrading your existing MQSeries Workflow Configuration As updated DB2 bind files are included in this package, you have to bind the new files to your MQSeries Workflow runtime databases. For every configuration which involves the Runtime Database Utilies component on your system please invoke fmczrdb -y -o:b Now all bindings will be made for you. This may take several minutes. 1.2.4 Known Problems, hints and tips 1.2.4.1 Desktop seems to be corrupted after uninstalling MQ Workflow on Windows 98 Certain hardware setups lead to the following problem when you uninstall MQ Workflow on Windows 98: After uninstalling MQ Workflow, the Windows desktop shows black and white waved lines and several windows are not displayed properly. To solve the problem, reboot the computer. 1.3 Installation on IBM AIX --------------------------- 1.3.1 Which files must be downloaded? Please download the package wf322a5u.tar.gz (79MB) and unpack the file to a temporary subdirectory. You need approximately 200MB to unpack the file. 1.3.2 Installing the Service Pack 1) First, stop all running MQSeries Workflow processes, for example by shutting down the MQSeries Workflow System using the admin utility "fmcautil". 2) As root, perform the command 'slibclean'. 3) Update your MQSeries Workflow 3.2.2.x installation (with or without having hotfixes applied) using smit - "update to latest level" to level 3.2.2.50. 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=5". 4) As updated DB2 bind files are included in this package, you have to bind the new files to your MQSeries Workflow runtime databases. As user "fmc" invoke fmczutil and choose the configuration identifier of the configuration you would like to update. Then choose the 'r'untime database menu and select 'b'ind. Now all bindings will be made for you. This may take several minutes. After these steps your system is ready to run. You may 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 Installation on SUN Solaris ------------------------------- 1.4.1 Which files must be downloaded? Please download the package wf322s5u.tar.gz (32MB) and unpack the file to a temporary subdirectory. You need approximately 120MB to unpack the file. 1.4.2 Installing the Service Pack 1) First, stop all running MQSeries Workflow processes, for example by shutting down the MQSeries Workflow System using the admin utility "fmcautil". Make sure that all MQSeries Workflow processes are stopped and no file of the product is in use. 2) This is how to update your MQSeries Workflow 3.2.2.x files (with or without having hotfixes applied) to level 3.2.2.50: Issue the following command line as user "root", replace the path "/tmp/fmc-3.2.2-update.pkg" from this example with the fully qualified path and filename of your ".pkg" file: pkgadd -d /tmp/fmc-3.2.2-update.pkg accept the installation of this package and overwriting files of the previous package 3.2.2.x. Note: Your configuration(s) (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=5". 3) As updated DB2 bind files are included in this package, you have to bind the new files to your MQSeries Workflow runtime databases. As user "fmc" invoke fmczutil and choose the configuration identifier of the configuration you would like to update. Then choose the 'r'untime database menu and select 'b'ind. Now all bindings will be made for you. This may take several minutes. After these steps your system is ready to run. You may 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.5 Installation on HP-Unix --------------------------- 1.5.1 Which files must be downloaded? Please download the package wf322h5u.tar.gz and unpack the file to a temporary subdirectory. 1.5.2 Installing the Service Pack 1) First, stop all running MQSeries Workflow processes, for example by shutting down the MQSeries Workflow System using the admin utility "fmcautil". Make sure that all MQSeries Workflow processes are stopped and no file of the product is in use. 2) This is how to update your MQSeries Workflow 3.2.2.x files (with or without having hotfixes applied) to level 3.2.2.50: Use "sam" to install the new package. Use the "software" icon, and select "add software to local host". Then choose installation from disc and enter the fully qualified path to the file "FMC322U5.PKG" and the filename itself. Choose "Install" from the "Actions" pulldown menu and confirm twice. After installation you will be ready to go on with step 3. If you do not want to use sam, you can use "swinstall" with the appropriate command line parameters that suit your needs. Note: Your configuration(s) (profiles, /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=5". This value reflects the current service pack level of the installation. 4) As updated DB2 bind files are included in this package, you have to bind the new files to your MQSeries Workflow runtime databases. As user "fmc" invoke fmczutil and choose the configuration identifier of the configuration you would like to update. Then choose the 'r'untime database menu and select 'b'ind. Now all bindings will be made for you. This may take several minutes. After these steps your system is ready to run. You may 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 & 2. Important Notices =========================================== When using JDK 1.2 with security enabled together with the MQWF Java Agent using RMI, the following authorizations must be added to {java.home}/jre/lib/security/java.policy: grant codeBase "file:/e:/Program Files/MQSeries Workflow/bin/-" { permission java.net.SocketPermission "*:1024-", "accept, connect, listen, resolve"; }; Be sure to use the correct path for your MQWF installation in the codeBase attribute. 3. Changes =========================================== 3.1 Changes for Service Pack #3 ------------------------------ MQSeries Workflow now comes with a feature that makes sure that all server resources (e.g. memory) are freed regularily. The feature is enabled by setting the profile variable RTRecycleThreshold. This defines the maximum number of server transactions that a server instance performs before it frees its resources. The actual threshold is determined by a random threshold based on threshold defined in RTRecycleThreshold. Not setting the profile variable or setting it to 0 (or a negative number) disables this feature. You could enable this feature when you experience: o that memory consumption increases o that server performance decreases when servers are running for a long period e.g. weeks. The feature applies to the execution server, cleanup server and scheduling servers on distributed platforms. To make the changes active, it is necessary to update the IBM MQSeries Workflow profile fmcrc. In a default installatin and configuration, this file can be found in /var/fmc/cfgs/FMC. The keyword is: RTRecycleThreshold If you want to shutdown and restart a fmcemain every 1000 transactions, you need to specify fmczchk -c inst:m,RTRecycleThreshold,1000 Any fmcemain started after having specified this, will quit after 1000 transactions and then start a new one. 3.2 Change log ------------------------------ The following problems are fixed: Nr. PMR/APAR Desc. Service Pack #1 ----------------------------------------------------------------------- 13270 /390: Admin server terminates due to DB2 cancellation 13681 OS/2: Configuration checker does not show MQSeries CSD 4 13726 FMLConnectName not written when using fmczutil -k (client using MQ server API) 13750 Enable Runtime Client to be able to connect to different system groups simultanously 13754 /390: Enable change of LE Runtime Options 13808 /390: Multiple OID encoding support 13816 Errors in HTML code when exporting from Buildtime 13831 Migration utility fails for DBCS databases 13844 Wrong error message when setting filter in Runtime Client 13848 Admin server abends when client uses invalid code page 13865 175851LD Exceptions occur when running multithreaded API programs 13868 Migration fails if one or more container names reach 32 byte 13869 Logon/logoff takes more time when system was idle for more than 5 minutes 13876 Performance problem in case of invalid XML characters 13880 Unicode 2.0 is not properly handled by UnicodeConverter 13886 Cleanup server abends with protection exception after deadlock 13897 Migration utility does not work correctly under HP and Sun 13911 /390: Increased pathlength in PES 13941 Multiple network adapter takeover problem Service Pack #2 ------------------------------------------------------------------------- 13970 PMR 07543,519,000 XML response messages with array members 14014 Memory leak in ExecuteProcInst 14045 PES 0C4 if Backoutcount Exceeded 14078 Return additional info in case of communication errors. 14254 34920 EINTR error on semaphore calls 14255 Change exception handling of FML layer 13636 The API FmcjExeOptions:WindowStyle reports NOT_SET 13929 ProcessInstance.start2() crashes when using RMI and JDK 1.2.2 13932 Run of "fmctiqo -p" abends 13943 RMI-IIOP does not work with JDK 1.2 13961 The following parameters are no longer supported by MQSeries 5.2 13984 FmcFileSys::CanonicalDir does not work for root dir '/' on UNIX: 14012 IY13898 Admin utility shows wrong information about cleanup server 14027 fmczacfg: DB2 Connect panel does not allow to enter a UID (JPN) 14126 Memory leak when using containers and ActiveX 14144 Exception in Ctnr Element accessor when related Ctnr is deleted 14261 PQ43517 OS/390 XML interface problem with non English codepages 14236 Buildtime: Organization not saved in person after usage of "find" button 14292 ConfigID not found, if ServiceDisplayName is changed on Windows 2000 14322 FMC01100E Incorrect XML document is displayed although the document is correct Service Pack #3 ------------------------------------------------------------------------- 14818 fmczchk does not translate configuration ID to uppercase Therefore the configuration might not be found on UNIX 14965 fmczchk: AssertionException in Fmckstr PositionChar 14530 IY15338 Intermediate PEA cores on Unix due to SIGCHLD 14575 Build Time Japanese version: garbled characters on Windows 2000 e.g. in activity names 14846 Missing java run time in Xbootclasspath 14467 Memory Leak using UPES InvokeProgram 14476 PMR 91711 Memory leak using DATA DEFAULT connector 14518 PMR 91711 Memory leak in trace Context setter methods on SUN and HP 14797 Memory leak in XML out message 14401 Return MQSeries action code 'close' to API 14602 PMR 49884.499 Migration problem on AIX 14612 IY16621 Execution server shutdown performance enhanced 14809 PMR 01203 Provide module flow trace information for MQ transaction calls 14928 IY16881 FDL import problem 14349 Staffresolution problem causes an abend of the emain server Service Pack #4 -------------------------------------------------------------------------- 12585 -/pq49748 Cleanup server floods the execution server queue 14990 01203,057,649/- FmcDynPointer::Ensure potentially loops forever 15003 Link errors on HP-UX C++ binding 15018 Checker traps when reading qm.ini file 15066 Incorrect conversion from locl time to UTC (and v.v) in Windows 15075 35112,180,000/- Multithreading problems in web context on Unix 15080 01203,057,649/- Better stream protection against programming errors. 15085 Memory Leak in MQSeries C++ Binding classes 15093 Cannot import restarted processes 15107 Checker does not recognize 3.3 HF2 as SP1 15154 Codepage conversion: support SUN patch 107811-01 Service Pack #5 -------------------------------------------------------------------------- 15235 fmczchk does not check Database Profile for variable RR_TO_RS 15359 Wrong sorting of date in Runtime Client 15550 assertion with fmcibie - workaround via fdl possible 15637 workitem transfer can cause an assertion User A124653 logged on and wants to transer the Workitem to A222222. Second call of the API-method causes a stop of the two fmcemain servers. The Error-Log of the servers are showing: "FmcAssertionException, Condition=*** Pre-condition failed in e:\v321\src\fmcdsdf.inl<10347>: _ownerSystem.IsNull() != true""