Also it is unhealthy when you cast your bitstream as char to set it to the CCSID of the Input as you did not specify a CCSID in your ASBITSREAM command. Suggestion use the same CCSID in both ASBITSTREAM and CAST... You might be hitting some weird CCSID translation problem especially if your input message was in EBCDIC....
Now if due to that fact some character translates into something that is not authorized for the CData section you are SOL.
Let's see with input message in CCSID 500.... and broker CCSID = 819
You are creating the bitstream in CCSID 0 (defaults to the platform the broker is on. Check value with mqsiservice -v? ). If the broker is running on Unix under CCSID 819 you might get 819 here. Better to set the CCSID explicitely... You are then casting this to a char using CCSID 500 on the BLOB ... and you expect something else than gibberish???
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