| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TCP/IP responder program (AMQCRSTA)not starting on iSeries |
« View previous topic :: View next topic » |
| Author |
Message
|
| dwilson |
 Posted: Fri Apr 02, 2004 11:42 am Post subject: TCP/IP responder program (AMQCRSTA)not starting on iSeries |
 |
|
Newbie
Joined: 15 Jan 2004
Posts: 2
Location: Ghent, Kentucky
|
Starting a listerner for a server-client channel and getting AMQ9228 (TCP/IP responder program could not start). I received this message over and over until I end the queue manager. Once I end the queue manager and listerner I receive AMQ9999(channel program ended abnormally). I receive this message over and over until I end the AMQCRSTA job. I have 9 other queue mangers running that don't have this problem. Does any know what could be causing this. I am on release 5.2 of MQ csd9 and release V5R1 of OS/400. Thanks for your help.
_________________
David Wilson
Project Lead
North American Stainless
dwilson@northamericanstainless.com |
|
| Back to top |
|
 |
| kman |
| Posted: Mon Apr 05, 2004 12:48 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
What is your endmqm command? It should be quescing normally.. as in
| Code: |
RCDMQMIMG OBJ(*ALL) OBJTYPE(*ALL) MQMNAME(Qmgr_Name) DSPJRNDTA(*YES)
ENDMQM MQMNAME(*ALL) OPTION(*IMMED) ENDCCTJOB(*YES) TIMEOUT(15)
ENDSBS QMQM
|
Also check if there is a lot of socket files in a certain /tmp directory. I forgot which one. YOu should clear all these after you have ended everything MQ. Don't worry, these files are supposed to be cleared by normal endmqm command, but for some reasons it did not. It will be created again on listener starts.
 |
|
| Back to top |
|
|
| dwilson |
| Posted: Mon Apr 05, 2004 12:15 pm Post subject: |
|
|
Newbie
Joined: 15 Jan 2004
Posts: 2
Location: Ghent, Kentucky
|
my end command has been:
ENDMQM MQMNAME(Q_MANAGER) OPTION(*CNTRLD) ENDCCTJOB(*NO)
The main reason for this is to speed up the shut process of the AS/400. I then do a ENDMQM MQMNAME(*ALL) OPTION(*IMMED) ENDCCTJOB(*YES) about once every two weeks.
I checked the /tmp and the SOCKET connections ended when the queue managers were ended. The problem seems to be with one of my clients, the TCP/IP responder not starting message only happens on the one channel and when I changed the port number and connected it worked fine, but I had my client change their programs to connect to the new port number and I started getting the channel error again. They are currently working on this side and hopefully will correct the issue.
Should I be shutting down MQ differently ?
Thanks for you help.
_________________
David Wilson
Project Lead
North American Stainless
dwilson@northamericanstainless.com |
|
| Back to top |
|
|
| kman |
| Posted: Mon Apr 05, 2004 7:59 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
The first line - RCDMQIMG is to help in the recovery of qm in case of any failure. In fact, it also helps in the housekeeping of the journals.
Take a look at the Guick Beginnings guide on further explaination, or the Command Reference. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
