|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
URGENT : USS problem on low values in packed zone |
« View previous topic :: View next topic » |
Author |
Message
|
guestman |
Posted: Wed Jun 11, 2003 5:00 am Post subject: URGENT : USS problem on low values in packed zone |
|
|
Newbie
Joined: 11 Jun 2003 Posts: 3
|
Hi,
For message recycle purposes, I need to store MRM messages in a DB2 database. Problem is that messages contain packed zones and when they are inserted by odbc driver into db2 database, messages are truncated. In fact, as they contain low values (00) in packed zone, i think this is interpreted by USS odbc driver like an ending character string.
Any idea to get rid of this problem will be welcome! |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Jun 11, 2003 5:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Can you describe better the format of the packed field, and the column you are inserting into? Can you also give an example of the ESQL you're using for the insert? |
|
Back to top |
|
 |
guestman |
Posted: Thu Jun 12, 2003 7:10 am Post subject: |
|
|
Newbie
Joined: 11 Jun 2003 Posts: 3
|
To be more simple and in order to simulate a low-value (00 hexa code), here is a sample e-sql code :
declare w_string char;
declare w_lowvalue blob;
SET w_lowvalue = X'00';
SET w_string = 'BEGIN' || CAST (w_lowvalue as CHAR CCSID 1208) || 'END';
insert into Database.MSGSTORE(DESCRIPTION) values(w_string);
--------------------
When I look at the message inserted in database, only 'BEGIN' substring is present. I tried it on NT environment, message is also truncated.
Any idea? |
|
Back to top |
|
 |
shalabh1976 |
Posted: Thu Jun 12, 2003 7:58 am Post subject: |
|
|
 Partisan
Joined: 18 Jul 2002 Posts: 381 Location: Gurgaon, India
|
I tried it on my NT box.
I got the output string as 'BEGIN.END'
When I looked at the hex equivalent of this string the '.' appeared as '00'. |
|
Back to top |
|
 |
guestman |
Posted: Wed Jun 18, 2003 3:13 am Post subject: |
|
|
Newbie
Joined: 11 Jun 2003 Posts: 3
|
Solution is to use BLOB data type into db2 database. Like this, BLOB data type is also to be used from WMQI part and x'00' is no more interpreted like an ending character string. |
|
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
|
|
|
|