The following table shows values needed in the system table SYSIBM.SYSLUNAMES on the remote XDB Server sales to implement the examples discussed in this topic for inbound mapping (without trusting).
| LUNAME | SYSMODE-NAME | USER-SECURITY | ENCRYPT-PSWDS | MODE-SELECT | USER-NAMES |
|---|---|---|---|---|---|
| develop | I |
This table indicates that all requests received from the XDB Server develop are subject to inbound mapping.
The following table shows the values needed in the system table SYSIBM. SYSUSERNAMES on the XDB Server sales to implement the inbound 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 | i | debbie | develop | developr | |
| 2 | i | arlene | develop | nora | |
| 3 | i | develop | developr | ||
| 4 | i | harold | harry |
Row 1 maps Debbie to developr for all requests received from the XDB Server develop. This is the configuration used in the examples on inbound mapping.
Row 2 maps arlene to nora for all requests from the XDB Server develop.
Row 3 maps any AuthID to developr for request received from the XDB Server develop.
Row 4 maps harold to harry for requests received from any XDB Server.
In this example, rows 1, 2 and 4 take precedence over row 3 because they mention specific AuthIDs.