Modifying Protection for Files
To modify protection for a file or group of files, enter "1" in the Opt field for those files on the Protect DB Files screen (shown in Protecting Files). The Modify Protection of File screen appears.
Modify Protection of File File . . . . . . . . . . AUSYSID Name Library . . . . . . . . ALEX Name Secured File Description . System id Reaction to UNALLOWED programs Reaction types Ticket Exists Mode Reaction 1=Reject No Int 3 1-9 2=Request Tkt+Pwd No Bch 1 1, 7, 9 3=Request Tkt Yes Int 7 1, 7, 9 5=< Remote permission > Yes Bch 7 1, 7, 9 7=Allow with trace 9=Allow without trace ALLOWED updates By authorized programs . . *REGULAR Named list, *REGULAR - or - *REGULAR=All, except file editors For non-critical fields . Y Y=Specify e.g. description Activate file protection . Y Y=Yes, N=No If not yet active F3=Exit F4=Prompt F12=Cancel |
The Updates are always allowed fields show which programs are allowed to update the file.
The By authorized programs field can contain either:
- the name of a whitelist, as defined on the Work with Program Lists screen (shown in Working with Allowed Program Whitelists), or
- the string "*REGULAR", which indicates that any program that is not in the blacklist defined on the Change File Editors screen (shown in Working with the File Editor Blacklist) may update the file.
To indicate that the file contains non-critical fields (such as many text descriptions) that any program may update, enter "Y" in the For non-critical fields field.
The Reaction to UNALLOWED programs fields show how Safe Update is to react to attempts by programs that are not allowed to edit the files to update them.
The fields show four possible situations. The Ticket Exists field indicates whether a ticket has been issued for the change. The Mode field shows whether the program attempting to update the field is running interactively ("Int") or batch ("Bch").
For each of these possibilities, the Reaction field indicates which of a set of reactions would be used:
- The update is rejected.
- Safe Update requests that the user enter both the ticket number and his system password (which is verified through an IBM API, and does not otherwise expose the password).
- Safe Update requests that the user enter the ticket number.
- (Not used)
- Safe Update requires that the person who submitted the work order confirm the update via the Work with Active Tickets screen.
- (not used)
- The update is allowed. The system traces the work done.
- (Not used)
- The update is allowed without any trace.
The next, unlabeled field shows the possibilities for each combination of the Ticket Exists and Mode fields. For interactive updates without a ticket, any of the options may be chosen. For the other situations (batch updates without a ticket, or either interactive or batch updates with a ticket), it can be set to 1, 7, or 9.
When you have set all the relevant fields, press Enter. If you have set the For non-critical fields value to "Y", the Define Non-Critical Fields screen (shown in Defining Non-Critical Fields) appears. Otherwise, the Protect Physical FIles screen (shown in Protecting Files) reappears.