| Author |
Message
|
| LouML |
 Posted: Mon Aug 06, 2007 9:31 am Post subject: What does the 'x' in the CONNAME mean? |
 |
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
What does an 'x' preceeding the CONNAME of the following sender channel definition mean?
bash-2.05$ echo "dis chl(CH.ME.TO.YOU) all" | runmqsc QM.aewdev.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.aewdev.01.
1 : dis chl(CH.ME.TO.YOU) all
AMQ8414: Display Channel details.
CHANNEL(CH.ME.TO.YOU) CHLTYPE(SDR)
TRPTYPE(TCP) DESCR( )
XMITQ(QX.YOU.01) MCANAME( )
MODENAME( ) TPNAME( )
BATCHSZ(50) DISCINT(6000)
SHORTRTY(10) SHORTTMR(60)
LONGRTY(999999999) LONGTMR(1200)
SCYEXIT( ) SEQWRAP(999999999)
MAXMSGL(4194304) CONVERT(YES)
SCYDATA( ) USERID( )
PASSWORD( ) MCATYPE(PROCESS)
CONNAME(x.123.123.123.123(1414)) HBINT(300)
BATCHINT(0) NPMSPEED(FAST)
SSLCIPH( ) BATCHHB(0)
LOCLADDR( ) KAINT(AUTO)
MCAUSER( ) ALTDATE(2005-09-23)
ALTTIME(15.45.03) SSLPEER()
MSGEXIT( )
SENDEXIT( )
RCVEXIT( )
MSGDATA( )
SENDDATA( )
RCVDATA( )
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$ |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Aug 06, 2007 9:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you were running a recent version of MQ (which the build number and copyright dates do not suggest, compared to similar from my v6.0.2.1 version), then it could be an IPv6 standin.
Are you using IPv6? Are you running MQ v5.3 or v6?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| LouML |
| Posted: Mon Aug 06, 2007 9:53 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
|
| Back to top |
|
|
| Michael Dag |
| Posted: Mon Aug 06, 2007 1:02 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
is this a "working" sender channel???
if not it could also be a typo 
possibly caused by using vi...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| LouML |
| Posted: Tue Aug 07, 2007 3:50 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
I just took over responsibility for this queue manager, so I'm not sure of the history. I see that there are 17 sender channels with the 'x'. I can't check the logs to see if any of them started because another overnight error cause the logs to roll over too quickly.
My guess (thanks to Michael Dag's hint) is that these are most likely obsolete channels which someone modified to prevent accidental starting, rather than just deleting. I will check with the application owner to confirm. |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Tue Aug 07, 2007 7:31 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| jefflowrey wrote: |
If you were running a recent version of MQ (which the build number and copyright dates do not suggest, compared to similar from my v6.0.2.1 version), then it could be an IPv6 standin.
Are you using IPv6? Are you running MQ v5.3 or v6? |
IPv6 addresses contain colons, such as ffff::123.123.123.123
Regards
Hubert
_________________
Regards
Hubert |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 07, 2007 7:50 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| HubertKleinmanns wrote: |
| IPv6 addresses contain colons, such as ffff::123.123.123.123 |
I agree. I considered it possible that "x" was a display bug of some kind, from something that wasn't expecting an IPv6 address being given one.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
