######################################################################## # # # COMPONENT_NAME: WebSphere MQ Integrator # # # # FILE: MEMO.PTF # # # # Program Number 5724-A82 # # (C) COPYRIGHT International Business Machines Corp. 1999, 2001 # # 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 REVIEW THE README.TXT FILE WHICH HAS BEEN UPDATED IN THIS # # MAINTENANCE RELEASE. # # # ######################################################################## # # # The WebSphere MQ Integrator V2.1 documentation has been updated to # # the CSD02 level. The March 2002 levels will be available by the # # end of April from the following Web page on the MQSeries Web site: # # # # http://www.ibm.com/software/ts/mqseries/library/manualsa/ # # # ######################################################################## PTF Memo for WebSphere MQ Integrator Version 2.1 for Sun Solaris ---------------------------------------------------------------- The memo.ptf file contains information you need for updating WebSphere MQ Integrator Version 2.1 for Sun Solaris. This memo.ptf file corresponds to CSD02 which is defined as PTF U482016 and is divided into the following sections: o Installation and maintenance information o Documentation changes o Special information o New Era of Networks 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. CSD02 requires approximately 110MB 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 ____________________________________ The instructions for applying and removing maintenance can be found in Appendix D (Applying Maintenance) of the Websphere MQ Integrator for Sun Solaris Installation Guide (GC34-5842-04) but must be amended by any changes documented below. 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 --------------------- IC33040 - INSUFFICIENT DETAIL ON IMPLEMENTING THE PASSTHRU FUNCTION. Description of the PASSTHRU statement, previously described in the MQSeries Integrator, Using the Control Centre manual, SC34560200, and now described in the WebSphere MQ Integrator ESQL Reference guide, SC34-5923-02, will be expanded in Chapter 4; ESQL statements, as follows: If two or more other parameters are passed, each parameter is bound to the corresponding question mark in the statement string: that is, the first parameter is bound to the first question mark, the second parameter is bound to the second question mark, and so on. The question marks are processed as parameter markers in a prepared SQL statement by the DBMS. This means that if you are passing values to functions in the DBMS you will have to be sure to have appropriately typed your parameter markers. For example, in DB2 a parameter marker would be cast as follows: SET OutputRoot.XML.Result.Data = PASSTHRU('SELECT * FROM user1.stocktable where time=TIMESTAMP(CAST(? as TIMESTAMP)), '1999-12-31-23.59.59.999999'); ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SPECIAL INFORMATION ------------------- PLEASE REVIEW THE README.TXT FILE WHICH HAS BEEN UPDATED IN THIS MAINTENANCE RELEASE. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ To use WebSphere MQ Integrator on a Solaris machine in Simplified Chinese in zh locale you should modify the sample profile as shown below. If you are using zh.GBK locale, there is no need for you to modify the sample profile. NLSPATH=/usr/lib/locale/%L/LC_MESSAGES/%N:$NLSPATH; /opt/wmqi/messages/Zh_CN/%N:/opt/wmqi/messages/%N LANG=zh LC_ALL=zh export NLSPATH LANG LC_ALL Alternatively you may set up symbolic links to the message catalogue files in /opt/wmqi/messages/Zh_CN from /usr/lib/locale/zh/LC_MESSAGES if you wish to avoid changing the NLSPATH environment variable. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ CSD02 introduces the concept of prefixed identifiers for MRM elements. Refer to the Working with Messages book, Chapter 4 section "Names and Identifiers" for full details. If this concept is exploited, you must ensure that all components of your WMQI domain are upgraded to CSD2, that is, your Configuration Manager, all Control Centers, and all brokers to which a message set containing such elements is to deployed. Failure to upgrade in this manner will result in parse errors in the broker. Please note also that the DTD Importer functionality of the Control Center exploits prefixed identifiers, so if this is used to populate message sets then the upgrade stated above must be performed. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC32427 - V201 AND V202 TO V2.1 MRM MIGRATION AND COEXISTENCE WMQI V2.1 contains a major upgrade to MRM capability. As a result of this upgrade, the format of the message dictionary that flows from the Configuration Manager to brokers during a deploy operation has changed compared with MQSeries Integrator V2.0.x. Migration details are in the Administration Guide, chapter 12. Please note the following additional information: Importing 2.0.x message sets into a 2.1 Configuration Manager. When importing 2.0.x message sets into the 2.1 Configuration Manager you may choose to create a default XML wire format layer. This additional layer allows a 2.1 broker to process application messages that specify a message domain of 'MRM' and a message format of 'XML'. You create the layer by adding the '-x XML' option to your mqsiimpexpmsgset command line. You may specify any valid name for the new layer, but for compatibility with existing messages and message flows you must use 'XML'. If you do not migrate your Control Centers, Configuration Manager and all brokers in the domain to WMQI 2.1 at the same time, then you must be aware of the following extra information that applies to co-existence scenarios: A 2.1 Configuration Manager may co-exist with 2.0.1 and 2.0.2 brokers, as long as message sets assigned to the 2.0.x brokers do NOT exploit the new messaging functionality available in 2.1. This is the recommended co-existence scenario. In order to implement this scenario, you must perform the following steps: 1) Apply the fix for APAR IC32427 to all the 2.0.x brokers in the domain. 2) Migrate the existing 2.0.x Configuration Manager to V2.1 and apply cumulative maintenance zero to the 2.1 Configuration Manager. Once the first step is complete you will still be able to administer your brokers using the 2.0.x Configuration Manager. After you complete the second step you will be able to add 2.1 brokers to the domain. If the message set does exploit new MRM function, the deploy to a 2.0.x broker will fail with a BIP5293 message. Function that can cause this error includes: - Types with composition other than 'ordered set' and 'unordered set'. - Types with context other than 'open'. - Types with Types as members. - Types with Messages as members. - Simple Types other than 'binary', 'boolean', 'float', 'integer', and 'string'. - Type Members of type 'string' with no maximum length specified. You may specify the maximum length by adding an Element Value Constraint with the role of Max Length. - Types with a value. If your Compound Type has a value, there will be a 'Type' field shown on the main properties page for the type, below the 'Suspended from Use' field. A 2.0.1 or 2.0.2 Configuration Manager may co-exist with 2.1 brokers. Note that this co-existence scenario is NOT supported for application messages that specify a message domain of 'MRM' and a message format of 'XML'. In order to implement this scenario you must perform the following steps, IN THIS ORDER: 1) Apply the fix for APAR IC32427 to all the 2.0.x brokers in the domain. 2) Apply the fix for APAR IC32427 to the 2.0.x Configuration Manager. 3) Apply cumulative maintenance zero to 2.1 brokers, and add them to the domain. Once the first step is complete you will still be able to administer your existing brokers using the 2.0.x Configuration Manager. If you apply the fix for APAR IC32427 to the 2.0.x Configuration Manager before applying the fix to the 2.0.x brokers then message sets may fail to deploy. If the failure occurs, BIP5145 and BIP5280 messages will be reported by the broker. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ NEW ERA OF NETWORKS INFORMATION ------------------------------- Contents: Part 1: General Issues Part 2: New Era of Networks Formatter Part 3: New Era of Networks Rules Part 4: Documentation Issues ==================================================================== Part 1: General Issues ==================================================================== CMVC # 17303 CR # 253330 Description: If the ICU_DATA variable is not specified in a UNIX environment, DataFlowEngine (DFE) crashes. Work-around: You must specify the ICU_DATA environment variable in a UNIX environment. This defect will be resolved in a future patch release. -------------------------------------------------------------------- CMVC # 22900 CR # 261619 Description: You can create export files containing string literals x'0A' and x'1A', but these characters can cause problems when reimporting. Value x'0A' causes the record to split onto another line in the export file, and value x'1A' causes the following error to be written to the nnfie.log when importing on an ASCII platform: ERROR: Failed to separate and fetch a piece of the input data. Resolution: NNFie was modified to only write HEX-encoded literal values to the NNFie export file. This modification stops the export file from being corrupted. -------------------------------------------------------------------- CMVC # 24145 CR # 266308 Description: On AIX 4.3.3, the WMQI Data Flow Engine can fail when using Sybase as a New Era of Networks repository. The Data Flow Engine can abend. Work-around: Run with fewer message processing threads (message flows plus additional instances). You can also create more execution groups and spread the message flows among the execution groups. -------------------------------------------------------------------- CMVC # 24600 CR # 269179 Description: On AIX, when DEBUG MALLOC is turned on and when NEON Nodes are loaded during start-up of the Broker, there is corruption of the heap. Work-around: Use MQSI_PRELOAD to verify that the ICU libraries are loaded when the process starts. Set the following environment variable: export MQSI_PRELOAD=/usr/lpp/nnsy/bin/ libicuin18.a:/usr/lpp/nnsy/bin/ libicuio18.a:/usr/lpp/nnsy/bin/ libicuio18.a:/usr/lpp/nnsy/share/icu/data/libicudt18b.a -------------------------------------------------------------------- CMVC # 24629 CR # 267223 Description: While uninstalling both the GA and CSD component versions or just the CSD component version on HP-UX 11.00, the following error message appears: There is unmarked software which depends on software that is marked for remove. The remaining software cannot operate properly without the software you plan to remove. Work-arounds: To remove the CSD patch and leave the GA component: 1. Run swremove, click Options, and then Change Options to list the remove options. 2. Deselect Enforce dependency analysis errors in agent and click OK. 3. Scroll to the component in the Software Selection menu and do one of the following: - If the component was added by the CSD, then mark the component. The component will be marked Yes. - If the component was patched by the CSD, then press ENTER to open the Software Selection sub-menu and mark the specific patch level of the component to be removed. Select ..(go up). The component will be marked Partial. NOTE: If a Dependency Message Dialog appears when marking a full component or a component patch level for removal, ignore it and click OK. 4. Select Actions, Remove (analysis)..., OK, Yes, and Done. 5. Repeat steps 3 and 4 for each New Era of Networks component, starting with the highest numbered component and working down the list of components ending with the lowest numbered component (for example, n7nrfdk52, n6nrfx52, ..., n0infr20). To remove both the CSD and the GA components 1. Run swremove, click Options, and then Change Options to list the remove options. 2. Deselect Enforce dependency analysis errors in agent and click OK. 3. Scroll to the component in the Software Selection menu and mark the component. The component will be marked Yes. NOTE: If a Dependency Message Dialog appears when marking a full component for removal, ignore it and click OK. 4. Select Actions, Remove (analysis)..., OK, Yes, and Done. 5. Repeat steps 3 and 4 until all New Era of Networks components are removed from the "Software Selection" menu. This problem will be resolved in a future release. -------------------------------------------------------------------- CMVC # 24635 CR # 269174 Description: When moving files across operating systems, string literals are subject to code page changes. This can cause an import failure even when they have been changed to Binary. Resolution: All literals are now stored as HEX in the export files. -------------------------------------------------------------------- CR # 253460 Description: inst_db leaves files containing plain text passwords in its directory structure. Resolution: Scripts were created to delete files containing plain text passwords after an inst_db run. To use this feature of inst_db, run the following: o Windows NT inst_db.cmd o UNIX inst_db.sh These files run the inst_db program plus remove the text-encoded password files from your inst_db directories. --------------------------------------------------------------------- CR # 268274 Description: On z/OS, database commits cannot be issued from a New Era of Networks Formatter user exit because this impacts the WMQI broker. Resolution: On z/OS, the New Era of Networks Formatter user exits are now run in a child thread, allowing them to issue database commits without impacting the WMQI Broker. NOTE: COBOL user exits compiled with version 3.0 and higher can run in a multi-threaded environment. To run COBOL in a multi-threaded environment, the keyword RECURSIVE must be specified in the COBOL program on the PROGRAM ID statement, and the compiler option THREAD must be specified in the compile step. ==================================================================== Part 2: New Era of Networks Formatter ==================================================================== CMVC # 22158 CR # 257695 Description: If repeat count field is not within the immediate sibling format, parsing of repeating formats fails. Resolution: The algorithm has been modified so that if the repeat count field is not found in any immediate sibling, it walks up the format hierarchy in search of the field. -------------------------------------------------------------------- CMVC # 22898 CR # 261617 Description: On z/OS, the New Era of Networks Formatter GUI is unable to show conflicts when they exist. Resolution: NNFie failed to parse the command sent by the New Era of Networks Formatter GUI to report conflicts. NNFie was fixed to handle the command properly. -------------------------------------------------------------------- CMVC # 23080, 23098 CR # 262539, 262603 Description: On z/OS, an export file cannot be FTP or imported from a different operating system from which it was initially exported. Resolution: To migrate formats and rules between platforms, observe the following guidelines: - Use the NNFie and NNRie utilities provided with New Era of Networks Support for WMQI to migrate rules and formats between platforms. - Do not transfer export files that use different code pages between platforms by ftp. NOTE: Characters that are in the syntactic character set, that is, characters whose code points are invariant between most code pages may not be converted correctly during an ftp transfer. For example, the exclamation mark (!) is at code point 0x5A in some EBCDIC code pages and can be converted as the pipe symbol (|). NNFie and NNRie use the ICU function calls to convert character data. These calls are more sensitive to variations in code points between code pages. For more information, see the WMQI 5.6 System Management Guide, Process Overview section. -------------------------------------------------------------------- CMVC # 23881 CR # 266591 Problem 1: The New Era of Networks Formatter GUI fails to import or export if an nnfie.err file exists anywhere in the system path. Resolution 1: The GUI now deals with the nnfie.err file correctly and ignores files that are not related to the current import/export session. Problem 2: Using NNFie to import from the command line can cause the following error: Assertion failed: CNTL_NAME && CNTL_NAME[0]. Resolution 2: A fix was made in NNFie to eliminate the error. Problem 3: Using an Oracle 8.1.7 client, the New Era of Networks Formatter GUI can cause an assert on exit: 'DDE Server Window: nnfmt.exe - Application Error. Resolution 3: A change was made in the database session handling code to fix this. --------------------------------------------------------------------- CR # 260376 Description: It may appear that the Import/Export function of the New Era of Networks Formatter GUI does not work. In actuality, the problem lies in the path with the nnfie.err file. Resolution: The New Era of Networks Formatter GUI properly handles the files that NNFie creates and ignores files not associated with the session that the user is currently in. -------------------------------------------------------------------- CR # 268922 Description: When editing maps, errors display when no errors have actually occurred. The New Era of Networks Formatter GUI is attempting to retrieve rows from the database by passing the incorrect retrieval argument. Resolution: Now the correct argument is passed to the database. ==================================================================== Part 3: New Era of Networks Rules ==================================================================== CMVC # 23774 CR # 264519 Description: When using the Import/Export feature in the New Era of Networks Rules GUI, a db password is left in nnrie.dat file. Resolution: Remove the temporary nnrie.dat file when the import/export dialog terminates. ==================================================================== Part 4: Documentation Issues ==================================================================== CMVC # 25618 CR # 264846, 273815 System Management Guide Description: The following changes are required in Chapter 4, Formats and Rules Database Migration under the section Migrating Between Versions and Platforms: 1) On page 110, instead of the paragraph 'To export data....' substitute: If your export files are from a Version 1.1 database and you want to represent your literal values as ASCII strings, you must include the -p option when you run NNFie. You cannot use the -p option when exporting from a Version 2.0.1 or 2.1 database. 2) On page 111, the sentence beginning, 'For more information...' needs to be removed. 3) This information must be added to the following z/OS migration procedures: - from 1.1/2.0.1 Windows NT to 2.1 z/OS (bottom of p.114) - from 2.0.2 Windows NT to 2.1 z/OS (middle of p.115) - from 1.1/2.0.1 AIX/HP/Solaris to 2.1 z/OS (bottom of p.115) - from 2.0.2 AIX/HP/Solaris to 2.1 z/OS (bottom of p.116) For Windows NT Version 2.1, you must use an intermediate machine with Windows NT and WebSphere MQ Integrator to complete this migration. a. Create the nnfie.exp and nnrie.exp export files by running the NNFie and NNRie utilities on the source machine. b. Transfer these files to the intermediate machine. c. To import to WebSphere MQ Integrator for z/OS v2.1, use the version 2.1 NNFie and NNRie utilities on the intermediate machine while using an ODBC connection to import to the DB2 database on the target machine. ---------------------------------------------------------------------- CR # 275197 System Management Guide APAR# IY29253 - V5.6 VERSION OF THE NNSY GUIDES MISSING STEPS ON HOW TO GIVE MULTIPLE USERS DB ACCESS VIA TABLE ALIASES IN DB2. Description: The section of information, Assigning Permissions, is missing from the WMQI V2.1 System Management guide. Resolution: The following information needs to be added to the Configuration chapter: Assigning Permissions To assign permissions, you must create more than one user in your database. In Oracle The following procedure describes how to create database users in Oracle. To access e-Biz Integrator databases, users must be created and associated with the user role that was created during the e-Biz Integrator installation. The process for creating users in Oracle includes: - Creating users - Granting roles to users - Creating synonyms for database objects Creating Users You must create users to identify individual user names in the database. To create a user, type the following command and press ENTER. create user identified by ; where USERNAME and PASSWORD are required parameters. Granting Roles to Users To give users permissions to access the database data, you can grant permissions to an individual user or create roles with certain permissions and associate users with specific roles. A role was created for user access to the e-Biz Integrator database during the installation process. This role uses the following format: _ROLE where is your site-specific role name provided during installation. To grant the role to each created user: 1. Log in to the database as SYS. 2. Establish a connection to the Oracle instance using SQL Plus and the SYS username and password. 3. Type the following command to grant the role to the new user: grant _ROLE to ; The _ROLE role is granted to the user identified by USERNAME. NOTE: For rules permissions, each user can have only one role granted and this role must be the same for all users. Creating Synonyms for Database Objects To create synonyms for the e-Biz Integrator database objects, users must run a database script. To run the e-Biz Integrator synonyms SQL script: 1. Locate the nn_synonyms.sql script in the install.sql_rulfmt56\inst_db\tmp sub-directory of the installation directory. Log in to the directory where the nn_synonyms.sql resides. 2. Run the nn_synonyms.sql script for each user using the following command: sqlplus @@ nn_synonyms.sql> synonyms.log 3. Review the contents of the synonyms.log file for any errors. Ignore the errors related to dropping synonyms. In Sybase or SQL Server The following procedures describe how to create users in Sybase or Microsoft SQL server. The commands are run within the command line program isql, and all references to SQL Server include both Sybase and SQL Server. Except for changing passwords, these procedures are limited to either the system administrator or database owner. Users must have login accounts and a user name in each database they want to access. Adding login accounts, database users, and object permissions can be done by the system administrator, security officer, or database owner. A single person can occupy one or more of these roles. Check with your database administrator for information about your specific environment. The process includes: - Creating login accounts - Assigning users to a database - Defining user groups Creating Login Accounts Login accounts give users access to the SQL Server. To access a database, a login must be assigned to a user name to the databases the user wants to access. Only a system administrator or security officer has the authority to create login accounts. To create a login account, enter the following: sp_addlogin loginName, password [, defdb [, deflang [,sid [, encryptopt]]]] where loginName is the sysname with no default, where password is the login; login is sysname with no default, where defdb is the default database for the login (database is sysname with a default of master), where deflang is the name of the default language assigned when a user logs in to SQL Server (language is sysname with a default of NULL; if language is not specified, language is set to the servers current default language defined by the sp_configure variable default language). NOTE: Changing the server default language does not change the default language for existing logins. The language remains the same as the default language used when the login was added. where sid is the security identification number (SID) [sid is varbinary (16) with a default of NULL. If sid is NULL, the system generates a SID for the new login, specifying a value other than NULL, but the number must not already exist. SID is useful when you are scripting or moving SQL Server logins from one server to another and you want the logins to have the same SID between servers.], and where encryptopt specifies whether the password is encrypted when stored in the system tables (encryption_option is varchr(20) and can be one of these values: Value Description NULL (default) The password is encrypted. skip_encryption The password is not encrypted. The supplied password was encrypted by an earlier version of SQL Server and is used for upgrade purposes only. Assigning Users to a Database To use a database, the server login must be associated with a user name in the database. Only the database owner (DBO) can assign users to a database. From the database in which the user is to be added, enter the following: sp_adduser loginName [, nameInDB] [, group] where the loginName is the user's server login account, where the nameInDB parameter is the name for the user in the database, where the nameInDB defaults to the loginName if it is not specified, and where the group enables the DBO to add the user to an existing group in the database. If a group is not specified, the user is placed in the default group, PUBLIC. NOTES: - To add permissions both in New Era of Networks Rules and in New Era of Networks Formatter, you must add users as users not aliases. They must be members of the same user group. - SQL Server: Permission errors occur if the user is the same as the database owner (DBO). the user must be part of NNSYGRP, but cannot be the DBO. Defining User Groups During installation process, NNSYGRP is created for e-Biz Integrator users. Users must be linked to the NNSYGRP group to access the e-Biz Integrator databases. In addition, each database user, with the exception of the database owner, must be granted permissions to access objects within that database. To add users to NNSYGRP, do one of the following: - To use the sp_adduser procedure, enter the following: sp_adduser loginName [, nameInDB] [, group] where the loginName is the user's server login account, where the nameInDB parameter is the name for the user in the database, where the nameInDB defaults to the loginName if it is not specified, and where the group enables the DBO to add the user to an existing group in the database. If a group is not specified, the user is placed in the default group, PUBLIC. - To use the sp_changegroup system procedure, enter the following: sp_changegroup groupName, userName where groupName is the name of the group to which the user is added, and where userName is the database user name. In DB2 UDB The following procedures describe how to create database users in DB2. It includes the following: - Creating users - Creating aliases for database objects To allow other users to have access to the objects created during installation, a new user must be created with aliases to link the user’s objects to the objects in the installer’s schema. New users are added to the NNSYGRP group created during installation. You must be a member of NNSYGRP in order to access any of the objects owned by another NNSYGRP member. Creating Users To grant user access to the database, you must create additional user accounts at the local system level. Create additional users in the NNSYGRP group. Creating Aliases for Database Objects Each new user must run a database script to create aliases for the e-Biz Integrator database objects created during the e-Biz Integrator database installation. NOTE: To have assignable permissions, you must be a member of the system group NNSYGRP. Ask your database administrator to create aliases for OS/390. To create aliases using the nn_aliases.sql script: 1. Connect to the e-Biz Integrator database using the user ID of the user you want to add. 2. Establish a DB2 CLP session. Example: db2 connect to user using 3. Locate the nn_aliases.sql script in the \install.sql_rulfmt56\inst_db\tmp directory of the installation directory. 4. Run the nn_aliases.sql script using the following command: db2 -f nn_aliases.sql -l aliases.log -t 5. Review the contents of the aliases.log file for any errors. Ignore the errors related to dropping aliases. ---------------------------------------------------------------------- PMR # 07191 - System Management Guide Description: The WMQI 5.6 System Management Guide contains some errors. Resolution: Page 27, 29, 32, and 34: The NNOT_SHARED_LIBRARY items are incorrect. The tables should read: -------------------------------------------------------------- Database Type NNOT_SHARED_LIBRARY NNOT_FACTORY_FUNCTION -------------------------------------------------------------- Microsoft SQL Server 6.5, 7 dbt26sq165 NNSesMS6Factory Oracle 8 dbt26or806 NNSesOra8Factory Sybase CTLIB dbt26syb11 NNSesSybCTFactory DB2 dbt26db250 NNSesDB2Factory Page 134: The path for the example Makefile is incorrect. o Verify that the following drives are mapped. These drives are supplied in the $(INSTALL)/examples/Makefile. K:\ - The location of the appropriate database installation files. L:\ - The Microsoft Visual Studio 6.0 directory including vc98/bin and vc98/lib. The information should read: Verify that the following drives are mapped. These drives are defined in the example Makefile. To locate the example go to: nnsy\rulfmt56\examples\NNSYrf directory ====================================================================== ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SERVICE AND TECHNICAL SUPPORT ----------------------------- This is the first release of WebSphere MQ Integrator Version 2.1 for Sun Solaris, 5724A8202. It supersedes IBM MQSeries Integrator Version 2 for Sun Solaris, 5765D6700. 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 IC27350 - RFH2 THAT IS ADDED AFTER THE BODY OF THE MESSAGE SHOULD NOT BE IC27394 - INCOMPATIBILITY BETWEEN MQSI-TIMESTAMP-DATATYPE AND THE FORMAT 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 IC28452 - RULES NODE - SUBSCRIPTION REFORMAT OPERATION IS IGNORING THE IN 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 IC28607 - HEX FF VALUES NOT VALID FOR STRING TYPES 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 IC29180 - THE INTERVAL DATETIME TYPE DOESN T WORK AS DOCUMENTED IC29184 - XML-PARSE ENVIRONMENT INCORRECT IC29200 - XML MESSAGE GETTING TRUNCATED AFTER PROCESSING THROUGH COMPUTE IC29210 - MQSIMRMCOPYMSGSET CHANGES TWO ATTRIBUTES OF THE COPY IT MAKES IC29235 - SPURIOUS ESQL SYNTAX ERROR IN COMPUTE NODE WHEN SETTING A FIELD IC29371 - MQSI DOES NOT PROPERLY CONVERT HEX VALUE FOR UNICODE CODE-POINT IC29387 - MESSAGE TRANSLATION INTERFACE SEEMS TO HAVE A PROBLEM WITH THE IC29416 - COMPUTE NODE ADD MAPPING TO MRM LAYOUT GENERATES BAD ESQL IC29489 - DBCS MESSAGES WERE NOT CONVERT CORRECTLY FROM PC CODEPAGE TO H IC29506 - MQSI SUPERUSER IBMMQSI2 CAN CHECKOUT RESOURCES, BUT GETS AN ERR IC29632 - MQSI - INCORRECT STRUCLENGTH AND NAMEVALUELENGTH IN RFH2 LOOP IC29775 - MQSI BROKER DO NOT PASS THE MQMD CONTEXT INFORMATION WHEN A IC29789 - IT APPEARS THAT A CDATA SECTION IS MARKED AS "SPECIAL" IN THEXM IC29801 - MQSI V2 FAILS TO RECONNECT AFTER ORACLE HAS BEEN BOUNCED IC29992 - IF DEFAULTHEX IN THE DB TABLE HAS 1000 BYTES OR MORE THEN SPACE IC30171 - REORDER OF ELEMENTS FOR A MESSAGE SET, WITHIN A COMPOUND TYPE IC30173 - MQINPUT CATCH TERMINAL DOES NOT COMMIT DATABASE LOCKS. IC30195 - EG ABEND WHEN USING TWO MESSAGES OF THE SAME STRUCTURE WITHIN IC30424 - AFTER APPLIED CSD2, THE MESSAGE BROKER INTERNAL PROBLEM ERROR O IC30497 - ERRORS OCCURRING DURING MQSI GUI CONNECTION TO ORACLE 8.1.6 NE IC30653 - WHEN YOU UNSET A PROMOTED PROPERTY, DEFAULT IS LOST IC30673 - SQL SYNTAX CHECKER REPORTS ERROR ON VALID SYNTAX WHICH DEPLOYS IC30970 - GLOBALLY CO-ORDINATED FLOW INVOKING NEON PARSER CAUSE XA PROBLE IC31150 - GETTING AN ERROR BIP1835E. THE CREATE RUNTIME MESSAGE DIC. IC31345 - COBOL IMPORT PROBLEM WHEN LEVEL NUMBERS FIELDS NOT ASCENDING IC31362 - MESSAGE GROUPING FUNCTION ONLY PROCEED THE FIRST MESSAGE IC31445 - DEFINING A STRING MRM-MESSAGE ELEMENT AS NULL-TERMINATED WITHIN IC31787 - MQSICHANGEUSERNAMESERVER ACCEPTS INVALID USERID, AND CHANGES IC31806 - PROBLEM IMPORTING COBOL COPYBOOK. IMPORTER DOESN T LIKE EXTRA IC31825 - BOTHRESH AND BOQNAME NOT WORKING PROPERLY WHEN ERROR OCCURS ON 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), IY17561 - RULES NODE NOT PROCESSING A MQS EXPIRY NO PROPAGATE FIELD IN SU 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 IY17806 - WHEN BROKER HAS LONG CONNECTION TO DATABASE, SOMETIMES THE CONN IY17808 - XML PARSER ADD TRUE TO THE END OF XML DECLARATION. IY18104 - CAST FUNCTION INTERMITTENTLY FAILING IY18146 - IF THE BROKERDB IS ORACLE, ADDITIONAL NLSPATH IS REQUIRED. IY18245 - PERFORMANCE FIX TO ADDRESS INEFFICENCY IN BIT STREAM FOR 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% IY19382 - DATAFLOWENGINE LOOP IY19787 - BIP1205E DATABASE EXCEPTION SQL0302N ON DEPLOY IY20050 - ERROR WHEN OUTPUT TERMINAL THAT IS LABELLED WITH A NAME THAT IY21179 - DFE COSUMING HIGH CPU AND HANGING WITH NO ERRORS IY22261 - BROKER IN AIX SMP ENVIRONMENT MEMORY MANAGEMENT VULNERABLE TO F IY23087 - EXCESSIVE CASHING PERFORMED BY MQSI CAN LEAD TO MEMORY HEAP The WebSphere MQ support page is located at: http://www.ibm.com/software/ts/mqseries/support from which you can obtain the latest information about various WebSphere MQ topics including :- - Hints and Tips - APARs and Fix Packages - FAQs - Support downloads - Newsgroups For the latest versions of WebSphere MQ Integrator Version 2.1 for Windows NT and Windows 2000 documentation see the following Web page on the MQSeries Web site: http://www.ibm.com/software/ts/mqseries/library/manualsa/ The README file shipped with WebSphere MQ Integrator Version 2.1 contains information that was current at that time. The very latest information is available at:- http://www.ibm.com/software/ts/mqseries/support/readme/index.html ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ CSD HISTORY =========== CSD02 - U482016 ________________ This is CSD02 for WebSphere MQ Integrator Version 2.1 for Sun Solaris. It is delivered via PTF U482016 for APAR IY28082. It contains fixes for ALL the problems listed below: Name - Abstract IY28082 - CUMULATIVE MAINT #02 FOR WEBSPHEREMQ INTEGRATOR V2.1 FOR SOLARIS IC31345 - COBOL IMPORT PROBLEM WHEN LEVEL NUMBERS FIELDS NOT ASCENDING IC31766 - MQSIREPORTTRACE DOES NOT WORK CORRECTLY WITH USERNAMESERVER COM IC31806 - PROBLEM IMPORTING COBOL COPYBOOK. IMPORTER DOESN T LIKE EXTRA IC31916 - MESSAGE CONVERSTION TROUBLE (SI/SO HANDLING) WITH MQSI IC32037 - MQSI ERROR RFH2 MESSAGE FAILS TO CONVERT. REASON 2116 - IC32047 - CONTROL CENTER HANG DURING IMPORT AND/OR DEPLOY LARGE NUMBER OF IC32440 - ASSURED DELIVERY OF MESSAGES TO MQE NODES IN MQSI BROKEN IC32690 - BIP5502E FAILURE UNDER MQSI V210. IC32828 - RUNTIME ERROR EXPERIENCED BY SETTING AN EXTENDED DECIMAL FIELD IC32868 - ERROR BIP1812S IS RECEIVED WHEN IMPORTING C HEADER FILE. IC32871 - USING ALT+CTRL+SUPP DOEN NOT REBOOT THE MACHINE DUE TO 2 EG IC32896 - IMPORTING A C HEADER FILE ON A REMOTE CM FAILS IF A LOCAL IC32918 - BIPCONFIGMGR.EXE TERMINATES ABNORMALLY WHEN MACHINE IS REBOOTED IC32929 - ESQL STATEMENT IS DELETED IF COMMENT DOESN'T MATCH CC LOCALE IC33040 - INSUFFICIENT DETAIL ON IMPLEMENTING THE PASSTHRU FUNCTION. IC33053 - ERROR BIP0067E WHEN SWITCHING THE CONTROL CENTER ON THE MACHINE IC33066 - MQE NODES SENDING DUPLICATE MESSAGES IY16738 - START OF BROKER CONFIGURED TO USE ORACLE GIVES AN ERROR - UNABL IY21734 - MQSI CRASHED WHEN ADDITIONAL INSTANCES OF A MESSAGE-FLOW WERE IY26160 - BIP2088E AND BIP2106E AT DEPLOYMENT OPERATION. IY26427 - A BROKER RUNNING WITH A SCADA NODE LOCKS UP IY28136 - PART OF DBCS CHARACTERS CHANGED TO DIFFERENT CHARACTERS WHEN IY28181 - NEONRULES AND NEONFORMATTER WERE NOT ABLE TO BE IMPORTED. IY28384 - CONTROL CENTER FOR V2.01 INCORRECTLY IMPORT VIRTUAL IY29050 - ORA-03113: DFE TERMINATES AFTER A LOSS OF COMMUNICATION WITH DB PQ57196 - MESSAGES COMING FROM OS/390 TO AIX/NT THROUGH NETVIEW FAIL TO PQ57697 - ERROR OCCUR WHEN MQSICHECKSETUP IS CHECKING THE DSNAOINI FILE. PQ57991 - DATAFLOWENGINE GOES INTO LOOP IF TRACE NODE IS USED AND THE f13625 - Output Parameters And Stored Procedures f18699 - Multipart Message support f21571 - Optimize CC when performing commands on list of entities f21825 - Enhanced Select Function f22439 - NULL Handling - MRM Parsers f23840 - Enhanced MOVE statement f23842 - Enhanced CREATE function f24317 - Allowing expressions in field references f24543 - Further implementation of MM messages for runtime broker f24706 - Relax delimiter limitations in TDS messages. f24859.1- Add new Data Element Separation method "Undefined" f25032 - Natural ESQL support for local elements & attributes f25127.1- EUI changes for Enhanced THROW statement f25730 - Modifications to DTD Importer handling of PCDATA Elements s25795 - C,D,F packed flags in CWF 19930 - MRM BIP5167 error message bad substitution 20220 - BIP5117: Message full of meaningless numbers and terms 20685 - MRM/CWFLayer: CT with base type elements not properly rendered 20737 - Event ID 3100 not found 20787 - ERRMSG: MRM BIP5294 message content 21542 - Netview not seeing all response messages from MVS command 21989 - MRM MRMB0406 padding char SPACE 22232 - MQSI2.1:Default value of Transaction mode in data nodes 22831 - Unhelpful BIP5170 when input CWF msg does not match definition 22962 - GUI:User Role 'Op. Domain Controller' has misleading help text 22963 - GUI:User Role 'Topic security administrator' misleading help 23120 - MRM: Event 5199 Description inaccurate 23293 - MRM-problems writing simple types to bitstream. 23334 - CCSID and ENCODING clauses not reported in User Trace 23377 - MRM- CC online Help needs "Check-Out List" explanation adding 23381 - MRM BIP1929 message content 23536 - BIP2801E on broker startup if DB2 not installed 23589 - Trace node properties - File Path 23755 - MRM-DTD Importer imports an element with a strange icon 23855 - OVERLAY function causes unexpected truncation 23899 - missing repetitions incorrectly handled 23916.1 - MRM-Element Value value should not be mandatory 24225 - PubSub RC 3073 to ReqUpdate after successful RegSub 24284 - MRM-Imported DTD cannot be deployed 24294 - ERRMSG: 5339 Dictionary Iterator Error Event Viewer Insertions 24296 - SQLCODE and SQLNATIVEERROR wrong when TEODBE=NO 24297 - EXCEPTION_ACCESS_VIOLATION (C0000005). 24359 - ERRMSG: Wellformed XML but 5285 gives insufficient diagnostics 24364 - Repeating choice not working for Tagged Fixed Length 24364.1 24379 - MRM-Extractor logs only show last message set 24385 - Can't get rid of warning box in MRM after changing a choicetype 24416 - Oracle 8.1.6 SEGVing in Malloc 24417 - ERRMSG: MRM Type composition sequence error diagnostics poor 24420 - CWF Repeats not working with Choice Type 24421 - STRESS: SQLstate HY010 on aggregation test 24438 - Choice with compound elements not working for some TDS formats 24450 - ERRMSG: TDS 5436 missing Insertion for Element Name 24456 - TDS-XML : MRM give an existing identifier who can't be altered 24461 - MRM incomplete messageset errormessages need substitution vars 24469 - Rules can no longer reference fieldnames containing parentheses 24477 - BIP5339: Confusing error caused by simple mistake 24481 - STRESS: Extra added by mrm parser 24484 - SEGV in broker when DB2 terminated 24488 - MRM- Base type data causes following child lost from bitstream 24496 - Invalid MF copy/assignment while broker copy/paste 24522 - output of ''asdf'' instead of 'asdf' 24523 - MRM Cobol import of extended decimal 24524 - impexp with -x swaps public and system ids. 24542 - ERRMSG: BIP 5512 Insertion not working 24550 - Message Format on Input Node supplies incorrect value 24558 - In the XML plugin, the DOCTYPE text property currently has maxl 24559 - Parsing of unresolved choice not working for tds formats. 24564 - Generic XML : Bad DOCTYPE causes DataFlowEngine to loop 24568 - Cannot parse TDS repeating embedded compound types 24592 - Error with coordinated transaction value 24602 - BIP2605E should not be issued for OS/390 (as use RRS for TC) 24619 - GUI Check Out list does not complete 24620 - MRM Invalid datetime allowed on output TDS 24621 - MRM-DATETIME Bizarre week in month behaviour when handling the 24624 - MRM - XML as reserved word stops you defining an XML namespace 24627 - At the moment when the extractors run, the log files for it are 24628 - DFE failure with large MRM message 24638 - MRM-DATETIME Make binary and ICU DATETIME parsers have common b 24674 - Ongoing TDS Parser work with EDIFACT Imp 24697 - Break point infront of AggregateReply node corrupts message 24709 - TDS Problems with EDIFACT smaple from IMP 24710 - Embedded message support for compute node customizer. 24716 - Multiple calls to hasnext cause TDS to fail 24739 - Can't deploy messageset with embedded msg and C lang binding. 24746 - Nested repeats for zero occurrences not working correctly. 24758 - Do not handle Nested message from within MatchEmbeddedCompound 24810 - Database SELECT does not work any more 24831 - Gen XML: setElementChanged is inefficient 24834 - Root message name being lost 24846 - MRM- Base Type BINARY for XML not working 24850 - BIP1836E is showing wrong log names. 24870 - AIX NNSY messages are not being found 24877 - AggregateReplyNode binds incorrectly to VARCHARs 24878 - Reference variables in a SELECT's FROM clause does not work 24889 - Inserts in exceptions thrown by the THROW statement are wrong 24906 - MRM- XML CDATA tag for BINARY element (Null Handling related?) 24908 - MRM BIP5521 output extended decimal in codepage 1200 24961 - Uuid generation failures bring down Config Mgr 24968 - Unable to go from one message set to another 24979 - MRM/Length and Repeat Count Types are wrongly editable combo 24986 - Improve performance of CC<->CM MRM interaction 25010 - Broker restart fails with Aggregation on SQL Server 25028 - Config manager gets CPU bound when deploying large message sets 25029 - Parsing of unresolved choice not working for tds formats. 25037 - Repeating choice failing for TDS when choice is compound type 25041 - Choice with compound elements not working for some TDS formats 25060 - MRM-Simple message brings down the execution group 25089 - MRM- NullPadFill shouldnt be offered for certain PhysicalTypes 25123 - Mnemonic escape character not translated properly in TDS 25152 - XML Extractor doesn't complain when attributes occur after elem 25168 - Incorrect string in Interpret Element Value attribute dropdown 25216 - Attributes cannot be specified on the XML Root Tag Name 25226 - Negative value in 'numeric' field causes DFE to exit() 25227 - MRM - TDF & XML parser does not handle a Message Type Path 25232 - TDS defaults not displayed correctly 25243 - Rules for REPEAT,Min/Max Occurs on connection tab are incorrect 25244 - Repeating choice not working for Tagged Fixed Length 25247 - Message/explanation/user response text in :MSG./:EMSG. tags. 25248 - MRM CWF Null handling datetime NULLLogicalValue causes BIP5168 25257 - MRM/Length and Repeat Count Types are wrongly editable combo 25260 - MRM CWF Length Value Of eligible fields not displayed 25262 - Can no longer use CWF Repeat Count Value of field in GUI 25300 - MRM- Base type Decimal causes Internal MTI Error 5354E 25302 - Apply button wrongly greyed on CompoundType TDS view 25312 - MRM- TDS Writer Problem with Simple Types 25316 - MRM- CWF Datetime String not being recognised 25322 - MRM-CWF Tab, Boolean Value fields are not editable. 25323 - Console output not coming back to USS via oeconsol command 25338 - MRM BIP1951 Wrong substitution 25339 - GUI Check Out list does not complete 25340 - DATABASE exception shouldn't be accepted in THROW syntax 25341.1 - Increase timeout in MQConnection for MRM_WAIT_INTERVAL 25341.3 - Config. Mgr. gets knotted after 1350 timeout. BIP1350E 25341.3.1 - CC sends to CM several times same request after Time-Out. 25341.8 - Add filtering for MRM member collections 25342 - Backend still won't allow ^ in an identifier when it is checked 25347 - TDS input, empty values not being recognised as NULL 25355 - XML undefined attributes on 390 not rendered correctly 25356 - TDS Validator - ensure DEST=Undefined if CT composition=MESSAGE 25358 - Sybase broker hangs on restart w/multiple msg sets 25361 - Trace updates for improved MOVE command 25362 - nullPointerException when trying to check a Message Flow 25364 - MRM - Absolute Message Type Path doesn't work with Message Type 25366 - MRM Check out attempted even though messageset is frozen 25370 - Incorrect data element separation for type cmposition = message 25375 - Default DateTime ElementValue causing an exception on deploy. 25378 - Unable to SET a REFERENCE to a DECLARED variable 25385 - MRM COBOL import fails if >1 space after OCCURS 25386 - DTD Importer - Type content should be closed to model valid DTD 25391 - UNA and ISA written out with extra delimiter 25391.1 - GUI must allow non empty delimiter in some cases 25394 - CacheManager should be symmetric about UUID usage 25409 - CC not allows duplicate name on message set in special case 25414 - Parsing of repeated nesting items not working 25419 - MRM-DATETIME Bizarre week in month behaviour when handling the 25424 - Generation of dictionaries on delta deploy 25428 - ERRMSG: CWF 5181 Insertions not working 25432 - MRM BIP5440 incorrect substitution 25434 - CC model optimisations are not reset when exceptions occur 25445 - Error introduced after GA for bip8120.msg 25447 - Bracket flagged in error in function call 25451 - TDS Validator - ensure DEST=Undefined if CT composition=MESSAGE 25457 - EUI MRM Tagged Delimited requires Tag Length/Separator 25482 - Recursive multipart mess causes DFE abend TDS->XML 25493 - TDS Writer is too memory intensive 25509 - Tagged Delimited Choice with compound elements failing. 25525 - bip5503.msg, error in the text of the message. 25532 - Storage not released by DataFlowEngine after PROPAGATE 25533 - DataFlowEngine and ConfigMgr terminate on NT user logoff 25547 - MRM TDS unresolved choice 25550 - Inconsistent format TDS->XML vs XML->TDS with embedded messages 25558 - MRM-Using Message Type Path with CWF causes broker abend 25566 - In the EUI, Attributes cannot be specified on the XML Root Tag 25585.1 - The EUI needs to validate dateime values entered. 25602 - Bad expiry value causes MQe message flow failure 25610 - uid(0) causing problems in changebroker and 25617 - Modification of message identifiers and XMLName by DTD Importer 25662 - XML msg without top level causes DFE process to go into spin 25666 - Wrong path is generated for embedded message. 25668 - MRM- Null Handling CWF String input blank NullLogicalValue 25675 - TypePrefix incorrectly handled 25696 - keywords CREATE FUNCTION, PROCEDURE, REPEAT case sensitive 25697 - MRM Check in all with new 'message' compound type 25699 - MRM- Broker Abend with XML Input 25723 - XML: encoding null NUMERIC, fails to parse on NULLElement 25727 - DTD Importer doesn't support recursive elements 25741 - MRM finalize messageset not reflected in GUI 25745 - CWF length units End of Bitstream not working 25753 - TDS Parser does not support syntax level B defaults 25761 - Unable to set (XML.Attribute)Type using SELECT 25763 - MTiImbparser - support for string -datetime conversion 25783 - First week of year not used in runtime 25794 - Input node parser name attributes not being set 25802 - Valid syntax gets flagged in error 25827 - MRM- Hex Delimiter Substitution wrong in tdscommonutils 25842 - MRM- Null Handling TDS Fix Length Float NullLog / Pad confusion 25868 - Add Message List for a closed compound type is not filtered 25869 - Incorrect Value set for ISA INdexes 25885 - STRESS: Core File from UserNameServer in Mixed test 25895 - Repeating Tagged Fixed Length choice type is still failing. 25917 - Contol Centre loops trying to expand message with lots of child CSD01 - U481438 ________________ This is CSD01 for WebSphere MQ Integrator Version 2.1 for Sun Solaris. It is delivered via PTF U481438 for APAR IY26924. It contains fixes for ALL the problems listed below: Name - Abstract IY26924 - CUMLULATIVE MAINTENANCE #01 FOR WEBSPHEREMQ INTEGRATOR FOR SUN IC30350 - CONFIGMGR NOT DETECTING A COMM LINK FAILURE TO DB2, GIVES IC31802 - GETTING PARSING ERRORS WHILE USING REPEATING FIELDS WITH SECOND IC32018 - WHEN A REFORMAT OPEARTION IN A NEON-MQSI-ENVIRONMENT DOES NOT IC32309 - WITHIN THE COMPUTE NODE, WHEN CODING A PASSTHRU FUNCTION IY16738 - START OF BROKER CONFIGURED TO USE ORACLE GIVES AN ERROR - UNABL IY24362 - CONVERSION INCORROUT FROM OS/390 TO OS/400. IY25465 - SCADA NODE STOPS TRANSMITTING MESSAGES THROUGH FLOW f16275 - Command line deploy utilities f22449.2- Add non loaded skip node to the workspace when it is check out. f23369.2- ESQL Syntax Checker:Removing field names checking in path f24217 - Complete set of diagnostic streams written under single JOBLOG. readme - README updates for CSD01 17377 - mqsilist shows old 'default' execution group label after rename 18007 - Cannot set breakpts in main flow whilst in subflow 18405 - mqsichange with -a only does not work 18578 - mqsicreate / mqsichange -t on AIX has no error msg 19673.4 - Handling errors during lil loading on OS390 (and related) 20308 - MRM-mqsimrmimpexp gives wrong errMsg when MsgSet is incomplete 20408 - report trace command does not produce output on OS/390 20847 - MRM-BIP1930E is not displayed correctly 20946 - DateTime - MRM Parser Support 20955 - MRM Data Converters - handling overflow 21208 - The control centre users don't accurately reflect real users 21208.1 - Primary group not enumerated on Unix Platforms. 21569 - OS390 Java Plugin Node Message Flow Failure 21724.1 - New message for 21724. 21843 - MRM-DATETIME processing ignores Era 22144 - MRM-self-defining messages unacceptable to MRM. 22233 - The call ImbWstring MtiImbParser::getTypeProperty() 22249 - MRM TDS Writer is writing TagDataSeparator when not required 22521 - Control Centre unacceptably slow when adding types to workspace 22548 - MRM-Modified Self defining elems cause DI prob. 22548.1 - XML - Parsing of compound types with attribute values results 22654 - 0 occurrences of repeating elem/comptype failing for CWF input. 22687 - Java trace not working from registry setting 22751 - GMTTIMESTAMP gives incorrect results 22836 - MRM-XWF Encoding not working 22925 - BIP1802: error message gives wrong name for database. 23037 - The time zone in the JVM is being set explicitly to GMT. 23147 - Typing 'NNRie' produces help text, core dump. 23232 - TDS strings containing just spaces fail on AIX 23283 - Poor performance of TextBufferReader::getStringSection 23309 - Change description on STEPLIB_NAME 23316.1 - Maintain list of delimiters to improve TDS performance 23316.2 - In TDSParser SetReservedChars not reset for service string 23318.1 - Memory Leaks in MRM (part 2) 23341 - MRM: CWF Parsing of Choice Message Fails 23351 - 390 debugger will not start 23359 - Swift importer fails with "attribute name is not defined" 23404 - Unnecessary bracket in syntax description of "mqsichangetrace" 23429 - Dataflow engine terminates on large (cust mfs) debug deploys 23453 - Trace formatting-ImbMqOutputNode::evaluate 23476 - Expiry event not available 23543 - Boolean default values not being written out on Unix and 390 23545 - MtiImbParserFactory in stdout 23558 - Ambigious behaviour for TDS messages with choice type. 23568 - Repeating choice not working correctly 23568.1 - Some problems with choices. 23577 - STRESS: Code dump in mixed test with NNSY nodes on HP 23581 - Command line deploy - misleading message 23583 - CWF output not working for nested choice 23584 - Cmd line deploy - no message returned when -f and -a flags used 23599 - Currently the Java node API does not have an onDelete( ) method 23603 - STRESS: Resource Manager errors in XMLtoMRMCWF 23605 - Trace entries missing in textbffr.cpp 23614 - MRM-Errors handling binary DATETIMEs 23622 - mqsiimportmsgflows - no msg flow in Control Center 23627 - dump formatter abends no memory 23651 - Add fields in the ESQL and the new field gets concatenated 23667 - STRESS: SQL server error in aggregation tests 23670 - MRM-DTD Generator does not append * and + to appropriate elems 23690 - Update .bat files 23697 - Some console messages have old format 23701 - cb command converts mixed case lilpath to lower case - 23703 - MRM-problem with encoding for base type binary. 23713 - bipjrst reset broker has problems with clearing one queue 23719 - wmqpslist coredumps on Unix 23722.1 - Implement MRM implicit casts at the tree level 23723 - Wrong description of console command is displayed 23738 - Shipped Merant ODBC driver still "available" after uninstall 23765 - abend in ImbUGI because of wrong linkage 23784 - Unable to debug failing flow 23786 - MRM-can assign any string value to Boolean elements. 23796 - MRM BIP2160 trying SWIFT -> CWF 23805 - EXCEPTION_ACCESS_VIOLATION (C0000005) 23819 - FI events during TDS parser destruction 23821 - MRM BIP1951 if no length on CWF endofbitstream 23852 - STRESS: Core File from UserNameServer in Mixed test 23856 - Refresh New Era SysMgmtGuide in docs pkg 23861 - MRM Add mapping for element in nested type 23882 - TDS:LengthValueOf is enable if embedded simple(element or type) 23892 - MRM: Deleting types can cause database corruption. 23894 - MRM rounding of CWF packed decimal on input 23896 - MRM CWF null chars in fixed length strings 23899.2 - TDS Writer related fixes for defect 23905 - MRM-DTD Imprtr,typng non existent filenme doesn't throw an err 23906 - OS390: mqsicreatebroker allows invalid broker name. 23907 - Disconnecting Scada client on HP-UX causes EG failure 23915 - MRM-DTD Imprtr creates uncheckinable cmpts names frm valid DTDs 23921 - MRM-all inline DTD data dropped on output. 23922 - MRM BIP5285 with TDS unresolved choice 23929 - Parsing BaseType in TDSParser 23947 - Config manager and broker JVM's share a CLASSPATH 23961 - Abend during MbSQLStatement object usage 23966 - MRM BIP1950 because EDIFACT Boolean Null not set 23972 - STL exception in TDSValidator::ValidateMessageTypeMembers 23974 - Memory leak in MRM2 with TDS fix 23983 - IC01 ref to the jar files jfaceall and argo 23994 - No error messages for out of range timeoutvalues 23997 - CoreDump on Mqsistop + unexpected syslog messages. 24001 - MRM BIP0068 on save to shared 24005 - Stopping and starting broker causes database errors 24038 - Unable to connect from English CC to Chinese ConfigMgr 24044 - Problem with TDS repeating structures. 24047 - Unable to change type composition from sequence to choice. 24055 - Database deadlocks on SQLServer when unknown timeout set 24061 - MRM2 Data Datatype test failing 24068 - MRM BIP5339 input EDIFACT/TDS output XML 24073 - STRESS: Memory Leaks shown in Bitstream Parsing tests 24075 - CWF Repeats not working with Choice Type 24077 - Unexpected response to invalid input 24078 - Problem with compound elements/types within a choice type. 24089 - MRM: TDS Mnemonics aren't used by the TDS Parser or Writer. 24089.1 - MRM: TDSWriter not writing mnemonics 24098 - Memory used after being freed in choice parse 24102 - MRM-error message 5503 when copy input root to output root. 24104 - MRM-problem rendering compound element with base type. 24110 - Can't check in repeating choice with Repeat Type as "Value of" 24112 - SIGSEGV raised but DFE did not core dump 24115 - MRM: TDS Parser causes execution group restart when RFH2 type t 24126 - DataCnv::IntFromInt32 and DataCnv::IntFromInt64 need to check f 24133 - MRM: STL Errors & exec group restart on Debug builds 24144 - MRM - INT64_MAX is not defined properly on AIX 24148 - MRM TDS fixed length output max occurrences instead of actual 24152 - MRM-broker abend following TDS length delimited message input. 24175 - NNRie and the Rules GUI rearrange long rules 24176 - MRM TDS BIP5425 on fixed length repeat structure 24177 - RC=9 from BIP$JCVP verification job. 24180 - TDS Fixed Length Choice padding is incorrect. 24181 - MVS: Broker will not start with DB2_CONVERSION=MIXED 24203 - MRM EDIFACT UNA not processed in runtime 24206 - MRM-standalone clause in xml declaration not suppressed. 24220 - TDS read error, integer -99 out of bounds 24223 - The XL plugin doesn't return the default for for anonymoud simp 24229 - NNFie loses data from Substitute output operations 24230 - Error with TDS decimal->CWF packed decimal when precision set 24235 - MRM-MRMB0425 is failing on all platforms 24235.1 - Same problem as 24235 but on parsing. 24240 - The defaults for XML SYSTEMID and PUBLICID are the wrong way ar 24252 - MRM BIP5426 Tagged fixed length repeating elements 24260 - Using mqsideploy the wrong BIP message is displayed 24261 - MRM-DTD Importer produces AQM7610E when importing a DTD 24263 - TDS fixed length compound choice type not working. 24265 - Parameters in call to IMBDate are reversed 24273 - CPI/MTIIMBParser Error messages 24277 - MRM-MRMB0815 & 1115 fail on OS/390 24280 - NNSY Formatter GUI does not import format definitions 24288 - ERRMSG: TDS Missing Group Indicator BIP5437 insertion 24290 - MRM TDS X12 default settings wrong 24293 - Some CWF exceptions logged even though they are not errors 24303 - Incorrrect message number used for incomplete message set 24319 - MRM-MRMB1815 is failing on Windows 24321 - Pointer returned from cniGetEnvironment is wrong. 24326 - IC01 export return codes (nonexistant flow) 24327 - Parsing of EDI problem 24340 - Requested changes to NNInstall-Driver.sh 24346 - ERRMSG: TDS Incorrect Issuing of 5422 24354 - definition of UINT32_MAX has a ... at the end of it 24361 - ERRMSG: CWF 5181 Insertions not working 24368 - MRM BIP1949 trying to check in Type 24381 - ERRMSG: Generation of new BIP msg req'd for use by TDS Parser 24392 - ERRMSG: CWF Expected BIP5520 Not Being Thrown 24395 - ERRMSG: BIP5519 Insertions not working 24402 - MRM- Generate Message Book HTML contains nonsense min/max info 24406 - mqsifindandreplace replaces keyword with quoted lowercase equiv 24411 - MRM-elements rendered as xmlAttribute not found. 24412 - MRM-XML/Perf: broker keeps opening ccsid 0 24413 - MRM: TDSWriter has problems writing out message, and gives litt 24431 - XML message in Double Byte char set causes XML ParserException 24437 - Syntax error reported from quoted field references 24453 - MRM BIP8184 message content unclear 24457 - IC01: -r flag used in mqsideploy causes timeout 24462 - onDelete method java call stops msg flow deletion. 24474 - Dictionary delete memory that was allocated with malloc. 24475 - MRM BIP1812 manipulating large message 24560 - Field in ENVFILE not updated 24581 - Missing line feed escape in BIP0001E error message 24656 - MRM-DATETIME CSD1 regression. Packed decimal DATETIMEs not pars 24661 - wrong description of Compound Type attribute Type Composition 24675 - MRM - CWF->CWF Cannot write out to different output msg 24698 - MRM-Irrelevant ESQL makes message fail inexplicably GA PTF - U481172 ________________ This is the GA PTF for WebSphere MQ Integrator Version 2.1 for Sun Solaris. It is delivered via PTF U481172 for APAR IY26071. It contains fixes for ALL the problems listed below: Name - Abstract IY26071 - CUMULATIVE MAINTENANCE #00 FOR WEBSPHEREMQ INTEGRATOR FOR SUN 17516.1 - MRM BuildTimeDictionary S202 Compatibility 19673.3 - Handling errors during lil loading on OS390 20950.2 - MRM - Integer Backward compatibility support - RTD Extractor 21724 - S000-L010828_D Java exception when starting execution group 21930 - Oracle XA on NT makes the execution group unresponsive. 22534 - MVS: Data corrupted when Inserting DBCS string in Database node 23218 - MRM MRMB5914 extended decimal dbcs codepage 23351.2 - 390 debugger will not start 23379 - Choice has stopped working for CWF messages 23683 - STRESS:Abend file produced during destruction of a locale objec 23813 - STRESS: Memory corruption with large repeating message 24013 - MRM-cwf error writing to bitstream causes broker abend. 24031 - NNSY Updates to CIF file ( mqsicompcif) 24056.1 - Rename WMQI_REGISTRY 24079 - Allow import to proceed even if importing attributes fails. 24255 - Update classpath within envnt.bat 24256 - BIP$JCVP job should return Java 24323 - Sample nnsyreg.dat needs changing to include NNFIE session ####### ------- end of file MEMO.PTF ------------#######################