| Author |
Message
|
| n1ghtrain |
 Posted: Thu Mar 19, 2009 11:05 pm Post subject: Support for DBCS in WMB 6.1.0.3 |
 |
|
Apprentice
Joined: 23 Mar 2006
Posts: 48
Location: Bangalore
|
I have WMB 6.1.0.3 running on Z/OS with DB2 8.1.
I'm trying the setup with steps mentioned in
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=/com.ibm.etools.mft.doc/ac00407_.htm
When i set
MQSI_DB2_CONVERSION=UNICODE, the starting of the broker gives the following error.
| Code: |
BIP2901W IWWMBRK 0 The character data '42705' returned by the database could not converted
BIP8875W IWWMBRK 0 The component verification for 'IWWMBRK' has finished, but one or more checks failed. : ImbComponentVerification(137)
' returned by the database could not be converted to Unicode. : ImbOdbc(368) |
Not sure whether its the problem with DB2 version or 'UNICODE' is case sensitive.?
**
Then i left
MQSI_DB2_CONVERSION=MIXED
Flow is MQInput -> Compute -> MQOutput -> FileOutput
The message has MQMD.CCSID = 1208 throughout.
MQ output and File output looks fine But DB2 insert in compute doesn't seem to work for Double Byte characters.
Its stored as Hex (1A 00 1A 00 ) into CHAR column in the table.
What am i missing here. Same flow seem to work on Aix. Any Suggestions/Comments.? |
|
| Back to top |
|
 |
| n1ghtrain |
| Posted: Thu Mar 19, 2009 11:31 pm Post subject: |
|
|
Apprentice
Joined: 23 Mar 2006
Posts: 48
Location: Bangalore
|
Forgot to mention that i'm able to insert the same data from QMF and view it correctly.
Also in the compute node i have tried using PASSTHRU with no luck,
 |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Mar 19, 2009 11:39 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
What CCSID was the DB2 Database created with? Was it one that is capable of holding double byte characters?
It sometimes pays to have a common CCSID throuough if possible
I'd also check the support matrix for Broker 6.1.0.3 and check which Fixpack of Db2 V8.1/8.2 is supported. Broker 6.1 won't work (on windows or Linux) on some versions of DB2 V8.1.
_________________
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 |
|
|
| n1ghtrain |
| Posted: Fri Mar 20, 2009 1:16 am Post subject: |
|
|
Apprentice
Joined: 23 Mar 2006
Posts: 48
Location: Bangalore
|
The database is capable of holding double byte characters and I am able to insert the same data from control centre or QMF. But when i'm trying the same from message flow it is storing as Hex (1A 00 1A 00 ).
The flow and message uses 1208 as CCSID throughout [No conversion at MQ Input].[I verified it by putting it into Debug].
What worries me is whether Permitted value for MQSI_DB2_CONVERSION includes 'UNICODE'.
This Suggests it does
Sample BIP Profile suggests it doesn't |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Mar 21, 2009 8:10 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
| n1ghtrain wrote: |
The database is capable of holding double byte characters and I am able to insert the same data from control centre or QMF. But when i'm trying the same from message flow it is storing as Hex (1A 00 1A 00 ).
The flow and message uses 1208 as CCSID throughout [No conversion at MQ Input].[I verified it by putting it into Debug].
What worries me is whether Permitted value for MQSI_DB2_CONVERSION includes 'UNICODE'.
This Suggests it does
Sample BIP Profile suggests it doesn't |
Be aware that the broker's internals are in ccsid 1200 and not 1208 (utf-8 ) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
