Examples

Restriction: This topic applies to Windows environments only.

Bob is logged in to the XDB Server develop. He issues a SELECT command referencing orders.eastern.may. This request is received by the XDB Server develop. Develop determines that the orders location is controlled by the XDB Server sales. Develop checks its system catalog table SYSIBM.SYSLUNAMES, which indicates that any request going to sales is subject to outbound mapping.

Develop then checks the system table SYSIBM.SYSUSERNAMES, which indicates the AuthID of Bob should be translated to devbob for all requests to the XDB Server sales. The SELECT request referencing ORDERS.EASTERN.MAY is sent to sales with an AuthID of devbob.

The SELECT request is then received at the XDB Server sales. If inbound mapping is not being used, sales verifies that the AuthID devbob is a valid AuthID in the SYSXDB.SYSACFUSERS table. The SELECT query is processed, privileges are checked and a result is returned to Bob via the XDB Server develop.

As another example, consider that any user accessing develop issues a request referencing data on the XDB Server sales. According to the system table SYSIBM.SYSUSERNAMES on develop, the AuthID on all outbound requests to sales are mapped to developr.

In this case, the system administrator of the XDB Server sales needs to maintain only one account, developr, for users from the XDB Server develop. As users are added and removed from develop, the system administrator of sales does not need to modify accounts or system tables to reflect these changes. No matter what the AuthID on develop, it will be mapped to developr before it is sent to sales.