What you should know before running the Restore Authority command

There are some general facts you should be aware of when running the Restore Authority (RSTAUT) command on a system in a nonrestricted state.

This command might take a long time depending on how many private authorities that you have on your system.
During system recovery, you should not start all subsystems and allow all users to sign on and use the system while RSTAUT is being run. The only subsystem that is needed to run RSTAUT in a nonrestricted state is QSYSWRK. Allowing all users access to the system before RSTAUT completes might cause many more objects to be locked, preventing a larger number of the private authorities from being restored.
All private authorities for all authority reference tables that are processed by one prestarted job might not be successfully regranted. If they are regranted, then the message logging level that is used for that prestarted job will be the same as the logging level that is used by the user's main job.
If one or more private authorities for an authority reference table are not successfully regranted, then LOG(*SECLVL) will be used for the message logging for that prestarted job.

For example, you can run the RSTAUT command with the system default logging level of LOG(4 0 *NOLIST). All prestarted jobs that are run by RSTAUT that have all private authorities regranted successfully will use the LOG(4 0 *NOLIST) message logging level. The job log will not remain on the system after the prestarted job completes. All prestarted jobs that are run by RSTAUT, that have one or more private authorities that are not regranted, will instead use the LOG(4 0 *SECLVL) logging level. The job log will remain on the system after the prestarted job completes.
Do not cancel any of the prestarted jobs RSTAUT has started. Doing so will cause the entire RSTAUT command to cancel, similar to cancelling a RSTAUT command on a restricted state system.
One user's authority reference tables are always processed by a single prestarted job.
If the authority reference tables are small, one prestarted job might process more than one user's authorities.

Subsystem QSYSWRK must be started in order for the prestarted jobs to start. The RSTAUT command will start several prestarted jobs at once, and assign the restore of authorities for one or more user profiles to each of the prestarted jobs. During the RSTAUT command, when the prestarted jobs are running, an entry will appear for each prestarted job on the Work with Active Jobs display.

                            Work with Active Jobs                MYSYSTEM
                                                       05/01/97  16:02:05
CPU %:   26.5     Elapsed time:  00:00:31      Active jobs: 94

Type options, press Enter.
  2=Change   3=Hold   4=End   5=Work with   6=Release   7=Display message
  8=Work with spooled files   13=Disconnect ...

Opt  Subsystem/Job  User        Type  CPU %  Function        Status
__   QSYSWRK        QSYS         SBS     .1                   DEQW
__   QSRRATBL       QUSER         PJ    1.2                    RUN
__   QSRRATBL       QUSER         PJ    1.0                    RUN

If subsystem QSYSWRK is active but the prestarted jobs cannot be started for any reason, you should receive messages in your job log, including escape message CPF386D, stating why the prestarted jobs cannot be started.