If a privileges list is modified, those privileges that remain unchanged must be repeated in the MODIFY statement.
If a new privilege is assigned to a structure, only the dependent structures defined with PRIVILEGE=*SAME receive the new privilege. This means that after every modify operation, dependent structures having privileges of their own must be altered separately (with EDIT and MODIFY-...).
The same test is run in all MODIFY and ADD statements, in order to prevent a dependent structure having more privileges than the higher-order structures.
If a privilege is canceled in a structure, it is also canceled in those dependent structures that have privileges of their own. This prevents inconsistencies in the syntax tree.The privilege in question is canceled in those dependent structures defined with PRIVILEGE=*SAME.
The last privilege in a dependent structure cannot be canceled. An attempt to cancel the last privilege is rejected with an error message. If this happens, use the REMOVE statement to explicitly remove the structure.If an operand has a default value, the default value must have the same privileges as the operand.
If an operand does not have a default value, it must have the same privileges as its higher-order structure (command or value). For each of the operand’s privileges, there must be at least a value having the same privilege. These two rules ensure that, irrespective of its privileges, each user request can assign a value to the operand.