| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| The input Cobol copybook fields onto the destination |
« View previous topic :: View next topic » |
| Author |
Message
|
| chris boehnke |
 Posted: Sat May 19, 2007 1:41 pm Post subject: The input Cobol copybook fields onto the destination |
 |
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi,
I have a message flow:
Input->Compute->Output
The incoming msg is a CWF(cobol copybook) and in the compute node it is converting into MRM with this part of code in Compute node:
CREATE LASTCHILD OF OutputRoot DOMAIN 'MRM'
PARSE(InputBody."BLOB",
InputRoot.Properties.Encoding, InputRoot.Properties.CodedCharSetId,
'GeocodeServiceMS', -- MessageSet
'msg_ESBMESSAGEHEADERNEW', -- MessageType
'CWF'); -- MessageFormat
The incoming field is
20 MSGBD-ACCURACY PIC 9. //In the Cobol Copybook
1 NUMB MSGBD-ACCURACY //In the Rfhutil Client Data Tab view.
When I create the message definition file, in the message definition file the properties for this field are:
Logical Properties->Local Element
Name:MSGBD-ACCURACY
Type: xsd:short-
Physical Properties->CWF->Local Element
Physical Type: External Decimal
Length count: 1
Length Units: Bytes
I am getting a Parsing error for this field.
What could be the reason?.
If I change the properties the in the message definition file for this field:
Logical Properties->Local Element
Name:MSGBD-ACCURACY
Type: string
then this field is parsing without the problem....
Please suggest what could be the reason and how to handle this field?.
Thanks. |
|
| Back to top |
|
 |
| Bill.Matthews |
| Posted: Sat May 19, 2007 3:45 pm Post subject: |
|
|
Master
Joined: 23 Sep 2003
Posts: 232
Location: IBM (Retired)
|
Chris,
When you display the message with RFHutil - along with the COBOL copybook:
1. Are the copybook length and data length the same value?
2. For the field in question, what is the actual value - in hex?
My guess is that the field in question is not a numeric value - and is probably not used by the COBOL application and thus is not initialized.
While you are checking this field, also make the same checks of the other PIC 9 fields
_________________
Bill Matthews |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat May 19, 2007 7:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Make it easier on you....
Don't create the message in the message set, import the cobol copy book.
Make sure you specify as "compiler" not the system the copy book resides on but the system the broker resides on: i.e. broker on unix and cobol from zos:
Specify on the cobol import 2nd or 3rd screen Unix as system.
You may still specify a zos numeric format and other niceties like default nulls etc....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Sun May 20, 2007 7:32 am Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi All,
Now I figured out the problem. As there was a problem with one field datatype, it was throwing the parsing exception error. Now I corrected the datatype and the parsing is successful.
Thanks all for your valuable suggestions.
Chris. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun May 20, 2007 8:28 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Just wanted to share with you all another cause why the parsing would fail.
Our original message comes from the Mainframe (EBCDIC ccsid 500).
Our failover message is stored as a CLOB in a UTF-8 DB.
Parsing of the failover message failed...
Reason.
The message contained some special character (Ň).
Those special characters are 2 byte characters in UTF-8 but only one byte characters in EBCDIC. The content of the message (parsed as by copy book) was off by one byte after the the special character until there was a field that could not be parsed and the parser threw an exception....
So yes sometimes the CCSID of the message does matter.
Solution
We had the preceding flow spit out the message in EBCDIC...
Enjoy
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
