*LOOPBACK is used for IASP devices.
There might be another usage scenario but I have not run into it.
*LOCAL would seem to be the correct for the primary database.
On Sun, Mar 16, 2014 at 8:00 AM, CRPence <CRPbottle@xxxxxxxxx> wrote:
The /special value/ *LOOPBACK [i.e. what Mark suggested] would seem
to be a better choice than what was already done. That is because if
the IP address of that server partition ever changes, then the RDB Entry
pointing to *LOOPBACK [remaining unresolved at create-time] would not
suddenly fail to connect locally or suddenly attempt to effect a
connection to a system with the old IP address. Those might be
potential issues if that RDB Directory Entry does not get updated to
specify the same value as the changed-to\new IP address. If not
explicitly *LOOPBACK, then using the address of 127.0.0.1 would seem to
be an option, as the probable _localhost_ loop-back host address.
On 12-Mar-2014 12:49 -0700, fbocch2595@xxxxxxx wrote:
I already used ADDRDBDIRE with the system's IP address as the--
RMTLOCNAME of the IP address. Would loopback work better?
Mark S Waterbury onWed, Mar 12, 2014 1:34 pm wrote:
ADDRDBDIRE RDB(oldname) RMTLOCNAME(*LOOPBACK)
That will add the "old name" back again, to the Relational
Database Directory Entries -- you can issue WRKRDBDIRE to see them
That way, your users do not have to change all of those documents,
etc. (preserves compatibility with the past).
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives