Quick question on port numbers (V8.1 or V8.2):

Is it true that on HP11, db2icrt command ignores -p option for port
(Non DPF)? Does DB2 always take 60000 (assuming this is the first
instance), regardless of what's passed to -p option (only on HP11)
and the only way to change this port is to manually update svcename dbm
cfg.

Unfortunately, I don't have root access to verify this.

Thanks.

KP

Keith wrote:[color=blue]
> Quick question on port numbers (V8.1 or V8.2):
>
> Is it true that on HP11, db2icrt command ignores -p option for port
> (Non DPF)? Does DB2 always take 60000 (assuming this is the first
> instance), regardless of what's passed to -p option (only on HP11)
> and the only way to change this port is to manually update svcename dbm
> cfg.
>[/color]

-p specifies the client connection port (in effect, it sets registry
variable DB2COMM and the DBM CFG parameter SVCENAME during instance
creation.

The ports around 60000 are used by the FCM for inter-partition
communication, not for client communication. DB2 UDB ESE is a
partitioned database -- by default it has only 1 partition. DPF
is a license only, that allows you to have more than one database
partition.

You can control these port numbers if you wish by changing the
DB2_<instance> and DB2_<instance>_END entries in /etc/services.

Thanks for the reply. I just wanted to verify, with ESE on HP11, if -p
60040 is specified in db2icrt command, will the instance come up using
60040?

Or do we have to take the default (60000) and then modify it (thru the
process you've discussed:
"You can control these port numbers if you wish by changing the
DB2_<instance> and DB2_<instance>_END entries in /etc/services. ")




Thanks.

Keith wrote:[color=blue]
> Thanks for the reply. I just wanted to verify, with ESE on HP11, if -p
> 60040 is specified in db2icrt command, will the instance come up using
> 60040?[/color]

Yes. You can verify this after the instance is created:

db2set DB2COMM
--> should should DB2COMM=tcpip
db2 get dbm cfg | grep SVCENAME
--> should see 60040 as the value for SVCENAME

[color=blue]
> Or do we have to take the default (60000) and then modify it (thru the
> process you've discussed:
> "You can control these port numbers if you wish by changing the
> DB2_<instance> and DB2_<instance>_END entries in /etc/services. ")[/color]

The DB2_<instance> and DB2_<instance>_END don't have anything to do with
client communication (or the -p option). Do not use the port numbers in
the range delimited by these two entries for your SVCENAME.


Typically you'll have at least 3 entries in /etc/services per DB2
ESE instance (example below is for an instance named 'db2inst1'):

db2cdb2inst1 50000/tcp # TCP/IP client communication
DB2_db2inst1 60000/tcp # FCM Port start range (Part 0)
DB2_db2inst1_1 60001/tcp # FCM Port (Part 1)
DB2_db2inst1_2 60002/tcp # FCM Port (Part 2)
DB2_db2inst1_END 60003/tcp # FCM Port start range (Part 3)