Translating outbound IDs

If an ID on your system is duplicated on a remote system, you can translate outbound IDs to avoid confusion. You can also translate IDs to ensure that they are accepted by the remote system.

Procedure

To indicate that you want to translate outbound user IDs, perform the following steps:

  1. Specify an O in the USERNAMES column of the SYSIBM.IPNAMES or SYSIBM.LUNAMES table.
  2. Use the NEWAUTHID column of the SYSIBM.USERNAMES table to specify the ID to which the outbound ID is translated.

Example

Suppose that the remote system accepts from you only the IDs XXGALE, GROUP1, and HOMER.
  1. Specify that outbound translation is in effect for the remote system LUXXX by specifying in SYSIBM.LUNAMES the values that are shown in the following table.
    Table 1. SYSIBM.LUNAMES to specify that outbound translation is in effect for the remote system LUXXX
    LUNAME USERNAMES
    LUXXX O

    If your row for LUXXX already has I for the USERNAMES column (because you translate inbound IDs that come from LUXXX), change I to B for both inbound and outbound translation.

  2. Translate the ID GALE to XXGALE on all outbound requests to LUXXX by specifying in SYSIBM.USERNAMES the values that are shown in the following table.
    Table 2. Values in SYSIBM. USERNAMES to translate GALE to XXGALE on outbound requests to LUXXX
    TYPE AUTHID LINKNAME NEWAUTHID PASSWORD
    O GALE LUXXX XXGALE GALEPASS
  3. Translate EVAN and FRED to GROUP1 on all outbound requests to LUXXX by specifying in SYSIBM.USERNAMES the values that are shown in the following table.
    Table 3. Values in SYSIBM. USERNAMES to translate EVAN and FRED to GROUP1 on outbound requests to LUXXX
    TYPE AUTHID LINKNAME NEWAUTHID PASSWORD
    O EVAN LUXXX GROUP1 GRP1PASS
    O FRED LUXXX GROUP1 GRP1PASS
  4. Do not translate the ID HOMER on outbound requests to LUXXX. (HOMER is assumed to be an ID on your Db2, and on LUXXX.) Specify in SYSIBM.USERNAMES the values that are shown in the following table.
    Table 4. Values in SYSIBM. USERNAMES to not translate HOMER on outbound requests to LUXXX
    TYPE AUTHID LINKNAME NEWAUTHID PASSWORD
    O HOMER LUXXX (blank) HOMERSPW
  5. Reject any requests from BASIL to LUXXX before they are sent. To do that, leave SYSIBM.USERNAMES empty. If no row indicates what to do with the ID BASIL on an outbound request to LUXXX, the request is rejected.

If you send requests to another LU, such as LUYYY, you generally need another set of rows to indicate how your IDs are to be translated on outbound requests to LUYYY.

However, you can use a single row to specify a translation that is to be in effect on requests to all other LUs. For example, if HOMER is to be sent untranslated everywhere, and DOROTHY is to be translated to GROUP1 everywhere, specify in SYSIBM.USERNAMES the values that are shown in the following table.

Table 5. Values in SYSIBM. USERNAMES to not translate HOMER and to translate DOROTHY to GROUP1
TYPE AUTHID LINKNAME NEWAUTHID PASSWORD
O HOMER (blank) (blank) HOMERSPW
O DOROTHY (blank) GROUP1 GRP1PASS

You can also use a single row to specify that all IDs that accompany requests to a single remote system must be translated. For example, if every one of your IDs is to be translated to THEIRS on requests to LUYYY, specify in SYSIBM.USERNAMES the values that are shown in the following table.

Table 6. Values in SYSIBM. USERNAMES to translate every ID to THEIRS
TYPE AUTHID LINKNAME NEWAUTHID PASSWORD
O (blank) LUYYY THEIR THEPASS

If the ICSF is installed and properly configured, you can use the DSNLEUSR stored procedure to encrypt the translated outbound IDs that are specified in the NEWAUTHID column of SYSIBM.USERNAMES. Db2 decrypts the translated outbound IDs during connection processing.