Files and job variables are saved to tape, MT cartridge or disk by means of the EXPORT statement. After this they can be transferred to another BS2000 system or another user ID by means of the IMPORT statement. The files and job variables can be renamed with the RENAME operand in the FILES or JOBVAR statement.
With the EXPORT statement you can only save complete files from public disk as well as catalog entries of files on tape or MT cartridge. ARCHIVE save data can be copied in an EXPORT run.
Save runs performed using EXPORT exclude save files (ARCHIVE.SAVE.FILE...) from saving. This also applies to any other files which may have been cataloged under this name.
The EXPORT statement exports cataloged files and job variables regardless of their BACKUP entry (i.e. also those with BACKUP=E).
As of ARCHIVE V2.8A, nonprivileged users may export files and/or job variables which are shareable and readable. Shareable files can only be exported without a directory file. The exported files can subsequently be imported under another user ID. During the export operation, all password and environment attributes of the save file must be reset with the operand ATTRIBUTES=RESET.
ARCHIVE does not support protection of individual elements in the PLAM library. Problems can occur as a result if the library is restored using a different user ID.
If no output volume is specified in the IMPORT statement, all files and job variables are restored on public volume sets. The file attributes with which the files are created are described on "File attribute handling".
If you want to process private volumes in another BS2000 system, ARCHIVE offers the option of saving only the catalog entries of these volumes in the first system by means of the operand CATONLY=YES of the EXPORT statement. In the second system, the catalog entries can be read into TSOSCAT via the IMPORT statement.
For restoration on private disk the VTOC extent must be sufficiently large to accommodate all the files and job variables to be transferred. One PAM page in the VTOC area is required for between 13 and 15 catalog entries.
The replacement of existing files in an IMPORT run (REPLACE=YES) can be controlled via the SPACE operand in the same way as was described for the RESTORE run.