Jerry,
There is no problem running on any TCPIP ports > 1024, (which are reserved for system use), as long as it is not in use by another process. I'll offer some other TCPIP info that I've learned over the years, that might be of some help: You really only need one TCPIP port per instance, the "service" port. The second port is only needed to support *very* old client connections. (I forget how old, maybe < V3?) The port number you use is completely arbitrary and and does not need to be added to /etc/services, unless you need some way to reference the it via a name, ie "db2cdb2inst1". It is perfectly OK to multiple DB2 instances per machine, as long as each has their own TCPIP service port. I hope this helps, Doug On Thu, Oct 04, 2001 at 08:45:26AM +1000, Jerry Long wrote: > G'day Listers, > > Thanks to Mike Leberman for the response on my query regarding node and > database directories. This has led to a further question. > > The default TCP port numbers for db2 are 50000 for the connection > channel and 50001 for the interrupt channel. Our unix bods have advised > that solaris may use ports in the range 32768 thru 65535 by default for > a TCP connection source. If a solaris server by chance has 50000/50001 > open as a source port at db2 startup, then problems will occur. > > Has anyone experienced such problems? Are you using the default port > numbers 50000/50001 or have you adopted your own local standards using > port numbers <32K? > > Grateful for any advice. > > Regards, > Jerry Long > > ===== To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
