G06.28 Software Installation and Upgrade Guide

Resuming Normal Operations
G06.28 Software Installation and Upgrade Guide—541688-001
12-14
OSS Unautomated Configuration and Startup
•
If no OSS files are managed by DSM/SCM, use COPYOSS for all of the OSS pax
archives in the ZOSSUTL subvolume. See the OSS Management and Operations
Guide for a description of COPYOSS use or the copyoss(8) reference page in
the OSS Shell and Utilities Reference Manual. Then use PINSTALL to install any
pax archives in other subvolumes. See the OSS Management and Operations
Guide for a description of PINSTALL use, or the pinstall(1) reference page in
the OSS Shell and Utilities Reference Manual.
For any pre- or post installation instructions, see also the appropriate product’s softdoc.
Note OSS Alerts and Considerations
•
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 SMF.
•
For the OSS environment, certain configuration files require symbolic links from the
OSS file system. For more information, see the OSS Management and Operations
Guide for details.
Run the inetd Process
The inetd process should be run immediately after loading the OSS product files into
the OSS environment. The inetd process listens for connections on certain Internet
sockets. When a connection is found on one of its sockets, inetd determines what
service the socket corresponds to and invokes a program to service the request.
See the inetd(8)reference page in the Open System Services Shell and Utilities
Reference Manual for more information. For installation instructions, see
T9660G07^AAG or later softdoc.
OSS Unautomated Configuration and Startup
Unautomated configuration and startup is described in the Open System Services
Management and Operations Guide, Appendix B.
OSS EasySetup (T0585)
The OSS EasySetup product (T0585) is available for automated setup, as described in
the Open System Services Installation Guide. OSS EasySetup is a series of TACL
scripts that assist a site when configuring and installing a minimal OSS subsystem for
the first time or when starting, stopping, or removing an OSS subsystem. For setup
and fallback purposes, OSS EasySetup provides:
•
A journal file of all installation and configuration actions.
•
A file that records the directory structure of the initial OSS file installation.
•
A configuration file to partially automate restarting the OSS subsystem. This file
can be edited as needed when the configuration changes.