| Author |
Message
|
| lium |
 Posted: Wed Jan 08, 2014 12:49 pm Post subject: same installation image for both 32 bit and 64 bit? |
 |
|
Disciple
Joined: 17 Jul 2002
Posts: 184
|
We want to go with 64 bit queue manager.
From IBM partner site, there does not seem to be a x64 specific MQ image for windows.
So I am wondering if it is the same image supports both 32 and 64 bit versions of windows?
If yes, how to specify 64 bit queue manager? Through path?
Tx |
|
| Back to top |
|
 |
| mqsiuser |
| Posted: Thu Jan 09, 2014 12:42 am Post subject: Re: same installation image for both 32 bit and 64 bit? |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
For IIB it is
"x86" (32 bit version)
"x86-64" (64 bit version)
There should be 2 different versions, I do not think that they are provided in one bundle !
Though you can typically install 32-bit software on 64 bit OSes, but you then have (memory) limitations.
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Jan 09, 2014 1:02 am Post subject: Re: same installation image for both 32 bit and 64 bit? |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mqsiuser wrote: |
For IIB it is
"x86" (32 bit version)
"x86-64" (64 bit version)
There should be 2 different versions, I do not think that they are provided in one bundle !
Though you can typically install 32-bit software on 64 bit OSes, but you then have (memory) limitations. |
For WMQ there is only one installation package...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| lium |
| Posted: Thu Jan 09, 2014 1:56 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2002
Posts: 184
|
Hmmm, Seems like I got different answers for the same question.
The issues: from the IBM partner site, we don't find installation image which says explicitly it is 64 bit.
Also, during the installation procedure, it never says if it is 32 bit or 64 bit.
Does windows only support 32 bit?
if not, how to get the 64 bit image and install that? |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Thu Jan 09, 2014 2:10 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
Sorry, I was wrong, exerk is right.
I guess the installation will likely install the right version  (would make sense, doesn't it?).
To find out how many bits (32, 64) the OS is, search google.
To verify that MQ is installed with the proper version (32, 64) do a "dspmqver" after the installation:
| Code: |
...
Mode: 64-bit
... |
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| Philip Morten |
| Posted: Thu Jan 09, 2014 2:29 am Post subject: Re: same installation image for both 32 bit and 64 bit? |
|
|
Master
Joined: 07 Mar 2002
Posts: 230
Location: Hursley Park
|
| lium wrote: |
We want to go with 64 bit queue manager.
From IBM partner site, there does not seem to be a x64 specific MQ image for windows.
So I am wondering if it is the same image supports both 32 and 64 bit versions of windows?
If yes, how to specify 64 bit queue manager? Through path?
Tx |
There is no 64-bit Queue Manager on Windows, the Windows installation package will install on either 32- or 64-bit Windows and on a 64-bit system will support both 32- and 64-bit applications but in all cases the Queue Manager will run 32-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 |
|
|
| mqsiuser |
| Posted: Thu Jan 09, 2014 3:41 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| mqsiuser wrote: |
To verify that MQ is installed with the proper version (32, 64) do a "dspmqver" after the installation:
| Code: |
...
Mode: 64-bit
... |
|
Ok, so for Windows this then is always "32-bit" (I issued the command on Linux).
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| lium |
| Posted: Thu Jan 09, 2014 7:33 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2002
Posts: 184
|
Thanks for reply.
If there is no 64 bit queue manager on windows, but why the qmgr on windows has exits and exits64 folder for the XA |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Jan 09, 2014 7:35 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| lium wrote: |
| ...but why the qmgr on windows has exits and exits64 folder for the XA |
See Philip Morten's post above.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| lium |
| Posted: Thu Jan 09, 2014 7:42 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2002
Posts: 184
|
The following is xaswit.mak from windows. It mentioned 32 and 64 etc.
#
# Name: XASWIT.MAK
#
# Description: Windows NT makefile for DB2, Oracle, Informix and Sybase XA switch load files
#
# <copyright
# notice="lm-source-program"
# pids="5724-H72,"
# years="1996,2012"
# crc="4293609679" >
# Licensed Materials - Property of IBM
#
# 5724-H72,
#
# (C) Copyright IBM Corp. 1996, 2012
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with
# IBM Corp.
# </copyright>
#
# To make the DB2 XA switch load file, run the command:-
# nmake -f xaswit.mak db2swit.dll
#
# To make the DB2 XA Static Registration switch load file, run the command:-
# nmake -f xaswit.mak db2swits.dll
#
# To make the Sybase XA switch load file, run the command:-
# nmake -f xaswit.mak sybswit.dll
#
# To make the Oracle XA switch load file, run the command:-
# nmake -f xaswit.mak oraswit.dll
#
# To make the Oracle XA Dynamic Registration switch load file, run the command:-
# nmake -f xaswit.mak oraswitd.dll
#
# To make the Informix XA switch load file, run the command:-
# nmake -f xaswit.mak infswit.dll
#
# Note: The above commands will build a debug version of the switch load files,
# to build a non-debug version invoke nmake with the nodebug=1 argument,
# for example:-
# nmake nodebug=1 -f xaswit.mak db2swit.dll
#
# Note: To build a 32-bit switch load file you can set the appropriate environment
# by issuing: 'vcvarsall x86'; to build a 64-bit switch load file issue:
# 'vcvarsall amd64'. Ensure the environment variable 'CPU' is either unset
# or set to 'i386' when building the 32-bit switch load file and set to
# 'AMD64' when building the 64-bit switch load file.
#
# Note: When building both the 32-bit and 64-bit switch load files delete the
# old .obj and .lib files or use the -a argument, for example:-
# nmake nodebug=1 -a -f xaswit.mak db2swit.dll
#
# Note: If your database library has a different name, or is on a different
# drive, or is in a different directory to the one listed in the xxxLIBPATH
# statement, you will need to alter that statement.
#
!include <ntwin32.mak>
!if (defined(PROCESSOR_ARCHITEW6432) || "$(PROCESSOR_ARCHITECTURE)" == "AMD64")
MQ_DEFAULT_INSTALLATION_PATH=C:\Program Files (x86)\IBM\WebSphere MQ
MQ_DEFAULT_DATA_PATH=C:\Program Files (x86)\IBM\WebSphere MQ
!else
MQ_DEFAULT_INSTALLATION_PATH=C:\Program Files\IBM\WebSphere MQ
MQ_DEFAULT_DATA_PATH=C:\Program Files\IBM\WebSphere MQ
!endif
#-------------------------------------------------------------------------------
# If the default MQ/DB2/Informix installation directory has not been overridden,
# work it out.
#
# The default product install location differs depending on whether the
# operating system is 32-bit or 64-bit. We can determine this because on 64-bit
# operating systems, either PROCESSOR_ARCHITEW6432 is defined, or
# PROCESSOR_ARCHITECTURE is set to AMD64.
#
# The PROCESSOR_ARCHITECTURE environment variable being set to AMD64 indicates
# that a 64-bit compiler is in use. If this is the case, we build to the 64-bit
# exits directory (exits64) as opposed to the 32-bit one (exits).
#
# Note: If you have installed MQ/DB2/Informix into a different location to the
# default, or otherwise want to override the location to which the product
# exit is built, you can do so by setting the appropriate macro, either on
# the command line, or before this point in the make file.
#
#-------------------------------------------------------------------------------
MQ_INSTALLATION_PATH=$(MQ_DEFAULT_INSTALLATION_PATH)
MQ_DATA_PATH=$(MQ_DEFAULT_DATA_PATH)
!if !defined(MQEXITDIR)
!if ("$(PROCESSOR_ARCHITECTURE)" != "AMD64")
MQEXITDIR="$(MQ_DATA_PATH)\exits"
!else
MQEXITDIR="$(MQ_DATA_PATH)\exits64"
!endif
!endif
!if !defined(DB2LIBPATH)
!if (defined(PROCESSOR_ARCHITEW6432) || "$(PROCESSOR_ARCHITECTURE)" == "AMD64")
!if ("$(PROCESSOR_ARCHITECTURE)" != "AMD64")
DB2LIBPATH="C:\Program Files\IBM\SQLLIB\lib\Win32"
!else
DB2LIBPATH="C:\Program Files\IBM\SQLLIB\lib"
!endif
!else
DB2LIBPATH="C:\Program Files\IBM\SQLLIB\lib"
!endif
!endif
!if !defined(INFLIBPATH)
!if (defined(PROCESSOR_ARCHITEW6432) || "$(PROCESSOR_ARCHITECTURE)" == "AMD64")
!if ("$(PROCESSOR_ARCHITECTURE)" != "AMD64")
INFLIBPATH="C:\IBM\Informix\Client-SDK\32-bit\lib"
!else
INFLIBPATH="C:\IBM\Informix\Client-SDK\64-bit\lib"
!endif
!else
INFLIBPATH="C:\Program Files\Informix\Client-SDK\lib"
!endif
!endif
# Uncomment only one set of ORALIBPATH statements
# Note the first default database instance Oracle creates has been used (db_1)
# for the following releases of Oracle, this may need changing if this instance
# name does not exist in the Oracle release sub directory.
!if !defined(ORALIBPATH)
!if (defined(PROCESSOR_ARCHITEW6432) || "$(PROCESSOR_ARCHITECTURE)" == "AMD64")
!if ("$(PROCESSOR_ARCHITECTURE)" != "AMD64")
# The following line is for Oracle 10gR1
# ORALIBPATH="C:\oracle\product\10.1.0\client_1\RDBMS\XA"
# The following line is for Oracle 10gR2
ORALIBPATH="C:\oracle\product\10.2.0\client_1\RDBMS\XA"
# The following line is for Oracle 11gR1
# Note UserId will be the user identifier for the user which installed Oracle
# ORALIBPATH="C:\app\UserId\product\11.1.0\client_1\RDBMS\XA"
!else
# The following line is for Oracle 10gR1
# ORALIBPATH="C:\oracle\product\10.1.0\db_1\RDBMS\XA"
# The following line is for Oracle 10gR2
ORALIBPATH="C:\oracle\product\10.2.0\db_1\RDBMS\XA"
# The following line is for Oracle 11gR1
# Note UserId will be the user identifier for the user which installed Oracle
# ORALIBPATH="C:\app\UserId\product\11.1.0\db_1\RDBMS\XA"
!endif
!else
# The following line is for Oracle 10gR1
# ORALIBPATH="C:\oracle\product\10.1.0\db_1\RDBMS\XA"
# The following line is for Oracle 10gR2
ORALIBPATH="C:\oracle\product\10.2.0\db_1\RDBMS\XA"
# The following line is for Oracle 11gR1
# Note UserId will be the user identifier for the user which installed Oracle
# ORALIBPATH="C:\app\UserId\product\11.1.0\db_1\RDBMS\XA"
!endif
!endif
#-------------------------------------------------------------------------------
# DB2 XA switch load file
#-------------------------------------------------------------------------------
DB2LIBS=db2api.lib
DB2LIBFLAGS=$(DB2LIBPATH)\$(DB2LIBS)
db2swit.lib db2swit.exp: $*.obj $*.def
$(implib) -machine:$(CPU) \
-def:$*.def $*.obj
$(MQEXITDIR)\db2swit.dll: $*.obj $*.def $*.exp
$(link) $(dlllflags) \
-base:0x1C000000 \
$*.exp $*.obj \
-out:$(MQEXITDIR)\db2swit.dll \
$(conlibsdll) $(DB2LIBFLAGS)
if exist $(MQEXITDIR)\db2swit.dll.manifest \
mt.exe -manifest $(MQEXITDIR)\db2swit.dll.manifest \
-outputresource:$(MQEXITDIR)\db2swit.dll;#2
#-------------------------------------------------------------------------------
# DB2 XA Static Registration switch load file
#-------------------------------------------------------------------------------
db2swits.lib db2swits.exp: $*.obj $*.def
$(implib) -machine:$(CPU) \
-def:$*.def $*.obj
$(MQEXITDIR)\db2swits.dll: $*.obj $*.def $*.exp
$(link) $(dlllflags) \
-base:0x1C000000 \
$*.exp $*.obj \
-out:$(MQEXITDIR)\db2swits.dll \
$(conlibsdll) $(DB2LIBFLAGS)
if exist $(MQEXITDIR)\db2swits.dll.manifest \
mt.exe -manifest $(MQEXITDIR)\db2swits.dll.manifest \
-outputresource:$(MQEXITDIR)\db2swits.dll;#2
#-------------------------------------------------------------------------------
# Sybase XA switch file
#-------------------------------------------------------------------------------
# Uncomment only one pair of SYBLIBS/SYBLIBPATH statements
# The following line is for Sybase 12.5
# SYBLIBS=libxadtm.lib
# SYBLIBPATH=C:\sybase\OCS-12_5\lib
# The following line is for Sybase 15
SYBLIBS=libsybxadtm.lib
SYBLIBPATH=C:\sybase\OCS-15_0\lib
SYBLIBFLAGS=$(SYBLIBPATH)\$(SYBLIBS)
sybswit.lib sybswit.exp: $*.obj $*.def
$(implib) -machine:$(CPU) \
-def:$*.def $*.obj
$(MQEXITDIR)\sybswit.dll: $*.obj $*.def $*.exp
$(link) $(dlllflags) \
-base:0x1C000000 \
$*.exp $*.obj \
-out:$(MQEXITDIR)\sybswit.dll \
$(conlibsdll) $(SYBLIBFLAGS)
if exist $(MQEXITDIR)\sybswit.dll.manifest \
mt.exe -manifest $(MQEXITDIR)\sybswit.dll.manifest \
-outputresource:$(MQEXITDIR)\sybswit.dll;#2
#-------------------------------------------------------------------------------
# Oracle XA switch load file
#-------------------------------------------------------------------------------
# Uncomment only one ORALIBS statement
# The following line is for Oracle 9
# ORALIBS=oraxa9.lib
# The following line is for Oracle 10
# ORALIBS=oraxa10.lib
# The following line is for Oracle 11
ORALIBS=oraxa11.lib
ORALIBFLAGS=$(ORALIBPATH)\$(ORALIBS)
oraswit.lib oraswit.exp: $*.obj $*.def
$(implib) -machine:$(CPU) \
-def:$*.def $*.obj
$(MQEXITDIR)\oraswit.dll: $*.obj $*.def $*.exp
$(link) $(dlllflags) \
-base:0x1C000000 \
$*.exp $*.obj \
-out:$(MQEXITDIR)\oraswit.dll \
$(conlibsdll) $(ORALIBFLAGS)
if exist $(MQEXITDIR)\oraswit.dll.manifest \
mt.exe -manifest $(MQEXITDIR)\oraswit.dll.manifest \
-outputresource:$(MQEXITDIR)\oraswit.dll;#2
#-------------------------------------------------------------------------------
# Oracle XA Dynamic Registration switch load file
#-------------------------------------------------------------------------------
oraswitd.lib oraswitd.exp: $*.obj $*.def
$(implib) -machine:$(CPU) \
-def:$*.def $*.obj
$(MQEXITDIR)\oraswitd.dll: $*.obj $*.def $*.exp
$(link) $(dlllflags) \
-base:0x1C000000 \
$*.exp $*.obj \
-out:$(MQEXITDIR)\oraswitd.dll \
$(conlibsdll) $(ORALIBFLAGS)
if exist $(MQEXITDIR)\oraswitd.dll.manifest \
mt.exe -manifest $(MQEXITDIR)\oraswitd.dll.manifest \
-outputresource:$(MQEXITDIR)\oraswitd.dll;#2
#-------------------------------------------------------------------------------
# Informix XA switch load file
#-------------------------------------------------------------------------------
INFLIBS=isqlt09a.lib
INFLIBFLAGS=$(INFLIBPATH)\$(INFLIBS)
infswit.lib infswit.exp: $*.obj $*.def
$(implib) -machine:$(CPU) \
-def:$*.def $*.obj
$(MQEXITDIR)\infswit.dll: $*.obj $*.def $*.exp
$(link) $(dlllflags) \
-base:0x1C000000 \
$*.exp $*.obj \
-out:$(MQEXITDIR)\infswit.dll \
$(conlibsdll) $(INFLIBFLAGS)
if exist $(MQEXITDIR)\infswit.dll.manifest \
mt.exe -manifest $(MQEXITDIR)\infswit.dll.manifest \
-outputresource:$(MQEXITDIR)\infswit.dll;#2
#-------------------------------------------------------------------------------
.c.obj:
$(cc) $(cflags) $(cvarsdll) $*.c |
|
| Back to top |
|
|
| lium |
| Posted: Thu Jan 09, 2014 7:49 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2002
Posts: 184
|
Thanks for the reply.
In the installation image, I also find IBM WebSphere MQ 64bitSupport.msi.
I am wondering what is that for? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jan 09, 2014 8:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Read Phillip Morten's response again.
Carefully.
Remember that a queue manager IS NOT a single process. It is a distinct set of processes.
Remember that an application using a queue manager DOES NOT share the same runtime context as any of the queue manager processes. (Unless you use FASTPATH bindings. Please don't use FASTPATH bindings.) |
|
| Back to top |
|
|
| lium |
| Posted: Thu Jan 09, 2014 11:03 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2002
Posts: 184
|
Thanks a lot for everybody.
I really appreciate that. |
|
| Back to top |
|
|
| imageat |
| Posted: Fri May 30, 2014 12:17 am Post subject: |
|
|
Newbie
Joined: 30 May 2014
Posts: 2
|
thanks, appreciate the help  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri May 30, 2014 5:09 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| imageat wrote: |
| thanks, appreciate the help |
Before you get too happy, read the what's new in WMQ V 8.
There now is a 64 bit version of WMQ for windows... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
