########################################################################
# #
# COMPONENT_NAME: MQSeries Integrator #
# #
# FILE: MEMO.PTF #
# #
# Program Number 5639-F61 #
# (C) COPYRIGHT International Business Machines Corp. 1999, 2000 #
# All Rights Reserved #
# Licensed Material - Property of IBM #
# #
# US Government Users Restricted Rights - Use, duplication or #
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp. #
# #
########################################################################
# #
# Please note that any references in this product to NEON do not refer #
# to Neon Systems, Inc. #
# #
########################################################################
PTF Memo for IBM MQSeries Integrator Version 2.0.2 for Windows NT**
------------------------------------------------------------------------
The memo.ptf file contains information you need for updating
IBM MQSeries Integrator Version 2.0.2 for Windows NT. This memo.ptf
file corresponds to the third CSD which is defined as PTF U200172
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.
CSD03 requires approximately 250MB of disk space to do this.
150 Mb of free space should also be available for TEMPorary space.
APPLYING MAINTENANCE
____________________
Maintenance updates are supplied on CD in the form of a
Program Temporary Fix (PTF), referred to as a Corrective
Service Diskette (CSD). You can find the latest
information about available CSDs on the Internet, at this
address:
http://www.ibm.com/software/ts/mqseries/
You can also download CSDs from this web site.
APPLYING THE MAINTENANCE INFORMATION
____________________________________
If you need to apply maintenance updates to MQSeries
Integrator Version 2.0.2:
1. Ensure that the user ID you are logged on with is a
member of the Windows NT ADMINISTRATORS group in the
local security domain. You are recommended to use
the same ID as the one you used for installing
MQSeries Integrator.
2. Ensure that all MQSeries Integrator function is
stopped. You must:
a. Stop execution of the Configuration Manager, the
User Name Server, and all brokers on this system
using the MQSISTOP command, or by stopping the
Windows NT services for these components from the
Services program in the Control Panel.
b. Stop execution of all programs that manage
MQSeries Integrator Version 1.1 rules and formats
(the Visual Tester, the NEONFormatter user
interface, and the NEONRules user interface).
c. Stop execution of the Control Center.
d. Ensure that you do not have any MQSeries
Integrator Version 2.0.2 files open.
3. You are also strongly recommended to exit all Windows
NT programs before applying maintenance to MQSeries
Integrator.
4. If you have downloaded maintenance from the web, you
must:
a. Read the "memo.ptf" file associated with this
maintenance on the Web site. This might contain
additional information regarding the installation
of maintenance.
b. Select a suitable destination as the target for
download.
c. When the file has been downloaded, change to the
download directory and run the executable file.
You must choose a temporary directory to extract
the maintenance files from the downloaded file.
You are presented with a dialog where you can
accept the default, or specify an alternative.
d. Click NEXT to activate the extract.
e. Click FINISH to end the dialog.
f. The "setup.exe" file now runs.
5. If you are installing from CD you must:
a. Read the file "memo.ptf" in the Readmes directory of
the CD, and any "Readme.txt" files also in the
Readmes directory. These files might contain
additional information about how you must install
this maintenance.
b. Insert the maintenance CD into the appropriate
drive. If you have autorun enabled, "setup.exe"
will start to run automatically. If you do not,
you must start "setup.exe" from the CD by
doubleclicking.
6. When "setup.exe" runs, you are presented with a
window that provides instructions for applying
service. These include a checkbox that controls the
backup of files replaced during the application of
this service level. If you take the default action to
replace these files (and you are recommended to do
so), you can specify the directory in which the
backup files are created. Click NEXT when you have
made the updates you want. A confirmation window
displays your choices. Click NEXT to continue, or
BACK if you want to return and make further changes.
7. The maintenance is applied to MQSeries Integrator.
You can cancel this action at any time by clicking
CANCEL.
The maintenance process backs up updated files in the
subdirectory "\CSDbkup" in the MQSeries Integrator
Version 2.0.2 home directory. If you click CANCEL
before the maintenance process has completed, these
backup files are restored and the maintenance backed
out (the CSD is not applied).
8. When you have completed installation, review the
"memo.ptf" file supplied as part of the CSD. Complete
any manual post-install actions required.
NOTE: CSDs are cumulative, therefore you do not need to
apply CSD1 before you can apply CSD2. When you have
installed a CSD, you are prevented from installing a
previous CSD without first restoring the system using the
backed-up files.
RESTORING A PREVIOUS SERVICE LEVEL
__________________________________
You are able to restore a previous service level if you
want to, or if you are instructed to do so by your IBM
Support Center. However, this is only possible if you
accepted the default action to backup replaced files when
you applied the current service level (see the
instructions in "Applying the maintenance information").
If you need to restore MQSeries Integrator to a previous
level of maintenance:
1. Ensure that the user ID you are logged on with is a
member of the Windows NT ADMINISTRATORS group in the
local security domain. You are recommended to use
the same ID as the one you used for installing
MQSeries Integrator.
2. Access the Windows NT Control Panel
(Start->Settings->Control Panel).
______________________________
3. Double-click the Add/Remove Programs icon.
4. Find and highlight IBM MQSeries Integrator V2.0.2, and
____________________________
click ADD/REMOVE. This starts the MQSeries Integrator
uninstall program, and presents the uninstall dialog.
5. If one or more CSDs have been applied the dialog
allows you to select the option to uninstall CSDs.
Select the option to uninstall the most recently
installed CSD and return to the previous service
level. If you want to remove all CSDs, you must
invoke this option for each one in turn to return to
the base service level.
If no CSDs have been applied, this option is
unavailable.
You are able to restore a previous level of New Era Of
Networks V5.2 by accessing the New Era of Networks installer.
By uninstalling the latest version of the infr file,
ie n0infr20_45 the previous version will be restored.
REMOVAL OF THE NEW ERA OF NETWORKS COMPONENT
--------------------------------------------
To uninstall New Era of Networks V5.2 you should to use the
Add/Remove programs dialog found under the Control Panel. Note
that having uninstalled the New Era of Networks component you
need to reboot before reinstalling, otherwise attempts to
uninstall New Era of Networks V5.2 in the future may fail.
If New Era of Networks uninstall fails then the following manual
steps can be used to remove it.
1. Remove the registry entries under
HKEY_LOCAL_MACHINE\SOFTWARE\New Era of Networks
2. Delete the files from the neonsoft directory
3. Delete neoncomp.ics from your WINNT directory (normally c:\WINNT).
4. Remove the uninstall registry entry for "neoncomps" in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Steps 1 and 4 above involve working with the Registry and you are
advised to ensure that you have suitable mechanisms for recovering the
registry in case of errors.
INSTALLING NEW COMPONENTS AFTER APPLYING MAINTENANCE
____________________________________________________
If you install maintenance and then decide to install a
new component from the MQSeries Integrator CD, you will
be advised that you must reapply the maintenance
following installation of the new component. You are
strongly recommended to do this: if you do not, it is
likely that the integrity of the product files will be
compromised and unexpected results might ensue.
FAILURE DURING THE APPLICATION OF MAINTENANCE
_____________________________________________
If you have a failure when applying a CSD (for example,
a power failure), the product files are likely to be in
an unknown state, especially if existing files have been
replaced. You must rerun the installation of the
maintenance (to completion) before using the product.
To recover from this situation, assuming you accepted the
option of backing up replaced files you should:
Copy the contents of the backup directory (CSDbkup\1 for
CSD#1,unless you chose a different backup location) back
into their original locations. This is most easily done
using Windows Explorer and answering yes to the message
asking whether you want to replace existing files files.
You can then rerun the CSD install.
You can manually re-invoke the New Era of Networks 5.2
upgrade as a separate exercise using setup.exe from the
Neon52\n6nrf52_152 directory on the CSD image.
CHECKING THE SERVICE LEVEL
__________________________
After initial installation, the MQSeries Integrator
Service level indicates no service has been applied.
After one or more updates, the service level is updated
to show the CSD most recently applied. The service level
is expressed in terms of the PTF number for a particular
CSD.
To check the service level, select
Start->Programs->IBM MQSeries Integrator 2.0.2->Service Level.
______________________________________________________________
This displays the "memo.ptf" file containing the service level
and details of the maintenance applied (PTF Number). This file
is installed in the program file directory.
APPLYING MAINTENANCE TO IBM DB2 UNIVERSAL DATABASE
__________________________________________________
If DB2 was installed on this system by the MQSeries Integrator
installation program, DB2 7.1 is installed with no service applied.
If using an existing DB2 6.1 database then fixpack 7 is required.
You can also obtain information about the current status
of maintenance of this product, and download fix packs
for DB2 from this Web site:
http://www.ibm.com/software/data/db2/udb/
APPLYING NEW ERA OF NETWORKS MAINTENANCE INFORMATION
____________________________________________________
As part of the install of maintenance the NEONRules and NEONFormatter
support will also be upgraded if it is installed. This will present
itself as a series of separate InstallShield 6 component installs that
take approximately 10-15 minutes in total.
It is possible to install maintenance for NEONRules and NEONFormatter
manually by running setup.exe from the location pointed to by the
autorun.inf file in the Neon52 directory on the image.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
DOCUMENTATION CHANGES
---------------------
IY28520 - 2.0.2 MANUALS NOT CORRECT IN STATING HOW TO BUILD A
NEONMSG MESSAGE GOING OUT OF A MSGFLOW.
In WebsphereMQ Integrator V2.1 the Working with Messages manual,
SC34-6039-00, expands on the small section in the MQSeries
Integrator V2.0.2 manual Using the Control Center about Creating
a NEONMSG domain message. It explains the difficulty with
repeating formats and covers the method of overcoming it and is
reproduced here.
Transforming from XML and MRM to NEONMSG
You can use the facilities provided by the message processing
nodes and the brokers to transform an input MRM or XML message
to an output NEONMSG message. However, you must be aware that
the NEONMSG parser does not recognize repeating fields in these
messages: if the input message includes repeating fields the
output message generated will not accurately reflect the input.
If the input message is an XML message, you can manually edit
the message to insert the attribute NEON-XML-repeating="true"
to each repeating field. For example, an input message might
contain:
IBM
1234-L
Large Widget
1234-M
Medium Widget
1234-S
Small Widget
This must be manually edited to contain:
IBM
1234-L
Large Widget
1234-M
Medium Widget
1234-S
Small Widget
If the input message is MRM, the message cannot be manipulated
and any repeating fields will be lost in this transformation.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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');
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IC30818 - DEPLOYING FROM A 2.0.1 CONFIGMGR TO 2.0.2 BROKERS.
Deploying from a V2.0.1 Configuration Manager to a V2.0.2 Broker is
not supported.
After installing V2.0.2 and migrating brokers to the
V2.0.2 level or creating new brokers, it is not possible to deploy to
those brokers from a V2.0.1 Configuration Manager. The Version 2.0.1
Configuration Manager must be upgraded as described in Chapter 9 of
the MQSeries Integrator V2.0.2 Administration Guide, SC34-5792-04.
This Guide will also be updated to include the following note under
the existing heading 'Upgrading your Version 2.0.1 brokers':
When upgrading any brokers to Version 2.0.2, the Configuration
Manager used to deploy to those brokers must also be upgraded to
Version 2.0.2.
Deploying from a V2.0.1 Configuration Manager to a V2.0.2 broker
is not supported.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SPECIAL INFORMATION
-------------------
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.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IC30888 - THE MQINPUTNODE ADVANCED PROPERTIES FIELDS MATCH MESSAGE ID
AND MATCH CORRELATION ID HAVE CHANGED IN V202.
The MQInputNode Advanced properties fields Match Message ID and Match
Correlation ID have changed from input fields with a default value of
'no' in V2.0.1 to check box fields in V2.0.2. This situation has been
corrected however the following actions need to be taken to activate
the resolution:-
1. Copy the provided file ComIbmMQInput to :-
MQSI_SETUP_DIR\primitives\MessageProcessingNodeType and
MQSI_SETUP_DIR\Tool\repository\development\MessageProcessingNodeType
directories to replace the existing file.
2. Logon to an NT session as IBMMQSI2. For this specific task this user
must belong to groups mqbrdevt, mqbrasgn, mqbrops and mqbrtpic).
3. Open the MQSI Control Center.
4. Unlock the MQInput node.
5. Check-out the MQInput node.
6. Replace the file ComIbmMQInput which is located in the private
repository directory (this should be MQSI_SETUP_DIR\tool\repository\
private\\\MessageProcessingNodeType) with
the provided file.
7. Save the workspace or quit MQSI Control Center, saving workspace.
8. Open the saved workspace or reopen the MQSI control center.
In the MQInput node advanced properties, verify on the right of the
fields 'Match Message ID' and 'Match Correlation Id' the check boxes
have been replaced by text editors.
9. Check-in the MQInput node.
10. Check-out the MQInput node to prevent other modifications.
11. Remove the ComIbmMQInput and ComIbmMQInput.wdp files from the
private repository directory.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IC31219 - MQSI STACK OVERFLOW BY MESSAGE FLOW THAT LOOPS
This problem has been resolved by extending use of the environment
variable MQSI_THREAD_STACK_SIZE, to the NT platform. This variable
was first introduced for the Unix platforms in IY21179, DFE CONSUMING
HIGH CPU AND HANGING WITH NO ERRORS.
The stack size should be specified in bytes, so to override the
thread stack size on NT to 2MB for example, set the following
environment variable:-
MQSI_THREAD_STACK_SIZE=2000000
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IY21179 - DFE CONSUMING HIGH CPU AND HANGING WITH NO ERRORS
A message flow that processed a message successfully on NT failed to
complete on AIX. This was due to a stack overflow problem on AIX.
On Unix platforms, MQSI overrides the default thread stack size and
allocates a stack size of 1MB to each thread.
This problem has been fixed by allowing the default thread stack size
of 1MB on Unix platforms to be overridden by use of a new environment
variable:- MQSI_THREAD_STACK_SIZE
The stack size should be specified in bytes, so to set the thread
stack size to 2MB for example, set the following in the environment
from which the Broker will be started:
MQSI_THREAD_STACK_SIZE=2000000
export MQSI_THREAD_STACK_SIZE
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IC30611 - STRESS PROBLEM WITH NEON DOMAIN MESSAGE PARSER
There is a known problem on all platforms (NT, AIX, Solaris, and
HP/UX) with the new Neon domain message parser and associated
new nodes. This issue is being investigated and IBM expects to
have a fix available as soon as possible after the GA of MQSI
V202.
When running multiple flows using the new Neon nodes with MQSI
202 on an SMP machine, the broker can exhibit a number of
problems, including termination with a segment violation (GPF),
if the product is put under stress. These problems do not occur
when using the old NeonRules and NeonFormatter nodes.
Please avoid stressing the product in this environment until
this APAR is resolved and a fix is made available. Further
information is available in the README file which is included in this
maintenance.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IC29727 - CREATE CONFIGMGR FAILS WHEN A USERID USED TO ACCESS
THE MRMDB CONTAINS A $ (DOLLAR) SIGN PREFIX
An attempt to run the 'mqsicreateconfigmgr' command, using as
a parameter a user id beginning with a $ (dollar) sign, causes
the command to fail with a BIP1801S error. This problem may
also occur when other non-alphanumeric characters are used.
Until this problem is fully investigated and resolved, it is
recommended that customers restrict characters of the MQSI
service user ids to the letters A to Z, a to z and numbers
0 to 9.
It is our belief that in most cases, user ids already conform
to this rule.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IC28810 - SUBSCRIPTIONS WON'T SHOW UP FOR A SINGLE USERID
The fix for this problem has removed the lowercaseing applied by the
Control Centre on the user identifier (userid) in Subscriptions View;
userid has become case sensitive.
In order to display subscriptions it is now necessary to respect the
case of the userid to get its subscriptions in the view.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IY13468 - DEFECT IN CLI IN REGARDS TO HOW WE DETERMINE THE CTX USED AT
THE ENVIRONMENT LEVEL.
Broker not stopping after an mqsistop command has been issued
An intermittent problem has been discovered on AIX and Sun Solaris
where the broker may not shutdown following the issuing of the
mqsistop command (without the -i option). This is only a problem
when using DB2 as a broker or customer database. If you encounter
such a symptom, then the broker should be able to be successfully
shutdown by re-issuing an mqsistop command, specifying the -i option.
This problem has been raised against DB2 as APAR IY13468.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IC30331 -CHECKIN GIVES ERROR BIP1205E ON MQSI V202 AT DB2 V7.1 FP2 LEVEL
MQSeries Integrator V2.0.2 is being shipped with DB2 7.1 ..
It is possible that customers may then apply DB2 fp2
There are known errors with FP2 where on check-in a BIP1205E
message is generated
This error is resolved at DB2 V7.1 FP3 level.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IY18146 - IF THE BROKERDB IS ORACLE, ADDITIONAL NLSPATH IS REQUIRED.
When the environment is set to a Japanese code page the broker
will not start. This is because Oracle cannot be accessed when
running in the Japanese code page.
When using an Oracle Database on UNIX, the following environment
variables must be set to ensure the broker starts cleanly:
LC_MESSAGES=en_US
LANG=en_US
Alternatively, en_GB also works.
This information will be added to the MQSeries Integrator
Installation Guide.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
NEW ERA OF NETWORKS INFORMATION
-------------------------------
The installation of the New Era of Networks (NEON) component may have
altered the permissions of the /usr and /usr/lpp directories to 777.
The new /usr/lpp/neonsoft directory that is used for the NEON component
and some of its subdirectories may also have been given the same 777
permission. If security is a concern review the permissions on these
directories and change as required. To restore the default permissions
on /usr and /usr/lpp use:
chmod 755 /usr
chmod 755 /usr/lpp
CSD03
-----
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
====================================================================
APAR # IY22041 - WHEN USING OLD NEW ERA OF NETWORKS NODES C++ RUNTIME
LIBRARIES FAIL TO LOAD, UNLESS DB2 IS INSTALLED.
CR # 258490
Description:
When using the New Era of Networks plugins (Parser, Transform, and
RulesEval) and using a broker repository other than DB2 on HP, the
plugins may fail to load.
Resolution:
Set the MQSI_PRELOAD variable to the following:
export MQSI_PRELOAD="/usr/lib/libCsup.2 /usr/lib/libstream.2 /usr/lib/libstd.2"
--------------------------------------------------------------------
APAR # IY28332 - CONVERSION PROBLEM - OUTPUT CCSID NOT WORKING
CR # 272154
Description:
On all UNIX platforms, messages with a CCSID of 437 are not being
processed correctly.
Resolution:
Preserve message CCSID settings.
====================================================================
Part 2: New Era of Networks Formatter
====================================================================
APAR # IY26986 - RECEIVED AN ERROR RUNNING NNFIE CAUSING AN OUPUT
OPERATION COLLECTION TO NOT BE LOADED.
CR # 267515
Description:
A collection item fails if it is non-existent. Processing should be
allowed to continue and add the operations defined in the export
although the actual collection has no associated operations
contained in the database.
Resolution:
A change was made in nnfmgrdb.cpp(::UpdateCollectionCntl) to correct
the problem.
--------------------------------------------------------------------
APAR # IC31419 - FORMATTER GUI CLOSING ABNORMALLY
CR # 256893
Description:
When closing an Oracle 8.1.7 database client, the application
crashed. This was caused by failing to free a client library resource.
Resolution:
The problem was fixed by properly disposing of the resource.
--------------------------------------------------------------------
APAR # IC31778 - NEONMESSAGELOG.NML BUILDING OUT OF CONTROL EVEN
THOUGH FLOW IS REFORMATTING MESSAGES CORRECTLY
CR # 258531
Description:
The NNSY log file, NNSYMessage.nml, fills with Informational as
well as Warning and Error messages from the NNSY Formatter and Rules
engines. Unless periodically truncated, this quickly consumes the
entire file system.
Resolution:
A new configuration parameter was added to the nnsyreg.dat file
which allows logging of Informational/Warning/Error messages to be
selectively disabled.
To add the new configuration parameter, type the following in the
nnsyreg.dat file:
Broker.Logging
LogLevel = 3
All message logging to the NNSYMessage.nml file is disabled.
To selectively enable message logging of various levels, set the
LogLevel value to one of the following:
0 = log messages of any severity (Error, Warning and
Informational)
1 = log error and warning messages
2 = log only error messages
3 = disable all logging
--------------------------------------------------------------------
APAR # IC31885 - NEW ERA GUI ERROR ORA-00942 ON DELETE A FIELD
CR # 261359
Description:
When removing fields from an Input Format in the New Era of Networks
Formatter GUI, an error message appears.
Resolution:
The SQL statement that incorrectly referenced dbo ownership was
removed.
--------------------------------------------------------------------
CR # 251778
Description:
When all components are exported in the New Era of Networks Formatter
GUI, the comments not saved.
Resolution:
The code to create the comments is now executing.
--------------------------------------------------------------------
CR # 255370
Description:
When selecting the Used In tab from Output Control properties
window, the New Era of Networks Formatter GUI crashes.
Resolution:
Permissions code in Used In tab was fixed. Permissions now check
correctly.
--------------------------------------------------------------------
CR # 259989
Description:
In the Tag Search area, the Data Field output control does not
accept a valid input tag because the Tag value is prematurely
verified.
Resolution:
Verification was set to occur just prior to saving.
--------------------------------------------------------------------
CR # 263294
Description:
If you select another tab before clicking Apply, field comments are
lost.
Work-around:
If you change the focus from Comments tab, the comments are saved.
--------------------------------------------------------------------
CR # 265983
Description:
During a String to Decimal conversion, the leading whitespace
causes a loss of the negative sign.
Resolution:
A fix was made so that the leading whitespace no longer causes the
loss of the negative sign during a String to Decimal conversion.
--------------------------------------------------------------------
CR # 267680
Description:
When attempting to remove a field from a format the following
message appears:
Database error code: -204
Database Error Text SQLSTATE = S0002
[IBM][CLIDriver][DB2/NT] SQL0204N "DBO.NNF_FMT" is an
undefined name.
Resolution:
The reference to DBO was removed from inline SQL script.
--------------------------------------------------------------------
CR # 268424
Description:
In the New Era of Networks Formatter GUI, the Field Mapping window
can be seen from the New Map - Edit map entries, but nothing can be
mapped.
Resolution:
Mapping security was not being set for the object. A security call
has been added for the object.
--------------------------------------------------------------------
CR # 268531
Description:
A Map Permission Error occurs in the New Era of Networks Formatter
GUI.
Resolution:
An incorrect object was being passed to the API. The parameter was
adjusted to correct the problem.
--------------------------------------------------------------------
CR # 268921
Description:
When editing map entries, an error message shows because of an
incorrect SQL statement.
Resolution:
The SQL statement was corrected.
--------------------------------------------------------------------
CR # 269075
Description:
In the New Era of Networks Formatter GUI, the Delete, Add Field
Components, and Apply Input Control choices are greyed out in the
popup menu for Input Formats.
Resolution:
The GUI was adjusted to give the appropriate permissions to use
these options.
--------------------------------------------------------------------
CR # 269718
Description:
NNFie is failing to import a substring control that performed a
substring operation to the end of the field with a literal pad
character literal definition other than NONE.
Resolution:
The check was removed when "start position to end of field" is
defined, and processing continues when a valid literal is defined
as the pad character other than "NONE."
--------------------------------------------------------------------
APAR # IC33330 - SECURITY TAB IN NNSY FORMATTER GUI IS GRAYED OUT
FOR NEWLY CREATED FORMATS.
CR # 272891
Description:
When removing a format from a collection, the format security
becomes invalid.
Resolution:
Security is no longer affected when removing a format from a
collection.
--------------------------------------------------------------------
CR # 274229
Description:
When importing using the New Era of Networks Formatter GUI,
conflicts are not always reported.
Resolution:
Code was inserted into the file to provide the required cleanup
before importing.
====================================================================
Part 3: New Era of Networks Rules
====================================================================
APAR # IY28136 - PART OF DBCS CHARACTERS CHANGED TO DIFFERENT CHARACTERS
WHEN THEY GOT THROUGH NEON TRANSFORM NODE.
CR # 268316, 270056
PMR # 3828, 33331
Description:
When using the NEON Nodes, multi-byte character code set messages
are not being converted correctly.
Resolution:
MIF 2.0 was changed to handle the character code set ID for message
data.
--------------------------------------------------------------------
APAR # IY28181 - NEONRULES AND NEONFORMATTER WERE NOT ABLE TO BE IMPORTED.
CR # 267552
Description:
The Rules Expression parser does not accept parentheses in field
names, and many S.W.I.F.T. format fields have parentheses.
Solution:
The parser was changed to validate field functions without placing
restrictions on field names that may contain parentheses.
--------------------------------------------------------------------
CR # 257809
Description:
Exporting to a file where the path contains spaces causes the export
process to fail.
Resolution:
Quotation marks were placed around the code path to solve problem.
--------------------------------------------------------------------
CR # 259180
Description:
When repeats are controlled through Access Mode Access Next, rather
than Relative Index or Controlling Field, repeating terminates
earlier than desired.
Resolution:
An adjustment was made to the engine to now examine the currently
mapped field's Access Mode, check for Access Next, and to continue
processing until the current field has no data. Output format
repeats should be controlled through Relative Index or Controlling
Field.
====================================================================
Part 4: Documentation Issues
====================================================================
APAR # IY23879 - MQSIV2.02 WITH MATH EXPRESSION / DECIMAL U.S. THE
BEHAVIOR OF FORMATTER IS DIFFERENT FROM MQSIV1.1.
CR # 259601, 259599 System Management Guide
Description:
In the Formats and Rules Database Migration chapter, a section
titled "Upgrading Output Controls Using Math Express and Data Types
Other than U.S. Decimal" contains some incorrect information.
Resolution:
The heading should read "Upgrading Output Controls Using Math
Expressions" and the sentence which occurs in the subsequent
paragraph that reads "This occurs if the final data is anything
other than Decimal U.S." should be removed.
--------------------------------------------------------------------
CR #266133 New Era of Networks Formatter Programming Reference
Description:
In chapter 6, the General New Era of Networks Formatter Errors table
fails to define error messages beyond 1083.
Resolution:
The following information defines Formatter errors 1084-1088:
1084 Format name exceeds 120 byte maximum.
Check for valid length of format name.
1085 User-defined data type error ().
Check the user-defined data type. It failed the user-defined
validation routine. The values of and
are supplied by the routine.
1086 User exit returned an undefined data type. Check the data
type of the user exit. It should be an integer, "double,"
or an array of characters.
1087 Sub-control error: Behavior failed on output field
, . Check each output control in the
output operation collection. At least one output control
in the collection failed when the operation was applied to
the indicated output field using the data from the indicated
input field.
1088 Sub-controls (in reverse order) Check the order of each
sub-control and the components of the operation definitions
and converted input field data type.
====================================================================
CSD02
-----
Contents
1. New Era of Networks Formatter
2. New Era of Networks Rules
3. Visual Tester
4. Documentation
5. General Issues
Each section is sequenced in the following order: by case number
and then followed by defect/CR number and APAR number, and then
by defect/CR number or APAR number alone.
====================================================================
Part 1: New Era of Networks Formatter
====================================================================
Case #7135 - Empty Formats
Defect #7154
Description:
When creating two formats in which one is an empty format and
another contains at least one field, or when both formats contain
at least one field, the following error message appears:
Error text = invalid data window row/column specified.
Resolution:
The code was adjusted to correct the problem.
--------------------------------------------------------------------
Cases #10855, 11582, 12633 -Prefix/Suffix Output Operations
Defect #8204
Description:
Output Operations, Prefix or Suffix, fail to import when defined
with a value of NONE.
Resolution:
An adjustment has been made so that the value of NONE is
substituted for the prefix/suffix value.
--------------------------------------------------------------------
Case #12780 - S.W.I.F.T. and Other Large Formats
Defects #9582, 10040
Description:
In the New Era of Networks Formatter GUI, when using large formats,
such as SWIFT, if you double-click Formats in the tree view to
expand the entire format list, it takes a very long time for the
list to display.
Resolution:
The security checks location was adjusted to correct the problem.
--------------------------------------------------------------------
Case #13663 - Overwrite Parameter [-o] and Single Transaction
Parameter [-T]
Defect #8311
Description:
When running NNFie as one transaction, the overwrite parameter [-o]
does not overwrite the data when importing. Instead, an Import
Failed error message appears.
Problem Resolution:
The problem was resolved, but to overwrite the data, you must enter
parameter [-T] before [-o] on the command line.
--------------------------------------------------------------------
Case #13836 - Import Problems with Invalid Output Controls
Defect #9438
Description:
In the New Era of Networks Formatter GUI, it is possible to create
invalid output controls that NNFie can export but cannot import.
Resolution:
An error message now alerts the user to any invalid output controls
that are created in the New Era of Networks Formatter GUI.
--------------------------------------------------------------------
Case #15121 - Permutil Problems on New Era of Networks Formatter
Defect #10074
Description:
PermUtil did not work for listing ownership of the New Era of
Networks Formatter components.
Resolution:
Additional database queries were added to retrieve the New Era of
Networks Formatter component names.
--------------------------------------------------------------------
Case #17772 - Format Remover Failure with Compound Formats
Defect #11022
Description:
The Format Remover fails to remove a format in a compound format
that contains other compound formats. It attempts to remove the
same format twice, resulting in a failure at the second attempt.
Resolution:
The Format Remover now continues processing once a format has been
removed and does not exit with an error.
--------------------------------------------------------------------
Case #18209 - Overwrite Failure with Compound Formats
Defect #11179
Description:
When overwriting a compound format with no component formats using
NNFie, the overwrite fails. This occurs when the optional
parameter [-o] is on or if the Interactive Overwrite is chosen.
Resolution:
An adjustment has been made to overwrite empty compound formats.
---------------------------------------------------------------------
Defect #6438 - Retrieval Error with Compound Formats
Description:
When you save compound formats as opposites, the following
retrieval error is generated:
ds_retrieval_error/Retrieval Error...
Message
Retrieval Error
Unable to retrieve rows from the database into a datastore
Resolution:
Saving a compound format as opposite now works correctly; no error
is generated.
---------------------------------------------------------------------
Defects #8421, 10443 - Oracle 8.1.6 Client Software
APAR # IC31418 - Formatter GUI not working with Oracle greater than 8.1.6
Description:
When creating an Oracle session driver from an existing connection,
the New Era of Networks Formatter GUI does not work with the
Oracle 8.1.6 Client software.
Resolution:
A change was made to allow New Era of Networks Formatter GUI to
work with the Oracle 8.1.6 or 8.1.7 Client software.
--------------------------------------------------------------------
CR #254254 - Removing Literals
Description:
Literals cannot be removed when associated with an input control
type of literal.
Resolution:
A check was included for Literal input control types. The check
marks a literal for deletion when the literal name is defined in
the input control.
--------------------------------------------------------------------
CR #254396 - Import Error with the New Era of Networks Formatter GUI
Defect #11175
Description:
When trying to import using the New Era of Networks Formatter GUI,
a message saying "Unable to open NNFIE.inv" or "Unable to open
NNFIE.err" occurs. This happens because the GUI is trying to
read the NNFIE.inv file before the write is completed.
Resolution:
The code was changed to read the correct directory and .inv file
and a second pause was put in to ensure that the file write is
completed and the file closed by the operating system prior to
the read happening.
--------------------------------------------------------------------
CR# 255142 - Literals Not Alphabetizing in New Era of Networks
Formatter Treeview
Defect #11235
APAR # IC31862 - LITERALS AND OUTPUT CONTROLS DON T ALPHABETIZE
UPON REFRESH
Description:
In the New Era of Networks Formatter GUI, new literals do not
alphabetize when you refresh.
Resolution:
A correction was made so that literals do alphabetize now.
--------------------------------------------------------------------
CR #255144 - Delete Function Disabled in New Era of Networks
Formatter GUI
Description:
In the New Era of Networks Formatter GUI, if you right-click on
a format in the context menu to display the shortcut menu and have
permissions to delete the format, the Delete function remains
disabled.
Resolution:
A correction was made so that the Delete function is enabled when
you have permissions to delete a format.
--------------------------------------------------------------------
CR #255144 - Delete Function Disabled in New Era of Networks
Formatter GUI
Description:
In the New Era of Networks Formatter GUI, if you right-click on
a format in the context menu to display the shortcut menu and have
permissions to delete the format, the Delete function remains
disabled.
Resolution:
A correction was made so that the Delete function is enabled when
you have permissions to delete a format.
--------------------------------------------------------------------
CR # 255463 - Compound Output Formats Not Reformatting Properly
Description:
Compound output formats with repeating fields are not reformatting
message data properly. The first record gets reformatted, but
instead of reformatting the second record, New Era of Networks
Formatter simply repeats the first record.
Resolution:
When defining Data Field Tag Search output controls, New Era of
Networks Formatter searches for the first field in the input
message with the specified tag value. This type searches the input
data for the first occurrence of the specified tag and gets the
first instance of it, generating the correct number of repeats,
but always getting the first repeat’s data.
To avoid this problem, use the following work-around.
1. Define the output control type for your compound output format
as Data Field Name Search.
2. Add a prefix to the tag you were looking for.
--------------------------------------------------------------------
CR #256022, 256570 - Migration Problem on AIX/Oracle
APAR # IY22611 - FAILURE TO COMPLETELY IMPORT FORMATS AND RULES INTO AN ORACLE
Description:
1) When migrating formats from MQSI 1.1 AIX/Oracle 8.0.5 to
MQSI 2.02/AIX/Oracle 8.1.7, several components are missing
after migration and no errors are reported.
2) The nml file is reporting the following error:
First detection of out-of-memory condition. Freed memory
reserve and setting shutdown-flats to true.
Resolution:
1) Because the allocated tablespace was insufficient, inst_db was
changed to increase the tablespace size.
2) Memory leaks were found and resolved.
--------------------------------------------------------------------
CR #256089 - Optional Formats Fail
Description:
A reformat defect was causing optional formats to fail, miss
repeats, and become out of order.
Resolution:
A code adjustment was made to correct the problem.
--------------------------------------------------------------------
Case #10769881 - Apitest Problem on Solaris
Defect #256537
APAR # IY24470 - APITEST CORE DUMPS FOR SOME FORMATS HOWEVER DOES
APPEAR TO WORK
Description:
On Solaris, the New Era of Networks Formatter 5.2 apitest core
dumps when attempting to display the contents of empty data fields.
Resolution:
NULL pointer errors were fixed to correct the problem.
--------------------------------------------------------------------
CR #256893 - New Era of Networks Closes Abnormally on Oracle 8.1.7
APAR # IC31419 - FORMATTER GUI CLOSING ABNORMALLY
Description:
With the Oracle 8.1.7 client libraries, the New Era of Networks
Formatter GUI may close abnormally, and the following error message
appears at shutdown:
DDE Server Window: nnfmt.exe - Application error
The instruction at "0x77f83a33" referenced memory at "0x00000010".
The memory could not be read.
Work-around:
Click OK to close the error message.
--------------------------------------------------------------------
CR #258003 - NNFie Not Importing Literal Values
Description:
NNFie not importing literal values where the first value of the
literal contains a value of zero (0). This became an issue in the
this version because literal definitions were expanded to meet the
requirements for internationalization.
Resolution:
The check for the first value of zero was removed.
====================================================================
Part 2: New Era of Networks Rules
====================================================================
Defect #9128 - BooleanOperator Object Can Crash in Rules
Description:
When Rules loads the data for evaluation, it creates a
BooleanOperator object that can crash under certain circumstances.
Resolution:
Memory allocation problems were resolved.
---------------------------------------------------------------------
Defect #9284 - Cannot Exit on PermUtil
Description:
PermUtil does not allow you to exit after you have performed one
function.
Resolution:
An Exit option was added to the submenu in the Application Group
Selection menu allowing you to return to the Application Group
Selection menu or exit the application.
--------------------------------------------------------------------
Defect #9493 - Application Group Default Name
Description:
When the user creates a new Application Group, the name of the
Application Group defaults to NewApplication<#>. To rename the
Application Group, the user must either right-click
NewApplication<#> to access Rename from the shortcut menu or click
NewApplication<#>.
Resolution:
The user is now put in Edit mode after a new Application Group is
created, eliminating the rename step.
--------------------------------------------------------------------
Defect # 9574 - MQS Expiry Argument Not Working Properly
Description:
The MQS Expiry argument no longer has a pull-down menu associated
with it and will not allow you to enter a numeric value. When
attempted, the error message #2697 appears:
Invalid option value '100' for putqueue MQS_EXPIRY option"
The only entries that are allowed are "PROPAGATE" and
"NO_PROPAGATE".
Resolution:
A New Era of Networks Rules Management API has been adjusted. The
GUI now allows you to enter numeric values, and the values are
correctly represented in the message header.
--------------------------------------------------------------------
Defect #9668 - New Era of Networks Rules Requires an Expression
Before Exiting
Description:
The GUI does a validation check to make sure the user entered an
expression. There might be times where a user does not have the
expression determined yet and the user is not allowed to exit
the rule without entering something.
Resolution:
The validation was removed allowing the user to come back to a
rule and enter an expression at a later time.
--------------------------------------------------------------------
Defect #9833 - Read Permissions Appear Missing in View
Description:
When new users are added to a component and given Read and Update
permissions, the Read permission is not there when you go back
into the component's Permission tab.
Resolution:
The setting and viewing of the Read permission has been fixed.
--------------------------------------------------------------------
Defect #9905 - Error Messages Not Pulled from Correct Files
Description:
Some error messages were not being pulled from the correct
language file.
Resolution:
Some of the error messages were always looking in the English
directory. This was fixed so the correct locale's messages are
used.
--------------------------------------------------------------------
Defects #9907, #10419 - Import Problem in New Era of Networks
Rules GUI
Description:
The GUI does not report problems encountered when importing using
the GUI.
Resolution:
The GUI was modified to recognize the return code from NNRie and
report the problem.
--------------------------------------------------------------------
Defect #10504 - Importing Problem in New Era of Networks Rules GUI
Description:
Importing using the New Era of Networks Rules GUI causes
intermittent database deadlocks.
Resolution:
Added transaction boundary after login that eliminates NNRie
locking.
--------------------------------------------------------------------
Defect # 10699 - Setting Expiry Fields Generates An Error
Description:
Setting the expiry field in a rules evaluation node causes an error.
Resolution:
To correct the problem, the following changes have been implemented:
MQS_EXPIRY = - Propagate any value set in the original
message.
MQS_EXPIRY = -1 - Disable MQS_EXPIRY
MQS_EXPIRY = - Set MQS_EXPIRY to the number
of milliseconds specified
MQS_EXPIRY = PROPAGATE - Propagate any value set in the original
message.
MQS_EXPIRY = NO_PROPAGATE - Disable MQS_EXPIRY
--------------------------------------------------------------------
Defect #10717 - Problem with Sub Expression Tab
Description:
When using the Sub Expression tab to build an expression if you
use the F2FSTRING operator, the expression builder adds the space
character that separates the left field name and the operator as
part of the field name. This creates an invalid expression.
Resolution:
The expression builder now puts the space in the correct place.
--------------------------------------------------------------------
Defect # 10883 - Incorrect Error Messages on Subscriptions
Description:
An error message appears stating that a rule is missing a
subscription when the message being processed successfully
reformats and routes.
Resolution:
These errors occur when a message goes through a Rules Eval Node
and does not hit any rule. The message is then routed to the NoHit
queue and sends the following error message as designed:
Rules subscription list missing or empty.
--------------------------------------------------------------------
Defect #11195 - Message Type Cannot Be Set to Inbound Format
Description:
In the Rules GUI, the message type cannot be set to inbound format
for processed messages.
Resolution:
The format types available from the putqueue message type only
listed output formats. The list now contains input formats.
--------------------------------------------------------------------
CR #257951 - Memory Allocation Failure in NNDOData.cpp
Defect #257951
APAR # IC31306 - USING THE NEW ERA OF NETWORK NODES AND GETTING A
MEMORY ALLOCATION ERROR.
Description:
The neonmsg parser fails to parse certain messages and generates
an error.
Resolution:
A fix was made to the NDO fixing the problem.
====================================================================
Part 3: Visual Tester
====================================================================
Defect #10920 - Message Data Encoding Differs from Default Encoding
Description:
A user loads messages onto an MQSeries transport using MQSeries
Explorer or some alternative method (the user does not use Visual
Tester to load the transport). The messages are typed or pasted in
and assumed to be in the native encoding of the machine. When the
message is read from the transport using Visual Tester and the
user attempts to change the Data Source to "Screen" to edit the
message data, a message appears stating that the message data
encoding differs from the default system encoding; editing the
data is not allowed. The user assumes the encodings should be
the default of the machine.
Workaround 1:
If the user has set up MQSeries with the default configuration,
MQSeries may use a different default encoding than our software
uses. In this case, when messages are loaded with MQSeries
Explorer, the encoding seen when Visual Tester reads from the
transport appears to differ from that used as default by Visual
Tester. The solution is to configure MQ Series to use the proper
encoding rather than its default.
Workaround 2:
If MQSeries is loaded by a method that allows you to set the RFH,
specify the encoding of the message in the RFH.
Workaround 3:
After reading the message from a transport, you can copy the
message data from the Input Message control, switch the input
message to screen, dismiss the informational message, press reset,
then paste the message data back into the Input Message area. The
data can now be edited.
--------------------------------------------------------------------
CR #255381 - Visual Tester GUI Problem
Description:
When attempting to parse a message, the Visual Tester GUI crashes.
Resolution:
The Visual Tester GUI now works correctly.
====================================================================
Part 4: Documentation
====================================================================
Case #11368 - User's Guide
Defect #8439
Description:
Additional information needs to be included in the New Era of
Networks Formatter Chapter regarding the Jump to Rules
functionality.
Resolution:
To view the Jump to Rules errors when running the consistency
checker, type the following syntax into any SQL Query window:
Select m.MSG_NAME 'Message Type', s.SUBN_NAME 'Subscription Name',
a.OPT_VAL 'Bad control name' from
NNR_MSG_MSTR m, NNR_SUBN_LIST s, NNR_SUBN_ACT a WHERE
m.MSG_ID = a.MSG_ID AND
a.MSG_ID = s.MSG_ID AND
s.SUBN_ID = a.SUBN_ID AND
a.APP_ID = s.APP_ID AND
a.OPT_NAME = "FORMAT_CONTROL" AND
a.OPT_VAL not in
( select CNTL_NAME from NNF_OUT_MSTR )
order by f.MSG_NAME
--------------------------------------------------------------------
Case #11982 - Open Transport MQSeries Driver Configuration Guide
Defect #8645
Description:
In the Open Transport MQSeries Driver Configuration Guide, the
NNOT_FACTORY_FUNCTION parameter is incorrectly defined.
Resolution:
The correct definition of the parameter is:
NNOT_FACTORY_FUNCTION = NNMQSSessionFactory.
--------------------------------------------------------------------
Defect #5987 - User's Guide
Description:
It is no longer necessary to quote field names that contain
non-alpha characters. The only time that you need to quote a
field name is when the name contains one of the four basic
arithmetic signs (+, -, *, /).
Resolution:
The following changes were made the New Era of Networks Formatter
chapter of the user guide:
1. The note regarding the use of quotations marks now reads:
Note:
You must enclose field names in single or double quotes when
the field name contains one of the following arithmetic signs:
(+, --, *, /)
For example, ’inField1 + $MAPPED_INFIELD’ or
inField1 + $MAPPED_INFIELD are valid math expressions.
2. All quotation marks have been removed from the example text,
except those using one of the four arithmetic expressions.
--------------------------------------------------------------------
Defect #8494 - User's Guide
Description:
In Visual Tester chapter of the User Guide, it does not state that
the Load tab is not enabled unless transport parameters are defined.
Resolution:
The Visual Tester chapter of the User Guide now contains the
following note:
To enable the Load function, you must have defined the transport
parameters in the configuration mechanism. For more information,
refer to the Open Transport Configuration and User Guide
for your transport driver.
--------------------------------------------------------------------
Defect #10763 - User's Guide and New Era of Networks Formatter
Programmers Reference
Description:
In both the User Guide and New Era of Networks Formatter Programmers
Reference, the documentation needs additional information regarding
how to define a math expression.
Resolution:
The following information must be added to the User Guide, To define
a math expression operation (procedure), and the New Era of Networks
Formatter Programming Reference , NNNFMgrMathExpCntlInfo API
parameter table:
The maximum value for decimal precision in a math expression is 11.
--------------------------------------------------------------------
Defect #253061 - Installation Guide
Description:
When importing rules, NNRie makes dbo the owner of the rules,
leaving the user with read-only permission. Additional
information is needed in the documentation to avoid this
occurrence.
Resolution:
The following note was added to the Verifying the Environment
section in the e-Biz 3.2.2 install guide for Microsoft SQL
Server and Sybase:
NOTE:
New Era of Networks components do not work properly when using
aliased database owner accounts. To ensure the proper functioning
of all component applications, you must run them as a database user
in the NEONGRP database group/role. However, the inst_db
installation process is an exception to this rule, using an aliased
database owner account to refresh the New Era of Networks databases.
The owner account used for refreshing is created when inst_db
creates the database.
--------------------------------------------------------------------
CR # 253713 - New Era of Networks Formatter Programming Reference
Description:
The following error code descriptions are needed in the New Era of
Networks Formatter Programming Reference:
1085, 1086, 1087, and 1088.
Resolution:
Descriptions for the error codes are now in the New Era of Networks
Formatter Programming Reference.
--------------------------------------------------------------------
CR # 254838 - System Management Guide
Description:
Information regarding the NNFie.err file need to be added to the
System Management Guide.
Resolution:
The following note was added to the migration chapter of the
System Management Guide:
Note:
For e-Biz 3.2.2, delete the NNFie.err and NNFie.log files before
running NNFie. Failure to follow this procedure results in an error
message in the NNFie.log that states that NNFie.err already exists.
--------------------------------------------------------------------
Case# 10748911
CR #255445 - User's Guide
APAR # IY22705 - THE DOCUMENTATION IS NOT CLEAR ON VALID OUTPUT
CONTROLS WHERE THE TYPE IS INPUT FIELD VALUE =.
Description:
The User's Guide does not instruct users that NONE cannot be used
as the field value for an Output Control type.
Resolution:
The User's Guide now contains a statement that although the default
of NONE appears as the field value for an Output Control type, an
actual value must be used.
--------------------------------------------------------------------
CR # 258078 - System Management Guide
Description:
If you bring up Visual Tester and the Load tab is disabled, it is
because there is no transport information in the configuration,
or the configuration information cannot be found. In order to
enable transports, transport session information must be entered
in the neonreg.dat file.
These procedures need to be added to the System Management Guide.
Resolution:
The following information was added to Chapter 3, Component
Configuration:
Specifying Transport Session Information
On z/OS, you must specify transport session information in the
neonreg.dat file to enable the Visual Tester Load feature. After
completing this procedure, the Load tab is enabled in the Visual
Tester GUI.
To specify transport session information:
1. Locate the neonreg.dat file.
For more information, see Locating the Example Folder on
page 20.
2. Create an entry for MQSeries Session parameters.
Example:
Session.MQSeriesSession
NNOT_SHARED_LIBRARY=dbt22mqs
NNOT_FACTORY_FUNCTION=NNMQSSessionFactory
NNMQS_SES_OPEN_QMGR=
3. To set default parameters for MQSeries queuing, specify the
following using the model in step 2:
a. Set NNOT_SHARED_LIBRARY to dbt22mqs.
b. Set NNOT_FACTORY_FUNCTION to NNMQSSessionFactory.
c. Set NNMQS_SES_OPEN_QMGR to your queue manager.
4. Create an entry for Transport parameters.
Example:
Transport.
NNOT_FACTORY_FUNCTION=NNMQSQueueFactory
NNOT_SHARED_LIBRARY=dbt22mqs
NNOT_TIL_OPEN_TSI=
NNOT_TIL_OPEN_SESSION_ID=MQSeriesSession
5. To set default parameters for your inbound queue, specify
the following:
a. Set NNOT_FACTORY_FUNCTION to NNMQSQueueFactory.
b. Set NNOT_SHARED_LIBRARY to dbt22mqs.
c. Set the NNOT_TIL_OPEN_TSI to your inbound queue name.
d. Set NNOT_TIL_OPEN_SESSION_ID to MQSeriesSession.
e. To test the Load function in Visual Tester, open the
Visual Tester GUI.
For more information, see the MQSeries Integrator User's Guide.
--------------------------------------------------------------------
Installation Guide
The installation guide incorrectly states that e-Biz Integrator
3.2.2 supports the Windows 98 platform. It does not support
Windows 98.
====================================================================
Part 5: General Issues
====================================================================
Defect # 9191 - Extraneous Error Messages Are Being Generated
Description:
Extraneous error messages are being generated by the New Era of
Networks nodes when they are unable to propagate a message to the
failure terminal.
Resolution:
These error messages have been removed.
---------------------------------------------------------------------
Defect # 10560 - DFE Core Dumps When Creating the First Execution
Group
Description:
During stress testing, the DFE core dumps when it creates the first
execution group. If all three New Era of Networks lils are removed
from the lil directory, the problem is non-existent.
Resolution:
Changes were made to the msg catalogs to correct user messages.
---------------------------------------------------------------------
Defect # 10616
Description:
The WebDav driver that allows the MQSI Control Center tooling to
see New Era of Networks Formatter definitions adds an _m_id suffix
to all message ( format name ) identification names.
Resolution:
The code was adjusted and the suffix is no longer visible in the
tooling.
---------------------------------------------------------------------
Defect # 10639 - Error Occurs When Modifying Message in Two Compute
Nodes
Description:
When you modify the New Era of Networks message in two compute
nodes in a row with the final compute node setting the message
type to an output format, the following error message is written
out to the event log:
Event ID: 120
(STRESS1.default) Input message type was not specified for output
transformation.
The NEONMSG Parser may require a New Era of Networks input format
name to correctly transform a message from its internal
representation to a bit stream. The transformation will fail only
if a "Message Eval" operation is encountered during the
transformation.
Resolution:
A correction was made so that now the current state of the message
post compute node is acceptable to the input of subsequent compute
nodes without regard for the message name.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SERVICE AND TECHNICAL SUPPORT
-----------------------------
This is the third release of product 5639F6100, IBM MQSeries
Integrator Version 2 for Windows NT. The following APARs have been
incorporated into it.
Name Abstract
IC26734 - SQL ERRORS OCCUR WHEN WORKING WITH DATABASEUPDATE NODE
IC26799 - BIP2293 WHEN DEPLOYING A MESSAGE USING PLUG-IN PARSER
IC26880 - FAILURE TO START/STOP ALL MESSAGE FLOWS FOR AN EXECUTION GRP
IC26952 - CREATION OF RESPONSE MSG FAILS DUE TO NULL NAMEVALUECCSID
IC27033 - TRACE DOES NOT SHOW CORRECT DATA - XML STATEMENT WITH A NULL
IC27038 - ADD MAPPING IN AN OUTPUT MESSAGE COMPUTE NODE IS NOT POSSIBLE
IC27068 - REGISTER A SUBSCRIPTION GIVES THE EVENT ERROR 7053 -UNEXPECTED
IC27301 - SETTING MQMD.EXPIRY FIELD TO AN ABSOLUTE VALUE IN COMPUTE NODE
IC27806 - DATA FLOW ENGINE WILL NOT RECOVER FROM ERRORS DURING DELETION
IC27959 - DELETING A DATABASE REFERENCE FROM A COMPUTE NODE DOES NOT STO
IC28174 - COMPOUND NODE OF A FLOW CONTAINING LABELS CANNOT BE INCLUDED
IC28312 - FLOAT DATA TYPES OF LENGTH 8 ARE NOT HANDLED CORRECTLY WHEN SE
IC28324 - COBOL COPYBOOK IMPORT PROBLEM, MESSAGE BIP1812S RECEIVED.
IC28401 - BIP2211E ERROR OCCURRED BY USING BYUSERID IN ORDER MODE OF INP
IC28443 - BIP1812S RECEIVED USING THE CONTROL CENTER GENERATE FUNCTION I
IC28446 - INSTALL GUIDE DOES NOT DISCUSS ABOUT MQSI_PARAMETERS_FILE VARI
IC28447 - INSTALL GUIDE PAGE 129/130 HAVE INCORRECT NAMES FOR NT CONSIST
IC28518 - 1. CREATING A BITSTREAM THAT CONTAINS A REPEATING SEGMENT OF
IC28520 - LOOP ON COMPUTE NODE - REPEATING ELEMENT USES A REPEAT COUNT
IC28605 - MESSAGE FLOW LOOP WITH MSGBIP2608I MSGBIP2623I AND MSGBIP2611I
IC28724 - IMPORT OF COBOL COPY BOOK THAT DOES NOT HAVE A COMPLETELY ASCE
IC28810 - SUBSCRIPTIONS WON T SHOW UP FOR A SINGLE USERID
IC28926 - SIGNED PACKED DECIMALS WILL ACCEPT F AS WELL AS C AND D
IC29022 - BIP1812E CAUSED DURING A DEPLOY IN STRUCTURES WITH MANY EBMEDD
IC29033 - MQSI V201 USING DUPLICATE FLOW FEATURE TO CREATE MESSAGE FLOW
IC29184 - XML-PARSE ENVIRONMENT INCORRECT
IC29200 - XML MESSAGE GETTING TRUNCATED AFTER PROCESSING THROUGH COMPUTE
IC29210 - MQSIMRMCOPYMSGSET CHANGES TWO ATTRIBUTES OF THE COPY IT MAKES
IC29489 - DBCS MESSAGES WERE NOT CONVERT CORRECTLY FROM PC CODEPAGE TO H
IC29632 - MQSI - INCORRECT STRUCLENGTH AND NAMEVALUELENGTH IN RFH2 LOOP
IC29775 - MQSI BROKER DO NOT PASS THE MQMD CONTEXT INFORMATION WHEN A
IC29801 - MQSI V2 FAILS TO RECONNECT AFTER ORACLE HAS BEEN BOUNCED
IC30173 - MQINPUT CATCH TERMINAL DOES NOT COMMIT DATABASE LOCKS.
IC30195 - EG ABEND WHEN USING TWO MESSAGES OF THE SAME STRUCTURE WITHIN
IC30424 - AFTER APPLIED CSD2, THE MESSAGE BROKER INTERNAL PROBLEM ERROR O
IC30497 - ERRORS OCCURRING DURING MQSI GUI CONNECTION TO ORACLE 8.1.6 NE
IY12651 - DATA FLOW ENGINE WILL NOT RECOVER FROM ERRORS DURING DELETION
IY13621 - MQSI MRM MESSAGE IS CAUSING THE BROKER TO SPIN
IY14540 - AIX BROKER CONFIGURATION LIBPATH MODIFICATION MISSING IN DOCUM
IY14660 - MEMORY CORRUPTION ON AIX USING DB2 VIA TCP/IP WITH NIS ENABLED
IY14720 - MSGBIP2301E WHEN A BROKER TRIES TO LOAD THE MQSI SAMPLE PLUGIN
IY14970 - DOCUMENTATION INCORRECT/NEEDS CHANGE ON COMPILERS SUPPORTED BY
IY15310 - MEMORY LEAK AND THROUGHPUT DEGREDATION
IY16379 - EXECUTION GROUP TERMINATES ON STARTUP WITH BIP2123
IY16620 - MQSI CORE DUMP CAUSED BY ADDRESS ALIGHNMENT ISSUE WHEN BINDING
IY16679 - INADEQUATE ERROR MESSAGE PRODUCED FOR EXECUTION GROUP FAILURE
IY16970 - DFE STOPS PROCESSING MESSAGES FOR A FLOW. INCOMING MESSAGES BA
IY17486 - COBOL STRUCTURES, CONTAINING SIGNED DECIMAL NUMBERS (PIC S9),
IY17772 - AFTER UPGRADE MQSI VERSION F/V1.1 T/V2.0.1, MQSI BROKER HANG
IY17780 - DFE NOT STARTING PROCESSING OF MESSAGES ON THE INPUT QUEUES
IY17808 - XML PARSER ADD TRUE TO THE END OF XML DECLARATION.
IY18104 - CAST FUNCTION INTERMITTENTLY FAILING
IY18245 - PERFORMANCE FIX TO ADDRESS INEFFICENCY IN BIT STREAM FOR
IY19382 - DATAFLOWENGINE LOOP
The MQSeries support page is located at:
http://www.ibm.com/software/ts/mqseries/support
from which you can obtain the latest information about various
MQSeries topics including :-
- Hints and Tips
- APARs and Fix Packages
- FAQs
- Support downloads
- Newsgroups
For the latest versions of MQSI V2.0.2 documentation see the
following Web page on the MQSeries Web site:
http://www.ibm.com/software/ts/mqseries/library/manualsa/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
CSD HISTORY
===========
CSD03 (PTF U200172)
___________________
This is the third PTF for IBM MQSeries Integrator Version 2.0.2 for
Windows NT. It is delivered via PTF U200172 for APAR IC33018.
It contains fixes for ALL the problems listed below:
Name - Abstract
IC33018 - CUMULATIVE MAINT #03 FOR MQSERIES INTEGRATOR FOR WINDOWS NT V202
IC28837 - RENAME A DEPLOYED FLOW, DEPLOY EXEC GROUP SHOWS NEW FLOW NAME I
IC30505 - ERROR HANDLING IN EXECUTION GROUP, CAUSES THE EXECUTION GROUP
IC31160 - FAILURE OF SELECTS ON MULTIPLE OBJECTS
IC31219 - MQSI STACK OVERFLOW BY MESSAGE FLOW THAT LOOPS
IC31345 - COBOL IMPORT PROBLEM WHEN LEVEL NUMBERS FIELDS NOT ASCENDING
IC31419 - FORMATTER GUI CLOSING ABNORMALLY
IC31766 - MQSIREPORTTRACE DOES NOT WORK CORRECTLY WITH USERNAMESERVER COM
IC31778 - NEONMESSAGELOG.NML BUILDING OUT OF CONTROL EVEN THOUGH FLOW IS
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
IC31885 - NEW ERA GUI ERROR ORA-00942 ON DELETE A FIELD
IC32018 - WHEN A REFORMAT OPEARTION IN A NEON-MQSI-ENVIRONMENT DOES NOT
IC32037 - MQSI ERROR RFH2 MESSAGE FAILS TO CONVERT. REASON 2116 -
IC32047 - CONTROL CENTER HANG DURING IMPORT AND/OR DEPLOY LARGE NUMBER OF
IC32155 - OUTPUT FROM MQSIREADLOG CORRUPTED, CAUSING INCORRECT DATA IN
IC32259 - MQBR* GROUPS NAMES DEFINED IN UPPERCASE ON WINDOWS CAUSES AUTHE
IC32427 - V201 AND V202 TO V2.1 MRM MIGRATION AND COEXISTENCE
IC33040 - INSUFFICIENT DETAIL ON IMPLEMENTING THE PASSTHRU FUNCTION.
IC33066 - MQE NODES SENDING DUPLICATE MESSAGES
IC33330 - SECURITY TAB IN NNSY FORMATTER GUI IS GRAYED OUT FOR NEWLY CREA
IY16738 - START OF BROKER CONFIGURED TO USE ORACLE GIVES AN ERROR - UNABL
IY21734 - MQSI CRASHED WHEN ADDITIONAL INSTANCES OF A MESSAGE-FLOW WERE
IY22100 - CONTROL CENTER CACHE NOT REFRESHING PROPERLY.
IY22757 - INCOMPLETE OR INVAVID SUBSCRIPTION DATA RETURNED DURING PUB/SUB
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
IY26567 - RESETCONTENTDESCRIPTOR NODE DOESN T FORMAT MRM MESSAGE CORRECTL
IY26986 - RECEIVED AN ERROR RUNNING NNFIE CAUSING AN OUPUT OPERATION
IY28136 - PART OF DBCS CHARACTERS CHANGED TO DIFFERENT CHARACTERS WHEN
IY28181 - NEONRULES AND NEONFORMATTER WERE NOT ABLE TO BE IMPORTED.
IY28520 - 2.0.2 MANUALS NOT CORRECT IN STATING HOW TO BUILD A NEONMSG
IY28733 - CSD02 IC30011 CHANGED THE PROCESS OF ERROR AT MQINPUT NODE WHER
IY28995 - BIPSERVICE TERMINATING ON AIX IN AN ENVIRONMENT WITH LOT OF MQS
IY29050 - ORA-03113: DFE TERMINATES AFTER A LOSS OF COMMUNICATION WITH DB
IY29128 - BROKER 'CONFIGURATION MESSAGES' ARE SENT TO THE MQSERIES DEAD
IY29419 - BROKER EXITING EARLY BEFORE CONFIGURATION MESSAGE ARRIVE FROM E
13040 - Add Idoc parser to build tree
18062 - Wrong level name in level.txt on NT CSD
18637 - Expiry field ignored on MQe messages.
18851 - Database error handling "too visible"
18894 - Un-deploying Scada node on HP causes database error
19063 - SQL definitions do not conform to NLS rules
19080 - logExit missing on MQe/SCADA table creation functions
19255 - JNI problems in MQe and SCADA
20093 - Broker reports error when applicationOriginData field is set
20271 - Deploy Opn. Successful even when Queue Mgr Dir. is invalid
23464 - lslpp and list installed software in smit show wrong version of
23536 - BIP2801E on broker startup if DB2 not installed
23775 - Errors on deploying message set 2.1->2.02
23988 - 2.1->2.02: Relax broker to allow bytes for Ext Dec Length Units
24063 - Adding PSService node to workspace
24496 - Invalid MF copy/assignment while broker copy/paste
24882 - BIP0056E when importing a topology which contains bend points
24962 - Message Set identifier 'Cwf' causes deploy to fail
25446 - Import Resources window unavailable after Cancel action
25611 - Abend if DLQ is full
25779 - Incorrect location of memo file in maintenance documentation
25993 - Deploy failures cause a cascade of failures
CSD02 (PTF U200161)
___________________
This is the second PTF for IBM MQSeries Integrator Version 2.0.2 for
Windows NT. It is delivered via PTF U200161 for APAR IC31702.
It contains fixes for ALL the problems listed below:
Name - Abstract
IC31702 - CUMULATIVE MAINT #02 FOR MQSERIES INTEGRATOR FOR WINDOWS NT V202
IC28463 - LENGTH FUNCTION NOT WORKING IF THE ELEMENT ARRIVE WITH A DATA O
IC29235 - SPURIOUS ESQL SYNTAX ERROR IN COMPUTE NODE WHEN SETTING A FIELD
IC29387 - MESSAGE TRANSLATION INTERFACE SEEMS TO HAVE A PROBLEM WITH THE
IC29416 - COMPUTE NODE ADD MAPPING TO MRM LAYOUT GENERATES BAD ESQL
IC29789 - IT APPEARS THAT A CDATA SECTION IS MARKED AS "SPECIAL" IN THEXM
IC29873 - NO ABILITY TO ASSIGN A VALUE OUTSIDE THE SPECIFIED RANGE
IC29992 - IF DEFAULTHEX IN THE DB TABLE HAS 1000 BYTES OR MORE THEN SPACE
IC30011 - INCORRECT MESSAGES, WHICH ARE SENT TO THE FAILURE-TERMINAL OF A
IC30171 - REORDER OF ELEMENTS FOR A MESSAGE SET, WITHIN A COMPOUND TYPE
IC30502 - OUTPUT TREE AFTER PARSING XML MESSAGE IS NOT CORRECT
IC30611 - STRESS PROBLEM WITH NEON DOMAIN MESSAGE PARSER
IC30653 - WHEN YOU UNSET A PROMOTED PROPERTY, DEFAULT IS LOST
IC30673 - SQL SYNTAX CHECKER REPORTS ERROR ON VALID SYNTAX WHICH DEPLOYS
IC30818 - DEPLOYING FROM A 2.0.1 CONFIGMGR TO 2.0.2 BROKERS.
IC30888 - THE MQINPUTNODE ADVANCED PROPERTIES FIELDS MATCH MESSAGE ID AND
IC31040 - OUTPUT FROM THE NEON FORMATTER NODE IS DIFFERENT TO OUTPUT FROM
IC31150 - GETTING AN ERROR BIP1835E. THE CREATE RUNTIME MESSAGE DIC.
IC31306 - USING THE NEW ERA OF NETWORK NODES AND GETTING A MEMORY
IC31362 - MESSAGE GROUPING FUNCTION ONLY PROCEED THE FIRST MESSAGE
IC31418 - Formatter GUI not working with Oracle greater than 8.1.6
IC31445 - DEFINING A STRING MRM-MESSAGE ELEMENT AS NULL-TERMINATED WITHIN
IC31612 - NEWERAOFNETWORKS VISUAL TESTER FAILS WITH NNVT.EXE - APPLICATIO
IC31657 - NEON PROPERTIES FILE MQSIV2NEONPLUGINS.PROPERTIES IS
IC31739 - WHEN USING THE DEBUGGER WITH XML MESSAGES THAT MIX BOTH
IC31825 - BOTHRESH AND BOQNAME NOT WORKING PROPERLY WHEN ERROR OCCURS ON
IC31862 - LITERALS AND OUTPUT CONTROLS DON T ALPHABETIZE UPON REFRESH
IC31916 - MESSAGE CONVERSTION TROUBLE (SI/SO HANDLING) WITH MQSI
IY17561 - RULES NODE NOT PROCESSING A MQS EXPIRY NO PROPAGATE FIELD IN SU
IY17806 - WHEN BROKER HAS LONG CONNECTION TO DATABASE, SOMETIMES THE CONN
IY18458 - ERROR PUT TO DLQ BY THROW NODE IS UNREADABLE - 4048 ERROR AND
IY19242 - LOCAL_TIMEZONE ESQL IS RETURN 239/241 INSTEAD OF 240 ABOUT 50%
IY20050 - ERROR WHEN OUTPUT TERMINAL THAT IS LABELLED WITH A NAME THAT
IY21179 - DFE COSUMING HIGH CPU AND HANGING WITH NO ERRORS
IY22197 - ELEMENTS CONTAINING THE &APOS: ENTITY ARE NOT BEING HANDLED COR
IY22611 - FAILURE TO COMPLETELY IMPORT FORMATS AND RULES INTO AN ORACLE
IY23076 - DEFINING BINARY ELEMENTS/FIELDS IN A MRM-MESSAGE SET WITH
IY23087 - EXCESSIVE CASHING PERFORMED BY MQSI CAN LEAD TO MEMORY HEAP
IY24470 - APITEST CORE DUMPS FOR SOME FORMATS HOWEVER DOES APPEAR TO WORK
f21983 - New Era Renaming - V2.0.2 Service Stream
16758 - Exponential growth of DeletePub messages in collective
18105 - Mixed stress test fails with corupt core file
19084 - Migration library shipped with wrong name
19406 - Regression - V2.0.1 plugin fails under V2.0.2
20216 - Exception thrown creating EG on a migration broker
20404 - Multiple broker deploy fails
20592 - CARDINALITY returns incorrect results if path invalid
21173 - Using \u3044 causes filter error
22471 - IBM Primitives nodes list inconsistent in Assignment view
23018 - MRM/byte alignment pad/valid values are rejected
CSD01 (PTF U200147)
___________________
This is the first PTF for IBM MQSeries Integrator Version 2.0.2 for
Windows NT. It is delivered via PTF U200147 for APAR IC30416.
It contains fixes for ALL the problems listed below:
Name Abstract
IC30416 - CUMULATIVE MAINT #01 FOR MQSERIES INTEGRATOR FOR WINDOWS NT V202
IC30331 - CHECKIN GIVES ERROR BIP1205E ON MQSI V202 AT DB2 V7.1 FP2 LEVEL
IY17486 - COBOL STRUCTURES, CONTAINING SIGNED DECIMAL NUMBERS (PIC S9),
IY19382 - DATAFLOWENGINE LOOP
f13586 - MQe/Scada - Migration Aid
f14128 - README UPDATES
f17791 - update Korean index.htm
f18038 - NLS ESQL Reference
f18057 - Add undocumented plugin logging env variables
f18096 - Update english pdfs. bipyal03 & bipyar03
f18182 - Italian PDFS
f18335 - Updated index.htm files including UNIX Platform
f18725 - Updated English and Brazilian index.htm files
f18822 - update index.htm nls files with ESQL ref
13712 - MTI problem converting floats which are not explicity cast
14500 - Over optimization in MTI refresh bitstream method
15437.1 - Fix junction support on NT output trees
16632 - STRESS: PubSub matches wrong retained pub topic16951 - Standard XML entities rejected when standalone="yes"
17031 - BIP2211E is an inapropriate mesage for duplicate Scada port
17175 - Expiry field ignored on MQe messages.
17301 - Missing exit trace from WebDavException::GetErrorCode
17315 - Missing Exit trace from ATTRIBUTEGROUP:: GetDTDAttributes
17359 - Missing exit trace from UG methods
17413 - Missing exit trace from COMPONENT::GetLockInfo
17423 - Missing exit trace from GPROCS::AccessComponentHandle
17429 - Missing exit trace from UGRegistry.getGroup
17495 - MQeInput nodes - inconsistent Queue Managers not diagnosed.
17593 - When Running the RTS test psubatest12 on NT, event log entries
17603 - Missing MQe ini file not diagnosed.
17684 - Non-english uninstalls leave some menu items around....
17718 - Flow with two MQeInput nodes fails to initialise correctly.
17721 - MQSISTOP hangs following MQe flow initialisation failure.
17725 - GLOSINDX.HTML contains broken tag when element name is in DBCS
17742.1 - Timing hole in sql cache
17753 - Badly configured scada node causes broker to fail on redeploy
17757 - problem with using keyboard on scribble sample
17761 - MQe/Scada db tables have incorrect size for column BrokerUUID
17763 - CCI_SQL_TRANSACTION_COMMIT ignored
17764 - ImbDecimal needs to support ".xyz" numbers
17765 - Repeating elements take value of first element
17769 - MQeInput node with message domain MRM not working.
17814 - reame.txt and memo.ptf not getting installed
17817 - S201 IC01 SupportPac does not support S202 export file format
17818 - Japanese Neon install shows failed when successful
17822 - Error closing the MQe server while stopping broker.
17832 - Start menu shortcut to NEON pdf incorrect
17871 - Incomplete cleanup when MQeInput has invalid queue manager.
17884 - Unable to write to trace file.
17980 - Missing messages in EventLog
17994 - XML Parser does not correctly process empty elements
18022 - MQInput + SCADA Input nodes can not send msgs in same flow
18026 - Persistence attribute not set by Scada Input Node
18030 - postcard sample will not allow entry of UPPERCASE characters
18032 - Memory leak + tidy up of indenting
18069 - Wrong setExpiry and getExpiry MQe interpretation
18094 - Replace ImbException with ImbRecoverableException
18193 - Ensure that clean start + finish works correctly (18192)
18198 - Control Center ESQL "Not a valid Compute Node" with PASSTHRU
18214 - Neon properties files need to be updated in CC
18262 - Transactionality still lost for some MQe messages
18292 - Database connections are not released when SCADA
18301 - Problems setting 50 breakpoints or more
18304 - Message delivery indicated although no breakpoints set
18370 - Clean session _may_ remove QoS2 messages
18469 - NLS: DBCS chars not displayed in Field value
18496 - DFE process seems to be dying after
18497 - Fix migration defect
18558 - Copyright Statements
18657 - NT install pacakge needs to includ UNIX pdf files
18778 - plugin parser can not be rolled if deploy fails
18840 - Behaviour of the 'Cancel' button on the DB2 Panel
18841 - No reference to NEON component in the summary panel
18854 - Event Map
19061 - icon displaying in explorer
####### ------- end of file MEMO.PTF ------------#######################