|
dbname
Name of the database
realm-name
Name of the realm
password
password may be up to four bytes in length and is represented as follows:
C’xxxx’:
where xxxx comprises one through four alphanumeric and special characters
X’nnnnnnnn’:
where nnnnnnnn comprises one through eight hexadecimal digits
d:
where d is a decimal number (comprising up to eight digits and a sign) that is to be converted to a binary value
The syntax conventions for BS2000 apply (see the commands manuals for "BS2000 OSD/BC", ADD-PASSWORD)
admpassword
May be up to four bytes in length and is represented as follows:
C’xxxx’:
where xxxx comprises one through four alphanumeric and special characters
X’nnnnnnnn’:
where nnnnnnnn comprises one through eight hexadecimal digits
d:
where d is a decimal number (comprising up to eight digits and a sign) that is to be converted to a binary value
The syntax conventions for BS2000 apply (see the commands manuals for "BS2000 OSD/BC", ADD-PASSWORD)
The database administrator can detach databases, realms and passwords from a running session by using the DROP command.
Detaching a database
DROP DB=dbname
Detaches the designated database. All the realms involved reach a consistency point. This alters the current DB configuration.
If the given database is not attached and no request to attach it is pending, this command is immediately rejected.
If a request to attach a database (original or copy) which is currently not attached exists, this request is cancelled by DROP DB.
When the database is dropped, the number of DML statements per database and the number of input and output operations per database are output to SYSOUT.
Examples
DROP DB for the SHIPPING database
//EXECUTE-DAL-CMD CMD=DROP DB=SHIPPING % UDS0347 UDS ADMINISTRATION: LOGON = UAD@0E82 (OPDM239,09:30:37/4TTP) % UDS0220 UDS RECEIVED COMMAND: DROP DB=SHIPPING (OPOX073,09:30:37/4TTP) % UDS0218 UDS COMPLETED EXECUTION OF DAL COMMAND (OPCC074,09:30:37/4TTP) //EXECUTE-DAL-CMD CMD=PERFORM % UDS0220 UDS RECEIVED COMMAND: PERFORM (OPOX073,09:30:37/4TTP) % UDS0206 UDS ACCEPTED COMMAND (OPCC012,09:30:37/4TTP) % UDS0356 UDS EXECUTION OF ORDERS FOR CONFEXMP STARTED (OPCC309,09:30:38/4TTP) % UDS0722 UDS ORDER DROP DB=SHIPPING IN EXECUTION (OPCC283,09:30:38/4TTP) % UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (OPCC758,09:30:38/4TTP) 4TTP: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE 4TTP: ------------------------------------------------------------------------ 4TTP: SHIPPING 0 67 57 5 5 % UDS0356 UDS EXECUTION OF ORDERS FOR CONFEXMP TERMINATED (OPCC309,09:30:40/4TTP) % UDS0218 UDS COMPLETED EXECUTION OF DAL COMMAND (OPCC074,09:30:41/4TTP)
DROP DB for several databases
//EXECUTE-DAL-CMD CMD=DROP DB=SHIPPING % UDS0220 UDS RECEIVED COMMAND: DROP DB=SHIPPING (OPOX073,09:30:45/4TTP) % UDS0218 UDS COMPLETED EXECUTION OF DAL COMMAND (OPCC074,09:30:45/4TTP) //EXECUTE-DAL-CMD CMD=DROP DB=CUSTOMER % UDS0220 UDS RECEIVED COMMAND: DROP DB=CUSTOMER (OPOX073,09:30:45/4TTP) % UDS0218 UDS COMPLETED EXECUTION OF DAL COMMAND (OPCC074,09:30:45/4TTP) //EXECUTE-DAL-CMD CMD=PERFORM % UDS0220 UDS RECEIVED COMMAND: PERFORM (OPOX073,09:30:45/4TTP) % UDS0206 UDS ACCEPTED COMMAND (OPCC012,09:30:45/4TTP) % UDS0356 UDS EXECUTION OF ORDERS FOR CONFEXMP STARTED (OPCC309,09:30:46/4TTP) % UDS0722 UDS ORDER DROP DB=SHIPPING IN EXECUTION (OPCC283,09:30:48/4TTP) % UDS0722 UDS ORDER DROP DB=CUSTOMER IN EXECUTION (OPCC283,09:30:48/4TTP) % UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (OPCC758,09:30:48/4TTP) 4TTP: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE 4TTP: ------------------------------------------------------------------------ 4TTP: SHIPPING 0 67 50 5 5 4TTP: CUSTOMER 0 31 22 4 4 % UDS0356 UDS EXECUTION OF ORDERS FOR CONFEXMP TERMINATED (OPCC309,09:30:48/4TTP) % UDS0218 UDS COMPLETED EXECUTION OF DAL COMMAND (OPCC074,09:30:49/4TTP)
Detaching a realm
DROP RN=realm-name
[,DB=dbname]
The DBH notes a request to detach the realm realm-name or cancels a pending ADD request. The realm reaches a consistency point before it is detached.
DB=dbname need only be specified if the realm name is not unique throughout the DB configuration. It then specifies the intended database.
The DROP RN command cannot be executed if the database has been locked against updating accesses by means of PP DBNAME=dbname,SHA. No communication is possible between the DBHs accessing this database in parallel.
Detachment of realms is appropriate in the following cases:
Device shortages: realms can be detached in a consistent state either logically or physically.
Hardware errors where the DBH does not automatically detach the realm concerned: following a DROP and subsequent PERFORM command, the database administrator can reconstruct the realm using BMEND while the session is running. In order to do this, all ALOG files required for repairing the realm must be available. If the current ALOG file of the database in question is needed for the repair, a CHECKPOINT command must also be issued.
The DROP DB and DROP RN requests are not executed until the PERFORM command is issued to initiate execution. A failsafe log of the exclusion of a realm is not entered in the DBDIR until the request has been processed in full. A failsafe exclusion is one that remains in effect following session aborts and DBH termination.
The DROP command is the exact counterpart of the ADD command. As long as execution of a pending ADD request has been not yet initiated by means of PERFORM, the ADD command can be canceled by means of DROP.
The DBDIR realm cannot be detached.
Excluding a file password
DROP PW=password
Excludes the given file password from the set of passwords.
When DROP PW is specified, the DBH checks whether the specified file password is actually known. If it is, the DBH cancels the specified file password. If not, the DROP PW command is rejected by the DBH.
File passwords should not be excluded until the corresponding files have been detached (see section “Assigning passwords to UDS/SQL files”).
Excluding an database administrator password
DROP ADM=password
Excludes the given database administrator password.
When DROP ADM is specified, the DBH checks whether the specified database administrator password is actually known. If it is, the DBH cancels the specified database administrator password. If not, the DROP ADM command is rejected by the DBH.
The DROP PW and DROP ADM commands are executed immediately without a PERFORM being issued.