![]() |
![]() HP OpenVMS Systemsask the wizard |
![]() |
The Question is: We have 200-300 concurrent processes running applications utilizing indexed RMS files. When a record gets locked for long periods of time (program bug or the users "go to lunch" in the middle of a transaction) the RMS lock may cause dozens of other users to hang or apps to bomb. Is there a way to identify what RMS files/records are locked and the PID that owns the lock? We've been nailed with this several times in the past month. Any help would be appreciated. Thanks! The Answer is : DECamds would be the immediate choice of the OpenVMS Wizard. This tool is separately installed, but is licensed with OpenVMS. The application can also be recoded to only hold the record lock for a specified interval, before forcing the record accessor to reload the data and try again. More quickly.
|