The owner of an archive has various possibilities of controlling access to the archive. By default an archive is not created as shareable, in other words only the owner of an archive may use it to back up data; it is a private archive.
All users have the right to create an archive that may be used by other users besides the owner for the basic function defined. This is considered to be a public archive:
//CREATE-ARCHIVE USER-ACCESS=*ALL-USERS
Public backup archives belonging to nonprivileged users can, however, only be used by other users within the context of co-ownership. A public backup archive is available to all users only if the archive’s owner ID is SYSHSMS (see section "Default system archives"). However, long-term archives are not affected by this restriction.
Public archives from which users are to be able to restore the data belonging to their user ID must be set up with ACCESS=*READ. If users are to be able to back up their files in a public archive, the archive must be set up with ACCESS=*WRITE.
Co-ownership of an archive is defined via the co-ownership of the corresponding directory file. All co-owners can use this archive as their own, however, they cannot change the archive properties, share save files or change their RETPD. Co-ownership access is irrespective of the archive’s specified access attributes.
Whether or not an archive is shareable within HSMS is independent of the file attributes of its directory and is determined exclusively by the entry in the HSMS control file – with the exception of co-ownership (see above). It is determined exclusively by the entry in the HSMS control file – with the exception of co-ownership (see above). Its ability to be shared cannot be changed by means of BS2000 commands.
The access authorization for a shadow archive includes only the explicit copying of save files from the long-term or backup archive into the associated shadow archive and vice versa, and the restoration of data from the shadow archive. The authorization for automatic duplication to a shadow archive depends entirely on the access authorization of the associated long-term or backup archive.
If a nonprivileged user performs an archival to a public archive to which a shadow archive is assigned, the data is automatically duplicated in the shadow archive, even if the shadow archive is private (ACCESS=*OWNER-ONLY).
The following overview clarifies the access to foreign archives, which comprise co-ownership (in conjunction with SECOS).
To enable access, it is required that each target archive is installed correspondingly (with USER-ACCESS=*ALL-USERS and ACCESS=*WRITE or the archive/directory’s co-ownership). In order to backup own files into other archives, you have to be co-owner of the respective archive directory, unless the backup archive is created under the SYSHSMS ID.
Backup by user A: | in archive of | in archive of | in SYSBACKUP |
Own file under user ID A | yes | yes | no |
File under user ID B for which user A is a co-owner | yes | yes | no |
Shared file under user ID B (no co-ownership) | no | no | no |
yes: | access permitted |
no: | access not permitted |
Long-term archival by user A: | in archive of | in archive of | in SYSARCHIVE |
Own file under user ID A | yes | yes | yes |
File under user ID B for which user A is a co-owner | yes | yes | yes |
Shared file under user ID B (no co-ownership) | no | no | no |
yes: | access permitted |
no: | access not permitted |
Migration by user A: | in archive of | in archive of | in SYSMIGRATE |
Own file under user ID A | no | no | yes |
File under user ID B for which user A is a co-owner | no | no | yes |
Shared file under user ID B (no co-ownership) | no | no | no |
yes: | access permitted |
no: | access not permitted |
Version backup by user A: | in archive of user ID A | in archive of user ID B | in SYSVERSION |
Own file under user ID A | no | no | yes |
File under user ID B for which user A is a co-owner | no | no | yes |
Shared file under user ID B (no co-ownership) | no | no | no |
yes: | access permitted |
no: | access not permitted |