For UDS-D
|
processor-name
Name of a host;
must be no more than eight characters in length.
confname
The first eight characters of configuration-name; must be unique in its first seven characters. The eighth character must not be ’@’. Trailing zeros are nonsignificant characters, i.e. there is no difference between confname ABC and confname ABC0.
dbname
Name of a database;
may be up to 17 characters in length;
must be unique network-wide.
subschema-name
Name of a subschema;
must be no more than 30 characters in length;
must be unique network-wide in its first six characters.
This command deletes entries from the distribution table (see section “Structure of the distribution table”).
&DROP DISTRIBUTION,ALL
These operands are used to delete all the entries. When the command has been executed the distribution table is empty. To create a new distribution table, a new input file must be read in using the command &ADD DISTRIBUTION,FILE=...
&DROP DISTRIBUTION,
NODE=...,CONF=...[,ALL]
These operands are used to delete the specified NODE/CONF entry.
The suffix ALL causes all DB and SS entries chained to the NODE/CONF entry to also be deleted.
&DROP DISTRIBUTION,
NODE=...,CONF=...,DB=...[,ALL]
These operands are used to delete the specified DB entry if it is chained to the specified NODE/CONF entry or it is not chained to any NODE/CONF entry.
The suffix ALL causes all SS entries chained to the DB entry to be deleted as well.
&DROP DISTRIBUTION,
DB=...,SS=...
These operands are used to delete the specified SS entry if it is chained to the specified DB entry or it is not chained to any DB entry.
Example
The following assignments are present at each configuration and are reflected in the distribution tables:
|
|
|
|
|
|
|
|
|
The DB administrator enters the DAL command below at configuration CONF2:
|
This deletes the DB entry for the database DB1 in the distribution table of configuration CONF2 and has the following effect:
Application programs that were started with
SET-FILE-LINK LINK-NAME=DATABASE,FILE-NAME=CONF2
can no longer access the subschemas of the database DB1.Application programs that were started with another configuration are not affected by the change in this distribution table.
Changes to the distribution table do not take effect until the next READY statement is issued.