The channel table should contain all information necessary to create the client channel.
Likewise, the MQCONNX call should contain all information necessary to create the client channel.
You can not mix the two, without writing code to parse the (I believe undocumented structure of) the channel table. Although you could reverse engineer the code in the MQSeries perl module that lets you work with channel tables.
But that shouldn't be necessary. If you put the SSL information in the channel definitions on the server that creates the channel table, then that information will be in the channel table. As far as I know. _________________ I am *not* the model of the modern major general.
looks like I have to use only Env. variables, if i plan to use channel tables and use the MQCONN call. In this case, the SSL env variables like MQSSLKEYR would need to be set. this is just for everyones benefit...
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