try ADMIN password!
- Original Message -
From: N Vinodh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 05, 2002 10:22 AM
Subject: not able to login to buildtime
Hi
We have installed MQworkflow on win/NT. The installation is fine. But we
are not able to login to
Dear Friends:
We have downloaded Application Messaging Interface (AMI) Support Pacs from
IBM website. We have successfully installed this AMI support on Win NT, Win
2000, Win Xp operating system.
However, while trying to install AMI on a Windows 95 system, the setup
program gives a SEVERE
Vinodh,
When you are logging on to the buildtime for the first time, use
ADMIN/password as userid/password as that is the default user created in the
workflow domain.
WindowsNT also provides a facility of Unified Logon which can be activated
by defining the corresponding
winNT userid as
How do I configure a non-cluster Q-Manager to send messages to a cluster of
queue managers in a fault tolerant manner aside from creating an overlapping
cluster?
The way I understand it the sender channel configured on the external Q-Manager
explicitly references a particular machine in the
Ryan
Though I haven't used this particular interface, I'm guessing that like all
other interfaces that I can think of, the queue manager name does not have
to be specified when identifying a queue on the queue manager that you are
connected to. From the documentation queue name is mandatory.
Emile,
There is a section covering this in the WebSphere MQ Security manual.
Regards,
Tim Crossland
http://www.cclDesign.com
Emile Kearns [EMAIL PROTECTED]@AKH-Wien.AC.AT on
05/06/2002 13:34:21
Please respond to MQSeries List [EMAIL PROTECTED]
Sent by: MQSeries List [EMAIL PROTECTED]
Got the solution from IBM...
Hi Paul, Investigating further, I found this to be a known problem that
occurs due to an incorrect registry entry. The problem can easily be
solved by using regedit to examine HK_LOCAL_MACHINE\SOFTWARE\New Era of
Networks\nnsycomps and making sure that
BDY.RTF
Description: RTF file
I have a strange one here. Installed MQ/Win2K V5.2.1 with CSD4. I can
create a qmgr via MQ Explorer and it starts up, turns green, and all the
other services, e.g. listener, also start. But, the status of the qmgr is
not connected as per the properties report. A normal qmgr would have
John - the fact that you've got a queue manager outside of the
cluster immediately implies that you cannot make full use of
its benefits.
In fact, the same 'problem' exists when an application tries
to connect to queue manager, say, QM1 whose WLM is then in charge
of distributing the messages to
Title: COD delivery problem on AIX
I am having a problem with report messages on AIX 4.3 MQ 5.2.
I receive messages from QM1 with MQMD.Feedback set to MQFB_COA+MQFB_COD, MQMD.ReplyToQueue = DESTQ and MQMD.ReplyToQMgr = QM2
Initially, the report messages were hitting my Dead Letter Queue. I
Rick -
It sounds like you are logged onto your Win2K server via Terminal Services.
When you do this, you can use the MQ Services MMC as normal, but to use the
MQ Explorer MMC you must connect to the queue manager as a client. (Right
click Queue Managers, select Show Queue Manager ..., select the
How does runmqsc react?
From: Rick Tsujimoto [EMAIL PROTECTED]
Reply-To: MQSeries List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Win/2K QMGR problem
Date: Wed, 5 Jun 2002 11:35:11 -0400
I have a strange one here. Installed MQ/Win2K V5.2.1 with CSD4. I can
create a qmgr via MQ Explorer
I believe this is a security issue. What I did was to completely unstall
MQSeries and clean up registry and then reinstall MQSeries with Domain
Administrator Special User ID (password never expired). It should work.
Jeff
-Original Message-
From: Rick Tsujimoto [mailto:[EMAIL
Hello Brant,
The event message tells you what failed and why. You should easily see
the qmgr/queue it was tring to open and the userid it was using. The
somewhat tricky part is the MQIACF_OPEN_OPTIONS (0x03FE) parameter which
is immediately followed by the open options passed to the failed
Brant,
the difference between the two reports is a subtle one. COA's are generated
by the queue manager itself, (usually) using the mqm userId to put them to
the replyToQueue. COD's, however, are generated by the agent process that is
started on behalf of each application that issues an MQCONN
Additionally, if you want to know the object for which the 2035 message
was issued, look on the appropriate error log for the qmgr and there should be a
corresponding 8077 message which specifies the object name.
-Original Message-From: Alessandro Brezzi
[mailto:[EMAIL
Title: COD delivery problem on AIX
How you doing Brant?
I think the problem is the COD is being put to the
xmitq but under the userid that's in the MQMD. You have to grant that
userid put access to the xmitq.
- Original Message -
From:
Gutekunst, Brant
To: [EMAIL
Is it customary (beneficial ??) to
have OS/390 processes write to a locally managed queue and to have that queue
pushed by the server to a remote managed queue (hub) in a non OS/390
environment. Why not let clients (Linux/VM in my case) connect directly to the
OS/390 managed queue ?
William
There are two main reasons
1. The client attachment feature costs extra on OS/390 - I dont know how
much but I am sure that it is unreasonable - ie more than the cost of the
hub server
2. Misbehaving clients cause problems on the QM boxes so it is easier to
handle problems on a client
Actually, I think it all depends...
Here, the vast majority of messages are transient, used to send inquiries
and answers back and forth between web servers and the backend (OS/390)
databases (mostly IDMS, but also some VSAM).
So, we made a conscious decision to NOT do the full blown backup
Folkes,
In case you do have to manage a Queue Manager node on
a citrix or Terminal Server remotely (other than using
the remote MMC and Command Server setup or writing a
client compiled admin tool) is to use VNC.
Make sure that the Server is installed and working on
the Citrix server and
I will be out of the office starting 06/05/2002 and will not return until
06/17/2002.
I will be out of the office on vacation from June 5 through June14. I will
be unavailable during this period.
All problem issues should be routed through your appropriate HelpDesk
infrastructure.
General
23 matches
Mail list logo
