Title: Message
Hi
Nadi
I
expect, security switch(es...) have been defined but no access
profiles...
Try
this one first:
Define
in theclass MQADMIN the profile .NO.SUBSYS.SECURITYwhere is the subsystem name.
After refreshing the profile, recycle the queue manager. This should
Hi,
I can't (won't!) answer the first question, beyond that root certificates
should last an order of magnitude longer than end-users.
If you have a number of queue managers, managing them with self-signed
certificates can become a nightmare. To add/renew one certificate would
then require you
Title: Message
thanks
Guido for the input. We managed to start the channel initiator fromthe
master console which started giving out security errors, combined with you input
all is now running
thanks
-Original Message-From: Rechsteiner, Guido
[mailto:[EMAIL PROTECTED]Sent: 26
Hi
I have a queue that contains a number of uncomitted messages. Messages are
written there by a channel exit which is used by a number of channels, plus
by a few other internal applications.
Is there any way for me to identify the source of the uncommitted messages?
(Or any way to clear / delete
I am working with a group who is using the Java client. They
are not using the local bindings. To connect to the queue
manager they decided to use SYSTEM.DEF.SVRCONN.
The applications failed to connect and the error logs have the
following errors. These errors continue though all their error
Greetings All,
We are in the process of rehosting OS/390 to AIX and I am looking for some
thoughts on a problem we have run into. To provide test data on AIX I have a
channel message exit on our gateway/hub.OS/390 channel that copies all
mainframe-bound messages to the AIX qmgr, however initial
Hi Jeff,
I have found that the 2 major reason you get rc of 2059 is because:
(1) The listener for that particular queue manager is not running.
(2) Incorrect port number.
Hope that helps.
Regards,
Roger Lacroix
Capitalware Inc.
http://www.capitalware.biz
Quoting Jeff A Tressler [EMAIL
Message Id and Correlation Id are defined to be BINARY data, not character
data.
MQ will never convert these, and IMHO, neither should you. If the
application
developer is assuming that they will be converted they are mistaken.
Dave
Instructions for managing your mailing list subscription are
Hi,
MQ treats MsgID, CorrelID and GroupID fields as binary data and these fields are
NOT converted when messages hope between queue managers.
Over the years, I have learnt to never store application related data in any of
these fields because you never know when you will get burnt by the
Roger Lacroix wrote:
Did you issue the 'refresh security' from runmqsc (or whatever it is called
for OpenVMS).
Note: For earlier releases of MQ for Unix, you had to bounce to queue manager
to pick up new security setting. (Strange but true.)
Roger, there were no security setting changes made
We routinely change the MCAUSER of any SYSTEM channels to nobody so that
they cannot be used as points of entry. We then create a separate channel
for specific applications etc. (remembering to remove/change the MCAUSER for
each individual channel).
In any event, Java client connections have been
Thanks,
I did try to put messages on an XMITQ that has the same name as the remote QManager
name. I used a java program MQSender.java to do it. so my java command looked like :
java MQSender remoteQueueName XMITQName(this is my destination QMANGER Name too) . I
got an error code 2085. what am
You shouldn't put the XMITQName in the remoteQueueName. You should populate
your sender routine with a queue name and qmgr name the same way you would
if the queue was a local queue. The local qmgr will then find the xmitq and
route your message correctly.
Nick
-Original Message-
From:
We have wbimbv5.0.3 installed on a Solaris
machine, with WMQ 5.3 (CSD06)
When I try and issue the mqsicreatebroker
command, I am getting the following error returned:
ld.so.1: mqsicreatebroker: fatal:
libjvm.so: open failed: No such file or directory
Killed
Has anybody encountered this?
Any
Kerry,
No, no, no...You cannot put EBCDIC in msgid/correlid. MQ never
translates them and neither should you; they ARE readable on AIX and
will contain exactly what was sent. All by design. Passing application
data in those fields is a boo-boo. You may be able to overcome it with
some creative
Thanks Nick,
Here is what I meant by my command:
Java MQsender queueName QManagerName
java MQSender remoteQueueName XMITQQName . ( note I my XMITQQName is the same as the
destination Q Manager Name)
To simplify, I need to put a message on an XMITQ, the message should routed to a
remote
Hossam,
It's looks like you are using some sort of wrapper. You may have to make
the change in the wrapper program since it may always assume you are
connecting to the qmgr which hosts the queue. I'm not familiar with your
wrapper program so I can't give you much help. In order for this to
fyi,
I just encountered a strange problem where a channel failure did not result
in a channel event being generated. I didn't realize we had a problem
until an application generated an email informing me of a connection
problem. IBM says this is a known problem.
- Forwarded by Richard
Hi Ruzi,
did you figure out how to set it? I don't seem to be able to make the
BlockIP2.dll get loaded. specifically, I put all the files into
d:\utils\exit, and configured my SYSTEM.ADMIN.SVRCONN with
scyexit('d:\utils\exit\BlockIP2(BlockExit)'), and
scydata('d:\utils\exit\blck.cfg; -d')
But
Hi Benjamin,
You should get a file: c:\BlockIP2.log presenting you with a log/trace fil
telling you what BlockIP2 do.
If you're dealing with windows you must specify scyexit() and scydata() like
this:
alt chl(SYSTEM.ADMIN.SVRCONN) chltype(SVRCONN) +
SCYDATA('FN=d:\utils\exit\blck.cfg;-d') +
An update.
I disabled the OAM as Ken suggested, and that has solved the problem, so I now
know it is security related.
So this still begs the question: how on VMS do I find out what the security
violation is?
Thanks,
Dave A.
--- David Awerbuch [EMAIL PROTECTED] wrote:
Date: Mon, 26 Apr 2004
The permissions on authorization files, created by the OAM, are:
S:RWD, O:RWD, G:RWD, W:R (ID=MQM, ACCESS=R+W+E+D+C)
see the following for more info:
http://www-306.ibm.com/software/integration/mqfamily/library/manualsb/amqqag
00/amqqag001q.htm#HDRUAF
-Original Message-
From:
The (BlockExit) part is the function to call inside the DLL.
The exit is loaded when someone uses the channel. Try the following simple
test procedure:
Creating a test server connection channel called test
define the exit against that
Open a DOS window set MQSERVER=test/TCP/localhost
Use a tool
While it's possible to open the XMITQ directly, it's not advised because
you have to build a distribution header and play other low-level games.
You want to open the replytoqueue at replytoqmgr and allow the local
qmgr to resolve that combination to the xmitq.
I'm not totally sure what your
24 matches
Mail list logo