The following table shows values needed in the system table SYSIBM.SYSLUNAMES on the primary XDB Server, develop, to implement the examples discussed in this topic for outbound mapping (without trusting).
| LUNAME | SYSMODE-NAME | USER-SECURITY | ENCRYPT-PSWDS | MODE-SELECT | USER-NAMES |
|---|---|---|---|---|---|
| sales | O |
This table indicates that all requests sent to the XDB Server sales are subject to outbound mapping.
The following table shows the values needed in the system table SYSIBM. SYSUSERNAMES on the XDB Server develop to implement the outbound mapping examples used in this topic. This table also shows several other valid records, explained after the table. Please note that the NO. column is not actually part of the table, and is only displayed for reference.
| NO. | TYPE | AUTHID | LUNAME | NEWAUTHID | PASSWORD |
|---|---|---|---|---|---|
| 1 | O | bob | sales | devbob | devbpass |
| 2 | O | debbie | sales | developr | devpass |
| 3 | O | bruce | sales | developr | devpass |
| 4 | O | eric | sales | devepass | |
| 5 | O | david | devdavid | devdpass | |
| 6 | O | arlene | arlpass | ||
| 7 | O | sales | developr | devpass |
Row 1 maps Bob to devbob for all requests sent to sales. This is the configuration used in the examples on outbound mapping.
Rows 2 and 3 map Debbie and Bruce to developr for all requests sent to sales. Here, developr is assumed to be a group of people.
Row 4 does not map Eric when sending requests to sales. Eric is assumed to be an AuthID on SALES. If Eric tried to go to SALES, the Row 4 mapping would take precedence over the Row 7 mapping because it mentions a specific AuthID.
Row 5 maps David to devdavid anytime outbound requests are sent to any server.
Row 6 does not map Arlene when sending request to any remote servers. Arlene is assumed to be an AuthID on all other servers.
Row 7 maps all AuthIDs to developr when sending requests to sales. The mappings of rows 1 through 6 take precedence over Row 7 mapping because they mention specific AuthIDs.