Author |
Message
|
akm.mohan |
Posted: Wed Oct 29, 2008 12:07 pm Post subject: channel is going to stopped status on z/os |
|
|
Apprentice
Joined: 07 Oct 2008 Posts: 41
|
Hi,
Here one of the channel is always going to stopped status. whenever the messages has to be processed i have to start manually.
In the xmtq the trigger set is yes trigger type is first trigger data is that channel name. so this definition looks fine.
in the channel definition
transport type = tcp/ip
conname = ****
xmitq = aaaa
disconnect interval = 300
batch interval = 0
batch heartbeat interval = 0
short retry interval = 60
short retry count = 10
long retry interval = 1200
long retry count = 5
conversion by sender = y
mca user id = process
nonpersistent messages = normal
maximum message length = 8388608
batch size = 50
sequence number wrap = 99999999
heart beat interval = 60
keep alive interval = auto
monitoring =qmgr
LOGS
-------
when the first time i have seen the logs it showed that
CSQX632I +CSQ1 CSQXRCTL SSL certificate has no associated user ID,
remote channel (sender channel name)
- channel initiator user id used
second time i have seen the log that was disconnect interval expired
could you please navigate me to troubleshoot this issue. I am new to mainframes. Please let me know how can i find the perticular channel logs.
version =5.3
If you need any other information, please let me know i would like to provide you. Thanks for your help. |
|
Back to top |
|
 |
bruce2359 |
Posted: Wed Oct 29, 2008 3:06 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
I'd suspect that the channel went in to retry due to some error, and exceded the number of retries, then stopped state.
Look in the channel initiator address space (xxxxCHIN) syslog. You should see channel errors there. _________________ 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 |
|
 |
gbaddeley |
Posted: Thu Oct 30, 2008 7:12 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
bruce2359 wrote: |
I'd suspect that the channel went in to retry due to some error, and exceded the number of retries, then stopped state. |
Yep, it will go into stopped state after retrying for 10 x 60 + 5 x 1200 = 6600 seconds = 1 hour 50 minutes.
Normally the long retry count (5) would be much larger (eg. 500), such that the channel would retry for a least the length of the longest possible outage of the partner system, including in a DR. eg. 2 or more days. _________________ Glenn |
|
Back to top |
|
 |
akm.mohan |
Posted: Fri Oct 31, 2008 9:02 am Post subject: channel went to stopped status on z/os |
|
|
Apprentice
Joined: 07 Oct 2008 Posts: 41
|
Hi all,
Thanks for your great support. i have gon thru the previous chin logs i found the error message like remote dead letter queue . My issue was resolved. once again thanks for your support. Could you please let me know the Main frame commands (MQ TO MQ NO BROKER) which are most useful by us.
Thanks,
Mohan. |
|
Back to top |
|
 |
Vitor |
Posted: Fri Oct 31, 2008 9:58 am Post subject: Re: channel went to stopped status on z/os |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
akm.mohan wrote: |
Could you please let me know the Main frame commands (MQ TO MQ NO BROKER) which are most useful by us.
|
They're the commands you use the most!
Seriously, you've clearly used the script commads to define objects. The other, mainframe specific, commands are laid out in the platform system administration guide and are used to to control things like buffer pools. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Oct 31, 2008 10:37 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
My issue was resolved |
Please share your experience. How was the issue resolved? _________________ 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 |
|
 |
akm.mohan |
Posted: Fri Oct 31, 2008 10:53 am Post subject: channel is in stopped status in z/os |
|
|
Apprentice
Joined: 07 Oct 2008 Posts: 41
|
hi,
The destination queue was full. increased the queue depth aswell as processed the messages...
I need the commands for
1) how can we give the mq commands in mainframe
2) how can we backup the qmgr properties and its object's properties
Please let me know i am new to mainframes...
Thanks,
krishna. |
|
Back to top |
|
 |
akm.mohan |
Posted: Fri Oct 31, 2008 10:57 am Post subject: platform system administration guide |
|
|
Apprentice
Joined: 07 Oct 2008 Posts: 41
|
Thanks JD Council for the pdf....I would like to refere that pdf ..
thanks,
krishna |
|
Back to top |
|
 |
GSI |
Posted: Sun Nov 02, 2008 10:48 pm Post subject: |
|
|
Novice
Joined: 16 Apr 2008 Posts: 18
|
Could you please share the PDF with us.
Thanks
Kris. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 03, 2008 2:51 am Post subject: Re: channel is in stopped status in z/os |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
akm.mohan wrote: |
Please let me know i am new to mainframes...
|
Speak to your site's sys prog. If you're that new, you may need some assistance with the JCL. At the least you'll need to know the HLQ that was used when MQ was installed.
1) You use CSQUTIL & IDCAMS as indicated in the documentation
2) AFAIK there's no mainframe equivalent of saveqmgr _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 03, 2008 2:52 am Post subject: Re: platform system administration guide |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
akm.mohan wrote: |
Thanks JD Council for the pdf....I would like to refere that pdf ..
|
You'll find the relevant links at the top of this page
Happy Reading  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 03, 2008 2:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
GSI wrote: |
Could you please share the PDF with us.
|
You'll find the relevant links at the top of this page
Happy Reading  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Nov 03, 2008 2:53 am Post subject: Re: channel is in stopped status in z/os |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Vitor wrote: |
2) AFAIK there's no mainframe equivalent of saveqmgr |
MS03 runs just fine against zOS queue managers at v6 level or higher, such that they have a proper PCF command server.  |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 03, 2008 2:56 am Post subject: Re: channel is in stopped status in z/os |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
Vitor wrote: |
2) AFAIK there's no mainframe equivalent of saveqmgr |
MS03 runs just fine against zOS queue managers at v6 level or higher, such that they have a proper PCF command server.  |
So I don't know far enough!
All this new-fangled technology..... _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Nov 03, 2008 3:20 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
And for those who remember the days before V6 use CSQUTIL to back up the qmgr definitions. Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|