Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Transferring files

&pagelevel(4)&pagelevel

If files are to be processed in another data center, they can be written to tape, MT cartridge or disk in the first BS2000 system or under the first user ID with an EXPORT run.

The save volumes are then moved to or made available on the second BS2000 system and the files and/or job variables are read in by ARCHIVE with the IMPORT statement. The catalog entries are also constructed in the TSOSCAT catalog.

With ARCHIVE it is also possible to read files or job variables into the new system under another user ID (SHARE=YES operand for saving, RENAME operand for exporting or importing; RENAME is not permitted for exporting with a directory).

ARCHIVE also supports parallel processing if several files and job variables are to be transferred.

The transfer function does not require a directory file. However, it is possible to execute EXPORT/IMPORT runs with a directory file.
If this directory file is the last file to be written to the save volume (using the DIRSAVE=YES operand) and is the first to be imported to the second BS2000 system with DIRECTORY=NONE, then a table of contents of the files to be imported is made available in the second system. The directory file can then be used to enable the remaining files to be read into the system. This is generally only advisable when you have extensive save files on a number of volumes, which can be processed in parallel runs (DRIVES operand).