| Author |
Message
|
| apiddi05 |
 Posted: Fri Jun 03, 2011 1:31 am Post subject: Parse decimal to Packed Decimal with CWF msgset on Windows |
 |
|
Newbie
Joined: 03 Jun 2011
Posts: 3
Location: Singapore
|
We are developing a message flow and a CWF message set to send message in EBCDIC to backend system, expecting few fields in packed decimal. We have a message set with few fields logical type 'decimal' and physical type 'packed decimal' with lenght 5. When flows deployed and ran to parse decimal 1234 to packed decimal, its parsing to '4f23010000'. Even after a long struggle, changing code pages and changing possible configurations of both flow and msg set it didn't resolved.
When we deploy the same flow in AIX to test, it went fine and got expected result '000001234f'.
Any idea on this behavior of Windows XP on this kind of parsing issue with MB flows? |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Jun 03, 2011 4:02 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Look at the Endian settings on the system where is does not work.
_________________
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 |
|
|
| fjb_saper |
| Posted: Fri Jun 03, 2011 8:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
When importing the cobol copy book make sure you set the endianness correctly on the last of the 3 panels on the import wizard.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| apiddi05 |
| Posted: Mon Jun 06, 2011 7:35 am Post subject: |
|
|
Newbie
Joined: 03 Jun 2011
Posts: 3
Location: Singapore
|
Dear smdavies99,
Endian settings didn't made any difference too. I deleted MQMD before parsing so that to use 'default packed decimal byte order'.
By the way I am using V7.0 toolkit.
Dear fjb_saper,
The most intrusting thing is we don't get Cobol copy book, i am just creating msg set manually for more than 330 fields 
We deploy flow successfully into dev AIX...but Windows issue still persist.
Thanks,
Anand |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 06, 2011 7:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| apiddi05 wrote: |
| Endian settings didn't made any difference too |
The problem in your original post is the number 1234 being interpreted with the wrong endinesness (if that's the word!). Why delete the MQMD? You need that to describe the byte order of the message - if you interpret a z/OS packed number using Windows defaults you'd get this effect.
| apiddi05 wrote: |
| i am just creating msg set manually for more than 330 fields |
Yikes. Why no copybook?
| apiddi05 wrote: |
| We deploy flow successfully into dev AIX...but Windows issue still persist. |
This absolutely proves the point. These 2 platforms use different byte orders, but AIX (IIRC) uses the same as z/OS.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Mon Jun 06, 2011 5:40 pm Post subject: Re: Parse decimal to Packed Decimal with CWF msgset on Windo |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| apiddi05 wrote: |
| We are developing a message flow and a CWF message set to send message in EBCDIC to backend system, expecting few fields in packed decimal. ... Even after a long struggle, changing code pages ... |
For WMQ headers: CodedCharSetID is for character data; Encoding is for numeric data; Format is for distinguishing between the two.
For packed decimals, either the broker should set the desired output Encoding for the target system, or else the target system should enable convert for MQGET. |
|
| Back to top |
|
|
|
|
