Re: Traveler on i and HADR options

Related to this, we're a Mimix shop. We have a primary ERP lpar called
GDIHQ. It is MIMIXED over to GDIHQ2. You have to doctor your WRKRDBDIRE.
It's not enough to just monkey around with your DNS and say GDIHQ is now
pointing over to GDIHQ2. When your client does a CONNECT TO GDIHQ and
it's connecting to GDIHQ2 all heck breaks loose.
There are documents on how to set this up.
This is also the reason that we busted off Domino into it's own lpar off
of GDIHQ. Running the client, connecting to the server, on the same lpar
was a little harder to get working. (Also a reason why we eschew virtual
lan between lpars.)

Configuring RDB Names for High Availability and External System Access
Document Number: 416466888
http://www-912.ibm.com/s_dir/SLKBase.nsf/1ac66549a21402188625680b0002037e/31d82ab263ae401f8625717e0068d44f?OpenDocument

Keep in mind, the following is "in transition". There's a strong
possibility that the physical GDIHQ may become GDIHQ1. Which is how we
should have set it up in the first place.

Goal: We want others (such as Domino agents, Excel connections, etc) to
be able to connect to the machine set up as GDIHQ by the current DNS
entry. However, we want a back door to get to the 'real' machine of our
choice for systems internal use. Everyone will use GDIHQ. The systems
dept may use GDIHQ1 or GDIHQ2 depending on which machine we need to do
work with at the time. A systems example may be an automated connection
to both lpars that returns the current amount of disk used.

GDIHQ - WRKRDBDIRE
Remote
Entry Location
...
GDIHQ *LOCAL
GDIHQ1 GDIHQ1
GDIHQ2 GDIHQ2
...
On this machine GDIHQ1 is just an alias
Relational database . . . . . . : GDIHQ
Relational database alias . . : GDIHQ1

GDIHQ2 - WRKRDBDIRE
Remote
Entry Location
...
GDIHQ *LOCAL
GDIHQ1 GDIHQ1.CORP.DEKKO.COM
GDIHQ2 GDIHQ2
...
On this lpar GDIHQ2 is just an alias
Relational database . . . . . . : GDIHQ
Relational database alias . . : GDIHQ2

MAIL1 - WRKRDBDIRE (a Domino lpar)
Remote
Entry Location
...
GDIHQ GDIHQ
GDIHQ1 GDIHQ1.CORP.DEKKO.COM
GDIHQ2 GDIHQ2
...
There are no alias entries. Someone using GDIHQ1 or GDIHQ2 from this
machine will be questioned. netstat will be monitored.

HTH

Rob Berendt