When the shared pubset is exported, a processor is disconnected from the shared pubset network.
Exporting a shared pubset
A shared pubset is exported when the EXPORT-PUBSET command is issued on the processor or HIPLEX MSCF is terminated. A distinction is made between a master and slave export, and with a master export an additional distinction is whether or not a master change is to take place.
Slave export
If a slave processor exports a shared pubset, its resources are released to the master processor (including those resources that could not be released during the slave pubset session due to communication problems).
Master export without master change
If the EXPORT-PUBSET command is executed on the master processor without explicitly requesting a master change, the entire shared pubset network is cleared down. The pubset is therefore exported not only from the master processor but from all slave processors as well.
Master export with master change
The EXPORT-PUBSET <catid>,SHARER-TYPE=*MASTER(MASTER-CHANGE=*YES) command executed on the master processor has the following effects:
After the command starts, the DMS management operations are halted on the slave processors.
The shared pubset is exported from the master processor.
When the export procedure has terminated on the master processor, a master change takes place automatically on the slave processors. A new master processor is selected from the set of slave- processors.
After the master change has concluded, the pubset is again available in full on the former slave processors (with new master processor). As far as the applications on the slave processors are concerned, this master change is just as transparent as the master change following a shutdown or failure of the master processor.
An export with master change is initiated automatically when MSCF is terminated on the master processor.
Notes
A master change is only possible if it is permitted (see "Parameters for defining the shared pubset master") and the necessary CCS connections are established.
If EXPORT-PUBSET TERMINATE-JOBS=*YES is specified UTM applications that use the shared pubset receive an end signal when they use the pubset.
The POSIX file systems /root and /var should not be placed on shared pubsets, otherwise POSIX must be terminated manually so that the affected pubsets can be exported outside of a shutdown. This could lead to blocks, especially during automatic fail reconfiguration (RECOVERY-START=*AUTOMATIC / *SECURE), because MSCF cannot be terminated until all shared pubsets have been exported.