| Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Copy Library (CPYLIB) command copies the contents of a library to a new library. If the new library does not exist, the command optionally creates it before the copy.
All copied objects are created in the same auxiliary storage pool (ASP) as the new library. Any objects that already exist in the new library remain in the new library after the new objects are copied.
Note: If the new library is created by this command:
Use the Display Library Description (DSPLIBD) command to display journal information for the library. Refer to the Start Journal Library (STRJRNLIB) command for more information about journaling a library.
Restrictions:
| Top |
| Keyword | Description | Choices | Notes |
|---|---|---|---|
| FROMLIB | Existing library | Name | Required, Positional 1 |
| TOLIB | New library | Name | Required, Positional 2 |
| CRTLIB | Create library | *YES, *NO | Optional |
| DATA | Duplicate data | *YES, *NO | Optional |
| CST | Duplicate constraints | *YES, *NO | Optional |
| TRG | Duplicate triggers | *YES, *NO | Optional |
| FILEID | Duplicate file identifiers | *NO, *YES | Optional |
| Top |
Specifies the existing library to be copied.
This is a required parameter.
| Top |
Specifies the new library to which objects will be copied from the existing library.
This is a required parameter.
| Top |
Specifies whether the new library should be created.
| Top |
Specifies whether the data records in database physical files or save files in the existing library are copied to the newly-created object in the new library. Members of physical files are copied whether or not the data contained in them is copied. The specified value is not used for objects which are not database physical files or save files.
Note: The relative record numbers in the new file are the same as those in the original file.
| Top |
Specifies whether any constraints associated with database physical files in the existing library are copied to the newly-created files in the new library. The specified value is not used for objects which are not database physical files.
| Top |
Specifies whether any triggers associated with database files in the existing library are copied to the newly-created files in the new library. The specified value is not used for objects which are not database files.
Note: There are special considerations of which to be aware relating to the duplication of triggers. For example, the duplication will differ depending on whether or not the trigger program associated with the existing file was in the same library as the existing file. For additional information, see the Database category in the IBM i Information Center at http://www.ibm.com/systems/i/infocenter/.
| Top |
Specifies whether the file level and member level identifiers for a database file in the existing library will be used for the newly-created file in the new library. The specified value is not used for objects which are not database files.
| Top |
Example 1: Copying the Contents of a Library to a New library After Creating the New Library
CPYLIB FROMLIB(MYLIB) TOLIB(NEWLIB)
This command copies the contents of library MYLIB into library NEWLIB after creating library NEWLIB. The data records, constraints, and triggers associated with a database physical file in library MYLIB will be copied to the database physical file created in library NEWLIB. New file level and member level identifiers will be generated for each database file created in library NEWLIB. This means that the file level and member level identifiers for a database file created in library NEWLIB will not be the same as the file level and member level identifiers for the database file in library MYLIB from which it was copied.
Example 2: Copying the Contents of a Library to an Existing Library
CPYLIB FROMLIB(MYLIBA) TOLIB(MYLIBB) CRTLIB(*NO) +
DATA(*YES) CST(*NO) TRG(*NO) FILEID(*YES)
MONMSG MSGID(CPF2358)
This command copies the contents of library MYLIBA into existing library MYLIBB. All copied objects are created in the same auxiliary storage pool (ASP) as library MYLIBB. Any objects that already exist in library MYLIBB will not be copied from library MYLIBA and those objects will remain in library MYLIBB after other new objects are copied. The data records in a database physical file in library MYLIBA will be copied to the database physical file created in library MYLIBB. The constraints and triggers associated with a database file in library MYLIBA will not be copied to the database file created in library MYLIBB. The file level and member level identifiers for each database file created in library MYLIBB will be the same as the file level and member level identifiers for the database file in library MYLIBA from which it was copied.
The MONMSG command allows you to ignore escape message CPF2358 which may be signalled if all objects in library MYLIBA cannot be copied to library MYLIBB. One reason an object cannot be copied is if the object already exists in library MYLIBB.
| Top |
*ESCAPE Messages
| Top |