If you revoke SYSADM authority from an ID that has installation SYSADM authority, you can
avoid certain side effects.
About this task
When you revoke SYSADM authority from an ID that does not have installation SYSADM authority, the
following actions occur:
- The REVOKE statement drops dependent views and materialized query tables for which SYSADM
authority was used to create those views or materialized query tables.
- If SYSADM authority was used to create a package, that package is invalidated when SYSADM
authority is revoked.
Procedure
To avoid dropping dependent views or materialized query tables, or invalidating
dependent packages when you revoke SYSADM authority from an ID, follow this procedure.
-
Determine which IDs currently hold installation SYSADM authority.
Those IDs are the values of the SYSADM and SYSADM2 subsystem parameters. During this
procedure, you will temporarily replace one of those values.
-
Give installation SYSADM authority to the ID from which you want to revoke SYSADM authority. To
do that:
-
Run the installation CLIST in UPDATE mode. In PROTECTION PANEL 2, replace the value of field
SYSTEM ADMIN 1 (subsystem parameter SYSADM) or SYSTEM ADMIN 2 (subsystem parameter SYSADM2) with the
name of the authorization ID from which you want to revoke SYSADM authority.
-
After the installation CLIST completes, run job DSNTIJUZ to produce a new subsystem parameter
load module.
-
Issue the -SET SYSPARM command to load the subsystem parameter load module
that you created in step 2.b
Updating SYSADM or SYSADM2 requires installation SYSADM authority or SECADM authority. For
example, if you are replacing the SYSADM subsystem parameter value, you need to run the
-SET SYSPARM command using the authorization ID to which subsystem parameter
SYSADM2 is set.
-
Issue the REVOKE statement to revoke SYSADM authority from the ID to which you assigned
installation SYSADM authority in step 2.
-
Change the value of subsystem parameter SYSADM or SYSADM2 back to the value that it had in step
1.