######################################################################## # # # COMPONENT_NAME: WebSphere MQ Integrator Broker # # # # FILE: MEMO.PTF # # # # Program Number 5724-D07 # # (C) COPYRIGHT International Business Machines Corp. 1999, 2000, 2001 # # 2002 # # All Rights Reserved # # Licensed Material - Property of IBM # # # # US Government Users Restricted Rights - Use, duplication or # # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # # ######################################################################## PTF Memo for IBM WebSphere MQ Integrator Broker V2.1 for Multiplatforms ----------------------------------------------------------------------- The memo.ptf file contains information you need for updating IBM WebSphere MQ Integrator Broker Version 2.1. This memo.ptf file corresponds to CSD05 which is defined as the following PTFs :- - U200196 for Windows NT/2000 - U487643 for AIX - U487769 for Sun Solaris - U487768 for HP-UX This memo.ptf file 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 ---------------------------------------- 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 the Applying Maintenance Appendix of the WebSphere MQ Integrator Broker Installation Guide, but must be amended by any changes documented below. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ DOCUMENTATION CHANGES --------------------- IC36010 - DOCUMENT USE OF CLEARMESSAGE FOR JAVA PLUGIN NODES Use of the Java plug-in method clearMessage is not documented. Not using this method can lead to growth in memory usage by the broker. The WebSphere MQ Integrator Programming Guide, SC34-5603-03, Chapter 6; Implementing a plug-in node or parser, section; Implementing a node in Java, subsection; Building an output message, will have a new subsection entitled Propagating the message as follows: Propagating the message Before you propagate a message, you have to decide what message flow data you want to propagate, and which of the node's terminals is to receive the data. You should finalize the message before you propagate it. After propagating a message, you must delete the output message. For example: 1. To propagate the message to the output terminal "out": MbOutputTerminal out = getOutputTerminal("out"); out.propagate(outAssembly); 2. To delete the output message: outMessage.clearMessage(); Any other messages created during the processing of the node should also be deleted in a similar manner. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ PQ67615 - CNIELEMENTCHARACTERVALUE/CPIELEMENTCHARACTERVALUE CAUSING 0C4 When using either cpiElementCharacterValue or cniElementCharacterValue using an incorrect value in the length value can result in 0C4 abends or in overwrites of user storage. The Programming Guide specifies that the length parameter of these calls should have units of bytes. This is incorrect; the length should be provided in units of CciChar. The Programming Guide (SC34-5603-03) will be changed in Chapters 8 and 9 so that the following functions are now documented as taking CciChar as the unit for the length parameter: cniElementCharacterValue cniElementDecimalValue cniElementName cpiElementCharacterValue cpiElementDecimalValue cpiElementName ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC35011 - IMPROVE DOCUMENTATION REGARDING NULL HANDLING The documentation regarding how WebSphere MQ Integrator handles NULL processing will be be updated to more clearly outline and explain the process as follows :- 1. Websphere MQ Integrator Working With Messages, SC34-6039-01, Chapter 4, The MRM logical message model; Section, The broker's view of the logical message model; Sub-Section, Using ESQL to manipulate the message tree; Null Handling will have the following information added at the start of the section :- Parser overview with Null Handing --------------------------------- In a WMQI message flow, there are the concepts of a message bitstream and a logical message tree. The logical message tree shields the user from the physical bitstream by providing fields that can be manipulated without having to consider the exact sequence of bytes. In WMQI parsers are used to convert a message bitstream into a message tree and vice versa. Each parser uses its own 'algorithms' to dissect the bitstream and then create the appropriately named fields in the message tree giving them the relevant field types and field values. For the XML parser these algorithms involve identifying XML markup language and then using these to separate this into the correct XML objects. The MRM parser has different ways of parsing a bitstream and these are represented by the physical layers in a messageSet. For CWF, this involves reading a set sequence of bytes and translating these into the fields value in the message tree. For TDS, the parser uses the Data Element Separation method to parse the bitstream. Depending on what has been set this could involve identifying delimiters, tags, fixed length elements or patterns etc. The parsers are also responsible for writing a new message bitstream based on the values in the message tree. This will occur when a bitstream representation is required, such as in the MQOutput node or when calling the ESQL ASBITSTREAM function. Parsing and writing can be mutually independent operations such that they both do not have to be performed in a message flow. On this basis, it is possible for users to manually create new message trees in a compute node and then the parsers will attempt to create a bitstream from this message tree. It is also very common that the parsers will receive bitstreams that they did not create and have to attempt to create a message tree from them. The ESQL SET and CREATE statements can be used to populate a message tree field with a Name, Type and Value. It is therefore possible that the Value assigned to the message tree can be the result of an expression that evaluates to a NULL. This can be caused by the use of an uninitialised variable, a message tree field that does not exist, the result of a database query or use of the NULL keyword directly. When dealing with a message tree, there are two types of NULL : - Implicit : A message tree field does not exist and so implicitly has a NULL value. - Explicit : A message tree field actually contains a NULL value through the use of the SET with VALUE keyword or similar ESQL. When a message tree field has an explicit NULL value then this will be interpreted in different ways depending on the owning parser of the message tree field, the operations performed by the parser and the ESQL operations performed on the message tree field. Not all of the WMQI parsers have 'NULL handling' capabilities, but for those that do the following is possible : - A sequence of bytes can be identified in the message bitstream that will cause a NULL value to be created in the related message tree field. - An explicit NULL value can be accepted in the message tree and this will result in a set sequence of bytes to be written into the message bitstream. When explicit NULL handling is considered as part of these parser operations then : - NULL is not a consistent concept. - In WMQI the concept of NULL is present in the logical model and is created in the variables within the message flow. There is no notion of a NULL value in a bitstream. The NULL value in the message tree is created when a specific sequence of bytes are encountered within the bitstream. This sequence of bytes will be different for each parser. - Each parser has its own representation of a NULL in a bitstream. In the case of the MRM, this representation can be different for each element if the user requires such behaviour. - Each parser will interpret a NULL value in a message tree field differently. In summary, some WMQI parsers can lead to a NULL value to be created in the message tree, and can handle a message tree field containing an explicit NULL value when writing a new output message. However, other operations can be performed on message tree fields outside the scope of parsing and writing. It is possible for a user to create or manipulate a parser created message tree through the use of ESQL or nodes that cause message tree fields to be copied from one domain to another. For more information regarding the use of explicit NULLs in the XML domain, please see the ESQL reference (as point 2 below). 2. Websphere MQ Integrator ESQL Reference, SC34-5923-02, Chapter 2; Messages and ESQL; Section, Referencing information in XML messages; will have a new subsection added after 'Constructing XML in the Compute Node' as follows : The XML message domain and NULL values -------------------------------------- The XML domain does not have a concept of a NULL value in the message bitstream. This means that there is no sequence of bytes in an XML message that will lead to an explicit NULL value to be created in the message tree. Although the XML parser will not create a message tree field with an explicit NULL value, ESQL within a message flow can lead to the creation of such a field. When the XML parser needs to construct a new message bitstream from the message tree, then it could encounter explicit NULL values and therefore needs to be able to handle them. In this case, an explicit NULL value is seen as 'no characters to write' and therefore the field is created as the empty tags. In the XML domain, there are several values that will lead to the writing of XML empty tags in the resultant XML message : - A message tree field that contains an explicit NULL value - A message tree field that contains the zero length string ('') - A message tree field that does not have a value Once these have been written as the empty tags in an XML message then, if the XML message is subsequently parsed, it is not possible to distinguish between these three cases. When empty tags are parsed in XML, then an XML message tree field is created that does not have a value. This is different from a message tree field that contains an explicit NULL value, and also different from a message tree field that contains a zero length string. Although the XML parser resolves these three different message tree field values to the same result in the message bitstream, other message tree operations can distinguish between them. Although the XML parser will not create fields that contain explicit NULLS and zero length strings, the user can perform operations in message flows that can. Therefore, if a message flow is processing messages in the XML domain, then the ESQL will need to distinguish between a explicit NULL value, a zero length string, and a message tree field that does not have a value. Not even a field that contains the explicit NULL value is considered to be NULL when using ESQL to query the value of the element. The XML writing process can handle this condition however other operations within ESQL will not treat this as a NULL value. As previously stated, the XML domain does not have a concept of NULL and the parser will never create a field that contains an explicit NULL value. Because the XML domain is a character based domain, when the value of a field is queried, it returns the result as a character field. If the user creates an XML message tree field with an explicit NULL, then this will not be seen as a NULL value for those ESQL routines that get the value of the message tree field. What will actually be returned is the character representation of the contents of the field, which in this case will be the character string 'NULL'. For example, if the user performs such comparisons as with IS NULL, then this will never evaluate to a TRUE value. If the user copies this message tree field to another message tree, then the target message tree field will be populated with the character string 'NULL'. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC35575 - RENAME MSGFLOW FOR DEVELOPMENT & PRESERVE ORIGINAL COPY A new section; Preserving message flows, will be added to the Using the Control Center manual, SC34560205, in Chapter 5; Working with message flows, before the Debugging message flows section to improve the documentation regarding preservation of message flows as follows:- If you wish to preserve a message flow to enable reuse or retain a stable level, whilst further developing a copy it is important to understand that renaming a message flow merely changes a label. Message flows are identified in the configuration repository by a generated unique identifier (CUUID). Therefore when a message flow is exported from configuration repository to another it will retain its CUUID. This means that if an exported message flow is imported and modified on another system then subsequently re-imported to the original system, the original message flow, even if it has been renamed, will be overwritten with the imported modified message flow unless a copy has been made of the original. Preserving a copy of a message flow: 1. Click the Message Flows tab. 2. Select the message flow you wish to preserve, and click Copy. 3. Paste the message flow to the Message Flows root. 4. A copy of the original message flow is created as a new message flow (this will have a different CUUID). Select the copy and click Rename to change the label of the message flow. 5. You can now modify the renamed copy of the message flow independent of the original. 6. Save your new message flow in the configuration repository using either Check In or one of the File -> Check In menu options. A reference with recommendation to read this will be made in Chapter 3, Using the Control Center - configuration data and the workspace, in the 'Importing resources' section. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ PQ71204 - UPDATE TO THE PROGRAMMING GUIDE ON HANDLING ERRORS RETURNED FROM THE JAVA PROPAGATE METHOD. The following following paragraph will be added to the WebSphere MQ Integrator Version 2.1 Programming Guide (SC34-5603-04) in Chapter 6, the section 'Implementing a node in Java', sub-section 'Error handling and exception' to document the exception handling for the Java propagate method. When an error occurs downstream of the plugin node the exception will get flowed back up the flow and returned to the evaluate method of the plugin. As the broker is handling this execption it is better not to handle this exception within the plugin. To do this do not code the propagate method within a try code block. If you wish to carry out some error handling then once complete the exception should be thrown back to the broker to allow it to complete its error handling. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IY36091 - DOCUMENTATION PROBLEM WITH HOW MESSAGES ARE PROCESSED IN BOOK The WebSphere MQ Integrator Introduction and Planning Guide V2.1, GC34-5599-04, Chapter 5: Messages, Section: How messages are processed in a message flow the bulletted list will be changed to describe the correct way in which messages are processed in a message flow as follows:- The characteristics of MQSeries messages are identified by the input node of a message flow in the following way: - The input node will allocate a parser to each header in the message in turn, and the message body is simply treated as another header in the chain. - Being an MQSeries message, the first header is assumed to be the MQMD and is parsed accordingly. - Each header should indicate the type of header or data following it. With MQSeries messages, this is normally done using the 'Format' field. The MQRFH and MQRFH2 headers are slightly different in that the Name/Value data in the header may also contain information regarding the format of the following data. If the value in the Format field is a known parser (recognised by WQMI) then this will always take precedent over any Name/Value data. See the WebSphere MQ Integrator Programming Guide for more details about the content and use of these headers. - If the value in the "Format" field (or in the Name/Value data) is recognised by the input node, and it has an associated parser, this parser will be used to parse the following header (which may be the message body). - If no specific parser has been identified by the 'Format' field, the input node uses the default message template, defined as a property of the input node, to determine how the remaining message body must be parsed. - If a default message domain hasn't been specified on the input node, the BLOB parser is used. It is normal practice to use either the folder in the MQRFH2 header or the MQInput node to indicate to the message flow the characteristics of the message data. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IY37844 - NNSYMESSAGELOG MUST BE ACCESSIBLE BY THE BROKER AND IN THE CURRENT DIRECTORY. Chapter 12: Migrating from MQSeries Integrator of the WebSphere MQ Integrator Administration Guide V2.1, GC34579206, Section: Migrating New Era of Networks Rules and Formats, Subsection: Logs and log records will be added to to specify that WebSphere MQ Integrator must have access to the New Era Messagelog file as follows :- Log records generated by all New Era of Networks Rules and Formatter Support nodes and parsers are written to the log file defined for the message flow in which the nodes appear. For details of how to specify a log file for a message flow, see WebSphere MQ Integrator Using the Control Center. The NEONMap, NEONRulesEvaluation, and NEONTransform nodes also write log information to the NNSYMessageLog.nml file. This file is created in the directory from which you issue the mqsistart command > and hence MQSeries Integrator must have write access to that > current directory. > The NEONMap, NEONRulesEvaluation, and NEONTransform nodes also write > log information to the NNSYMessageLog.nml file. This file is > created in the directory from which you issue the > mqsistart command. Note that the New Era log file is named NEONMessageLog.nml in MQSeries Integrator V2.0.2. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IY37824 - WMQI ADMINISTRATION GUIDE IS MISSING DOCUMENTATION FOR MQSI_SETUPDATABASE SUPPORTING ORACLE9 The Websphere MQ Integrator Administration Guide V2.1, SC34-5792-05, Chapter 3: The broker, Topic: Creating a broker database, Section: Using Oracle or Sybase databases on UNIX platforms, will be updated to include instructions for creating an Oracle 9i database as follows :- In the SubSection: For Oracle 8.1.6 the command to issue to perform the required setup for Oracle 8.1.6 will be changed from: mqsi_setupdatabase oracle to: mqsi_setupdatabase oracle8 where is the directory in which Oracle 8.1.6 is installed. The SubSection: For Oracle 8.1.7 and Sybase will be changed to read as follows:- For Oracle 8.1.7, Oracle 9 and Sybase You are recommended to complete this setup after you have installed your database, but you can complete it before database installation if you specify the intended database installation directory correctly during this setup. You must issue the following command: mqsi_setupdatabase where is oracle8, oracle9, sybase 11, sybase12, or sybase12_5 depending on your database version and is the directory in which the database is (or will be) installed. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC35769 - DISCEPANICES AROUNDTHE COMPOUND STATEMENT AND CASE FUNCTION. The ESQL CASE statement function is incorrectly documented in the WebSphere MQ Integrator ESQL Reference, SC34592302, the WebSphere MQ Integrator CSD Release Guide, SC34619700, and the product README.TXT file. There is also an implication that there is an ESQL keyword/verb called "COMPOUND", which there is NOT. Future versions of the documentation will correct this. The README.TXT file which accompanies this maintenance has been updated. See point 95. ESQL CASE Statements, in The All Operating Systems section. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ PQ66774 - ASBITSTREAM FUNCTION IS NOT DOCUMENTED IN THE ESQL GUIDE FOR WMQI 2.1. The ASBITSTREAM function was not documented in the ESQL Guide or the README.TXT file which accompanied CSD03. The information will be included in any future release of the Guide and is included in the README.TXT file which accompanies CSD04. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IY35159 - PROBLEM DETERMINATION GUIDE ON PAGE 39 STATES THAT HARD LIMIT FOR PROCESS ON AIX IS 512MB, HOWEVER IT IS USER DEFINED. The AIX hard limit size described in the WebSphere MQ Integrator Problem Determination Guide V2.1, GC34592000, Chapter 5, Dealing with problems during administration, Section: Configuration problems with a large number of components will be corrected and added to as follows :- AIX 4.3.3 and 5.1 For 32 bit system : 2 GB On AIX , WMQI limits DataFlowEngines to two 256MB memory segments i.e. 512MB. Normally DFE processes do not require more than 512MB of the AIX address space therefore the DataFlowEngine executable is linked so as to have a default address space of 2 segments. It is possible to extend the size of the AIX address space available to the DataFlowEngine process by increasing the number of 256MB memory segments available to it. This can be done by patching the executable. Using the following shell commands you can patch DataFlowEngine to use more memory segments. /usr/bin/echo '\0100\0\0\0'|dd of=executable_file_name bs=4 count=1 seek=19 conv=notrunc This creates a version of the DataFlowEngine which uses 4 segments, i.e. 1GB. NOTE: The above technique only overrides the soft limit, not the hard limit. If your broker processes regularly reach these sizes, consider spreading your messageflows across more execution groups to reduce the size of each one below these limits. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC34391 - DB2 INSTANCE PARAMETERS MAXAGENTS AND MAXAPPLS NEED TO BE SET The WMQI V2.1 documentation does not specify that the maxagents parameter needs to be set at the same time as the maxappls parameter. The following books will be amended to specify that the maxagents parameter needs to be set at the same time as the maxappls parameter. WebSphere MQ Integrator Administration Guide V2.1 (SC34579206), Chapter 3; The broker, Defining and authorizing a broker database, Creating a broker database, Broker database connections. WebSphere MQ Integrator Using the Control Center V2.1 (SC34560205), Chapter 5; Working with message flows, Creating a message flow, Managing database resources. WebSphere MQ Integrator Problem Determination Guide V2.1 (GC345920-01), Chapter 5; Dealing with problems during administration, Problems with databases, Message SQL1040N. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC30627 - EXPLANATION OF CARDINALITY FUNCTION IS INCOMPLETE AND INCONSISTENT IN USING THE CONTROL CENTER The examples supplied in the Using the Control Center manual are lacking and/or incorrect in clarifying how things actually work with regards to the Cardinality function and XML messages that contain pcdata, white space characters, attributes etc. The following information on the Cardinality function will be added to the WebSphere MQ Integrator Using the Control Center manual, SC34-5602-02, Chapter 16 - Concepts of XML messages :- WMQI V2 treats XML pcdata, attributes and sub-elements as children of the element. The ESQL Cardinality function returns the number of children of a parent in the message tree. This means it counts pcdata, attributes and sub-elements together, therefore when using the Cardinality function with XML messages that contain pcdata, white space characters, attributes etc. you need to distinguish what you are determining the Cardinality of. For example, to get the Cardinality of the number of elements (tags), you would replace .* with .(XML.tag) The MOVE statement will also navigate to such fields in an XML tree when dealing with FIRSTCHILD, LASTCHILD, PREVIOUSSIBLING and NEXTSIBLING. In CSD02 the TYPE and NAME clauses were added to allow target fields of a specific NAME or TYPE meaning that 'non-data' fields in the tree can be skipped over. The WebSphere MQ Integrator ESQL Reference V2.1 (SC34592302), Chapter 4; ESQL Statements, MOVE will be update to emphasise this point. The fourth paragraph currently states :- If a TYPE clause, NAME clause or both are present, the target is again moved in the direction specified (PREVIOUSSIBLING or NEXTSIBLING or FIRSTCHILD or LASTCHILD) but to a field with the given type, name or both. If the specified move cannot be made ....... This will be added to as follows :- If a TYPE clause, NAME clause or both are present, the target is again moved in the direction specified (PREVIOUSSIBLING or NEXTSIBLING or FIRSTCHILD or LASTCHILD) but to a field with the given type, name or both. This is particularly useful when the name and/or type of the target field is known because this will reduce the number of MOVE statements required to navigate to a field. This is because fields that do not match the criteria will be 'skipped' over, and this could also include unexpected message tree fields such as those representing whitespace. If the specified move cannot be made ........ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ PQ62125 - NEED DOCUMENTED GUIDELINES ON LOGGING 1GB LOB COLUMNS. The following information will be added to the WebSphere MQ Integrator for z/OS Customization and Administration Guide Version 2.1 (SC34-5919-01), Chapter 2; Customization, Customizing a broker, Step 7. Create the broker database p39 Considerations with WMQI usage of large objects in DB2 tables on z/OS. 1) DB2 needs to allocate auxiliary tables to hold large objects (LOBs). By default WMQI tables are created with CURRENT RULES = 'STD'. With this option set, DB2 implicitly defines a LOB table space, an auxiliary table and unique index for each LOB column (using default sizes). The default sizes of these tables may be too small for your particular requirements. This can mean that the maximum number of extents for the table space is quickly used up. If these tables have large and frequent updates the BIPDBTB member in the CNTL library for the broker should be edited as follows :- 1.1) The line SET CURRENT RULES = 'STD'; should be commented out 1.2) For all tables using LOB columns, including the following tables :- BSUBSCRIPTIONS, BRETAINEDPUBS, BACLENTRIES, BMQPSTOPOLOGY, BROKERAAEG, BROKERRESOURCES, BRMRTDINFO, BRMPHYSICALRES and BAGGREGATE a) Add a ROWID column to each of the create table definitions. e.g. ROW_ID ROWID NOT NULL GENERATED ALWAYS; b) Create a table space and table to hold the LOB data. The table space and table are called a LOB table space and an auxiliary table. One LOB table space and one auxiliary table must be created for each LOB column. Create these objects using the CREATE LOB TABLESPACE and CREATE AUXILIARY TABLE statements. For the create table space statement the following should be taken into consideration. PRIQTY n Specifies the minimum primary space allocation for a DB2-managed data set. The primary space allocation is at least the integer n in kilobytes, the actual value will vary depending on the page size for the buffer pool used. If PRIQTY is omitted, n is 200, 400, 800, or 1600 for 4KB, 8KB, 16KB and 32KB page sizes, respectively. SECQTY n Specifies the minimum secondary space allocation for a DB2-managed data set. The secondary space allocation is at least the integer n in kilobytes. This will again vary with respect to the page size for the buffer pool used. If SECQTY is omitted, n is either 10% of PRIQTY or 50 times the page size of the table space, whichever is larger. c) Create an index on the auxiliary table. The DSNTEJ7 sample shipped with DB2 demonstrates the above. For existing brokers a DB2 utility tools such as RUNSTATS and REORG can be used on the default named table spaces to increase the primary and secondary quantities respectively. 2) LOBs defined with a maximum size of > 1GB are not logged by DB2. This means that if you restore a backup copy of a database with LOBs > 1 GB, DB2 will not recover changes to that table at restart. To log changes to LOB columns you will need to reduce the size of the LOB column to less than or equal to 1 GB and specify LOG YES on the CREATE LOB TABLESPACE statement. Be aware that this may affect the performance of the updates to these tables. If you do not wish a LOB column to be logged, that is not greater than 1 GB, you will need to specify LOG NO for the table space concerned. Migration from an existing broker to one that supports logging of LOB columns will require the recreation of the broker. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SPECIAL INFORMATION ------------------- PLEASE REVIEW THE README.TXT FILE WHICH HAS BEEN UPDATED IN THIS MAINTENANCE RELEASE. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 29862 - Merant driver updates CSD05 includes a new version of the DataDirect Technology (formerly Merant) ODBC Driver Manager. Changes MUST be made to the ODBCINI file entries and to any user compiled switch load files that use the number '16' files. All entries containing the number '16' MUST be changed to the number '18'. See below for details. Switch load files supplied by WebSphere MQ Integrator will be updated automatically by application of CSD05. Note that the value for LANG should be set to C or en_US While the number '16' files will remain there will be no further updates to them. ODBC fixes will only be supplied on the number '18' files. AIX, Solaris and HP-UX. ----------------------- The ODBCINI file. ----------------- DB2 (on AIX only). ----------------- The name of the DB2 driver used has also changed from db2.o to libdb2.a . The file pointed to by your $ODBCINI environment variable and any other user built files using db2.o will need to be changed . For example change Driver=/db2data/db2inst1/sqllib/lib/db2.o to Driver=/db2data/db2inst1/sqllib/lib/libdb2.a where /db2data/db2inst1 is the DB2 instance home on your machine ORACLE and SYBASE. ------------------ WMQI V2.1 CSD05 includes a new version of the DataDirect Technology (formerly Merant) ODBC drivers and Driver Manager. The driver files supplied by DataDirect have changed name from drivers containing the number '16' to the number '18'. Changes MUST be made to the file refrenced by your $ODBCINI environment variable . All entries containing the number '16' MUST be changed to the number '18'. On AIX change Driver=/usr/opt/mqsi/merant/lib/UKor816.so to Driver=/usr/opt/mqsi/merant/lib/UKor818.so and Driver=/usr/opt/mqsi/merant/lib/UKase16.so to Driver=/usr/opt/mqsi/merant/lib/UKase18.so On Solaris change Driver=/opt/mqsi/merant/lib/UKor816.so to Driver=/opt/mqsi/merant/lib/UKor818.so and Driver=/opt/mqsi/merant/lib/UKase16.so to Driver=/opt/mqsi/merant/lib/UKase18.so On HP/UX change Driver=/opt/mqsi/merant/lib/UKor816.sl to Driver=/opt/mqsi/merant/lib/UKor818.sl and Driver=/opt/mqsi/merant/lib/UKase16.sl to Driver=/opt/mqsi/merant/lib/UKase18.sl The qm.ini file. ---------------- Brokers using MQSeries queue managers that are performing XA coordination with Sybase or Oracle on AIX or Solaris will need their XA stanzas in the queue managers qm.ini file altered to use the '18' files instead of the '16' files. On AIX change SwitchFile=/usr/opt/wmqi/merant/lib/UKor8dtc16.so to SwitchFile=/usr/opt/wmqi/merant/lib/UKor8dtc18.so and SwitchFile=/usr/opt/wmqi/merant/lib/UKase16.so to SwitchFile=/usr/opt/wmqi/merant/lib/UKase18.so On Solaris change SwitchFile=/opt/wmqi/merant/lib/UKor8dtc16.so to SwitchFile=/opt/wmqi/merant/lib/UKor8dtc18.so and SwitchFile=/opt/wmqi/merant/lib/UKase16.so to SwitchFile=/opt/wmqi/merant/lib/UKase18.so There are no changes needed on HPUX for qm.ini. WINDOWS ------- Oracle and Sybase. ------------------ ODBC definitions. ----------------- WMQI V2.1 CSD05 includes a new version of the DataDirect Technology (formerly Merant) ODBC drivers and Driver Manager. The driver files supplied by DataDirect have changed name from drivers containing the number '16' to the number '18'. You MUST need recreate the ODBC definitions for your databases so as they use the following drivers. For Oracle use the "MQSeries DataDirect Technologies 4.10 32-BIT Oracle" driver For Sybase use the "MQSeries DataDirect Technologies 4.10 32-BIT Sybase" driver XA Resource definitions ----------------------- Brokers using MQSeries queue managers that are performing XA coordination with Sybase or Oracle will need to have their resource properties modified to use the new DataDirect dlls. Change $MQSI\bin\UKor8dtc16.dll to $MQSI\bin\UKor8dtc18.dll and $MQSI\bin\UKase16.dll to $MQSI\bin\UKase18.dll where $MQSI is the place where WMQI V2.1 is installed. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC35512 - UPDATE TO DOMAIN SECURITY AND AWARENESS DOCUMENTATION. Problems have been experienced concerning the use of extended domain security options, specifically domain awareness and the -l and -d options, when creating the Configuration Manager. The changes to the domain security function have been explained in the readme.txt file (accompanying this maintenance release) in the Documentation section, subsection: Updates, point 1, Using Fully Qualified User Names for Control Center Users. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SupportPac IA0F: WebSphere MQ Integrator - IDoc parser for SAP The IDoc SupportPac, IA0F, was included in the product from CSD03 onwards. This SupportPac contains a set of parsers which add support for parsing of input messages and creation of output messages in the SAP IDoc Version 4 format. The IDoc parser represents incoming data to WebSphere MQ Integrator in a format that the Integrator compute node can manipulate. It also allows data of a different format to be mapped to an IDoc stream. For more information, see the support pack IA0F documentation at www.ibm.com/software/integration/support/supportpacs/individual/ia0f.html ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ WebSphere MQ Everyplace 1.2.7 nodes The WebSphere MQ Everyplace nodes (1.2.7) supported in WebSphere MQ Integrator V2.1 can be obtained via the Level 2 Service organisation at http://l3.hursley.ibm.com/ftp/fixes/MQe/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Migration from previous levels to CSD04 The redundant validate checkbox has been removed from the Advanced tab of the input nodes in CSD04. Therefore, when migrating flows developed pre-CSD04, ensure the validate check box on the Advanced tab of all input nodes is unchecked. Failure to do this will result in BIP1758 error messages during a deploy of message flows containing such nodes. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 28704 - Merant Driver Manager update Support for DB2 UDB Version 7.1 FixPak 2 or later on UNIX. The DB2 flash 1042663 - "Merant Driver Manager and DB2 UDB V7 ODBC driver on Unix" described incompatibilities that had been encountered with Unicode support when the Merant Driver Manager accessed DB2's ODBC driver on UNIX. The affected versions of DB2 UDB included Version 7.1 with FixPak 2 or later, and Version 7.2. The workaround was to use an alternative DB2 ODBC driver library without Unicode support enabled. CSD04 includes a new version of the DataDirect (formerly Merant) Driver Manager which has removed the need for the workaround documented in the above DB2 flash. If your DB2 database is running on HP-UX or Solaris you will need to remove the above workaround to enable this support. If your DB2 database is running on AIX you will need to remove the above workaround and also change the DB2 Driver entry in your .odbc.ini file from : Driver=/db2data/db2inst1/sqllib/lib/db2.o to : Driver=/db2data/db2inst1/sqllib/lib/libdb2.a ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC34394 - MQOUTPUT NODE ABENDS WHEN WRITING AGGREGATED REPLY MESSAGE This is resolved in CSD04 however if the problem has already been encountered the BAGGREGATE table of the broker database will contain records which MUST BE DELETED after applying CSD04 and BEFORE STARTING THE BROKER. Failure to do this will prevent the fix taking effect and errors will be reported in the system log indicating 'failure due to invalid MQMD header at MQOUTPUT node'. If this problem has not been encountered these entries will not be present in the BAGGREGATE table and no further action is required. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ IC33207 - SILENT INSTALL FOR CSD FAILS The problem with the backup folder has now been resolved. For information on how to perform a silent install of a CSD see Chapter 3; Installing Websphere MQ Integrator; Silent Installation, of the Websphere MQ Integrator for Windows NT and Windows 2000 Installation Guide Version 2.1, and use the maintenance CD instead of the product CD. Note that to perform a silent install of a CSD downloaded from the web perform the following actions. To create the response file change to the directory where the CSD .exe file has been stored and run the following command :- U200nnn.exe -s -a setup.exe -noinst -r -f1x:\mypath\my.iss Where U200nnn is the PTF number of the CSD being loaded and x:\mypath\my.iss is the target drive for the response file being recorded To perform the silent install run the following command:- U200nnn.exe -s -a setup.exe -nomsgbox -s -f1x:\mypath\my.iss ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Migration to CSD03. In order to activate new options within the Control Center, the Config Manager must be deleted and re-created. This is done as follows 1) Stop the Config Manager mqsistop ConfigMgr 2) Delete the Config Manager preserving the configuration and message repository. mqsideleteconfigmgr Use no options on this command. 3) Re-create the Config Manager mqsicreateconfigmgr Use all the options that were used when the Config Manager was last created. 4) Start the Config Manager mqsistart ConfigMgr 5) Restart the Control Center and the new options will be available. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ SERVICE AND TECHNICAL SUPPORT ----------------------------- This is the first release of WebSphere MQ Integrator Broker Version 2.1. 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 IC30350 - CONFIGMGR NOT DETECTING A COMM LINK FAILURE TO DB2, GIVES 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 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 IC31766 - MQSIREPORTTRACE DOES NOT WORK CORRECTLY WITH USERNAMESERVER COM IC31787 - MQSICHANGEUSERNAMESERVER ACCEPTS INVALID USERID, AND CHANGES IC31802 - GETTING PARSING ERRORS WHILE USING REPEATING FIELDS WITH SECOND IC31806 - PROBLEM IMPORTING COBOL COPYBOOK. IMPORTER DOESN T LIKE EXTRA IC31825 - BOTHRESH AND BOQNAME NOT WORKING PROPERLY WHEN ERROR OCCURS ON 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 IC32309 - WITHIN THE COMPUTE NODE, WHEN CODING A PASSTHRU FUNCTION IC32427 - V201 AND V202 TO V2.1 MRM MIGRATION AND COEXISTENCE IC32440 - ASSURED DELIVERY OF MESSAGES TO MQE NODES IN MQSI BROKEN IC32689 - ESQL CAUSES EG TO USE 100% CPU 202 CSD02 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 IC33053 - ERROR BIP0067E WHEN SWITCHING THE CONTROL CENTER ON THE MACHINE IC33066 - MQE NODES SENDING DUPLICATE MESSAGES IC33135 - BIP1350 CONTROL CENTER TIME OUT, CONFIGMGR NOT RESPONDING IC33333 - MQE SUBSCRIBER RECEIVING A MESSAGE CONTAINING CERTAIN BINARY CH 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 IY16738 - START OF BROKER CONFIGURED TO USE ORACLE GIVES AN ERROR - UNABL 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 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 IY21734 - MQSI CRASHED WHEN ADDITIONAL INSTANCES OF A MESSAGE-FLOW WERE IY22261 - BROKER IN AIX SMP ENVIRONMENT MEMORY MANAGEMENT VULNERABLE TO F IY23087 - EXCESSIVE CASHING PERFORMED BY MQSI CAN LEAD TO MEMORY HEAP IY24362 - CONVERSION INCORROUT FROM OS/390 TO OS/400. IY25465 - SCADA NODE STOPS TRANSMITTING MESSAGES THROUGH FLOW IY26160 - BIP2088E AND BIP2106E AT DEPLOYMENT OPERATION. IY26427 - A BROKER RUNNING WITH A SCADA NODE LOCKS UP 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 PQ65755 - WMQI SHOULD EITHER PASS THE USERID AND THE PASSWORD ON THE 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 product 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 products 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 =========== CSD05 _____ This is CSD05 for WebSphere MQ Integrator Broker Version 2.1. It is delivered via the following PTFs:- - U200196 for Windows NT/2000 - U487643 for AIX - U487769 for Sun Solaris - U487768 for HP-UX It contains fixes for ALL the problems listed below: Name - Abstract IC35883 - CUMUL MAINT #03 FOR WEBSPHEREMQ INT BR V2.1 FOR NT IY41591 - CUMUL MAINT #03 FOR WEBSPHEREMQ INT BR V2.1 FOR AIX IY41627 - CUMUL MAINT #03 FOR WEBSPHEREMQ INT BR V2.1 FOR HP-UX IY41628 - CUMUL MAINT #03 FOR WEBSPHEREMQ INT BR V2.1 FOR SUN PQ74752 - CUMUL MAINT #03 FOR WEBSPHEREMQ INT BR V2.1 FOR Z/OS PQ74753 - CUMUL MAINT #03 FOR WEBSPHEREMQ INT BR V2.1 FOR Z/OS IC32907 - SELECT FROM A DATABASE IS NOT RETURNING THE MICROSECON IC32971 - BIP2430 - ESQL CONCATENATION WITH NON EXISTANT FIELD IC34708 - RCD NODE CAUSES MRM MSGTYPE PREFIX DOUBLE PRE-PEND. IC35006 - USE OF REPLYTO FIELDS IN THE DESTINATIONDATA FOLDER. IC35011 - WMQI V2.1 - C/T REQUEST TO IMPROVE DOCUMENTATION REGAR IC35052 - ADDRESS TREE COPYING FROM USER PARSER CREATED MESSAGE IC35097 - COBOL INPORT : DEFAULT VALUES NOT CREATED FOR DECIMAL IC35139 - REPEAT KEYWORD IN MOVE INCORRECTLY REJECTED IN CONTROL IC35298 - REPEATING RECORDS ARE SEEN AS EXTRANEOUS IF THE LAST F IC35342 - CODE PROBLEM WITH MULTIBYTE CHARACTER SETS IC35370 - DECIMAL POINT IS NOT SUBSTITUTED IN MRM COBOL LANGUAGE IC35397 - ADD MSGFLOW VERY SLOW - IMPROVE PERFORMANCE IC35479 - QUEUE MANAGER HANGS AFTER INITIATING USER LOGS OFF IC35512 - UPDATE TO DOMAIN SECURITY AND AWARENESS DOCUMENTATION. IC35549 - CONTROL CENTER HANGING - DUE TO THREADING PROBLEMS. IC35575 - RENAME MSGFLOW FOR DEVELOPMENT & PRESERVE ORIGINAL COP IC35664 - ONLINE HELP FILES INTEGRATED INTO CSD03 AND CSD04 HAVE IC35769 - DISCEPANICES AROUNDTHE COMPOUND STATEMENT AND CASE FUN IC35806 - BIP9398S,9351S ON IMPORTING THE MESSAGES IN THE SAME M IC35898 - 'TDS Group Indicator written for omitted compound elem IC35939 - DEADLOCKS WHEN USING THE AGGREGATE REPLY NODE. IC35942 - MESSAGES FAIL WHILE UPDATING THE TABLE BMQESTDMSGOUT U IC35949 - XML SCHEMA IMPORT FAILS, WHEN 'SIMILAR' ENUMERATION AR IC36010 - DOCUMENT USE OF CLEARMESSAGE FOR JAVA PLUGIN NODES IY25775 - PROBLEM WITH BIGINT DATATYPE ON AIX IY27218 - ERROR WHEN SELECTING DATETIME WITH MILLISECONDS ON MSS IY34362 - ORACLE DB CONNECTION IS NOT RE-ESTABLISHED IF USER DB IY36059 - ESQL SYNTAX ERROR CAUSING A EG TO ABEND IY36091 - DOCUMENTATION PROBLEM WITH HOW MESSAGES ARE PROCESSED IY37213 - FOLDERBITSTREAM CONSTANT INCORRECT ON AIX PLATFORM IY37803 - BROKER FAILS TO CONNECT TO ITS DATABASE, AFTER A DATAB IY37824 - WMQI ADMINISTRATION GUIDEIS MISSING DOCUMENTATION FOR IY37997 - 'MQCMITS ISSUED WHEN NO MSG AVAILABLE'. IY38039 - MQSICOPYMSGSET DOES NOT PRESERVE UNSET VALUES IY38589 - BIP2228E ON ORACLE DB IPL IY38673 - BIP2135E DATA CONVERSION ERROR DURING CONVERT FROM SJI IY38891 - JAVAW.EXE EXCEPTION (CSD04) ESQL SYNTAX CHECKER IY38894 - MIGRATION FROM V201 TO V202 USING ORACLE 815 IY39777 - CSD04 CAUSING DB2 STORED PROCEDURES TO FAIL. IY39952 - ERROR BIP5341 OCCURS WHEN COPYING MRM INT FIELD TO STR IY40097 - CASE FUNCTION CANNOT RETURN LIST/ROWS - BIP2556 IY40186 - SEMOP FAILURE IN IMBNAMEDMUTEX CAUSES DATAFLOWENGINE A IY40730 - 'MQINPUT NODE: MESSAGE TYPE SHOULD SHOW IDENTIFIERS NO IY40842 - MQSI NOT USING 'C' AS A CODE FOR SIGNED EBCDIC EXTENDE IY41088 - 'END OF BITSTREAM' DOESN'T WORK FOR BINARY ELEMENTS. IY41996 - ACCEPT ZERO LENGTH STRINGS FOR MRM NUMERIC FIELDS IY42133 - TEXT FOR ERROR BIP5199 NEEDS TO BE CORRECTED. PQ67615 - CNIELEMENTCHARACTERVALUE/CPIELEMENTCHARACTERVALUE CAUS PQ70700 - ABEND0C4 OR DICTIONARY LOAD ERROR INTERMITTENTLY WHILE PQ71204 - UPDATE TO THE PROGRAMMING GUIDE ON HANDLING ERRORS RET PQ71205 - BIP5502E:MRM INT/FLOAT->EBCDIC INC. SIGNED EXTDEC WITH 24125 - MRM: Msg 5424 user response could be more helpful. 27730 - HOT:ACORD:VAL:BIP5374 output ACORD message 28447 - Resource Manager cannot handle WMQI 5.0 dictionaries 28806 - v2.1 csd 03 breaks IH05/IC02 SupportPacs 28835 - Dublin - Incorrect parsing 29230 - XML Schema Importer does not handle UTF-16 + See comment 29382 - logErrorData macro causes java core dump in CMI on AIX p 29648 - When trying to run the sample program scribble on window 29862 - Merant driver updates 30107 - Problem importing a DTD 30150 - Invalid ESQL syntax checker scope error when using proce 30263 - readme update for ACORD 30709 - Poor perf. expanding large MRM structures in Compute nod CSD04 _____ This is CSD04 for WebSphere MQ Integrator Broker Version 2.1. It is delivered via the following PTFs:- - U200188 for Windows NT/2000 - U485928 for AIX - U485967 for Sun Solaris - U485966 for HP-UX It contains fixes for ALL the problems listed below: Name - Abstract IC34997 - CUMUL MAINT 02 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR NT IY37094 - CUMUL MAINT 02 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR AIX IY37095 - CUMUL MAINT 02 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR HP-U IY37098 - CUMUL MAINT 02 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR SUN PQ68897 - CUMUL MAINT 02 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR Z/OS PQ68898 - CUMUL MAINT 02 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR Z/OS IC33207 - SILENT INSTALL FOR CSD FAILS IC33844 - JUMPTORULES FUNCTION NOT WORKING THROUGH FORMATTER GUI IC34178 - USING DATE FORMAT FROM XML TO MRM, THERE IS A DECREASE OF ONE IC34394 - MQOutput node abends when writing aggregated reply message IC34449 - ZOOM FACTOR FAILS WHEN VIEWING A MESSAGE FLOW USING 'FIT TO IC34463 - 2068 ERROR WHEN A FAILED MESSAGE IS BACKED OUT TO A CLUSTERE IC34470 - BIP1813W OCCURS WHEN TRYING TO ADD A PHYSICAL LAYER ON A MESSAG IC34489 - USE OF INVALID CODEPAGE IN MRM CAUSES BROKER TO ABEN IC34526 - PROBLEMS IMPORTING XML SCHEMA FILE USING THE NEW PROVISION IC34563 - BIP5288E ERROR AT CSD03 LEVEL IC34594 - UNABLE TO RENAME A MESSAGE FLOW ON THE LEFT PANEL OF IC34602 - A BROKER DATABASE CONNECTION *LEAK* UPON MQISDP CLIENT IC34651 - PROPAGATED SUBSCRIPTION RECV'D ON SYSTEM.BROKER.CONTROL.QUEUE IC34656 - AFTER CSD03, COPY AND PASTE ON A MESSAGE FLOW DOESN'T WORK IC35035 - XML SCHEMA IMPORTER IS MISSING AT U200179 LEVEL OF WEBSPHERE IY29380 - BIP8146E MESSAGE IS NOT PICKING UP THE CORRECT INSERT FOR REGIS IY30276 - Problem selecting > 1998 bytes from Oracle CLOB column IY33022 - XA TRANSACTION BETWEEN A SOLARIS BROKER AND DB2 ON OS/390NOT WO IY33716 - AggregateReply node loops following catch terminal IY33904 - STATUS OF REMOVED MESSAGE SETS IS NOT UPDATED CORRECTLY ON THE IY34240 - BIP2080 MESSAGE IS LOGGED IN SYSLOG BECAUSE EXECUTION GROUP ( E IY34332 - THE VDB CAUSES A BIP5009E FOR SOME FIELD NAMES IN NON-XML IY34561 - DATABASE EXCEPTION WITH AN SQLCODE =-501 IY34804 - AGGREGATE NODES FAIL TO DEPLOY UNDER XA IY34805 - WMQI 2.1 CSD 03 LATE BREAKING TDS UPDATES AFFECTING SWIFT USERS IY34949 - COALESCE INCORRECTLY RETURNS A NULL VALUE. IY34951 - NEGATIVE EXTDEC WITH TRAIL 0 INCORRECT ON SOME EBCDIC CODEPAGES IY35037 - THE CWF TAB HAVING STRING JUSTIFICATION SET TO RIGHT JUSTIFY AN IY35159 - PROBLEM DETERMINATION GUIDE ON PAGE 39 STATES THAT HARD LIMIT IY35724 - TDS PARSER FAILS TO DETECT THE END OF A REPEAT. PQ66348 - THE BITSTREAM FUNCTION HAS BEEN REGRESSED IN CSD03 WHEN PQ66584 - WMQI DOESN'T FREE UP CACHE FOR PREPARED STATEMENTS. PQ66773 - ASBITSTREAM IS NOT AVAILABLE IN THE CONTROLCENTER FUNCTION PQ66774 - ASBITSTREAM FUNCTION IS NOT DOCUMENTED IN THE ESQL GUIDE PQ66775 - CONTROL CENTER DOES NOT ACCEPT ASBITSTREAM WITH ANY OPTIONS, PQ66803 - SELECT STATEMENT WITHIN PLUGIN NODE CAUSES SQLSTATE HY010 f20575 - MRM-Select layers to be pasted f24996 - IO02 message file need uppercase names f25963 - EUI "RegExp" verifications on "Data Pattern" value member f26073 - Improve messageset identifier usability f26106 - Tidy up DataConv error messages 11098 - Only first added broker is shown in collective's properties 15870 - Smartguide name edit controls allow names > 254 characters 16174 - Message pane does not display message clearly 16953 - Message flow view reset while flow is being modifie 17059 - one item of each type displayed as property for a collection 17288 - Exception Delete MsgProcNode from flow use pulldown/Delete key 18981 - Usability suggestion for Create Element Value 19499 - Broker subscriptions cannot be selected using the mouse. 19780 - Promote Property dialog wrong display after window /pane resize 20518 - Plug-in Wizard attribute/group ordering 20585 - Copying and pasting message flows and sets in assignments tab. 20794 - Node with promoted properties should not be delete 20860 - MRM-Inconsistent error messages 21679 - On-line help can't be invoked from Check Message Flow dialog 21905 - Focus does not default to parent if tree object delete 22009 - checkin and unlock very close together. 22222 - Type field not highlighted by tabbing if no selection made 22271 - MQSI2.1:GUI Nodes:Context menu is not getting cleared after Es 22522 - For all TDS string properties, the length > 254 is accepte 22601 - Finish of import dialog should be disable after remove all file 23511 - MRM-can edit frozen message set tab but then lose changes. 23571 - Dbl-clicking brings up properties when properties are disable 24196 - STRESS: repeated SEGV in aggr timeout threa 25183 - Topics: Principal highlight moves when navigating ACLs dropdown 25320 - MRM-User can create messages with base types 26231 - corruption of ImbStringBase object 26570 - Unable to Ctrl+Tab through node properties 26724 - Subscriptions: Unable to browse subscriptions using U/D arrow k 27442 - MRM:TDWF Tag is not setting default value correctly 27726 - ACORD:VAL:5371 on Parse/validate ACORD embedded compound type 27727 - Check out list dialog displays new objects 27753.1 - Internal error raised by PWFData 27786 - Broker registry key remains on Win XP 27841 - SWIFT:VAL:min and max occurs not validated at compute node 27844 - SWIFT:VAL:Closed type inside opendef makes opendef act close 27846 - ACORD: MRM BIP5506 in ACORD Message if non-? 27853 - ACORD:VAL:MRM Anon field inheriting values from prev elements 27891 - ACORD:MRM BIP5421/BIP5505 parsing repeating ACORD message body 27911 - Select As Function is wrong flagge 27921 - SWIFT:VAL:Missing mand. not validated after selfdef elem on o/p 27929 - SWIFT:VAL: MT562, problem with repeat within repeat validation 27944 - SWIFT:VAL: MT210_0015 repeat seq. causes DFE loop 27955 - SWIFT:VAL: MT300 repeating sequence causes val failure. 27958 - SWIFT:VAL: MT600 failis validat'n seqB missing but seqC present 27971 - ERRMSG BIP5452 has minor typo 27978 - SWIFT:VAL: Embedded Message in MT792 causes validation error 27979 - EUI Check out list causes workspace updates to be lost 27986 - EUI Java exception adding value constraint 27988 - SWIFT:VALID: MT521I messages giving BIP5371 27991 - EUI MRM unexpected hierarchy collapse 28005 - Interface to RgXExp matcher to take end offset 28026 - SWIFT: VAL: MT450: 52B: wrong path in choice being validated. 28037 - SWIFT: 2002: MT501 has 16R with missing : on output. 28047 - SWIFT: VAL: MT562 Some still failing 28048 - SWIFT: VAL: DFE Loop with MT801 message 28056 - SWIFT: 2001: VAL: MT204 57A: failures with validation. 28057 - SWIFT: 2002: VAL: MT103 invalid data pattern in 53B 28059 - German CSD3 Refresh install contains one garbage char 28088 - Correct m_Parent issues 28090 - Sub-field naming for SWIFT field 71F is incorrect 28099 - Failure using EVAL() in filter node on OS/390 28123 - SWIFT: Mset Problem MT500 field MT500^A should be optional 28124 - SWIFT: MT330 Fails to parse 28165 - SWIFT - 2002 failures: MT210, MT306, MT307, MT308 28171 - SWIFT - Modelling problem with 2002 MT321 28172 - Update the preimporter 28180 - The NT/2K CD for CSD03 does not install. 28183 - SWIFT : Missing sequence B1 in MT571 definition 28185 - Allow for MQSeries differences in endmqlsr 28187 - SWIFT: MT700 41D: extra inserted. 28195 - SWIFT: 2002: MT500 missing optional seq B1 not parsed correctly 28198 - SWIFT: 2002: MT514 SeqE shoulkd allow 3 not 2 repeats of 22F 28199 - Embedded messages no longer separated by delimiter of parent 28202 - SWIFT: 2002: MT536 etc. 98A/B/C repeats incorrect 28203 - SWIFT: 2002: MT519 etc repeats of 94C incorrect 28210 - SWIFT: 2002: repeats wrong in MT529 for 70 28213 - SWIFT: 2002: MT584 17B repeats wrong. 28215 - SWIFT: 2002: MT574 data pattern inccorect causes parse fail 28216 - SWIFT: 2002: MT578 seqE 17B should be optional 28217 - SWIFT: 2002: MT308 some msgs give BIP5371 with tags 22H or 19B 28221 - SWIFT: 2002: MT380 test 0004 fails with BIP5377 28228 - During uninstall psapi.dll gets locked by MQ5.3 28229 - SWIFT: 2002: MT513 test 1661 gives BIP5375 on seq F 28238 - SWIFT: 2002: MT500 parsing error 28241 - SWIFT: 2002: MT519 95S/P/U/R repeats wrong 28246 - SWIFT: 2002: MT578 seqD 20C should have 2 repeats 28247 - SWIFT: 2002: MT308 tests fail due to 70C in B4B being mandatory 28276 - Abend of DFE following several thousand SWIFT tests 28332 - Datetime problems 28350 - The MQInput node 'validate' property should not be present 28362 - Mandatory binary elements 28375 - AS400 database: (GEAC) broker loops in fetch with Client Access 28514 - MRM- Empty tags in mcd cause broker aben 28532 - Tag comparisons in parser 28548 - Res. Mgr. caching of dictionaries failing 28612 - Persistent msgs written to Temporary Dynamic Queues 28668 - Plug-in Wizard attribute group drag and drop 28682 - Finish of import dialog should be disabled if no text entere 28704 - Merant Driver Manager update 28706 - Aggregation performance improvements 28755 - Apply track 27891 in CP000_dea 28946 - REGR:Drag and drop into an execution group fails with BIP00004E 29097 - ERRMSG BIP5452 has minor typo 29100 - Unable to drag & drop more than 1 msgflow into an exgrp 28946 29144 - Build error on 390 caused by defect 28514 9177 - Inconsistent adding of brokers between Domain and Topology pan CSD03 _____ This is CSD03 for WebSphere MQ Integrator Broker Version 2.1. It is delivered via the following PTFs:- - U200179 for Windows NT/2000 - U483830 for AIX - U483937 for Sun Solaris - U483938 for HP-UX It contains fixes for ALL the problems listed below: Name - Abstract IC33925 - CUMUL MAINT 01 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR NT IY32346 - CUMUL MAINT 01 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR AIX IY32347 - CUMUL MAINT 01 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR HP-U IY32349 - CUMUL MAINT 01 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR SUN PQ62540 - CUMUL MAINT 01 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR Z/OS PQ63435 - CUMUL MAINT 01 FOR WEBSPHERE MQ INTEGRATOR BROKER V2.1 FOR Z/OS IC28837 - RENAME A DEPLOYED FLOW, DEPLOY EXEC GROUP SHOWS NEW FLOW NAME I IC29837 - COMMIT BY GROUPID DOCUMENTATION NOT CLEAR ABOUT ROLLBACK IC30627 - EXPLANATION OF CARDINALITY FUNCTION IS INCOMPLETE AN IC30970 - GLOBALLY CO-ORDINATED FLOW INVOKING NEON PARSER CAUSE XA PROBLE IC31219 - MQSI STACK OVERFLOW BY MESSAGE FLOW THAT LOOPS IC31421 - IN MQSI 2.0.2 USERIDENTIFIER IN MSG CONTEXT GETS SET THE USERI IC32774 - PROBLEM WITH COPY MSG HEADERS IN COMPUTE NODE IC32883 - BIP5341 ERROR IS THROWN WHEN ASSIGNING DATE VALUES TO THE MRM IC33120 - IMPROVE DOCUMENTATION ON THE NEW BEHAVIOUR OF PARSERS IC33126 - INCORRECT COPYBOOK IMPORT CAUSES CONFIGMGR TO HANG IC33163 - MQI V2.1 MRM CWF PARSER BEHAVIOUR NEEDS TO BE CHANGED TO OPERAT IC33180 - THE MRM PARSER WILL NOT ACCEPT AN MRM FOLDER THAT HAS ANY FIEL IC33382 - TDS PARSER THROWING ERRORS FOR REPEATING FIELDS. IC33383 - INSTALLING THE CSD02 ON A CONTROL CENTER MACHINE ONLY GIVES IC33412 - XML TO IDOC CONVERSION RESULTS IN TIMESTAMP PROBLEM IC33445 - VISUAL DEBUGGER CAN'T HANDLE MESSAGE FLOWS IN WHICH THE MQINPUT IC33480 - BIP5009 PARSER ERROR - VISUAL DEBUGGER ADDS SPURIOUS END TAG IC33490 - COBOL IMPORTER INCORRECTLY SETS THE PADDING AND JUSTIFICATION IC33549 - AIX BROKER CSD02 UNABLE TO PARSE TAD/DELIMITED MESSAGE - TREATI IC33588 - EXTENSIONS TO MQSIIMPEXPMSGSET TO HANDLE ERRORNEOUS COBOL IC33610 - BIP0068E CONTROL CENTER STARTUP PROBLEM IC33627 - CCI_EXCEPTION PLUGIN SAMPLE TO BE UPDATED TO INCLUDED AN EXAMPL IC33693 - BIP1812S WHEN IMPORTING COBOL COPYBOOK ON MQ V5.2 IC33699 - DEFAULT VALUE FOR THE DATE IS NOT BEING UNDERSTOOD BY ONE OF TH IC33728 - MRXCOBOL.DLL OMITTED ON CC ONLY INSTALLATION. IC33871 - WMQI TRIMMING FIXED LENGTH ELEMENTS IS CAUSING PROBLEMS. IC33959 - MQSIREADLOG/MQSIFORMATLOG GIVES BIP8029E ERROR WHEN USERI IC33962 - MRXYYYY.DLL'S BEING UNLOADED AS MSG SETS ARE BEING WORKED ON IC34041 - CONTINOUS PUBLICATION NODE RESULTING IN EG FAILURE WITH BOOTSTR IC34060 - PROBLEM WITH ESQL EDITOR IN THE COMPUTE NODE WHEN ENTERING WHEN IC34115 - COBOL SIGN KEYWORDS NOT USED ON DECIMALS DURING IMPORT IC34191 - COBOL COPYBOOK IMPORTER SETS MINOCCURS INCORRECTLY IC34206 - SCADA SUBSCRIPTION FAILS ON 2ND BROKER IN A COLLECTIVE IC34246 - BIP2461E WHEN INTERNALLY CASTING CHAR TO DECIMAL IC34289 - WHEN AN EXECUTION GROUP IS RENAMED - IT REVERTS TO THE OLD NAME IC34391 - DB2 INSTANCE PARAMETERS MAXAGENTS AND MAXAPPLS NEED TO BE SET IY21834 - case#1274377 CHAR CONVERSION NOT PERFORMED ON CLOBS PASSE IY26056 - ADDING MQCIH HEADER TO THE MESSAGE AND ENCODING AND CCSID VALUE IY27441 - MQSI V202 BROKER CAN T RESET BIP2135E STATUS ONCE THE MESSAGE IY28005 - LOOP ON MSG BIP2609E BIP2608E BIP2610E IF THE MQINPUT NODE IS A IY28995 - BIPSERVICE TERMINATING ON AIX IN AN ENVIRONMENT WITH LOT OF MQS IY29128 - BROKER 'CONFIGURATION MESSAGES' ARE SENT TO THE MQSERIES DEA IY29419 - BROKER EXITING EARLY BEFORE CONFIGURATION MESSAGE ARRIVE FROM E IY29461 - ADD TO DOCUMENTATION THAT IT S NECESSARY TO HAVE A MATCHINGCALL IY30451 - BROKER ABENDS WHEN PARSING AN XML MESSAGE AGAINST A MESSAGE IY30965 - WMQI V2.1 PARSER LOOPS IF NO MESSAGE BODY TO AN XML DOCUMENT IY32778 - MQSILIST COMMAND SHOWS NO RESULT OR ERROR IY32888 - PROBLEMS WITH DEPLOYING THE EXECUTION GROUPS THAT ARE IN INVALI IY33138 - INPUT MQRFH2 MCD FOLDER DETAILS INCORRECTLY USED IN RCD NODE IY33268 - EXECUTION GROUP ABENDS AFTER SELECTING THE CONTINUE WHEN A FLOW IY33912 - MESSAGES GO TO DEAD LETTER QUEUE WITH DLH REASON CODE 65536 PQ56571 - MQSICREATEBROKER ON Z/OS FAILS WITH INCORRECT INSTALL PATH PQ57687 - SETTING FOR ICU_DATA IS ERRONEOUS PQ59154 - RUNNING MQSICUSTOMISE CAUSES DATA TO BE APPENDED TO BOTTOM OF PQ60310 - 0C1 ABEND WHEN STARTING WMQI DATAFLOW ENGINE PQ60976 - LARGE MESSAGES IN MESSAGE FLOW CAUSE DEBUGGER TO LOSE PQ61201 - 'LOCAL ENVIRONMENT' IS BEING CALLED 'DESTINATION LIST'BY DEBUGG PQ62125 - NEED DOCUMENTED GUIDELINES ON LOGGING 1GB LOB COLUMNS. f13552 - Improved Flow of Control in SQL f13638 - Improve ConfigMgr Role Management f14155.1- MRM dictionary validation f14313 - Relocatable runtime capability needed on UNIX f18003 - Unable to insert BLOBs/CLOBs of >4k in oracle f19256.4.1 - Implement indexes on non-390 platforms f19256.4.3 - Make broker table lock switchable f19604.2- Performance enhancements: DataFlowEngine f20573 - Exit to flow NT domain info from Control Center f23727.1- Reduce AdminAgents memory requirements on deploy f23841 - Enhanced BITSTREAM function f24881 - Improve scalability of large message processing f24911 - Upgrade MQSeries Everyplace to latest level f25127.2- Enhanced THROW statement f25879 - Optionally disable comment in MRM-XML f25959 - Allow amount fields to contain a trailing comma f25963 - Parsing using regular expressions f25967 - mqsiimpexpmsgset defaults reset f26060 - ModelMessages.properties correction f26066 - Datetime defaults inconsistent between CWF and TDS/XML f26081 - GenXML: Enable quotes in Processing Instructions f26087 - General feature for the SWIFT messageset work f26106 - Error Message Architecture review for MRM f26124.1- Generate runtime objects for SQL f26172.1- Minimise UnicodeString use in dataconv f26172.2- Remove UnicodeString from bitstreamworkerstatechecker f26309 - A set of User/Group Plug-ins to improve Performance f26336 - Optimized (small) jar for MQe clients f26480 - CSD03: ship new WMQI license text f26613 - Support for E format floats in TDS f27332 - Customers want to access the database from inside SQL routines f7631.3 - Allow zero or more input terminals in the plugin wizard 10775 - BIP2212: Error message does not say which node caused the error 11522 - mqsicreate... qmgr exists but no DLQ 11721 - C & P. Cross-msg-set warning is insufficiently selective 13040.4 - Allow format field of header to be set for IDO 14996 - Change default setting in export preferences 15614 - Errors written to event log when catch terminal is connected. 15624 - MQInput node catch terminal changes the exception list 15869 - Smartguides : Element no removed from list if added to Summary 16522 - Inconsistent behaviour if renaming broker & checked in Topology 17516.3 - CWF Padding char different on 2.1 from 202 17877 - MRM-Properties Pane History and Description Tab entries lost 18047 - MRM-BIP0074E 1. presentation inconsistent 2. Inappropriate wor 18229 - Database Node message now appearing on Failure Terminal 19266 - MRM msg BIP0707E text 19501 - Broker subscriptions cannot be deleted using the delete key. 19508 - Default domain list for MQInput, MQeInput etc needs JMSdomains 19557 - Help window doesn't close when Argo is shut down 19575 - Help "Tour" window close when Argo is shut down 20175 - Need to characterise behaviour of XA with 2 DSNs resolving to a 20256 - spaces in physical format name causes problems 20501 - cut and paste of elements not working for XML layer in CC. 20583 - String "PublicGroupRef" not translated in Topic View 20676 - DFE startup trace cannot be obtained. 20715 - Cannot access 'Refresh' using shortcut key 20999 - Testing TDS properties values unitary, MRM refuse EUI right val 21369 - MRM: When changing properties of a type within a sequence type, 21446 - Command-line usage is inconsistent with other products 21459 - loop back connections hidden if nodes are rotate 21565 - List option gives wrong error message 21640 - CC Syntax Checker rejects UUIDASxxxx functions on RHS of !! fn. 21715 - CAST decimal to decimal fails 21770 - Consistency between Syntax Check of BITSTREAM and FIELDNAME fns 21826 - tdsextractor: Incorrect text in warning message - PT_WARNING 21989.1 - Validation of CWF pad character 22077 - Improve ImbLanguage tracing 22367 - Tidy up ImbConsoleParser code 22506 - Debug node shown in Add Message Flow list only on Assignments 22514 - 'Undo' does not fully work on Assignments page 22594 - Remove Delete of element under elementQualifier should disable 22607 - Missing mnemonics Value Constraint/Language Binding/Physical Fo 22612 - Create an element with an existing name should be forbidden 22672 - Messages 9141 & 9142 should be informational 22854 - Wrong logo for warning message in Topics properties 22930 - ERRMSG: BIP5511: inserts wrong, raw conversion error code 22980 - ERRMSG: MRM BIP5180 message text 22983 - ERRMSG: MRM BIP5505 message content 23060.1 - Remove use of MQSI_DONT_XA_UNENLIST 23130 - TDS floats don't use non-standard negative signs on output 23436 - BIP9177I is misleading. 23456 - MRM-Check-out confusion follows Finalize Failure 23514 - Progresss bar in Visual Debugger title contains MQSI reference 23550 - FIELDVALUE function badly neede 23623 - ERRMSG: MRM BIP5199 message content 23729 - Length of element.Tag value should equal parent type.Tag Length 23761 - dump of BAGGRGEATE table does not correctly show NULL data 23764 - insert missing from message - so produced wrong value 23794 - The message BIP8137 is uninformative 23931 - Copy message flow after compute node properties 23988 - 2.1->2.02: Relax broker to allow bytes for Ext Dec Length Units 24007 - Message in rstclog written incorrectly. 24037 - Create Broker uses -k flag with diff meaning to 2.1 24090 - Semaphore can be left locked if exceptions are thrown 24116 - RFH2 Parser is very slow 24149 - Message BIP9172E should be BIP9172I. 24232 - MRM-4 MRMBxx22 testcases are failing 24287 - BIP2163 text missing apostrophe 24344 - MRM Generate messagebook xtrcterr.log content 24414 - Import MFs - Wrong displayed BIP0662W when there's MF category 24433 - Debugger - No mnemonic for the Settings in Actions menu 24434 - Debugger - Mnemonic "O" is used twice in Actions menu 24464 - Plugin Node - After drag and drop , attribute duplication 24499 - OS390: 2060 should be sent to the console by default. 24575 - Inconsistent behaviour when more than one choice in message. 24589 - Repeating compound type >max occurs not output correctly in CWF 24694 - Type-o in scripts/...template/dsnaoini SUBSYSTEME 24733 - Aggregated response contains data from another group 24805 - MtiImbSyntaxElement::copyElement(ImbSyntaxElement* source) 24861 - MRM Skip count does not work for compound elements 24997 - Messages BIP2206I, BIP2282W, and BIP2320W are obsolete. 24998 - Message BIP3902I is obsolete. 25045 - Check for correct ODBC driver level 25072 - Aggregation node gives DB2 error 25178 - TDS doesn't output default values for missing fixed elements 25369 - Multipart: Message embedded in choice failing for AED/VL/FL 25427 - TDS Fixed length output incorrectly for repeating choice. 25431 - Using DBCS name does not seemed to work 25456 - ERRMSG: Wording of BIP5429E needs amending 25527 - Bad error message when saving log 25559 - MRM BIP5168 message content 25573 - -l option iseen n help text for configmgr commands 25590 - Invalid field values in MQM 25600 - RecoverableException ?????????? 0 ?????????? 25652 - MQeMbMsgObject's priority field set incorrectly 25672 - MQMD field values differ between MQe & MQSI 25673 - Exception on setting value 9996 into Feddback field for Mb msg 25735 - setUniqueId declared as public in MQeMbMsgObject 25746 - MRM- Null Handling CWF Integer Extend Dec Padded Literal Null 25748 - ERRMSG: CWF General Error BIP5167 insertions are muddled up 25754 - GUI allows TDS esc of more than one char 25758 - Data conversion to code page 932 (double byte) and back to 437 25824 - MRM TDS and multipart message keys 25830 - Select As Function is wrong flagge 25835 - Call to execute a Stored Procedures fails on z/os. 25842 - MRM- Null Handling TDS Fix Length Float NullLog / Pad confusion 25857.1 - XML Schema Extensions and Restrictions 25899 - Changes with 25636 coming up in English on NLV 25903 - Not seeing Control Center log if security exits set MCAUserI 25914 - MRM:No hourglass cursor while expanding large message subtree 25925 - EVAL cannot execute a CALL statement 25934 - CWF:Multiple levels of unresolved messages/choice not supporte 25939 - Add message popupmenu item only available on Compoun 25978 - TDS Validator to check for unbounded repeats 25986 - PrivateRegistry causes MQeInputNode failure 25993 - Deploy failures cause a cascade of failures 26002 - Unable to add panes for nested multipart msgs in compute node 26003 - In the EUI, Attributes cannot be specified on the XML Root Tag 26014 - BIP5355 messgae content 26016 - STRESS: BIP8303 produced by broker during cache update 26019 - Syslog does not report failure to load lils 26022 - Insert missing in BIP9170E when compcif not found. 26024 - Aggregation stress test abends after 20 mins 26042 - MRM- Broker Abend due to 'StrToDatetime' metho 26046 - MRM TDS Message Format with NULLs not Parsing Correctly on 390 26054 - MRM-Trace node stops tracing tree at an unresolved choice. 26075 - MRM-CWF IEEE floats not as accurate on 390 as they should be 26076 - Stack overflow in TDS parser 26084 - Certain MRM tests fail on AIX and Solaris. 26086.1 - Covering TDS Parser side of 26086 26091 - Incorrect length of ISA 26096 - Regression breaking plugin input nodes with MRM messages 26097 - Stopped flow not recreated on broker stop/restart 26109 - Broker abends when parsing an XML message 26127 - broker crashes if java node accesses GlobalEnvironment 26130 - MQe/SCADA Participant tables are not protected by a semaphore 26131 - In testing for repeating tags look for group in 26133 - MRM CWF setting to null unexpected short message 26134 - mqsimrmimpexp - mispelling in help instructions 26137 - MRM TDS Data lost on output 26138 - BIP2011 message content 26140 - NT handling of 390 floats has regresse 26155 - ERRMSG: BIP5004 full of meaningless numbers and terms 26160 - Multiple topics import incorrectly 26181.2 - CC not prevent user to repeat element in simple unordered type 26182 - Poor diagnosis of missing length count 26185 - Pubsub expiry tests failing since clock change to BST 26189 - DTD Importer-Imports mixed content model as ordered set 26190 - Abend of DFE when a message set is deploye 26193 - Use of 16S as group terminator failing in TDS 26198 - MRM- XML Schema Importer incorrect treatment of "fixed" 26203 - MRM- XML Schema Importer namespace errors 26225 - MRM- XML Schema Importer NOTATION datatype not recognise 26226 - MRM- XML Schema Importer Name datatype not recognise 26227 - looks like a syntax error in ImbPointer.hpp 26237.1 - CMI: (stddi) BIP5323, BIP5323 defined in wrong place. 26237.2 - CMI: (bsutils) New PWFCh & PWFString implementation breaks CMI 26237.3 - CMI: (stddi) StdDictionaryIterator uses ImbOwnedLogSource 26237.4 - CMI: (cwf) CWF worker specific CMI resync changes 26239 - MRM- XML Schema Importer "use" clause on attribute not importe 26247 - Sample DB2 switch load file must be rebuilt for MQ 5.3 26248 - MRM- XML Schema Importer wrong treatment of recursive import 26249 - GenericPropertyParser class name should bt upper case 26272 - Parsing of empty 16R 16S sequence fails 26307 - DFE fails to start with 0c1, if region size too small 26317 - MRM- XML Schema Importer MaxExclusive for STRING wrong 26321 - Change abend code from 2C3 to 2C1 26322 - MRM- 5354E MTI Internal Error with TDS layer 26324 - CWF parameter 'First Week of Year' in message sets on C 26339 - MRM- XML Schema Importer "nil" namespace prefix 26343 - MRM- XML Schema Importer using Finalized Message Set 26380 - MRM- TDS Writer Internal Error BIP5432 26384 - Performance inline 26398 - e-fix2961:Broker abend with TDS containing embedded message 26425 - TDS with VDP set and explicit decimal gives incorrect output 26431 - Parsing of LX loops in X12 not correct 26439 - mqsi_setupdatabase creates link for wrong libraries 26447 - Glossary generates the German version. 26454 - HOT: MRM-Certain chars in doctype text cause serious CC errors 26460 - Import Topics enabled and processed when Topics not checked-out 26471 - Multipart messages with absolute paths cause abends 26475 - MRM- Broker Abend when writing to TDS with Base & Simple Types 26491 - MRM DTD Generator and Choice elements 26499 - mqsideploy -r doesn't work in Japanese environment (CCSID=932) 26502 - No retry on BSUBSCRIPTIONS table lock. 26503 - Hang in JVM during DFE termination. 26536.1 - Disable Member Rendering for Compound Elements 26572 - I enter a direct setting to a float in the ESQL of a compute no 26594 - Syntax checker flags CREATE ... AS X as error 26616 - Registry setting needed for trace file size 26628 - Exception for TDS input of multipart recursive message 26645 - ESQL statement deleted if comment was defined in another Locale 26646 - 'Reply Queue*' fields NOT disabled when 'Request' is unselecte 26664 - Unknown locale "null" causes core file 26672 - load failure of brokerprincipalsg110 when broker security set 26691 - Priroty being allocated to higher level repeats in X12 26700 - MRM- Datetime Element Value does not allow 24hr clock times 26717 - Oracle package names not recognised on CALL of external (store 26725 - Warning 2235 generated during broker deploy 26738 - Arguements not being passed properly 26744 - Need way to call JVM signal handler on aben 26747 - XML - Inconsistent xmi.label for Suppress Timestamp Comment 26779 - oracle9i changes for solaris and HPUX in mqsi_setupdatabase 26787 - Invalid CCSID causes aben 26796 - configmgr jvm heap size goes negative 26805 - MRM- DateTime template value constraints can't be deploye 26820 - MRM- Decimal Output incorrectly truncated - REG 26822 - MRM- Decimal TDS Precision not working correctly 26865 - Precision should not be applied to float or decimal on iput 26867 - S210M-L20529_D solaris MRM m/set deploys fail. 26869 - Incorrect conversion of MbXException to ImbRecoverableException 26871 - Missing text continuation characters in ModelMessages file 26881 - A call to getData() on a MtiImbSyntaxElement Usertrace error 26883 - Package new UserGroup plugins 26890 - When creating the execution group, it appears to pass although 26892 - bipconfigmgr.exe dies when connection from Control Center attem 26898 - Plugin Sample code causes exception violation. (STILL) 26904 - ImbParserManager.cpp", line 76.100 26916 - Never deleting iMutex in ImbConfigurationNode::Transaction 26924 - Japanese translation error on MRProject_ja.properties 26926 - MRM-XML Suppress Timestamp Comment should be Yes/No dropdown 26931 - Unable to use new version of MA88 in Java node. 26935 - MRM-MRMB3426 causes dfe to enter tight loop 26938 - MRM-Can no longer import old message set 26950 - Params_ko.properties needs fixing 26953 - MRMBVT failing 26958 - BIP2160 abend on tdsparseitem.cpp 26964 - ClassNotFoundException when using JNDI in Java node. 26970 - MRM-2 simple consecutive compute nodes cause BIP5502E 26974 - DECIMAL paramters in stored procs don't work 26977 - BIP2110 during thread cleanup 26986 - MRM- Regression in Null Handling of FLOAT 26991 - Hyphen can be typed in the message identifier, although it is n 26996 - Length Encoded Length flagged wrong 27004 - CREATE AS does not set MODIFIABLE on Field Ref 27008 - SegV When null datasource specifie 27019 - DTDImporter- Orphan elements' type member mishandling 27034 - Remove extraneous material from DTD Importer GUI 27041 - Looping in that while loop again 27045 - looks like a problem with tdsparseitem.cpp 27052 - Problems adding to an element of CT message 27063 - With Validate set back to None - wrong values at runtime 27065 - MRM-The vast majority of MRM testcases failing on all platforms 27073 - Remove redundent compile flag MTINLS for 390 27080 - MRM-All MRM testcases still failing on all platforms 27082 - MRM- Length of Encoded Length Fiel 27086 - REGR: BIP2329 in RCD node 27087 - mqsicompcif missing from 390 tape install 27128 - SELECT fails when called from within a procedure / function 27143 - Invalid xml in deploy causes invalid flow deployment 27144 - MRM- CWF 1 Byte Integer wont accept values > 127 27145 - SELECTed CLOBS on Oracle are corrupted when > 2000 Chars 27147 - Element Qualification tab disappering for Element under Message 27153 - Missing SqlParser.tables for feature 13552.1 27154 - Lots of Errors in /MTI/MTIforBroker/MtiImbParser2 27156 - Invalid Control Center title for Event Broker version 27161 - Default Values 27171 - ERRMSG BIP 5199 Insertion not working 27184 - Create bip5448.msg in S210 27190 - MRM- Validation exceeding maxOccurs gives 5371 instead of 5375 27191 - MRM- Validation BIP5374E Insertion for MinOccurs is out by 1 27199 - Create bip5447.msg in S210 27200 - InputDestinationList correlation name not working 27201 - MRM-"SET OutputRoot=InputRoot;" causes MRM XML msg to be parse 27204 - MTIParser.cpp: Operand for "->" must be a pointer or array 27207 - Incorrect handling of NULL's in + - * / operations 27208 - DFE abend with character class regular expression 27209 - spurious delimiters occur in variable elements delimited mess 27215 - wmqpsreporttrace -e returning unexpected default trace size 27217 - MRM- Validation not carried out for flow: MQInput->MQOutput 27218 - Correct path for MtiImbValueValidator 27222 - Fixed Al3 not outputting ? 27239 - Last thread returned to thread pool in plugin input node 27245 - Good Bye FUNCTION TRACE 27246 - MRM- Tagged Delimited discards Binary el data 27248 - MRM- Interaction of Datetime Template with "I" format string 27250 - Can't deploy Fixed Length parent with Use Data Pattern chil 27253 - Too many bipmsgs for missing mandatories on output 27257 - MRM- Control Center cursor control causes craziness 27258 - MRM Validation - incomplete TDS message written with validation 27261 - Still errors in MTIImbParser.cpp 27268 - "pattern" role icon is missing 27269 - Exception caught on changebroker when serviceid not correct 27274 - Problem using reclaimed syntax elements. 27277 - SELECT with WHERE and XML.attribute does not work 27280 - ImbAbend not initialize 27286 - Closed message working like open define 27296 - Merant driver bug fixes 27297 - SOLARIS Sybase 12.5 requires update to mqsi_setupdatabase. 27302 - MRM- Broker Abend in TDS Writer 27304 - Missing initial value for Default Time Zone ID (TDS & XML) 27308 - DFE abend when using regexp 'non-greedy' ? construct 27311 - Abend in TDSParser when testing closed validation 27317 - Fix up tdsmsgnumbers.h 27319 - Debugger gives message BIP0642 after breakpoint 27342 - New AIX UserGroup Plugins cannot be loade 27348 - MRM-Abend as TDS msg (with exponent. notation floats) is parse 27351 - Self defining element at beginning of message failing 27352 - Extraneous elements in MRM tree 27360 - Choice dictionary error 27373 - New DomainAware functionality does not work as expected. 27380 - COBOL Importer fieldname containing Group 27385 - Adding PSService node to workspace 27390 - Ensure that a XML delete message always works 27401 - Writer stuck in infinite loop 27403 - Problem resolving choices with embedded seq 27404 - Validation of embedded compound types 27407 - Error handler does not print le message inserts 27413 - ConfigMgr HeapSize should check for 2045 not 4045 27422 - lookahead parameter not being rest 27428 - MRM- BIP5354 MTI Internal Error shouldnt be put in usertrace 27431 - Broker gives STL port error for SET... = UUIDASBLOB(); 27439 - bip5502 internal error if DBCS data passed to TDS with DataPatt 27466 - Skip count omitted from choice length calculations 27467 - Skip count not extracted for compound elements 27468 - EndMessageContent sent before root tag encountere 27470 - MRM BIP2160 exercising EDIFACT TDS message 27471 - Error found in zh_TW mrmtoxmlmsgs.rc file 27476 - BIP2110 during thread cleanup 27485 - Abend when finding string length in PWFDateTimeFormatter 27487 - Error found in Pt-BR msg file bip9206 27491 - Sun's java symbol appears in Warning message box 27509 - validation tab in wrong place 27510 - Empty elements not editable in debugger 27525 - cpi/bsutils/RegExp... should be in Release CP210 27533 - Sample odbc file needs updating 27541 - MRM-Validation causes ELEM ON TREE WITHOUT VALUE internal error 27564 - Validation - Remove Timing from Compute node & alter defaults 27569 - Validate Escape Character atrribute 27585 - Repeated Java exc after multi EG startup or seq num recovery 27597 - Escaped Seg Terminator should not be interprete 27603 - MRM- REG Choice Variable Length All Elements Delimite 27619 - MRM- TDS Extractor should warn if Boolean reps are dift lengths 27624 - Memory cleanup and MQe multibroker fix 27626 - MRM- REG TDS Tagged Delimited repeating children within choice 27630 - Memory leaks in convertData in tdsparser.cpp 27631 - GetCompoundLength not coping with embedded types 27633 - min and max occurs not validated at compute node 27636 - STRESS: Oracle8.1.7 fails XA test (HY000) 27637 - Treat booleans as fixed in VED if all lengths are equal 27639 - Data pattern field wiping incorrectly. 27661 - Problem with wrong assertion check in MTIDict 27662 - Regular Expressions do not seem to be working well on AIX 27673 - Wrong index used in stddict getvalue calls 27674 - Change unsupported database message to a warning (BIP2112) 27683 - mqsidelete command with -q option fails 27686 - Incorrect .jar file on mqsilccsedm.bat file 27695 - MRM TDWF Length of Encoded Length not correctly greyed out 27702 - fields out of sequence following regular expression choice 27705 - Incorrect behaviour for CCI_SQL_TRANSACTION_COMMIT 27716 - NullPadFill Input for TDS Fixed Length not recognise 27718 - pattern role icon is missing 27722.1 - Disable CASE statement 27723 - FOR All/Some fails to deploy (FILTER) 27731 - Null permitted not being extracted for compounds with a base ty 27733 - MRM BIP5374 Message text 27751 - Configmgr does not start with BIP1161S 27759 - Tagged encoded lengths not output correctly 27761 - Dynamic Schema Name Resolution (DSNR) 27766 - Reduce occurance of BIP2061, BIP2062, BIP2063, BIP2064 27772 - Add new files to UNIX packages 27811 - Java problems connecting to cfgmgr from control centre AGAIN. 27814 - XML/TDS prperties added in F26066 are inconsistent with CWF 27816 - Errors in ImbContextSwitch 27821 - Errors in track 27705 27822 - ABEND: EXCEPTION_ACCESS_VIOLATION 27824 - VDB BIP0642 with large message 27834 - ODE pkg.parse.mk rules error in 390 service packaging 27836 - BIP4280: Control center losses connection to visual debugger 27868 - Broker internal error when DELETE cursor followed by ATTACH 27883 - pattern role icon is missing 27899 - Setting on service trace causes 0C4 abend. 27975 - MRM TDS Boolean Extractor warnings 28004 - 390 Stored Procedure test failure 28017 - MRM- Abending TDS writer 28029 - Creation of EG - UNS cores 28039 - 0c4 abend in libMessageservices.a 28058 - Japanese install bipihlpw.chm has error ####### ------- end of file MEMO.PTF ------------#######################