For a frozen instance Source Server shutdown reports whether or not it deleted the Journal Pool ipcs
Final Release Note
MUPIP REPLICATE -SOURCE -SHUTDOWN reports whether or not it deleted the Journal Pool shared memory and semaphores even if the instance is frozen. Previously, it reported this information only if the instance was not frozen. [#364 (closed)]
Description
A source server shutdown command normally produces the following output in case there are other processes still attached to the journal pool.
> mupip replicate -source -shut -time=0
Wed Sep 26 10:48:00 2018 : Forcing immediate shutdown
Wed Sep 26 10:48:00 2018 : Initiating SHUTDOWN operation on source server pid [3170] for secondary instance [INSTB]
Wed Sep 26 10:48:00 2018 : Waiting for upto [120] seconds for the source server to shutdown
Wed Sep 26 10:48:01 2018 : Not deleting jnlpool ipcs. 1 processes still attached to jnlpool
But if the instance is frozen, the output does not include the last line ("Not deleting jnlpool ipcs"). This is a regression in GT.M V6.3-000A. It would be nice to know if the jnlpool ipcs were not deleted even if the instance is frozen.
As for some background on this request, the msreplic_B/deadlock_check subtest failed because it expected to see the "Not deleting jnlpool ipcs" line in the source server shutdown command output but did not see it in one rare test run because the instance was frozen for a short time coincidentally when that shutdown command was run. That test failure could be fixed by removing the section which was expecting the "Not deleting jnlpool ipcs" string. But instead it was considered a better change to make the shutdown command output consistent whether or not the instance is frozen.
Draft Release Note
MUPIP REPLIC -SOURCE -SHUTDOWN gives an indication of whether it did not delete the journal pool shared memory and semaphores even if the replication instance is frozen. Previously, it used to give the indication only if the instance was not frozen.