Open System Services Management and Operations Guide (G06.29+, H06.07+)

OSS Management Utilities
Open System Services Management and Operations Guide—527191-005
C-11
OSSSETUP Utility
Examples
1. To issue progress messages as EMS events using a ZSPIDEF subvolume on
$SYSTEM when initially configuring and starting OSS, enter:
PARAM EASYSETUP^EMSVOL $SYSTEM
OSSSETUP
2. To issue progress messages as EMS events using a ZSPIDEF subvolume on
$SYSTEM on the remote node \NODE when initially configuring and starting OSS,
enter:
PARAM EASYSETUP^EMSVOL \NODE.$SYSTEM
OSSSETUP
This allows systems in an Expand network to share a ZSPIDEF subvolume instead
of maintaining a separate ZSPIDEF subvolume on each node.
3. To configure and start both $ZSMP and $NULL when initially configuring and
starting OSS, enter:
PARAM EASYSETUP^STARTUP "$ZSMP $NULL"
OSSSETUP
4. To start only $NULL when starting OSS, enter:
PARAM EASYSETUP^STARTUP "$NULL"
STARTOSS
5. To configure and start OSS using an installation subvolume on the disk $DSM,
enter:
PARAM EASYSETUP^UTILVOL $DSM
OSSSETUP
OSSSETUP Utility
The OSSSETUP utility configures a new, basic OSS environment by using the server
and fileset configuration file values discussed in Section 4, Managing Servers
, and
Section 5, Managing Filesets. The T0585AAA version of OSSSETUP also configures
the OSSMON object file ($ZPMON) as a persistent object in the Kernel Subsystem;
T0585AAB and subsequent versions configure $ZPMON as a generic object.
The T0585AAA version of OSSSETUP configures the OSMP object file ($ZSMP) as a
generic object and the NULL object file ($NULL) as a persistent object if they are not
already running. The T0585AAB and subsequent versions of OSSSETUP can be
configured to do that also, but do not do so by default.
The OSSSETUP utility can be used when:
•
Your system was not preconfigured by HP.
•
You do not require more than three filesets (ROOT for /, TEMP for /tmp, and
HOME for /home).