When used independently of each other, outbound mapping, inbound mapping, and trusting are easy procedures to set up. However, if you wish to use these features together, you should plan out your mapping and trusting scheme before implementing it.
Some concepts, such as AuthID, password, groups, and priorities are controlled on a per server basis. Others, such as database and table privileges, are controlled on a per location basis.
If you will be using inbound mapping and outbound mapping between two servers you must be sure that your system tables cover all possible mappings. For example, requests from Bob on the XDB Server develop to the XDB Server sales will be subject to outbound mapping on develop. Requests from Debbie on develop to sales will be subject to inbound mapping on sales.
To allow this scenario, you must have one additional row in the SYSIBM.SYSUSERNAMES tables on each XDB Server (sales and develop) that indicates requests from these users should not be mapped.