Re: database name for ado.net

What makes this fun is when you have two machines/lpars. One main and one
H/A. And, you actually do switches and run on the other machine on
occasion. It is important they return the same database name. In our case
I'll use GDIHQ1 and GDIHQ2 but they both have to report the database as
GDIHQ. If not, then when you run on Cognos (in our example) it will report
the database failed and you have to reconfigure Cognos. You can test this
by using iACS Schemas. They both should return GDIHQ.
To add to the fun, there are times when you need to refer to the database
on the specific end points. BRMS tape inventory is our classic example.

In WRKRDBDIRE GDIHQ* we have
GDIHQ1:
Remote
Entry Location
GDIHQ *LOCAL
GDIHQ1 LOOPBACK
GDIHQ2 GDIHQ2
with GDIHQ1 as
Relational database . . . . . . : GDIHQ
Relational database alias . . : GDIHQ1
Remote location:
Remote location . . . . . . . : LOOPBACK


GDIHQ2:
GDIHQ *LOCAL
GDIHQ1 GDIHQ1
GDIHQ2 LOOPBACK
with GDIHQ2 as
Relational database . . . . . . : GDIHQ
Relational database alias . . : GDIHQ2
Remote location:
Remote location . . . . . . . : LOOPBACK

If you run the following in sql: VALUES CURRENT SERVER on either machine
it will return GDIHQ