Author |
Message
|
PeterPotkay |
Posted: Tue Apr 19, 2005 6:59 am Post subject: Check it out - new features in Distributed MQ 6.0 |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
http://www-306.ibm.com/common/ssi/fcgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS205-094#@2h@80@
among other things....
Quote: |
The new DISPLAY CONN command shows which applications are connected to a queue manager and which queues they have opened.
The new STOP CONN command forces a disconnection from a queue manager, allowing an MQ administrator to disable a problem application.
New attributes for queues, queue manager channels, and cluster channels extend the range of cluster workload algorithms.
WebSphere MQ can track the route that a message would be expected to take through its network. New flags can request that queue managers that process the message should send back an activity report (for example, which channel, queue manager, and transmission queue have been used).
The size of the active log is now 128 GB on UNIX® platforms and 64 GB on Microsoft Windows systems.
Event messages are generated when log files are switched and it is now easier to automate the copying and archiving of log files. In addition, a queue manager can be made to replay copied logs without fully starting.
|
_________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
Michael Dag |
Posted: Tue Apr 19, 2005 7:06 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Apr 19, 2005 7:07 am Post subject: Re: Check it out - new features in Distributed MQ 6.0 |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
PeterPotkay wrote: |
The size of the active log is now 128 GB on UNIX® platforms and 64 GB on Microsoft Windows systems. |
I guess that is maximum size, not required size or default size?
It seems that way, as the QM in Beta6 I created has the standard 3/2/256 configuration. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Apr 19, 2005 7:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Also,
Quote: |
* JMS clients can use the channel definition table and run the same channel exits as other clients. |
If it's in JMS, I bet it's in Java API as well... _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Michael Dag |
Posted: Tue Apr 19, 2005 7:15 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
|
Back to top |
|
 |
malammik |
Posted: Tue Apr 19, 2005 8:01 am Post subject: |
|
|
 Partisan
Joined: 27 Jan 2005 Posts: 397 Location: Philadelphia, PA
|
|
Back to top |
|
 |
Michael Dag |
Posted: Tue Apr 19, 2005 8:09 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
malammik wrote: |
Is 6.0 going to be java based? |
I don't think IBM re-wrote MQ, from the open V6 beta it looks like OS native code same as V5.x
malammik wrote: |
How fast do you think companies will begin to upgrade? |
I think that all depends on plans, budgets, headcount etc...
some companies are still on V5.2  _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
markt |
Posted: Tue Apr 19, 2005 8:15 am Post subject: |
|
|
 Knight
Joined: 14 May 2002 Posts: 508
|
Not Java (apart from the bits that need to be).
Right now, no end of service date has been announced for V5.3. And when that does get announced there would be a MINIMUM of 12 months lifetime from that announcement date. But it's always worth starting to plan the migration early so you're not having to rush at the end. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Apr 19, 2005 9:15 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
I plan on waiting until at least CSD3 or 4 before upgrading distributed.
Mainframe we will probably complete this fall. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
JLRowe |
Posted: Tue Apr 19, 2005 9:56 am Post subject: |
|
|
 Yatiri
Joined: 25 May 2002 Posts: 664 Location: South East London
|
Other juicy stuff I like:
64-bit version of MQ on unix/linux platforms
clusters have more sophisticated workload management
eclipse management plugin can be extended
... and channel compression!
Very, very nice |
|
Back to top |
|
 |
malammik |
Posted: Tue Apr 19, 2005 9:59 am Post subject: |
|
|
 Partisan
Joined: 27 Jan 2005 Posts: 397 Location: Philadelphia, PA
|
|
Back to top |
|
 |
Michael Dag |
Posted: Tue Apr 19, 2005 10:03 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
some disapointments too:
- no configuration events (so the configuration can not be audited)
- no MQSC equivalents of PCF security commands (so you need a tool to do remote management or logon to the box) _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Apr 19, 2005 10:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Quote: |
The security interfaces used by setmqaut are given programmable command format (PCF) equivalents to permit remote administration. |
_________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
RogerLacroix |
Posted: Tue Apr 19, 2005 1:53 pm Post subject: |
|
|
 Jedi Knight
Joined: 15 May 2001 Posts: 3264 Location: London, ON Canada
|
Lots and lots of interesting items on that page. I think my 3 favor items are:
- JMS clients can use the channel definition table
- PCF commands to get security info
- 64-bit queue managers for AIX, HP-UX & Solaris
We've waited a long time for the last item, but I'm happy and sad at the same time. That means I cannot use my AIX box with AIX v5.1 installed because it is 32-bit.
Actually, since WMQ v6 cannot co-exist with v5.3, it means I will need to buy 3 new boxes (AIX, HP-UX & Solaris), since it will take companies a year or two (or longer) to upgrade to the new release.
Hey guys at Hursley, us small developers cannot afford to go out and spend thousands and thousands of dollars (euros) on new hardware, just to support 2 releases of WMQ at the same time. It would have been REALLY nice if v6 could co-exist with v5.3!!!!!! Are you guys trying to help out the hardware part of the business??
Regards,
Roger Lacroix _________________ Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
Back to top |
|
 |
kirani |
Posted: Tue Apr 19, 2005 7:33 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
64-bit ... ummm .. We are in the process of replacing our current Broker servers .. but .. somebody in H/W OS team didn't like the idea of buying 64-bit AMD servers .. so we are now buying 32-bit Intel servers .. big disappointment for our team ..
The 64-bit servers were too good .. and we were hoping to use 64-bit WMQ 6.0 on the new server after it becomes stable .. anyway .. the version 6.0 features looks promising .. let's see how many fixpack do we get before it becomes "production-ready". _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
|