HP Integrity NonStop J-Series - Manual (Page 37)

Securing Disk Files
Safeguard User’s Guide — 422089-020
3 - 3
Getting Started
Getting Started
You must use SAFECOM, the Safeguard command interpreter, to enter commands. As
described in
Section 7, Working With SAFECOM , you can choose different operating
modes and options when you run SAFECOM.
For simplicity, the examples in this section assume that you are running SAFECOM in
interactive mode. To start SAFECOM in interactive mode, type the following command
at the TACL prompt:
1> SAFECOM
In response to this command, SAFECOM displays its program banner and an equal
sign (=). The equal sign is the SAFECOM command prompt. It indicates SAFECOM is
ready to accept commands.
To end an interactive session, type EXIT at the SAFECOM command prompt.
Adding a Disk File to the Safeguard
Subsystem
You must own a disk file or be owner’s group manager or a super user to secure a disk
file with the Safeguard subsystem. The ADD DISKFILE command puts a file under
PERSISTENT Specifies that the authorization record for a file is to be retained
if the file is purged.
PROGID Applicable only to files that contain object code; sets the
process access ID (PAID) to the user ID of the file's primary
owner.
TRUST Specifies whether or not the file can be trusted to not access I/O
buffers during execution. Applies only to program files. Only the
super ID can set this attribute. This attribute is valid only on
systems running H-series RVUs.
LICENSE Applicable only to files that contain privileged object code;
specifies that nonprivileged users can execute the code.
OBJECT-TEXT-
DESCRIPTION
^^
Allows comments on authorization records to be associated with
objects.
PRIV-LOGON ^ Specifies whether the program file (object disk file) added in
Safeguard protection can request additional logon-related
sensitive features and whether delay should be imposed for
failed authentication attempts.
Table 3-2. Disk-File Attributes (page 2 of 2)
Attribute Function
^ Supported only on systems running H06.11 and later H-series RVUs and G06.32 and later G-series RVUs.
^^ Supported only on systems running J06.05 and later J-series RVUs, H06.16 and later H-series RVUs, and
G06.32 and later G-series RVUs.