Removing locks from distribution table entries (&UNLOCK DISTRIBUTION)

For UDS-D

 &UNLOCK DISTRIBUTION,
   {NODE=processor-name |
    CONF=confname |
    DB=dbname |
    SS=subschema-name }

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.

Locks can be removed from the following elements in the distribution table:

• hosts

• configurations

• databases

• subschemas

The locked entries in the local distribution table are those which have been locked with the DAL command &LOCK DISTRIBUTION or which have a minus sign prefix in the input file for the distribution table (see section “Structure of the input file for the distribution table”).

&UNLOCK DISTRIBUTION removes blocked access to the specified entry.
Under local administration, &UNLOCK DISTRIBUTION only changes the local distribution table.

Example

When the lock on a subschema is removed, READY statements are again accepted for that subschema. When the lock on a configuration is removed, READY statements are again accepted for subschemas of that configuration unless databases or subschemas have been locked explicitly.

Changes to the distribution table do not take effect until the next READY statement is issued.

Example

The following assignments are present at each configuration and are reflected in the distribution tables:

PROC1	CONF1	DB1
PROC2	CONF2	DB2
PROC3	CONF3	DB3

The DAL command below is entered by the DB administrator at configuration CONF2:

&UNLOCK DISTRIBUTION,DB=DB1

This removes the lock on the database DB1 in the distribution table for configuration CONF2 and has the following effect:

• Application programs that were started with SET-FILE-LINK LINK-NAME=DATABASE,FILE-NAME=CONF2 will now be able to access all subschemas of the database DB1, except for those which were locked explicitly.

• Application programs that were started with another configuration are not affected by the change in this distribution table.