G06.26 Software Installation and Upgrade Guide
Overview of Installing G06.26
G06.26 Software Installation and Upgrade Guide—529886-002
1-27
OSS (G06.12 through G06.26)
For fallback issues, see the OSM Migration Guide. The guide covers OSM and TSM 
coexistence and fallback issues, such as:
•
Comparison of OSM to TSM
•
OSM hardware and software requirements
•
Migrating an existing TSM system list to a new console for OSM use
•
coexistence issues for using both OSM and TSM
•
Fallback instructions for changing configuration from OSM back to TSM
OSS (G06.12 through G06.26)
As of G06.12, the format of the records in the OSS configuration databases has 
changed. A special SPR, T8622AAH, ensures backward compatibility if you need to fall 
back to an RVU prior to G06.12.
These are additional considerations for OSS upgrade and configuration:
•
Disk volumes that are accessed by the OSS environment, including the $SYSTEM 
volume where the OSS Monitor’s configuration files are kept, must not be 
configured for administration by the HP NonStop Storage Management Foundation 
(SMF).
•
Beginning with the G06.18 RVU, OSSMON is not dependent on $ZSMP to be 
started. (In earlier G-series and D-series RVUs, when you configured OSSMON to 
start automatically during the system load process, you had to configure the 
Safeguard security manager process $ZSMP to start automatically before 
OSSMON was started.) 
•
Starting with G06.26, Safeguard volume protection records are no longer required 
for creation of OSS files.
•
For more information, see:
°
Open System Services Installation Guide
°
Open System Services Management and Operations Guide
°
Interactive Upgrade Guide
°
Support Note S01025
°
T8621 SPR
•
Beginning with the G06.18 RVU, all OSS SUT-based products with pax files must 
have the A7CINFO file in their DSVs to be installed by DSM/SCM. Before installing 
the SUT:
°
Check the Interactive Upgrade Guide for DSM/SCM support and other new 
features and possible migration issues.
°
Check the appropriate softdoc for the OSS product. 
°
Check that all OSS file sets used by DSM/SCM for OSS file installation are 
mounted and started. 










