Mixed environment

SUPER.SUPER and the initial global DBS administrator user are added as security administrators in SQL/MX.

If users are not configured with CREATE CATALOG management privilege, configuring DBS on the system grants CREATE CATALOG management privilege to SUPER.SUPER and global DBS administrator user. Other users are then restricted from creating their own catalogs on the system. A SQL/MX security administrator must explicitly grant CREATE CATALOG privilege to users wanting to create their own catalogs.

The global DBS administrator user configured by DBS is added to Safeguard as administrator who can manage users and volumes. The global DBS administrator user is also added to security-group as security-persistence-admin who can manage NSK persistent process.

DBS is configured with dedicated data volumes on the system. The data volumes configured for DBS are protected by Safeguard. That is, the volumes are for exclusive DBS use and other users on the system cannot create objects in the data volumes configured for DBS.

The global DBS administrator user is added as operator for MXCS administration.

The CPUs configured for DBS user are available for other applications accessing SQL/MX outside of DBS. If CPUs are shared between applications accessing SQL/MX and user databases, CPU utilization by one could impact the other applications sharing CPU. If a system is going to be shared for regular users and for DBS, then ensure that dedicated CPUs configured for DBS are not used by other SQL/MX applications coexisting on the system.

The DBS environment is configured with dedicated MXCS services for application access to the user databases. Other MXCS services can coexist with services configured for DBS. Other users of the system can access SQL/MX database using the services configured outside of DBS. Regular Guardian users cannot access the databases in DBS environment.