| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Tandem NSK TCPIP |
« View previous topic :: View next topic » |
| Author |
Message
|
| relheop |
 Posted: Fri Jul 25, 2003 11:05 am Post subject: Tandem NSK TCPIP |
 |
|
Apprentice
Joined: 30 Jan 2003
Posts: 40
|
What have I to do on Compac NonStop Kernel, if I want to use MQSeries V2.2.0.1 with another TCP-process than $ZTC0?
I added the Statement "DEFINE= TCPIP^PROCESS^NAME, FILE $ZTC1" to TCPLIS00, ECBOSS and all EC-processes. Receiving data works, but when sending data, the channel goes to Status "retrying". In the log-file there is a message "channel started", but there is no error message. When I stop the channel manually, there is no stop-message in the log, but the channel goes to status stopped. When trying "ping channel" I get the message "Channel in use". |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Fri Jul 25, 2003 12:59 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
What level of code you are on. I believe a similar problem was fixed in one of the Apars. Do you have the latest patch, U473441. If not, you may request it from your ibm rep.
As an aside, you should know that 2201 is out of service as of December 2002. Hence there wouldnt be any support unless you pay, i guess.
Why dont you upgrade to 51 instead.
Cheers
Kumar |
|
| Back to top |
|
|
| relheop |
| Posted: Mon Jul 28, 2003 10:46 pm Post subject: |
|
|
Apprentice
Joined: 30 Jan 2003
Posts: 40
|
Hello Kumar,
thanks for answering my question.
We have installed the PTF U473441. That wasn't the problem.
But you gave us the essential hint. We had a look at the README of this PTF again, and there we saw, that using the "DEFINE TCPIP^PROCESS^NAME" in the serverclass definitions of the EC-processes is no longer the way to get sender channels connected to another IP-Process. We found out that we now had to add the name of the wanted TCP/IP-process to the "conname" (or TCPIP/SNA Process in the MQMC). After doing this everything worked fine
When using a special TCP/IP process for the listener, it still is correct to add the "DEFINE TCPIP^PROCESS^NAME" in the serverclass definition of the listener process. Therefore all of our receiver channels worked. |
|
| 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
|
|
|
|
