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

Figure 1-2 Software Configuration Management Overview
Managing the SYSnn Subvolumes
During the Build request, , if needed, a new operating system image is created. For software
updates that do not require system generation, you can use the current SYSnn. When system
generation is required for an RVU or SPR, you may have to specify a new SYSnn. However, you
should minimize the number of SYSnn subvolumes on each target. NonStop Software Essentials
requires only one SYSnn in order to operate. If you need to back out to a previous revision, you
need the previous SYSnn if the previous revision was not on the current SYSnn.
File Types Supported
NonStop Software Essentials supports both format 1 Guardian and OSS file types < 2GB.
Guardian File Types Supported
All Guardian files are always accessible to all logical targets.
OSS File Types Supported
NonStop Software Essentials supports the management of these OSS file types:
• Directories
• Hard and symbolic links
• Regular files (disk files)
You can configure NonStop Software Essentials to manage OSS files. This requires that all OSS
products contain an A7CINFO file. If you do not configure NonStop Software Essentials to manage
OSS files, you must use COPYOSS and PINSTALL. Use COPYOSS and PINSTALL only if some OSS
24 Introduction to the Role of NonStop Software Essentials in NonStop Software Management