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

File Placement Locations
DSM/SCM places files during an apply in a target subvolume (TSV) or target directory location
(TDL).
• Target Subvolume (TSV)
When DSM/SCM places Guardian files during an Apply, and a different version of the file
already exists in the TSV, the file is placed under a temporary name of the form ZFBccncc.
Do not purge these ZFB* files. They are deleted in normal DSM/SCM processing.
Multiple copies of changed files might be in the TSV at a given time. TSVs might contain
Guardian files under both their actual names and their temporary names, requiring more disk
space for software on target systems. Do not purge these files. DSM/SCM deletes them when
possible.
Because only changed files are sent in most Apply requests, the number of temporary files is
representative of the number of changes made to the TSV in the last Apply.
• Target Directory Location (TDL)
DSM/SCM places packaged OSS files that it manages in a TDL on a logical target. Unlike a
TSV, a TDL specifies an absolute path. You cannot control the location of a TDL. For example,
you cannot copy or move a TDL to another location. DSM/SCM manages OSS files in a TDL
only.
Prepare for a Build and Apply Request
You can submit the Build and Apply requests together or separately, depending on the connection
between your host and target systems. This section covers both procedures because they are often
executed in a single request. If the Build and Apply are submitted in a single request and the target
system is connected to the host system using Expand, the activation package is automatically
applied to the target system.
The steps needed to prepare for Build and Apply requests include:
• “Check If Additional Disk Space Is Required” (page 110)
• “Check That the Spooler Is Active” (page 110)
• “Collect the Information Needed for the Build” (page 111)
• “Specify PARAMs as Needed” (page 111)
• “Assemble the Planner Instructions to the Operator” (page 111)
Check If Additional Disk Space Is Required
Before performing a Build/Apply, check the amount of additional disk space you might need on
the volume for new and changed files. For example, if your past configurations normally take about
1500 megabytes of disk space and your new configuration has few changes, you might need
only 20 megabytes of additional free disk space (total disk space of 1520 megabytes) to process
that Apply.
Check That the Spooler Is Active
Check that the spooler is active if you are installing a different SUT.
110 Primary Build and Apply Process