The following mechanisms are provided for file protection:
Only archive owners are permitted to use archive administration functions to modify and list archive attributes, delete an archive, or access an archive’s save files and volumes, for example.
Only the HSMS administrator and users working under the appropriate archive owner IDs can administer existing archives.Users’ access rights to archives are determined by the archive definition. A public archive. All users are authorized to set up an archive that can be accessed by other users.
The directory is created under the user ID of the archive owner (non-shareable, unless otherwise specified). If the archive directory is password-protected, this password must be entered before the archive is accessed, even by the HSMS administrator.Unless otherwise specified, HSMS creates save files as non-shareable files (USER-ACCESS=*USER-ONLY) under the user ID of the archive directory. This means that access to the contents of save files without using HSMS is possible only for the archive owner.
If migrated files are to be erased by overwriting them with binary zero when deleted (DESTROY-BY-DELETE), then the storage space released by migrating such files is also cleared in this manner. The same procedure is used for deleting a save file in a migration archive on S1; the save files are created with DESTROY-BY-DELETE.
The protection attributes of a file are not changed by recalling or copying it with the aid of HSMS.
During automatic recall of a migrated file, for example with an OPEN command, DMS checks whether the user is authorized to access the file at all.
All users – whether privileged or not– may use HSMS statements to access the files belonging to other user IDs if this is permitted by the data management system (DMS). All users can use the HSMS statement EXPORT-FILES to export accessible files belonging to other user IDs (with read access).
HSMS does not check whether a user is authorized to access (possibly password-protected) files of his or her own user ID unless the contents of a file are accessed. This applies to deletion under the archival function and to the replacement of files existing in the system when restoration takes place.
Access to files of foreign user IDs
In calls of the HSMS administrator, files and job variables of foreign user IDs are supported in full.
The following restrictions apply for calls of a nonprivileged user:
Foreign files and job variables for which co-ownership exists are supported with the statements BACKUP-FILES, MIGRATE-FILES, COPY-SAVE-FILE, RESTORE-FILES, SELECT-FILE-NAMES and SELECT-JV-NAMES.
The recalling (both implicit and explicit) of foreign, migrated files is permissible if co-ownership exists or the file protection attributes allow access from another user ID.
A special feature here is that, regardless of the access rights of the caller for the individual files, all files and job variables are taken over into the same archive or into the shadow archive when COPY-SAVE-FILE without file selection is used for copying.
When SHOW-ARCHIVE with INFORMATION=*FILES is called, the names of foreign files and job variables are output only if co-ownership exists.
When IMPORT- and EXPORT-FILES or ARCHIVE-FILES are called, all files and job variables are supported for which the caller has a DMS access right.