Discussion:
Does enabling performance events require an MQ bounce at all?
Costa, D. (Damian)
2014-04-16 08:45:50 UTC
Permalink
HI y'all,
Question is in the topic line......
Nuff sed.
Caio.


********************
Nedbank Limited Reg No 1951/000009/06. The following link displays
the names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ]
This email is confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Thomas Dunlap
2014-04-16 09:23:45 UTC
Permalink
Damian,

I believe all you have to do is alter the queue manager attributes and
they take effect immediately.

Cheers,
Tom
Post by Costa, D. (Damian)
HI y'all,
Question is in the topic line......
Nuff sed.
Caio.
********************
Nedbank Limited Reg No 1951/000009/06. The following link displays
the names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ]
This email is confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
--
_______________________________________________________________
Regards,
Thomas Dunlap Chief Technology Officer tomd-lQL1WHg3ccB8UrSeD/***@public.gmane.org
Themis, Inc. http://www.themisinc.com 1 (800) 756-3000

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Potkay, Peter M (CTO Architecture + Engineering)
2014-04-16 16:59:50 UTC
Permalink
In general, if you can change the QM property via runmqsc, its dynamic, but if it's something that's controlled by qm.ini or mqs.ini, then it requires a QM restart.

Hmm, would be nice to have a REFRESH QMINI command....



Peter Potkay

-----Original Message-----
From: MQSeries List [mailto:MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org] On Behalf Of Thomas Dunlap
Sent: Wednesday, April 16, 2014 5:24 AM
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Subject: Re: Does enabling performance events require an MQ bounce at all?

Damian,

I believe all you have to do is alter the queue manager attributes and they take effect immediately.

Cheers,
Tom
Post by Costa, D. (Damian)
HI y'all,
Question is in the topic line......
Nuff sed.
Caio.
********************
Nedbank Limited Reg No 1951/000009/06. The following link displays the
names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ] This email is
confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided
in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
--
_______________________________________________________________
Regards,
Thomas Dunlap Chief Technology Officer tomd-lQL1WHg3ccB8UrSeD/***@public.gmane.org
Themis, Inc. http://www.themisinc.com 1 (800) 756-3000

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and, in the message body (not the subject), write: SIGNOFF MQSERIES Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
T.Rob
2014-04-16 18:50:06 UTC
Permalink
X-Originating-IP: 184.154.225.7
X-SpamExperts-Domain: siteground247.com
X-SpamExperts-Username: 184.154.225.7
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: SB/global_tokens (0.00353748081236)
X-Recommended-Action: accept
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379,
Antispam-Data: 2014.4.16.182419
X-PMX-Spam: Gauge= Probability=9%, Report='
AT_TLD 0.1, REPLYTO_FROM_DIFF_ADDY 0.1, FROM_NAME_ONE_WORD 0.05, HTML_00_01 0.05, HTML_00_10 0.05, BODY_SIZE_5000_5999 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, FORGED_MUA_OUTLOOK 0, URI_ENDS_IN_HTML 0, WEBMAIL_SOURCE 0, WEBMAIL_XOIP 0, WEBMAIL_X_IP_HDR 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __C230066_P5 0, __CP_MEDIA_BODY 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_LIST_HEADER 0, __HAS_LIST_HELP 0, __HAS_LIST_SUBSCRIBE 0, __HAS_LIST_UNSUBSCRIBE 0, __HAS_MSGID 0, __HAS_REPLYTO 0, __HAS_X_MAILER 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __OUTLOOK_MUA 0, __OUTLOOK_MUA_1 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_NS , __USER_AGENT_MS_GENERIC 0'
Sender: MQSeries List <MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org>
In-Reply-To: <11721_1397667623_1397667623_9BB766F505133C498D6D60FB74AA403C2E5C1057-Sa/7lAhLIlFOSYu4ox5p5Tfn7f/***@public.gmane.org>
Precedence: list
List-Help: <http://listserv.meduniwien.ac.at/cgi-bin/wa?LIST=MQSERIES>,
<mailto:LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org?body=INFO%20MQSERIES>
List-Unsubscribe: <mailto:MQSERIES-unsubscribe-request-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org>
List-Subscribe: <mailto:MQSERIES-subscribe-request-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org>
List-Owner: <mailto:MQSERIES-request-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org>
List-Archive: <http://listserv.meduniwien.ac.at/cgi-bin/wa?LIST=MQSERIES>
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2014.4.16.184222
Archived-At: <http://permalink.gmane.org/gmane.network.mq.devel/17687>

Part of the strategy in moving things from the QM.ini to the QMgr as
attributes has specifically been to distinguish between those items that can
be made to be dynamic vs. those that cannot or should not. You cannot
easily update exits or pluggable services on the fly, for example. Even
where that level of refresh is technically possible, it introduces too much
risk and too large a code path to add that support to a QMgr, especially
after decades of tuning and optimization.

Other things such as the size of the error or transaction logs introduce a
security exposure if they can be changed without a restart. To erase
evidence of an attack, first minimize the log extents, then reset them to
the original values.

The REFRESH SECURITY TYPE(SSL) actually drops the cached in-memory image of
the keystore and any revocation checks and reloads them. That's why all the
connections using those assets must stop to execute the refresh.
Unfortunately, that's also why it's been necessary to bounce the QMgr to do
that refresh at almost every client I've ever consulted for. That was a
case where making it dynamic created an expectation that usually cannot be
met and was probably a bad decision.

What's left in the qm.ini that you'd reasonably want to make dynamic?


Kind regards,
-- T.Rob

T.Robert Wyatt, Managing partner
IoPT Consulting, LLC
+1 704-443-TROB
https://ioptconsulting.com
https://twitter.com/tdotrob
Post by Potkay, Peter M (CTO Architecture + Engineering)
-----Original Message-----
Of Potkay, Peter M (CTO Architecture + Engineering)
Sent: Wednesday, April 16, 2014 13:00 PM
Subject: Re: Does enabling performance events require an MQ bounce at all?
In general, if you can change the QM property via runmqsc, its dynamic,
but if it's something that's controlled by qm.ini or mqs.ini, then it
requires a QM restart.
Hmm, would be nice to have a REFRESH QMINI command....
Peter Potkay
-----Original Message-----
Of Thomas Dunlap
Sent: Wednesday, April 16, 2014 5:24 AM
Subject: Re: Does enabling performance events require an MQ bounce at all?
Damian,
I believe all you have to do is alter the queue manager attributes and
they take effect immediately.
Cheers,
Tom
Post by Costa, D. (Damian)
HI y'all,
Question is in the topic line......
Nuff sed.
Caio.
********************
Nedbank Limited Reg No 1951/000009/06. The following link displays the
names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ] This email is
confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided
in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
--
_______________________________________________________________
Regards,
Themis, Inc. http://www.themisinc.com 1 (800) 756-3000
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv
General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
************************************************************
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you
are not the intended recipient, please notify the sender immediately by
return e-mail, delete this communication and destroy all copies.
************************************************************
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv
General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Neil Casey
2014-04-16 22:32:44 UTC
Permalink
Hi T.Rob,

I’d like to see queue buffer tuning outside of qm.ini, and not requiring 2 QM restarts and redefinition of each queue.

I raised an RFE about it back in 2012, but it has languished ever since.
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=35063


Neil
--
Neil Casey
Senior Consultant | Syntegrity Solutions

+61 414 615 334 neil.casey-VLLIzlmz+***@public.gmane.org
Syntegrity Solutions Pty Ltd | Level 23 | 40 City Road | Southgate | VIC 3006
Analyse >> Integrate >> Secure >> Educate
Post by T.Rob
Part of the strategy in moving things from the QM.ini to the QMgr as
attributes has specifically been to distinguish between those items that can
be made to be dynamic vs. those that cannot or should not. You cannot
easily update exits or pluggable services on the fly, for example. Even
where that level of refresh is technically possible, it introduces too much
risk and too large a code path to add that support to a QMgr, especially
after decades of tuning and optimization.
Other things such as the size of the error or transaction logs introduce a
security exposure if they can be changed without a restart. To erase
evidence of an attack, first minimize the log extents, then reset them to
the original values.
The REFRESH SECURITY TYPE(SSL) actually drops the cached in-memory image of
the keystore and any revocation checks and reloads them. That's why all the
connections using those assets must stop to execute the refresh.
Unfortunately, that's also why it's been necessary to bounce the QMgr to do
that refresh at almost every client I've ever consulted for. That was a
case where making it dynamic created an expectation that usually cannot be
met and was probably a bad decision.
What's left in the qm.ini that you'd reasonably want to make dynamic?
Kind regards,
-- T.Rob
T.Robert Wyatt, Managing partner
IoPT Consulting, LLC
+1 704-443-TROB
https://ioptconsulting.com
https://twitter.com/tdotrob
Post by Potkay, Peter M (CTO Architecture + Engineering)
-----Original Message-----
Of Potkay, Peter M (CTO Architecture + Engineering)
Sent: Wednesday, April 16, 2014 13:00 PM
Subject: Re: Does enabling performance events require an MQ bounce at all?
In general, if you can change the QM property via runmqsc, its dynamic,
but if it's something that's controlled by qm.ini or mqs.ini, then it
requires a QM restart.
Hmm, would be nice to have a REFRESH QMINI command....
Peter Potkay
-----Original Message-----
Of Thomas Dunlap
Sent: Wednesday, April 16, 2014 5:24 AM
Subject: Re: Does enabling performance events require an MQ bounce at all?
Damian,
I believe all you have to do is alter the queue manager attributes and
they take effect immediately.
Cheers,
Tom
Post by Costa, D. (Damian)
HI y'all,
Question is in the topic line......
Nuff sed.
Caio.
********************
Nedbank Limited Reg No 1951/000009/06. The following link displays the
names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ] This email is
confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided
in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
--
_______________________________________________________________
Regards,
Themis, Inc. http://www.themisinc.com 1 (800) 756-3000
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv
General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
************************************************************
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you
are not the intended recipient, please notify the sender immediately by
return e-mail, delete this communication and destroy all copies.
************************************************************
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv
General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
George Carey
2014-04-17 01:14:43 UTC
Permalink
These would be a very useful RFE.

Buffer tuning can make huge performance improvement

But the manner in which the buffer tuning is configured is , as has been
stated by others as well, a complete kludge and an obvious after thought
that was never properly implemented.



GTC



From: MQSeries List [mailto:MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org] On Behalf Of
Neil Casey
Sent: Wednesday, April 16, 2014 6:33 PM
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Subject: Re: Does enabling performance events require an MQ bounce at all?



Hi T.Rob,



I'd like to see queue buffer tuning outside of qm.ini, and not requiring 2
QM restarts and redefinition of each queue.



I raised an RFE about it back in 2012, but it has languished ever since.

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe
<http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=35063>
&CR_ID=35063





Neil
--
Neil Casey
Senior Consultant | Syntegrity Solutions

+61 414 615 334 <tel:+61%20414%20615%20334>
<mailto:neil.casey-VLLIzlmz+***@public.gmane.org> neil.casey-VLLIzlmz+***@public.gmane.org

Syntegrity Solutions Pty Ltd <http://www.syntegrity.com.au/> | Level 23 |
40 City Road | Southgate | VIC 3006

Analyse >> Integrate >> Secure >> Educate





On 17 Apr 2014, at 4:50 am, T.Rob <t.rob-CkT6zf+urXSzW/GOMZKyElesiRL1/***@public.gmane.org> wrote:




Part of the strategy in moving things from the QM.ini to the QMgr as
attributes has specifically been to distinguish between those items that can
be made to be dynamic vs. those that cannot or should not. You cannot
easily update exits or pluggable services on the fly, for example. Even
where that level of refresh is technically possible, it introduces too much
risk and too large a code path to add that support to a QMgr, especially
after decades of tuning and optimization.

Other things such as the size of the error or transaction logs introduce a
security exposure if they can be changed without a restart. To erase
evidence of an attack, first minimize the log extents, then reset them to
the original values.

The REFRESH SECURITY TYPE(SSL) actually drops the cached in-memory image of
the keystore and any revocation checks and reloads them. That's why all the
connections using those assets must stop to execute the refresh.
Unfortunately, that's also why it's been necessary to bounce the QMgr to do
that refresh at almost every client I've ever consulted for. That was a
case where making it dynamic created an expectation that usually cannot be
met and was probably a bad decision.

What's left in the qm.ini that you'd reasonably want to make dynamic?


Kind regards,
-- T.Rob

T.Robert Wyatt, Managing partner
IoPT Consulting, LLC
+1 704-443-TROB
https://ioptconsulting.com
https://twitter.com/tdotrob




-----Original Message-----
From: MQSeries List [mailto:MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org] On Behalf
Of Potkay, Peter M (CTO Architecture + Engineering)
Sent: Wednesday, April 16, 2014 13:00 PM
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Subject: Re: Does enabling performance events require an MQ bounce at all?

In general, if you can change the QM property via runmqsc, its dynamic,
but if it's something that's controlled by qm.ini or mqs.ini, then it
requires a QM restart.

Hmm, would be nice to have a REFRESH QMINI command....



Peter Potkay

-----Original Message-----
From: MQSeries List [mailto:MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org] On Behalf
Of Thomas Dunlap
Sent: Wednesday, April 16, 2014 5:24 AM
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Subject: Re: Does enabling performance events require an MQ bounce at all?

Damian,

I believe all you have to do is alter the queue manager attributes and
they take effect immediately.

Cheers,
Tom


On 4/16/2014 4:45 AM, Costa, D. (Damian) wrote:



HI y'all,
Question is in the topic line......
Nuff sed.
Caio.


********************
Nedbank Limited Reg No 1951/000009/06. The following link displays the
names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ] This email is
confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and, in
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided
in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html



--
_______________________________________________________________
Regards,
Thomas Dunlap Chief Technology Officer tomd-lQL1WHg3ccB8UrSeD/***@public.gmane.org
Themis, Inc. http://www.themisinc.com 1 (800) 756-3000

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and, in the
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv
General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
************************************************************
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you
are not the intended recipient, please notify the sender immediately by
return e-mail, delete this communication and destroy all copies.
************************************************************

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and, in the
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv
General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html


To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html





_____

List Archive <http://listserv.meduniwien.ac.at/archives/mqser-l.html> -
Manage Your List Settings
<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> -
Unsubscribe
<mailto:LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org?subject=Unsubscribe&BODY=signoff%
20mqseries>

Instructions for managing your mailing list subscription are provided in the
Listserv General Users Guide available at http://www.lsoft.com
<http://www.lsoft.com/resources/manuals.asp>


To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Neil Casey
2014-04-17 01:34:11 UTC
Permalink
Thanks George,

I checked again, and it was actually 2013, but that’s not really significant I guess.

Happy to have you vote for it of course. The more votes, the more likely it is to be considered I guess. At least it hasn’t been denied (yet). :-)


Regards,


Neil
--
Neil Casey
Senior Consultant | Syntegrity Solutions

+61 414 615 334 neil.casey-VLLIzlmz+***@public.gmane.org
Syntegrity Solutions Pty Ltd | Level 23 | 40 City Road | Southgate | VIC 3006
Analyse >> Integrate >> Secure >> Educate
Post by George Carey
These would be a very useful RFE.
Buffer tuning can make huge performance improvement
But the manner in which the buffer tuning is configured is , as has been stated by others as well, a complete kludge and an obvious after thought that was never properly implemented.
GTC
Sent: Wednesday, April 16, 2014 6:33 PM
Subject: Re: Does enabling performance events require an MQ bounce at all?
Hi T.Rob,
I’d like to see queue buffer tuning outside of qm.ini, and not requiring 2 QM restarts and redefinition of each queue.
I raised an RFE about it back in 2012, but it has languished ever since.
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=35063
Neil
--
Neil Casey
Senior Consultant | Syntegrity Solutions
Syntegrity Solutions Pty Ltd | Level 23 | 40 City Road | Southgate | VIC 3006
Analyse >> Integrate >> Secure >> Educate
<image003.png>
Part of the strategy in moving things from the QM.ini to the QMgr as
attributes has specifically been to distinguish between those items that can
be made to be dynamic vs. those that cannot or should not. You cannot
easily update exits or pluggable services on the fly, for example. Even
where that level of refresh is technically possible, it introduces too much
risk and too large a code path to add that support to a QMgr, especially
after decades of tuning and optimization.
Other things such as the size of the error or transaction logs introduce a
security exposure if they can be changed without a restart. To erase
evidence of an attack, first minimize the log extents, then reset them to
the original values.
The REFRESH SECURITY TYPE(SSL) actually drops the cached in-memory image of
the keystore and any revocation checks and reloads them. That's why all the
connections using those assets must stop to execute the refresh.
Unfortunately, that's also why it's been necessary to bounce the QMgr to do
that refresh at almost every client I've ever consulted for. That was a
case where making it dynamic created an expectation that usually cannot be
met and was probably a bad decision.
What's left in the qm.ini that you'd reasonably want to make dynamic?
Kind regards,
-- T.Rob
T.Robert Wyatt, Managing partner
IoPT Consulting, LLC
+1 704-443-TROB
https://ioptconsulting.com
https://twitter.com/tdotrob
-----Original Message-----
Of Potkay, Peter M (CTO Architecture + Engineering)
Sent: Wednesday, April 16, 2014 13:00 PM
Subject: Re: Does enabling performance events require an MQ bounce at all?
In general, if you can change the QM property via runmqsc, its dynamic,
but if it's something that's controlled by qm.ini or mqs.ini, then it
requires a QM restart.
Hmm, would be nice to have a REFRESH QMINI command....
Peter Potkay
-----Original Message-----
Of Thomas Dunlap
Sent: Wednesday, April 16, 2014 5:24 AM
Subject: Re: Does enabling performance events require an MQ bounce at all?
Damian,
I believe all you have to do is alter the queue manager attributes and
they take effect immediately.
Cheers,
Tom
HI y'all,
Question is in the topic line......
Nuff sed.
Caio.
********************
Nedbank Limited Reg No 1951/000009/06. The following link displays the
names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ] This email is
confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided
in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
--
_______________________________________________________________
Regards,
Themis, Inc. http://www.themisinc.com 1 (800) 756-3000
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv
General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
************************************************************
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you
are not the intended recipient, please notify the sender immediately by
return e-mail, delete this communication and destroy all copies.
************************************************************
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv
General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Potkay, Peter M (CTO Architecture + Engineering)
2014-04-17 12:06:51 UTC
Permalink
Being able to fiddle with the Max Active Channels parameter without having to restart the QM would be nice. Not that this is something that needs to be played with often, but when you find yourself in a situation where you have to up this value, adding a QM restart on top of everything else that is going wrong for you that night is just the icing on the cake!

Peter Potkay

-----Original Message-----
From: MQSeries List [mailto:MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org] On Behalf Of T.Rob
Sent: Wednesday, April 16, 2014 2:50 PM
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Subject: Re: Does enabling performance events require an MQ bounce at all?

Part of the strategy in moving things from the QM.ini to the QMgr as attributes has specifically been to distinguish between those items that can be made to be dynamic vs. those that cannot or should not. You cannot easily update exits or pluggable services on the fly, for example. Even where that level of refresh is technically possible, it introduces too much risk and too large a code path to add that support to a QMgr, especially after decades of tuning and optimization.

Other things such as the size of the error or transaction logs introduce a security exposure if they can be changed without a restart. To erase evidence of an attack, first minimize the log extents, then reset them to the original values.

The REFRESH SECURITY TYPE(SSL) actually drops the cached in-memory image of the keystore and any revocation checks and reloads them. That's why all the connections using those assets must stop to execute the refresh.
Unfortunately, that's also why it's been necessary to bounce the QMgr to do that refresh at almost every client I've ever consulted for. That was a case where making it dynamic created an expectation that usually cannot be met and was probably a bad decision.

What's left in the qm.ini that you'd reasonably want to make dynamic?


Kind regards,
-- T.Rob

T.Robert Wyatt, Managing partner
IoPT Consulting, LLC
+1 704-443-TROB
https://ioptconsulting.com
https://twitter.com/tdotrob
Post by Potkay, Peter M (CTO Architecture + Engineering)
-----Original Message-----
Behalf Of Potkay, Peter M (CTO Architecture + Engineering)
Sent: Wednesday, April 16, 2014 13:00 PM
Subject: Re: Does enabling performance events require an MQ bounce at all?
In general, if you can change the QM property via runmqsc, its
dynamic, but if it's something that's controlled by qm.ini or mqs.ini,
then it requires a QM restart.
Hmm, would be nice to have a REFRESH QMINI command....
Peter Potkay
-----Original Message-----
Behalf Of Thomas Dunlap
Sent: Wednesday, April 16, 2014 5:24 AM
Subject: Re: Does enabling performance events require an MQ bounce at all?
Damian,
I believe all you have to do is alter the queue manager attributes and
they take effect immediately.
Cheers,
Tom
Post by Costa, D. (Damian)
HI y'all,
Question is in the topic line......
Nuff sed.
Caio.
********************
Nedbank Limited Reg No 1951/000009/06. The following link displays
the names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ] This email
is confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are
provided in the Listserv General Users Guide available at
http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
--
_______________________________________________________________
Regards,
Themis, Inc. http://www.themisinc.com 1 (800) 756-3000
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided
in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
************************************************************
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If
you are not the intended recipient, please notify the sender
immediately by return e-mail, delete this communication and destroy all copies.
************************************************************
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided
in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and, in the message body (not the subject), write: SIGNOFF MQSERIES Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Bob Juch
2014-04-17 13:35:26 UTC
Permalink
Peter,

You can on the mainframe.

Bob Juch
Juch Services LLC

On Thu, Apr 17, 2014 at 8:06 AM, Potkay, Peter M (CTO Architecture +
Post by Potkay, Peter M (CTO Architecture + Engineering)
Being able to fiddle with the Max Active Channels parameter without having
to restart the QM would be nice. Not that this is something that needs to
be played with often, but when you find yourself in a situation where you
have to up this value, adding a QM restart on top of everything else that
is going wrong for you that night is just the icing on the cake!
Peter Potkay
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Loading...