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

multiple RVUs, the DSM/SCM archive must be on a volume with a name of no more than seven
characters ($xxxxxx) . The archive volume must be network accessible to the system.
Many procedures in this guide assume that $AUDIT is the location for the archive and TMF audit
trails. If you move the archive and audit trails, update your procedures accordingly. For instructions
on how to move the archive, see
“Moving the NonStop Software Archive through ZPHIHMI”
(page 164) .
Description Subvolume
Contain DSM/SCM archive files (product DSVs). DO NOT
ALTER OR PURGE THESE SUBVOLUMES. $volume.ZPHIcncc.ZPHIcncc
ZPHI0001
ZPHI0002
ZPHI0003
ZPHI0004
TMF audit-trail files. ZTMFAT
Configuration Files
DSM/SCM uses the information in the configuration files to install and manage product files:
• “A0CINFO Files” (page 236)
• “A1CINFO Files” (page 236)
• “A7CINFO Files” (page 236)
A0CINFO Files
The A0CINFO file for a product contains records that describe the product and its files. Every
distribution subvolume (DSV) used as an input to DSM/SCM must contain an A0CINFO file. The
A0CINFO file includes product and file dependencies, how the files are used, where they are
placed, and which type of processor the product runs on.
HP includes an A0CINFO file in the DSV of each of its software products. HP customers and
third-party vendors developing software to be managed by DSM/SCM must create an A0CINFO
file for every DSV. To specify or change any of these attributes through CNFGINFO, enter
information and select options in the CNFGINFO dialog boxes.
A1CINFO Files
DSM/SCM requires an A1CINFO configuration file for shared run-time library (SRL) products on
NonStop S-series systems. A1CINFO configuration files are distributed with SRL products.
CNFGINFO has not been updated to handle A1CINFO files. Otherwise, you should be able to
treat any A1CINFO file that you see just as you would any A0CINFO file.
A7CINFO Files
DSM/SCM requires A7CINFO files to manage OSS products. Every OSS product DSV that
DSM/SCM manages requires both an A0CINFO and an A7CINFO file. In addition, these constraints
apply to pax files and OSS product DSVs:
• Each OSS DSV to be managed by DSM/SCM must contain a pax file.
• Pax files must be distributed to the ZOSSUTL TSV. Furthermore, only pax files may be distributed
to the ZOSSUTL DSV.
• Pax files may contain only absolute paths. (Relative paths are not allowed.)
• File paths may not contain /G, /E, .dsmscm.*, or zzDSMSCM.Managed.
Scratch Volume
Although these files are temporary, do not delete them.
$scratch.ZISSCnnn.ZSIGSCRA IS Scratch Subvol
$scratch.ZACFGnnn.* System Generation Configuration Files
$scratch.ZATLSnnn.* System Generation Tools
236 Required Processes and Files