Funny
but we just had this conversation in our team meeting today except it was about
JMS and Pub/Sub. My colleague was explaining that JMS requires a
one-to-one correspondence between JNDI managed objects and potential
destinations.So a cluster queue defined in JNDIis known to JMS
as a single
Title: Message
Peter,
On the
distributedplatformswe would create the file on a single QMgr.
Each channel would need a different name because you can't have two same-named
objects on the same QMgr. So for example,
On
QM1:
DEF CHL(QM1.SVRCONN) CHLTYPE(SVRCONN) TRPTYPE(TCP)
DEF
Janet,
The two approaches are not mutually exclusive. Go ahead and plan your disk
space for some reasonable number of messages and set trigger on depth. Then
the app will never exceed it's quota and your concerns are met. In addition
let the developer schedule the job. As long as the
The
classic example of this is for 3rd party connections (which for security reasons
are usually dedicated to a singlebusiness partneror app). In
situations where there is a gateway QMgr in the DMZ that serves multiple 3rd
parties the channel retry can isolate the3rd partiesfrom one
another.
To: Wyatt, T Rob
Subject: FW: Receiver channel parameters mrrty and mrtmr
The following message was addressed to our organisation using a domain name
that is being retired:
From: [EMAIL PROTECTED]
To : [EMAIL PROTECTED]
Subject : FW: Receiver channel parameters
Pavel,
MQ is it's own platform-independent data mover! Last time I did a migration such as
you describe, I just set up channels between the two boxes and wrote a script to copy
the contents of the queues across the channel. Once the messages were confirmed good
on the new QMgr, I deleted the
Carol,
Once upon a time we tested what was then Candle's MQ Secure. When it was first set up
it worked great. But it had a problem queue where it would dump messages it could
not decrypt. After it had been running a while, suddenly about a fourth of the
messages started dumping to the
Tad,
The
module codedoesn't help diagnose this. Would need to see the
relevant code from the get_prices.pl program - including the parms passed to the
module. Interesting thing here is that, even though you say it's a local
connection, the error log shows a server, QMgr name, channel and port
It's not the size of your queue, it's the service interval that counts.
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Roger
Lacroix
Sent: Tuesday, October 19, 2004 6:45 PM
To: [EMAIL PROTECTED]
Subject: Re: What do MQAdmins read?
Hummm,
So, put a couple of
I've seen this kind of behavior when the filesystem runs out of space. What does 'df
-k /var/mqm' show?
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Tony
Boggis
Sent: Wednesday, October 20, 2004 4:16 PM
To: [EMAIL PROTECTED]
Subject:
MQSeries.net?
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Monday, October 18, 2004 11:43 AM
To: [EMAIL PROTECTED]
Subject: Re: Security Exit
I apologize for sending this to you all. It was not my intention to do so.
However, you now
Sounds like a MAXMSGLEN problem...
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of
Christopher Fryett
Sent: Wednesday, October 13, 2004 1:54 PM
To: [EMAIL PROTECTED]
Subject: Re: JPMorganChase Co looking for MQ Systems Talent - respond
directly to sender
This is working as designed and documented:
http://publibfp.boulder.ibm.com/epubs/html/csqzas01/csqzas010y.htm#HDRSP1WOUNWI
The OAM maintains an access control list (ACL) for each WebSphere MQ object it is
controlling access to. On UNIX systems, only group IDs can appear in an ACL. This
means
John,
On windows, all accounts have two components - the human readable account name and the
SID as stored in the SAM database. Generally, you see the human-readable version
while the SID us used under the covers (like in the MQ Auth Data queue). If an
account is deleted and recreated it
Peter,
I had the same question and Paul Clarke clarified this in a prior thread.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg17173.html
Short answer - RQSTR not supported. But Paul provided some hope: I suggest that if
this is a problem for anyone that they raise a requirement (if it's a
Paul,
Yes, they are talking about the SID but I don't know how you might look that up from
Unix. I raised a requirement a while back to add PCF commands to display authorities
specifically for that reason. I was able to parse the format of the AUTH DATA
messages and created a Unix client to
Hubert,
I think you are almost there. We know that the ID being used for COA is from the
message context. So I think the message context rules apply here and you might need
to grant nobody some additional authorities as described in the SYS Admin Guide
here:
tand correctly, does this mean that on
Repos-A, I have todefine a CLUSSDR to Repos-B,C D? Similarly on
Repos-B, do I have todefine a CLUSSDR to Repos-A,C D... and so
on?tonyB. Original Message
Subject: Re: Disappearing cluster queues From: "Wyatt, T Rob"
[EMAIL P
Peter,
The
full repositories publish to as many other full repositories as they have
explicit CLUSSDR definitions for but a partial publishes to only two full
repositories no matter how many you have. Once the full repository
receives information from a partial, it then republishes to all the
Paul,
Short answer...no. For the detailed answer, go here:
http://publibfp.boulder.ibm.com/epubs/html/csqzaf07/csqzaf071l.htm#Header_331
Basically, this section boils down to this - you can pass the ID as [EMAIL PROTECTED]
only by using environment variables. The hitch is that if a
Thanks, Paul! This will be very useful. I wasn't surprised by the numbering though -
I figured all along they had reserved a block of Support Pac numbers just for you. ;-)
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul
Clarke
Sent: Tuesday,
Thanks for the offer! Solaris would be key for us.
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul
Clarke
Sent: Tuesday, September 21, 2004 11:05 AM
To: [EMAIL PROTECTED]
Subject: Re: MQSC client - MO72
Thanks T.Rob, glad to be of service.
I
Scott,
The quote and link I provided apply specifically to *full* repositories. The idea
behind that was for Tony to make absolutely sure the full repositories were in synch
before trying to diagnose the partials. If the full repositories are not
synchronized, there is no basis to think the
Tony,
Information flows between repositories only on explicitly defined channels. Do all
four of your repositories have explicitly defined CLUSSDRS to each other? When your
queues go missing, do they go missing on the partial repository only? If they are in
the full repositories, are they
Jitender,
Short answer - you can't. At least not at the QMgr level with OAM or based on
incoming User IDs.
Longer answer...Once you connect to a SVRCONN channel you gain either full admin
authority or whatever authority the MCAUSER limits you to. Obviously, if the MCAUSER
is set to a
Jitender,
To
remotely administer any QMgr you need a few things.
First,
the Command Server needs to be running. Use the strmqcsv command to get it
going. It reads messages off of the SYSTEM.ADMIN.COMMAND.QUEUE which is a
default object when you create the QMgr.
Next,
you need a
to the queue
manager. Please enlighten me further if my understanding is incorrect."Wyatt, T Rob"
[EMAIL PROTECTED]
"Wyatt, T Rob"
[EMAIL PROTECTED]
Sent by: MQSeries List
Janet,
You might want to look at the BlockIP2 or LogIP channel exits. They can tell you
where your SVRCONN channels are originating. That might help you correlate the events
with the specific clients causing them. See: http://www.mrmq.dk/index.htm?BlockIP.htm
-- T.Rob
-Original
Christopher,
Are you sure about #1? We had separate part numbers and pricing for the ETC. It was
slightly less than a full QMgr, actually. Of course with our ELA, the prices may bear
no resemblance to street prices. But it definitely was a different part number. Now,
I know that the
Thanks for the clarification, Paul! I think we will raise adoptable MCAs as a
requirement since we use RQSTR over RCVR for the most part. Our understanding up to
now was that the functionality of a RQSTR was a superset of that of a RCVR. This
explains a few things we've observed over here
Why not? Aside from the fact that SVRCONN and RQSTR channels are not available as
options to the AdoptNewMCA parm, the fact that you have several instances should not
be a problem as long as you set the AdoptNewMCACheck parameter. It causes a check
against the IP address (among other things)
Guides states, as you've said, the channel types supported.
Also, take note that the manual states it works for amqcrsta there's no
mention about runmqlsr
Wyatt, T Rob
[EMAIL PROTECTED]To: [EMAIL PROTECTED
Title: Message
Andreas,
Try this...
dmpmqaut -m QMGR -t queue -n
ETSB_EDIFACT_INBOUND -g eai
dmpmqaut -m QMGR -t queue -n
ETSB_EDIFACT_OUTBOUND -g eai
This
will dump all rules that apply to the given queues so you can compare. My
guess is that you have multiple rules or additional
Send an email to [EMAIL PROTECTED] with...
unsubscribe mqseries
...as the only line in the body of the message. Subject line is ignored.
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Larry
Murray
Sent: Wednesday, June 30, 2004 10:00 AM
To: [EMAIL
Pavel,
One technique would be to write a wrapper for the command server. The wrapper uses
and extends the PCF formats and monitors the command queue. Any commands that it
knows about are handled by the wrapper. Any commands it does not know about are
passed to the command server. The
Title: Message
Andreas,
Your
rule specifies that the queue name must have at least two nodes where the node
separator is a dot " . " and not an underscore " _ ".
So...
These
would work...
ETSB.EDIFACT_INBOUND
-Original Message-From: MQSeries List
[mailto:[EMAIL PROTECTED]On Behalf Of
ning
a dot and at least one more character would work with this
rule.
Alternately, rules that would work for this
queue would include...
ETSB_*
ETSB_**
Note the lack of a dot character in these
rules.
--
T.Rob
-Original Message-From: Wyatt, T Rob
Sent: Wednesday, June 30, 2004 10:19 AMTo:
Paul,
Just curious - I thought the direction was to use the QMID rather than the
QMgr name. Is this not the case with channel status info as described
below?
Thanks -- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Paul
Clarke
Sent: Friday, June 25,
Paul,
No, I think you got the point ok but I was labouring under false
assumptions. The QMID provides a key that is reasonably guaranteed to be
unique and I made a leap in assuming IBM would favor it over the QMgr name
where uniqueness is a requirement. The point in your email that struck me
Dave,
If I read you right, you are trying to open a queue on pay_gw_qm from
ofac_qm for input, right? Even in a clustering environment, the queue you
are trying to open MUST be local on the QMgr to which you are connected. In
this case, only processes connected to pay_gw_qm (either locally or
as a destination only
to non-local QMgrs and as both a source AND a destination to the local QMgr.
Hope that helps.
-- T.Rob
-Original Message-
From: Awerbuch, David (CALYON) [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 24, 2004 3:39 PM
To: MQSeries List (E-mail)
Cc: Wyatt, T. Rob
Subject: RE
Dave,
There are a few ways to do this. Using remote queues at every hop as you
describe works just fine. If the RNAME is specified, then you will be
changing the destination as the messages pass through the remote queue. For
example, the message leaving QMA is addressed to [EMAIL PROTECTED]
Bobbee,
Would you settle for Perl if no MQSeries module was required?
#!/usr/bin/perl -w
#--#
# trigger.pl
#
# Script parses a WMQ TMC2 tigger message and runs the application as
# specified in the process definition. Uses
Pan?
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Robert
Broderick
Sent: Thursday, June 17, 2004 4:52 PM
To: [EMAIL PROTECTED]
Subject: Re: can a message multi-hop using remote queues?
DTC has an exit example that sends a userid and password across the
Bobbee,
That depends. Remember that the command string passed by the trigger
monitor to the operating system is built as follows:
The ApplId from the relevant PROCESS definition (if created)
The MQTMC2 structure, enclosed in quotation marks
The EnvData from the relevant PROCESS definition (if
David,
I suspected as much, that's why I mentioned the security angle. Most of the
vendors I deal with do something like this, especially where one DMZ QMgr
serves multiple external users. Their XMitQs are all very cryptic names
that have nothing to do with my QMgr name and there are no QMgr
There's so many documentation changes, the fixes are almost lost at the
bottom! Scroll a little over halfway down or search for the second instance
of the string FIX PACK HISTORY. Once again, lots of JMS-related fixes.
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL
David,
Long shot here, but does the exit need to be relinked after the upgrade?
Check out:
http://publibfp.boulder.ibm.com/epubs/html/amqcac05/amqcac050m.htm#Header_47
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of David
C. Partridge
Sent: Tuesday,
The page headline talks about v10 vs. v11 but I was thinking more about the
threaded/unthreaded, DCE/non-DCE issues discussed there. I found this
reference that may be of use:
The problem is that any shared library that contains Thread Local Storage
(TLS) cannot be used as a dependency of
The AdoptNewMCA stanza of the QM.ini file addresses this. See:
http://www-306.ibm.com/software/integration/mqfamily/library/manualsa/amqzag
/amqzag2j.htm#HDRAMQ521U
http://www-306.ibm.com/software/integration/mqfamily/library/manualsa/csqzae
05/csqzae0578.htm
-- T.Rob
-Original Message-
Anthony,
"1. You have set the MCAUSER to "MQM" therefore you must connect
with the user MQM if you however leave the MCAUSER blank you can connect with
any user name but the user must be defined on the system for which you are
connecting and be part of the MQM group.
"
Not
true. The value in
Benjamin,
Using QMgr tuning to bring these channels down addresses only the symptom.
Unless you correct the problem at it's root, nothing you do will scale well.
The application MUST properly close it's resources and disconnect from the
QMgr. If you successfully tune the channels, you will
David,
This wouldn't happen to be a cluster XMitQ, would it?
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Warren
Betty
Sent: Thursday, June 03, 2004 1:05 PM
To: [EMAIL PROTECTED]
Subject: Messages stuck in the XMIT queue
Hi, All,
What are the
Ray,
We can at least solve the (old!) manual problem easily...
http://www-306.ibm.com/software/integration/mqfamily/library/manualsa/manual
s/crosslatest.html
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of
Kinzler, Raymond C
Sent: Thursday, May 27,
Is message A the only persistent one of the bunch? If so, B C might be
skipping ahead of it on a channel with NPMSPEED(FAST).
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Krishan
Agarwal
Sent: Friday, May 21, 2004 9:08 AM
To: [EMAIL PROTECTED]
Usha,
Have a look at the PCF Manual:
http://publibfp.boulder.ibm.com/epubs/html/csqzac03/csqzac03tfrm.htm
You can send messages to the command server of a remote QMgr to create your
queues. This method is used by many of the admin tools on the market such
as QN-AppWatch and is very powerful.
Kumar,
You always have to assume that an MQ client
connection is insecure. Even if you only use MQ inside your company's
firewall, anybody could put the client on a laptop, plug intoyour
network,and impersonate mqm or whatever UserID is required to access your
system. If you use the
on mqseries.net.
Cheers
Kumar
Wyatt, T. Rob [EMAIL PROTECTED]
Sent by: MQSeries List [EMAIL PROTECTED]
05/17/2004 09:45 AM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: Java Clients
There's a FAQ section on http://mqseries.net but nothing associated with
this list.
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of
Balakrishnan Ganesan
Sent: Thursday, May 13, 2004 6:55 AM
To: [EMAIL PROTECTED]
Subject: MQ FAQ
Any FAQ document for
Paul,
How about a channel exit that suppresses the stop messages for this channel?
The compromise costs you the stop events for this channel but at least
allows it to time out.
-- T.Rob
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Meekin,
Paul
Sent:
; start channel (to send event
message); discard event message and stop channel (message exit); stop
channel event etc)?
Did you have another method in mind?
Cheers,
Paul
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Wyatt,
T. Rob
Sent: 12 May 2004 14:21
Quick question...
Concerning NPMSPEED, the Intercommunication manual states that Note: If the
other end of the channel does not support the option, the channel runs at
normal speed.
What about if the other end *supports* the option but is set to
NPMSPEED(NORMAL)? Do both sides need to specify
, the lower value is adopted, in your example
NPMSPEED(NORMAL).
Don Thomas
EDS - PASC
* Phone: +01-412-893-1659
Fax: 412-893-1844
* mailto:[EMAIL PROTECTED]
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Wyatt, T.
Rob
Sent: Tuesday, May 11, 2004 1:11
Which Reconda is doing as well with QN-StatWatch. It would be interesting
to see how Roger might differentiate his exit product from the others.
-- T.Rob
-Original Message-
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 29, 2004 5:20 PM
To: [EMAIL
Sounds like the MCA has a message or two under syncpoint. Is the channel in
doubt?
-Original Message-
From: Khedr, Hossam (GEI, MORT) [mailto:[EMAIL PROTECTED]
Sent: Friday, April 23, 2004 3:34 PM
To: [EMAIL PROTECTED]
Subject: AMQ8143 WebSphere MQ queue not empty
Trying to delete an
You have to convert it to display format. MQ will see your numeric field
and attempt to convert it as character data.
-- T.Rob
-Original Message-
From: Maitra, Subhajit [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 22, 2004 1:22 PM
To: [EMAIL PROTECTED]
Subject: Msg put problem
Hi
When you download the client code, the enclosed license should give you the
proof you need. I think the license terms may even be presented on the web
page prior to the download but I'm not sure.
-- T.Rob
-Original Message-
From: Usha Suryadevara [mailto:[EMAIL PROTECTED]
Sent:
http://www.mqseries.net/phpBB2/viewtopic.php?t=12657highlight=sour+grapes
-Original Message-
From: David Awerbuch [mailto:[EMAIL PROTECTED]
Sent: Monday, April 19, 2004 2:48 PM
To: [EMAIL PROTECTED]
Subject: mqseries pick-up lines
Hey all,
I remember reading or receiving a collection
Alex,
MQ now
starts the defaultchannel initiator for you. When you start it
again, the first one already has the init queue open so the second instance
fails.
--
T.Rob
-Original Message-From: Alex A. L. Sousa - BMS
[mailto:[EMAIL PROTECTED]Sent: Thursday, April 15, 2004 2:27
I have heard from a couple of people recently that in MQ prior to 5.3
cluster information could leak over into another cluster through shared
QMgrs. I have no firsthand knowledge of this and, while it was presented to
me as fact, I have not confirmed it one way or another. Perhaps this is a
good
If you ever have a QMgr long enough for the log file numbers to wrap around,
you probably want to manually clean the log files until the wrap is
complete. There is a window of time during which the oldest log files are
numbered higher then the newest log files. I don't know if the script has
Title: MQ Security data in SYSTEM.AUTH.DATA.QUEUE
Rao,
Use
the "id" command to display your currently set active group. This should
be the group that is used to make the second entry. Try doing a "newgrp"
to change your active groupbefore creating the queue and see if it makes
the second entry
Yup, I just tried it and you are right. We use it in our object definition
scripts but the reason we do was lost to the sands of time. I just assumed
it was for creation of the objects. As it turns out, we do it to insure
that the *output* of the scripts is owned by the correct group so the MQ
You'll get multiple instances of the receiver channel and both will run
simultaneously.
-- T.Rob
-Original Message-
From: Web Sphere [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 31, 2004 8:36 AM
To: [EMAIL PROTECTED]
Subject: 2 sender channels, 1 rcvr channel
Hi everyone,
I'm
Krishnan,
These are not directly comparable. Both Websphere MQ and MSMQ actually
transport messages. JMS, on the other hand, is simply an API which requires
an underlying message mover such as the other two.
-- T.Rob
-Original Message-
From: Krishan Agarwal [mailto:[EMAIL PROTECTED]
Actually, I miss the days when we used to get announcements of new and
updated Support Pacs here. Personally, I don't mind your announcing new
versions of BlockIP here, especially since it's grown to the stature of an
unofficial Support Pac. Your work on the program and willingness to add
[mailto:[EMAIL PROTECTED]
Sent: Monday, March 22, 2004 3:50 PM
To: [EMAIL PROTECTED]
Subject: Re: Managing linear logs with MQ5.3 on Windows
Rob
Love the idea, and I am sure this must have been asked before but HOW and
WHOM to talk to??
Cheers
Rao
-Original Message-
From: Wyatt, T. Rob
Rao,
Sounds like this would be a good addition to the current Support Pac or even
a stand-alone Support Pac. Why not submit it?
-- T.Rob
-Original Message-
From: Adiraju, Rao [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 21, 2004 4:12 PM
To: [EMAIL PROTECTED]
Subject: Re: Managing
Luc-Michel,
I might be able to help with the Perl problems depending on what error you
saw. I'm thinking that I could compile the Perl script into a free-standing
executable. That would remove dependencies on the Perl version and
libraries. Let me know if you think this would help.
-- T.Rob
Sid,
As of 5.3 the listener doesn't run the channel anymore, it just passed the
connection off to the channel pooling process. So even if you could run the
listener under a different ID, the MCA would still be running as mqm.
Yes, the client will inherit the authorizations of either the MCAUSER
Michelle,
The 2320 error is from the AMI. Text below:
MQRC_HBAG_ERROR
A call was issued that has a parameter that is a
bag handle, but the handle is not valid. For output
parameters, this reason also occurs if the parameter
pointer is not valid, or points to read-only storage.
Peter,
I agree that the number sounds suspicious. Especially in relation to
messages as opposed to connections. It suggests the app is making a new
connection for each message and not releasing them. Have you checked for
that?
Alternatively, what kind of logging are you using and are all the
Rao,
I think you are drawing the wrong conclusion. It's not that we have more
people administering Windows servers in our organization, rather the
architecture of Windows requires more people NOT in the admin team to have
admin access in order to perform their jobs. On our Unix servers the
Another mailing list gem! Thanks much, Roger. This one goes in my toolbox
*and* my hall of fame.
-- T.Rob
-Original Message-
From: Roger Lacroix [mailto:[EMAIL PROTECTED]
Sent: Monday, March 15, 2004 4:56 PM
To: [EMAIL PROTECTED]
Subject: Re: Strange problem when compiling C on HP-UX
Mickel Thomas - see below for instructions on how to unsubscribe.
-Original Message-
From: Wyatt, T. Rob
Sent: Monday, March 15, 2004 9:37 AM
To: 'MQSeries List'
Subject: RE: unsubscribe
Venkat Aditya,
Getting unsubscribed from this list is similar to subscribing to the list -
you
Venkat Aditya,
Getting unsubscribed from this list is similar to subscribing to the list -
you send the command to the list server at:
[EMAIL PROTECTED]
...and NOT the list itself. In the body of the email include a single line
that reads:
unsubscribe mqseries
...and you will be
Sid,
You'll want to keep the SYSTEM.* queues that are not defaults. The only
reason we deleted the default queues was to require fully-specified
definitions for any new objects. The intent was not to increase security as
much as it was to slow down an intruder so (s)he spends more time on the
]
Subject: Re: Deleting SYSTEM queues on DMZ MQ Server
http://www.mqseries.net/phpBB2/viewtopic.php?t=13935highlight=
See this post, where the conversation turns to clusters spanning a DMZ.
-Original Message-
From: Wyatt, T. Rob [mailto:[EMAIL PROTECTED]
Sent: Monday, March 15, 2004 9:53
Rao,
We have far fewer people who can log onto our Unix servers as root than we
have local admins on any given Windows server. So for us at least, this
alone makes it a LOT easier to secure a Unix QMgr. Add in all the inherent
problems with Windows user security, viruses and worms, OS
Michael,
Actually my quote was the light a fire for a man...light a fire to a
man... but thanks for remembering!
We have gone a long way toward teaching many of our business partners how to
better secure and tune their MQ so we haven't completely abandoned that
role. The thing is that deep
Michael,
We don't get a lot of Production Support calls. We did when the group was
first formed (in fact that's why the group was formed) but over the years
we've tuned the WMQ network quite well and trained the developers on the use
of WMQ to the point that we have very few problems and they
Never figured that one out myself. I suspect there was some difference
early on that no longer applies.
-- T.Rob
-Original Message-
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]
Sent: Friday, March 12, 2004 8:10 AM
To: [EMAIL PROTECTED]
Subject: Re: RCVR versus RQSTR
with control...
Original Message
== From: Wyatt, T. Rob [EMAIL PROTECTED]
== Date: Fri, 12 Mar 2004 09:12:15 -0600
Never figured that one out myself. I suspect there was some
difference early on that no longer applies.
-- T.Rob
Instructions for managing your mailing list
Peter,
Thanks for the tips. I played around with this a little but some of our
vendors configure their QMgrs specifically to obfuscate QMgr resolution,
especially those who host multiple clients on the same QMgr. Instead of
having a QMgr alias or XMitQ with my QMgr name, they put up QRemotes
Paul,
All due respect but that seems like a really strange basis to make a
decision between SVR vs. SDR. The extra callback takes a fraction of a
second. If this delay is a problem for the app, there is probably something
exercising the channels to keep them up anyway. Even if the extra
Richard,
If you happen to be using Java clients, it is possible to assert ANY UserID
that you want, regardless of the Windows ID. In that case, just map your
Windows IDs to Unix IDs and have the Java code assert the correct ID.
On the other hand, if you are NOT running Java code, you should be
that the runmqsc command was processed but failed with
rc2059.
Regards
Henry
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Wyatt,
T. Rob
Sent: Thursday, 11 March 2004 12:28 AM
To: [EMAIL PROTECTED]
Subject: Re: Auto start queue manager
Henry,
What's the line of script
Yes. Try it.
-Original Message-
From: David C. Partridge [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 11, 2004 12:08 PM
To: [EMAIL PROTECTED]
Subject: Re: RCVR versus RQSTR channels
Are you sure that if the SVR channel has a conname specified that it will
reply
to any IP address?
-Original Message-
From: Bill Anderson [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 11, 2004 1:19 PM
To: [EMAIL PROTECTED]
Subject: Re: RCVR versus RQSTR channels
If a SVR is fully qualified it matches the behavior of a sender + it can be
started from the receiving machine (from a
Peter,
We have connections to a number of service bureaus and business partners.
Sometimes the users call to say an expected message is overdue and we see
the channel is down. This can mean any number of things that generally fall
into two categories - 1) triggering is broken or 2) the app is
1 - 100 of 398 matches
Mail list logo
