> yes I used often the port number and I never had a problem, but you should > notice that the mapping port number service name in the services file it > is not only intended to be able to use a more intuitive name rather then a > sometime more complex to remember port number; the more important reason > why you want always to insert the line in the services file is that in > this way you are reserving the port for your application and it won't be > possible for anyother application to start communicating on that port > blocking your DB2 client the ability to communicate with the server.
No, AFAIK the services file only sets up a name on your client systems to connect to the servers. It does not matter which application on the client system binds to or uses port 50000 as long as no DB2 server is running there. If you run a netstat -n on your DB2 servers you will see a lot of client IP addresses with various port numbers all connecting to port 50000 on the server. Any TCP/IP connection is defined by the unique combination of server IP address, server TCP port, client IP address and client TCP port. The services file tells the client which TCP port to request on the server and NOT which TCP port it should bind to on the local machine. -HJC - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
