Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
Vitor wrote:
jcv wrote:
This is not documenting anything. That's just repeating information already present in the definition.
I also use a port number in the listener name as a surprising number of people can see the name of a listener but appear incapable of finding the port number in the definition / finding the definition / correlating the "port number" field in the definition to the port number used by the listener.
Seriously.
I was once asked how the port number defined to a listener correlated to the port that would be opened in the network.
You can't fix stupid, but this at least duct tapes it in place.
P.S.
I don't include "TCP" in the name. This is a deliberate policy so anyone who asks what network protocol we're using in a distributed Linux environment can be culled to improve the herd _________________ Honesty is the best policy.
Insanity is the best defence.
Here: http://www.mqseries.net/phpBB2/viewtopic.php?t=48691 , LISTNER.APPS and LISTNER.MQADMIN would be examples of listener names that actually document something, like why these two listeners are defined, what and who is using which port to access that qmgr. You can write such info to DESCR instead, and produce names by merely concatenating "LISTENER" and a few attribute values, but you cannot say then that such names document anything.
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