Methods to save 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?
SAVSYS¹	Yes
SAVSECDTA¹	No
GO SAVE command, menu option 21	Yes
GO SAVE command, menu option 22	Yes
GO SAVE command, menu option 23	No²
QSRSAVO API (for saving user profiles)	No³

Note:

¹: SAVSYS and SAVSECDTA do not save authority information for objects in the QNTC file systems. The server saves authority information with the Windows^® server objects.
²: When you use option 23 from the GO SAVE command menu, the default is to place your server in a restricted state. If you choose the prompting option, you can cancel the display that puts your server in a restricted state.
Important: For procedures where the server does not require a restricted state, you must ensure that the server can get the locks necessary to save the information. You should place your server in a restricted state whenever you save multiple libraries, documents, or directories, unless you use the save-while-active function.
³: 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.