× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Dave,

As a standard in our shop, we name our channels based on the system name they are communicating with.

For example, on System A with QMGRA I have channel names of IN.SYSTEMB (*SVRCN channel) or TO. SYSTEMB.xxxx (sender channel).

Not knowing how big your environment is, it is probably not convenient to go back and change your configuration; but this could be an opportunity going forward.

Hope that helps,

Jim

----- Original Message -----

From: "Rob Berendt" <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, March 3, 2016 9:44:50 AM
Subject: Re: MQ message

Is the application using IP address instead of name? Ideally the change
would be made there. But, a cursory glance for that message id seems to
show it favors showing you the IP address.

As a manual step one can usually do
NSLOOKUP 'xxx.xxx.xxx.xxx'
and get the name. For example:

NSLOOKUP '10.17.6.32'
Server: 10.10.4.250
Address: 10.10.4.250#53

32.6.17.10.in-addr.arpa name = gdihq1.corp.dekko.com.

Press ENTER to end terminal session.


This means that on DNS server 10.10.4.250 it did a reverse lookup (that's
why the IP address is shown backwards) and found an entry for
gdihq1.corp.dekko.com
I use this technique quite often. There's probably some API to look that
up also if you need to program that.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.