MQSeries.net :: View topic

DJGoodrich · Posted: Thu Mar 20, 2003 12:06 pm Post subject:

Unable to start queue manager FMCQM, which was creating using the configuration utility.

$ strmqm FMCQM
AMQ7626: XA resource manager initialization failure. Refer to the error log for more information.

/var/mqm/qmgrs/FMCQM/errors/AMQERR01.LOG
----- amqtrmca.c : 256 --------------------------------------------------------
03/20/03 11:22:30
AMQ6188: The system could not dynamically load the shared library
'/usr/lpp/fmc/db2swit/db2swit' due to a problem with the library. The error
message was 'The system call does not exist on this system. (MQStart)'. The queue manager will continue without this library.

EXPLANATION:
This message applies to AIX systems. The shared library
'/usr/lpp/fmc/db2swit/db2swit' failed to load correctly due to a problem with the library.

ACTION:
Check that the library exists and is in the correct place with the correct file
permissions etc. and has not been corrupted. Check that the entry point
'MQStart' has been exported from the library.
----- amqxufnx.c : 703 --------------------------------------------------------
03/20/03 11:22:30
AMQ7622: WebSphere MQ could not load the XA switch load file for resource manager 'fmcinst FMCDB'.

EXPLANATION:
An error has occurred loading XA switch file /usr/lpp/fmc/db2swit/db2swit. If the error occurred during startup then the queue manager will terminate. At all other times the queue manager will continue without this resource manager meaning that it will no longer be able to participate in global transactions.
The queue manager will also retry the load of the switch file at regular
intervals so that the resource manager will be able to participate again should the load problem be resolved.
ACTION:
Look for a previous message outlining the reason for the load failure. Message AMQ6175 is issued if the load failed because of a system error. If this is the case then follow the guidance given in message AMQ6175 to resolve the problem. In the absence of prior messages or FFST information related to this problem check that the name of the switch load file is correct and that it is present in a directory from which it can be dynamically loaded by the queue manager.
The easiest method of doing this is to define the switch load file as a
fully-qualified name. Note that if the queue manager is still running it will
need to be restarted in order that any changes made to its configuration data can be picked up.
----- amqtrmca.c : 256 --------------------------------------------------------

===============================================
$ ls -l | grep usr
lrwxrwxrwx 1 bin bin 8 Dec 02 12:25 bin -> /usr/bin
lrwxrwxrwx 1 bin bin 8 Dec 02 12:25 lib -> /usr/lib
lrwxrwxrwx 1 root system 21 Dec 02 13:32 unix -> /usr/lib/boot/unix_mp
drwxr-xr-x 40 bin bin 1024 Mar 18 13:40 usr

$ ls -l | grep lpp
drwxr-xr-x 237 bin bin 6144 Mar 19 15:05 lpp

$ ls -l | grep fmc
drwxr-xr-x 36 root system 1536 Mar 18 16:34 fmc

$ ls -l | grep db2
drwxr-xr-x 2 root system 512 Mar 19 19:48 db2swit

/usr/lpp/fmc/db2swit
$ ls -l
total 56
-rwxr-xr-x 1 bin bin 1024 Nov 22 2000 db2swit
-rw-r--r-- 1 bin bin 3440 Oct 30 1997 db2swit.c
-rwxr-xr-x 1 bin bin 168 Nov 22 2000 db2swit.mak
-rw-r--r-- 1 bin bin 10942 Oct 30 1997 xa.h
-rw-r--r-- 1 bin bin 1223 May 06 1998 xaswit.mak