I think we've discovered why it's a mess: the CCSID still represents wintel OS 437 and not MVS OS CCSID 500.
Encoding is 546 which is what was originally placed on the request message by me via the GUI. Hence the gui not converting it as it thinks it's already in ASCII format.
Will keep you posted on progress.
Post by Paul Clarke-----Original Message-----
Behalf Of Paul Clarke
Sent: 12 November 2013 02:22 PM
Subject: Re: Conversion of message data across platforms
Hi,
Well, it depends what you mean by 'made it worse'. As I said in my note if you
switch off the 'predict hexadecimal characters' I would expect MO71 to show
you gobbledygook since it will not be trying to show EBCDIC characters on an
ASCII terminal which is rarely going to come out well :-) So, anyway that option
merely answer one of you questions which was why does it look 'ok'ish' in
MO71.
However, the question as to why the message is not being converted is still
unanswered. As far as I can see you didn't answer my previous question.
What is the FORMAT of the message? ie. what do you see when you use MO71
to browse the message in the FORMAT field of the message descriptor (MQMD)
?
Cheers,
Paul.
Paul Clarke
www.mqgem.com
-----Original Message-----
From: Costa, D. (Damian)
Sent: Tuesday, November 12, 2013 11:47 AM
Subject: Re: Conversion of message data across platforms
HI Paul,
Predict option was enabled while I had the issue so I've subsequently disabled
The preview pane no longer shows the ASCII version and the convert option still
doesn't want to convert the message.
The developers are looking at me like I'm a dunce in the corner ..... it's really not
a good feeling because I sort of agree with them , this should be straight
forward.
So,
I went through the message with a fine toothed comb and found deep in
amongst the EBCDIC data a string of ascii characters that are from the original
request message, string is "AAAA-BBBB-CCCC-DDDD" . Could it be these 19
characters that are causing the gui and mq to turn to goo when trying to convert
it?
Post by Paul Clarke-----Original Message-----
Behalf Of Paul Clarke
Sent: 11 November 2013 06:20 PM
Subject: Re: Conversion of message data across platforms
Well...such is the power of MO71 :-)
Seriously though....this probably a feature called 'Predict
Hexadecimal characters'. If this is enabled then MO71 will try to
predict whether it is looking at ASCII or EBCDIC characters based on
the hit rate. If you disable this feature I suspect you will see the
gobbledygook you were expecting (or a line of dots).
Cheers,
Paul.
Paul Clarke
www.mqgem.com
-----Original Message-----
From: Costa, D. (Damian)
Sent: Monday, November 11, 2013 3:52 PM
Subject: Re: Conversion of message data across platforms
It's MQSTR.
The weird thing is in the MQMON preview pane I can see the initial
part of the message converted into readable ASCII characters.....
Post by Paul Clarke-----Original Message-----
Behalf Of Paul Clarke
Sent: 11 November 2013 05:33 PM
Subject: Re: Conversion of message data across platforms
Hi,
Well, I guess the first question is what is in the FORMAT field of
the MQMD of the generated message. If it isn't in something MQ
recognises then MQ won't be able to convert it and it will stay in
its original Encoding/CCDID no matter how you try to browse it.
Cheers,
Paul.
Paul Clarke
www.mqgem.com
-----Original Message-----
From: Costa, D. (Damian)
Sent: Monday, November 11, 2013 2:47 PM
Subject: Conversion of message data across platforms
Hi all,
Having a bit of a 'mare here. I'm placing a message on a MVS queue
using
the MQMON app from my laptop. I expected it to be in EBCDIC format
on the MVS queue even though the MQMON gui is placing ASCII data on
the queue I expected it to be converted at some point. The Encoding
for this message is
546 and CodedCharSetId 437 on the MVS queue. But when I view the
message on the MVS queue using the browser on MVS it shows in ASCII
format i.e. looks garbled. Looks to be ASCII from the MQMON GUI
though....
This then triggers an app to generate a message destined for an AIX box.
It's a sizeable message 400k in size which is sent over to an AIX box.
There is no
convert specified in the sdr/rcvr channel pair.
The message looks like it's in EBCDIC on the queue as no convert was
specified on the channel. When I try to view the message using MQMON
with
convert specified it still presents in EBCDIC. The encoding still says
546
and CCSID 437. Shouldn't this change when traversing different
Platforms?
No amount of fiddling with setting or anything in the MQMON gui will
allow me to view the message in ascii format.
I'm stuck and not sure what to try now.
Anyone have any ideas?
Thanks.
********************
Nedbank Limited Reg No 1951/000009/06. The following link displays
the names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ] This email
is confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are
provided in the Listserv General Users Guide available at
http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are
provided in the Listserv General Users Guide available at
http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
********************
Nedbank Limited Reg No 1951/000009/06. The following link displays the
names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ] This email is
confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided
in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided
in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
********************
Nedbank Limited Reg No 1951/000009/06. The following link displays the names
of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ] This email is
confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv General
Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv General
Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Nedbank Limited Reg No 1951/000009/06. The following link displays
the names of the Nedbank Board of Directors and Company Secretary.
This email is confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,