| Author |
Message
|
| anderc1 |
 Posted: Tue Oct 23, 2007 7:13 am Post subject: Suppressing Chinit auto startup |
 |
|
Acolyte
Joined: 11 Sep 2002
Posts: 55
Location: Research Triangle Park, NC
|
AIX 5.3, MQ 6.0.2.1
For DR purposes, need to prevent chinit from starting automatically. Previously (5.3) we used the QueueManagerStartup: Chinit=No stanza in the qm.ini. Using the same qm.ini, the chinit starts automatically due to the SCHINIT attribute on the Qmgr. Set it to manual, chinit doesn't start. Set it to Qmgr, it starts regardless of the QueueManagerStartup stanza. Tried variations of the command in the qm.ini; Mixed Case, UPPER CASE, and lowercase. What am I missing? |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Tue Oct 23, 2007 10:57 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
This QM attribute is set via runmqsc in MQ 6.0 using the ALTER QMGR command. Its not coded in the qm.ini file.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| anderc1 |
| Posted: Tue Oct 23, 2007 11:53 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2002
Posts: 55
Location: Research Triangle Park, NC
|
| That's what I was afraid of. It's likely a trade off, one or the other but not both. Think I'll call Level 2 support and see if they can find out why we can't have both. Thanks! |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Oct 23, 2007 11:57 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
?
There aren't any parms that I can think of that can be set in two places. That just leads to confusion. And what happens when the two settings conflict? I don't think L2 is going to give you any answers you like, but let us know!
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| anderc1 |
| Posted: Tue Oct 23, 2007 12:31 pm Post subject: |
|
|
Acolyte
Joined: 11 Sep 2002
Posts: 55
Location: Research Triangle Park, NC
|
| Just opened a PMR with a smokin severity of 4. Hate to bug those guys with something like this, but once the powers that be find out this changed (isn't working) they'd make me open a PMR anyway. I understand about setting parms in two places; but it might be nice if when you set the SCHINIT attribute to manual on the Qmgr, you could still control the chinit with the qm.ini. Yep, could get confusing. Sounds like the making of a good cert test question. I'll let you know what L2 has to say. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 23, 2007 12:48 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I guess ideally one of the values of SCHINIT would be "use qm.ini".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Oct 23, 2007 2:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| jefflowrey wrote: |
| I guess ideally one of the values of SCHINIT would be "use qm.ini". |
I only saw qmgr and manual 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 23, 2007 4:29 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| fjb_saper wrote: |
| jefflowrey wrote: |
| I guess ideally one of the values of SCHINIT would be "use qm.ini". |
I only saw qmgr and manual |
It's not an ideal world... 
I'm sure it doesn't work this way now. I strongly suspect that any change to how it works now would be along the lines of adding another possible value to SCHINIT - and not along the lines of "if SCHINIT == MANUAL THEN".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| anderc1 |
| Posted: Wed Oct 24, 2007 6:31 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2002
Posts: 55
Location: Research Triangle Park, NC
|
From IBM L2:
The runmqchi will not be automatically started for the following conditions:
.
1) When strmqm -ns is used with strmqm it Prevents any of the following
processes from starting automatically when the queue manager starts:
- channel initiator
- command server
- listeners
- services
.
2)The queue manager attribute SCHINIT has a default option SCHINIT(QMGR) if this
is changed to SCHINIT(MANUAL) then runmqchi will NOT be started automatically and
needs manual starting.
.
3) If the qm.ini is configured as follows
QueueManagerStartup:
Chinit=No
.
The default option is 'Yes', so remove this stanza or set Chinit=Yes for
runmqchi to start automatically.
----------------------------------------------------------------------------------------
I just updated the PMR to get them to verify that the qm.ini setting is still valid as I tested it and it was ignored on a production system during a DR test and it is ignored on my dev system. The strmqm -ns will resolve my issue, but think they need to tell us for sure that the Chinit=No either works in V6 or not. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 24, 2007 11:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| anderc1 wrote: |
| think they need to tell us for sure that the Chinit=No either works in V6 or not. |
It may depend on what FP level of v6 you're at, too...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| anderc1 |
| Posted: Thu Oct 25, 2007 5:54 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2002
Posts: 55
Location: Research Triangle Park, NC
|
Here's the scoop from IBM L2.
IBM Update Oct 25, 2007 6:04:00 AM -0500
In MQ V5.3 the Chinit attribute in the QueueManagerStartup stanza
within the qm.ini file was used to control whether the channel initiator
was started at queue manager startup. At MQ V6 the only use of this
attribute is to set the initial value for the SCHINIT queue
manager attribute for a queue manager which is migrated from MQ V5.3.
After the initial migration from MQ V5.3 to MQ V6 then the Chinit
attribute is thus ignored.
PRB 3374 has been corrected to reflect this information. |
|
| Back to top |
|
|
|
|
