| Author |
Message
|
| sebastia |
 Posted: Sun Oct 22, 2006 9:48 am Post subject: runmqsc + ALTER command |
 |
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
I was wondering ...
If I run
RUNMQSC <qmgr_name>
+
ALTER <resource name> TAG NEWVALUE
as "PERSISTENCY YES" ...
wil this new value be still be valid after a queue manager restart ?
I mean, is it FOREVER ?
Cheers. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sun Oct 22, 2006 12:42 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes.
But it only is used if the application uses MQPER_PERSISTANCE_AS_QDEF
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sebastia |
| Posted: Sun Oct 22, 2006 1:21 pm Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
can u explain a little bit more GENERAL ...
how must i "ALTER" properties
on run-time environment
so the changes are FOREVER ...
(not just until next re-boot) ...
Thankx. ! |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Sun Oct 22, 2006 1:34 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Quote: |
how must i "ALTER" properties
on run-time environment
so the changes are FOREVER ...
(not just until next re-boot) ...
|
Would you expect a DEFINE to only last for the lifetime of the queue manager? NO So why do you expect ALTER only to last the lifetime of the queue manager?
ALTER changes an MQ object definition. Once you do an ALTER it is, changed permantently (or until to issue another ALTER for that object)
I guess the question is, why would you want to ALTER an object for just the life of the queue manager?. If you really want to alter it as a temporary change, just re-issue an ALTER to revert it back just before you shut the queue manager . |
|
| Back to top |
|
|
| sebastia |
| Posted: Sun Oct 22, 2006 1:37 pm Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
well, it looked to me that DEFINE was forever,
and RUNMQSC + ALTER was a "runtime" change"
so i didn't know if it lasted
AFTER nest MQ re-start
I dont know where the MQ characteristics reside
so I can not look at them "on-line",
afte a RUNMQSC + ALTER ...
to know if they will survive the re-start ...
THANKS !
( ) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Oct 22, 2006 2:30 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sebastia wrote: |
I dont know where the MQ characteristics reside
so I can not look at them "on-line",
|
To look at them online try
| Code: |
runmqsc QMGR
display ....
....
....
end |
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sebastia |
| Posted: Mon Oct 23, 2006 4:39 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
OK - let me try to change my question ..
WHERE DOES RESIDE THE MQ DEFINITIONS ?
I mean, if a queue named Q1 has PERSISTENT messages or not,
and what is the Max message length for channel CH1 ?
are they writen on a file ?
are they in the registry (if Windows) ?
where is it written if i use UNIX ?
Thanks ! |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Mon Oct 23, 2006 4:43 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Why?
You shouldn't need to do anything with it....use the DISPLAY command.
If you really MUST know then look under the qmanager directory structure on windows. Look in the Pagesets on z/OS.
Not sure on the penguin machines.
Last edited by kevinf2349 on Mon Oct 23, 2006 4:48 am; edited 1 time in total |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 23, 2006 4:47 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sebastia wrote: |
OK - let me try to change my question ..
WHERE DOES RESIDE THE MQ DEFINITIONS ?
I mean, if a queue named Q1 has PERSISTENT messages or not,
and what is the Max message length for channel CH1 ?
are they writen on a file ?
are they in the registry (if Windows) ?
where is it written if i use UNIX ?
Thanks ! |
Depending on platform & version, all of the above.... 
Stick to using runmqsc - platform agnostic (except for z/OS) and safe to use.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Oct 23, 2006 4:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You're still having some trouble with Persistance. Persistance is strictly an attribute of an individual message, and is stored in the MQMD of that message. When a persistant message is stored, it is written into the q file in the <mq-install>/qmgrs/<qmgr_name>/<queue-name>. There is a setting on a queue, that is the default persistance. It is only used, as I said, if an application chooses to use it by setting MQPER_PERSISTANCE_AS_QDEF.
But the settings that are changed by runmqsc are stored in undocumented, private locations - as far as I know. Regardless, they are always permanent and persistant across queue manager restart. They never change unless you explicitly change them.
As long as you follow the guidelines for backing up and restoring queue managers, or running queue managers under high availability, then you do not need to care where these settings are kept or how they are stored there.
Some settings on the queue manager are stored in the qm.ini file. But not all. And not all of the settings that are in qm.ini can be changed (well, the file can be edited, but the changes won't be taken up).
Why are you really asking this, what are you really trying to do or learn?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Oct 24, 2006 1:28 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
and, its only used "at the time of the mqput"... so changing the value of the default AFTER a message is placed on the queue has no effect on messages already on the queue...just in case you were wondering .....
_________________
-wayne |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Oct 25, 2006 3:51 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Thanks, Jeff and all
I was just trying to learn, not to use those files.
Just dont like to read "values are stored in a file you dont care the name about, and we wont tell you its name", as Windows did all the time.
Knowing the name wil not hurt me, and I do no pretend to write into this file.
I have NO PROBLEM with Persistenct - I understand perfectly how it works. I only did use it as a "value" a queue has, similar to MAX_MSG_LENGTH.
Just happened to me that I did ALTER some value, and after a QM re-start the old value came back ( some other guy changed it back, I guess ) so I was trying to have a way to "look" into a file (or COPY it) to make sure the value was set into QM forever.
Now I know all my ALTER commands are forever, I am fine.
Thanks a lot. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 25, 2006 3:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's reasonable for IBM to say that certain parts of their software are nicht fur gefingerpoken und mittengraben.
You certainly wouldn't want one of your developers getting "clever" and writing code to change a queue definition by writing into the files on the fly, would you?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
