Open System Services Management and Operations Guide (G06.25+, H06.03+)

OSS Management Utilities
Open System Services Management and Operations Guide—527191-002
C-8
Utility File Security
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.
default_response
is the action taken or the value used if the user presses Return.
After you start a utility, you cannot back up within its dialog and choose alternate
responses to prompts. Only the OSSSETUP utility provides help as a TACL command
line option.
OSSTREE file
and
/tmp/oss.tree.
ddmmmyyyy.system_name 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 OSSSETUP utility
and contain the result of the following OSS shell
command:
find / -WNOE -WNOG -type d -print
ddmmmyyyy.system_name file
(continued)
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.
Table C-1. The EasySetup Utilities (page 2 of 2)
Component Description