######################################################################## # # # 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.2 for Windows NT** ------------------------------------------------------------------------ The memo.ptf file contains information you need for updating IBM MQSeries Integrator Version 2.0.2 for Windows NT. This memo.ptf file corresponds to the first CSD which is defined as PTF U200147 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 ---------------------------------------- ************************************************************************ * NOTE:- MQSERIES INTEGRATOR V2.0.2 Refresh and PTF U200147 * ************************************************************************ * * * U200147 will not install on the refreshed base version of MQSI V202 * * as this already contains the fixes embodied in this PTF. If you are * * not sure what level of MQSI V202 you have then you should examine * * the Registry. If there is a string value for "Refresh" under * * HKEY_LOCAL_MACHINE\Software\IBM\MQSeriesIntegrator\CurrentVersion * * then your system has the fixes in U200147 already. Attempting to * * install U200147 will terminate. * ************************************************************************ As part of the install of maintenance the NEONRules and NEONFormatter support will also be upgraded if it is installed. This will present itself as a series of seperate InstallShield 6 component installs that take approximately 10-15 minutes in total. It is possible to install maintenance for NEONRules and NEONFormatter manually by running setup.exe from the location pointed to by the autorun.inf file in the Neon52 directory on the image. In order to restore a previous level you must backup replaced files. CSD01 requires approximately 250MB of disk space to do this. 150 Mb of free space should also be available for TEMPorary space. 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.2: 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.2 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.2 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"). 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.2, 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. You are able to restore a previous level of Neon 52 by accessing the NEON uninstaller. By uninstalling the latest version of the infr file, ie n0infr20_45 the previous version will be restored. 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 applying a CSD (for example, a power failure), the product files are likely to be in an unknown state, especially if existing files have been replaced. You must rerun the installation of the maintenance (to completion) before using the product. To recover from this situation, assuming you accepted the option of backing up replaced files you should: Copy the contents of the backup directory (CSDbkup\1 for CSD#1,unless you chose a different backup location) back into their original locations. This is most easily done using Windows Explorer and answering yes to the message asking whether you want to replace existing files files. You can then rerun the CSD install. You can manually reinvoke the Neon 5.2 upgrade as a seperate exercise using setup.exe from the Neon52\n6nrf52_152 directory on the CSD image. 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.2->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, DB2 7.1 is installed with no service applied. If using an existing DB2 6.1 database then fixpack 7 is required. 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 --------------------- None. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SPECIAL INFORMATION ------------------- Uninstallation of Neon To uninstall Neon 5.2 you should to use the Add/Remove programs dialog found under the Control Panel. Note that having uninstalled Neon you need to reboot before reinstalling, otherwise attempts to uninstall Neon 5.2 in the future may fail. If Neon uninstall fails then the following manual steps can be used to remove it. 1. Remove the registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\New Era of Networks 2. Delete the files from the neonsoft directory 3. Delete neoncomp.ics from your WINNT directory (normally c:\WINNT). 4. Remove the uninstall registry entry for "neoncomps" in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall Steps 1 and 4 above involve working with the Registry and you are advised to ensure that you have suitable mechanisms for recovering the registry in case of errors. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC30611 - STRESS PROBLEM WITH NEON DOMAIN MESSAGE PARSER There is a known problem on all platforms (NT, AIX, Solaris, and HP/UX) with the new Neon domain message parser and associated new nodes. This issue is being investigated and IBM expects to have a fix available as soon as possible after the GA of MQSI V202. When running multiple flows using the new Neon nodes with MQSI 202 on an SMP machine, the broker can exhibit a number of problems, including termination with a segment violation (GPF), if the product is put under stress. These problems do not occur when using the old NeonRules and NeonFormatter nodes. Please avoid stressing the product in this environment until this APAR is resolved and a fix is made available. Further information is available in the README file which is included in this maintenance. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC29727 - CREATE CONFIGMGR FAILS WHEN A USERID USED TO ACCESS THE MRMDB CONTAINS A $ (DOLLAR) SIGN PREFIX An attempt to run the 'mqsicreateconfigmgr' command, using as a parameter a user id beginning with a $ (dollar) sign, causes the command to fail with a BIP1801S error. This problem may also occur when other non-alphanumeric characters are used. Until this problem is fully investigated and resolved, it is recommended that customers restrict characters of the MQSI service user ids to the letters A to Z, a to z and numbers 0 to 9. It is our belief that in most cases, user ids already conform to this rule. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC28810 - SUBSCRIPTIONS WON'T SHOW UP FOR A SINGLE USERID The fix for this problem has removed the lowercaseing applied by the Control Centre on the user identifier (userid) in Subscriptions View; userid has become case sensitive. In order to display subscriptions it is now necessary to respect the case of the userid to get its subscriptions in the view. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 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. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC30331 -CHECKIN GIVES ERROR BIP1205E ON MQSI V202 AT DB2 V7.1 FP2 LEVEL MQSeries Integrator V2.0.2 is being shipped with DB2 7.1 .. It is possible that customers may then apply DB2 fp2 There are known errors with FP2 where on check-in a BIP1205E message is generated This error is resolved at DB2 V7.1 FP3 level. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IY18146 - IF THE BROKERDB IS ORACLE, ADDITIONAL NLSPATH IS REQUIRED. When the environment is set to a Japanese code page the broker will not start. This is because Oracle cannot be accessed when running in the Japanese code page. When using an Oracle Database on UNIX, the following environment variables must be set to ensure the broker starts cleanly: LC_MESSAGES=en_US LANG=en_US Alternatively, en_GB also works. This information will be added to the MQSeries Integrator Installation Guide. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SERVICE AND TECHNICAL SUPPORT ----------------------------- This is the third release of product 5639F6100, IBM MQSeries Integrator Version 2 for Windows NT. The following APARs have been incorporated into it. Name Abstract 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 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 IC27301 - SETTING MQMD.EXPIRY FIELD TO AN ABSOLUTE VALUE IN COMPUTE NODE 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 IC28312 - FLOAT DATA TYPES OF LENGTH 8 ARE NOT HANDLED CORRECTLY WHEN SE IC28324 - COBOL COPYBOOK IMPORT PROBLEM, MESSAGE BIP1812S RECEIVED. IC28401 - BIP2211E ERROR OCCURRED BY USING BYUSERID IN ORDER MODE OF INP IC28443 - BIP1812S RECEIVED USING THE CONTROL CENTER GENERATE FUNCTION I IC28446 - INSTALL GUIDE DOES NOT DISCUSS ABOUT MQSI_PARAMETERS_FILE VARI IC28447 - INSTALL GUIDE PAGE 129/130 HAVE INCORRECT NAMES FOR NT CONSIST IC28518 - 1. CREATING A BITSTREAM THAT CONTAINS A REPEATING SEGMENT OF IC28520 - LOOP ON COMPUTE NODE - REPEATING ELEMENT USES A REPEAT COUNT IC28605 - MESSAGE FLOW LOOP WITH MSGBIP2608I MSGBIP2623I AND MSGBIP2611I IC28724 - IMPORT OF COBOL COPY BOOK THAT DOES NOT HAVE A COMPLETELY ASCE IC28810 - SUBSCRIPTIONS WON T SHOW UP FOR A SINGLE USERID IC28926 - SIGNED PACKED DECIMALS WILL ACCEPT F AS WELL AS C AND D IC29022 - BIP1812E CAUSED DURING A DEPLOY IN STRUCTURES WITH MANY EBMEDD IC29033 - MQSI V201 USING DUPLICATE FLOW FEATURE TO CREATE MESSAGE FLOW IC29184 - XML-PARSE ENVIRONMENT INCORRECT IC29200 - XML MESSAGE GETTING TRUNCATED AFTER PROCESSING THROUGH COMPUTE IC29210 - MQSIMRMCOPYMSGSET CHANGES TWO ATTRIBUTES OF THE COPY IT MAKES IC29489 - DBCS MESSAGES WERE NOT CONVERT CORRECTLY FROM PC CODEPAGE TO H IC29632 - MQSI - INCORRECT STRUCLENGTH AND NAMEVALUELENGTH IN RFH2 LOOP IC29775 - MQSI BROKER DO NOT PASS THE MQMD CONTEXT INFORMATION WHEN A IC29801 - MQSI V2 FAILS TO RECONNECT AFTER ORACLE HAS BEEN BOUNCED IC30173 - MQINPUT CATCH TERMINAL DOES NOT COMMIT DATABASE LOCKS. IC30195 - EG ABEND WHEN USING TWO MESSAGES OF THE SAME STRUCTURE WITHIN IC30497 - ERRORS OCCURRING DURING MQSI GUI CONNECTION TO ORACLE 8.1.6 NE IY12651 - DATA FLOW ENGINE WILL NOT RECOVER FROM ERRORS DURING DELETION IY13621 - MQSI MRM MESSAGE IS CAUSING THE BROKER TO SPIN IY14540 - AIX BROKER CONFIGURATION LIBPATH MODIFICATION MISSING IN DOCUM IY14660 - MEMORY CORRUPTION ON AIX USING DB2 VIA TCP/IP WITH NIS ENABLED IY14720 - MSGBIP2301E WHEN A BROKER TRIES TO LOAD THE MQSI SAMPLE PLUGIN IY14970 - DOCUMENTATION INCORRECT/NEEDS CHANGE ON COMPILERS SUPPORTED BY IY15310 - MEMORY LEAK AND THROUGHPUT DEGREDATION IY16379 - EXECUTION GROUP TERMINATES ON STARTUP WITH BIP2123 IY16620 - MQSI CORE DUMP CAUSED BY ADDRESS ALIGHNMENT ISSUE WHEN BINDING IY16679 - INADEQUATE ERROR MESSAGE PRODUCED FOR EXECUTION GROUP FAILURE IY16970 - DFE STOPS PROCESSING MESSAGES FOR A FLOW. INCOMING MESSAGES BA IY17486 - COBOL STRUCTURES, CONTAINING SIGNED DECIMAL NUMBERS (PIC S9), IY17772 - AFTER UPGRADE MQSI VERSION F/V1.1 T/V2.0.1, MQSI BROKER HANG IY17780 - DFE NOT STARTING PROCESSING OF MESSAGES ON THE INPUT QUEUES IY17808 - XML PARSER ADD TRUE TO THE END OF XML DECLARATION. IY18104 - CAST FUNCTION INTERMITTENTLY FAILING IY18245 - PERFORMANCE FIX TO ADDRESS INEFFICENCY IN BIT STREAM FOR IY19382 - DATAFLOWENGINE LOOP 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.2 documentation see the following Web page on the MQSeries Web site: http://www.ibm.com/software/ts/mqseries/library/manualsa/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ CSD HISTORY =========== CSD01 (PTF U200147) ___________________ This is the first PTF for IBM MQSeries Integrator Version 2.0.2 for Windows NT. It is delivered via PTF U200147 for APAR IC30416. It contains fixes for ALL the problems listed below: Name Abstract IC30416 - CUMULATIVE MAINT #01 FOR MQSERIES INTEGRATOR FOR WINDOWS NT V20 IC30331 - CHECKIN GIVES ERROR BIP1205E ON MQSI V202 AT DB2 V7.1 FP2 LEVEL IY17486 - COBOL STRUCTURES, CONTAINING SIGNED DECIMAL NUMBERS (PIC S9), IY19382 - DATAFLOWENGINE LOOP f13586 - MQe/Scada - Migration Aid f14128 - README UPDATES f17791 - update Korean index.htm f18038 - NLS ESQL Reference f18057 - Add undocumented plugin logging env variables f18096 - Update english pdfs. bipyal03 & bipyar03 f18182 - Italian PDFS f18335 - Updated index.htm files including UNIX Platform f18725 - Updated English and Brazilian index.htm files f18822 - update index.htm nls files with ESQL ref 13712 - MTI problem converting floats which are not explicity cast 14500 - Over optimization in MTI refresh bitstream method 15437.1 - Fix junction support on NT output trees 16632 - STRESS: PubSub matches wrong retained pub topic 16951 - Standard XML entities rejected when standalone="yes" 17031 - BIP2211E is an inapropriate mesage for duplicate Scada port 17175 - Expiry field ignored on MQe messages. 17301 - Missing exit trace from WebDavException::GetErrorCode 17315 - Missing Exit trace from ATTRIBUTEGROUP:: GetDTDAttributes 17359 - Missing exit trace from UG methods 17413 - Missing exit trace from COMPONENT::GetLockInfo 17423 - Missing exit trace from GPROCS::AccessComponentHandle 17429 - Missing exit trace from UGRegistry.getGroup 17495 - MQeInput nodes - inconsistent Queue Managers not diagnosed. 17593 - When Running the RTS test psubatest12 on NT, event log entries 17603 - Missing MQe ini file not diagnosed. 17684 - Non-english uninstalls leave some menu items around.... 17718 - Flow with two MQeInput nodes fails to initialise correctly. 17721 - MQSISTOP hangs following MQe flow initialisation failure. 17725 - GLOSINDX.HTML contains broken tag when element name is in DBCS 17742.1 - Timing hole in sql cache 17753 - Badly configured scada node causes broker to fail on redeploy 17757 - problem with using keyboard on scribble sample 17761 - MQe/Scada db tables have incorrect size for column BrokerUUID 17763 - CCI_SQL_TRANSACTION_COMMIT ignored 17764 - ImbDecimal needs to support ".xyz" numbers 17765 - Repeating elements take value of first element 17769 - MQeInput node with message domain MRM not working. 17814 - reame.txt and memo.ptf not getting installed 17817 - S201 IC01 SupportPac does not support S202 export file format 17818 - Japanese Neon install shows failed when successful 17822 - Error closing the MQe server while stopping broker. 17832 - Start menu shortcut to NEON pdf incorrect 17871 - Incomplete cleanup when MQeInput has invalid queue manager. 17884 - Unable to write to trace file. 17980 - Missing messages in EventLog 17994 - XML Parser does not correctly process empty elements 18022 - MQInput + SCADA Input nodes can not send msgs in same flow 18026 - Persistence attribute not set by Scada Input Node 18030 - postcard sample will not allow entry of UPPERCASE characters 18032 - Memory leak + tidy up of indenting 18069 - Wrong setExpiry and getExpiry MQe interpretation 18094 - Replace ImbException with ImbRecoverableException 18193 - Ensure that clean start + finish works correctly (18192) 18198 - Control Center ESQL "Not a valid Compute Node" with PASSTHRU 18214 - Neon properties files need to be updated in CC 18262 - Transactionality still lost for some MQe messages 18292 - Database connections are not released when SCADA 18301 - Problems setting 50 breakpoints or more 18304 - Message delivery indicated although no breakpoints set 18370 - Clean session _may_ remove QoS2 messages 18469 - NLS: DBCS chars not displayed in Field value 18496 - DFE process seems to be dying after 18497 - Fix migration defect 18558 - Copyright Statements 18657 - NT install pacakge needs to includ UNIX pdf files 18778 - plugin parser can not be rolled if deploy fails 18840 - Behaviour of the 'Cancel' button on the DB2 Panel 18841 - No reference to NEON component in the summary panel 18854 - Event Map 19061 - icon displaying in explorer ####### ------- end of file MEMO.PTF ------------#######################