This information provides you with several different methods to save your system data and related user data. These methods include the GO SAVE command and manual save commands and APIs.
The easiest way to save all of your user data and system data is with menu option 21 of the GO SAVE command. This saves all of your system data as well as the related user data.
The following commands enable you to manually save your system and user data:
v SAV (Save Object in the integrated file system or in directories) v SAVCFG (Save Configuration)
v SAVDLO (Save Document Library Object)
|
v SAVLIB (Save Library)
v SAVLICPGM (Save Licensed Programs) v SAVSECDTA (Save Security Data) v SAVSYS (Save System)
The following links provide you with detailed information about various save commands and save APIs:
v QSRSave API v QSRSAVO API v SAV command v SAVCFG command v SAVCHGOBJ command v SAVDLO command v SAVLIB command v SAVOBJ command v SAVSAVFDTA command v SAVSECDTA command v SAVSYS command v SAVLICPGM command
The following information explains the various methods that you can use to save your system data and related user data:
Methods for saving security data:
Use any of these methods for saving security data.
Table 17. 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
Note:
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.
Important:For procedures where the system does not require a restricted state, you must 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 about how to back up the authority data for your users and objects.
Related concepts:
“Save-while-active function” on page 106
The save-while-active function allows you to use your system during all or part of the save process, that is, save your system while it is active.
Related tasks:
“GO SAVE: Option 21 (saving the entire system)” on page 29
Option 21 saves everything on your system and allows you to perform the save while you are not there.
“GO SAVE: Option 22 (saving system data)” on page 30
Option 22 saves only your system data. It does not save any user data. Option 22 puts your system into a restricted state. This means that no users can access your system, and the backup is the only thing that is running on your system.
“GO SAVE: Option 23 (saving user data)” on page 31
Option 23 saves all user data. This information includes files, records, and other data that your users supply into your system.
Related reference:
“Saving security data” on page 56
This information describes the commands that save user profiles, private authorities, authorization lists, and authority holders.
“QSRSAVO API” on page 67
You can use the Save Objects List (QSRSAVO) application programming interface (API) to save multiple objects.
Related information:
SAVSYS SAVSECDTA
Methods for saving configuration objects in QSYS:
Use any of these methods for saving configuration objects in QSYS.
Table 18. Configuration objects in QSYS information
Item description When changes occur Contains user data or changes?
IBM-supplied data?
Configuration objects in QSYS
Configuration objects in QSYS change regularly. This happens when you add or change configuration information with commands or with the Hardware Service Manager function. These objects might also change when you update licensed programs.
Yes No
Common save method for configuration objects in QSYS Requires restricted state?
SAVSYS Yes
SAVCFG No1
GO SAVE command, menu option 21 Yes
GO SAVE command, menu option 22 Yes
GO SAVE command, menu option 23 No2
1 Important:For procedures where the system does not require a restricted state, you must 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.
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.
Save configuration information contains information about how to save your configuration objects.
Related concepts:
“Save-while-active function” on page 106
The save-while-active function allows you to use your system during all or part of the save process, that is, save your system while it is active.
Related tasks:
“GO SAVE: Option 21 (saving the entire system)” on page 29
Option 21 saves everything on your system and allows you to perform the save while you are not there.
“GO SAVE: Option 22 (saving system data)” on page 30
Option 22 saves only your system data. It does not save any user data. Option 22 puts your system into a restricted state. This means that no users can access your system, and the backup is the only thing that is running on your system.
“GO SAVE: Option 23 (saving user data)” on page 31
Option 23 saves all user data. This information includes files, records, and other data that your users supply into your system.
Related reference:
“Saving configuration information” on page 57
This information describes when to use the SAVCFG command and the SAVSYS command and what object types are saved.
Related information:
SAVSYS SAVCFG
Methods for saving IBM i optional libraries (QHLPSYS, QUSRTOOL):
Use any of these methods for saving IBM i optional libraries.
Table 19. IBM i optional libraries (QHLPSYS, QUSRTOOL) information
Item description When changes occur Contains user data or changes?
IBM-supplied data?
IBM i optional libraries (QHLPSYS, QUSRTOOL)
IBM i optional libraries (QHLPSYS, QUSRTOOL) change when you apply Program Temporary Fixes (PTFs) or when you install new releases of the operating system.
No1 Yes
Common save method Requires restricted state?
SAVLIB*NONSYS Yes
SAVLIB *IBM No2, 3
SAVLIB library-name No3
GO SAVE command, menu option 21 Yes
GO SAVE command, menu option 22 Yes
1 You should avoid changing objects or storing user data in these IBM-supplied libraries or folders.
You could lose or destroy these changes when you install a new release of the operating system.
If you make changes to objects in these libraries, note them carefully in a log for future reference.
2 You do not need to put your system into a restricted state, but it is recommended.
3 Important:For procedures where the system does not require a restricted state, you must 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.
Save libraries with the SAVLIB command explains how to save one or more libraries. This information also includes special SAVLIB parameters and how to select libraries on your system.
Related concepts:
“Save-while-active function” on page 106
The save-while-active function allows you to use your system during all or part of the save process, that is, save your system while it is active.
Related tasks:
“GO SAVE: Option 21 (saving the entire system)” on page 29
Option 21 saves everything on your system and allows you to perform the save while you are not there.
“GO SAVE: Option 22 (saving system data)” on page 30
Option 22 saves only your system data. It does not save any user data. Option 22 puts your system into a restricted state. This means that no users can access your system, and the backup is the only thing that is running on your system.
Related reference:
“Saving libraries with the SAVLIB command” on page 50
Save one or more libraries. You can use this information to save your IBM i optional libraries. This information also includes special SAVLIB parameters and how to select libraries on your system.
Related information:
SAVLIB
Methods for saving licensed program libraries (QRPG, QCBL, Qxxxx):
Use any of these methods for saving licensed program libraries.
Table 20. Licensed program libraries (QRPG, QCBL, Qxxxx) information
Item description When changes occur Contains user data or changes?
IBM-supplied data?
Licensed program libraries (QRPG, QCBL, Qxxxx)
When you update licensed programs
No1 Yes
Common save method for licensed program libraries (QRPG, QCBL,
Qxxxx) Requires restricted state?
SAVLIB *NONSYS Yes
SAVLIB *IBM No2, 3
SAVLICPGM No3
GO SAVE command, menu option 21 Yes
GO SAVE command, menu option 22 Yes
1 You should avoid changing objects or storing user data in these IBM-supplied libraries or folders.
You could lose or destroy these changes when you install a new release of the operating system.
If you make changes to objects in these libraries, note them carefully in a log for future reference.
2 You do not need to put your system into a restricted state, but it is recommended.
3 Important:For procedures where the system does not require a restricted state, you must 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.
Related information:
SAVLIB