Dan:
You need to flag the mq stuff as 32 bit. See if the following flow
helps:
2. Keyword options:
Keyword options are specified in one of the following ways:
-q
-q=
-q=:
where is an option name and is a
parameter value.
Keyword options with no parameters represent switches
that may be either on or off. The keyword by itself turns
the switch on, and the keyword preceded by the letters NO
turns the switch off. For example, -qLIST tells the
compiler to produce a listing and -qNOLIST tells the
compiler not to produce a listing. If an option that
represents a switch is set more than once, the compiler
uses the last setting.
Keyword option and parameter names may appear in either
UPPER CASE or lower case letters in the ixlc command.
Options without parameters:
32 Selects 32-bit compiler mode.
64 Selects 64-bit compiler mode.
|-+>
| | [EMAIL PROTECTED]|
| | COM |
| | Sent by: |
| | "MQSeries List" |
| | <[EMAIL PROTECTED]|
| | n.AC.AT> |
| ||
| ||
| | 09/04/2003 03:06 |
| | PM |
| | Please respond to|
| | "MQSeries List" |
| ||
|-+>
>--|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Linking MQSeries [v5.2 in this case] into utility with 64-bit
Oracle |
|
|
>--|
Problem
Applications group has upgraded a server to AIX 5.2 [64-bit] and upgraded
Oracle to 9.2.0.4. They are now trying to relink a module that performs
MQI calls and are getting an error message that they feel is attributed to
a 64-bit vs 32-bit issue [see text below].
msp23039 was upgraded to AIX 5.2 (64 bit) last week. While linking one of
LifeCAD utilities I received following errors and on researching this
further noticed that (using nm command) /usr/lib/libmqm.a was a 32-bit
library.
With other software packages we have been able to get around such problem
by installing 64-bit version of the same package. Could you tell us what
options we have with MQ and their implications ?
(msp23039):faasupgf>make -f ora2mq.mk
/usr/vacpp/bin/xlC_r ora2mq.o -lmqm -L/usr/local/lib
-L/usr/lpp/mqm/lib -L/opt/app/oracle/product/9.2.0.4/lib -L/opt/app
/oracle/product/9.2.0.4/rdbms/lib -o ora2mq ora2mq.o -lclntsh
ld: 0711-317 ERROR: Undefined symbol: .MQCMIT
ld: 0711-317 ERROR: Undefined symbol: .MQCLOSE
ld: 0711-317 ERROR: Undefined symbol: .MQBACK
ld: 0711-317 ERROR: Undefined symbol: .MQDISC
ld: 0711-317 ERROR: Undefined symbol: .MQPUT
ld: 0711-317 ERROR: Undefined symbol: .MQOPEN
ld: 0711-317 ERROR: Undefined symbol: .MQCONN
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
information.
make: 1254-004 The error code from the last command is 8.
I reviewed the tech support website and could find no clear references to
such a problem, although I found entries for similar issues with other
products. The explanation was for MQ v5.2 and indicated 64-bit was not an
option. I did find an entry or two that referenced support packs for the
MQ Client providing 64-bit modules but nothing about the server. I also
reviewed the release paper for MQ v5.3 but didn't find much there either.
Question
What recommendations can I provide to the applications group concerning the
use of MQSeries with 64-bit apps?
Thanks in advance,
Dan Jones
Senior Systems Engineer
ING AMERICAS - Technology Management Office
IA3 - Integrated Americas Adaptive Architecture
TOMORROW. TODAY @ING
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
