Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Hanging shared pubset occupation

&pagelevel(3)&pagelevel

When HIPLEX MSCF is terminated, all shared pubsets are always exported. However, it is possible that pubsets are still occupied by the DMS and the export is therefore blocked. For this reason, message DMS039B indicates which pubsets are still occupied on which sharers. Message MCS4122 indicates which pubsets have not yet been exported. Message MCS1006 indicates whether the registered function CPM or XPM is preventing the termination of the XCS reconfiguration.
Systems support can issue the following command to determine the blocking tasks, and can eliminate the cause of the block:

/SHOW-PUBSET-PARAMETERS <catid>,INFORMATION=*PUBSET-OCCUPATION

If EXPORT-PUBSET TERMINATE-JOBS=*YES is specified UTM applications 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 when fail reconfiguration of MSCF (RECOVERY-START=*AUTOMATIC / *SECURE) is started automatically, because MSCF cannot be terminated until all shared pubsets have been exported.