mxdbs [-h] [-V] subcommands

Sub-commands are

{ db-create | db-delete | db-alter-share | db-add-user | db-remove-user | db-add-storage | db-user-change-access | user-change-password | show-databases }


Executes the mxdbs command-line utility.


Sub-command Description
db-create Creates a database.
db-delete Deletes a database.
db-alter-share Shares or unshares a database.
db-add-user Adds a user to a database.
db-remove-user Deletes a user from the database.
db-add-storage Adds storage to a database.
db-user-change-access Modifies the access level of a user in the database.
user-change-password Modifies the password for a user in the system.
show-databases Displays all the databases on the system.


Displays the usage information for mxdbs utility and exits.
Displays the version procedure for mxdbs utility and exits.


  • The MXCS service configured at the time of DBS installation for application access must be running on the system.

  • Database services require the system to be running SQL/MX software version 3500 or higher and system schema version 3500 or higher.
  • The system must be configured for DBS with InstallDBS script before using the database services.

  • Safeguard process $ZSMP must be running on the system.


The global DBS administrators, who are users authorised to manage databases without being database users themselves or SUPER.SUPER can execute the mxdbs sub-commands. The DBS administrators have DDL privileges on all the user database schemas to manage the database objects. However, the DBS administrators will not have access to the data in the user tables.


The mxdbs sub-commands can be executed concurrently from different sessions. At any given time, only one mxdbs sub-command is active and concurrent mxdbs commands will wait until the active command completes. If the active mxdbs sub-command does not complete in 3 minutes, concurrent waiting commands will fail and the user must retry the operation.


When a mxdbs sub-command operation fails, all the changes made to the database until then are reverted and the database is restored to a consistent state. In case of system or CPU failure, which abruptly terminates the operation, the database remains in an inconsistent state until the next mxdbs command is executed. The subsequent mxdbs command first performs recover cancel operation to bring the database to a consistent state and then performs the actual operation. If there is a failure during recover cancel operation, an error is returned. Contact the service provider or system administrator to correct the reported problem.