Methods for saving security data
There are several methods that you can use for saving security data.
Table 1. Information about security data Item description When changes occur Contains user data or changes? IBM-supplied data? Security data Security data—user profiles, private authorities, and authorization lists—change regularly as you add new users and objects or if you change authorities.
Yes Some
Common save method for security data Requires restricted state? SAVSYS1 Yes SAVSECDTA1 No GO SAVE command, menu option 21 Yes GO SAVE command, menu option 22 Yes GO SAVE command, menu option 23 No2 QSRSAVO API (for saving user profiles) No3
- 1
- SAVSYS and SAVSECDTA do not save authority information for objects in the QNTC file systems. The system saves authority information with the Windows® server objects.
- 2
- When you use option 23 from the GO SAVE command menu, the default is to place your system in a restricted state. If you choose the prompting option, you can cancel the display that puts your system in a restricted state.
For procedures where the system does not require a restricted state, ensure that the system can get the locks necessary to save the information. You should place your system in a restricted state whenever you save multiple libraries, documents, or directories, unless you use the save-while-active function.
- 3
- You must have *SAVSYS special authority to save user profiles with the QSRSAVO API
Save security data contains information on how to back up the authority data for your users and objects.
Parent topic:
Methods for saving system data and related user dataRelated concepts
Saving your system while it is active