| Author |
Message
|
| adder |
 Posted: Mon Jan 09, 2006 12:12 am Post subject: how to know MQ6 is 32bit or 64bit |
 |
|
Apprentice
Joined: 06 Dec 2005
Posts: 43
|
hi, how can I know my MQ6 installed on AIX and solaris is 64bit or 32bit.
the cpu of my AIX is 64 bit, but kernel is 32 bit, and after I install MQ, is this MQ 32bit or 64bit, is there some command or other way to know the MQ's version |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Jan 09, 2006 12:29 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| AFAIK, MQv6 can only be 64 bit on AIX and Solaris platforms. |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Jan 09, 2006 7:35 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Yes, only 64 bits on AIX, Solaris, HP-UX and Linux/pSeries.
Aside from general curiosity, is it important? Those qmgr will still work with 32 bit programs and exits.
EDIT: seeing your duplicate post, let me add that 32-bit exits should go in /var/mqm/exits and 64-bit exits in /var/mqm/exits64
_________________
-wayne |
|
| Back to top |
|
|
| adder |
| Posted: Mon Jan 09, 2006 11:56 pm Post subject: |
|
|
Apprentice
Joined: 06 Dec 2005
Posts: 43
|
thanks!
oh, really, only 64bit MQ6 exist on solaris and AIX, so If I want to 32 bit MQ, then I need install MQ5.3. |
|
| Back to top |
|
|
| Philip Morten |
| Posted: Tue Jan 10, 2006 1:56 am Post subject: |
|
|
Master
Joined: 07 Mar 2002
Posts: 230
Location: Hursley Park
|
| Quote: |
| oh, really, only 64bit MQ6 exist on solaris and AIX, so If I want to 32 bit MQ, then I need install MQ5.3. |
Yes, but why would you need to? In V.6 the queue manager runs in 64-bit mode but applications can be 32-bit or 64-bit.
_________________
Philip Morten
The postings on this site are my own and do not necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| adder |
| Posted: Wed Jan 11, 2006 7:24 am Post subject: |
|
|
Apprentice
Joined: 06 Dec 2005
Posts: 43
|
thanks!
beacuse we need write exit to extend MQ, so for 64bit MQ, exit must be 64-bit mode, for 32bit MQ, exit must be 32-bit mode, right?
| Philip Morten wrote: |
| Quote: |
| oh, really, only 64bit MQ6 exist on solaris and AIX, so If I want to 32 bit MQ, then I need install MQ5.3. |
Yes, but why would you need to? In V.6 the queue manager runs in 64-bit mode but applications can be 32-bit or 64-bit. |
|
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jan 11, 2006 7:36 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
No, a 64 bit MQ can still use a 32 bit exit...
| Quote: |
EDIT: seeing your duplicate post, let me add that 32-bit exits should go in /var/mqm/exits and 64-bit exits in /var/mqm/exits64
|
_________________
-wayne |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jan 11, 2006 7:51 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
|
| Back to top |
|
|
| hal |
| Posted: Wed Jan 11, 2006 1:11 pm Post subject: |
|
|
Acolyte
Joined: 07 Dec 2005
Posts: 67
Location: New York City, New York
|
I am running a 64-bit version of WebSphere MQ V6.0.1 and a 32-bit version of WebSphere Message Broker V6 on a Solaris platform. IBM support told me that Hursley has not released 64-bit broker components.
The only way that I could get my API exit handlers to work was to build 64-bit versions in /var/mqm/exits64 and 32-bit versions in /var/mqm/exits.
Are there supposed to be duplicate 64-bit and 32-bit ApiExitLocal stanzas in the queue manager's qm.ini file?
When my qm.ini contained only the 64-bit ApiExitLocal entry,
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
ExitsDefaultPath64=/var/mqm/exits64/
ApiExitLocal:
Name=mirrorq
Function=EntryPoint
Module=/var/mqm/exits64/mirrorq
Data=MIRRORQ
Sequence=100
WebSphere 32-bit executables (bipbroker, bipconfigmgr, bipuns, saveqmgr, etc.) generated warning messages in the queue manager logs:
-------------------------------------------------------------------------------
01/11/06 03:10:24 PM - Process(4366.1) User(mqm) Program(bipbroker)
AMQ6254: The system could not dynamically load the shared library
'/var/mqm/exits64/mirrorq', library '/var/mqm/exits/mirrorq' has been used
instead.
EXPLANATION:
This message applies to UNIX systems. The shared library
'/var/mqm/exits64/mirrorq' failed to load as it is probably a 64-bit library, a
32-bit library is required. Note that MQ has sucessfully located and loaded a
32-bit library named '/var/mqm/exits/mirrorq'.
ACTION:
Supply the name of a 32-bit library or put the library (alternatively a
symbolic link can be used) in the appropriate place: 32-bit libraries in
/var/mqm/exits; 64-bit libraries in /var/mqm/exits64.
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
01/11/06 03:10:37 PM - Process(4383.1) User(mqm) Program(saveqmgr)
AMQ6254: The system could not dynamically load the shared library
'/var/mqm/exits64/mirrorq', library '/var/mqm/exits/mirrorq' has been used
instead.
EXPLANATION:
This message applies to UNIX systems. The shared library
'/var/mqm/exits64/mirrorq' failed to load as it is probably a 64-bit library, a
32-bit library is required. Note that MQ has sucessfully located and loaded a
32-bit library named '/var/mqm/exits/mirrorq'.
ACTION:
Supply the name of a 32-bit library or put the library (alternatively a
symbolic link can be used) in the appropriate place: 32-bit libraries in
/var/mqm/exits; 64-bit libraries in /var/mqm/exits64.
-------------------------------------------------------------------------------
So I added a 32-bit stanza to my qm.ini:
ApiExitLocal:
Name=mirrorq
Function=EntryPoint
Module=/var/mqm/exits/mirrorq
Data=MIRRORQ
Sequence=102
After recycling the queue manager and message broker components the 32-bit log warnings disappeared. Now whenever I start up 64-bit WebSphere applications I get these warning messages:
-------------------------------------------------------------------------------
01/11/06 03:35:02 PM - Process(5648.1) User(mqm) Program(strmqm)
AMQ6254: The system could not dynamically load the shared library
'/var/mqm/exits/mirrorq', library '/var/mqm/exits64/mirrorq' has been used
instead.
EXPLANATION:
This message applies to UNIX systems. The shared library
'/var/mqm/exits/mirrorq' failed to load as it is probably a 32-bit library, a
64-bit library is required. Note that MQ has sucessfully located and loaded a
64-bit library named '/var/mqm/exits64/mirrorq'.
ACTION:
Supply the name of a 64-bit library or put the library (alternatively a
symbolic link can be used) in the appropriate place: 32-bit libraries in
/var/mqm/exits; 64-bit libraries in /var/mqm/exits64.
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
01/11/06 03:35:02 PM - Process(5698.1) User(mqm) Program(runmqtrm)
[img]AMQ6254[/img]: The system could not dynamically load the shared library
'/var/mqm/exits/mirrorq', library '/var/mqm/exits64/mirrorq' has been used
instead.
EXPLANATION:
This message applies to UNIX systems. The shared library
'/var/mqm/exits/mirrorq' failed to load as it is probably a 32-bit library, a
64-bit library is required. Note that MQ has sucessfully located and loaded a
64-bit library named '/var/mqm/exits64/mirrorq'.
ACTION:
Supply the name of a 64-bit library or put the library (alternatively a
symbolic link can be used) in the appropriate place: 32-bit libraries in
/var/mqm/exits; 64-bit libraries in /var/mqm/exits64.
------------------------------------------------------------------------------- |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jan 11, 2006 3:50 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Hi Hal.... I think you would simply say:
since both exits are in the default paths, there should be no need to specify the path in the stanza.
_________________
-wayne |
|
| Back to top |
|
|
| hal |
| Posted: Thu Jan 12, 2006 6:17 am Post subject: |
|
|
Acolyte
Joined: 07 Dec 2005
Posts: 67
Location: New York City, New York
|
Thanks Wayne! That worked.
From the Info Center's Configuring API exits section:
"Module=module_name
The module containing the API exit code.
If this field contains the full path name of the module it is used as is.
If this field contains just the module name, the module is located using the ExitsDefaultPath attribute in the ExitPath in qm.ini.
The length of this field is limited to the maximum path length the platform supports." |
|
| Back to top |
|
|
|
|
