Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Action statements, requests and HSMS server tasks

&pagelevel(4)&pagelevel

A number of HSMS statements result in I/O operations on user files and save files and these are executed in an HSMS subtask (not in the calling task) and require some action on the part of the software product ARCHIVE. These HSMS statements are referred to as action statements:

ARCHIVE-FILES (ARF)

Archive files

ARCHIVE-NODE-FILES (ANF)

Archive node files

BACKUP-FILES (BCF)

Save files and job variables

BACKUP-FILE-VERSIONS (BFV)

Save files

BACKUP-NODE-FILES (BNF)

Save node files

COPY-EXPORT-SAVE-FILE (CES)

Copy save file

COPY-NODE-SAVE-FILE (CNF)

Copy node save files

COPY-SAVE-FILE (CSF)

Copying save files

EXPORT-FILES (EXF)

Export files and job variables

IMPORT-FILES (IMF)

Import files and job variables

MIGRATE-FILES (MGF)

Migrate files

MOVE-SAVE-FILES (MSF)

Move save file

RECALL-MIGRATED-FILES (RMF)

Retrieve files

REORGANIZE-VERSION-BACKUP (RVB)Reorganization of version backup archives

REPAIR-CATALOG-BY-RESTORE (RCR)

Repair inconsistencies in migrated files using RESTORE

REPLACE-SAVE-FILE-BY-RESTORE (RFR)

Replace save file in migration archive using RESTORE

RESTORE-FILES (RSF)

Restore files and job variables

RESTORE-LIBRARY-ELEMENTS (RLE)

Restore elements of a library file

RESTORE-NODE-FILES (RNF)

Restore node files

UPDATE-EXPORT-SAVE-FILE (UES)

Update backup

Each action statement includes an OPERATION-CONTROL operand which serves to control the processing of the requests.

HSMS generates a request for each I/O operation initiated by any of these action statements. The requests are processed by user tasks specifically designed for this purpose, the HSMS server tasks. With the exception of the data transfer function, the HSMS server tasks are given the job name “HSMSSERV” and run under the TSOS user ID; they are present throughout the HSMS session.

These HSMS server tasks call ARCHIVE, which in turn creates ARCHIVE subtasks for processing the inputs/outputs. The ARCHIVE subtasks are given the job name in accordance with the specification in the REQUEST-NAME operand (see section "Operation control").