Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

ARCHIVE functions in HSMS

&pagelevel(3)&pagelevel

HSMS is based on the software product ARCHIVE. HSMS offers the functions supplied by ARCHIVE, but via a more modern user interface and with additional control features.

HSMS makes a clear distinction between the two functions backup and archival, which are not differentiated under ARCHIVE. HSMS offers separate statements for the individual functions as well as separate management of the corresponding data.

Most ARCHIVE functions are also supported by HSMS. But since the HSMS user interface is different, the same functions must be invoked by means of different statements under HSMS. The following table is designed to help users who are familiar with the software product ARCHIVE by giving a few examples of how to map ARCHIVE statements and operands onto their HSMS equivalents.

The second table maps the operands of the ARCHIVE statement PARAM and appropriate operands of HSMS statements.

ARCHIVE continues to be available to all HSMS users.

The following functions are only possible with HSMS:

  • all actions affecting migration and node files

  • updating of backups (Several-SVID format)

  • version backups
  • some additional functions such as the restoration of library elements (made possible by saving the metainformation of PLAM libraries) or all functions linked to archive atributes

  • via the "select only files on Net-Storage" or "exclude files on Net-Storage" operand (control possible only via the parameter file for the entire ARCHIVE session, see “Saving Net-Storage files” in section "Restrictions due to new functions").


Device reservation in HSMS

HSMS reserves the tape devices required for the run itself. Tape devices that are reserved by a user in their own task prior to an HSMS run, are not available to HSMS.

Table of ARCHIVE and HSMS statements

ARCHIVE statement

HSMS statement

DELETE

DELETE-REQUESTS

EXPORT

EXPORT-FILES

,DIRSAVE=*YES

,DIRECTORY-NAME=<filename> –
    (SAVE-DIRECTORY=*YES)

IMPORT

IMPORT-FILES

FILES

SELECT-FILE-NAMES statement and FILE-NAMES operand
    (SELECT-FILES operand of COPY-SAVE-FILE)

,FROM=*PRDISC

BACKUP-FILES SUPPORT=*PRIVATE-DISK
    (VOLUMES=*ALL)

,FROM=*PRTAPE

BACKUP-FILES SUPPORT=*TAPE

INQUIRE

SHOW-ARCHIVE

JOBVAR

SELECT-JV-NAMES and operand JV-NAMES
(SELECT-JV operand of COPY-SAVE-FILE)

LIST

LIST-VOLUMES

POOL

MODIFY-ARCHIVE VOLUMES=*ADD/*REMOVE

PURGE

MODIFY-ARCHIVE SAVE-FILES=*DELETE

PROCESS

RESTART-REQUESTS

RESTORE

RESTORE-FILES

,FROM=*LATEST

,SELECT-SAVE-VERSIONS=*ALL

,FROM=*LATEST,*STATE

,SELECT-SAVE-VERSIONS=*LATEST

SAVE

ARCHIVE-FILES, BACKUP-FILES

,CHANGED=*NO

BACKUP-FILES SELECT-FILES=*ALL-FILES

,CHANGED=*YES,*LARGE

BACKUP-FILES SELECT-FILES=*MODIFIED-FILES
    (PARTIAL-FILE-SAVE=*LARGE-FILES)

,DIRSAVE=*YES

BACKUP-FILES SAVE-OPTIONS=*PAR
    (SAVE-DIRECTORY=*YES)

,DRIVES=

BACKUP-FILES OPERATION-CONTROL
    (PARALLEL-RUNS= )

STATUS

SHOW-REQUESTS

Table 6: Mapping ARCHIVE statements onto HSMS statements

PARAM operand of ARCHIVE statement

HSMS operand

CNS=*YES/*NO

REPORT=*FULL/*SUMMARY

RESTART=*YES/*NO

WRITE-CHECKPOINTS=*YES/*NO

UNLOAD=*YES/*NO

UNLOAD-TAPE=*YES/*NO

OPERATOR=*YES/*NO

OPERATOR-INTERACTION=*YES/*NO

WRCHK=*YES/*NO

WRITE-CHECK=*YES/*NO

SNR=*YES/*NO

REPORT=*FULL/*RESTORED-FILES

DESTROY=*YES/*NO

DESTROY-BY-DELETE=*YES/*NO

CATID=*YES/*NO

CATALOG-ID-MODE=*YES/*NO (only for export/import, otherwise HSMS works only with catalog ID)

OLS=*YES/*NO

SAVE-OPTIONS=*PAR (SAVE-ONLINE-FILES=*YES/*NO) operand of BACKUP-FILES

Table 7: Mapping PARAM operands onto HSMS operands