######################################################################## # # # COMPONENT_NAME: MQSeries Integrator for Sun Solaris # # # # FILE: MEMO.PTF # # # # Program Number 5765-D67 # # (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. # # # ######################################################################## # # # Please note that any references in this product to NEON do not refer # # to Neon Systems, Inc. # # # ######################################################################## PTF Memo for IBM MQSeries Integrator Version 2.0.2 for Sun Solaris** -------------------------------------------------------------------- The memo.ptf file contains information you need for updating IBM MQSeries Integrator Version 2.0.2 for Sun Solaris. This memo.ptf file corresponds to the first CSD which is defined as PTF U479743 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 30MB of disk space in the /var/sadm/pkg directory to save the previous level. The old files are backed off and stored at location /var/sadm/pkg/mqsi-updn. 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 ____________________________________ 1. Ensure that all brokers are stopped before installing maintenance and only restart them once installation is complete. 2. From the directory of the CSD image enter the command: pkgadd -d Unnnnnn.TAR where Unnnnnn is the number of the PTF to be added. 3. Select: mqsi -updn where n is the level of 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. To remove a CSD on Solaris enter the command: pkgrm mqsi-updn (where n is the number of the CSD to be removed) Because CSDs are cumulative, you must uninstall the most recent CSD you applied before attempting to uninstall any previous CSDs. For example, if you have installed CSD1, CSD2 and CSD3 on your machine and you want to revert to the CSD1 level of code, you must first uninstall CSD3 and then uninstall CSD2. 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 __________________________ To see the current level of corrective service, enter the command: pkginfo | grep mqsi The current level is the highest value of n in the displayed values of mqsi-updn. 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/ APPLYING NEW ERA OF NETWORKS MAINTENANCE INFORMATION ____________________________________________________ Ensure that all brokers are stopped before installing maintenance and only restart them once installation is complete. From the directory of the CSD image enter the command: pkgadd -d neonsoft ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ DOCUMENTATION CHANGES --------------------- IC30818 - DEPLOYING FROM A 2.0.1 CONFIGMGR TO 2.0.2 BROKERS. Deploying from a V2.0.1 Configuration Manager to a V2.0.2 Broker is not supported. After installing V2.0.2 and migrating brokers to the V2.0.2 level or creating new brokers, it is not possible to deploy to those brokers from a V2.0.1 Configuration Manager. The Version 2.0.1 Configuration Manager must be upgraded as described in Chapter 9 of the MQSeries Integrator V2.0.2 Administration Guide, SC34-5792-04. This Guide will also be updated to include the following note under the existing heading 'Upgrading your Version 2.0.1 brokers': When upgrading any brokers to Version 2.0.2, the Configuration Manager used to deploy to those brokers must also be upgraded to Version 2.0.2. Deploying from a V2.0.1 Configuration Manager to a V2.0.2 broker is not supported. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SPECIAL INFORMATION ------------------- IC30888 - THE MQINPUTNODE ADVANCED PROPERTIES FIELDS MATCH MESSAGE ID AND MATCH CORRELATION ID HAVE CHANGED IN V202. The MQInputNode Advanced properties fields Match Message ID and Match Correlation ID have changed from input fields with a default value of 'no' in V2.0.1 to check box fields in V2.0.2. This situation has been corrected however the following actions need to be taken to activate the resolution:- 1. Copy the provided file ComIbmMQInput to :- MQSI_SETUP_DIR\primitives\MessageProcessingNodeType and MQSI_SETUP_DIR\Tool\repository\development\MessageProcessingNodeType directories to replace the existing file. 2. Logon to an NT session as IBMMQSI2. For this specific task this user must belong to groups mqbrdevt, mqbrasgn, mqbrops and mqbrtpic). 3. Open the MQSI Control Center. 4. Unlock the MQInput node. 5. Check-out the MQInput node. 6. Replace the file ComIbmMQInput which is located in the private repository directory (this should be MQSI_SETUP_DIR\tool\repository\ private\\\MessageProcessingNodeType) with the provided file. 7. Save the workspace or quit MQSI Control Center, saving workspace. 8. Open the saved workspace or reopen the MQSI control center. In the MQInput node advanced properties, verify on the right of the fields 'Match Message ID' and 'Match Correlation Id' the check boxes have been replaced by text editors. 9. Check-in the MQInput node. 10. Check-out the MQInput node to prevent other modifications. 11. Remove the ComIbmMQInput and ComIbmMQInput.wdp files from the private repository directory. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IY21179 - DFE CONSUMING HIGH CPU AND HANGING WITH NO ERRORS A message flow that processed a message successfully on NT failed to complete on AIX. This was due to a stack overflow problem on AIX. On Unix platforms, MQSI overrides the default thread stack size and allocates a stack size of 1MB to each thread. On NT, MQSI does not override the default thread stack which is sufficiently high at 2MB. This problem has been fixed by allowing the default thread stack size of 1MB on Unix platforms to be overridden by use of a new environment variable:- MQSI_THREAD_STACK_SIZE The stack size should be specified in bytes, so to set the thread stack size to 2MB for example, set the following in the environment from which the Broker will be started: MQSI_THREAD_STACK_SIZE=2000000 export MQSI_THREAD_STACK_SIZE This environment variable is only applicable on the Unix platforms. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 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. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ NEW ERA OF NETWORKS INFORMATION ------------------------------- Contents 1. New Era of Networks Formatter 2. New Era of Networks Rules 3. Visual Tester 4. Documentation 5. General Issues Each section is sequenced in the following order: by case number and then followed by defect/CR number and APAR number, and then by defect/CR number or APAR number alone. ==================================================================== Part 1: New Era of Networks Formatter ==================================================================== Case #7135 - Empty Formats Defect #7154 Description: When creating two formats in which one is an empty format and another contains at least one field, or when both formats contain at least one field, the following error message appears: Error text = invalid data window row/column specified. Resolution: The code was adjusted to correct the problem. -------------------------------------------------------------------- Cases #10855, 11582, 12633 -Prefix/Suffix Output Operations Defect #8204 Description: Output Operations, Prefix or Suffix, fail to import when defined with a value of NONE. Resolution: An adjustment has been made so that the value of NONE is substituted for the prefix/suffix value. -------------------------------------------------------------------- Case #12780 - S.W.I.F.T. and Other Large Formats Defects #9582, 10040 Description: In the New Era of Networks Formatter GUI, when using large formats, such as SWIFT, if you double-click Formats in the tree view to expand the entire format list, it takes a very long time for the list to display. Resolution: The security checks location was adjusted to correct the problem. -------------------------------------------------------------------- Case #13663 - Overwrite Parameter [-o] and Single Transaction Parameter [-T] Defect #8311 Description: When running NNFie as one transaction, the overwrite parameter [-o] does not overwrite the data when importing. Instead, an Import Failed error message appears. Problem Resolution: The problem was resolved, but to overwrite the data, you must enter parameter [-T] before [-o] on the command line. -------------------------------------------------------------------- Case #13836 - Import Problems with Invalid Output Controls Defect #9438 Description: In the New Era of Networks Formatter GUI, it is possible to create invalid output controls that NNFie can export but cannot import. Resolution: An error message now alerts the user to any invalid output controls that are created in the New Era of Networks Formatter GUI. -------------------------------------------------------------------- Case #15121 - Permutil Problems on New Era of Networks Formatter Defect #10074 Description: PermUtil did not work for listing ownership of the New Era of Networks Formatter components. Resolution: Additional database queries were added to retrieve the New Era of Networks Formatter component names. -------------------------------------------------------------------- Case #17772 - Format Remover Failure with Compound Formats Defect #11022 Description: The Format Remover fails to remove a format in a compound format that contains other compound formats. It attempts to remove the same format twice, resulting in a failure at the second attempt. Resolution: The Format Remover now continues processing once a format has been removed and does not exit with an error. -------------------------------------------------------------------- Case #18209 - Overwrite Failure with Compound Formats Defect #11179 Description: When overwriting a compound format with no component formats using NNFie, the overwrite fails. This occurs when the optional parameter [-o] is on or if the Interactive Overwrite is chosen. Resolution: An adjustment has been made to overwrite empty compound formats. --------------------------------------------------------------------- Defect #6438 - Retrieval Error with Compound Formats Description: When you save compound formats as opposites, the following retrieval error is generated: ds_retrieval_error/Retrieval Error... Message Retrieval Error Unable to retrieve rows from the database into a datastore Resolution: Saving a compound format as opposite now works correctly; no error is generated. --------------------------------------------------------------------- Defects #8421, 10443 - Oracle 8.1.6 Client Software APAR # IC31418 - Formatter GUI not working with Oracle greater than 8.1.6 Description: When creating an Oracle session driver from an existing connection, the New Era of Networks Formatter GUI does not work with the Oracle 8.1.6 Client software. Resolution: A change was made to allow New Era of Networks Formatter GUI to work with the Oracle 8.1.6 or 8.1.7 Client software. -------------------------------------------------------------------- CR #254254 - Removing Literals Description: Literals cannot be removed when associated with an input control type of literal. Resolution: A check was included for Literal input control types. The check marks a literal for deletion when the literal name is defined in the input control. -------------------------------------------------------------------- CR #254396 - Import Error with the New Era of Networks Formatter GUI Defect #11175 Description: When trying to import using the New Era of Networks Formatter GUI, a message saying "Unable to open NNFIE.inv" or "Unable to open NNFIE.err" occurs. This happens because the GUI is trying to read the NNFIE.inv file before the write is completed. Resolution: The code was changed to read the correct directory and .inv file and a second pause was put in to ensure that the file write is completed and the file closed by the operating system prior to the read happening. -------------------------------------------------------------------- CR# 255142 - Literals Not Alphabetizing in New Era of Networks Formatter Treeview Defect #11235 Description: In the New Era of Networks Formatter GUI, new literals do not alphabetize when you refresh. Resolution: A correction was made so that literals do alphabetize now. -------------------------------------------------------------------- CR #255144 - Delete Function Disabled in New Era of Networks Formatter GUI Description: In the New Era of Networks Formatter GUI, if you right-click on a format in the context menu to display the shortcut menu and have permissions to delete the format, the Delete function remains disabled. Resolution: A correction was made so that the Delete function is enabled when you have permissions to delete a format. -------------------------------------------------------------------- CR #255144 - Delete Function Disabled in New Era of Networks Formatter GUI Description: In the New Era of Networks Formatter GUI, if you right-click on a format in the context menu to display the shortcut menu and have permissions to delete the format, the Delete function remains disabled. Resolution: A correction was made so that the Delete function is enabled when you have permissions to delete a format. -------------------------------------------------------------------- CR # 255463 - Compound Output Formats Not Reformatting Properly Description: Compound output formats with repeating fields are not reformatting message data properly. The first record gets reformatted, but instead of reformatting the second record, New Era of Networks Formatter simply repeats the first record. Resolution: When defining Data Field Tag Search output controls, New Era of Networks Formatter searches for the first field in the input message with the specified tag value. This type searches the input data for the first occurrence of the specified tag and gets the first instance of it, generating the correct number of repeats, but always getting the first repeat’s data. To avoid this problem, use the following work-around. 1. Define the output control type for your compound output format as Data Field Name Search. 2. Add a prefix to the tag you were looking for. -------------------------------------------------------------------- CR #256022, 256570 - Migration Problem on AIX/Oracle APAR # IY22611 - FAILURE TO COMPLETELY IMPORT FORMATS AND RULES INTO AN ORACLE Description: 1) When migrating formats from MQSI 1.1 AIX/Oracle 8.0.5 to MQSI 2.02/AIX/Oracle 8.1.7, several components are missing after migration and no errors are reported. 2) The nml file is reporting the following error: First detection of out-of-memory condition. Freed memory reserve and setting shutdown-flats to true. Resolution: 1) Because the allocated tablespace was insufficient, inst_db was changed to increase the tablespace size. 2) Memory leaks were found and resolved. -------------------------------------------------------------------- CR #256089 - Optional Formats Fail Description: A reformat defect was causing optional formats to fail, miss repeats, and become out of order. Resolution: A code adjustment was made to correct the problem. -------------------------------------------------------------------- CR #256537 - Apitest Problem on Solaris Description: On Solaris, the New Era of Networks Formatter 5.2 apitest core dumps when attempting to display the contents of empty data fields. Resolution: NULL pointer errors were fixed to correct the problem. -------------------------------------------------------------------- CR #256893 - New Era of Networks Closes Abnormally on Oracle 8.1.7 APAR # IC31419 - FORMATTER GUI CLOSING ABNORMALLY Description: With the Oracle 8.1.7 client libraries, the New Era of Networks Formatter GUI may close abnormally, and the following error message appears at shutdown: DDE Server Window: nnfmt.exe - Application error The instruction at "0x77f83a33" referenced memory at "0x00000010". The memory could not be read. Work-around: Click OK to close the error message. -------------------------------------------------------------------- CR #258003 - NNFie Not Importing Literal Values Description: NNFie not importing literal values where the first value of the literal contains a value of zero (0). This became an issue in the this version because literal definitions were expanded to meet the requirements for internationalization. Resolution: The check for the first value of zero was removed. ==================================================================== Part 2: New Era of Networks Rules ==================================================================== Defect #9128 - BooleanOperator Object Can Crash in Rules Description: When Rules loads the data for evaluation, it creates a BooleanOperator object that can crash under certain circumstances. Resolution: Memory allocation problems were resolved. --------------------------------------------------------------------- Defect #9284 - Cannot Exit on PermUtil Description: PermUtil does not allow you to exit after you have performed one function. Resolution: An Exit option was added to the submenu in the Application Group Selection menu allowing you to return to the Application Group Selection menu or exit the application. -------------------------------------------------------------------- Defect #9493 - Application Group Default Name Description: When the user creates a new Application Group, the name of the Application Group defaults to NewApplication<#>. To rename the Application Group, the user must either right-click NewApplication<#> to access Rename from the shortcut menu or click NewApplication<#>. Resolution: The user is now put in Edit mode after a new Application Group is created, eliminating the rename step. -------------------------------------------------------------------- Defect # 9574 - MQS Expiry Argument Not Working Properly Description: The MQS Expiry argument no longer has a pull-down menu associated with it and will not allow you to enter a numeric value. When attempted, the error message #2697 appears: Invalid option value '100' for putqueue MQS_EXPIRY option" The only entries that are allowed are "PROPAGATE" and "NO_PROPAGATE". Resolution: A New Era of Networks Rules Management API has been adjusted. The GUI now allows you to enter numeric values, and the values are correctly represented in the message header. -------------------------------------------------------------------- Defect #9668 - New Era of Networks Rules Requires an Expression Before Exiting Description: The GUI does a validation check to make sure the user entered an expression. There might be times where a user does not have the expression determined yet and the user is not allowed to exit the rule without entering something. Resolution: The validation was removed allowing the user to come back to a rule and enter an expression at a later time. -------------------------------------------------------------------- Defect #9833 - Read Permissions Appear Missing in View Description: When new users are added to a component and given Read and Update permissions, the Read permission is not there when you go back into the component's Permission tab. Resolution: The setting and viewing of the Read permission has been fixed. -------------------------------------------------------------------- Defect #9905 - Error Messages Not Pulled from Correct Files Description: Some error messages were not being pulled from the correct language file. Resolution: Some of the error messages were always looking in the English directory. This was fixed so the correct locale's messages are used. -------------------------------------------------------------------- Defects #9907, #10419 - Import Problem in New Era of Networks Rules GUI Description: The GUI does not report problems encountered when importing using the GUI. Resolution: The GUI was modified to recognize the return code from NNRie and report the problem. -------------------------------------------------------------------- Defect #10504 - Importing Problem in New Era of Networks Rules GUI Description: Importing using the New Era of Networks Rules GUI causes intermittent database deadlocks. Resolution: Added transaction boundary after login that eliminates NNRie locking. -------------------------------------------------------------------- Defect # 10699 - Setting Expiry Fields Generates An Error Description: Setting the expiry field in a rules evaluation node causes an error. Resolution: To correct the problem, the following changes have been implemented: MQS_EXPIRY = - Propagate any value set in the original message. MQS_EXPIRY = -1 - Disable MQS_EXPIRY MQS_EXPIRY = - Set MQS_EXPIRY to the number of milliseconds specified MQS_EXPIRY = PROPAGATE - Propagate any value set in the original message. MQS_EXPIRY = NO_PROPAGATE - Disable MQS_EXPIRY -------------------------------------------------------------------- Defect #10717 - Problem with Sub Expression Tab Description: When using the Sub Expression tab to build an expression if you use the F2FSTRING operator, the expression builder adds the space character that separates the left field name and the operator as part of the field name. This creates an invalid expression. Resolution: The expression builder now puts the space in the correct place. -------------------------------------------------------------------- Defect # 10883 - Incorrect Error Messages on Subscriptions Description: An error message appears stating that a rule is missing a subscription when the message being processed successfully reformats and routes. Resolution: These errors occur when a message goes through a Rules Eval Node and does not hit any rule. The message is then routed to the NoHit queue and sends the following error message as designed: Rules subscription list missing or empty. -------------------------------------------------------------------- Defect #11195 - Message Type Cannot Be Set to Inbound Format Description: In the Rules GUI, the message type cannot be set to inbound format for processed messages. Resolution: The format types available from the putqueue message type only listed output formats. The list now contains input formats. -------------------------------------------------------------------- CR #257951 - Memory Allocation Failure in NNDOData.cpp Description: The neonmsg parser fails to parse certain messages and generates an error. Resolution: A fix was made to the NDO fixing the problem. ==================================================================== Part 3: Visual Tester ==================================================================== Defect #10920 - Message Data Encoding Differs from Default Encoding Description: A user loads messages onto an MQSeries transport using MQSeries Explorer or some alternative method (the user does not use Visual Tester to load the transport). The messages are typed or pasted in and assumed to be in the native encoding of the machine. When the message is read from the transport using Visual Tester and the user attempts to change the Data Source to "Screen" to edit the message data, a message appears stating that the message data encoding differs from the default system encoding; editing the data is not allowed. The user assumes the encodings should be the default of the machine. Workaround 1: If the user has set up MQSeries with the default configuration, MQSeries may use a different default encoding than our software uses. In this case, when messages are loaded with MQSeries Explorer, the encoding seen when Visual Tester reads from the transport appears to differ from that used as default by Visual Tester. The solution is to configure MQ Series to use the proper encoding rather than its default. Workaround 2: If MQSeries is loaded by a method that allows you to set the RFH, specify the encoding of the message in the RFH. Workaround 3: After reading the message from a transport, you can copy the message data from the Input Message control, switch the input message to screen, dismiss the informational message, press reset, then paste the message data back into the Input Message area. The data can now be edited. -------------------------------------------------------------------- CR #255381 - Visual Tester GUI Problem Description: When attempting to parse a message, the Visual Tester GUI crashes. Resolution: The Visual Tester GUI now works correctly. ==================================================================== Part 4: Documentation ==================================================================== Case #11368 - User's Guide Defect #8439 Description: Additional information needs to be included in the New Era of Networks Formatter Chapter regarding the Jump to Rules functionality. Resolution: To view the Jump to Rules errors when running the consistency checker, type the following syntax into any SQL Query window: Select m.MSG_NAME 'Message Type', s.SUBN_NAME 'Subscription Name', a.OPT_VAL 'Bad control name' from NNR_MSG_MSTR m, NNR_SUBN_LIST s, NNR_SUBN_ACT a WHERE m.MSG_ID = a.MSG_ID AND a.MSG_ID = s.MSG_ID AND s.SUBN_ID = a.SUBN_ID AND a.APP_ID = s.APP_ID AND a.OPT_NAME = "FORMAT_CONTROL" AND a.OPT_VAL not in ( select CNTL_NAME from NNF_OUT_MSTR ) order by f.MSG_NAME -------------------------------------------------------------------- Case #11982 - Open Transport MQSeries Driver Configuration Guide Defect #8645 Description: In the Open Transport MQSeries Driver Configuration Guide, the NNOT_FACTORY_FUNCTION parameter is incorrectly defined. Resolution: The correct definition of the parameter is: NNOT_FACTORY_FUNCTION = NNMQSSessionFactory. -------------------------------------------------------------------- Defect #5987 - User's Guide Description: It is no longer necessary to quote field names that contain non-alpha characters. The only time that you need to quote a field name is when the name contains one of the four basic arithmetic signs (+, -, *, /). Resolution: The following changes were made the New Era of Networks Formatter chapter of the user guide: 1. The note regarding the use of quotations marks now reads: Note: You must enclose field names in single or double quotes when the field name contains one of the following arithmetic signs: (+, --, *, /) For example, ’inField1 + $MAPPED_INFIELD’ or inField1 + $MAPPED_INFIELD are valid math expressions. 2. All quotation marks have been removed from the example text, except those using one of the four arithmetic expressions. -------------------------------------------------------------------- Defect #8494 - User's Guide Description: In Visual Tester chapter of the User Guide, it does not state that the Load tab is not enabled unless transport parameters are defined. Resolution: The Visual Tester chapter of the User Guide now contains the following note: To enable the Load function, you must have defined the transport parameters in the configuration mechanism. For more information, refer to the Open Transport Configuration and User Guide for your transport driver. -------------------------------------------------------------------- Defect #10763 - User's Guide and New Era of Networks Formatter Programmers Reference Description: In both the User Guide and New Era of Networks Formatter Programmers Reference, the documentation needs additional information regarding how to define a math expression. Resolution: The following information must be added to the User Guide, To define a math expression operation (procedure), and the New Era of Networks Formatter Programming Reference , NNNFMgrMathExpCntlInfo API parameter table: The maximum value for decimal precision in a math expression is 11. -------------------------------------------------------------------- Defect #253061 - Installation Guide Description: When importing rules, NNRie makes dbo the owner of the rules, leaving the user with read-only permission. Additional information is needed in the documentation to avoid this occurrence. Resolution: The following note was added to the Verifying the Environment section in the e-Biz 3.2.2 install guide for Microsoft SQL Server and Sybase: NOTE: New Era of Networks components do not work properly when using aliased database owner accounts. To ensure the proper functioning of all component applications, you must run them as a database user in the NEONGRP database group/role. However, the inst_db installation process is an exception to this rule, using an aliased database owner account to refresh the New Era of Networks databases. The owner account used for refreshing is created when inst_db creates the database. -------------------------------------------------------------------- CR # 253713 - New Era of Networks Formatter Programming Reference Description: The following error code descriptions are needed in the New Era of Networks Formatter Programming Reference: 1085, 1086, 1087, and 1088. Resolution: Descriptions for the error codes are now in the New Era of Networks Formatter Programming Reference. -------------------------------------------------------------------- CR # 254838 - System Management Guide Description: Information regarding the NNFie.err file need to be added to the System Management Guide. Resolution: The following note was added to the migration chapter of the System Management Guide: Note: For e-Biz 3.2.2, delete the NNFie.err and NNFie.log files before running NNFie. Failure to follow this procedure results in an error message in the NNFie.log that states that NNFie.err already exists. -------------------------------------------------------------------- Case# 10748911 CR #255445 - User's Guide APAR # IY22705 - THE DOCUMENTATION IS NOT CLEAR ON VALID OUTPUT CONTROLS WHERE THE TYPE IS INPUT FIELD VALUE =. Description: The User's Guide does not instruct users that NONE cannot be used as the field value for an Output Control type. Resolution: The User's Guide now contains a statement that although the default of NONE appears as the field value for an Output Control type, an actual value must be used. -------------------------------------------------------------------- CR # 258078 - System Management Guide Description: If you bring up Visual Tester and the Load tab is disabled, it is because there is no transport information in the configuration, or the configuration information cannot be found. In order to enable transports, transport session information must be entered in the neonreg.dat file. These procedures need to be added to the System Management Guide. Resolution: The following information was added to Chapter 3, Component Configuration: Specifying Transport Session Information On z/OS, you must specify transport session information in the neonreg.dat file to enable the Visual Tester Load feature. After completing this procedure, the Load tab is enabled in the Visual Tester GUI. To specify transport session information: 1. Locate the neonreg.dat file. For more information, see Locating the Example Folder on page 20. 2. Create an entry for MQSeries Session parameters. Example: Session.MQSeriesSession NNOT_SHARED_LIBRARY=dbt22mqs NNOT_FACTORY_FUNCTION=NNMQSSessionFactory NNMQS_SES_OPEN_QMGR= 3. To set default parameters for MQSeries queuing, specify the following using the model in step 2: a. Set NNOT_SHARED_LIBRARY to dbt22mqs. b. Set NNOT_FACTORY_FUNCTION to NNMQSSessionFactory. c. Set NNMQS_SES_OPEN_QMGR to your queue manager. 4. Create an entry for Transport parameters. Example: Transport. NNOT_FACTORY_FUNCTION=NNMQSQueueFactory NNOT_SHARED_LIBRARY=dbt22mqs NNOT_TIL_OPEN_TSI= NNOT_TIL_OPEN_SESSION_ID=MQSeriesSession 5. To set default parameters for your inbound queue, specify the following: a. Set NNOT_FACTORY_FUNCTION to NNMQSQueueFactory. b. Set NNOT_SHARED_LIBRARY to dbt22mqs. c. Set the NNOT_TIL_OPEN_TSI to your inbound queue name. d. Set NNOT_TIL_OPEN_SESSION_ID to MQSeriesSession. e. To test the Load function in Visual Tester, open the Visual Tester GUI. For more information, see the MQSeries Integrator User's Guide. -------------------------------------------------------------------- Installation Guide The installation guide incorrectly states that e-Biz Integrator 3.2.2 supports the Windows 98 platform. It does not support Windows 98. ==================================================================== Part 5: General Issues ==================================================================== Defect # 9191 - Extraneous Error Messages Are Being Generated Description: Extraneous error messages are being generated by the New Era of Networks nodes when they are unable to propagate a message to the failure terminal. Resolution: These error messages have been removed. --------------------------------------------------------------------- Defect # 10560 - DFE Core Dumps When Creating the First Execution Group Description: During stress testing, the DFE core dumps when it creates the first execution group. If all three New Era of Networks lils are removed from the lil directory, the problem is non-existent. Resolution: Changes were made to the msg catalogs to correct user messages. --------------------------------------------------------------------- Defect # 10616 Description: The WebDav driver that allows the MQSI Control Center tooling to see New Era of Networks Formatter definitions adds an _m_id suffix to all message ( format name ) identification names. Resolution: The code was adjusted and the suffix is no longer visible in the tooling. --------------------------------------------------------------------- Defect # 10639 - Error Occurs When Modifying Message in Two Compute Nodes Description: When you modify the New Era of Networks message in two compute nodes in a row with the final compute node setting the message type to an output format, the following error message is written out to the event log: Event ID: 120 (STRESS1.default) Input message type was not specified for output transformation. The NEONMSG Parser may require a New Era of Networks input format name to correctly transform a message from its internal representation to a bit stream. The transformation will fail only if a "Message Eval" operation is encountered during the transformation. Resolution: A correction was made so that now the current state of the message post compute node is acceptable to the input of subsequent compute nodes without regard for the message name. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SERVICE AND TECHNICAL SUPPORT ----------------------------- This is the second release of product 5765D6700, IBM MQSeries Integrator Version 2 for Sun Solaris. 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 IC30331 - CHECKIN GIVES ERROR BIP1205E ON MQSI V202 AT DB2 V7.1 FP2 LEVEL IC30424 - AFTER APPLIED CSD2, THE MESSAGE BROKER INTERNAL PROBLEM ERROR O 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 U479743) ___________________ This is the first PTF for IBM MQSeries Integrator Version 2.0.2 for Sun Solaris. It is delivered via PTF U479743 for APAR IY23539. It contains fixes for ALL the problems listed below: Name - Abstract IY23539 - CUMULATIVE MAINT #01 FOR MQSERIES INTEGRATOR FOR SOLARIS V202 IC28463 - LENGTH FUNCTION NOT WORKING IF THE ELEMENT ARRIVE WITH A DATA O IC29235 - SPURIOUS ESQL SYNTAX ERROR IN COMPUTE NODE WHEN SETTING A FIELD IC29387 - MESSAGE TRANSLATION INTERFACE SEEMS TO HAVE A PROBLEM WITH THE IC29416 - COMPUTE NODE ADD MAPPING TO MRM LAYOUT GENERATES BAD ESQL IC29789 - IT APPEARS THAT A CDATA SECTION IS MARKED AS "SPECIAL" IN THEXM IC29873 - NO ABILITY TO ASSIGN A VALUE OUTSIDE THE SPECIFIED RANGE IC29992 - IF DEFAULTHEX IN THE DB TABLE HAS 1000 BYTES OR MORE THEN SPACE IC30011 - INCORRECT MESSAGES, WHICH ARE SENT TO THE FAILURE-TERMINAL OF A IC30171 - REORDER OF ELEMENTS FOR A MESSAGE SET, WITHIN A COMPOUND TYPE IC30502 - OUTPUT TREE AFTER PARSING XML MESSAGE IS NOT CORRECT IC30653 - WHEN YOU UNSET A PROMOTED PROPERTY, DEFAULT IS LOST IC30673 - SQL SYNTAX CHECKER REPORTS ERROR ON VALID SYNTAX WHICH DEPLOYS IC30818 - DEPLOYING FROM A 2.0.1 CONFIGMGR TO 2.0.2 BROKERS. IC30888 - THE MQINPUTNODE ADVANCED PROPERTIES FIELDS MATCH MESSAGE ID AND IC31150 - GETTING AN ERROR BIP1835E. THE CREATE RUNTIME MESSAGE DIC. IC31362 - MESSAGE GROUPING FUNCTION ONLY PROCEED THE FIRST MESSAGE IC31418 - Formatter GUI not working with Oracle greater than 8.1.6 IC31445 - DEFINING A STRING MRM-MESSAGE ELEMENT AS NULL-TERMINATED WITHIN IC31612 - NEWERAOFNETWORKS VISUAL TESTER FAILS WITH NNVT.EXE - APPLICATIO IC31657 - NEON PROPERTIES FILE MQSIV2NEONPLUGINS.PROPERTIES IS IC31739 - WHEN USING THE DEBUGGER WITH XML MESSAGES THAT MIX BOTH IC31825 - BOTHRESH AND BOQNAME NOT WORKING PROPERLY WHEN ERROR OCCURS ON IC31916 - MESSAGE CONVERSTION TROUBLE (SI/SO HANDLING) WITH MQSI IY17561 - RULES NODE NOT PROCESSING A MQS EXPIRY NO PROPAGATE FIELD IN SU IY17806 - WHEN BROKER HAS LONG CONNECTION TO DATABASE, SOMETIMES THE CONN IY18458 - ERROR PUT TO DLQ BY THROW NODE IS UNREADABLE - 4048 ERROR AND IY19242 - LOCAL_TIMEZONE ESQL IS RETURN 239/241 INSTEAD OF 240 ABOUT 50% IY20050 - ERROR WHEN OUTPUT TERMINAL THAT IS LABELLED WITH A NAME THAT IY21179 - DFE COSUMING HIGH CPU AND HANGING WITH NO ERRORS IY22197 - ELEMENTS CONTAINING THE &APOS: ENTITY ARE NOT BEING HANDLED COR IY22611 - FAILURE TO COMPLETELY IMPORT FORMATS AND RULES INTO AN ORACLE IY23076 - DEFINING BINARY ELEMENTS/FIELDS IN A MRM-MESSAGE SET WITH IY23087 - EXCESSIVE CASHING PERFORMED BY MQSI CAN LEAD TO MEMORY HEAP f21983 - New Era Renaming - V2.0.2 Service Stream 16758 - Exponential growth of DeletePub messages in collective 18105 - Mixed stress test fails with corupt core file 19084 - Migration library shipped with wrong name 19406 - Regression - V2.0.1 plugin fails under V2.0.2 20216 - Exception thrown creating EG on a migration broker 20404 - Multiple broker deploy fails 20592 - CARDINALITY returns incorrect results if path invalid 21173 - Using \u3044 causes filter error 22471 - IBM Primitives nodes list inconsistent in Assignment view 23018 - MRM/byte alignment pad/valid values are rejected ####### ------- end of file MEMO.PTF ------------#######################