Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

Stopping OSSTTY
To stop a copy of the OSSTTY process started through either the OSH command or from a TACL
prompt, use the TACL STOP command. Use the STOP command carefully; when OSSTTY does not
terminate normally, any EDIT files it has open might not be properly closed and data could be lost.
To stop a copy of the OSSTTY process monitored by the persistence manager, use the SCF Kernel
subsystem ABORT PROCESS $ZZKRN.#ZTTY command.
EasySetup Utilities
The OSS EasySetup utilities can be used to partially automate operation of the OSS environment.
These utilities consist of the scripts, data files, and library files described in Table 18 (page 399).
Table 18 The EasySetup Utilities
DescriptionComponent
A TACL macro (script) that executes either interactively or without interactive
dialog.
“OSSSETUP Utility” (page 402)
A TACL macro (script) that executes without interactive dialog.“STARTOSS Utility” (page 405)
A TACL macro (script) that executes without interactive dialog.“STOPOSS Utility” (page 406)
A TACL macro (script) that executes interactively.“OSSREMOV Utility” (page 407)
An EDIT file used by OSSSETUP that contains entries it configured for entities
managed through the OSS Monitor. This file is supplied by HP.
“OSSINF File” (page 408)
An EDIT file that initially duplicates the contents of OSSINF. OSSINFIL is used
by STARTOSS and is created by it when the file cannot be found. This file is
“OSSINFIL File” (page 408)
created in the volume and subvolume from which the STARTOSS utility is run.
You should create this file yourself before you use STARTOSS for the first time.
An EDIT file containing all messages logged by the OSSSETUP utility. This file
is created in the volume and subvolume from which the OSSSETUP utility is
run.
OSSJOURN file
A library of routines shared among the OSS EasySetup utilities.OSSLIB file
An EDIT file and an ASCII text file, respectively, containing a list of all
directories created in the OSS file system. These files are created by the
OSSTREE file and /tmp/oss.tree.
ddmmmyyyy.system_name file
OSSSETUP utility and contain the result of the following OSS shell command
find / -WNOE -WNOG -type d -print. Creation of these files can take
a long time. The OSSTREE file is created in the volume and subvolume from
which the OSSSETUP utility is run. The pathname of the OSS copy of the file
contains the name of the local system node and the timestamp from when the
file was created.
Utility File Security
Once installed, the utility files should be properly secured for execution only by site-selected user
IDs. Because they are TACL macros, the READ permission (not the EXECUTE permission) must be
secured to control execution. For example, NN-N does not prevent execution by any user; however,
---- does restrict execution to the super ID. Commonly, STARTOSS and STOPOSS are secured
G--- for use by the super group.
Interactive Dialogs
During interactive execution, the OSSSETUP or OSSREMOV utility prompts the user for needed
configuration data or permission to proceed. Prompts have the form of:
prompt_message [default_response]
prompt_message
is a detailed description of the processing step about to be taken or the information needed
to take the step.
EasySetup Utilities 399