Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Central administration

&pagelevel(5)&pagelevel

In the case of central administration, all DB configurations are addressed from a single console, i.e. every DBH involved can be started, administered and terminated from the same console.

It is also possible to administer multiple DB configurations centrally

Central administration using OMNIS

OMNIS communicates messages between the database administrator and the DBHs to be managed, regardless of which hosts are running these DBHs.

Figure 27: Central administration using OMNIS


Starting and administering DBHs with OMNIS

For operational security reasons, it is advisable to start UDS/SQL as an ENTER job and to perform administration tasks via UDSADM or the DCAM interface.

All DBHs must be started with the DBH load parameter PP ADM=REMOTE (see PP ADM in chapter "DBH load parameters"). This causes every DBH to open a DCAM application for administration with the application name confname.
The database administrator connects OMNIS with these DCAM applications or starts UDSADM in multiple tasks and can then address all DBHs via OMNIS from one console.

If the connection to OMNIS is down, the database administrator can also manage the DB configuration locally.
Central administration can be resumed as soon as OMNIS is available again, assuming that the configuration is not being managed locally.

In the OMNIS administration concept, all data terminals have the same privileges. Consequently, it is only possible to provide limited protection against unauthorized interference with the UDS/SQL administration.