Candle had me set the SYSTEM.COMMAND.REPLY.MODEL to TEMPDYN.  That seems to fix the problem.

Glen Shubert
[EMAIL PROTECTED]
Associate Director
TSYS - MQSeries Technical Support



"Herd, Stewart" <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>

10/30/2003 11:24 AM

Please respond to MQSeries List

       
        To:        [EMAIL PROTECTED]
        cc:        
        Subject:        Re: Mainframe monitoring - what product do you use?

Whilst Using CCC has anyone had a erroneous 'REPLY' queues accumulating when using PERMDYN for MQ, if so did you find a way to stop them appearing or a way to remove them without bouncing the QMGR or the Agent.

I am currently speaking with Candle about this but was interested in any views from the list.

Thanks

Stewart


-----Original Message-----
From: Rick Tsujimoto [
mailto:[EMAIL PROTECTED]]
Sent: 30 October 2003 15:54

To: [EMAIL PROTECTED]

Subject: Re: Mainframe monitoring - what product do you use?





Bruce,

Where is NOQDATA specified?



                      Bruce Giordano
                     <[EMAIL PROTECTED]         To:      [EMAIL PROTECTED]

                     ENTIAL.COM>                  cc:

                     Sent by: MQSeries            Subject: Re: Mainframe monitoring - what product do you use?

                     List

                     <[EMAIL PROTECTED]

                     C.AT>

                      10/30/2003 08:54 AM
                     Please respond to

                     MQSeries List





We are also using Candle Command Center now although looking at
alternatives.  To reduce the overhead, you may want to specify NOQDATA for

your application statistics and only produce queue statistics for

predefined queues.

                                           - Bruce Giordano


              "Khan, Nadi N"
             <[EMAIL PROTECTED]>                     To:

[EMAIL PROTECTED]

                                                         cc:

             Sent by: MQSeries List                      Subject:   Re:

Mainframe monitoring - what product do you use?

             <[EMAIL PROTECTED]>


              Thursday October 30, 2003 05:14 AM
             Please respond to MQSeries List





We use the candle command center for both the mainframe monitoring and
unix.

The biggest issue is the amount of cpu it uses.

We also have System automation which can be used to pick up any log

messages

and send alerts to the operators.

-----Original Message-----
From: Stubbs, Colleen H. [
mailto:[EMAIL PROTECTED]]
Sent: 30 October, 2003 00:50

To: [EMAIL PROTECTED]

Subject: Mainframe monitoring - what product do you use?


What product do you use for mainframe MQ monitoring and do you like it?

Any input is appreciated.

Thanks.

Colleen



__________________________________________________________________________________________________________________________________


For information about the Standard Bank group visit our web site
<www.standardbank.co.za>

__________________________________________________________________________________________________________________________________


Disclaimer and confidentiality note
Everything in this e-mail and any attachments relating to the official

business of Standard Bank Group Limited  is proprietary to the group.

It is confidential, legally privileged and protected by law.

Standard Bank does not own and endorse any other content. Views and

opinions are those of the sender unless clearly stated as being that of the

group.

The person addressed in the e-mail is the sole authorised recipient. Please

notify the sender immediately if it has unintentionally reached you and do

not read,

disclose or use the content in any way.

Standard Bank can not assure that the integrity of this communication has

been maintained nor that it is free of errors, virus, interception or

interference.

___________________________________________________________________________________________________________________________________

(See attached file: C.htm)

(See attached file: C.htm)


The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you

Reply via email to