| Author |
Message
|
| NotMe |
 Posted: Thu Dec 03, 2009 12:02 pm Post subject: Problem creating CLNTCONN Channel AMQ8425 |
 |
|
Apprentice
Joined: 25 Nov 2009
Posts: 26
|
I'm attempting to create a CLNTCONN Channel but I keep getting a AMQ8425 error. Has anyone experienced this? I've searched the web and other forums but could not find anything that was very helpful. Thanks in advance...
1 : DEFINE CHANNEL ('SYSTEM.DEF.SVRCONN') CHLTYPE(CLNTCONN) +
: TRPTYPE(TCP) +
: CONNAME(' ') +
: LOCLADDR(' ') +
: DESCR(' ') +
: HBINT(300) +
: MAXMSGL(4194304) +
: QMNAME(' ') +
: RCVDATA(' ') +
: RCVEXIT(' ') +
: SCYDATA(' ') +
: SCYEXIT(' ') +
: SENDDATA(' ') +
: SENDEXIT(' ') +
: USERID(' ') +
: SSLCIPH(' ') +
: SSLPEER(' ') +
: KAINT(AUTO) +
: COMPMSG(NONE) +
: COMPHDR(NONE) +
: SHARECNV(10) +
: AFFINITY(PREFERRED) +
: CLNTWGHT(0) +
: REPLACE
AMQ8425: Attribute value error. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Dec 03, 2009 12:10 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
One of the attributes is wrong. 
My tip - create a new client pair rather than use the SYSTEM ones. It's best practice not to use SYSTEM objects and there's less to specify. Most of which you don't need, and some of that IIRC isn't valid on a CLNTCONN.
(Not looked it up, could be mistaken there).
Anyway, define a new pair. If you insist on specifying all the attributes and get this error remove one at a time until it works.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Dec 03, 2009 12:12 pm Post subject: Re: Problem creating CLNTCONN Channel AMQ8425 |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| I don't suppose it makes sense to have a blank CONNAME in a CLNTCONN. What happens if you fill in a value for this field? |
|
| Back to top |
|
|
| NotMe |
| Posted: Thu Dec 03, 2009 12:19 pm Post subject: |
|
|
Apprentice
Joined: 25 Nov 2009
Posts: 26
|
My tip - create a new client pair rather than use the SYSTEM ones. It's best practice not to use SYSTEM objects and there's less to specify. Most of which you don't need, and some of that IIRC isn't valid on a CLNTCONN.
I realize it's not best practices to use SYSTEM objects but per the below link I have to do it this way.
http://www.ibm.com/developerworks/websphere/library/techarticles/0704_xu/0704_xu.html
When I change SVRCONN in the name definition to CLNTCONN it works. Does this make sense?
1 : DEFINE CHANNEL ('SYSTEM.DEF.CLNTCONN') CHLTYPE(CLNTCONN) +
: TRPTYPE(TCP) +
: CONNAME(' ') +
: LOCLADDR(' ') +
: DESCR(' ') +
: HBINT(300) +
: MAXMSGL(4194304) +
: QMNAME(' ') +
: RCVDATA(' ') +
: RCVEXIT(' ') +
: SCYDATA(' ') +
: SCYEXIT(' ') +
: SENDDATA(' ') +
: SENDEXIT(' ') +
: USERID(' ') +
: SSLCIPH(' ') +
: SSLPEER(' ') +
: KAINT(AUTO) +
: COMPMSG(NONE) +
: COMPHDR(NONE) +
: SHARECNV(10) +
: AFFINITY(PREFERRED) +
: CLNTWGHT(0) +
: REPLACE
AMQ8014: WebSphere MQ channel created. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 03, 2009 12:22 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Fair point. Clearly some kind of WAS restriction I wasn't aware of.
| NotMe wrote: |
| When I change SVRCONN in the name definition to CLNTCONN it works. Does this make sense? |
Yes. These are 2 different types of channel with different attributes and uses.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| NotMe |
| Posted: Thu Dec 03, 2009 12:30 pm Post subject: |
|
|
Apprentice
Joined: 25 Nov 2009
Posts: 26
|
[quote="Vitor"]
| NotMe wrote: |
| Yes. These are 2 different types of channel with different attributes and uses. |
I realize they are two different channels but in order for my MQClient connection to work I need a SVRCONN Channel and CLNTCONN channel defined with the same name as I understand it. Is this not correct? |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Dec 03, 2009 12:35 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
Your CLNTCONN will have to have the same name as your SVRCONN. Therefore as per that web page you have to name your CLNTCONN with the incongruous name of SYSTEM.DEF.SVRCONN.
Is it really true that only this channel name can be used? I don't see why any software other than MQ cares what channel names are chosen for its client connections. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 03, 2009 12:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| NotMe wrote: |
| I realize they are two different channels but in order for my MQClient connection to work I need a SVRCONN Channel and CLNTCONN channel defined with the same name as I understand it. Is this not correct? |
Correct in all respects.
But they're not the same type of channel, and take different attibutes. So if you specify AFFINTY for a SVRCONN that's not valid and the command fails, but if you specify it for a CLNTCONN that's fine.
It's all laid out here. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 03, 2009 12:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mvic wrote: |
| Is it really true that only this channel name can be used? I don't see why any software other than MQ cares what channel names are chosen for its client connections. |
News to me, and I have my fingers crossed that someone will post some information on it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| NotMe |
| Posted: Thu Dec 03, 2009 12:51 pm Post subject: |
|
|
Apprentice
Joined: 25 Nov 2009
Posts: 26
|
[quote="Vitor"]
| NotMe wrote: |
But they're not the same type of channel, and take different attibutes. So if you specify AFFINTY for a SVRCONN that's not valid and the command fails, but if you specify it for a CLNTCONN that's fine. |
I think if you look at both examples you can see that I am defining a CLNTCONN channel with all CLNTCONN channel attributes. The difference is the name of the channel would should not matter. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Dec 03, 2009 1:28 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
That article is more than two years old and almost certainly incorrect in the first place that you have to use SYSTEM.DEF.SVRCONN at all. Best bet is to open a PMR with the WAS team and ask them to confirm this.
The name of the channel should have no bearing on whether the DEF CHANNEL fails with an AMQ8425.
Something is going wrong here that is not obvious from the data you have posted. Perhaps you are changing non-printable characters or otherwise making the script more different than you think it is when you changed the name.
You're going to need to specify the CONNAME and the QMNAME attributes on the CLNTCONN if you want it to be useful, btw. The QMNAME is used to identify which channel definition in the CCDT should be used and the CONNAME says where the other end of the channel is. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 03, 2009 1:53 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| The QMNAME is used to identify which channel definition... |
Adding to the confusion, QMNAME in a CCDT can also be used to specify a groups of qmgrs eligible for connection. There's a delightful Hursley piece on this.
_________________
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 |
|
|
| NotMe |
| Posted: Fri Dec 04, 2009 5:18 am Post subject: |
|
|
Apprentice
Joined: 25 Nov 2009
Posts: 26
|
| mqjeff wrote: |
You're going to need to specify the CONNAME and the QMNAME attributes on the CLNTCONN if you want it to be useful, btw. |
You are right. I put a value in the CONNAME and the channel was created. It appears that MQ 7.0.1 will not allow the creation of any CLNTCONN channels without a value in CONNAME. I'm not sure if previous versions have the same restriction. Thanks again MQJeff |
|
| Back to top |
|
|
| mvic |
| Posted: Fri Dec 04, 2009 5:32 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
|
| Back to top |
|
|
|
|
