One additional note (that I thought of after seeing the DC AI Bot response): The DC AI Bot explains that the lock can be "manually" released by logging into terminal window and forcing the lock. And while that is true, the goal of my post is to allow our support team to be able to use our LIS web-based application to remove the locks and NOT have to waste time logging in to another piece of software to perform the task that should be able to be done via our LIS application. And as you can imagine, there is a whole separate support process including creation/updating/assignment/etc... of a support ticket if the support team is unable to use the LIS application for certain pre-defined/verified workflows. So it is not cost-effective to have to deal with support tickets every time an orphaned lock needs to be removed. So please keep this item in mind when offering feedback/suggestions for how to allow the LIS web-based application to remove the lock for another Cache process. Best Regards.
- Log in to post comments