MQSeries Workflow 3.2.1 - Service Pack #3 07/31/2000 ------------------------------------------------------- Installing MQSeries Workflow 3.2.1 - Service Pack #3 corresponds to upgrading to MQSeries Workflow 3.2.2 including HotFix #1. IMPORTANT: We strongly recommend to use the latest versions of the MQSeries Workflow books. You can obtain the latest copies via the Web from: http://www.ibm.com/software/ts/mqseries/library/mqpdfs.html INDEX ------------------------------------------ 1. Installation of Service Pack #3 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 Migrating data from a previous release 2. Important Notices 2.1 General 2.2 Java 3. Changes 3.1 Changes in Service Pack #1 3.2 Changes in Service Pack #2 3.3 Changes in Service Pack #3 ------------------------------------------ 1. Installation of Service Pack #3 =========================================== 1.1 Installation on IBM OS/2 ------------------------------------------- There is no service pack available for OS/2. You will need to deinstall your current version of MQSeries Workflow. Contact flowmark@de.ibm.com to get a 3.2.2 CD. 1.2 Installing the Service Pack on Windows NT, Windows 95 and Windows 98 ------------------------------------------------------------------------ 1.2.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 a language other than U.S. English ("ENU"), both the U.S. English language version and the language dependent version must be downloaded. Following is the list of the self-extracting executables: W321ENU3.EXE - U.S. English language version including the common files of MQSeries Workflow W321CHS3.EXE - Simplified Chinese language version W321CHT3.EXE - Traditional Chinese language version W321DAN3.EXE - Danish language version W321DEU3.EXE - German language version W321ESP3.EXE - Spanish language version W321FIN3.EXE - Finnish language version W321FRA3.EXE - French language version W321HEB3.EXE - Hebrew language version W321HUN3.EXE - Hungarian language version W321ITA3.EXE - Italian language version W321JPN3.EXE - Japanese language version W321KOR3.EXE - Korean language version W321NLD3.EXE - Dutch language version W321NOR3.EXE - Norwegian language version W321PLK3.EXE - Polish language version W321PTB3.EXE - Brazilian Portuguese language version W321PTG3.EXE - Portuguese language version W321TRK3.EXE - Turkish language version To make the distribution of client updates easier, there are two types of self-extracting executables to update Client and Buildtime installations. These packages contain only certain MQSeries Workflow components and they are only applicable if these components or a subset of these components are installed. 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. As with the all-including package you will need the U.S. English self extracting executable and the language dependent executable. The file name consists of the prefix W321 the package type prefix (that is, B for Buildtime and C for Client) the Language abbreviation and the service pack number, so the following executables are available Client Package: --------------- W321CEN3.EXE - U.S. English language version including the common files of MQSeries Workflow W321CCS3.EXE - Simplified Chinese language version W321CCT3.EXE - Traditional Chinese language version W321CDA3.EXE - Danish language version W321CDE3.EXE - German language version W321CES3.EXE - Spanish language version W321CFI3.EXE - Finnish language version W321CFR3.EXE - French language version W321CHE3.EXE - Hebrew language version W321CHU3.EXE - Hungarian language version W321CIT3.EXE - Italian language version W321CJP3.EXE - Japanese language version W321CKO3.EXE - Korean language version W321CNL3.EXE - Dutch language version W321CNO3.EXE - Norwegian language version W321CPL3.EXE - Polish language version W321CPB3.EXE - Brazilian Portuguese language version W321CPG3.EXE - Portuguese language version W321CTR3.EXE - Turkish language version Buildtime Package: ----------------- W321BEN3.EXE - U.S. English language version including the common files of MQSeries Workflow W321BCS3.EXE - Simplified Chinese language version W321BCT3.EXE - Traditional Chinese language version W321BDA3.EXE - Danish language version W321BDE3.EXE - German language version W321BES3.EXE - Spanish language version W321BFI3.EXE - Finnish language version W321BFR3.EXE - French language version W321BHE3.EXE - Hebrew language version W321BHU3.EXE - Hungarian language version W321BIT3.EXE - Italian language version W321BJP3.EXE - Japanese language version W321BKO3.EXE - Korean language version W321BNL3.EXE - Dutch language version W321BNO3.EXE - Norwegian language version W321BPL3.EXE - Polish language version W321BPB3.EXE - Brazilian Portuguese language version W321BPG3.EXE - Portuguese language version W321BTR3.EXE - Turkish language version 1.2.2 Unpack the files Copy the W321ENU3.EXE to a temporary directory and execute it using the command: W321ENU3 /D . This command unpacks all the common files and the U.S. English files. If you need to update a language other than U.S. English ("ENU"), you must copy the file you downloaded additionally to the temporary directory and invoke it using the command: W321xxx3 /D . where 'xxx' is the language abbreviation. 1.2.3 Update your existing MQSeries Workflow installation Note: First stop any running MQSeries Workflow programs and services. If you have an MQSeries Workflow Server installed and running, make sure to migrate your data as described in section 1.5 "Migrating data from a previous release" , 1.5.1 "Runtime database migration from Version 3.2.1 to Version 3.2.2" and 1.5.2 "Runtime database migration tool" before you launch the setup program. To install this Service Pack, switch to the subdirectory 'xxx' (language abbreviation) which is located in the directory into which you unpacked the downloaded file. To start the installation of the Service Pack, run SETUP.EXE. Note: If you install Service Pack #3 immediately after running the installation of MQSeries Workflow version 3.2 (General Availability version), make sure you reboot your machine between these two installation processes, whenever the system requires you to do so. Otherwise the registration of ocx and dll files will not work properly and you might experience errors in Buildtime and the Runtime client. Note: If you have problems to apply the Serivce Pack #3 on a Windows 2000 machine please refer to MQSeries Workflow Service Page for more help. 1.2.4 Upgrading your existing MQSeries Workflow Configuration 1. Please follow the instruction in section 1.5.3 "How to upgrade MQSeries to Version 5.1 with CSD level 4" to upgrade MQSeries. 2. To be able to use the product after upgrading the files, certain new queue definitions have to be made to MQSeries. To do this, run fmczq322.EXE as described in section 1.5.5 "Queue manager migration from Version 3.2.1 to Version 3.2.2" 3. Now start the MQSeries Workflow services as described in the Installation Guide. 1.2.5 MQSeries Workflow Buildtime with DB2 6.1 We recommend that you do not install DB2 6.1 Fixpack 3, because of these problems: After having installed this fixpack on several workstations (NT and Windows 2000), Buildtime - configured with a DB2 database - fails to start with the following error message: MSRDC1 IM006: [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed This problem has been solved with DB2 6.1 Fixpack 4. Therefore, keep your DB2 6.1 Fixpack 2 installation or install Fixpack 4 or later. 1.3 Installation on IBM AIX --------------------------- 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. Stopping your MQSeries queue manager is described in step 3, DB2 need not be shut down. 2) As root, perform the command 'slibclean'. 3) If you have an MQSeries Workflow Server installed and running, make sure to migrate your data as described in section 1.5 "Migrating data from a previous release" , 1.5.1 "Runtime database migration from Version 3.2.1 to Version 3.2.2" and 1.5.2 "Runtime database migration tool" before you launch smit. Important notice: Before you can run step 4 you have to do the following: Download and extract the file UPD3220.tar.gz (36 KB) into an empty directory. When extracted it needs about 700 KB. The command to extract the files is "gzip -dc UPD3220.tar.gz | tar -vxf -". Do a "smitty - update to latest level" to bring the existent install packages to level 3.2.2.0, then proceed as usual with the "real" update package for v3.2.2.1. 4) Update your MQSeries Workflow 3.2.1.0 (or later) installation (with or without having hotfixes applied) using smit - "update to latest level" to level 3.2.2.0. Note: Your configuration (profiles, /var/fmc/...) will not be modified by the installation update. However, the installation profile /usr/lpp/fmc/fmcrc will be updated to reflect the new level VRM=030202. 5) Please follow the instruction in section 1.5.3 "How to upgrade MQSeries to Version 5.1 with CSD level 4" to upgrade MQSeries. 6) update file and directory ownerships and permissions using the command fmczinsx -o mig as described in section 1.5.4 "Changing directory and file permissions for Version 3.2.2 on UNIX" 7) To be able to use the product after having upgraded the files, certain new queue definitions have to be made to MQSeries. To do this, run fmczq322 as Workflow Administrator (default: "fmc"). Please follow the instructions in chapter 1.5.5 "Queue manager migration from Version 3.2.1 to Version 3.2.2" After completion of these 7 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 & Info for Update Package on AIX ============================== The installation package fmc.java.samples has not been updated after MQSeries Workflow 3.2.1. When upgrading v3.2.1 to v3.2.2 this package: fmc.java.samples 3.2.1.0 can safely be removed. The same (and more) content is now available in the installation package fmc.samples 3.2.2.0 1.4 Installation on SUN Solaris ------------------------------- 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. Stopping your MQSeries queue manager is described in step 3, DB2 need not be shut down. 2) If you have a MQSeries Workflow Server installed and running, make sure to migrate your data as described in section 1.5 "Migrating data from a previous release" , 1.5.1 "Runtime database migration from Version 3.2.1 to Version 3.2.2" and 1.5.2 "Runtime database migration tool" before you upgrade the files. 3) This is how to update your MQSeries Workflow 3.2.1.0 (or later) files (with or without having hotfixes applied) to level 3.2.2.0: 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.1.0 (or later). 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 VRM=030202. 4) Please follow the instruction in section 1.5.3 "How to upgrade MQSeries to Version 5.1 with CSD level 4" to upgrade MQSeries. 5) update file and directory ownerships and permissions using the command fmczinsx -o mig as described in section 1.5.4 "Changing directory and file permissions for Version 3.2.2 on UNIX" 6) To be able to use the product after having upgraded the files, certain new queue definitions have to be made to MQSeries. To do this, run fmczq322 as Workflow Administrator (default: "fmc"). Please follow the instructions in chapter 1.5.5 "Queue manager migration from Version 3.2.1 to Version 3.2.2" After completion of these 6 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.5 Migrating data from a previous release ------------------------------------------- If you want to use Runtime data from your existing MQ Workflow installation with the new release of MQ Workflow you need to migrate the databases before installing the new release. Your Buildtime database for Version 3.2.1 does not require migration to work with Version 3.2.2. 1.5.1 Runtime database migration from Version 3.2.1 to Version 3.2.2 -------------------------------------- If you are currently running MQ Workflow Version 3.2.1, and want to use Runtime data with the new release of MQ Workflow, you must perform the steps described in this section. To migrate the Runtime database from your current MQ Workflow version to Version 3.2.2 you must perform the following: 1. Make sure that all MQ Workflow servers are shut down. 2. Back up the existing Runtime database data. Note: Although this step is not imperative, it is recommended that you back up your Runtime database before performing the migration in case problems occur and you need to restore it again. Details about how to back up a database are given in the DB2 Administration Guide. 3. Log on as the MQ Workflow configuration administrator. 4. At a command prompt, create a temporary directory called temp322 on your workstation. 5. Change to the directory temp322 you created. 6. Copy or unpack all files which are required for the migration to the directory temp322. Depending on your Operating System you will have to do the following to achieve this: On UNIX systems uncompress the tar file if necessary. For AIX: tar -xvf migaix322.tar For Sun Solaris: tar -xvf migsol322.tar For Windows NT: copy all files from the subdirectory mig322 which is located in the directory into which you unpacked the downloaded file to the current directory, by typing: copy \*.* where is the full or relative path to the mig322 directory. 7. From the temporary directory temp322, invoke the command- line migration tool by entering the following command and options (read the following command as one line): fmczm322 [-h] [-d] [-i] [-c] [-b] [-n ] [-u -p ] [-y ] For example, if your existing Runtime database is called FMCDB, no user ID and password are required to access it, and the MQ Workflow configuration is identified by the default configuration ID, then the command to migrate the Runtime database from your current version to Version 3.2.2 would be: fmczm322 -d -c -b -n FMCDB 8. When you see the message "Database migration completed successfully" the migration of your Runtime data is complete, and you can delete the temporary directory temp322, and its contents. Note: If errors occur during the migration process, restore the Runtime database data you backed up and repeat the migration procedure. How to restore backed-up data is described in the DB2 Administration Guide. If persistent errors exist, you should check the log files ( *.log) contained in the temporary directory temp322 to find the cause. 1.5.2 Runtime database migration tool -------------------------------------- The command-line migration tool fmczm322 is used to migrate the Runtime database. To invoke the migration tool, the migration command is used followed by the appropriate options as follows (read the following command as one line): fmczm322 [-h] [-d] [-i] [-c] [-b] [-n ] [-u -p ] [-y ] The command-line options are entered after the migration command without the square brackets, [ ]. The order in which command-line parameters are entered depends on whether you enter them all together after the command or one at a time. If you enter them all together after the command, the order is not important. If you want to enter them one at a time, you must first perform the schema changes using option -d. Then perform data preparation using option -c or binding using option -b in any order. The command-line parameters have the following functions: -h Invokes online help text that displays and describes all command-line options and the migration tool command. -i Reports information about the version of the Runtime database and about the current migration state. -d Changes the schema of the Runtime database. The layout and underlying processes of the existing database must be prepared for the next Version of MQ Workflow. -c Prepares existing Runtime data. The data contained in the existing Runtime database must be prepared for the next Version of MQ Workflow. -b Causes the new packages for Version 3.2.2 to be bound to the Runtime database. New packages must be bound to the Version 3.2.2 Runtime database. -n Specifies which database to migrate. Replace with the name of the database you want to perform the migration on. If this command-line parameter is not specified, the database name from the MQ Workflow profile is used instead. -u Specifies the user ID used to access the database. Replace with a valid user ID. If no user ID is specified, access to the database is tried without user ID and password values. -p Specifies the password used access the database. Replace with a valid password value. The password is only valid when a user ID has been previously specified. If no password is specified, access to the database is tried without a password value. -y Specifies the configuration ID that is set during the MQ Workflow configuration stage and which is used to identify an MQ Workflow configuration. If no configuration ID is specified, the default value is used. For example, to migrate the Runtime database to Version 3.2.2, use the migration command with command-line options as follows: fmczm322 -d -c -b -n FMCDB This assumes your existing Runtime database is called FMCDB, no user ID and password are required to access it, and the MQ Workflow configuration is identified by the default configuration ID. 1.5.3 How to upgrade MQSeries to Version 5.1 with CSD level 4 -------------------------------------------------------------- Queue managers from your exisiting MQ Workflow installation must be upgraded so that they can be used with the new release of MQ Workflow. If you already have MQSeries Version 5.1 installed, you must make sure that it is with CSD level 4. To upgrade the existing queue managers from a version below Version 5.1, you must install MQSeries Version 5.1 over your exisiting version. The Installation Guide contains details about MQSeries and the MQSeries components you must install. 1.5.4 Changing directory and file permissions for Version 3.2.2 on UNIX ---------------------------------------------------- Due to the changed security concept implemented for MQSeries Workflow Version 3.2.2 some ownerships and access rights for directories and files have to be changed. On UNIX platforms, you must do this be entering the command: fmczinsx -o mig 1.5.5 Queue manager migration from Version 3.2.1 to Version 3.2.2 ------------------------------------------------- Migrating the existing queue managers creates additional queue definitions required by the new release of MQ Workflow. This will be done by recreating and executing the MQSeries definitions for the queue manager based on the template files in the subdirectory "mqs". Queue manager migration tool ---------------------------- The command-line migration tool fmczq322 is used to migrate queue managers defined for MQ Workflow configurations. To invoke the migration tool, the migration command is used followed by the appropriate options as follows: fmczq322 [-y ] You can perform queue manager migration for a single configuration by specifying the '-y' parameter and the configuration identifier. If you omit the '-y' parameter all queue managers used by MQSeries Workflow will be migrated. On UNIX the executing user of that command must have update authority to the configuration profile, and must be a member of group "mqm" If the queue manager is an additional one in the cluster, you will be prompted for data concerning the primary queue manager: - Queue manager name. - TCP/IP address. - TCP/IP port number. - Principal name. For more information see the Installation Guide. 2. Important Notices =========================================== This ServicePack applies to these APAR numbers: PQ34776, PQ34802, PQ34803,PQ34805, and PQ34806 for MQSeries Workflow 3.2.1 for OS/390. 2.1 General ----------- o If the system fails to start by invoking fmcemain, shut down MQSeries Workflow. Then, run the following commands as user fmc: - endmqm -i , e.g. endmqm -i FMCQM - dltmqm , e.g. dltmqm FMCQM - fmczqqm -o:i Now you can start your MQSeries Workflow system as user fmc: strmqm , e.g. strmqm FMCQM runmqtrm -m FMCQM -q FMCTRIGGER &, assuming FMC is the qualifier being used fmcamain & o For all platforms MQSeries 5.1 CSD4 is required o Wrong description in Programming Guide WfMessageHeader instead of WfMessage In chapter 28. "The MQ Workflow message: The application data", page 186, the sample contains the following mistake. The Element WfHeader is wrong. The name of the element is WfMessageHeader as described in chapter 31, "The MQ Workflow XML message format". Format instead of MsgId In chapter 28. "The MQ Workflow message: Relevant MQSeries Message Descriptor fields", page 183, the reference to MsgId is wrong. The reference name should be: Format. o Configuring on a Windows NT server, which is not the primary domain controller During the configuration of an MQSeries Workflow 3.2.1 server, the 'fmc' user is created automatically. This user is required for MQSeries 5.1 communication. You can change the password of the user ID 'fmc' to any value you want. MQSeries and MQSeries Workflow do not use this password. The user ID 'fmc' is automatically added to the MQSeries Administration group 'mqm'. On a Windows NT server, which is not the primary domain controller, you cannot create users. If you try to create userss, an error occurs during the creation of the MQSeries Queue Manager. To avoid the error, create the user ID 'fmc' on the primary domain controller before configuring an MQSeries Workflow server. 2.2 Java -------- o Java Troubleshooting As a general rule of thumb: Whenever you experience problems with the Java API, turn off the JIT (Just in Time) compiler. Consult your JDK- / JRE- / Application Server- documentation for details on how to do this. o Applying Service to the Java API Beans and Java CORBA Agent component Locator policy LOC_LOCATOR -------------------------- Using the LOC_LOCATOR policy means that the Java Agent runs in the process of the application, a call level interface instead of a communication interface is used. For service updates,the new Java Agent code is installed into the directory \bin\java321x, where x is the number of the Service Pack. The directory name javaVRMS denotes Version, Release, Modification, and Service Pack Level of the code. Make sure that the CLASSPATH uses the path to the most recent level of code. Note: Whenever you use the LOC_LOCATOR policy in conjunction with servlets, for example, the MQ Workflow HTML client, you may need to update your servlet registration for the servlet engine. Locator policies COS_LOCATOR, IOR_LOCATOR, OSA_LOCATOR AND RMI_LOCATOR ---------------------------------------------------------------------- The Java API Beans and the Java CORBA Agent are based on RMI (Remote Method Invocation) and CORBA (Common Object Request Broker) technology. These technologies allow to develop distributed applications. This requires that the code on the server and on the client must match. If they do not match, the clients are NOT able to work with the server's objects. For example, if the code version on the server and on the client for the RMI protocol do NOT match, the following exception is thrown on the client: error unmarshalling return; nested exception is: java.io.InvalidClassException: ....Stub; Local class not compatible: stream classdesc serialVersionUID=5710528428249292109 local class serialVersionUID=9080421622065857355 This exception is caught by the Java API Beans code and wrapped into an FmcException with the message text "Could not locate Agent for Domain ..". Starting with MQSeries Workflow V3.2.1, a solution for this problem is available. Scenario for Windows NT: If you have a machine with the Java CORBA Agent installed, the java code (fmcojagt.jar), which represents the Java CORBA Agent, is installed in the \bin\java3210. It is assumed that various configurations exist, exploiting either RMI, OSA, IOR or COS locator policy. For each of the Agent configurations, there's a batch file to start the agent. Note that there are naming rules that apply, that is, if you have multiple agents exploiting the same locator policy, each one must have a unique name. The OSA locator policy is an exception to that rule, which means you can have two or more agents with the same name. This allows you to do an automatic workload balancing between these agents (Consult the Inprise Visibroker for Java documention for more details on that feature.) Now a Service Pack (CSD) for MQSeries workflow is made available. The Java component code of the service pack is installed into the directory \bin\java321x, where x is the number of the Service Pack. The directory name javaVRMS denotes the Version, Release, Modification and Service Pack Level of the code. To activate the new level of code, new Java CORBA Agent configurations have to be created. During the configuration, the level of code to be used must be specified. Select the most recent level. You can then migrate, which means you apply the service to one client after another. Having migrated the last one of the clients, the 'old' Agent, which is now obsolete, can be stopped and its configuration deleted. When applying service to the Java API Beans on the client, the CLASSPATH has to be adapted manually. The CLASSPATH is NOT updated automatically, because this allows you to apply the new Java API Beans code first and use it later. Note: - When you create an Agent with the new level of code, a unique name must be used. This requires your clients with the new level of code to use this new name too. This applies especially to OSA_LOCATOR, because the Visibroker Smart Agent technology selects the ORB to which the request is directed, and if there are two Agents running with different levels of code, one request will be handled successfully whereas another request may fail. - Service Packs are cumulative, which means that the latest Service Pack contains all the fixes of all previous Service Packs. Therefore, it is not necessary that you install all Service Packs in consecutive order. 3. Changes =========================================== 3.1 Problems addressed in Service Pack #1 ----------------------------------------- 1. Execution Server: Improved Memory Management Platform: independent 2. Administration Server: Improved Memory Management Platform: independent 3. Runtime Client: Improved Memory Management Platform: WinNT, Win95, Win98 4. Buildtime: Whenever you specify square brackets [] in condition strings, the Buildtime export function now converts square brackets to left and right brackets (). This improves flexibility to use FDL files in the OS/390 environment, which does not support square brackets. Platform: WinNT, Win95, Win98 5. Buildtime: In the BT dialog 'User-defined Program execution server properties', the UPES Queue Name (page 'Message Queuing') is no longer restricted to 32 characters. Now, 48 characters are allowed as well as lower case. Platform: WinNT, Win95, Win98 6. Buildtime: When creating a new system, the name of the system group is now preset, using the system group name, from which the dialog was invoked. Platform: WinNT, Win95, Win98 7. API: SetAnotherPersonAbsent() This method can now be called from the Execution Service object. Platform: WinNT, Win95, Win98 8. Standard Client for Runtime: Performance The default setup for the Standard Client is to display all available lists whenever you log on. The windows that are displayed for Process Template Lists, Process Instance Lists, and Worklists can contain a large number of list items. This can slow you down considerably, for example, if you have to deal with many worklists. Up to now, you could not close any of the List windows. You could only minimize these windows. To improve performance, new settings in the Windows Registry for the Client allow you to specify the following: If you set the following: "OpenWorklists"="N" "OpenProcessInstanceLists"="N" "OpenProcessTemplateLists"="N" the Tree View is displayed only, without opening all lists and displaying their contents. When you double-click on a list in the Tree View, the selected list and its contents are displayed. If you set the following: "Close"="Y" you can now close any of the List windows, using the standard Windows closing function (X in the upper right-hand corner of the window), instead of only minimizing them. To apply these the new settings, create the following entries in the Windows Registry: [HKEY_CURRENT_USER\Software\VB and VBA Program Settings\fmcn6rtc] [HKEY_CURRENT_USER\Software\VB and VBA Program Settings\fmcn6rtc\Lists] "Close"="Y" [HKEY_CURRENT_USER\Software\VB and VBA Program Settings\fmcn6rtc\Logon] "OpenWorklists"="N" "OpenProcessInstanceLists"="N" "OpenProcessTemplateLists"="N" Note: You must restart the Standard Client to activate the changes in the Windows Registry. Platform: WinNT, Win95, Win98 9.Database: Overall Performance Improve overall performance by introducing special database calls for immediate deletion of processes and work items. Platform: WinNT, IBM AIX, SUN Solaris, HP Unix 10.API: Memory Management To reduce the message size for container values, the message stream is now optimized and compacted. Platform: all 3.2 Problems addressed in Service Pack #2 ----------------------------------------- 1. Administration Server: Optional system shutdown without forced client logoff including shutdown of PEA. When an MQSeries Workflow system is shut down, all clients (including API programs) are logged off by deleting their session records from the MQSeries Workflow database, and all program execution agents (PEAs) are shut down. You can change this behavior by setting the variable "RTSystemShutdownMode" to: "KeepSessions" in the MQSeries Workflow profile. If the variable is set, clients are not logged off and running PEAs are not shut down. You can set this variable as follows: fmczchk -y -c inst:m,RTSystemShutdownMode,KeepSessions where is the ID of the configuration. For information on how to set and change profile variables, see the chapter about "MQ Workflow profiles" in the "MQSeries Workflow Installation Guide". Because session records are not removed from the database when the system is shut down with this option, make make sure that the regular cleanup of sessions is done by the administration server by setting a session expiration time and a session expiration check interval in the system settings. 2. Timestamps in filters are now assumed to be in local time So far, timestamps in filter strings were interpreted as specifying a time in UTC. They are now interpreted as timestamps in local time. If you have written applications to support local timestamps for your users, then any adaptions made must be removed. 3. Standard Client for Runtime The syntax for entering filter values has changed as follows: Strings for DESCRIPTION, NAME, PROCESS_CATEGORY, and PROCESS_NAME have to be enclosed in single quotation marks ('). If the IN operator is used to specify more than one string, enclose the strings in brackets (). The following example shows the syntax to be used in the value1 field: ('string1, 'string2'). Patterns must also be enclosed in single quotation marks ('). 3.3 Problems addressed in Service Pack #3 ----------------------------------------- MQSeries Workflow XML support Numerous bug fixes For a summary of changes and a list of problems addressed in this service pack please refer to the IBM MQSeries Workflow V3.2.2 Programming Guide, chapter "Summary of changes".