OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-13
SCF Command Interface
The File Utility Program (FUP) lets you secure files, including the code files for
subsystem processes, to restrict unauthorized access to those files. The authority to
read, write, execute, or purge a file can be restricted to one user or to the members of
a user group and can be further constrained to permit access only from the local
system.
Safeguard is a security subsystem that lets you secure not only files, but also running
processes and devices. You define access lists to assign authority to any set of users.
You can also specify a date and time when a user’s access to the system will
automatically expire. Safeguard logs attempts by unauthorized users to log onto the
system or use objects for which privileges have not been granted.
The user interfaces, such as SCF and the management programmatic interface,
provide security at the command level. Informational commands are generally
available to all users; these commands are called nonsensitive commands. Commands
that affect the state or configuration of an object require a higher level of security;
these commands are called sensitive commands. Some sensitive commands, such as
ADD APPL, are restricted to the super ID or to the owner of the OSI/MHS subsystem.
Sensitive and nonsensitive commands are described in Nonsensitive Commands on
page 2-15 and Sensitive Commands on page 2-16.
SCF Command Interface
This subsection describes SCF, the DSM-based command interface to OSI/MHS and
other subsystems.
You use the SCF commands to configure and alter the components (called objects) of
the subsystem and to monitor and evaluate their performance.
Generally, SCF commands interact with DSM objects in the ways described in the
Subsystem Control Facility (SCF) Reference Manual. However, individual subsystems
define the specifics of command-object interactions, such as what the particular
commands do and what the object types mean. The interactions described in this
manual are specific to OSI/MHS. For detailed information about SCF for OSI/MHS,
see the OSI/MHS SCF Reference Manual.
Generic SCF commands that are not described here still work for OSI/MHS. If the
OSI/MHS SCF Reference Manual states that a command applies to an object type that
is defined in OSI/MHS, and if the command-object interaction is not described in this
manual, then you can rely on the reference manual.
This subsection describes the following topics:
•
SCF command format
•
Using SCF to manage your OSI/MHS subsystem
•
Considerations for managing your subsystem
•
OSI/MHS objects and the SCF commands that apply to them