Interpretation of wildcards
Shared pubsets are handled like exclusively imported pubsets, irrespective of the master/slave mode.
Processing HSMS requests
All HSMS statements referencing shared pubsets are processed on the host where the HSMS statements were entered.
Recommendations concerning HSMS support for a shared pubset
For each shared pubset, the HSMS administrator should create a separate system archive for backup, version backup, archival, and migration.
The backup system archive of a shared pubset should be created with the same name and the same archive directory on all the sharers of the pubset. The other archive operands can differ from each other.
The same applies to the system archives for archival, version backup and migration.The backup system archive of this pubset can be assigned either the same or different operands for TAPE-CONTROL on all the sharers of a shared pubset. Please bear in mind one exception, however: the tape session intervals of the pubset sharers may not overlap.
The same applies to the system archives for archival, version backup and migration, as well as to private backup and archival archives whose directories are shared by two or more pubset sharers.In shared pubsets, the archive directory of the system archive for backup, version backup, archival and migration should reside on the pubset.
The S1 pubset assigned to a shared S0 pubset must be the same for all sharers of the S0 pubset and be shareable.
The tape pool assigned to a shared pubset’s system archive for backup, version backup, archival and migration must be accessible for all the sharers of the pubset (via MAREN).
For HSMS processing, all the sharers of a shared pubset must have access to a sufficient number of tape devices.
Restrictions and drawbacks
If tape sessions overlap, it must be ensured that different sharers do not work with the same archive directory at the same time.
Processing the metadata of the pubset requires extensive communication between the slave and the master.
Advantages of local mode
Local mode is not subject to the restrictions and drawbacks of master mode.
If a master crashes while processing an HSMS statement, processing of the statement is resumed automatically following a change of master.