ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Mainframe, CICS, TXSeries » CSQX514E xxS2 CSQXPING Channel xxS2.YYY.xxSE.INQ01 is active

Post new topic  Reply to topic
 CSQX514E xxS2 CSQXPING Channel xxS2.YYY.xxSE.INQ01 is active « View previous topic :: View next topic » 
Author Message
aahmad8
PostPosted: Sun Jan 13, 2008 2:41 pm    Post subject: CSQX514E xxS2 CSQXPING Channel xxS2.YYY.xxSE.INQ01 is active Reply with quote

Apprentice

Joined: 12 Sep 2005
Posts: 27
Location: Malaysia
Below are brief information about my channel connectivity between alpha (cross domain).

Name Type Disposition Status
xxS2.YYY.xxSE* CHANNEL QMGR xxS2
xxS2.YYY.xxSE.INQ01 SENDER QMGR xxS2 BIND

Name Type Disposition Status
xxS2.YYY* CHANNEL QMGR xxSE
xxS2.YYY.xxSE.INQ01 RECEIVER QMGR xxSE INACTIVE

CSQX514E xxS2 CSQXPING Channel xxS2.YYY.xxSE.INQ01 is active on xxS2
CSQ9023E xxS2 CSQXCRPS ' PING CHANNEL' ABNORMAL COMPLETION

Channel name . . . . . . . : xxS2.YYY.xxSE.INQ01
Channel type . . . . . . . : SENDER
Description . . . . . . . . : Sender channel to send message to xxSE

Disposition . . . . . . . . . P P=Private on XXS2
A=Shared on any queue manager

Stop mode . . . . . . . . . . 2 1. Quiesce 2. Force
Stop status . . . . . . . . . 2 1. Stopped 2. Inactive

Queue manager . . . . . . . .
Connection name . . . . . . .


EssssssssssssssssssssssssssssssssssssssssssssssssssssssssssN
e CSQ9022I xxS2 CSQXCRPS ' STOP CHANNEL' NORMAL COMPLETION e
DssssssssssssssssssssssssssssssssssssssssssssssssssssssssssM

Name Type Disposition Status
xxS2.YYY.xxSE* CHANNEL QMGR xxS2
xxS2.YYY.xxSE.INQ01 SENDER QMGR xxS2 BIND


xxS2 DIS CHS(xxS2.YYY.xxSE.INQ01)
CSQM134I xxS2 CSQMDCST DIS CHS(xxS2.YYY.xxSE.INQ01) COMMAND ACCEPTED
CSQM293I xxS2 CSQXDMSG 1 CHSTATUS FOUND MATCHING REQUEST CRITERIA
CSQM201I xxS2 CSQXDMSG DIS CHSTATUS DETAILS
CHSTATUS(xxS2.SOA.xxSE.INQ01)
CHLDISP(PRIVATE)
XMITQ(XXXX.YYY.RPL.INQ.XQ.01)
CONNAME(ZZZ6xxSE)
CURRENT
STATUS(BINDING)
STOPREQ(NO)
RQMNAME(xxSE)
END CHSTATUS DETAILS
CSQ9022I xxS2 CSQXDMSG ' DIS CHSTATUS' NORMAL COMPLETION


xxS2 DIS QL(XXXX.YYY.RPL.INQ.XQ.01) ALL
CSQM293I xxS2 CSQMDMSG 1 QLOCAL FOUND MATCHING REQUEST CRITERIA
CSQM201I xxS2 CSQMDMSG DIS QLOCAL DETAILS
QUEUE(XXXX.YYY.RPL.INQ.XQ.01)
TYPE(QLOCAL)
QSGDISP(QMGR)
STGCLASS(REMOTE)
PSID(3)
CFSTRUCT( )
CLUSTER( )
CLUSNL( )
DESCR(Transmit queue to send message to xxSE)
PUT(ENABLED)
DEFPRTY(0)
DEFPSIST(NO)
OPPROCS(1)
IPPROCS(1)
CURDEPTH(4)
MAXDEPTH(999999999)
PROCESS(XXXX.YYY.RPL.INQ.PR.01)
TRIGGER
MAXMSGL(4194304)
BOTHRESH(0)
BOQNAME( )
INITQ(SYSTEM.CHANNEL.INITQ)
USAGE(XMITQ)
SHARE
DEFSOPT(SHARED)
MSGDLVSQ(PRIORITY)
RETINTVL(999999999)
TRIGTYPE(FIRST)
TRIGDPTH(1)
TRIGMPRI(0)
TRIGDATA(xxS2.YYY.xxSE.INQ.01)
DEFTYPE(PREDEFINED)
NOHARDENBO
CRDATE(2004-03-14)
CRTIME(15.24.20)
GET(ENABLED)
QDEPTHHI(80)
QDEPTHLO(40)
QDPMAXEV(ENABLED)
QDPHIEV(DISABLED)
QDPLOEV(DISABLED)
QSVCINT(999999999)
QSVCIEV(NONE)
INDXTYPE(NONE)
DEFBIND(OPEN)
ALTDATE(2008-01-14)
ALTTIME(06.18.27)
END QLOCAL DETAILS
CSQ9022I xxS2 CSQMDMSG ' DIS QLOCAL' NORMAL COMPLETION


I cleared the message from transmission queue then start the channel again which gives:

CSQO015E Command issued but no reply received.

Before clearing the message from transmission queue "CSQX514E xxS2 CSQXPING Channel xxS2.YYY.xxSE.INQ01 is active" was displayed.

Any advice what could possibly the cause of the problem?

Thanks
_________________
Past, Present & Future of MQ

Last edited by aahmad8 on Sun Jan 13, 2008 8:20 pm; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website
fjb_saper
PostPosted: Sun Jan 13, 2008 3:22 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
Are you sure the max msglen on the channel is default @ 4MB?

I could understand the channel staying in bindings if the max msglen is less than that of the message on the xmitq.

If you cannot get the channel to stop in mode force try mode terminate...

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
PeterPotkay
PostPosted: Sun Jan 13, 2008 5:14 pm    Post subject: Re: CSQX514E xxS2 CSQXPING Channel xxS2.YYY.xxSE.INQ01 is ac Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722
aahmad8 wrote:
I cleared the message from transmission queue then start the channel again

Why did you clear the message from the q?

Look at the output of MQS2CHIN and the error log on the receiving side for details on why the channel was binding.

fjb_saper wrote:
Are you sure the max msglen on the channel is default @ 4MB?
I could understand the channel staying in bindings if the max msglen is less than that of the message on the xmitq.

I think if a message made it into the XMITQ but is to big for the channel, the SNDR MCA puts into the sending side's DLQ. It shouldn't cause the channel to get stuck in binding.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
aahmad8
PostPosted: Sun Jan 13, 2008 8:25 pm    Post subject: Reply with quote

Apprentice

Joined: 12 Sep 2005
Posts: 27
Location: Malaysia
Yes, it's defaulted @ 4MB max msglen. I use default setting for all my setup.


Channel name . . . . . . . : xxS2.YYY.xxSE.INQ01
Disposition . . . . . . . . : QMGR xxS2

MCA user ID . . . . . . . . :
Nonpersistent messages . . : N F=Fast, N=Normal
Maximum message length . . : 4194304 0 - 104857600
Batch size . . . . . . . . : 50 1 - 9999
Sequence number wrap . . . : 999999999 100 - 999999999
Heartbeat interval . . . . : 30 0 - 999999 seconds
Keep alive interval . . . . : AUTO 0 - 99999 seconds or AUTO

Code:
Are you sure the max msglen on the channel is default @ 4MB?

I could understand the channel staying in bindings if the max msglen is less than that of the message on the xmitq.

_________________
Past, Present & Future of MQ

Last edited by aahmad8 on Sun Jan 13, 2008 9:10 pm; edited 6 times in total
Back to top
View user's profile Send private message Visit poster's website
aahmad8
PostPosted: Sun Jan 13, 2008 8:32 pm    Post subject: Reply with quote

Apprentice

Joined: 12 Sep 2005
Posts: 27
Location: Malaysia
Since this is UAT environment, I am thinking it's much easier to troubleshoot the problem which gives me "CSQO015E Command issued but no reply received." error instead of "CSQX514E xxS2 CSQXPING Channel xxS2.YYY.xxSE.INQ01 is active"

Code:
Why did you clear the message from the q?


If this is the case, I assume all the messages will be landed in sending side's DLQ and eventually clear the xmitq but there are msgs still in xmitq but my CURDEPTH(4). There is no logic the message too big for the channel, right? How do I bring back to RUN state if you are saying that should cause the channel stuck in binding state?

Code:
I think if a message made it into the XMITQ but is to big for the channel, the SNDR MCA puts into the sending side's DLQ. It shouldn't cause the channel to get stuck in binding.



Let me know if there is a proper way to handle this problem.

Thank you.
_________________
Past, Present & Future of MQ

Last edited by aahmad8 on Sun Jan 13, 2008 8:51 pm; edited 2 times in total
Back to top
View user's profile Send private message Visit poster's website
aahmad8
PostPosted: Sun Jan 13, 2008 8:45 pm    Post subject: Reply with quote

Apprentice

Joined: 12 Sep 2005
Posts: 27
Location: Malaysia
As for z/OS I only have force mode.

Channel name . . . . . . . : xxS2.YYY.xxSE.INQ01
Channel type . . . . . . . : SENDER
Description . . . . . . . . : Sender channel to send message to xxSE

Disposition . . . . . . . . . P P=Private on xxS2
A=Shared on any queue manager

Stop mode . . . . . . . . . . 1 1. Quiesce 2. Force
Stop status . . . . . . . . . 1 1. Stopped 2. Inactive

Code:
If you cannot get the channel to stop in mode force try mode terminate...


The following messages being captured from xxS2MSTR log.

16.00.10 STC15622 CSQN207I xxS2 COMMAND SERVER UNABLE TO OPEN REPLY TO QUEUE
16.00.11 STC15622 CSQN203I xxS2 API COMPLETION CODE=2, REASON CODE=2085
16.03.57 STC15622 CSQN207I xxS2 COMMAND SERVER UNABLE TO OPEN REPLY TO QUEUE
16.03.57 STC15622 CSQN203I xxS2 API COMPLETION CODE=2, REASON CODE=2085
16.03.59 STC15622 CSQN207I xxS2 COMMAND SERVER UNABLE TO OPEN REPLY TO QUEUE
16.03.59 STC15622 CSQN203I xxS2 API COMPLETION CODE=2, REASON CODE=2085
16.05.58 STC15622 CSQN207I xxS2 COMMAND SERVER UNABLE TO OPEN REPLY TO QUEUE
16.05.58 STC15622 CSQN203I xxS2 API COMPLETION CODE=2, REASON CODE=2085
16.06.10 STC15622 CSQN207I xxS2 COMMAND SERVER UNABLE TO OPEN REPLY TO QUEUE
16.06.10 STC15622 CSQN203I xxS2 API COMPLETION CODE=2, REASON CODE=2085

... and just notice the following error:

CSQX500I xxS2 CSQXRCTL Channel xxS2.YYY.xxSE.INQ01 started
CSQX201E xxS2 CSQXRCTL Unable to allocate conversation, 202
channel xxS2.YYY.xxSE.INQ01,
connection BBB6xxSE
TRPTYPE=LU62 RC=00000003
CSQX599E xxS2 CSQXRCTL Channel xxS2.YYY.xxSE.INQ01 ended abnormally


Thank you.
_________________
Past, Present & Future of MQ
Back to top
View user's profile Send private message Visit poster's website
PeterPotkay
PostPosted: Mon Jan 14, 2008 8:33 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722
aahmad8 wrote:

Let me know if there is a proper way to handle this problem.


PeterPotkay wrote:
Look at the output of MQS2CHIN and the error log on the receiving side for details on why the channel was binding.

_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Mainframe, CICS, TXSeries » CSQX514E xxS2 CSQXPING Channel xxS2.YYY.xxSE.INQ01 is active
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.