Safeguard Reference Manual (G06.24+, H06.03+ )

Disk-File Security Commands
Safeguard Reference Manual—520618-013
8-27
ALTER DISKFILE Command
The following list of command pairs shows the equivalent SAFECOM commands to
use for the disabled FUP commands:
FUP GIVE filename-list , group-num,member-num
ALTER DISKFILE filename-list , OWNER owner-id
FUP SECURE filename-list , PROGID
ALTER DISKFILE filename-list , PROGID ON
FUP REVOKE filename-list , PROGID
ALTER DISKFILE filename-list , PROGID OFF
FUP SECURE filename-list , CLEARONPURGE
ALTER DISKFILE filename-list , CLEARONPURGE ON
FUP REVOKE filename-list , CLEARONPURGE
ALTER DISKFILE filename-list , CLEARONPURGE OFF
FUP LICENSE filename-list
ALTER DISKFILE filename-list , LICENSE ON
FUP REVOKE filename-list
ALTER DISKFILE filename-list , LICENSE OFF
The following two commands perform similar functions but are not strictly
equivalent:
FUP SECURE filename-list , "security-string"
ALTER DISKFILE filename-list , ACCESS access-spec
[ ; access-spec ] ...
An access-spec can include or deny specific users or groups of users to which
the owner does not belong. A security-string does not have this flexibility.
•
Altering a disk file that is currently open
Using ALTER DISKFILE to change one or more attributes for a disk file has no
effect on any users currently accessing the disk file. (That is, changing file security
attributes has no effect on processes that currently have the disk file open.)
For example, if you change a disk-file ACL to deny Read access to a user who is
running a process that is currently accessing the file, the process can continue
accessing the file until it closes the file. However, when the process attempts to
reopen the file for Read access, the Safeguard software returns a security violation
(file error 48).
Examples
1. The owner of the file $DATA.KEEP.INFO adds three ACL entries and changes
another entry:
=ALTER DISKFILE $data.keep.info, ACCESS 86,8 (r,w,e) ; &
=86,10 (r,w,e); prs.darlene DENY (w,e,p) ; 86,* - e