Safeguard User's Guide (G06.29+, H06.08+, J06.03+)

Securing Disk Files
Safeguard User’s Guide — 422089-020
3 - 5
Controlling Default Attributes
Once again, display the authorization record:
=INFO DISKFILE report1
The display shows:
The file report1 is protected by the Safeguard software with a simple access control list
that consists of only your user ID. To modify or expand the access control list, see
Working With Access Control Lists on page 3-7.
Controlling Default Attributes
When you add a file to the Safeguard database, any unspecified attributes take on the
default attributes for a disk file. As the previous examples showed, when report1 was
initially added to the Safeguard database, it did not have an access control list. This
occurred because the default disk-file attributes do not include an access control list.
To see the default values for disk files:
=SHOW DISKFILE
The display shows:
LAST-MODIFIED OWNER STATUS WARNING-MODE
$DATA.SALES
REPORT1 18JUL05, 11:03 2,1 THAWED OFF
002,001 R,W,E,P, O
Note. If you display the Guardian security string with the FUP INFO command or the TACL
FILEINFO command, the value of the RWEP field appears as four asterisks ("****") for the file
that is placed under Safeguard protection through the ADD DISKFILE command. But if the file
is placed under Safeguard control through the use of a DEFAULT-PROTECTION or
PERSISTENT PROTECTION record FUP INFO and FILEINFO will display Guardian security
string in the RWEP column though the file will be placed under Safeguard protection.
TYPE OWNER WARNING-MODE
DISKFILE 2,1 OFF
OBJECT-TEXT-DESCRIPTION =
AUDIT-ACCESS-PASS = NONE AUDIT-MANAGE-PASS = NONE
AUDIT-ACCESS-FAIL = NONE AUDIT-MANAGE-FAIL = NONE
AUDIT-PRIV-LOGON = OFF
LICENSE = OFF PROGID = OFF CLEARONPURGE = OFF PERSISTENT = OFF
TRUST = OFF
PRIV-LOGON = OFF
NO ACCESS CONTROL LIST DEFINED!
Note. The attributes, AUDIT-PRIV-LOGON and PRIV-LOGON, are supported only on systems
running H06.11 and later H-series RVUs and G06.32 and later G-series RVUs. The OBJECT-
TEXT-DESCRIPTION attribute is supported only on systems running J06.05 and later J-series
RVUs and H06.16 and later H-series RVUs.