| Author |
Message
|
| chris boehnke |
 Posted: Fri Jul 15, 2011 9:57 am Post subject: control characters |
 |
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi guys,
I am getting cobol data from a mainframe application. This data is decoded to base64 and dropped to message broker.
I am decoding the data in the message broker. the decoder output is BLOB.
The BLOB data has X'00' (null characters) at many places in the bitstream.
| Quote: |
| When I used create staetment with parse option to reset the domain to MRM, I see "" character in place of X'00'. |
Can I remove this character? Will it cause any day issues?
Thanks |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jul 15, 2011 6:26 pm Post subject: Re: control characters |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| chris boehnke wrote: |
Hi guys,
I am getting cobol data from a mainframe application. This data is decoded to base64 and dropped to message broker.
I am decoding the data in the message broker. the decoder output is BLOB.
The BLOB data has X'00' (null characters) at many places in the bitstream.
| Quote: |
| When I used create staetment with parse option to reset the domain to MRM, I see "" character in place of X'00'. |
Can I remove this character? Will it cause any day issues?
Thanks |
Don't touch this. First find out the CCSID of your BLOB. Be aware that if you BLOB was created in the wrong CCSID it may already have transformed characters into XML Illegal chars, or any substitution char that has been defined. The blob may no longer be parsable even though it was created from the broker...
Best would be to make sure that the target CCSID is a multibyte char set. This should avoid a number of problems.
There may be other problems then if the parse length is in bytes and not in characters...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Jul 15, 2011 11:24 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I have to ask why the MF Data which will be underneat actuall conforming to a Cobol CopyBook has been ENCODED (not IMHO decoded) as base64 before is has been sent to Broker.
Right since the early versions of Broker (2.0.1) the software has been able to handle MF data with ease (many devs these days shudder at the thought of using the MRM parser with a CWF format Te-He).
If I were you, I'd go back to the MF guys and find out why they are making your life so hard. Get them to plop the CopyBook data onto a Queue with the correct CCSID. Then create yourself a message set by importing the copybook.
KISS really applies when you are dealing with Z/OS (and any of its many subsystems such as IMS)
_________________
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 |
|
|
| chris boehnke |
| Posted: Mon Jul 18, 2011 6:38 am Post subject: Re: control characters |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
| fjb_saper wrote: |
Don't touch this. First find out the CCSID of your BLOB. Be aware that if you BLOB was created in the wrong CCSID it may already have transformed characters into XML Illegal chars, or any substitution char that has been defined. The blob may no longer be parsable even though it was created from the broker...
Best would be to make sure that the target CCSID is a multibyte char set. This should avoid a number of problems.
There may be other problems then if the parse length is in bytes and not in characters...
Have fun |
fjb/smdavies99,
We are testing this on our local with RFHUtil. We got the test data from our prod logs. This data has the control characters. I use RFHUTIL (CCSID is 437) to drop the data to Datapower queue manager which encodes the data to base64 and adds soap headers. When the message comes to our local, the ccsid is 1208. I am not changing the ccsid in message broker. I just decode the message and give it to message set.
The control character which I see is actually a space. But some how "" is introduced in place of space(blank) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 18, 2011 11:55 am Post subject: Re: control characters |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| chris boehnke wrote: |
fjb/smdavies99,
We are testing this on our local with RFHUtil. We got the test data from our prod logs. This data has the control characters. I use RFHUTIL (CCSID is 437) to drop the data to Datapower queue manager which encodes the data to base64 and adds soap headers. When the message comes to our local, the ccsid is 1208. I am not changing the ccsid in message broker. I just decode the message and give it to message set.
The control character which I see is actually a space. But some how "" is introduced in place of space(blank) |
So you start with an unknown CCSID (file content) loaded as CCSID 437 and you end somewhere there with 1208?
Better check out that all those conversions are made correctly!
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 18, 2011 11:55 am Post subject: Re: control characters |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| chris boehnke wrote: |
fjb/smdavies99,
We are testing this on our local with RFHUtil. We got the test data from our prod logs. This data has the control characters. I use RFHUTIL (CCSID is 437) to drop the data to Datapower queue manager which encodes the data to base64 and adds soap headers. When the message comes to our local, the ccsid is 1208. I am not changing the ccsid in message broker. I just decode the message and give it to message set.
The control character which I see is actually a space. But some how "" is introduced in place of space(blank) |
So you start with an unknown CCSID (file content) loaded as CCSID 437 and you end somewhere there with 1208?
Better check out that all those conversions are made correctly!
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
