Re: Building an API exit on Solaris
Tony, If you haven't tried it yet, I would suggest to try and setup the sample API exit. First with the binary that IBM provided, then build your own exit from the (unmodified) source. This would prove that both the MQ configuration and the compile/link process are correct. Also, exits should be written in C, so I am not sure whether compiling it as a C++ program does not cause any problems. I would think that LD_LIBRARY_PATH does not have any effect here, since /var/mqm/exits is the default directory for exits, and also you have specified the full path. Unfortunately I don't have access to a Solaris box, so I can't try out what works and what doesn't. Is the QM generating any FDC files? Peter --- Antony Boggis <[EMAIL PROTECTED]> wrote: > Thank you. > > I tried that, and it did indeed generate a binary (smaller than my previous > version!), but I still get the same error. > > Are there any issues with the value of LD_LIBRARY_PATH? > > tonyB. > > -Original Message- > Sent: Thursday 10/16/2003 12:30:32 PM > Subject: Re: Building an API exit on Solaris > > >Tony, > > > >Try something like this: > > > >CC -c -O -mt -KPIC mqAPIExit.cpp -o mqAPIExit.o > >CC -G -mt -lmqmzf -lmqm -lmqmcs -lmqmzse mqAPIExit.o -o mqAPIExit.so > > > >HTH, > >Peter > > > >--- Antony Boggis <[EMAIL PROTECTED]> wrote: > >> I am trying to get MQ to run my API exit, written in C++ (it's a hacked > >> version of the sample amqsaxe0.c). It works fine under Windows. > >> > >> I am using the following to build the .so file: > >> > >> CC -mt mqAPIExit.cpp -G -o mqAPIExit.so -lmqmzf -lmqm -lmqmcs -lmqmzse > >> > >> and no errors are generated, and the output is generated. > >> > >> I have added the following to qm.ini: > >> > >> ApiExitLocal: > >>Sequence=100 > >>Function=EntryPoint > >>Module=/var/mqm/exits/mqAPIExit.so > >>Name=mqAPIExit > >>Data=16 > >> > >> But when I try to start the qmgr I get the following: > >> > >> [EMAIL PROTECTED]:/var/mqm/trace]$ strmqm TEST > >> AMQ7214: The module '/var/mqm/exits/mqAPIExit.so' for Api Exit 'mqAPIExit' > >> could not be loaded for reason xecU_S_LOAD_FAILED. > >> > >> I have tried running an early trace, but all the trace files give me is > the > >> same return code info, so I am suspecting that my build is not good. > >> > >> Any help/comments appreciated, > >> > >> Regards, > >> > >> tonyB. > >> > >> 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 > > > >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 > > 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 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
Re: Building an API exit on Solaris
Thank you. I tried that, and it did indeed generate a binary (smaller than my previous version!), but I still get the same error. Are there any issues with the value of LD_LIBRARY_PATH? tonyB. -Original Message- Sent: Thursday 10/16/2003 12:30:32 PM Subject: Re: Building an API exit on Solaris >Tony, > >Try something like this: > >CC -c -O -mt -KPIC mqAPIExit.cpp -o mqAPIExit.o >CC -G -mt -lmqmzf -lmqm -lmqmcs -lmqmzse mqAPIExit.o -o mqAPIExit.so > >HTH, >Peter > >--- Antony Boggis <[EMAIL PROTECTED]> wrote: >> I am trying to get MQ to run my API exit, written in C++ (it's a hacked >> version of the sample amqsaxe0.c). It works fine under Windows. >> >> I am using the following to build the .so file: >> >> CC -mt mqAPIExit.cpp -G -o mqAPIExit.so -lmqmzf -lmqm -lmqmcs -lmqmzse >> >> and no errors are generated, and the output is generated. >> >> I have added the following to qm.ini: >> >> ApiExitLocal: >>Sequence=100 >>Function=EntryPoint >>Module=/var/mqm/exits/mqAPIExit.so >>Name=mqAPIExit >>Data=16 >> >> But when I try to start the qmgr I get the following: >> >> [EMAIL PROTECTED]:/var/mqm/trace]$ strmqm TEST >> AMQ7214: The module '/var/mqm/exits/mqAPIExit.so' for Api Exit 'mqAPIExit' >> could not be loaded for reason xecU_S_LOAD_FAILED. >> >> I have tried running an early trace, but all the trace files give me is the >> same return code info, so I am suspecting that my build is not good. >> >> Any help/comments appreciated, >> >> Regards, >> >> tonyB. >> >> 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 > >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 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
Re: Building an API exit on Solaris
Tony, Try something like this: CC -c -O -mt -KPIC mqAPIExit.cpp -o mqAPIExit.o CC -G -mt -lmqmzf -lmqm -lmqmcs -lmqmzse mqAPIExit.o -o mqAPIExit.so HTH, Peter --- Antony Boggis <[EMAIL PROTECTED]> wrote: > I am trying to get MQ to run my API exit, written in C++ (it's a hacked > version of the sample amqsaxe0.c). It works fine under Windows. > > I am using the following to build the .so file: > > CC -mt mqAPIExit.cpp -G -o mqAPIExit.so -lmqmzf -lmqm -lmqmcs -lmqmzse > > and no errors are generated, and the output is generated. > > I have added the following to qm.ini: > > ApiExitLocal: >Sequence=100 >Function=EntryPoint >Module=/var/mqm/exits/mqAPIExit.so >Name=mqAPIExit >Data=16 > > But when I try to start the qmgr I get the following: > > [EMAIL PROTECTED]:/var/mqm/trace]$ strmqm TEST > AMQ7214: The module '/var/mqm/exits/mqAPIExit.so' for Api Exit 'mqAPIExit' > could not be loaded for reason xecU_S_LOAD_FAILED. > > I have tried running an early trace, but all the trace files give me is the > same return code info, so I am suspecting that my build is not good. > > Any help/comments appreciated, > > Regards, > > tonyB. > > 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 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
Building an API exit on Solaris
I am trying to get MQ to run my API exit, written in C++ (it's a hacked version of the sample amqsaxe0.c). It works fine under Windows. I am using the following to build the .so file: CC -mt mqAPIExit.cpp -G -o mqAPIExit.so -lmqmzf -lmqm -lmqmcs -lmqmzse and no errors are generated, and the output is generated. I have added the following to qm.ini: ApiExitLocal: Sequence=100 Function=EntryPoint Module=/var/mqm/exits/mqAPIExit.so Name=mqAPIExit Data=16 But when I try to start the qmgr I get the following: [EMAIL PROTECTED]:/var/mqm/trace]$ strmqm TEST AMQ7214: The module '/var/mqm/exits/mqAPIExit.so' for Api Exit 'mqAPIExit' could not be loaded for reason xecU_S_LOAD_FAILED. I have tried running an early trace, but all the trace files give me is the same return code info, so I am suspecting that my build is not good. Any help/comments appreciated, Regards, tonyB. 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
