G06.25 Software Installation and Upgrade Guide

Overview of Installing G06.25
G06.25 Software Installation and Upgrade Guide—529430-001
1-29
OSS (G06.12 through G06.25)
See the sleep(1) reference page either online or in the Open System Services
Shell and Utilities Reference Manual for more information about the sleep
command.
For more information about the new attribute and considerations for its use, see
the SCF Reference Manual for the Kernel Subsystem.
•
Beginning with the G06.24 RVU, the OSS gtacl command has two more optional
flags added to its command line. See the T8628AAJ softdoc for more information.
If you have to fall back to a previous RVU, scripts that contain one or more of these
optional flags must be revised because the function will not be available.
Open System Services (OSS) and DSM/SCM (T6031D46 PVU)
Starting 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. Check the Interactive
Upgrade Guide or the softdoc corresponding to the OSS products to ensure that the
A7CINFO file is present.
If the OSS product is released without the A7CINFO file, you can still install the product
by using PINSTALL or COPYOSS.
If the OSS product is released with the A7CINFO, do not use PINSTALL/COPYOSS to
install those pax (archive) files; these files are installed and maintained by DSM/SCM.
The Receive Software activity for the OSS products with A7CINFO files in their DSVs
can only be performed when the installation of the new product version (PVU)
T6031D46 is complete on the Host. The T6031D46 PVU of DSM/SCM is required to
process the A7CINFO files present in the DSVs of the OSS products.
When using DSM/SCM to receive the SUT and perform a Build/Apply, you must
perform the following tasks:
1. When performing a DSM/SCM Receive Software activity on the Host, select the
Receive all files option.
2. In the Planner Interface for the Target system, select the Manage OSS Files
option.
3. Check that the OSS Root Name Server $ZPNS is running on the Target. The
volume where the SYSnn is being placed must be up as $SYSTEM to install OSS
files.
4. After you run ZPHIRNM, run the merge_whatis command. If you have OSS
configured to run the OSS merge_whatis utility automatically, you can ignore
running merge_whatis.
Unautomated configuration and OSS startup is described in Appendix B in the Open
System Services Management and Operations Guide.