Erik
AMQ6175: The system could not dynamically load the library
/opt/mqm/mwas/xatm/ora8swit. The error message was ld.so.1: amqzxma0:
fatal:
libucb.so.1: open failed: No such file or directory. The Queue Manager
will
continue without this module.
It looks as if the file
Hi all!
After re-installing CSD03 on NT (rolled back to CSD02 once) checking in/out in the
Control center is slow. Thing is, nothing happens in the computer. CPU usage
spikes for a bit, then nothing. CPU is idle, no disk-swapping, nothing. Seems like
some time-out occurs, because after a
No, I do mean SYSTEM.DEF.CLNTCONN and I do know where to click to show the
system objects. The restart with -c fixed the problem.
Francois van der Merwe
Senior IT Specialist
IBM, Cape Town, South Africa
+27 (0)82 556 9467 / +27 (0)21 402 5597
[EMAIL PROTECTED]
Jonas
Glen -
Thank you for the reply. I still am not sure where the GMT is coming from.
That's to say OS390 or WIN2000?
The book says Greenwich Mean Time (GMT) is used for the 'puttime' 'putdate'
fields, subject to the system clock being set accurately to GMT. I'm pretty
sure the OS390 machine is set
Dave
most mvs systems are set to GMT, and local times zone at IPL. If your NT
system is set up properly, it also knows which time zone it is in. MQ
just asks the os what the GMT time is.
glen
Hill, Dave [EMAIL PROTECTED]@AKH-Wien.AC.AT on 10/01/2002 09:26:50 AM
Please respond to MQSeries
Dave,
A computer stores time/date in GMT even
if it displays in your local time. The computer just does a + or
- on GMT according to the time zone you set and whether you have daylight
savings time enabled. The display of the time is usually converted
by the OS for your convenience. Since the
BDY.RTF
Description: RTF file
OK, here is where I am at now. Below is the set up once more:
**
QM1 and QM2 are in ClusterA.
QM3 is not in any cluster, and has a local queue called FinalQ.
QM1 is the gateway to QM3. QM1 has an XMIT queue called QM3.XMIT. It has a
QM
Hasta el proximo 17 de octubre estaré de vacaciones. Para cualquier consulta ponerse
en contacto con Manuel Morales o Josep Sanchez-Gracia
Gracias
--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn
Sie nicht der richtige Adressat sind oder diese E-Mail
mike,
these
are errors to indicate internal MQ errror. You may need to open a problem ticket
with IGS
-Original Message-From: Sampson Micheal
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, October 01, 2002 11:01
AMTo: [EMAIL PROTECTED]Subject: AMQ6183 and
AMQ6125
Before I open a problem ticket with IBM, I wanted to know if anyone else has
seen this error.
I have a vendor that requires specific values in the ApplIdentityData field.
I set up the developer's ID with +setid permissions to the remote queue and
to the XMitQ. We incrementally added
Does anybody know if some ingenious person/company has come up with a
product that performs Production source code versioning AND production code
rollout for MQSI yet??
bobbee in NJ
Rob,
I encountered this also. I was able to get it to work, by specifying +setid
with the permissions to the queue manager and to the queue. Hope this
helps.
Jim
-Original Message-
From: Wyatt, T. Rob [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 01, 2002 11:21 AM
To: [EMAIL
First, just a simple question. Did you do a refresh security with each
permission change?
Cheers,
Darry
-Original Message-
From: Wyatt, T. Rob [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 01, 2002 12:21 PM
To: [EMAIL PROTECTED]
Subject:Problem setting ID Context
Yes. Our script has that built in...
#!/usr/bin/ksh
(date;echo) $0.`date +%y%m%d`.out
/bin/ksh -v $0.`date +%y%m%d`.out 21 EOF
#--
# Set authorization
#
/opt/mqm/bin/setmqaut -m QM1 -t qmgr -g mqmdev -all +inq +connect +dsp
Before you ask...we are supposed to sanitize any scripts we share with the
world and I left in a typo. In the real script, my QMgr names match between
the setmqaut and runmqsc commands. Shoulda used a change all.
-- T.Rob
-Original Message-
From: Wyatt, T. Rob
Sent: Tuesday, October
Try this:
/opt/mqm/bin/setmqaut -m QM1 -t qmgr -g mqmdev -all +inq +connect +dsp
+setid
-Original Message-
From: Wyatt, T. Rob [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, October 01, 2002 11:06 AM
To: [EMAIL PROTECTED]
Subject: Re: Problem setting ID Context
Yes. Our script
No, but I found support pack IC01- MQSeries Integrator V2 - Change Management and
naming standards examples very helpful. It will work with any source control system.
Regards,
Stephen Hochman
Merrill Lynch
Middleware Technology Services
-Original Message-
From: Robert Broderick
That seems to have done it. Also, found the note in the manual about how
both are required. Thanks for the pointer, Dennis!
-- T.Rob
-Original Message-
From: Miller, Dennis [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 01, 2002 2:16 PM
To: [EMAIL PROTECTED]
Subject: Re: Problem
Currently, we are attempting to utilize the CICS Bridge to pass data to the COMMAREA
of a screenless CICS COBOL program that does a DB2 select. The comm area in the
linakage section is as follows:
LINKAGE SECTION.
01 DFHCOMMAREA.
05 HOLD-YEAR-PREFIXO PIC X.
I am facing an interesting issue regarding
how channels are started and how system administrators and application
developers perceive MQSeries to be running. I would like
to know of any experience, good or bad, you have had with running channels
this way and your opinion overall.
First - there
Mike,
The
whole point of asynchronicity is that the communication can be down without
affecting the interface between the app and the QMgr. MQ is supposed to
provide reliable messaging over unreliable transport and the mechanisms that
allow a channel to quiesce are a large part of how that
22 matches
Mail list logo
