| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Error CSQX208E CSQXRCTL : Error receiving data via channel |
« View previous topic :: View next topic » |
| Author |
Message
|
| bcostacurta |
 Posted: Fri Dec 11, 2009 8:27 am Post subject: |
 |
|
Acolyte
Joined: 10 Dec 2009
Posts: 71
Location: Luxembourg
|
Dears,
please find hereafter the channel sender definition.
Dear bruce2359 what do you mean by 'errors recorded in the TCP/IP address space' ? How can I check this ? Thanks for attention.
Channel Name QCE1.QMONI1E
Channel Type Sender
Description
Transport Type TCP/IP
Connection Name -hidden-
Local Address
Transmission Queue QMONI1E.XMITQ
Batch Size 50
Max Message Length 104857600
MCA UserId
Batch Interval 0
Heartbeat Interval 300
KeepAlive Int Auto
Batch Heartbeat 0
Disconnect Interval 3600
NPM Speed Fast
Header Compression None
Message Compression None
Short Retry Count 10
Short Retry Interval 1200
Long Retry Count 999999999
Long Retry Interval 1200
Data Conversion No
SSL Cipher Spec
SSL Peer Name
Security Exit
Security User Data
Message Exits
Message User Data
Send Exits
Send User Data
Receive Exits
Receive User Data
Seq Number Wrap 999999999
Channel Monitoring Qmgr
Alteration Date 2009-12-04
Alteration Time 14.10.17
Hope it helps.
But IMHO I cannot see here any potential problem, but your (very welcome) opinion or experience result might differ.
Bye,
Bruno |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri Dec 11, 2009 8:52 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
One more thing:
Please display your qmgr attributes using DISPLAY QMGR mqsc script command; then post here.
TCPIP address space (like XXXXCHIN) might have something interesting about your issue.
_________________
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 |
|
|
| JoePanjang |
| Posted: Sun Dec 13, 2009 6:24 pm Post subject: |
|
|
Voyager
Joined: 10 Jul 2002
Posts: 88
Location: Dengkil MALAYSIA
|
I saw the similar error on our mq console log. this is due to the F5 load balancer on the 2 servers. Similar rrror shown on the log but at the same time channel restarted immediately.
You probably want to check the servers coming to z/os whether they hv any load balancer, firewall rules changed etc.
_________________
Every good deed is charity... |
|
| Back to top |
|
|
| bcostacurta |
| Posted: Mon Dec 14, 2009 12:00 am Post subject: |
|
|
Acolyte
Joined: 10 Dec 2009
Posts: 71
Location: Luxembourg
|
Dears,
indeed the error I gave in the start of this thread came for my xxxCHIN log file. And, as far as I can see, I did not find additional error in the log file.
Also, as requested by bruce2359, please find hereafter the qmgr definition :
Description QCE1, IBM WebSphere MQ for z/OS - V6
Queue Manager Name QCE1
Queue Manager Id QCE1.BF926D1A0F53568C
Platform MVS
Command Level 600
QSG Name
Shared Queue QM Name Use
Repository Name
Repository Name List
Cluster Workload Exit
Cluster Workload Data
Cluster Workload Length 100
Cluster MRU Channel 999999999
Cluster Use Remote Q Local
IP Address Version IPv4
Active Channels 200
Chinit Adaptors 30
Chint Dispatchers 20
Chinit Service Parm 00000000000000000000000000000000
Chinit Trace Autostart No
Chinit Trace Space 2
Adopt Check All
Adopt Type All
DNS Group
DNS Workload Manager No
Listener Timer 60
Max Channels 200
TCP Channels 200
TCP Keep Alive Yes
TCP Name TCPIP
TCP Stack Type Single
Outbound Port Min 0
Outbound Port Max 0
Receive Timeout 0
Receive Timeout Min 0
Receive Timeout Type Multiply
LU62 Channels 0
LU Group Name
LU Name
LU62 Arm Suffix
Accounting - Queue On
Monitoring - Queue Off
Monitoring - Channel Off
Monitoring - CLUSSDR Qmgr
Trigger Interval 300000
Expiry Interval 10800
Dead Letter Queue
SSL Key Repository
SSL CRL Namelist
SSL Tasks 0
SSL Reset Count 0
Trace Route Recording Message
Activity Recording Message
Maximum Priority 9
Command Input Queue SYSTEM.COMMAND.INPUT
Coded Char Set Id 297
Max Handles 256
Max Msg Length 104857600
Max Uncommitted Msgs 50000
SyncPoint Available
Default Xmit Queue
Channel Define Exit
Authority Event Disabled
Inhibit Event Disabled
Local Event Disabled
Remote Event Disabled
Start/Stop Event Enabled
Performance Event Enabled
Channel Event Enabled
Bridge Event Disabled
SSL Event Disabled
Configuration Event Disabled
Command Event Disabled
Alteration Date 2009-11-21
Alteration Time 12.44.28
And as reminder the channel sender definition:
Channel Name QCE1.QMONI1E
Channel Type Sender
Description
Transport Type TCP/IP
Connection Name -hidden-
Local Address
Transmission Queue QMONI1E.XMITQ
Batch Size 50
Max Message Length 104857600
MCA UserId
Batch Interval 0
Heartbeat Interval 300
KeepAlive Int Auto
Batch Heartbeat 0
Disconnect Interval 3600
NPM Speed Fast
Header Compression None
Message Compression None
Short Retry Count 10
Short Retry Interval 1200
Long Retry Count 999999999
Long Retry Interval 1200
Data Conversion No
SSL Cipher Spec
SSL Peer Name
Security Exit
Security User Data
Message Exits
Message User Data
Send Exits
Send User Data
Receive Exits
Receive User Data
Seq Number Wrap 999999999
Channel Monitoring Qmgr
Alteration Date 2009-12-04
Alteration Time 14.10.17
Regards,
Bruno |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Dec 14, 2009 6:52 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
What platform is the receiver end?
Whatever failure your network is experiencing is orphaning (is this really a verb?) the MCA.
Your qmgr attribute Adopt Type All tells the qmgr to create a new MCA should one be orphaned. Working as designed... since your network connections seems to recover on its own.
_________________
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 |
|
|
| bcostacurta |
| Posted: Thu Dec 17, 2009 12:05 am Post subject: |
|
|
Acolyte
Joined: 10 Dec 2009
Posts: 71
Location: Luxembourg
|
So the AdoptMCA = yes should automatically re-start the channel ?
However status is binding, until being manually stop + re-start.
Note : still waiting details about receiver platform.
Bye,
Bruno |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
