In most cases, the SESDCN distribution component need only be loaded once per configuration. However, a large number of remote accesses of an SESDCN can have a negative effect on runtime behavior.
You can increase total throughput of remote accesses by starting several SESDCNs. Remote requests are then processed concurrently by more than one SESDCN.
A DBH may only ever be assigned to one SESDCN.
(A DBH can occur in several entries of the ADD-DISTRIBUTION-RULE-LIST statement if this DBH has several catalogs. The same LINK-NAME must be used in all these DBH entries and then describes the route via a DCN in the ADD-NETWORK-LINK-LIST statement. If this condition is not met, the statement is rejected with message SEN1003.)
Several DBHs can be assigned to a single SESDCN.
The SESDCN started first in a configuration assumes the function of the master DCN. When necessary, the master DCN carries out the SESDCN restart.
When starting the master DCN, you must define the distribution rule by means of the appropriate control statements. You can start the other SESDCNs in a configuration without defining the distribution rule, i.e. without supplying information on databases.