Locks on file objects not released unless RCLRSC is run -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Locks on file objects not released unless RCLRSC is run
From: "Chaudhary, Sachin \(GE Indust, ES Rail, consultant\)" <sachin.chaudhary@xxxxxx>
Date: Thu, 8 Jun 2006 20:02:52 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Sometimes if the application dumps in error, the system does not release locks 
on file objects. The locks are released when I run RCLRSC.

Can someone explain, what do we do if users face this problem...they do not 
have command line to run reclaim resource? Is it that their only option is to 
signoff from the interactive job, and login back again?

Regards,
Sachin

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.