| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| An Doubt in Security Exit on Z/OS |
« View previous topic :: View next topic » |
| Author |
Message
|
| vignesh1988 |
 Posted: Wed Jul 10, 2013 11:28 pm Post subject: An Doubt in Security Exit on Z/OS |
 |
|
Acolyte
Joined: 13 Apr 2013
Posts: 62
Location: Chennai
|
I have coded a Security Exit in C in Mainframe Z/OS 1.13 and it will make connection to Solaris Queue Manager. Iam using Agent Buffer to point to the message that is currently been sent and it's reaching the partner and there receiver exit is validating. But the block here for me is EBCIDIC and ASCII. Whatever data i pass from z/OS to Sun OS, it's going in Junk Values.
How can i transmit Data from z/OS where it reaches in the proper acceptable format and my channel gets authorized. I am sending as the same format that the partner exit expects,
Can anybody help me? |
|
| Back to top |
|
 |
| hughson |
| Posted: Thu Jul 11, 2013 3:43 am Post subject: Re: An Doubt in Security Exit on Z/OS |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| vignesh1988 wrote: |
| Can anybody help me? |
If I can figure out what it is you are trying to do, I will gladly help you. You can help me to understand what you are doing by answering the questions below.
| vignesh1988 wrote: |
| I have coded a Security Exit in C in Mainframe Z/OS 1.13 and it will make connection to Solaris Queue Manager. |
This sounds like you are saying that the security exit running on z/OS is making a connection to the Solaris Queue Manager. I am sure this is not what you meant. Do you perhaps mean that you are running a security exit at the sending end of a channel on z/OS where the receiving end of the channel is on Solaris?
| vignesh1988 wrote: |
I am using Agent Buffer to point to the message that is currently been sent and it's reaching the partner and there receiver exit is validating. But the block here for me is EBCIDIC and ASCII.
|
By "the block" I assume you mean the contents of the aforementioned Agent Buffer. You have said it is in EBCDIC and in ASCII? Can you provide more details. Perhaps even show us the contents of this buffer? I would expect it to be either in EBCIDC or in ASCII but not in both.
| vignesh1988 wrote: |
| Whatever data i pass from z/OS to Sun OS, it's going in Junk Values. |
I assume when you say "Junk Values" you are simply alluding to the fact that it is not in the code page you expect it to be in, as hinted to above.
| vignesh1988 wrote: |
| How can i transmit Data from z/OS where it reaches in the proper acceptable format and my channel gets authorized. I am sending as the same format that the partner exit expects. |
So the simple idea with a pair of Security Exits (which I assume is what you have - but please confirm this too), is that you fill in the buffer with the data that you want to be sent to the other end and the channel takes care of sending that data to the other end. This buffer is of no fixed format. You invent the format of this data when you write the pair of exits that will read and write this buffer. "No Fixed Format" includes the fact that this is not string data either. You are responsible for converting the data into the code page that will be understood by the exit at the other end of the channel. Are you doing this? Or are you just sending string data and expecting it to still be understood as string data by the exit at the other end of the channel?
Answers to all these questions will enable me to be able to help you further.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Jul 11, 2013 6:51 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
If you have Channel Security Exits on either end of a MQ Channel, and passing a Security Message between them using the protcol described in the Infocenters, MQ does not provide any conversion. The exits must agree on the format of the message. This is should be an encrypted binary format so that network sniffers can't see the payload. 
_________________
Glenn |
|
| 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
|
|
|
|
