| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 2.0.x to 2.1 Conversion Warning |
« View previous topic :: View next topic » |
| Author |
Message
|
| KSkelton |
 Posted: Wed Apr 17, 2002 6:32 am Post subject: |
 |
|
Apprentice
Joined: 28 Oct 2001
Posts: 45
|
We have run into an MQSI bug in upgrading from 2.0.x to 2.1.
We have exported our Message Sets from 2.0.2 and then imported them into 2.1 (CSD1 & CSD2).
If any of the elements in the message sets are defined as, "Integer" or "Float" they become Left Justified with a padding character of space! Obviously this will cause your message flows to produce parsing errors.
Of course you can go into each and every message set and change each and every Inetger field back to right justify with pad of '0'. If you have as many message sets and Integers as we do, this is not acceptable.
IBM claims that the problem is not with 2.1 but with 2.0.x. IBM does not have a fix for this yet. They are thinking of releasing a work around such as running a script against the 2.0.x export files to change justification before they are imported.
Just a heads up for those looking to upgrade. |
|
| Back to top |
|
 |
| meekings |
| Posted: Thu Apr 18, 2002 5:23 am Post subject: |
|
|
Voyager
Joined: 28 Jun 2001
Posts: 86
Location: UK, South West
|
| So ... does anybody know what hand editing of the exported file is required to fix this prior to re-importing? |
|
| Back to top |
|
|
| KSkelton |
| Posted: Thu May 16, 2002 12:25 pm Post subject: |
|
|
Apprentice
Joined: 28 Oct 2001
Posts: 45
|
IBM has released a fix for this problem:
WMQIv2.1.0 for NT at PTF level U200171 (CSD02)
Notes
-----
This fix is for the following problem:
PMR 07005 :
When importing a messageSet that has been created
using the COBOL copybook importer, then in WMQI
V2.1, the Padding and Justification will be
shown as Left and Space respectively. These
defaults should be Right and '0' for Numeric
fields with the physical type of Extended
Decimal. Fixing the problem in the COBOL importers
in V2.01, V2.02 and V2.1 will not change the
values that have already been written into the
messageSets that have been created. Therefore,
mqsiimpexpmsgset has been changed such that if
a back level messageSet is imported, then the
defaults for Padding and Justification are set
to '0' and Right for Extended Decimals. This can
be done because the user could not modify these
fields on V2.01 and V2.02, and therefore no other
values could have been specified by the user.
================================================= |
|
| Back to top |
|
|
| philip.baker |
| Posted: Wed Aug 14, 2002 12:56 pm Post subject: |
|
|
Voyager
Joined: 21 Mar 2002
Posts: 77
Location: Baker Systems Consulting, Inc. - Tampa
|
KSkelton,
I am finding that the import is still a problem with the mentioned types of fields even with CSD02 loaded on WMQIV2.1. And I have too many imported message sets to have to modify by hand. Do you know if there was an APAR written for this issue?
Thanks,
Phil |
|
| Back to top |
|
|
| KSkelton |
| Posted: Thu Aug 15, 2002 4:34 am Post subject: |
|
|
Apprentice
Joined: 28 Oct 2001
Posts: 45
|
Philip,
Yes fix 07005 fixes this particular import problem. I do not have the APAR number.
You may also need APAR IC34115 (PMR 39777,379) which addresses the importing of COBOL copybooks to create message sets. Signed fields, particularly DECIMAL fields were not being setup correctly. Sign not being set, and padding character not being set.
We also needed APAR IC34246 (PMR#46589,379) which fixes the parsing of DECIMAL fields. WMQI was trying to translate the DECIMAL fields into a TIMESTAMP! One wonders how much testing IBM performed on this product before release.  |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
