Figure 17: System environment for BPRIVACY
The BPRIVACY utility routine must be called in the identification under which the database is cataloged.
You can start BPRIVACY at any point after the BFORMAT routine has executed. It is thus possible to grant new groups access to an existing database application and to change the access rights of existing user groups any number of times.
After changes have been made to a schema (e.g. after new record types or new base tables have been introduced), you must update the access rights with BPRIVACY.
In the case of CODASYL access, BPRIVACY can run in the creation phase of a UDS/SQL database before the subschemas are compiled.
In the case of SQL access, you can start BPRIVACY after compilation and entry of the relational schema (UDS/SQL subschema) in the database.
When required, BPRIVACY automatically extends the DBDIR of the database being processed or the DBTTs of the record types in the DBDIR. For details, please refer to the "Database Operation" manual, Automatic realm extension by means of utility routines.
At startup BPRIVACY takes into account any assigned UDS/SQL pubset declaration (see the "Database Operation" manual, Pubset declaration job variable). Faulty assignment leads to the program aborting.
The BPRIVACY utility routine uses the linked-in DBH during execution.