When the DBH is started with the independent DBH, the DBH load parameter PP DISTRIBUTION can be used to control whether or not UDS-D mode is to be started for a configuration (see section “The session”). If UDS-D mode is started, the configuration may participate in it. Participating in the UDS-D mode means that local application programs can start distributed transactions and can process DML statements of remote application programs.
PP DISTRIBUTION=NO(default): This means that the configuration does not participate in UDS-D mode in the initiated session. In other words, local application programs cannot start distributed transactions and cannot process secondary subtransactions from remote application programs. Any attempt to access a database of this configuration from a remote application program is rejected with status code 141.PP DISTRIBUTION=START: The configuration will automatically participate in UDS-D mode, as soon as the DBH is started.PP DISTRIBUTION=STANDBY: The configuration is prepared for UDS-D mode, but does not participate in it until the DAL command&START DISTRIBUTIONis issued by the database administrator to start the UDS-D mode.
If you have set the DBH load parameter PP DISTRIBUTION to START or STANDBY, the master task will, on starting up, place the ENTER file for the UDS-D task UDSCT under the user ID in which you started the DBH under the following name:
UDS.ENTER.tsn.CT000
tsn Task sequence number of the master task
If PP DISTRIBUTION=START is specified, the ENTER job is started immediately.
The ENTER file continues to exist until DBH termination, even if the UDS-D mode is terminated beforehand.
Further DBH load parameter to control UDS-D mode can be found in section “DBH load parameters for UDS-D” and in chapter “DBH load parameters”.
Distributed RETRIEVAL transactions, by contrast, are allowed with PP LOG=NO.