| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Question on MRM |
« View previous topic :: View next topic » |
| Author |
Message
|
| prasadpav |
 Posted: Mon Sep 12, 2005 3:44 am Post subject: Question on MRM |
 |
|
Centurion
Joined: 03 Oct 2004
Posts: 142
|
Hi all,
I'm developing a message flow which does the EBCDIC to ASCII conversion. My message broker is running on AIX. The mainframe application sends a message and expects a response. The request & response formats which the mainframe application expects is:
| Quote: |
Request:
FIELDNAME SIZE FIELD_TYPE
FIELD1 18 Text
FIELD2 11 Number S9(9)v99
FIELD3 8 Number
Response:
FIELDNAME SIZE FIELD_TYPE
FIELD1 18 Text
FIELD2 11 Number S9(9)v99
|
I'm not a mainframe guy, so there are few areas around datatypes which i'm not clear of. Hope to get some answers from this forum.
Questions:
1) When the message broker receives a message from mainframes, having "Number S9(9)v99" datatype for FIELD2 doesn't necessary mean that, that value is a packed decimal. Is it true? I think it really depends on the cobol copy book definition.
2) If "Number S9(9)v99" is a packed decimal, then when I create my message set to convert from EBCDIC to ASCII, then I MUST import cobol copy book in order to create message definition. Is it correct? or Can I just declare a message definition having string element in CWF and still get the EBCDIC to ASCII conversion? ( I dont think the later way is going to work, because there is no way message broker knows that one of the field value is a packed decimal). I dont have access to mainframe input message at the moment to test this bit.
3) What is the difference between "Number S9(9)v99" and "Number"?
Thanks alot in advance
Prasad |
|
| Back to top |
|
 |
| EddieA |
| Posted: Mon Sep 12, 2005 4:33 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
1) Yes, that definition in itself doesn't say how the data is stored. To be a pcked decimal, it must be declared as COMP-3.
2) No. You can still create the MRM by hand, making sure that the options are set so it is treated as PD.
3) The "v" shows where the decimal point would go, but it isn't an actual character. So, 123456 is stored when the value is 1234.56.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| 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
|
|
|
|
