| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| EBCDIC Signed Numeric Fields that have Virtual Decimal Point |
« View previous topic :: View next topic » |
| Author |
Message
|
| rahdilarum |
 Posted: Tue Dec 09, 2003 9:00 am Post subject: EBCDIC Signed Numeric Fields that have Virtual Decimal Point |
 |
|
Novice
Joined: 02 Mar 2002
Posts: 15
Location: Winston-Salem, NC
|
Hello everyone, I Am using WMQI 2.1 with CSD 4
I imported a COBOL copybook with several Zoned Decimal fields.
Here is the list.
05 GPDFP-HOURS PIC S9(03)V9(05).
05 GPDFP-EARNED-HOURS PIC S9(03)V9(05).
05 GPDFP-PAY-RATE PIC S9(02)V9(04).
05 GPDFP-EARNINGS PIC S9(08)V9(02).
05 GPDFP-BASE-PAY PIC S9(05)V9(02).
05 GPDFP-HIRE-IN-RATE PIC S9(05)V9(02).
05 GPDFP-PERF-INDX PIC S9(03)V9(02).
05 GPDFP-TRAIN-PERF-INDX PIC S9(03)V9(02).
05 GPDFP-FOUR-WK-AVG PIC S9(02)V9(04).
The field
05 GPDFP-HOURS PIC S9(03)V9(05).
is imported to Message Set shows up as a DECIMAL has the following Custom Wire Format
Physical Type : Extended Decimal
Length Count : 8
Length Units : Bytes
Signed : Yes
Sign Orientation : Included Trailing
Virtual Decimal Point : 5
I have run time problem with the first Zoned Decimal Field.
And here is the Trace File
2003-12-09 11:03:08.999357 3356 ParserException BIP5285E:
Message Translation Interface Parsing Errors have occurred:
Message Set Name : 'ATISLHMSGSET'
Message Set Level : '1'
Message Format : 'CWF'
MessageType Path : 'ATISLHPR10_INPUT_DETAIL'
2003-12-09 11:03:08.999379 3356 ParserException BIP5171E: Custom Wire Format parsing error
An error occurred while parsing a Custom Wire Format message.
Current message : 'ATISLHPR10_INPUT_DETAIL'
Current element : 'GPDFP_HOURS'
Path from message root : '/ATISLHPR10_INPUT_DETAIL'
Offset from start of message : 66
See following errors for more details.
2003-12-09 11:03:08.999536 3356 ConversionException BIP5505E: Data conversion failed: data invalid. Type of data being read: decimal, data: 14.7600{;
A data conversion during reading or writing of a message failed because the input data was invalid for the output data type.
My next questions is should the field S9(10) be automatically imported as a Float instead of Integer ?
Any thoughts or ideas will be greately appreciated.
Thanks
Murali |
|
| Back to top |
|
 |
| kirani |
| Posted: Tue Dec 09, 2003 11:51 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Dec 09, 2003 11:57 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Is the data being converted between ASCII and EBCDIC. If so, where is the conversion being done. You can't treat COBOL signed fields as strings, because the sign byte is NOT a string character.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| rahdilarum |
| Posted: Tue Dec 09, 2003 12:33 pm Post subject: Regarding the Thread EBCIDIC signed data to ASCII .......... |
|
|
Novice
Joined: 02 Mar 2002
Posts: 15
Location: Winston-Salem, NC
|
Hello Kiran, I looked at the thread and I did pretty much what the last topic in the above mentioned thread said.
I have conducted two tests and the first succeeded and the second failed.
First of all I eliminated all the virtual decimal points in my COBOL Copybook and imported the copybook into my MRM.
Ofcourse PIC S9(10) was imported as integer, and so I had to manually change it to FLOAT in the Message Set.
I Am sending data from Mainframe and the format is "MQFMT_NONE" (Which was very important for this to work) and when the data gets thru everything works fine and I get my results(a well formed XML file). Cant ask for better I guess.
Then I wondered if WMQI will be able to recognize the Signed Decimal fields. The COPYBOOK was imported without any issues and all the fields are created as DECIMALS and the CWF interprets the virtual decimal point correctly.
But sadly at runtime the broker doesn't like the included trailing sign although it interprets the decimal position correctly. Earlier when the field was an INTEGER instead of DECIMAL things worked fine.
I requested for CSD06 to be applied and hoping that might solve this issue.
If CSD06 Solves I will let ya'll know. |
|
| Back to top |
|
|
| rahdilarum |
| Posted: Tue Dec 09, 2003 12:39 pm Post subject: WMQI 2.1 CSD Level |
|
|
Novice
Joined: 02 Mar 2002
Posts: 15
Location: Winston-Salem, NC
|
My apologies regarding CSD level. The highest level that could be applied to 2.1 for our situation is "05".
CSD "06" was for WMQIB 2.1 |
|
| 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
|
|
|
|
