m 6.0+)

dba/m Database Manager installation and Operations Manual 522633-004 2-11

Verifies that the Guardian Version is correct and that SQLCI2, TMF, and RSC are

running. If any of these checks fail, then the installation macro displays the appropriate

error message and exits.

Checks for the existence of all dba/m IPM related files, such as program files and IPM

installation macro, in the current sub volume. If the files are not found, the macro will

prompt you to enter the sub volume name where the NonStop dba/m IPM files are stored.

• If the above checks pass then macro:

Copies the program files from $<volume>.ZDBAM to the appropriate

subvolume.

SQL Compiles the Object code

Starts the dba/m Database Manager Pathway Environment.

• Verification of the dba/m Database Manager Macro:

The upgrade procedure writes the output from installation macros to the

terminal and a set of output files stored $<vol>.GENOUT

Where<vol>isthevolumeonwhichNonStopdba/mIPMisinstalled.

Check the outputs mentioned above for errors and warnings. If there are any errors or

warnings, call NonStop Dba/m Database Manager Support before using dba/m.

Start dba/m

At the end of installation, dba/m Database Manager will be started automatically. Verify

correct installation and startup using the procedures described in this section.

Verify Pathmon

To verify that dba/m Database Manager Pathmon was correctly started, type the

following command at the TACL prompt:

To verify that dba/m Database Manager Pathmon was correctly started, type the

following command at the TACL prompt:

PATHCOM $GDB; STATUS SERVER *

The status of the dba/m Database Manager processes will be displayed, for example

SERVER #RUNNING ERROR INFO

ALARMSV 1

CMNDS 1

DBAM 0

GDBAT 1