Locking entries in the distribution table (&LOCK DISTRIBUTION)

For UDS-D

 &LOCK 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.

The following elements can be locked in the local distribution table:

• hosts
  All related NODE/CONF entries are locked.

• configurations
  The related NODE/CONF entry is locked.

• databases
  The related DB entry is locked.

• subschemas
  The related SS entry is locked.

After processing the DAL command &LOCK DISTRIBUTION, UDS-D rejects any READY statement referencing a locked entry.
The application program is assigned the status code 141.

&LOCK DISTRIBUTION blocks access to the specified entry.
For example:
If a subschema is locked, any READY statement referencing that subschema is rejected.
If a configuration is locked, READY statements referencing any of that configuration’s subschemas are rejected. Under local administration &LOCK DISTRIBUTION only changes the local distribution table.

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 DB administrator enters the DAL command below at configuration CONF2:

&LOCK DISTRIBUTION,DB=DB1

This locks 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.