Ha! Office Space what a gem (and one of my favorites)! Strongly
recommended for everyone who hasn't seen it. I bet you can relate to it in
some way or the other. I like the scene where they beat up the peripherals
best... :-)
Make sure that somebody has a camera to document the post-it ambush,
Paul,
the PORT attribute is not used for the MQSeries JMS transport. IBM
introduced JMS over IP for publish/subscribe applications (supported with
WBIMB V5) and that's where the port comes into play.
If you have a local Java application and see the queue manager complain
about channel limits, you
I don't know how it is nowadays, but when I have been there a couple of
years ago, it was MUCH smaller than the US conference. But then again,
everything in Europe is/appears much smaller than here in the U.S.
I would not be so sure about the jobs/money statement, from what I hear.
From:
Pete,
you say: [...]using the transaction TST2 PUT 01 xxx where x is the
transmission queue we setup.
I am not sure if that can cause a S0C7 abend, but you shouldn't put to the
transmission queue, but instead define a remote queue and use that for your
remote tests.
The only application
Dax,
is the memory increase ongoing, ie. does it increase with every test run, or
only once?
If only once, have you tried to configure the exit, but bypass your
processing within the exit and just return? I am just guessing, but maybe
the memory increase you see is caused by the pure loading of
. It is as if
1,600 people collectively went eeewww, thanks for the visual - NOT!.
-- T.Rob (who is leaving his desk to go wash up...)
-Original Message-
From: Stefan Sievert [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 03, 2003 3:05 PM
To: [EMAIL PROTECTED]
Subject: Re: MVS msg exit (MQPUT
Hey Jim,
I dug this out from my archives (May 1st this year), hope it helps.
Stefan
---
Hi all,
hope someone can answer a query from an MQ newbie. The environment
is MQ 5.3 running under Solaris 8.
The queues directory contains a number of directories with names of the
form
I think one reasonable explanation as to why is that you cannot make use of
the new channel pooling feature introduced with runmqlsr in 5.3, which
dramatically increases the number of clients you can connect to a box. Can't
use that with inetd, which spawns a new amqcrsta for every incoming open
Peter,
what is your design rationale for having multiple initiation queues?
Stefan
From: Heggie, Peter [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Design Review - custom trigger monitor vs triggered program
Date: Tue, 29 Jul 2003 13:01:11 -0400
Jose,
glad to hear it works now. It's kind of strange though, because MQCCSI-Q-MGR
is the default value for MQMD-CODEDCHARSETID, if you use the copy book
CMQMDV to initialize your message descriptor structure before doing the
MQGET.
Anyways, it works now... ;-)
Stefan
From: Jose, Prince [EMAIL
Enrico,
is MQSIntegrator involved in processing this message?
Stefan
From: Enrico Strydom [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: DEAD Letter message
Date: Wed, 23 Jul 2003 15:36:07 +0200
I have a message on the dead-letter queue and cannot
testing I found when I removed the
MQOO_BIND_ON_OPEN
all works fine, but when I add it I get the 2257 error. Doesn't make
sense.
Chris
-Original Message-
From: Stefan Sievert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 22, 2003 3:24 PM
To: [EMAIL PROTECTED]
Subject: Re: Reason
Hi y'all,
does anybody know what happened to the MQSeries - ahem - WebSphere MQ
Planning Guide?
It had this nice table at the end which had the functional comparison
between platforms and I don't seem to be able to find it for the latest MQ
release.
Ideas? Hursley?
Stefan
[EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: WANTED: Planning Guide
Date: Wed, 23 Jul 2003 12:30:26 -0700
Stefan,
You can find it on this page:
http://www-3.ibm.com/software/integration/mqfamily/library/manualsa/manuals/crossprev.html
--- Stefan
Specifying MQFMT-STRING before issuing the MQGET won't change a thing, since
it's only an output field for MQGET.
As Peter suggested, I'd rather see to believe and dump the message
descriptor while the message is sitting on the MF queue. Check the format
and compare the CodedCharSetId field value
You might also want to ask them whether they have specified CONVERT(YES) on
their sender channel and ask them to change to CONVERT(NO) if they did.
From: Jose, Prince [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: ASCII to EBCDIC conversion problem
worked fine on OS/390 and UNIX, so maybe I can
just blame it on MS, lol!
Chris
-Original Message-
From: Stefan Sievert [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 2:43 PM
To: [EMAIL PROTECTED]
Subject: Re: Reason code 2257
HM..
Now, the obvious question is: What has
(Bad) Experience leads me to challenge that MQGMO-CONVERT was specified
correctly.
But you're right, most conversion 'errors' returned by MQ are returned with
MQCC-WARNING, so that might be worth checking, too.
Stefan
From: Jose, Prince [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
Rommel,
open the queue with MQOO_BROWSE and issue an MQGET with MQGMO_BROWSE, the
investigate the message descriptor or payload. Depending on the result, do a
destructive MQGET with the msgId returned from the browse (and be prepared
to handle the fact that the message might have been removed by
Context: MQ can act as the XA commit coordinator for XA/compliant resource
managers, like databases. For example, if you want to ACID treat MQ and -
let's say - Oracle updates, you create a switchfile for Oracle, configure MQ
and use the MQBEGIN verb to start a new transaction.
Now, in the absence
Chris,
I am not sure if I understand your question, but doesn't the reason code
explanation answer the 'why' of it, when it says: An MQGET, MQPUT, or
MQPUT1 call was issued specifying options that required an MQMD with a
version number not less than MQMD_VERSION_2, but the MQMD supplied did not
Dave,
here's what my book says:
[quote]
Wait interval.
This is the approximate time, expressed in milliseconds, that the MQGET
call waits for a suitable message to arrive. [...]
On OS/390, the period of time that the MQGET call actually waits is
affected by system loading and work-scheduling
Joe,
the FDC files are mainly for IBM tech support and I would seriously doubt
that you can find any documentation on the contents (unless you have some
connections with the lab in Hursley).
If you find something, please pass it on! ;-)
Stefan
From: JoE JK [EMAIL PROTECTED]
Reply-To: MQSeries
Hi folks,
I am trying to put together a matrix of supported XA resource coordination
scenarios. My potential in-scope candidates are:
Resource Managers (XA participants)
- MQ V5.2 and 5.3
- Oracle DB
- IBM UDB
Resource coordinators
- MQ V5.2 and 5.3
- BEA WebLogic
- IBM WebSphere AS
Platforms:
-
Paulo,
your response code indicates that you are putting the message to an
inititation queue. The trigger monitor that reads that queue expects a
special header (trigger message header) structure to be part of the message,
which is not present. Unable to process that message, it puts it to the
Dave,
shouldn't you be able to detect a failing partner by reacting to channel
event messages on the mainframe? I would expect the channels to go into
retry if the remote system goes down and a message being put to your queue
managers performance event queue (given you have those events enabled,
Rommel,
If you want to connect to more than one queue manager from a client
application, the MQSERVER variable will not work. Instead, you can either
use the MQCONNX call to specify your channel attributes within the
application code (see MQ Appl.Progr.Guide/Reference), or you can create what
is
Ruzi,
this might be totally off, but did you actually type hard return at the
end of the line? You said you copied/pasted the file, which makes me think
that this is what you did.
I think people meant that you have to hit the ENTER key at every line as you
enter it into your favorite editor, plus
Hi there,
does anybody know how to install MQ CSD's unattended using a batch
invocation and a response file?
Is it documented anywhere? I admit I haven't done a lot of RTFM on this
yet... ;-)
Thanks,
Stefan
_
The new MSN 8: smart spam
Michelle,
is it possible that a new application went into production three days ago
that (by accident) writes directly to the initiation queue
MQPB.INITQ.PB.PCCIC?
Also, the RACF message shows a queue name of MVB1.MQPB.INITQ.PB.PCCIC, which
is a different name, but that might be OK.
Did any RACF
Teresa,
if you specify a model queue on an MQOPEN, MQ will create a dynamic queue
with a unique name for each application. This unique name is returned to the
application in the OD (Object descriptor) structure element called
DynamicQName after the (successful) MQOPEN. It is that name that your
Nick is correct, the dynamic queue name is returned in the ObjectName field,
my bad.
In addition to my previous mail: You have to explicitly cause generation of
a unique queue name by specifying an asterisk as the last character of the
DynamicQName field before issueing the MQOPEN.
Sorry for the
Franklin,
if your application is compiled code that is linked with the MQ client
libraries, it may run without any error locally to a queue manager if either
MQSERVER or MQCHLTAB is defined and available. If they are not, I assume it
will just return a reason code of 2059 during MQCONN processing,
Ronald,
my understanding is that authorization checks are performed by MQ during
MQOPEN on the object name specified in the API verb. In your example, the
answer to a) would therefore be 'NO' and b) is then irrelevant.
Hope this helps (and is correct),
Stefan
From: Ronald Weinger [EMAIL PROTECTED]
Murugesan,
the things to check first are
1) Did you link the application on VMS with the MQ Client libraries?
2) Did you define the channel on Windows in exactly the same spelling
S_tcp? (case-sensitive!)
3) Is your listener on Windows running and listening on port 1414?
From the fact that you are
Hi Glen,
I know I won't really be answering your concrete questions below, but from
what you describe I get the feeling that your requirements might be better
addressed by thinking about clustering your Windows servers, not necessarily
your queue managers. MQ clustering doesn't really give you
that with v52 onwards, everything was in the registry. I'll try
setting up as System Environment variable.
Thanks Aatush
- Original Message -
From: Stefan Sievert [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 21, 2003 11:51 PM
Subject: Re: Increase size of error logs
Hi Aatush
Hi Aatush,
I would assume that you'd have to set a global environment variable
(ControlPanel-System) on Windoze platforms as well, wouldn't you?
Just a guess, haven't tried it.
Peace,
Stefan
From: Aatush Desai(PIPEX) [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL
Arun,
I suspect (meaning: I am not sure) that the MQRC_CMD_SERVER_NOT_AVAILABLE
reason code will only be returned if you use the MQ Adminsitration Interface
(available for C and VisualBasic applications) instead of building native
PCF commands. These interfaces probably encapsulate a 2033 from the
Hi,
I would just define one queue on the server where both 'clients' put the
messages to; call it SERVICE01.INPUT. This is where the server program picks
up the request for processing (assuming that the request are all for
service01). Since hardcoding is not considered a best practice, the client
, any new tricks of moving more than 100 MB message
using MQ ?
By the way, what's our general feeling now a day about using MQ as ftp ?
John C
-Original Message-
From: Stefan Sievert [mailto:[EMAIL PROTECTED]
Sent: Friday, February 21, 2003 6:56 PM
To: [EMAIL PROTECTED]
Subject: Re: XML
In addition to what was already said: If you traverse unlike platforms (ie.
from UNIX to Mainframe) and need character set conversion you will have no
other option than to convert the binary content into a character
representation. Otherwise either your XML tags will not be converted or your
Hi Dave,
you already got the answer for your 'will another instance be triggered'
question, but I want to comment on your other questions.
I suspect that you never see a CURDEPTH 0 on your triggered queue, because
- based on your message volume and the throughput of a CICS MQ transaction -
the
I agree with all that was said about why it's a bad idea to use the DLQ from
within ANY applciation. As a systems administrator I wouldn't even argue
with any developer about that, but instead revoke access to the DLQ from any
userID other than the started task or mqm user. Filling up the dead
Nope
Stefn
From: Robert Broderick [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: AMI
Date: Thu, 13 Feb 2003 15:46:13 -0500
Is AMI functionality a seperate install from the base MQ set
bobbee
]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: AMI
Date: Thu, 13 Feb 2003 17:43:13 -0500
it isnt on zOS, it is on the others...
Scott
- Original Message -
From: Stefan Sievert [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, February 13, 2003 4:59 PM
Hi Alex,
click to http://www.capitalware.biz/unix_general.html and search for MMX,
which is doing what you want (freeware, source included).
If your application is currently MQPUTing to a remote queue (definition) you
would still need to re-define the queue to a local queue, as somebody else
has
Hi Michelle,
if your application people are always getting the first message, even though
specifying a MSGID, I suspect they are doing something wrong. Having an
index on MSGID/CORRELID shoudl only affect performance, not the result of an
MQGET.
Just like with a database, the effects of an index
Binyamin,
the COA will be generated using the authority of the receiving MCA, which
usually has the permissions to put to the replyToQueue.
COD and Expiry reports will be generated using the originating userID, in
your case, this will be the userID under which the application issueing the
MQGET is
Sorry for the glitch, but I made a little mistake in my explanation. It's
not the userId of the getting application that is used to put the COD and
Expiry reports, but the userId contained in the MQMD.UserIdentifier of the
request message. So, the userId of your requesting application needs to be
...or just click here:
http://www-3.ibm.com/software/ts/mqseries/txppacs/ma12.html
From: Tim Armstrong [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Batch triggering
Date: Mon, 13 Jan 2003 08:57:57 +1100
Go to the support web site.
Hi TJo,
this quote is from Chapter 2 of the MQ Quick Beginnings for HP-UX manual
about Kernel configuration:
[quote]
MQSeries queue managers are independent of each other. Therefore system
kernel parameters, for example shmmni, semmni, semmns, and semmnu need to
allow for the number of queue
Hello and a Happy New Year to everyone!
We are running MQ5.2 and the current MQSI version on AIX and have
encountered the following message twice in the last couple of weeks:
AMQ7469: Transactions rolled back to release log space
The queue manager uses circular logging and when the message
John is correct, just send an email to [EMAIL PROTECTED] with the line
SET MQSERIES REPRO in the message body. Or just trust that your email will
make it, like you usually do... ;-)
Happy New Year everyone!!
Stefan
From: john gilmore [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
is the mq list affected by out of office messages
What do you mean by 'affected'? Those messages show up as 'normal' postings
and besides being somewhat meaningless (to use a mild expression) they are
not problematic. Well, maybe the list owner has a different perspective on
that... ;-)
if so
Matthew,
besides the requirements that need to be met for any other platform, you
need to have the MQSeries Client Attachment Feature (CAF) installed on the
mainframe. This is a feature that you need to pay for, so sometimes it is
not necessarily there. Your mainframe systems people can tell you
Binary messages are usually sent using MQFMT_NONE, so conversion is not even
considered by the queue manager; meaning there won't be any overhead at all.
Everybody have a nice weekend,
Stefan
From: MCSHEFFREY, MICHELLE (AIT) [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL
Hi Kevin,
most definitely does MQSeries for z/OS support MQGMO_CONVERT and it has been
ever since I have started to learn about it (I think V1.3.1 or something
like that).
I think it's not supported in MQ programs running under some older versions
of CICS and on VSE/ESA, but I am not 100% sure, if
Jim,
I think I remember reading in the announcment of MQ V5.3 that you no longer
have to write these scavenger routines to get rid of expired messages, but
that the queue manager itself will take care of that. Which version of MQ
are you currently on?
I don't know if my memory serves me well, but
Bobbeee,
take a look at the include file cmqcfc.h:
/* Channel Status */
#define MQCHS_INACTIVE 0L
#define MQCHS_BINDING 1L
#define MQCHS_STARTING 2L
#define MQCHS_RUNNING 3L
#define MQCHS_STOPPING 4L
#define MQCHS_RETRYING 5L
#define MQCHS_STOPPED 6L
#define
Mark,
it is CSQX START (with a blank). For reference to documentation, please take
a look at the MQSeries Command Reference
http://www-3.ibm.com/software/ts/mqseries/library/manualsa/csqzaj/csqzaj0y.htm
and scroll down to the description of the APPLICID parameter.
Hope that helps,
Stefan
From:
2002 09:19:55 -0600
But we are also using a different init queue.
-Original Message-
From: Stefan Sievert [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 18, 2002 4:20 PM
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
Doesn't matter, it's the process definition which controls what
Doesn't matter, it's the process definition which controls what gets
triggered. One trigger monitor is all you need.
Stefan
From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Trigger problem
Date: Mon, 18 Nov 2002
Hi Moshe,
if you are on V5.2 you can use the DISPLAY QSTATUS command to get the
information you are looking for (just learned that a couple of threads ago
from Dave on this list ;-) ).
Looks like you try to start the CICS trigger monitor CKTI more than once (it
opens the INITQ in exclusive mode).
Oh well, somebody must have hired them (including myself) in the first
place, correct!? Probably at times of need, correct!? Hmmm..
From: Randy J Clark [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: IT Employment Survey - Correct Attachment
not know
that there was a difference between Java client
program and other client programs. Can you clarify
that please? Thanks
Francois
--- Stefan Sievert [EMAIL PROTECTED] wrote:
Hi,
frankly, MQ clustering doesn't really provide
failover, that is one of the
common misconceptions about
Hi,
frankly, MQ clustering doesn't really provide failover, that is one of the
common misconceptions about it. If you have a client (or server bindings
program) connected to a clustered queue manager and that qmgr fails, than
your program will not be automagically reconnected to another qmgr in
Nawendu,
not sure if I understand your question. MQ is a messaging product mainly
used for application integration. Where do you want to extract data
from/load it into?
Can you elaborate a bit more on what you intend to use it for?
Cheers,
Stefan
From: NAWENDU_B [EMAIL PROTECTED]
Reply-To:
Prits,
check out the Appendix of the MQSeries Planning Guide. It contains a table
with all message size and queue limits on all platforms.
Cheers,
Stefan
From: Prithwiraj Basu [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: MQ message size limits?
Date:
Erik,
try this: http://www-3.ibm.com/software/ts/mqseries/txppacs/mc74.html
There is another support pack that deals with the same subject for
WebSphereMQ Integration Broker, which is available here:
http://www-3.ibm.com/software/ts/mqseries/txppacs/ic71.html
Hope that's what you are looking for.
Hi Norbert,
DLH reasoncodes in the range between 300 and 399 are actually feedback codes
generated by OTMA. You have to subtract MQFB_ERROR from that value (300),
which gives you the OTMA sense code. In your case that would be 26(dec);
converted to Hex that is 1A. Now, chapter 4 of the OTMA Guide
All,
can anybody give me or point me to more information about the class
MQJMSException? All that comes up if I google for it is a link to a
protected forum on an IBM site.
Any hints are highly appreciated,
Stefan
_
Broadband?
Gopi,
loadqm.exe is a program completely unrelated to MQSeries. You can do a
Google search or click here for starters:
http://www.infopackets.com/freenewsarticles/loadqm.exe.htm
Hope that helps,
Stefan
From: Gopi Krishna [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL
Arun,
the QDEPTH may include messages that are either expired or have been out
under syncpoint but have not been commited yet. Both situations will result
in the behavior you see.
What put options and message attributes are you using when putting the
message to the queue? Did you specify
Are you trying to connect to a local server or one on a different machine?
If you are using the MQClient to connect to a queue manager on a remote
machine (which is what your subject line suggests), please make sure that
you are linking with the MQ client libraries (mqic32.lib for NT). I have
Anupama,
this article is referring to MQSeries for Windows V2.1, which is the
lightweight queue manager product that is different than MQSeries for
Windows NT/2000.
Hope that helps,
Stefan
From: Anupama Vaid [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
are using, OS version and
SerivcePac level and specific error messages you get, chances are good that
somebody on this list can help you. ;-)
Cheers,
Stefan
-Original Message-
From: Stefan Sievert [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 25, 2002 11:38 AM
To: [EMAIL PROTECTED
Hi everybody,
can anybody with more experience on AIX please comment on Siva's question?
Thanks,
Stefan
From: [EMAIL PROTECTED]
To: Stefan Sievert [EMAIL PROTECTED]
Subject: MQ channels..
Date: Sat, 21 Sep 2002 15:29:52 +0530
Dear Stefan
I have some doubts in MQ performance. Let me tell you
to arrive sequentially
Given your scenario then messages should arrive sequentially. If the MQ
infrastructure is modified to allow multiple paths to the destination queue
then anything can happen
Brian S. Crabtree
EAI Consultant
- Original Message -
From: Stefan Sievert [EMAIL PROTECTED
Here's what the MQ Intercommunication Guide has to say:
[quote]
If an application puts a sequence of messages to the same destination queue,
those messages can be retrieved in sequence by a single application with a
sequence of MQGET operations, if the following conditions are met:
(1) All of
Rick,
I don't know if I have put together all the pieces of this thread correctly,
but my idea after that (and before that) is still that the physical network
is no constraint at all. I look at it from the MCA perspective: the sending
MCA doesn't even send message 2 if the receiver has received
Neelabh,
any MQ FDC files generated on the queue manager at the time of the hanging
application to be shared with us?
On Solaris these things sometimes point towards kernel config parameters
being unsufficiently set. The FDC file would probably tell us a bit more.
Stefan
From: N Ranjan [EMAIL
All,
can anybody (maybe from IBM) please provide some detail about what exactly
the checkpoint processor process amqzllp0 is doing? Is it a common service
process to manage checkpoints for persistent messages that are written to
the log or/and does it handle checkpoints for message channel
Ian,
in addition to Rebecca's suggestion...
When you say [...]to convert the text fields in the message [...], it
sounds like you expect MQ to know where text fields are located in your
message payload. That's not the case. Conversion always works on the
complete message payload as MQ has no
Hi Everyone,
Hi Jeff,
I am new to AIX and no knowledge about UNIX. (I am familiar to os/390 and
NT.) Just got my user id and create a qmgr. I have several questions:
1. How can I assign a specific port number to a qmgr?
port assignments are made in the file /etc/services. The
Peter,
I don't know about any tool to do this. Have you thought about getting the
time before and after the get, do the math in the program and put a
non-persistent message to a protocol queue? Performance impact of the second
put (non-persistent, outside syncpoint) should be minimal. You could
Shailesh,
the short answer is yes, if you specify MQxMO_SYNCPOINT on your GET/PUT.
From chapter 17 of the MQ Appl.Prog.Guide:
Syncpoints in IMS applications
In an IMS application, you establish a syncpoint by using IMS calls such as
GU(get unique) to the IOPCB and CHKP (checkpoint). To back out
Jerry,
the obvious answer would be to do a MQGET with MQGMO_BROWSE and specifying a
messageID of MQMI_NONE and correlId = 'UserId'.
Be careful though, if the putting application and the getting application
run on platforms with a different character set, because correlId is a byte
field and as
Supraba,
you will have to either specify your connection attributes in the JNDI
directory entry for you xxxConnectionFactory (where xxx is either 'Queue' or
'Topic', depending on your appl.model) or you can do it at runtime, using
the methods of the MQxxxConnectionFactory class: setChannel(...),
Bobbee,
take a look at this:
http://www.sysinternals.com/ntw2k/freeware/listdlls.shtml
It may be what you are looking for... ;-)
Stefan
From: Robert Broderick [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: MQ DLL
Date: Thu, 25 Jul 2002 08:44:10 -0400
Pisharath,
I do not think that you can get away without installing the base MQSeries
Client for your platform. It will add entries to the registry, update
environment variables, provide conversion tables and the like. The DLLs
alone just don't do the job. You don't need to install everything
Prits,
take a look at the RESET CHANNEL ... SEQNO(integer) command in the MQSeries
Commands manual to achieve what you want.
Stefan
From: Prithwiraj Basu [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: how to reset sequence numbers
Date: Thu, 25 Jul
Lee,
A couple of questions:
what platform are you running on and what programming language are you
using?
Have you tested your MQ connectivity from your MQ client to the server using
the sample programs (eg. amqsputc); in other words, are you sure that your
MQ client setup is good?
I can't
Hi Sid,
haven't done it myself, but this might hopefully help to get you closer
http://www.mqseries.net/phpBB2/viewtopic.php?t=3981
Cheers,
Stefan
From: Sid Young [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: .NET and MQ problems
Date: Mon, 22 Jul
Scott,
did you register an ExceptionListener within your JMS application? Only then
will you be notified about provider exceptions (2161/2162 in your case). I
would be stunned if the MQ provider classes are not coded using the
FAIL_IF_QUIESCING options.
Just a thought, lacking detailed knowledge
I read the question as: 'Can I connect a CICS region on LPAR1 to a MQSeries
subsystem on LPAR2 (no MQ on LPAR1)' and I am tempted to say that there
needs to be an MQ subsystem on the same LPAR as the CICS region which wants
to connect to it, but I might be wrong. I couldn't find anything in the
Sergio,
there is no MQ client available for OS/390, if that's what you are asking.
Stefan
From: Sergio Lima Costa Costa [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Connect CICS to MQSeries in another partition
Date: Wed, 10 Jul 2002 19:07:41
Bobbee,
Domino supports Java, MQ provides a Java API... there you go! ;-)
You could also use the MQLSX (LotusScript extension) classes, but this is
not supported any longer, so it doesn't sound like a sensible thing to do.
Hope that helps.
Cheers,
Stefan
From: Robert Broderick [EMAIL PROTECTED]
Hi Narasimha,
if you want to use messages 4MB you cannot use the MQSERVER variable to
define the client channel (no MAXMSGL attribute available). Instead you must
create a client channel definition file (which you implicitly did by issuing
the command 'DEFINE CHANNEL(CHAN2)
Alfons,
it is just a wild guess on my behalf, but you might want to check if the
OS/390 System Setup Guide, Chapter 16, section 'Security refreshes' holds
the answer to your question.
Stefan
From: Alfons Heirbaut [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
1 - 100 of 123 matches
Mail list logo
