G06.25 Software Installation and Upgrade Guide
Resuming Normal Operations
G06.25 Software Installation and Upgrade Guide—529430-001
12-14
Configure SMF (Optional)
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 Appendix B in the Open System 
Services Management and Operations Guide.
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.
OSS EasySetup requires the process $NULL and the installation of SPI template files. 
The product NULL (T6025) is included on each SUT.
Configure SMF (Optional)
If you plan to configure SMF, an optional product, note:
•
Migration of data from direct volumes to SMF logical volumes is documented in the 
Storage Management Foundation User's Guide.
•
Performance-critical applications that optimize the physical location of their data 
might need to specify the PHYSVOL option when creating data files, instead of 
relying on the SMF file-placement algorithm.
•
NonStop SQL/MP 3.x must be up and running before you start SMF. 
Caution. To maintain data integrity, do not place:
•
SWAP files on a virtual disk process (VDP)
•
TMF audit data on a VDP.
•
DSM/SCM files on a VDP.










