G06.30 Software Installation and Upgrade Guide

Overview of Installing G06.30
G06.30 Software Installation and Upgrade Guide—543764-002
1-33
Additional OSS Issues
FUP PURGE MYFILE
FUP RENAME TEMP, MYFILE
•
Protect the program by creating a Format 1 file, then appending the desired data to
the file. For example, replace the command:
cp myfile /G/mydisk/mysubvol/myfile
with the commands:
gtacl -c ’FUP CREATE $mydisk.mysubvol.myfile, FORMAT 1, &
TYPE U, ODDUNSTR, CODE 180, EXT (28,1400), MAXTENTS 749’
cat myfile >> /G/mydisk/mysubvol/myfile
Additional OSS Issues
OSS Configuration Database Changed
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.
Upgrade and Configuration Considerations
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 does not require $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
to create OSS files.
•
For more information, see:
°
Open System Services Installation Guide
°
Open System Services Management and Operations Guide
°
Interactive Upgrade Guide 2
°
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: