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

products are not NonStop Software Essentials-enabled. You must use COPYOSS for those files,
but you can use NonStop Software Essentials to manage everything else.
CAUTION: Do not use COPYOSS to install OSS files that NonStop Software Essentials manages.
Doing so replaces the NonStop Software Essentials-managed files, which can make it difficult to
determine whether OSS files are managed by NonStop Software Essentials. This confusion can
cause problems in managing OSS files with NonStop Software Essentials.
For NonStop Software Essentials, a physical target system might have more than one OSS hierarchy,
but only one OSS hierarchy can run and be accessible at a time. An OSS hierarchy must be
running for NonStop Software Essentials to manage the OSS files in it. For an OSS hierarchy to
run, the $SYSTEM volume on which ZXOSSMON exists must be the system load volume that is
currently running.
Comparing DSM/SCM to COPYOSS/PINSTALL/PCleanup
• PCleanup removes only old files that OSS products specify to remove. DSM/SCM removes
all files that are not still in the configuration.
• COPYOSS only installs software. DSM/SCM installs and manages the software in parallel
with your Guardian products.
• COPYOSS installs every file every time, overwriting existing files. DSM/SCM installs only files
that need to be installed, reducing downtime.
• Using DSM/SCM, you can back out your OSS files to the previous configuration.
• DSM/SCM provides separate placement and activation processes to minimize application
downtime.
• COPYOSS is somewhat simpler to use, but DSM/SCM activation is faster.
• DSM/SCM can install OSS files to remote systems.
• When DSM/SCM places a new file, the security and ownership attributes are adopted from
the pre-existing file, if any exist. If the file does not exist, the security attributes are designated
by the pax archive file, and the ownership is the DSM/SCM user ID.
Comparing DSM/SCM to COPYOSS/PINSTALL/PCleanup 25