Safeguard Reference Manual (G06.29+, H06.08+, J06.03+)

Table Of Contents
Disk-File Security Commands
Safeguard Reference Manual 520618-030
8 - 14
ADD DISKFILE Command
You can use the LIKE disk-file-name clause to define all the disk-file attribute
values for a disk file, and then change one or more of the attribute values by
specifying new values after the LIKE keyword. For example, this command adds
an authorization record for MEMO1 that has the same disk-file attribute values as
MEMO2 except for the OWNER attribute:
=ADD DISKFILE memo1, LIKE memo2, OWNER sales.kidd
Using the LIKE clause with an ADD DISKFILE command does not change any of
the current default disk-file attribute values.
Securing partitioned files
To secure a partitioned disk file completely, add a separate disk-file authorization
record for each partition. Adding an authorization record for only the primary
partition protects the partitioned file from any accesses made by opening the
primary partition but does not prevent the secondary partitions from being opened
individually.
Renaming a file with persistent protection
If you rename a file that has persistent protection, the persistent protection is lost
because it remains associated with the source file name. However, if the target file
name in a rename operation has persistent protection, the new file assumes that
protection record.
CREATE authority is meaningless without persistent protection.
CREATE authority for a disk file has no meaning unless the PERSISTENT attribute
is ON for that file.
The OWNER attribute and persistent protection
When a file with persistent protection is created, the OWNER attribute is not
changed to match the user ID of the user who creates the file. The OWNER
attribute remains set to the owner of the file’s protection record.
Persistent protection takes precedence over default protection.
When a file with persistent protection is created, the persistent protection t
akes
precedence over any default protection specified for the user who creates the file.
The PROGID, LICENSE, and CLEARONPURGE attributes in the persistent
protection records.
When a file with persistent protection is purged, the PROGID, LICENSE, and
CLEARONPURGE attributes are set to OFF.
If disk-file persistence is enabled, the ADD DISKFILE command accepts disk-file
protection records for non-existent files.
Licensed program object file requires local super ID.