|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Computational Value? |
« View previous topic :: View next topic » |
Author |
Message
|
Psynosis |
Posted: Wed Nov 24, 2004 6:37 am Post subject: Computational Value? |
|
|
Newbie
Joined: 18 Nov 2004 Posts: 2
|
I'm trying to fill the field:
MQ Inbound Copybook the field is listed with:
PIC S9(4) COMPUTATIONAL
VALUE +440.
Sending from MQ5.3 NT to a IMS then Mainframe.
this is for the datalength. When I send a message, it going to their DLQ with a 292. A screen shot of good messages shows a hex data of 01A70000 and the EBCDIC data of .x..
I'm trying to send that. I got the 01 & the 00, and am working on the A7. In dec it's 167. Using VB.NET I put MQMsg.WriteByte(167), using a text editor I see 01A70000 in the data field of the message I created and sitting in the transmission queue (c:\Program Files\IBM\MQSeries\Qmgrs\MyQManager\QUEUES\MyQueue\Q). When I send it, in there DLQ they see 019B0000. I have Data Conversion off on my sender channel. I do not understand why it's not showing up there as A7. I am hoping someone can help me with this.
Thanks,
Mark |
|
Back to top |
|
 |
EddieA |
Posted: Wed Nov 24, 2004 9:41 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Quote: |
PIC S9(4) COMPUTATIONAL |
This is a binary (integer) field.
Quote: |
Sending from MQ5.3 NT to a IMS then Mainframe |
These systems use different endian schemes for integers. How were you planning on converting this.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
oz1ccg |
Posted: Wed Nov 24, 2004 12:59 pm Post subject: |
|
|
 Yatiri
Joined: 10 Feb 2002 Posts: 628 Location: Denmark
|
The old and ugly way that allways works is sending it all as chars.....
This means that ASCII, EBCDIC, codepage whatever can be used/translated. WebSphere MQ can do the ASCII EBCDIC conversion for you. This require a MQMD.Format="MQSTR "
The it's up the the receiving applications to do the endian encoding, wheras it's binary on z/os or on an I586...
If you like to play with binary data between EBCDIC ASCII, it's once again up to your applications (or conv. exits). Personally I would not recomment the conv. exit, because it's moving application logic into the communication layer...
Just my $0.02  _________________ Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
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
|
|
|
|