When working with shared SM pubsets – as opposed to shared SF pubsets – HSMS itself guarantees the coherence of the migration, backup and version backup archive definitions on all sharers, i.e. the administrator no longer has to worry about it.
Request management is simpler for shared SM pubsets than for shared SF pubsets because only one request file – namely the local request file of the SM pubset – is involved. Requests can be displayed, restarted and deleted by any sharer. When requests are restarted, the new master sharer is dynamically separated for each restart. The master sharer does not have to be called when requests are deleted.
Furthermore, in an SM environment, only one catalog ID is involved so there are no wildcards to be interpreted.