Your error message is not surprising. Review the complete description of
the SVCENAME data base manager parameter. The port address specified is
"the first of two consecutive ports ...".

Use even numbered port addresses only; 60000, 60002, 60004, 60006.

Phil Sherman

Those service entries should not be used as SVCENAME. They are used
internally by DB2. You should have other entries in the sevices file. In
my case it also contains the entry 'db2c_DB2    50000/tcp'.
Just add entries to the services file in the 500.. range and use those
names or portnumbers in the instance definitions.

Is your test server set up identical to your production server?  The reason
why I ask is that these extra service entries should only show up on DB2
UDB ESE, and not on any other product.  So if you have ESE on your test
server, but WSE on your production server, for example, that would explain
this difference.

With non-ESE servers, you get one service entry: the connection port.  This
entry is usually something like "db2c_<instancename>" unless you opted for
a different name during instance creation (usually in the GUI or response
file).  This name goes in your SVCENAME parameter.  Again, this should
largely be automatic.  (Using db2icrt directly, however, may not create
this, so then it's manual.)

With ESE servers, you get the above connection port PLUS you get
FCM/INTRA-PARALLEL ports.  These are *always* of the format
"DB2_<instancename>".  The ones with _1, _2, and _END in your example
aren't needed by DB2 explicitly - they are derived internally by just
adding the node number to the port number.  They are placed in your
services file mostly to prevent other applications from trying to use them.

These ports are only needed if you're using multiple nodes (whether logical
or physical) in a DPF environment *or* you have intra-parallel turned on,
as I recall.  However, even if you're not using either of these yet, DB2
creates them during instance creation (unless they alread exist) to reserve
the ports for when you do need to scale to use these features.

Since these ports have a predefined name, not only can you not change the
names (you can change the numbers, however, as long as they remain
consecutive and not used by any other application on the machine, as well
among the entire cluster if using DPF), you need not configure DB2 in any
way to tell DB2 what the names are.  So do not set the SVCENAME to these
values.  Leave SVCENAME referencing the connection port from your services
file.

Hope that helps,