| Author |
Message
|
| bkiran2020 |
 Posted: Fri Jul 05, 2013 1:45 am Post subject: unable to create a SVRCONN channel |
 |
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
We are unable to create a SVRCONN channel on the MQ v7.0.1 server since the default SVRCONN channel is missing.
By using the strmqm -c QMGR we can resolve this issues but this PROD server
So please suggest any other option.  |
|
| Back to top |
|
 |
| zpat |
| Posted: Fri Jul 05, 2013 1:58 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You can just re-define that default object using MQSC, but you need to code every single parameter on the DEFINE command.
If you leave any parameter out - it tries to find the default object which does not (yet) exist. |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Jul 05, 2013 3:05 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Find another queue manager where the SVRCONN is defined, dump the object attributes using the tool appropriate to the version you are using, then run in the definition to the queue manager on which it's missing.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bkiran2020 |
| Posted: Fri Jul 05, 2013 5:49 am Post subject: |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
| exerk wrote: |
| Find another queue manager where the SVRCONN is defined, dump the object attributes using the tool appropriate to the version you are using, then run in the definition to the queue manager on which it's missing. |
thanks the issue resolved.
small doubt like if some one has deleted the channel or default svrconn is not created.
 |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Jul 05, 2013 5:56 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| exerk wrote: |
| ...using the tool appropriate to the version you are using... |
Means use MS03-SAVEQMGR for WMQ 7.0.1 and below, for WMQ 7.1 and up use dmpmqcfg administrative command.
Don't delete default objects and have no doubts... Restrict administrative access and maintain control of your environment? Could be a good idea...
btw, using one of these tools to grab and version a copy of your Qmgr definitions every so often would be a good idea. You might even consider backing up those files... |
|
| Back to top |
|
|
| bkiran2020 |
| Posted: Fri Jul 05, 2013 7:23 am Post subject: |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
| JosephGramig wrote: |
| exerk wrote: |
| ...using the tool appropriate to the version you are using... |
Means use MS03-SAVEQMGR for WMQ 7.0.1 and below, for WMQ 7.1 and up use dmpmqcfg administrative command.
Don't delete default objects and have no doubts... Restrict administrative access and maintain control of your environment? Could be a good idea...
btw, using one of these tools to grab and version a copy of your Qmgr definitions every so often would be a good idea. You might even consider backing up those files... |
yes, we are taking the object backup using saveqmgr (autosys job).
But my doubt is there any chance of creating QMGR with some default object missing. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jul 05, 2013 7:29 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| bkiran2020 wrote: |
| But my doubt is there any chance of creating QMGR with some default object missing. |
I've never seen this behavior - a random system object definition missing at qmgr creation.
I've often seen errant sysadmins delete system- and other- object definitions in the mistaken belief that he/she was doing a good deed.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| hughson |
| Posted: Tue Jul 09, 2013 3:04 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| bkiran2020 wrote: |
| small doubt like if some one has deleted the channel or default svrconn is not created. |
It is a common practice that I have seen to delete the default SVRCONN channel to ensure no-one can connect into it, since the SYSTEM.DEF.SVRCONN is a fully functioning SVRCONN object. Please ensure when you reinstate it that you also secure it. Quickest way would be to put some rubbish into the MCAUSER field.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jul 09, 2013 4:16 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| hughson wrote: |
| Quickest way would be to put some rubbish into the MCAUSER field. |
This would be the preferred and recommended procedure, rather than deleting the SVRCONN channel.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
