Neil,
It is true that z/OS uses different exit syntax, but MQ will automatically
convert exit names from distributed platform format into z/OS friendly
format on z/OS cluster sender channel autodefinition. The z/OS channel will
use the exit entry point or name and will also truncate to 8 characters.
For example...
"/var/mqm/exits/myExit.so(MsgExit)" converts to "MSGEXIT"
"/var/mqm/exits/myExit" converts to "MYEXIT"
"/var/mqm/exits/myExit.so(ExitLongName)" converts to "EXITLONG"
Yeah, but what do you do in the other direction? You
have only 8 characters when you alter the z/OS channel
definition.
So, you alter your (say) CLUSRCVR to by MYEXIT on the MF.
You get to the distributed side, and it's looking for a
shared library called /var/mqm/exits/MYEXIT. :-( And no
entry point; there's nothing in parentheses after MYEXIT.
So, fine, you say: I'll write a channel autodefinition
exit on the distributed side. When I do that (AIX,
Linux; MQ5.3):
a) MQCD.MsgExit is *blank*!
b) Messages in /var/mqm/qmgrs/FOO/errors/AMQERR01.LOG
say it can't dlopen /var/mqm/exits/MYEXIT
c) Even if I change MQCD.MsgExit to something else,
in the chad, like to /var/mqm/exits/libname.so(MYEXIT),
it still tries to dlopen("MYEXIT") and/or
/var/mqm/exits/MYEXIT.
Any ideas on how to deal with this? Why is my chad
ineffectual?
--
--Brian T. Shelden [EMAIL PROTECTED]
Shelden & Associates, Inc. New York, NY 10280
Certified MQSeries Specialists (212) 786-0175
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
