Another very useful is amqsblst in mqm/samp/bin. MQ for Win32
package contains only the C source but you can compile it (or I can
send the binary).
amqsblst ('mq blaster') can put, read or echo messages with any size
and count, waiting time and give statistics.
HTH,
Tibor
Instructions for
Start a service trace at 'debug level' on broker side and let we look
into it - just for a happy hacking :-)
Tibor
The configmgr and broker are comuunicating fine. The problem is between the
broker and its execution groups. For example,
SYSTEM.BROKER.EXECUTIONGROUP.QUEUE has messages
I'm in San Francisco for the Advanced Clustering class this week so maybe
I'll have a different view by Friday. At the moment, however, I'd have to
say that clustering adds even more security considerations into the mix. It
does channel auto-definition by default and the cluster channels need
Hi,
Does anyone have a copy of this that they could share with me? Or do you know if U469417 can be used instead? The cover letter indicates that U469417 is for VAX and is available, but U469416 has a dead link on the support page.
Cheers,
Kulbir.
Peter,
The one thing I still do not understand is why a 75K NP message
going thru FAST channels only does not require disk. If the default buffer
is 64K, does not the 75K message being placed into the XMIT queue leaving
the HUB require disk?
I think I can answer that. If the message is being
Hi,
One of my user has changed the following and caused
the mqseries unable to start(QMGR hang up):-
(1)the user id profile QMQM Job Queue is changed to
the new job description and processed in the new job
queue subsystem.
(2) after change above and start the qmgr, found out
the job AMQZFUMA in
Assuming you are using MQ 5.3, look at chapter 4 (Work Management) of the
iSeries System Administration Guide.
From what I can tell, there's a number of job descriptions that various
processes use to work out how things get executed. Chapter 4 should explain
it all (to an AS400 guy at least).
I
Ed
Lots of factors here. Nature of the business, how proprietary the data,
etc.
I have always thought of a MQM as a CICS region with lots of different
applications running it. Under that assumption, we never secured VSAM
files inside of CICS to prevent other applications from updating VSAM
What pay check ?
--- Robert Broderick [EMAIL PROTECTED]
wrote:
HUMM!
MQMMQM is always suggesting CQ. I wonder whos name
is on his/hers pay
check??? :-)
From: David C. Partridge
[EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL
Hi all,
We are using MQSeries V5.3 on Unix Sun Solaris 5.8.
While testing the installation, using the IVTSetup script, we get the error message as:
Unable to bind object.
The settings in JMSAdmin.config are:
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
Dave, my tests were run on 5.2.1 CSD05. I don't believe that feature was
implemented at that level, was it?
-Original Message-
From: David C. Partridge [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 10, 2003 4:29 AM
To: [EMAIL PROTECTED]
Subject: Re: How a MQSeries Hub does its thing with
Dennis and Bobbie
I missed the point, I was thinking at a level beyond the bridge, which would be the CICS application program itself
at entry to CICS, could not that program read all the data, determine if it will fit in the commarea (if not switch to temp storage), then do a RETURN
I was thinking more along the lines of functionality, additional coding
requirements, DPL, etc. For our proof of concept project we want to
replace an application that currently accesses CICS via an EXCI from a DB2
stored procedure. Currently this request goes directly into an AOR.
However,
Couldn't find this on a search of the list which surprised me.
The WMQI 2.1 Admin Guide recommends backing up a specific set of tables in the
broker database to be used to restore in case of breakage. I understand that
Publication and subscription data is stored there in this DB but, if I'm not
June,
I was thinking more along the lines of functionality, additional
coding requirements, DPL, etc. For our proof of concept project
we want to replace an application that currently accesses CICS via
an EXCI from a DB2 stored procedure. Currently this request goes
directly into an AOR.
Jason has a good point. creating rules for all the queues in a system can
be a maintenance headache.
If the application(s) are designed to reject unrecognizable messages
(politely, rather than taking a nasty abend), then the largest exposure
would be some hacker flooding the system with garbage
In past DR tests I found that just installing it and importing the defs was the
quickest way. I know that some of you just fell off your chairs but after many +/-
experiences I found this path the least resistant.
Have fun
Dave
-Original Message-
From: Kin Yeung [mailto:[EMAIL
Can someone help fill in the gaps or correct my note below? I'm trying
to establish a timeline and show the names of the various MQ software
names and dates.
MQ: MQM (199? - 199?) - MQSeries (199? - 2001) - Websphere MQ (2001 -
present)
MQSI: MQSI (199? - 2000) - WMQI (2000 - 2002) - WMQIB (2002
I thought that it was done in 5.2, but as they say:
The second thing that goes as you get older is your memory. I can't
remember what the first thing was!
I guess that's one for the Hursley folks to comment on.
Dave
Instructions for managing your mailing list subscription are provided in
the
Paul,
The WMQI 2.1 Admin Guide recommends backing up a specific set of
tables in the broker database to be used to restore in case of
breakage. I understand that Publication and subscription data
is stored there in this DB but, if I'm not using PubSub
applications is there any point in doing
PUB/SUB is right. I thought there was something else. I cannot remember it
right now OR I am wrong.
Gary W??? You mentioned this to me back a couple of months when we were
doing the XA stuff?? Any input??
bobbee
From: Paul Meekin [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To:
Back to my comments and Dennis'. You will end up building something simular
to what the bridge offers. Except you will be in charge of the coding. So if
you have requirements NOW or in the Future that the Bridge does not address
it is within you scope to add it.
Now it becomes a point of getting
What kind of problems will I have given this scenario:
1) DRP Hot Site Test where production MQM dataset's are restored from
backups.
2) MVS and Distributed MQM's recovered.
3) MQM's have CLUSTERs on both platforms.
4) Shared Queues and stand-alone Queues live inside CLUSTERs.
5) Now the BIGGY,
If you use Shared Queue's on MVS but want to use triggering, how would that work? If
the message lands on a shared queue but you want multiple CICS regions supporting
pulling the message off, how do you set it up so that only 1 trigger message is sent
to an initiation queue? On the shared
The Bridge simply reads the message passes it to your program BUT it is not
called by your program like a wrapper. Its monitoring a queue and when a
message arrives it reads it and links to your program and passes the
message to your program in the commarea.
This is not going to be a substitute
I think you are thinking they are two ways to do the same thing not exactly
and I doubt the Bridge is going to fit in all situations and thus will not
allow your people to remain ignorant of the MQ API or allow management to
keep them in this state.
The situation is the program you want to
American Express made the following
annotations on 06/10/2003 11:41:26 AM
--
**
This message and any attachments are solely for the
American Express made the following
annotations on 06/10/2003 11:36:42 AM
--
**
This message and any attachments are solely for the
Dave,
Thanks for your advise. But if we do that, a lot of
cluster queue information will be left over in
respository. I know MQ will clean those after 90
days.
Thanks
KK Yeung
--- Hill, Dave [EMAIL PROTECTED] wrote:
In past DR tests I found that just installing it
and importing the defs was
So lets say a programmer has only to receive a message and process it. The
company picks the bridge. When does the programmer get to learn about MQ??
I have interviewed people who have worked at companies that allowed them
access to MQ through their own home grown software (wrappers) These people
Wasn't there a second cousin in there named TCAM??
From: Ronald Weinger [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: MQ software evolution - fill in the gaps?
Date: Tue, 10 Jun 2003 13:35:25 -0400
You forgot the 'Grandfather' product EZ-Bridge.
Oh no!
A rebel without a queue.
Robert Broderick
[EMAIL PROTECTED]To: [EMAIL PROTECTED]
OTMAIL.COM cc:
Sent by: MQSeriesSubject: Re: MQSERIES AND CICS
I've also seen companies getting so obsessed with protecting the
programmer from MQ complexity (shame, poor programmers) that they layer
themselves into a calling stack that is so far removed from MQ and the
world of messaging in general, that it is really scary. In the end the
programmers are
wow someone that is making sense...
I agree just because programmers are not bit flippers and are closer to
burger flippers (due to offshore outsourcing - ooops I digress) is that
necessarily a bad thing
Fryett.Chris
[EMAIL PROTECTED]To:
I remember the days when I was at college. At year 1, I learned the Data
General MV machine and get familiar with it. At year 2, we started using
VAX. One of my 'smart' team member rushed to learn it and wrote the
'wrapper' for most of the line commands that made it looked like DG MV and
showed
35 matches
Mail list logo
