Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Miscellaneous

&pagelevel(5)&pagelevel
  • A report can be requested for each restore run with the LIST operand. This report contains file names, version numbers and file sizes etc. Files which could not be restored are also listed with an identifier to this effect.

  • For restoration on private disk the VTOC area must be sufficiently large to accommodate all the files to be transferred (cf. the F1SIZE specification for VOLIN in the “Utility Routines” manual [1]).
    One PAM page in the VTOC area is required for between 13 and 15 catalog entries.

  • If existing files are to be replaced in a RESTORE run (REPLACE=YES), the user can control via the SPACE operand whether the file is to be

    • deleted before restoration (SPACE=REORG)

    • overwritten in its original physical location (SPACE=KEEP).

    If the file is deleted before restoration, ARCHIVE effectively performs a reorganization of the disk when a disk restore is executed. After the restoration, the files do not occupy the same locations as they did before (see the section “Reorganization of disk storage units” below).

    Overwriting files in their original physical locations is important for files which have to occupy a particular physical location, e.g. the center of the disk for files which are accessed frequently.

  • If a file which does not yet exist is to occupy a specific physical position on the disk, systems support can create it on the desired disk areas with /CREATE-FILE before the RESTORE run. Precisely these disk extents will then be overwritten in a RESTORE run with SPACE=KEEP.

  • Encrypted files (BS2000/OSD as of V6.0) will be transferred without change from disk to the save file, for save as well as for migration. Encrypted files are thus stored on the save file in encrypted form.

    A specification of a crypto-password is not required.
    The run time of requests is not affected by encrypted files.

    In HSMS operation, the save of PLAM information for encrypted PLAM libraries will be rejected.

  • When restoring encrypted files (BS2000/OSD as of V6.0) a crypto-password need not be specified. The run time of requests is not affected by encrypted files.

    For encrypted files, the implicit Key/nonkey conversion from the save file is not possible with restore.