ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » IIB9 - Parser error

Post new topic  Reply to topic
 IIB9 - Parser error « View previous topic :: View next topic » 
Author Message
srs
PostPosted: Wed Nov 25, 2015 4:40 pm    Post subject: IIB9 - Parser error Reply with quote

Newbie

Joined: 25 Nov 2015
Posts: 3

Hi All,

Our Development environment recently migrated IIB 9.0.04 tool kit. This environment is having WMB 7.0.0.6 code. After toolkit got upgrade my interface not able to parse response copybook and throwing below error "CPI Converter Input Data Invalid:decimal:ùùùù".

Its currently failing where one of the element type is short , length is 4. The value we will get for this is 9999 or 0.

This code is currently in production and its working if environment is 7.

Thanks,
Anitha.B
Back to top
View user's profile Send private message
timber
PostPosted: Thu Nov 26, 2015 1:18 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280

Quote:
After toolkit got upgrade my interface not able to parse response copybook and throwing below error "CPI Converter Input Data Invalid:decimal:ùùùù".
That is an error from the MRM parser. It comes from the runtime, not from the toolkit.
Quote:
Its currently failing where one of the element type is short , length is 4.
Please describe the CWF physical format properties of this element.
Quote:
The value we will get for this is 9999 or 0
Which value *should* it be in the test that produces the error?
Back to top
View user's profile Send private message
srs
PostPosted: Thu Nov 26, 2015 3:15 am    Post subject: Reply with quote

Newbie

Joined: 25 Nov 2015
Posts: 3

The element properties:

Physical Properties-CWF1-
Physical type - External Decimal
Length - 4
Justification - right
Padding character - '0'
Encoding Null - Null logicalValue
Encoding Null Value - 0

The value of the element we get is 9999 or 0.

Let me know if u need more details.
Back to top
View user's profile Send private message
timber
PostPosted: Thu Nov 26, 2015 4:35 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280

OK - please answer all of the following questions:
0. For the message that triggers the error what should the answer be: 0 or 9999?
1. Was the runtime upgraded as well?
2. Any changes to the machine where the message flow is running?
3. Did you rebuild the BAR file after upgrading the toolkit?
4. If you re-deploy an old BAR file ( built using the old toolkit ) does it work correctly?
5. Could this be a CCSID problem ( any changes to the sending application? )
6. Are you sure that all of the preceding fields are being correctly parsed? Is it possible that the parsing has gone wrong earlier, and this is the first field where it actually triggers an error?
Back to top
View user's profile Send private message
srs
PostPosted: Thu Nov 26, 2015 5:46 am    Post subject: Reply with quote

Newbie

Joined: 25 Nov 2015
Posts: 3

timber wrote:
OK - please answer all of the following questions:
0. For the message that triggers the error what should the answer be: 0 or 9999?
If Response is success then that field value will be 0 if its failed in end system then thsi field value come as 9999
1. Was the runtime upgraded as well?
yes.
2. Any changes to the machine where the message flow is running?
server toolkit upgraded to 9
3. Did you rebuild the BAR file after upgrading the toolkit?
no still ist having wmb7 code
4. If you re-deploy an old BAR file ( built using the old toolkit ) does it work correctly?
not working.
WMB7 toolkit and WMD 7 code working. - currently in PROD
WMB7 code with IIB9 tookkit installed we are seeing this issue
5. Could this be a CCSID problem ( any changes to the sending application? )
no changes to this. Not sure of this.
6. Are you sure that all of the preceding fields are being correctly parsed? Is it possible that the parsing has gone wrong earlier, and this is the first field where it actually triggers an error?
.
Before this there is one more element of string no error for this element after this element we have lot number of elemnets.
When I do debug step by step then its parsing correctly if i don't do debug then its throwing this error.
Back to top
View user's profile Send private message
timber
PostPosted: Fri Nov 27, 2015 12:04 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1280

I did say 'all'.

I'm happy to help, but only if you put in some of your own time to provide good information.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » IIB9 - Parser error
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.