I need to amend my response. The userid assigned to CICS, or the one you
use via PLTPI would be used for connecting to MQSeries. If you're doing
context security, inserting the userid of the signed on user, it would be
that userid that would be checked. Otherwise, it's the former case. Since
y
Unless your user do not do a CICS signon that's validated by RACF, he/she
certainly does have an ACEE. If he/she doesn't do a signon, then the userid
that's checked could be the region's userid.
- Original Message -
From: "Alfons Heirbaut" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent
Andre,
Some time ago (2 years!) we ran MQ Clients with Citrix with no
problems...guess this isn't much help other than to confirm that it will
work.
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Andre
van Zyl
Sent: Friday, July 05, 2002 8:22 PM
To: [EMAIL P
2035 is an authorization failure. You need to ensure that you have security to do the get from that queue.
Glen Shubert
Reginaldo de Souza Rosa <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
07/05/2002 04:18 PM
Please respond to MQSeries List
To: [E
That's not a problem; it's how trigtype=every works by design.
Trigtype=every does not promise exactly one trigger per message. It may
produce more and, as you have discovered, it may produce fewer. Trigger
events simply indicate that the queue may need attention. Generally, you
cannot make assump
It's a security error and it means that the user ID you logged on with at
the client does not belong to a group on the server that has permission to
access the queue manager.
-Will
At 04:48 PM 7/5/2002 -0300, Reginaldo de Souza Rosa wrote:
>I received a RETURN CODE 2035 , and i have the followi
if you
don't have a listener listening to 1414 on your server, you will include the
port number, where your server listener is listening to, in your MQSERVER
definition. dont forget to put it in single quotes:
../tcp/'your.tcp.ip.address(1418)'.
-Original Message-From: Reginaldo d
I received a RETURN CODE 2035 , and i have the
following situation:
I have installed MQSeries Client (NT plataform)
connected with MQSeries Server (AIX plataform), and i'm trying use amqsgetc from
my MQSeries Client. I'm receiving
RETURN CODE 2035. In my Client MQSeries i set the following
Hi Neil,
The queue manager was deleted using MQExplorer I think. I will try out the
snap in option like you said and see how it goes. In the meantime I would
just try to snoop in around that machine.
There is a problem in that I cannot remotely connect (using MQExplorer) to
that queue manager fro
Hello Steve:
I feel this is quite difficult design problem for the MQSeries. I am not sure what
MQSeries Pub/Sub is (we use another MOM for publish/subscribe problems) but you might
want to check if it supports any kind of multicast -- if it does, consider using it.
Otherwise, multiple queues
We have a similar environment with about 600 NT clients, and we chose
option 2. We use a single permanent dynamic model queue as the source for
the reply queues, and the applications make the user's ID part of the
permanent queue name. We had thought about option 1, but it can be useful
to be able
Not an answer but more an observation.
Rather than the 190 queues you may want to consider grouping - say 19 queues, each
serviced by 10 clients.
Neil
-Original Message-
From: Steve Muller [mailto:[EMAIL PROTECTED]]
Sent: Fri 05/07/2002 11:17
To: [EMAIL PROTECTED]
Cc:
Subje
I haven't
done this in a while, but here are my notes on how to use client channel tables.
1.
Build a client channel table.
On
any MQ queue manager, define all the MQ client connections (CHLTYPE(CLNTCONN)). For example, if the client needs to connect to both QMA and
QMB, the
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
Hi all,
Part of our MQ environment is OS/390 (2.1) and NT
(5.2). We will have about 190 NT clients connected to
OS/390. These NT client apps will send a request and
get their replies from OS/390, based on a correlid.
More than 90% of these requests will be queries. We
are estimating that, for all
Some further information... I checked the 5.3 MQ beta documents. The
RUNMQLSR command has a new switch, "-i". The document states, "the IP
address for the listener,... if you omit this parameter, the listener
listens on all IP addresses available to the TCP/IP stack".
The key to this is the ph
I will be out of the office starting July 5, 2002 and will not return until
August 4, 2002.
I will respond to your message when I return.
For urgent Questions about MQ you can contact Michel Leijdekker.
About Software Services you can contact Martin Meijer or Jeroen Reizevoort
Instructions for
Don
Good point. I had noticed and kept meaning to mention it. I guessed someone was on
holiday or something.
The altenate route is useful to know :-)
Neil
-Original Message-
From: Don Golding [mailto:[EMAIL PROTECTED]]
Sent: Fri 05/07/2002 09:18
To: [EMAIL PROTECTED]
Cc:
In our case, the user doesn't have an ACEE in CICS. It is the CICS PLTPI
user that executes the transactions triggered by the application queues. The
user should be prevented from putting a message into the application queue
after he has been revoked and security-tables in MQS have been refreshed.
Hi,
Anybody notice that this got cut off by the list server on the 21st June? This
one's still working though:
http://www.mail-archive.com/mqseries%40akh-wien.ac.at/index.html
Bye.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide availab
20 matches
Mail list logo
