Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
1 reply Latest Post - ‏2013-04-04T13:59:59Z by krmilligan
SystemAdmin
SystemAdmin
3129 Posts
ACCEPTED ANSWER

Pinned topic Multiple LPARS using same RDB name

‏2013-04-01T17:54:03Z |
I'm on a system with several LPARS. Each LPAR calls its own database XYZ. In the RDB directory, each LPAR refers to the the databases on the other LPARS by their LPAR name, but refers to itself as XYZ. This means that no matter where SQL runs, CURRENT_SERVER is always XYZ. This is annoying when one is trying to determine which environment something is running in.

Can anyone think of any drawbacks to changing this. We have no applications that check CURRENT_SERVER presently, and it would be pointless if they did.

And assuming we do want to change this, how do we do it?
Updated on 2013-04-04T13:59:59Z at 2013-04-04T13:59:59Z by krmilligan
  • krmilligan
    krmilligan
    447 Posts
    ACCEPTED ANSWER

    Re: Multiple LPARS using same RDB name

    ‏2013-04-04T13:59:59Z  in response to SystemAdmin
    Shouldn't be any issues in changing it - assuming you don't have active host server jobs (eg, ODBC & JDBC requests) that are connected to that database.

    WRKRDBDIRE command would allow you to change the name of the *LOCAL entry.