DSM/SCM Quick Reference Guide

Creating an Alternate System Volume and Adding

and Deleting Logical Targets

DSM/SCM Quick Reference Guide—529847-005

2-3

Deleting a Logical Target

a. Click SYSGEN....

DSM/SCM displays the SYSGEN Defaults dialog box.

b. Enter values in the data fields as needed.

c. Click OK.

9. Click OK in the Target Information dialog box.

The new logical target is now defined to DSM/SCM, and its name appears on the

Configuration Revisions window with a revision number of 1.

After the new logical target is defined, you can modify the product list as necessary.

Then build and apply its initial revision, as described in the

DSM/SCM User’s Guide.

Deleting a Logical Target

You can remove a logical target, its profile information, and all of its associated

software revisions from DSM/SCM by first deleting the logical target from the host and

then deleting the logical target from the target system. For more information, see the

DSM/SCM User’s Guide

Deleting a Logical Target From a Host System

After you delete a logical target from the host, it no longer appears in the Configuration

Revisions window. From the Planner Interface:

1. Select a configuration revision from the Configuration Revisions window.

2. Select Maintain>Target maintenance>Delete....

Deleting a Logical Target From a Target System

Deleting the logical target from the host does not delete the logical target from the

target system. You must delete the logical target itself from the target system:

1. Check that ZDSMSCM is the current subvolume; then run the Target Interface:

> VOLUME $

volume

.ZDSMSCM

> RUN ZPHITI

2. Log on to the Target Interface.

3. Select 3 (Perform target activities); then press F1.

4. Select a target; then press F1. The current SYS

appears at the top of the next

screen. Note the SYS

Note. If you are using multiple targets on a system, always run DSM/SCM from the first

ZDSMSCM subvolume installed on the target system. To ensure that the correct installation

files are used, this ZDSMSCM subvolume must also be the one from which INITENV was run.