In all Linux serves, we have problems when we uninstall PAMSC endpoint.
The problem was because we have a conflict with falcon application, because that application was started after PAMSC. PAMSC should be always the last in starting up.
Release : PAMSC 14.1
Be able to see the applications intercepting PAMSC kernel
Usually it is because the application has been started after PAMSC, if PAMSC is the last one starting there is not problem.
The only way to confirm the problematic application is to set up a kernel debugger on the problematic system and review some internal memory locations. With the new kernel feature in PAMSC 14.1 post-CP5, the shutdown-out-of-order problem can be avoided and there is a way to check what product blocks it.
There is a new kernel feature created that will be included in cp06 that will tell you which is the problematic application in such cases. When you try to shutdown, now is not possible, with that new feature will tell you why.
In cp06 this feature will be included