| Author |
Message
|
| sunilagarwal.1982 |
 Posted: Sun Aug 14, 2011 9:10 pm Post subject: Cobol Copy messages failing after MQ/MB upgrade |
 |
|
Novice
Joined: 04 May 2009
Posts: 20
|
I upgraded mu MQ /Message broker and Operating system to MQ7/MB7 and REHL 5 from MQ5.3/MB6 and REHL3(Red Hat Enterprise Linux AS release 3 (Taroon Update 9),
I have a message flow which takes Input message generated by Cobol copy Book (Mainframe system). And process it and create a respective xml files.
After upgraded my input message started failing in message flow (MQ7/MB7/REHL5) with below error.
“Navigation error ImbRecoverableException caught from worker->parseNext.App1_App2_1_DownloadMessage_CC_MSGSET 1 CWF1 /EDIB816050/O50QTY01_AREAQL CWF Parsing error0 CWFWorker::parseNext EDIB816050 O50QTY02_AREA /EDIB816050 CPI Converter Input Data Invalid (External decimal - Invalid Positive sign code).”
But If I process the same message on older version of message flows it is getting processed successfully.
Could you please let me know what wrong going on here and how I can process the message on upgraded MQ/MB. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Aug 14, 2011 10:56 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you running on WMB 7.0.0.2 ? If not upgrade. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sunilagarwal.1982 |
| Posted: Sun Aug 14, 2011 11:32 pm Post subject: |
|
|
Novice
Joined: 04 May 2009
Posts: 20
|
Correcting the Message Broker Version : It is WMB 6.1.0.9, Not WMB 7,
Below are the configuration Details:
Upgraded system:
BIP8997I: Product: WebSphere Message Brokers
BIP8996I: Version: 6109
Name: WebSphere MQ
Version: 7.0.1.5
Operating System
Red Hat Enterprise Linux Server release 5.4 (Tikanga)
Old system:
BIP8997I: Product: WebSphere Message Brokers
BIP8996I: Version: 6003
Name: WebSphere MQ
Version: 530.10 CSD10
Operating System
Red Hat Enterprise Linux AS release 3 (Taroon Update 9) |
|
| Back to top |
|
|
| sunilagarwal.1982 |
| Posted: Mon Aug 15, 2011 12:02 am Post subject: |
|
|
Novice
Joined: 04 May 2009
Posts: 20
|
| Can you tell me the reason as to why my messages are failing in new upgraded system. |
|
| Back to top |
|
|
| WGerstma |
| Posted: Mon Aug 15, 2011 12:44 am Post subject: |
|
|
Acolyte
Joined: 18 Jul 2011
Posts: 55
|
I assume, the Broker is right and your input format is not ok.
I also was in a migration project to 6.1, and some FixedLength message sets which worked in 6.0 caused trouble in 6.1. In all cases it was a problem with the input format. I suppose in 6.0 the check of the input was less strict than it is in 6.1 |
|
| Back to top |
|
|
| sunilagarwal.1982 |
| Posted: Mon Aug 15, 2011 7:44 am Post subject: |
|
|
Novice
Joined: 04 May 2009
Posts: 20
|
How I can correct the message format? Did you also get same type of exception. How you fix the issue.
Is there any chance that this issue can be due to the 64 bit Operating system. I see that Cobol Copy book is installed on OS but not sure if message flow is using 64 Bit or still point to 32 Bit libraries. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 15, 2011 7:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Are you certain you followed all the steps for migrating data definitions appropripate for the source and target versions?
Are you certain these steps completed successfully?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sunilagarwal.1982 |
| Posted: Mon Aug 15, 2011 8:12 am Post subject: |
|
|
Novice
Joined: 04 May 2009
Posts: 20
|
| Yes, As per my best knowledge, we followed all the steps for migrating data definitions, This broker has more than 150 message flow running, and all are working fine. We are having issue with this Cobol Copybook formatted message only. Is there something different we were supposed to do as part of migration for handling these messages. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Aug 15, 2011 8:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The error message you posted says that the message contained a Positive sign in a place that was not allowed to have a Positive sign.
So either the Positive Sign is wrong or the model fails to allow the positive sign to occur. |
|
| Back to top |
|
|
| sunilagarwal.1982 |
| Posted: Sat Aug 27, 2011 7:30 pm Post subject: |
|
|
Novice
Joined: 04 May 2009
Posts: 20
|
Issue was with the data type of one of the field defined in message set. datatype of AREA field was defined as integer but message was having space always. Issue got resolved after changing the data type of AREA field as String.
But I still don't have the answer as to why it was working fine on lower version of message broker which was MB 6.0.
Thanks you all for you help.
Happy learning !! |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Aug 27, 2011 9:31 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Without you formally raising a PMR to get the definitive answer,
It might well be this...
| WGerstma wrote: |
| I suppose in 6.0 the check of the input was less strict than it is in 6.1 |
This is not uncommon where a later version of a product removes a few loopholes/features that were erronueously included in a prior release.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
