Re: NPMCLASS

2004-02-27 Thread Robert Broderick
They needed to add some new questions to the certification exam :-)

bee-oh-dubble0bee-dubble-egh


From: Bruce Giordano <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: NPMCLASS
Date: Fri, 27 Feb 2004 10:12:52 -0500
This parameter seems a little odd to me.  It seems like by definition,
non-persistent messages shouldn't persist across a queue manager restart.
Not sure why IBM saw the need to create a new "sort of persistent" message.
- Bruce Giordano


  "Adiraju, Rao"
  <[EMAIL PROTECTED]>To:
   [EMAIL PROTECTED]
  cc:
  Sent by: MQSeries List  Subject:   Re:
NPMCLASS
  <[EMAIL PROTECTED]>


  Thursday February 26, 2004 10:16 PM
  Please respond to MQSeries List




Did anybody get back to you on this. The doco which comes along with CSD06
give the full explanation of this field and here is the extract:
New Queue Attribute

   This WebSphere MQ V5.3 update introduces a new queue attribute
   NPMCLASS which applies to local and model queues.  NPMCLASS can
   take one of two values:
   1.NPMCLASS(NORMAL)  -  This is the default value and indicates
 that non-persistent messages on this queue are only lost following
 a failure, or a queue manager shutdown.  These messages will be
 discarded in the event of a queue manager restart.
   2.NPMCLASS(HIGH) - This setting enables non-persistent messages on
 this queue to be retained across a queue manager restart.
 Non-persistent messages may still be lost in the event of a
 failure.
Cheers

Rao

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 25 February 2004 2:38 AM
To: [EMAIL PROTECTED]
Subject: NPMCLASS
What is the purpose of NPMCLASS?

AAC
Kunio
Instructions for managing your mailing list subscription are provided in
the
Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy or
retain it.
If you have received it in error please immediately notify me by return
email
and delete the emails.
Thank you.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
 Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
_
Say  good-bye  to spam, viruses and pop-ups with MSN Premium -- free trial
offer! http://click.atdmt.com/AVE/go/onm00200359ave/direct/01/
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: NPMCLASS

2004-02-27 Thread Miller, Dennis
Yes. It's one thing to lose messages when the system crashes, but I've
always had trouble defending the loss of perfectly good messages during
a graceful shutdown. Now we can queues that survive a routine restart
without the performance penalty of persistence.  Seems like low-hanging
fruit, to me.   

  

-Original Message-
From: Jim Ford [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 27, 2004 7:49 AM
To: [EMAIL PROTECTED]
Subject: Re: NPMCLASS


It does seem odd, but also kind of useful. To me it means that you can
have a class of message that are sort of persistent, but any logging is
deferred until the qmgr shuts down. So you get the performance benefits
of a NP message yet there's persistence, too. I suppose it means that
the shutdown takes longer, and a crash means your messages are lost, so
I don't see that we'll use it that much.

Does that analysis sound correct?




  Bruce Giordano
  <[EMAIL PROTECTED]To:
[EMAIL PROTECTED]
  ENTIAL.COM> cc:
  Sent by: MQSeries   Subject:  Re: NPMCLASS
  List
  <[EMAIL PROTECTED]
  c.at>


  02/27/2004 09:12 AM
  Please respond to
  MQSeries List






This parameter seems a little odd to me.  It seems like by definition,
non-persistent messages shouldn't persist across a queue manager
restart. Not sure why IBM saw the need to create a new "sort of
persistent" message.
- Bruce Giordano



  "Adiraju, Rao"
  <[EMAIL PROTECTED]>To:
[EMAIL PROTECTED]
  cc:
  Sent by: MQSeries List  Subject:   Re:
NPMCLASS
  <[EMAIL PROTECTED]>



  Thursday February 26, 2004 10:16 PM
  Please respond to MQSeries List






Did anybody get back to you on this. The doco which comes along with
CSD06 give the full explanation of this field and here is the extract:

New Queue Attribute

   This WebSphere MQ V5.3 update introduces a new queue attribute
   NPMCLASS which applies to local and model queues.  NPMCLASS can
   take one of two values:

   1.NPMCLASS(NORMAL)  -  This is the default value and indicates
 that non-persistent messages on this queue are only lost following
 a failure, or a queue manager shutdown.  These messages will be
 discarded in the event of a queue manager restart.

   2.NPMCLASS(HIGH) - This setting enables non-persistent messages on
 this queue to be retained across a queue manager restart.
 Non-persistent messages may still be lost in the event of a
 failure.

Cheers

Rao

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 25 February 2004 2:38 AM
To: [EMAIL PROTECTED]
Subject: NPMCLASS

What is the purpose of NPMCLASS?

AAC
Kunio

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy
or retain it. If you have received it in error please immediately notify
me by return email and delete the emails. Thank you.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
 Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: NPMCLASS

2004-02-27 Thread Christopher Frank
Hello,

>>>It does seem odd, but also kind of useful. To me it means that
>>>you can have a class of message that are sort of persistent, but
>>>any logging is deferred until the qmgr shuts down. So you get
>>>the performance benefits of a NP message yet there's persistence,
>>>too. I suppose it means that the shutdown takes longer, and a
>>>crash means your messages are lost, so I don't see that we'll
>>>use it that much.

I would say that's a fair assessment. Technically there really isn't any
logging done, even at shutdown - what is done is that the messages are
hardened to the queue-backing files, which will take some amount of time.
Also, there may be a bit of a delay when opening a queue the first time of
the day, as the queue buffer will be populated with any NP messages that
might have been on the queue across a restart. I doubt this would be a
significant delay, though.

One caveat might be that there are some times when an application was
developed to 'expect' queues to be empty in the morning, because they
'know' that the QM has just been restarted - kind of akin to overnight
expiry.

Another warning I was given was to be careful when switching the
NPMCLASS(HIGH) attribute on for a queue, because once you do so you will
not be able to back off CSD06 without deleting/redefining the queue - the
reason is that a pre-CSD06 QM will interpret a queue with NPMCLASS(HIGH)
attribute as a damaged object.

Regards,

Christopher Frank
Certified I/T Specialist - WebSphere Software
IBM Certified Solutions Expert - Websphere MQ & MQ Integrator
--
Phone: 612-397-5532 (t/l 653-5532) mobile: 612-669-3008
e-mail: [EMAIL PROTECTED]

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: NPMCLASS

2004-02-27 Thread Dale M. Robertson
G'Day,

I believe that this was done to enable IBM to conform to a requirement in
the JMS spec (pub/sub) without unduly impacting overall messaging
performance,
i.e.  using real MQ persistent messages would mean a performance 'hit'.

CheersDale R.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: NPMCLASS

2004-02-27 Thread Ronald Weinger

I can't see a tremendous use for it, but
when new features are needed for a release I can see this being an easy
feature to provide.








"Bruce Giordano"
<[EMAIL PROTECTED]>
Sent by: "MQSeries List"
<[EMAIL PROTECTED]>
02/27/2004 10:12 AM
Please respond to "MQSeries
List"

        
        To:  
     [EMAIL PROTECTED]
        cc:  
     
        Subject:  
     Re: NPMCLASS



This parameter seems a little odd to me.
 It seems like by definition,
non-persistent messages shouldn't persist across a queue manager restart.
Not sure why IBM saw the need to create a new "sort of persistent"
message.
                      
                     -
Bruce Giordano



              "Adiraju, Rao"
            
 <[EMAIL PROTECTED]>            
       To:            
                     
      [EMAIL PROTECTED]
                      
                     
             cc:
              Sent by: MQSeries List  
                   Subject:
  Re: NPMCLASS
            
 <[EMAIL PROTECTED]>



              Thursday February 26, 2004
10:16 PM
              Please respond to MQSeries
List






Did anybody get back to you on this. The doco which comes along with CSD06
give the full explanation of this field and here is the extract:

New Queue Attribute

   This WebSphere MQ V5.3 update introduces a new queue attribute
   NPMCLASS which applies to local and model queues.  NPMCLASS
can
   take one of two values:

   1.NPMCLASS(NORMAL)  -  This is the default value and
indicates
     that non-persistent messages on this queue are only lost
following
     a failure, or a queue manager shutdown.  These messages
will be
     discarded in the event of a queue manager restart.

   2.NPMCLASS(HIGH) - This setting enables non-persistent messages on
     this queue to be retained across a queue manager restart.
     Non-persistent messages may still be lost in the event of a
     failure.

Cheers

Rao

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 25 February 2004 2:38 AM
To: [EMAIL PROTECTED]
Subject: NPMCLASS

What is the purpose of NPMCLASS?

AAC
Kunio

Instructions for managing your mailing list subscription are provided in
the
Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy or
retain it.
If you have received it in error please immediately notify me by return
email
and delete the emails.
Thank you.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
 Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive




The information contained in this message may be CONFIDENTIAL and is for
the intended addressee only.  Any unauthorized use, dissemination of the
information, or copying of this message is prohibited.  If you are not the
intended addressee, please notify the sender immediately and delete this
message.


Re: NPMCLASS

2004-02-27 Thread Jim Ford
It does seem odd, but also kind of useful. To me it means that you can have
a class of message that are sort of persistent, but any logging is deferred
until the qmgr shuts down. So you get the performance benefits of a NP
message yet there's persistence, too. I suppose it means that the shutdown
takes longer, and a crash means your messages are lost, so I don't see that
we'll use it that much.

Does that analysis sound correct?




  Bruce Giordano
  <[EMAIL PROTECTED]To:   [EMAIL PROTECTED]
  ENTIAL.COM> cc:
  Sent by: MQSeries   Subject:  Re: NPMCLASS
  List
  <[EMAIL PROTECTED]
  c.at>


  02/27/2004 09:12 AM
  Please respond to
  MQSeries List






This parameter seems a little odd to me.  It seems like by definition,
non-persistent messages shouldn't persist across a queue manager restart.
Not sure why IBM saw the need to create a new "sort of persistent" message.
- Bruce Giordano



  "Adiraju, Rao"
  <[EMAIL PROTECTED]>To:
[EMAIL PROTECTED]
  cc:
  Sent by: MQSeries List  Subject:   Re:
NPMCLASS
  <[EMAIL PROTECTED]>



  Thursday February 26, 2004 10:16 PM
  Please respond to MQSeries List






Did anybody get back to you on this. The doco which comes along with CSD06
give the full explanation of this field and here is the extract:

New Queue Attribute

   This WebSphere MQ V5.3 update introduces a new queue attribute
   NPMCLASS which applies to local and model queues.  NPMCLASS can
   take one of two values:

   1.NPMCLASS(NORMAL)  -  This is the default value and indicates
 that non-persistent messages on this queue are only lost following
 a failure, or a queue manager shutdown.  These messages will be
 discarded in the event of a queue manager restart.

   2.NPMCLASS(HIGH) - This setting enables non-persistent messages on
 this queue to be retained across a queue manager restart.
 Non-persistent messages may still be lost in the event of a
 failure.

Cheers

Rao

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 25 February 2004 2:38 AM
To: [EMAIL PROTECTED]
Subject: NPMCLASS

What is the purpose of NPMCLASS?

AAC
Kunio

Instructions for managing your mailing list subscription are provided in
the
Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy or
retain it.
If you have received it in error please immediately notify me by return
email
and delete the emails.
Thank you.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
 Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: NPMCLASS

2004-02-27 Thread Jeff A Tressler
This parameter seems a little odd to me.  It
seems like by definition, non-persistent
messages shouldn't persist across a queue
manager restart. Not sure why IBM saw the
need to create a new "sort of persistent"
message.
===
Seems to me that if you rely heavily upon the
speed of non-persistant messages, then these
messages should not be deleted for normal
queue manager down times.

If you stop the queue manager nightly to do
backups, then you dont want to lose normal
transaction traffic.

After all it is normal system down time.

On the other hand, if the queue manager or
sytem has a catastrophic failure then loss
of non-persistant messages is expected.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: NPMCLASS

2004-02-27 Thread Bruce Giordano
This parameter seems a little odd to me.  It seems like by definition,
non-persistent messages shouldn't persist across a queue manager restart.
Not sure why IBM saw the need to create a new "sort of persistent" message.
- Bruce Giordano



  "Adiraju, Rao"
  <[EMAIL PROTECTED]>To:   
  [EMAIL PROTECTED]
  cc:
  Sent by: MQSeries List  Subject:   Re: NPMCLASS
  <[EMAIL PROTECTED]>



  Thursday February 26, 2004 10:16 PM
  Please respond to MQSeries List






Did anybody get back to you on this. The doco which comes along with CSD06
give the full explanation of this field and here is the extract:

New Queue Attribute

   This WebSphere MQ V5.3 update introduces a new queue attribute
   NPMCLASS which applies to local and model queues.  NPMCLASS can
   take one of two values:

   1.NPMCLASS(NORMAL)  -  This is the default value and indicates
 that non-persistent messages on this queue are only lost following
 a failure, or a queue manager shutdown.  These messages will be
 discarded in the event of a queue manager restart.

   2.NPMCLASS(HIGH) - This setting enables non-persistent messages on
 this queue to be retained across a queue manager restart.
 Non-persistent messages may still be lost in the event of a
 failure.

Cheers

Rao

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 25 February 2004 2:38 AM
To: [EMAIL PROTECTED]
Subject: NPMCLASS

What is the purpose of NPMCLASS?

AAC
Kunio

Instructions for managing your mailing list subscription are provided in
the
Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy or
retain it.
If you have received it in error please immediately notify me by return
email
and delete the emails.
Thank you.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
 Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: NPMCLASS

2004-02-26 Thread Adiraju, Rao
Did anybody get back to you on this. The doco which comes along with CSD06
give the full explanation of this field and here is the extract:

New Queue Attribute

   This WebSphere MQ V5.3 update introduces a new queue attribute
   NPMCLASS which applies to local and model queues.  NPMCLASS can
   take one of two values:

   1.NPMCLASS(NORMAL)  -  This is the default value and indicates
 that non-persistent messages on this queue are only lost following
 a failure, or a queue manager shutdown.  These messages will be
 discarded in the event of a queue manager restart.

   2.NPMCLASS(HIGH) - This setting enables non-persistent messages on
 this queue to be retained across a queue manager restart.
 Non-persistent messages may still be lost in the event of a
 failure.

Cheers

Rao

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 25 February 2004 2:38 AM
To: [EMAIL PROTECTED]
Subject: NPMCLASS

What is the purpose of NPMCLASS?

AAC
Kunio

Instructions for managing your mailing list subscription are provided in the
Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy or retain it.
If you have received it in error please immediately notify me by return email
and delete the emails.
Thank you.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive


Re: NPMCLASS

2004-02-24 Thread Ronald Weinger

(BIf you need to keep non-persistent messages
(Bacross a controlled shutdown of a distributed qmanager.
(BIt appears that during a qmanager quiese it
(Bwill write the message to the log, but not otherwise.
(BSo  there will be no persistent
(Bmessage overhead normally; only during a controlled shutdown.
(BI guess it would help during maintenance
(Bshutdowns
(B
(B
(B
(B
(B
(B
(B
(B
(B
(B
(B" $B4];37{0l (B"
(B<[EMAIL PROTECTED]>
(BSent by: "MQSeries List"
(B<[EMAIL PROTECTED]>
(B02/24/2004 08:37 AM
(BPlease respond to "MQSeries
(BList"
(B
(B        
(B        To:  
(B     [EMAIL PROTECTED]
(B        cc:  
(B     
(B        Subject:  
(B     NPMCLASS
(B
(B
(B
(BWhat is the purpose of NPMCLASS?
(B
(BAAC
(BKunio
(B
(BInstructions for managing your mailing list subscription are provided in
(Bthe Listserv General Users Guide available at http://www.lsoft.com
(BArchive: http://vm.akh-wien.ac.at/MQSeries.archive
(B
(B
(B
(B
(BThe information contained in this message may be CONFIDENTIAL and is for
(Bthe intended addressee only.  Any unauthorized use, dissemination of the
(Binformation, or copying of this message is prohibited.  If you are not the
(Bintended addressee, please notify the sender immediately and delete this
(Bmessage.
(B

NPMCLASS

2004-02-24 Thread $B4];37{0l(B
What is the purpose of NPMCLASS?
(B
(BAAC
(BKunio
(B
(BInstructions for managing your mailing list subscription are provided in
(Bthe Listserv General Users Guide available at http://www.lsoft.com
(BArchive: http://vm.akh-wien.ac.at/MQSeries.archive