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

ASSIGNs and PARAMs
DSM/SCM User’s Guide — 529846-014
E - 12
KEEP-OBSOLETE-SYSNN Param
This PARAM remains active for all Apply requests for the target until you delete it using
PATHCOM.
KEEP-OBSOLETE-SYSNN Param
DSM/SCM normally deletes the obsolete SYSnn as part of normal cleanup during a
Build/Apply. However, you can choose to keep the obsolete SYSnn. subvolume.
1. Before the Apply begins, pass the KEEP-OBSOLETE-SYSNN PARAM to the
Target Activator server (TA-001):
> PATHCOM $YPHI

= Alter TA-001, PARAM KEEP-OBSOLETE-SYSNN
or
> PATHCOM $YPHI; Alter TA-001, PARAM KEEP-OBSOLETE-SYSNN
The SYSnn and CSSnn made obsolete in this Build/Apply become unmanaged but
are not purged by DSM/SCM.
The TA saves only the obsolete SYSnn and CSSnn. All other TSVs are purged.
2. Turn off the keep function by deleting the KEEP-OBSOLETE-SYSNN PARAM:
> PATHCOM $YPHI

= ALTER TA-001, DELETE PARAM KEEP-OBSOLETE-SYSNN
or
> PATHCOM $YPHI; ALTER TA-001, DELETE PARAM KEEP-OBSOLETE-
SYSNN
To confirm the addition or deletion of the PARAM:
> PATHCOM $YPHI; INFO TA-001
Example
1. With the current configuration SYS00, perform a Build/Apply and system load
SYS01:

SYS00 becomes the previous configuration.
2. Build/Apply and system load SYS02:

SYS00 and CSS00 become obsolete and are purged.

SYS01 becomes the previous configuration.
3. Pass KEEP-OBSOLETE-SYSNN to the TA:

Subsequent obsolete SYSnn subvolumes and CSSnn subvolumes, such as
SYS00 and CSS00 in Step 2, are saved and become unmanaged.
Note. All future Build/Apply request also keep the obsolete SYSnn until you turn off the
keep function.