however.
Hope this clarifies.
___
Steve Sacho
S3/CSSD - Architecture
Tel: 805-577-3983
Internal: 92-598-3983
MQSeries List [EMAIL PROTECTED] wrote:
Steve,
Just to verify, since I'm the orginal requester.
You have Domino R5, MQ 5.2.1, writing JAVA code to interface the 2
Domino 6 supports Java 1.3.1, but I found no problems with MQ 5.2.1 and R5.
Steve
MQSeries List [EMAIL PROTECTED] wrote:
Jim,
... It's fine for IBM to say just use Java, ...
Just a question: MQv53 is _really_ working with Lotus Notes' embeddded
JVM? AFAIK, Notes JVM is on level 1.1.8, but MQ
dcomcnfg.exe - which seems like an alternate to Control Panel Services
The last one tends to fix everything for me.
___
Steve Sacho
CSSD - Enterprise Architecture
Tel: 805-577-3983
Internal: 92-598-3983
Supraba Shekharan [EMAIL PROTECTED]
Sent by: MQSeries List [EMAIL
of the security issues with MQ, right?
___
Steve Sacho
CSSD - Enterprise Architecture
Tel: 805-577-3983
Internal: 92-598-3983
Malamud, Mikhail [EMAIL PROTECTED]
Sent by: MQSeries List [EMAIL PROTECTED]
07/15/2002 01:04 PM
Please respond to MQSeries List
, if your environment is clustered, this makes having different QM names much less of an issue.
I've found it boils down to who dominates in your organization: The hardware/infrastructure, or the architect/design/development teams.
___
Steve Sacho
CSSD - Enterprise Architecture
It's been discussed by this group, so I thought you'd be interested in a snippet from a reply I received from IBM, to a Q I asked regarding the whole Windows Terminal Server - MQ conflict issue:
The Windows 2000 Terminal Server environment introduces the idea of
name spaces for kernel objects
Any LotusScript code using MQLSX will surely be supported i.e. it won't suddenly break when newer versions of MQ come out - at worst you may have to keep your own copy of the mqlsx.dll. But the larger issue of concern for Lotus developers is IBM's not-so-subtle shift away from LotusScript as the
