| Maximum number of related objects that can be saved in a single save
operation1 |
Approximately 111 000 |
 Maximum number of related objects that can be restored
in a single restore operation 1 |
Approximately 104 000 |
| Maximum number of names in a save or restore command specifying which
objects or libraries to include or exclude in the save or restore operation2 |
300 |
| Maximum number of concurrent save or restore operations |
Limited only by available machine resources |
| Maximum size of an object that can be saved |
Approximately 2 terabytes |
| Maximum size of a save file |
Approximately 1 terabyte |
Note:
- All database file objects in a library that are related to
each other by dependent logical files are considered to be related objects.
Starting in V5R4, all database files in a library that have referential constraints
are considered to be related objects when using the save-while-active function.
A
database file object consists of one or more internal objects. A maximum of
approximately 500 000 related internal objects can be saved in a single
save operation. One internal object is saved for each database file object,
along with the following additional internal objects: - If the physical file is not keyed, add 1 internal object per member.
- If the physical file is keyed, add 2 internal objects per member.
- If the physical file has unique or referential constraints, add 1 internal
object per constraint.
- If the physical file has triggers, add 1 internal object for the file.
- If the physical or logical file has column level authorities, add 1 internal
object for the file.
- If you use ACCPTH(*YES) on the save command, add 1 internal object for
each logical file in the save request.
- Using generic names to specify groups of objects or libraries
can help avoid this limit. For the LIB, OMITLIB and OMITOBJ parameters on
save commands, you can use the Command User Space (CMDUSRSPC) parameter to
raise the limit to 32 767 simple or generic names.
|