Open System Services Installation Guide (H06.16+, J06.05+)

symbolic links to TCP/IP configuration files installed in that alternate subvolume. The following
symbolic links are created.
Source File from TCP/IP Installation LocationSymbolic Link
hosts/etc/hosts
inetconf/etc/inetd.conf
protocol/etc/protocols
services/etc/services
resconf/etc/resolv.conf
networks/etc/networks
ipnodes/etc/ipnodes
• Creates these files:
ContentsFile TypeFile SystemFilename
Status messages (see Appendix B
(page 46))
EDIT (file code
101)
GuardianOSSJOURN
Directory tree showing entire OSS
subsystem
EDIT (file code
101)
GuardianOSSTREE
Directory tree showing entire OSS
subsystem
ASCIIOSS/tmp/oss.tree.ddmmmyyyy.system-name
The files OSSTREE and /tmp/oss.tree.ddmmmyyyy.system-name have identical contents.
NOTE: Using the OSSSETUP utility is the first step to configuring the OSS environment. After
the OSSSETUP utility completes, you must finish configuring the OSS environment as described
in “Completing a Preconfigured Basic OSS Environment” in “Manually Setting Up an OSS
Environment” in the Open System Services Management and Operations Guide.
Usage Considerations:
• HP recommends that you log on with the super ID to run OSSSETUP.
• The OSSSETUP utility and the files it creates must be appropriately secured for access by users
other than the super ID, according to your site’s security guidelines. See “Licensing the OSS
Monitor to the Super Group” in the Open System Services Management and Operations
Guide for a possible approach.
• OSSSETUP is on the installation subvolume ZOSSINS. You must run OSSSETUP from ZOSSINS.
You cannot use this command from a remote Expand node.
• You cannot use this command from the system startup TACL session ($YMIOP.#CLCI). You
should use a Telserv session instead.
• The OSSSETUP utility installs all code and text files from current pax archive files in the
ZOSSUTL subvolume into the filesets it creates. The ZOSSUTL subvolume is in the $SYSTEM
volume, you override this location using the EASYSETUP^UTILVOL param.
• The OSS Monitor does not use the $NULL process or require the $ZSMP process for its own
startup. However, not configuring or starting $NULL or $ZSMP could affect the functioning of
other products or subsystems.
• If $NULL or $ZSMP is already running and not configured as a generic object, and you have
used the EASYSETUP^STARTUP param to specify $NULL or $ZSMP, you must stop it before
you can use OSSSETUP to configure it as a generic object. To stop $NULL, use the TACL STOP
Overview 21