######################################################################## # # # COMPONENT_NAME: MQSeries Integrator # # # # FILE: MEMO.PTF # # # # Program Number 5639-F61 # # (C) COPYRIGHT International Business Machines Corp. 1999, 2000 # # All Rights Reserved # # Licensed Material - Property of IBM # # # # US Government Users Restricted Rights - Use, duplication or # # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # # ######################################################################## PTF Memo for IBM MQSeries Integrator Version 2.0 for Windows NT** ------------------------------------------------------------------------ This memo.ptf file contains information you need for updating IBM MQSeries Integrator Version 2.0 for Windows NT. This memo.ptf file corresponds to the first CSD which is defined as PTF U200123 and is divided into the following sections: o Installation and maintenance information o Documentation changes o Special information o Service and technical support o CSD history ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ INSTALLATION AND MAINTENANCE INFORMATION ---------------------------------------- In order to restore a previous level you must backup replaced files. CSD01 requires approximately 65MB of disk space to do this. IMPORTANT! ---------- This CSD introduces a new value 'byQueueOrder' for the orderMode attribute of the MQInput node. In order for the Configuration Manager repository to be updated with the new MQInput node definitions, perform the following tasks after the CSD has been installed: 1) Enter the following commands from a DB2 command window: db2 connect to user using db2 delete from cuuidlocks where cuuid='InTerminalType' db2 delete from cuuidlocks where cuuid='OutTerminalType' where : is the name of the Configuration Manager repository and : is the userID who created the Configuration Manager repository tables (the -u parameter if specified on mqsicreateconfigmgr, otherwise the -i parameter) and : is the password of the user who created the Configuration Manager repository tables (the -p parameter if specified on mqsicreateconfigmgr, otherwise the -a parameter) 2) run mqsideleteconfigmgr WITHOUT specifying the -m -n parameters. This deletes your Configuration Manager but preserves the repository and the data in it. 3) run mqsicreateconfigmgr with the same arguments that were previously used to create your Configuration Manager. NOTE! For existing message flows containing MQInput nodes with the orderMode set to 'byUserid' (i.e. not the default setting), the drop down list for these nodes will not be updated with the new attribute value after applying the CSD. If you require to use the new 'byQueueOrder' value in an existing message flow, you will need to delete and recreate the MQInput node within that message flow. If you choose, for whatever reason, to back out the CSD, the new 'byQueueOrder' value for the orderMode will no longer be useable. The following tasks should be performed after removing the CSD: 1) Enter the following commands from a DB2 command window: db2 connect to user using db2 delete from cmsgflow where cuuid='ComIbmMQInput' 2) run mqsideleteconfigmgr WITHOUT specifying the -m -n parameters. 3) run mqsicreateconfigmgr with the same arguments that were previously used to create your Configuration Manager. NOTE: For any existing message flows that use the 'byQueueOrder' value on the MQInput node, these will have to be changed to one of the other orderMode options (either 'default' or 'byUserid') before redeploying. The byQueueOrder value will still be available from the drop down list, but this should not be used once the CSD has been backed off otherwise a failure will occur at deploy time. APPLYING MAINTENANCE ____________________ Maintenance updates are supplied on CD in the form of a Program Temporary Fix (PTF), referred to as a Corrective Service Diskette (CSD). You can find the latest information about available CSDs on the Internet, at this address: http://www.ibm.com/software/ts/mqseries/ You can also download CSDs from this web site. APPLYING THE MAINTENANCE INFORMATION ____________________________________ If you need to apply maintenance updates to MQSeries Integrator Version 2.0: 1. Ensure that the user ID you are logged on with is a member of the Windows NT ADMINISTRATORS group in the local security domain. You are recommended to use the same ID as the one you used for installing MQSeries Integrator. 2. Ensure that all MQSeries Integrator function is stopped. You must: a. Stop execution of the Configuration Manager, the User Name Server, and all brokers on this system using the MQSISTOP command, or by stopping the Windows NT services for these components from the Services program in the Control Panel. b. Stop execution of all programs that manage MQSeries Integrator Version 1.1 rules and formats (the Visual Tester, the NEONFormatter user interface, and the NEONRules user interface). c. Stop execution of the Control Center. d. Ensure that you do not have any MQSeries Integrator Version 2.0 files open. 3. You are also strongly recommended to exit all Windows NT programs before applying maintenance to MQSeries Integrator. 4. If you have downloaded maintenance from the web, you must: a. Read the "memo.ptf" file associated with this maintenance on the Web site. This might contain additional information regarding the installation of maintenance. b. Select a suitable destination as the target for download. c. When the file has been downloaded, change to the download directory and run the executable file. You must choose a temporary directory to extract the maintenance files from the downloaded file. You are presented with a dialog where you can accept the default, or specify an alternative. d. Click NEXT to activate the extract. e. Click FINISH to end the dialog. f. The "setup.exe" file now runs. 5. If you are installing from CD you must: a. Read the file "memo.ptf" in the root directory of the CD, and any "Readme.txt" files also in the root directory. These files might contain additional information about how you must install this maintenance. b. Insert the maintenance CD into the appropriate drive. If you have autorun enabled, "setup.exe" will start to run automatically. If you do not, you must start "setup.exe" from the CD by doubleclicking. 6. When "setup.exe" runs, you are presented with a window that provides instructions for applying service. These include a checkbox that controls the backup of files replaced during the application of this service level. If you take the default action to replace these files (and you are recommended to do so), you can specify the directory in which the backup files are created. Click NEXT when you have made the updates you want. A confirmation window displays your choices. Click NEXT to continue, or BACK if you want to return and make further changes. 7. The maintenance is applied to MQSeries Integrator. You can cancel this action at any time by clicking CANCEL. The maintenance process backs up updated files in the subdirectory "\CSDbkup" in the MQSeries Integrator Version 2.0.1 home directory. If you click CANCEL before the maintenance process has completed, these backup files are restored and the maintenance backed out (the CSD is not applied). 8. When you have completed installation, review the "memo.ptf" file supplied as part of the CSD. Complete any manual post-install actions required. NOTE: CSDs are cumulative, therefore you do not need to apply CSD1 before you can apply CSD2. When you have installed a CSD, you are prevented from installing a previous CSD without first restoring the system using the backed-up files. RESTORING A PREVIOUS SERVICE LEVEL __________________________________ You are able to restore a previous service level if you want to, or if you are instructed to do so by your IBM Support Center. However, this is only possible if you accepted the default action to backup replaced files when you applied the current service level (see the instructions in "Applying the maintenance information" on page 1). If you need to restore MQSeries Integrator to a previous level of maintenance: 1. Ensure that the user ID you are logged on with is a member of the Windows NT ADMINISTRATORS group in the local security domain. You are recommended to use the same ID as the one you used for installing MQSeries Integrator. 2. Access the Windows NT Control Panel (Start->Settings->Control Panel). ______________________________ 3. Double-click the Add/Remove Programs icon. 4. Find and highlight IBM MQSeries Integrator V2.0, and ____________________________ click ADD/REMOVE. This starts the MQSeries Integrator uninstall program, and presents the uninstall dialog. 5. If one or more CSDs have been applied the dialog allows you to select the option to uninstall CSDs. Select the option to uninstall the most recently installed CSD and return to the previous service level. If you want to remove all CSDs, you must invoke this option for each one in turn to return to the base service level. If no CSDs have been applied, this option is unavailable. INSTALLING NEW COMPONENTS AFTER APPLYING MAINTENANCE ____________________________________________________ If you install maintenance and then decide to install a new component from the MQSeries Integrator CD, you will be advised that you must reapply the maintenance following installation of the new component. You are strongly recommended to do this: if you do not, it is likely that the integrity of the product files will be compromised and unexpected results might ensue. FAILURE DURING THE APPLICATION OF MAINTENANCE _____________________________________________ If you have a failure when you apply a CSD (for example, a power failure), the product files are likely to be in an unknown state. You must rerun the installation of the maintenance (to completion) before using the product. CHECKING THE SERVICE LEVEL __________________________ After initial installation, the MQSeries Integrator Service level indicates no service has been applied. After one or more updates, the service level is updated to show the CSD most recently applied. The service level is expressed in terms of the PTF number for a particular CSD. To check the service level, select Start->Programs->IBM MQSeries Integrator 2.0->Service _____________________________________________________ Level. This displays the "memo.ptf" file containing the _____ service level and details of the maintenance applied (PTF Number). This file is installed in the program file directory. APPLYING MAINTENANCE TO IBM DB2 UNIVERSAL DATABASE __________________________________________________ If DB2 was installed on this system by the MQSeries Integrator installation program, it is installed with no service applied. You can also obtain information about the current status of maintenance of this product, and download fix packs for DB2 from this Web site: http://www.ibm.com/software/data/db2/udb/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ DOCUMENTATION CHANGES --------------------- There are no documentation changes associated with this CSD. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SPECIAL INFORMATION ------------------- CSD01 (PTF U200123) ------------------- o 7635 - Stopping the Broker sometimes locks up mqsistop has a new flag, -i, which will force a broker to terminate immediately. o 9480 - DatabaseUpdate node generates invalid SQL If you are using a DatabaseUpdate node within a message flow, it is necessary to delete the Key and Update ESQL mappings within the node properties, re-instate them and re-deploy the message flow in order to pick up the fix for this problem. o 9954 - Add process Id to mqsilist when a broker is specified mqsilist will now display the process id of each execution group. This makes it easier to attach a debugger to the required process. Usage: mqsilist o 10059 - Allow single threaded input node to guarantee order This change allows an MQInputNode to be configured so that it preserves the ordering of the messages on the queue received by that node. This causes that node to operate as a single thread regardless of the value of the AdditionalInstances property of the message flow. This allows a message flow to be created, for example, with two MQInputNodes, one of which is operating as a single processing thread to guarantee order and the other taking advantage of using multiple instances. o 10074 - Allow mqsicreateconfigmgr to pick up changed primitives Defect 10059.1 introduces a new value 'byQueueOrder' for the orderMode attribute of the MQInput node. In order for the Configuration Manager repository to be updated with the new MQInput definitions, perform the additional tasks described above in the INSTALLATION AND MAINTENANCE INFORMATION. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SERVICE AND TECHNICAL SUPPORT ----------------------------- This is the first release of product 5639F6100, IBM MQSeries Integrator Version 2.0 for Windows NT. No APARs or PTFs have been incorporated into it. The MQSeries support page is located at: http://www.ibm.com/software/ts/mqseries/support from which you can obtain the latest information about various MQSeries topics including :- - Hints and Tips - APARs and Fix Packages - FAQs - Support downloads - Newsgroups ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ CSD HISTORY =========== CSD01 (PTF U200123) ------------------- This is the first PTF for IBM MQSeries Integrator Version 2.0 for Windows NT. It is delivered via PTF U200123 for APAR IC26926. It contains fixes for ALL the problems listed below: Name Abstract IC26926 - CUMULATIVE MAINTENANCE #01 FOR MQSERIES INTEGRATOR V2.0 IC26734 - SQL ERRORS OCCUR WHEN WORKING WITH DATABASEUPDATE NODE IC26799 - BIP2293 PROBLEM WHEN DEPLOYING A MESSAGE USING CUSTOMER S IC26880 - FAILURE TO START OR STOP ALL MESSAGE FLOWS FOR AN EXECUTION IC26952 - CREATION OF RESPONSE MSG FAILS DUE TO NULL NAMEVALUECCSID f9889 - Allow Execution Group granularity for deploys f9889.1 - EUI change for Execution Group deploy 4135 - DFE does not handle endmqm properly. 5973 - Adding datasource removes existing SQL statements 7436 - DataFlow Engine takes a long time to shut down 7635 - Stopping the Broker sometimes locks up 8680 - ResetContentDescriptor failing on repeating elements 8882 - Deleting nodes when they have promoted attributes leads to 8985 - Error after duplication and original deleted. 9044 - CAST ('123456789012345678901234567890' AS DECIMAL(8,2)); 9059 - mqsiChangeProperties implementation incomplete 9072 - Change from GMT to BST not reflected in the Log timestamps 9088 - RCD node can not reparse MRM CWF messages. 9164 - PubSub with MRM messages leaks quite severely 9183 - Problems with Tour 9237 - Trusted domain is not recognised by MQSI 9252 - Deleting an Element does not delete associated valid values 9257 - Password is displayed in message 1209 9326 - MRM checkin fails in MQSITour 9380 - BIP2291 using compute node to create plugin parser message 9407 - Plug-in samples exception handling incorrect 9480 - DatabaseUpdate node generates invalid SQL 9516 - mqsilist returns old execution group label after rename 9516.1 - stop message flow from EUI fails 9517 - cniGetBrokerInfo() returns old exec group label after rename 9560 - DAV1361 message if MQJavaClient not present 9561 - Subscribing on a temp dyn queue 9562 - Event 0 occurring when failed de-register (ref defect 9561) 9609 - MessageFlow redeployment leads to an additional thread instance 9632 - BIP2323 on connect to a non NT remote DB2 DB via XA 9666 - Interbroker fails if Queue Manager name is too long 9695 - Sort out configurable/persistent dataflows. 9731 - None of BIP2223/2322/2321 set the database name as insert 9741 - BIP2066 occurring on complete deploy for 15 exe grps 9742 - BIP2803 & BIP2066 wrong insert from Cnt Cntr 9769 - Invalid CCSID in response message 9777 - FILEDNAME function does not recognise newly created elements 9833 - Publications are occasionally delivered to the wrong subscriber 9905 - Cannot distinguish a NULL value from the string 'NULL' 9951 - Update Tour XML documents for Create definition 9954 - Add process Id to mqsilist when a broker is specified 10006 - ThreadPool Destruction takes an abnormally long time to complete 10012 - Ensure that we never see bip2809 or bip2811 again, ever! 10059 - Allow single threaded input node to guarantee order 10059.1 - Add byQueueOrder value for MQIN orderMode attribute 10074 - Allow mqsicreateconfigmgr to pick up changed primitives 10094 - Event Log Entries for deleted IPC QUEUE 10151 - Improve report responses to provide DB connection activity 10194 - Catch Java errors to prevent thread dying & hanging. 10224 - PMR87005 - Unable to deregister subscribers 10227 - Turning on trace clears the execution group name. 10237 - Tolerate loss of ODBC connection due to DBMS outage 10264 - BIP2061 when deploying single execution group 10291 - Shutdown performance enhancements. 10428 - ODBC statement handles need to be freed if connection lost ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ TRADEMARKS ---------- The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM MQSeries Windows is a trademark of Microsoft Corporation. ####### ------- end of file MEMO.PTF ------------#######################