G06.26 Software Installation and Upgrade Guide

Overview of Installing G06.26
G06.26 Software Installation and Upgrade Guide—529886-002
1-28
OSS (G06.12 through G06.26)
•
Beginning with the G06.23 RVU, you can use SCF to configure an OSS process as
a persistent process under the persistence manager ($ZKRN). These necessary
SPRs are available on the SUT, except T8397G00^ABA:
°
T1084G06^AAH
°
T1085G06^AAL
°
T6586G07^AAU
°
T5800G06^AAP
°
T9082ACX (SCF)
°
T9082G02^ACX
°
T8624G10^AAM
°
T8397G00^ABA (See your service provider for SPR availability.)
OSS persistent processes can be used without SPRs T8624G10^AAM and
T8397G00^ABA. If those SPRs are not installed, some OSS applications might fail
at processor startup unless modified to include an initial delay (on the order of 10
seconds). This delay is not needed when you install those SPRs. All but one is on
the G06.25 SUT.
Without T8624G10^AAM and T8397G00^ABA, when an OSS shell is launched
immediately after a processor comes up, the shell needs to wait until processor
components of the OSS environment such as the OSS pipe server finish
initialization. The necessary delay can be achieved by adding an OSS sleep 10
command either to the STARTUPMSG attribute or as the first entry in the script
launched by the STARTUPMSG attribute.
For more information about the sleep command, see the sleep(1) reference
page either online or in the Open System Services Shell and Utilities Reference
Manual
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.