Is the queue you are querying a local or alias queue? I think you would
get this error if you inquire on CurrentDepth for a remote queue.
- Steve
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of David
Kendall
Sent: Friday, May 14, 2004 11:05 AM
To: [EMAIL PRO
Title: Using Candle UA from .NET
Apologies for the slightly off-topic post.
Has anyone successfully used Candle's Universal Agent Data Provider API from a .NET program (C# or VB.NET)?
I'm trying to write a service that goes out an periodically "pings" our queue managers and then report th
bobbee -
Let me ask the obvious question: Did you specify the MessageType in
your MQInput node? Even with just one message defined to the Message
Set, I think you still need to specify the MessageType, either via the
MQInput node or via an RFH2 header on the message.
- Steve
P.S. I assume the
Gary -
A point of clarification. The VB client uses mqic32.dll (not mqic.dll).
The mqicstd.dll is from the old VB support pac from the days before VB
support was officially added into the product (V5.1 I think). Assuming
that you are using a V5.1 or later client, then you will not need (or
find
Bill -
When using the standard MQI with VB, as opposed to the ActiveX classes,
you must indicate whether you want to compile with the server dll
(mqm.dll) or client dll (mqic32.dll). You do this via a conditional
compilation variable.
Open up the project properties dialog box ( Project | {nam
Title: Message
Peter
-
Is the
userid that the ConfigMgr NT Service runs under (mqsiuid in your example) a
member of the "administrators" group on the server? I seem to
recall getting this error if it is not.
-
Steve
-Original Message-From: MQSeries List
[mailto:[EMAIL PRO
Joan -
For us, we had two main reasons for going to V5.3 (in Windows). The first was the
generic security. The second was the Terminal Server support (we went to V5.3 as part
of our migration from WinNT to Win2K).
- Steve
P.S. It has also been more stable (especially with CSD05).
-O
Jeff -
What version of MQ are you running on your XP desktop? If it is not
V5.3 CSD01 or greater, then perhaps that is causing your problems.
- Steve Gies
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Jeff A
Tressler
Sent: Friday, January 09, 2004 11:
Gaurav -
I would suggest using a single Output node with the Destination Mode set
to DestinationList. Then, in a preceding Compute node, determine which
queue and queue manager the message belongs on and set the
DestinationList in the LocalEnvironment as follows:
SET
OutputLocalEnvironment.De
I assume you are looking to create some sort of monitoring app that will
alert you if queue X has not received a message in N minutes. If this
is the case, you might look into the RESET QSTATS command (See the
Command Reference for details). If you create a program that sends a
RESET QSTATS (queu
Bob -
I assume that what you are looking for is a way to turn off all IMS or
CICS triggering at this time and turn it back on again later. One
solution is to turn triggering off on each application via a batch job.
The downside of this is that if you've got lots of application queues
using trigg
Jeff -
The answer depends on what GMO options the receiving application is
using. If it uses MQGMO_ALL_MSGS_AVAILABLE, then a restart of the app
will not pick up the remaining messages from the groups -since some of
the messages are missing. If MQGMO_LOGICAL_ORDER is used, then this
will also f
Darren -
Yes. We got this error on a server that hosted multiple, test queue
managers. What turned out to be the problem is one of the admin folks
wrote a little command file to refresh the security on each queue
managers (basically ran a runmqsc command and piped in a file with
REFRESH SECURIT
Title: CA Monitoring Agents for MQ
We are looking at the possibility of replacing our current MQ monitoring solution with Unicenter Management for MQSeries (on Windows 2000) and SysView E WebSphere MQ Option (on z/OS) feeding into a Unicenter console. The reasoning behind this move is to con
Dave -
We have found that the NT Client trigger monitor does not properly handle
path definitions that contain spaces (i.e. C:\Program Files\My Program
Dir\My Program.exe). This has to be specified using the "DOS" path (i.e.
C:\PROGRA~1\MYPROG~1\MYPROG~1.EXE). I'm not sure if the server version
Ruzi -
I think you are on the right track here. A couple of points:
If possible (and this is really desirable) have all queues for a given
application start with the same app code. For example, in our shop, all
queues start with a three char application code followed by a period. For
example:
Andrew -
To force MQAX200 to use the client dll set the following environmental
variable:
GMQ_MQ_LIB = C:\Program Files\IBM\WebSphere MQ\bin\mqic32.dll
(Note: the path may be different depending on what version of MQ you are
using and what drive you installed on).
To go back to the server ver
buffer size on a PUT. What size do you
recommend?
Thanks again.
Elena.
"GIES, STEVE" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 06/03/2003 01:55:38 PM
Please respond to MQSeries List <[EMAIL PROTECTED]>
Sent by:MQSeries List <[EMAIL PROTECTED]>
To:[EMAIL
Elena -
This is a known bug in the current .NET support pac. What is happening is
that by default the MQQueue class attempts to get the message with a 1 byte
buffer. This of course fails (unless you just happen to be passing a 1 or 0
byte message!!) with a truncation failure. The class then res
Title: Message
We got
hit by this. We never got hit in dev either (and still haven't) but we've
had three incidents in the past 6 weeks were a queue was damaged. Both of
the queues involved (1 has been damaged twice) have a high number of abandoned
reply messages on them that get cleaned out n
Peter -
You need to create the Blocking value using a tool like regedit. It is not
created by any of the MQ Admin GUIs or commands. (Although you could use
amqmdain to create this value.)
We had the same problem as Cynthia report, but only on our 5.2 CSD05 WinNT
machines. Adding this registry
Sorry to disappoint, but I'm fairly certain that this new feature is OS/390
version only. It was implement to clean up shared queues in the coupling
facility. I don't think it was implemented in the distributed code base.
- Steve Gies
-Original Message-
From: Jim Ford [mailto:[EMAIL PRO
Jim -
Out of curiosity: Are these persistent messages? Are they relatively large?
I would expect that the actual, physical deletion of a persistent, expired
message would require the same logging overhead as any "normal" MQGET of the
same persistent message. If you are deleting a large volume of
Lizette -
I assume you are using WinNT or Win2000 and MQ v5.2:
>From a command prompt type DCOMCNFG.
In the dialog box that pops up, select IBM MQSeries Services, click the
Properties button.
In the properties sheet, select the Identity tab. From here you can change
the id under which the MQSeri
Richard
Try using this code instead:
strcpy(mqcd.MCAUserIdentifier, "mqm");
- Steve Gies
-Original Message-
From: Richard Killian [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 25, 2002 11:23 AM
To: [EMAIL PROTECTED]
Subject: channel security exit
I have another question related
Title: Channels out of sync - MQ5.2 OS/390
Pieter
-
This
problem may have nothing to do with the SYNCQ. You mentioned distributed
QMGR's in your email. We have experience several Msg Sequence errors ever
since we upgraded our NT V5.2 servers to CSD05. Apparently the receive
socket call was c
Dave -
A common "gotcha" with triggering on FIRST is the rule that the triggered
queue cannot be opened for input in order for a trigger message to be
generated. The presumption being that whatever has the queue open for input
is going to process off any messages on the queue.
So, if your progra
Peter -
You might want to consider your question from the other angle - what reason
codes, returned from the MQCONN call, are acceptable to use the queue
manager you are attempting to connect to. The answer, of course, is
(MQRC-NONE) and possibly 2002 (MQRC-ALREADY-CONNECTED). In all other
David -
This is correct. The MQMessage class Write* methods provide support for
data-conversion while the native MQPUT api call does not. This primarily to
support the conversion from Unicode (required by the ActiveX Classes) to the
native code page of the queue manager. However, as you've disc
This is another victim of CSD03. I got the following reply from IBM
Support:
There is a known issue with supportpac IC01 at CSD03; this is being
addressed by apar IC34712. The fix for the problem is inclusion of the
connector.jar file path in the classpath variable of the
Hi Peter -
Option 3 is your answer. Q1 and Q2 will trigger independent of each other.
The fact that they use the same process definition, and therefore trigger
the same transaction is immaterial. As far as processing the transaction is
concerned, if the tran is defined to multiple message region
Title: Message
Wendy
-
I
assume you mean you upgraded to WMQI V2.1 with CSD03. If so, contact IBM to get
APAR IC34470 which fixes the frozen message set problem.
-
Steve
-Original Message-From: wendy.dlamini
[mailto:[EMAIL PROTECTED]] Sent: Monday, October 07, 2002
11:22 PMTo: [E
Your thoughts are correct. When the queue manager restarts, MQSeries scans
any queues that have message in them (persistent messages of course) and
checks to see if the queue is triggered. If it is, then a trigger message is
sent to the initiation queue. This is true for all triggered queues (at
Yes,
of course your application folks won't trust the opinions of the MQSeries
experts within their own company (or consultants that their company as
hired). But strangers off the Internet - they must know what their talking
about!!!
-
Steve
-Original Message-From: Michael F
Mu
Dave -
One thing that can be confusing is that some message browser utilities will
automatically convert the putdate/time from GMT to the local time. Most
notably the MQExplorer that comes with MQ-NT will do this. If you are using
the ISPF Message Browser from MA10 to view the queues on the OS3
Title: Message
Mike -
We've
never added the channels as their own service under the snap-in, just the
channel initiator (which of course is added via the install of MQ). All of
our channels are triggered via the transmission queue. This works just
fine. Inactive channels start when message
Hello Listers -
I've come across a problem this morning that I'm hoping someone can shed
some light on.
We have a test server that has three queue managers installed that all use
linear logging. The server is WinNT V4 SP6a and MQSeries is V5.2 w/ CSD03
installed.
Every night we run a job that
Title: C++ Foundation Classes
Pieter
-
No, if
connectively is lost sometime between the internal MQCONN call and the MQPUT
call, you will get back an appropriate error message - 2002? - but the classes
will not attempt to redrive the put call.
-
Steve
-Original Message-From: Voges
Andre -
I'm fairly certain that this is the same issue as with Terminal Server on
Windows 2000. To run your app using Citrix you will need to set it up as a
client application. Ensure that you have the client code installed on the
server (if not, install this from the server CD, not the client
Title: Message
It
appears that you are using the MQSeries C++ Classes as well. There is a
class the encapsulates the IIH called ImqIMSBridgeHeader. Since this is
derived from the ImqHeader class, which is derived from the ImqItem class, you
can use the WriteItem method to add the header to you
Jessie -
I had this problem once. The only way that I could think of to find out who
was attempting to make the connection was to actually create the server-conn
channel with a security exit that logged the attributes from the Channel
Descriptor. It also denied the connection.
- Steve Gies
---
Paul -
There is a mqsiassign command in ic01. I have not used this myself, but it
appears to do what you are asking for.
- Steve Gies
-Original Message-
From: Paul Dix [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 11, 2002 1:34 PM
To: [EMAIL PROTECTED]
Subject: MQSI 2.1 Change Mgmt Is
Rick -
Actually, you can use the MQ Service snap-in remotely. From the MQ Service
MMC console on your PC (or any MMC console) select Console | Add/Remove
Snap-In... On the Add/Remove Snap-in dialog box click the Add button and
then select the MQSeries Services snap-in from the list. It will pro
Rick -
It sounds like you are logged onto your Win2K server via Terminal Services.
When you do this, you can use the MQ Services MMC as normal, but to use the
MQ Explorer MMC you must connect to the queue manager as a client. (Right
click Queue Managers, select Show Queue Manager ..., select the
Tony -
Check out support pac IC01. It provides a batch command for exporting and
importing message flows in WMQI V2.1.
- Steve
-Original Message-
From: Tony Devitt [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31, 2002 10:07 PM
To: [EMAIL PROTECTED]
Subject: MQSI - Exporting/Importing Me
Joshi -
Couple of things. First, by not setting the mqgmo.Options =
MQGMO_BROWSE_NEXT anymore you are doing destructive gets against your queue
not browse gets. Secondly, you are checking the CompletionCode of your
mqgmo object. I think you want to check the mqq object. This is the object
tha
Title: Message
Joshi
-
I
suspect that once you get the first message, the MessageId and CorrelationId in
the MQMessage object are set and are used as filters for subsequent get
calls. The easiest way to get around this is to set the MQGMO.MatchOptions
= MQMO_NONE. You can do this once prior
Markus -
This is a bug in the install routine for CSD02 when installing to a server
with only the Control Center installed. There are two new files that are
not installed in this situation: LogonInfo.dll and LogonInfo.pdb.
You can get these files from the server where the ConfigMgr is installed
We had this problem as well. It got fixed in one of the CSDs. I *think* it
was CSD02, but I'm not positive.
- Steve
-Original Message-
From: Jeff A Tressler [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 13, 2002 10:05 AM
To: [EMAIL PROTECTED]
Subject: MQSI : DataFlowEngine causing probl
49 matches
Mail list logo
