| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| NSK SDR Channel connectivity issue - resolving Domain Names |
« View previous topic :: View next topic » |
| Author |
Message
|
| JGRAN |
 Posted: Thu Nov 06, 2008 8:51 am Post subject: NSK SDR Channel connectivity issue - resolving Domain Names |
 |
|
Newbie
Joined: 06 Nov 2008
Posts: 3
|
Hi, I am running wmqv5.3 on Tandem. Before upgrading from v5.1 to v5.3, I had used several Defines I had added to my Qmanager Pathway server classes which were for the "TCPIP Service File" and "TCPIP Process Name". These defines needed to be in place to be able to use Domain names instead of IP addresses in SDR CHL connames. This was working fine for the v5.1 Qmanager's.
Now that I have upgraded from v5.1 to v5.3, these Defines are not working as they used to and I cannot use DNS. Is there anything else I can try so that I will be able to resolve the Domain Names I am attempting to use? I understand the underlying issue is probably due to how the system administrators have not properly configured the DNS resolution on our HP-NSK systems. Although, the workaround I had used for v5.1 worked fine and I'm hoping there is something similar I can do with v5.3.
Any help is appreciated. Thanks. |
|
| Back to top |
|
 |
| hankknowles |
| Posted: Thu Nov 06, 2008 9:52 am Post subject: Re: NSK SDR Channel connectivity issue - resolving Domain Na |
|
|
Centurion
Joined: 18 Aug 2003
Posts: 114
|
| JGRAN wrote: |
Hi, I am running wmqv5.3 on Tandem. Before upgrading from v5.1 to v5.3, I had used several Defines I had added to my Qmanager Pathway server classes which were for the "TCPIP Service File" and "TCPIP Process Name". These defines needed to be in place to be able to use Domain names instead of IP addresses in SDR CHL connames. This was working fine for the v5.1 Qmanager's.
Now that I have upgraded from v5.1 to v5.3, these Defines are not working as they used to and I cannot use DNS. Is there anything else I can try so that I will be able to resolve the Domain Names I am attempting to use? I understand the underlying issue is probably due to how the system administrators have not properly configured the DNS resolution on our HP-NSK systems. Although, the workaround I had used for v5.1 worked fine and I'm hoping there is something similar I can do with v5.3.
Any help is appreciated. Thanks. |
Here is the arg line out of my mqs-tcplis00 does yours resemble this?
ARGLIST -t,TCP,-g,$ZBnnn,-p,nnnnn,-m,qmgrname
We use dns resolution on all the channels with our qmanagers |
|
| Back to top |
|
|
| JGRAN |
| Posted: Thu Nov 06, 2008 10:11 am Post subject: |
|
|
Newbie
Joined: 06 Nov 2008
Posts: 3
|
Hi, Yes.. that is how my ARG list is configured on that Server (mqs-tcplis00). That ARG list is only specific to the MQ Listener. This unfortunately doesn't do anything for Sender Channels. It's the SDR chl's that I am unable to use dns resolution on since migrating to v5.3. The Remote Qmgrs sending to my NSK Qmgr are not having any issue with resolving dns to get to the NSK platform.
Thanks. |
|
| Back to top |
|
|
| hankknowles |
| Posted: Thu Nov 06, 2008 10:18 am Post subject: |
|
|
Centurion
Joined: 18 Aug 2003
Posts: 114
|
| JGRAN wrote: |
Hi, Yes.. that is how my ARG list is configured on that Server (mqs-tcplis00). That ARG list is only specific to the MQ Listener. This unfortunately doesn't do anything for Sender Channels. It's the SDR chl's that I am unable to use dns resolution on since migrating to v5.3. The Remote Qmgrs sending to my NSK Qmgr are not having any issue with resolving dns to get to the NSK platform.
Thanks. |
What does the oss qm.in and qmproc.ini look like in OSS? |
|
| Back to top |
|
|
| JGRAN |
| Posted: Thu Nov 06, 2008 10:38 am Post subject: |
|
|
Newbie
Joined: 06 Nov 2008
Posts: 3
|
Below are the contents of the two ini's.
I had wondered before if I should be adding an ''Env01={DNS Service File}" entry on the chlRule for the sender chl I'm trying to connect with. I hadn't tried that yet.
qm.ini -
ExitPath:
ExitsDefaultPath=/usr/ibm/wmq/UAT/V53/QX/var/mqm/exits/:$DATA22.ZWMQSAMP
#* *#
#* *#
Service:
Name=AuthorizationService
EntryPoints=10
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/usr/ibm/wmq/UAT/V53/QX/opt/mqm/lib/amqzfu
ComponentDataSize=0
Channels:
MQIBindType=FASTPATH
MaxChannels=10
MaxActiveChannels=10
MaxTries=3
MaxTriesIntvl=10
ChinitDiscint=10
TCP:
Port=1414
qmproc.ini -
# All Processes stanza
# --------------------
AllProcesses:
CPUs=0,1,2,3
# Agent type stanzas
# ------------------
LQMA:
MCA:
# Application rules
# -----------------
AppRule1-ProcNameMatch:
AppRule2-ProgNameMatch:
AppRule3-ExeNameMatch:
AppRule4-SubvolMatch:
AppRule5-CpuMatch:
# Channel rules
# -------------
ChlRule1-ChannelNameMatch:
ChlRule2-ChannelTypeMatch:
ChlRule3-ChannelProtocolMatch:
ChannelProtocolMatch=TCPIP
TransportName=$ZTCE
ChlRule3-ChannelProtocolMatch:
ChannelProtocolMatch=SNA
TransportName=$APC
# Repository Manager stanza
# -------------------------
RepositoryManager:
CPUs=0,1,2,3
Pathway:
ProcessName=$QMGR
DynamicProcessName=No
Hometerm=$HAMQ
ChlRule1-ChannelNameMatch:
ChannelNameMatch=QMGR1.QMGR2.C1
TransportName=$ZTCE |
|
| Back to top |
|
|
| hankknowles |
| Posted: Thu Nov 06, 2008 10:53 am Post subject: |
|
|
Centurion
Joined: 18 Aug 2003
Posts: 114
|
| JGRAN wrote: |
Below are the contents of the two ini's.
I had wondered before if I should be adding an ''Env01={DNS Service File}" entry on the chlRule for the sender chl I'm trying to connect with. I hadn't tried that yet.
qm.ini -
ExitPath:
ExitsDefaultPath=/usr/ibm/wmq/UAT/V53/QX/var/mqm/exits/:$DATA22.ZWMQSAMP
#* *#
#* *#
Service:
Name=AuthorizationService
EntryPoints=10
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/usr/ibm/wmq/UAT/V53/QX/opt/mqm/lib/amqzfu
ComponentDataSize=0
Channels:
MQIBindType=FASTPATH
MaxChannels=10
MaxActiveChannels=10
MaxTries=3
MaxTriesIntvl=10
ChinitDiscint=10
TCP:
Port=1414
qmproc.ini -
# All Processes stanza
# --------------------
AllProcesses:
CPUs=0,1,2,3
# Agent type stanzas
# ------------------
LQMA:
MCA:
# Application rules
# -----------------
AppRule1-ProcNameMatch:
AppRule2-ProgNameMatch:
AppRule3-ExeNameMatch:
AppRule4-SubvolMatch:
AppRule5-CpuMatch:
# Channel rules
# -------------
ChlRule1-ChannelNameMatch:
ChlRule2-ChannelTypeMatch:
ChlRule3-ChannelProtocolMatch:
ChannelProtocolMatch=TCPIP
TransportName=$ZTCE
ChlRule3-ChannelProtocolMatch:
ChannelProtocolMatch=SNA
TransportName=$APC
# Repository Manager stanza
# -------------------------
RepositoryManager:
CPUs=0,1,2,3
Pathway:
ProcessName=$QMGR
DynamicProcessName=No
Hometerm=$HAMQ
ChlRule1-ChannelNameMatch:
ChannelNameMatch=QMGR1.QMGR2.C1
TransportName=$ZTCE |
Have you tried it with out this ChlRule1- stanza at the end of the above
ChlRule1-ChannelNameMatch:
ChannelNameMatch=QMGR1.QMGR2.C1
TransportName=$ZTCE
I do not have that used!
I also do not have the hometerm specified either.
Up a little higher you have
ChlRule3-ChannelProtocolMatch:
ChannelProtocolMatch=TCPIP
TransportName=$ZTCE
ChlRule3-ChannelProtocolMatch:
ChannelProtocolMatch=SNA
TransportName=$APC
Maybe rem out one and see if this is confusing things |
|
| Back to top |
|
|
| hankknowles |
| Posted: Thu Nov 06, 2008 11:01 am Post subject: |
|
|
Centurion
Joined: 18 Aug 2003
Posts: 114
|
| hankknowles wrote: |
| JGRAN wrote: |
Below are the contents of the two ini's.
I had wondered before if I should be adding an ''Env01={DNS Service File}" entry on the chlRule for the sender chl I'm trying to connect with. I hadn't tried that yet.
qm.ini -
ExitPath:
ExitsDefaultPath=/usr/ibm/wmq/UAT/V53/QX/var/mqm/exits/:$DATA22.ZWMQSAMP
#* *#
#* *#
Service:
Name=AuthorizationService
EntryPoints=10
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/usr/ibm/wmq/UAT/V53/QX/opt/mqm/lib/amqzfu
ComponentDataSize=0
Channels:
MQIBindType=FASTPATH
MaxChannels=10
MaxActiveChannels=10
MaxTries=3
MaxTriesIntvl=10
ChinitDiscint=10
TCP:
Port=1414
qmproc.ini -
# All Processes stanza
# --------------------
AllProcesses:
CPUs=0,1,2,3
# Agent type stanzas
# ------------------
LQMA:
MCA:
# Application rules
# -----------------
AppRule1-ProcNameMatch:
AppRule2-ProgNameMatch:
AppRule3-ExeNameMatch:
AppRule4-SubvolMatch:
AppRule5-CpuMatch:
# Channel rules
# -------------
ChlRule1-ChannelNameMatch:
ChlRule2-ChannelTypeMatch:
ChlRule3-ChannelProtocolMatch:
ChannelProtocolMatch=TCPIP
TransportName=$ZTCE
ChlRule3-ChannelProtocolMatch:
ChannelProtocolMatch=SNA
TransportName=$APC
# Repository Manager stanza
# -------------------------
RepositoryManager:
CPUs=0,1,2,3
Pathway:
ProcessName=$QMGR
DynamicProcessName=No
Hometerm=$HAMQ
ChlRule1-ChannelNameMatch:
ChannelNameMatch=QMGR1.QMGR2.C1
TransportName=$ZTCE |
Have you tried it with out this ChlRule1- stanza at the end of the above
ChlRule1-ChannelNameMatch:
ChannelNameMatch=QMGR1.QMGR2.C1
TransportName=$ZTCE
I do not have that used!
I also do not have the hometerm specified either.
Up a little higher you have
ChlRule3-ChannelProtocolMatch:
ChannelProtocolMatch=TCPIP
TransportName=$ZTCE
ChlRule3-ChannelProtocolMatch:
ChannelProtocolMatch=SNA
TransportName=$APC
Maybe rem out one and see if this is confusing things |
Here I have generalized my qm.ini and qmproc.ini
QM.INI
#*******************************************************************#
#* Module Name: qm.ini *#
#* Type : WebSphere MQ queue manager configuration file *#
# Function : Define the configuration of a single queue manager *#
#* *#
#*******************************************************************#
#* Notes : *#
#* 1) This file defines the configuration of the queue manager *#
#* *#
#*******************************************************************#
ExitPath:
ExitsDefaultPath=/var/mqmv53/var/mqm/exits/:$vol.ZWMQSAMP
#* *#
#* *#
Service:
Name=AuthorizationService
EntryPoints=10
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/opt/mqm/lib/amqzfu
ComponentDataSize=0
Channels:
MQIBindType=FASTPATH
AdoptNewMCA=ALL
AdoptNewMCATimeout=60
AdoptNewMCACheck=QM
MaxChannels=250
MaxActiveChannels=250
TCP:
KeepAlive=Yes
QMPROC.INI
#*********************************************************************#
# #
# WMQ V5.3 for HP NonStop Server #
# #
# Template process management configuration file #
# The contents of this file are copied to create the initial version #
# of the qmproc.ini file for each queue manager that is created in #
# this installation. #
# #
#*********************************************************************#
# All Processes stanza
# --------------------
AllProcesses:
AllProcesses:
CPUs=,3,4
Priority=170
FailOnProcNameUnavail=Yes
# Agent type stanzas
# -----------------
LQMA:
ThreadedAgents=No
ProcessNameRoot=$BMQ
CPUs=3,4
Priority=165
MaxThreadedAgents=1000
MaxThreadedAgentUse=10
MaxAgentUse=10
MaxUnthreadedAgents=1000
MaxIdleAgents=10
MinIdleAgents=3
MCA:
CPUs=3,4
MaxThreadedAgents=1000
MaxThreadedAgentUse=10
MaxAgentUse=10
MaxUnthreadedAgents=1000
MaxIdleAgents=10
MinIdleAgents=3
# Application rules
# -----------------
AppRule1-ProcNameMatch:
AppRule2-ProgNameMatch:
AppRule3-ExeNameMatch:
AppRule4-SubvolMatch:
AppRule5-CpuMatch:
# Channel rules
# -------------
ChlRule1-ChannelNameMatch:
ChlRule2-ChannelTypeMatch:
ChlRule3-ChannelProtocolMatch:
ChannelProtocolMatch=TCPIP
TransportName=$ZBnnn
# Repository Manager stanza
# -------------------------
RepositoryManager:
ProcessNameRoot=$BEP
CPUs=3,4
Pathway:
ProcessName=$Qnnn
DynamicProcessName=No |
|
| 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
|
|
|
|
