HP Integrity NonStop H-Series - Manual (Page 38)

Introduction to DSM/SCM
DSM/SCM User’s Guide — 529846-014
1 - 5
DSM/SCM Archive
Logical Targets
A logical target is a specific software configuration on a target system. Every system,
including the host system, contains at least one logical target. The host activates and
manages its own software as it does for any of its target systems.
To manage different software configurations independently can manage different
software configurations independently on a single system, use multiple logical targets.
Provide a unique name for each logical target on the system. Each logical target
requires its own separate $SYSTEM volume. The same host system must manage all
the logical targets on a system.
DSM/SCM Archive
The DSM/SCM archive on the host system provides storage for software received into
DSM/SCM. The DSM/SCM archive stores:

All the software input into DSM/SCM from release version updates (RVUs),
software product revisions (SPRs), and third-party products. The configuration
revisions use the archived files when the software is configured.

The system generation output for configurations, including the OSIMAGE file.
The archive is located on one or more volumes of the host system. The planner
specifies the archive volumes when configuring DSM/SCM and can add or change
volumes using the Host Maintenance Interface (ZPHIHMI).
The software remains in the archive. You can copy software from the archive to update
the software configuration of a system.
Host and Target Databases
Each DSM/SCM system has one or more SQL databases for storing configuration
information. Each database must be located on a volume that is audited by HP
NonStop Transaction Management Facility (TMF) and has sufficient free space. The
volume name, including the dollar sign, cannot exceed seven characters. To ensure
the volume name does not change, do not place the host or target database on an
alternate system disk.
Host Database
The host database must reside on the host system and contains information about
requests, software, snapshots, configurations, and profiles. This information is
essential to the operation of the Planner Interface.