SQL/MX 2.x Reference Manual (H06.04+)

SQL/MX Statements
HP NonStop SQL/MX Reference Manual—540440-003
2-170
Considerations for REVOKE EXECUTE
•
SYSTEM specifies the implicit grantor of privileges to the creators of stored
procedures.
You cannot specify SYSTEM as an authid in a REVOKE EXECUTE statement.
If you specify RESTRICT, the REVOKE operation fails if there are privilege
descriptors that would no longer be valid after the EXECUTE privilege is removed.
If you specify CASCADE, any such dependent privilege descriptors are removed
as part of the REVOKE EXECUTE operation. The default is RESTRICT.
BY authid-grantor
specifies the authorization ID authid-grantor on whose behalf the revoke
operation is performed. The EXECUTE privilege being revoked must have been
previously granted by authid-grantor. Only the super ID can use the BY
clause. If another user attempts to do so, the system returns an error. The effect of
using the BY clause is the same as if the authid-grantor were to issue the
REVOKE EXECUTE statement directly (without using the BY clause).
authid-grantor must be a valid authorization ID and cannot be SYSTEM.
Considerations for REVOKE EXECUTE
Authorization and Availability Requirements
You can revoke EXECUTE privilege only if you have previously granted it to the user. If
the privilege does not exist, the system returns a warning.
To revoke privileges by using the CASCADE option, you must own the stored
procedure or be the super ID.
If the super ID has issued a REVOKE EXECUTE using the BY authid-grantor
clause, the authid-grantor must have previously granted the EXECUTE privilege
to the specified authorization IDs.
You cannot revoke privileges from a user of the system if you have granted privileges
to PUBLIC.