Hi Brent,
Q1. Brent : Does the remote definition queue and remote local queue in this
case
need to have the same names?
A1: Of course no, (otherwise they didn't give you the option of specifying
both names !)
==============
Q2. An API error when i try to open the remote definition queue
R.TEST.TRANS1 using the MQOPEN function. Why?
API completion and reason code: MQCC_FAILED(2)
MQRC_OPTION_NOT_VALID_FOR_TYPE(2045)
A2: Take care, you cannot open a remote queue (a physical queue that
doesn't belong to the queue manager you are connected to), for message
input.
You can get messages only from local queues (queue that belong to a queue
manager that your application is connected to).
Ensure that you turn off any MQOO_INPUT_* flag in the Options parameter of
your MQOPEN call (or its equivalent in other languages than C).
================
Q3. An API error occurs when an MQPUT is done on remote definition queue
R.TEST.TRANS1. Why?
API completion and reason code: MQCC_FAILED(2) MQRC_HOBJ_ERROR(2019)
However no error occurs when a MQPUT1 is done on remote definition
queue R.TEST.TRANS1. Explanation?
A3. MQPUT1 is equivalent to a series of 3 MQI calls : MQOPEN / MQPUT /
MQCLOSE
It's used whenever the output to the concerned queue is not frequent.
However if the application have to frequently send messages to this queue,
it must call MQOPEN first to obtain a handle for the queue object.
And this handle will be used subsequently in as many MQPUT calls as you
need to execute. Finally the application when it no more needs to send
messages to the queue, it will close it using MQCLOSE.
This way and from a performance point of view, you will avoid the overhead
of executing MQOPEN/MQCLOSE for each message sent via MQPUT1.
So as you see, you must obtain a valid handle for the queue object using
MQOPEN, in order to be able to send messages via MQPUT afterthen.
Hope this helps,
Best regards,
__________________________________________________
Mountazar Abou Chrouche
Consultant, Professional Services Department
QuanTech s.a.l.
Asseily Bldg., Bloc A, Riad el-Solh Square
P.O.Box 116-5004, Beirut, Lebanon
Tel: +961 1 999 500, Ext. 154
Fax: +961 1 999 550
Mobile :+961 3 313 656
e-mail: [EMAIL PROTECTED]
__________________________________________________
Brent Ireland
<[EMAIL PROTECTED]>
Sent by: MQSeries To
List [EMAIL PROTECTED]
<[EMAIL PROTECTED] cc
n.AC.AT>
Subject
Websphere MQ for Windows
08/14/2003 09:34
PM
Please respond to
MQSeries List
<[EMAIL PROTECTED]
n.AC.AT>
Hi
I'm new to MQSeries and have a few questions i was hoping someone could
answer for me.
Websphere MQ for Windows v5.3 is installed on server.
Q1. I created a queue manager called Q51T. I also created a remote
definition queue (R.TEST.TRANS1) for a remote local
queue. The remote queue manager is called CSQT. The remote local
queue
is called L.TEST.TRANS1.
Does the remote definition queue and remote local queue in this case
need to have the same names?
Q2. An API error when i try to open the remote definition queue
R.TEST.TRANS1 using the MQOPEN function. Why?
API completion and reason code: MQCC_FAILED(2)
MQRC_OPTION_NOT_VALID_FOR_TYPE(2045)
Q3. An API error occurs when an MQPUT is done on remote definition queue
R.TEST.TRANS1. Why?
API completion and reason code: MQCC_FAILED(2) MQRC_HOBJ_ERROR(2019)
However no error occurs when a MQPUT1 is done on remote definition
queue R.TEST.TRANS1. Explanation?
Brent
CAE Inc.
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
