The existence of an XCS pubset is part of the functionality of the XCS network and can be a prerequisite of the distributed system functions and the XCS applications. The import of the XCS pubset at network entry and export at network exit are implemented automatically by MSCF, as is the master change if the current master leaves the network or fails. Systems support must not import XCS pubsets. Operator intervention is only required in the event of an aborted master change or an input/output error.
When the XCS network is active, additional pubsets can be added to the XCS pubsets already active (i.e. shared pubsets declared as XCS pubsets). On the other hand, XCS pubset can also be removed from the XCS network, provided the last pubset is not removed (the XCS network requires at least one XCS pubset).
To add an XCS pubset to the network, the pubset must first be imported as a shared pubset on all processors in the XCS network and then declared an XCS pubset via the SET-XCS-PUBSET command. The SET-XCS-PUBSET definition only applies for the duration of the active XCS session.
If an XCS pubset is to be removed from the network, the pubset must be exported from the current master processor of the pubset.
In the event of write errors in the disk protocol of an XCS pubset, the pubset can be exported from the respective processor (e.g. to perform hardware repairs). During the period when no XCS pubset is available or an XCS pubset is not imported on every processor in the network, a join reconfiguration is not possible. The faulty XCS pubset should be exported from all processors connected in the network. If this was the last XCS pubset of the network, a new XCS pubset should be added to the network as soon as possible.