DSM/SCM User's Guide
Configuring DSM/SCM
DSM/SCM User’s Guide — 529846-014
5 - 18
Managing Logical Targets
You cannot perform an initialization Build/Apply if it was previously performed on
any other logical target created on that particular physical target system.
To add a logical target:
1. In the Configuration Revisions window, select the system to which you are adding
the new logical target.
2. Select Maintain>Target maintenance>Add....
3. In the New Target dialog box, enter a name for the new logical target in the Target
name field. When creating multiple logical targets, distinguish targets by giving
meaningful names.
4. Select another logical target from which to copy profile data in the Copy profile data
from list.
5. Click Setup. DSM/SCM displays the Target Information dialog box.
6. From the Target Information dialog box:
a. Check the defaults and update as needed. (Target Profile on page 17-6)
b. Click OK.
The new logical target is defined to DSM/SCM, and its name appears in the
Configuration Revisions window with a revision number of 1.
7. Modify the product list as necessary, then build and apply the initial revision for this
logical target. See Section 8, Creating and Managing Software Revisions.
Initializing a Logical Target
Initialize the logical target on the host system after these procedures
Adding a logical target to a system. See Adding a Logical Target on page 5-17. You
cannot perform an initialization Build/Apply if it was previously performed on any
other logical target created on that particular physical target system.
Using INITENV with the initialization option
To initialize the target:
1. Log on to the Planner Interface.
2. In the Configuration Revisions window, select the configuration name for the ta
rget.
For a new target, the name has the form:
\system_name DEFAULT
Note. If you use multiple logical targets on a system, always run DSM/SCM from the first
ZDSMSCM subvolume installed on the target system. To ensure the correct installation files
are used, this ZDSMSCM subvolume must also be the one from which INITENV was run.