######################################################################## # # # COMPONENT_NAME: MQSeries Integrator for AIX # # # # FILE: MEMO.PTF # # # # Program Number 5765-D66 # # (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.1 for AIX ---------------------------------------------------------- The memo.ptf file contains information you need for updating IBM MQSeries Integrator Version 2.0.1 for AIX. This memo.ptf file corresponds to the first CSD which is defined as PTF U472858 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 60MB of disk space to do this. 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 ____________________________________ Follow these instructions if you need to apply maintenance to your installation of MQSeries Integrator. 1. Ensure that you are logged on as root 2. Ensure that MQSI is stopped 3.a. Type smitty b. Select Software Installation and Maintenance Install and Update Software Update Installed Software to Latest Level (Update All) or use the fastpath command smitty update_all c. Either, enter the directory where the update images are, or press PF4 and select the appropriate device (for example, if installing from CD-ROM). d. Decide whether or not you want to commit the update by selecting the appropriate response in the COMMIT software updates field. If you answer Yes you will not be able to restore the previous level of the product without uninstalling it. Answering No will backup the replaced files so that you can reject the update and return to the original level of the product, (see 'Committing updates'). e. Press the Enter key to perform the update 4.When you have completed installation, review the memo.ptf file supplied as part of the CSD in /opt/mqsi. 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 maintenance on AIX). Carry out the following procedure: 1. Type smitty 2. Select Software Maintenance and Installation Software Maintenance and Utilities Reject Applied Software Updates (Use Previous Version) or use the fastpath command smitty reject 3. In the SOFTWARE name field type mqsi 4. Press the Enter key to remove the update COMMITTING UPDATES __________________ If you no longer need the ability to restore the product to a previous level, or want to save disk space, you can commit the update. This removes the files you backed up when the update was applied. To do this on AIX: 1. Type smitty 2. Select Software Maintenance and Installation Install and Update Software Commit Applied Software Updates (Remove Saved Files) or use the fastpath command smitty commit 3. In the SOFTWARE name field type mqsi 4. Press the Enter key to commit the update 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 that 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 on AIX: 1. Type smitty 2. Select Software Maintenance and Installation Software Maintenance and Utilities List Software and Related Information List Installed Software and Related Information List Installed Software or use the fastpath command smitty list_installed_sw 3. In the SOFTWARE Name field, enter mqsi\? 4. Press the Enter key 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 --------------------- 11318 - Implement ICU 1.6 for enhanced EUC support The latest version ICU 1.6 incorporates a new mechanism for packaging ICU data in the form of a shared DLL with the benefit of improved performance. The new release has improved locale support including support for EUC and further OS390 code pages. For a full list of supported code pages see file README.CCSID in /opt/mqsi ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SPECIAL INFORMATION ------------------- CSD01 (PTF U472858) ___________________ IY13468 - DEFECT IN CLI IN REGARDS TO HOW WE DETERMINE THE CTX USED AT THE ENVIRONMENT LEVEL. Broker not stopping after an mqsistop command has been issued An intermittent problem has been discovered on AIX and Sun Solaris where the broker may not shutdown following the issuing of the mqsistop command (without the -i option). This is only a problem when using DB2 as a broker or customer database. If you encounter such a symptom, then the broker should be able to be successfully shutdown by re-issuing an mqsistop command, specifying the -i option. This problem has been raised against DB2 as APAR IY13468. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 9049 - MRMB31 Memory leak associated with datasource keyword. During a redeploy operation to a running broker, a memory leak could occur under certain situations. This fix addresses this problem. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 13135 - XML white space on tree copies to NameVal parsers The following information will be added to Appendix C of the MQSeries Integrator Using the Control Center V2.0.1 book, SC34-5602-01. Copying messages between parsers Compute node expressions can copy part of an input message to an output message. The results of such a copy depend upon the type of input and output parsers involved. Like parsers Where both the source and target messages have the same folder structure at root level, a "like-parser-copy" is performed. For example: SET OutputRoot.MQMD = InputRoot.MQMD; will result in all the children in the MQMD folder of the input message being copied to the MQMD folder of the output message. Another example of a tree structure which will support a like-parser-copy is: SET OutputRoot.XML.Data.Account = InputRoot.XML.Customer.Bank.Data; Unlike Parsers Where the source and target messages have different folder structures at root level, it is not possible to make an exact copy of the message source. Instead, the "unlike-parser-copy" views the source message as a set of nested folders terminated by a leaf name-value pair. For example, copying the following message from XML to MTI: Value31Value32 will produce a name element "Name3", and a name-value element called "Name31" with the value "Value31". Note: The second XML pcdata (Value32) cannot be represented and will be discarded. The unlike-parser-copy scans the source tree, and copies folders, also known as name elements, and leaf name-value pairs. Everything else, including elements flagged as "special" by the source parser, will not be copied. An example of a tree structure resulting in an unlike-parser-copy is: SET OutputRoot.MTI.Data.Account = InputRoot.XML.Data.Account; Note: If the algorithm used to make an unlike-parser-copy does not suit your tree structure, it might be necessary to further qualify the source field to restrict the amount of tree copied. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 13137 - cpiCreateContext() called for each message parsed When running a broker which receives messages which are parsed using a plugin parser, then the parsers implementation function, cpiCreateContext() was being called multiple times on the same thread. This function should be invoked once only, on creation of the instance of the parser. Instead, the function was being called each time a message was received. This could cause problems in the operation of the parser, depending on the way in which that parser was implemented. One known possible side-effect would be to provoke a memory leak. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 13300 - ODBCINI must not be set on login accounts If, on AIX and Sun Solaris systems you have previously installed an ODBC driver from Merant, then you must ensure that the UNIX environment variable ODBCINI is NOT set on any login accounts used to create or start message brokers. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SERVICE AND TECHNICAL SUPPORT ----------------------------- This is the first release of product 5765D6600, IBM MQSeries Integrator Version 2.0.1 for AIX. The following APARs have been incorporated into it. Name Abstract IC27033 - TRACE DOES NOT SHOW CORRECT DATA - XML STATEMENT WITH A NULL IC27038 - ADD MAPPING IN AN OUTPUT MESSAGE COMPUTE NODE IS NOT POSSIBLE IC27068 - REGISTER A SUBSCRIPTION GIVES THE EVENT ERROR 7053 -UNEXPECTED IC26734 - SQL ERRORS OCCUR WHEN WORKING WITH DATABASEUPDATE NODE IC26799 - BIP2293 WHEN DEPLOYING A MESSAGE USING PLUG-IN PARSER IC26880 - FAILURE TO START/STOP ALL MESSAGE FLOWS FOR AN EXECUTION GRP IC26952 - CREATION OF RESPONSE MSG FAILS DUE TO NULL NAMEVALUECCSID 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 For the latest versions of MQSI V2.0.1 documentation see the following Web page on the MQSeries Web site: http://www.ibm.com/software/ts/mqseries/library/manualsa/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ CSD HISTORY =========== CSD01 (PTF U472858) ___________________ This is the first PTF for IBM MQSeries Integrator Version 2.0.1 for AIX. It is delivered via PTF U472858 for APAR IY12888. It contains fixes for ALL the problems listed below: Name Abstract IY12888 - CUMULATIVE MAINT #01 FOR MQSERIES INTEGRATOR FOR AIX V201 IC27806 - DATA FLOW ENGINE WILL NOT RECOVER FROM ERRORS DURING DELETION IC27959 - DELETING A DATABASE REFERENCE FROM A COMPUTE NODE DOES NOT STO IC28174 - COMPOUND NODE OF A FLOW CONTAINING LABELS CANNOT BE INCLUDED IC28401 - BIP2211E ERROR OCCURRED BY USING BYUSERID IN ORDER MODE OF INP IY12651 - DATA FLOW ENGINE WILL NOT RECOVER FROM ERRORS DURING DELETION IY13621 - MQSI MRM MESSAGE IS CAUSING THE BROKER TO SPIN f8167 - Properties windows always resizes back to default f13255 - Properties windows divider always gets back to default posit'n 9049 - MRMB31 Memory leak associated with datasource keyword. 11318 - Implement ICU 1.6 for enhanced EUC support 12106 - MRMB0408 Boolean tests fail 12191 - mqsistop causes DFE core in ~ostream_withassign (Neon?) 12201 - Messages without inserts get incorrect processing of quotes 12331 - Usage message wrong for mqsireport 12437 - Core dump when ODBC trace active 12507 - Generate fails for Gold Messageset. 12642 - Broker spins when Create ExecutionGroup does not respond 12678 - 1812 Generated when prod. Msg Bk for Gold Message set 12698 - sample directory not removed on uninstall 12772 - Cannot delete Brokers on Uninstall 12789 - Data flow engine will not recover from errors during deletion 12805 - executionGroupTraceOverrideLevel broken 12848 - Apparent memory leak in MTI 12889 - MRMB3503 Dataflowengine abnormally terminated event2160 12917 - NT: DB2: deploy invalid config msg -> broker terminates 12922 - mqsistop usernameserver gives BIP2015 12966 - Scribble IVP fails if no '.' in classpath 12975 - Data base update causes a memory leak on AIX using Oracle 12978 - Problem with sequencing of actions in the Tour 12989 - The CWF property of a string can only be set to a fixed length 12997 - DataFlowEngine locks on deploy with Sybase 13028 - MQRFH2 parser rejects valid RFH2 from AMI 13038 - DataFlowEngine locks on deploy with Sybase 13048 - Memory leak in ImbDecimal class 13121 - cniElementDecimalValue returning unexpected result. 13135 - XML white space on tree copies to NameVal parsers 13137 - cpiCreateContext() called for each message parsed 13149 - Element tree detached unexpectedly in plugin parser 13185 - Pub Sub is never going to work when access control is enabled 13187 - COBOL / C importer name clash (PMR 36770,278,000) 13188 - Reference to removed object in compute node mapping 13221 - Allow threads in a DataFlowEngine to run concurrently by dflt 13261 - Button labels doesn't change but the text indicates they will 13272 - An error message issued when using byUserID. 13300 - ODBCINI must not be set on login accounts 13356 - Valid mapping lines are removed when deleting an input message 13389 - 'pow' function gives SIGSEGV on AIX 13425 - Large columns >2000 bytes corrupted on retrieval ####### ------- end of file MEMO.PTF ------------#######################