HSMS distinguishes between three classes of users for the utilization and control of its functions: nonprivileged users, HSMS administrators and subsystem administrators. In this manual, the user classes to which the individual functions are available are indicated where appropriate.
Nonprivileged users (“STANDARD PROCESSING” privilege)
Nonprivileged users may back up files and job variables of which they are the owner or co-owner in the following archives:
a public system archive (to which ACCESS=*WRITE applies)
their own archive
a public archive belonging to another user if the data which is to be backed up belongs to another user.
another user’s archive, of which the user is a co-owner of the corresponding archive directory. This archive does not have to be public.
Nonprivileged users may archive files and job variables of which they are the owner or co-owner. They may archive these files in a system archive or in a user archive, provided they are authorized to access this archive.
Nonprivileged users may also migrate files of which they are the owner or co-owner to a public system archive. They are also permitted to transfer files and job variables of which they are the owner or co-owner.
Finally, nonprivileged users may also set up their own archives, which can be private or public.
HSMS administrator (“HSMS-ADMINISTRATION” privilege)
The HSMS administrator is authorized to make unrestricted use of all functions and features offered by HSMS. The HSMS administrator works under a user ID to which the “HSMS administration” privilege has been assigned. By default, these are the user IDs SYSHSMS and TSOS.
The HSMS administrator is responsible for system backups, i.e. system-wide backups of the data of all users. Once HSMS has been invoked, the HSMS administrator has access to the files of all users on all pubsets. He or she is also responsible for managing the storage hierarchy and creating the default system archives for the basic HSMS functions as well as for controlling tape access operations for HSMS.
In addition, the HSMS administrator is responsible for setting up shadow archives. Shadow archives are used to administer the copies of save files which are automatically created on magnetic tape cartridges for backups and archivals.
Subsystem administrator (“SUBSYSTEM-MANAGEMENT” privilege)
The subsystem administrator is authorized to start and terminate HSMS.