G06.25 Software Installation and Upgrade Guide

Overview of Installing G06.25
G06.25 Software Installation and Upgrade Guide—529430-001
1-28
OSS (G06.12 through G06.25)
•
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.
For more information, see:
°
Open System Services Installation Guide
°
Open System Services Management and Operations Guide
°
Interactive Upgrade Guide
°
Support Note S01025
•
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.
•
Beginning with the G06.23 RVU, you can use SCF to configure an OSS process as
a persistent process under the persistence manager ($ZKRN). To configure OSS
persistent processes, install these SPRs (all but one is on the G06.25 SUT):
°
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.