Re: Locks on file objects not released unless RCLRSC is run

   Sachin:
   You could give these guys a menu option that would run the RCLRSC command
   for them.  Since these sound like these guys have "Limit capabilities" set
   to *YES, I suspect that your menu programs are owned by someone more
   powerful and that they adopt their owner's authority.  If not, then have
   the menu call a (one-line) CL program that does adopt enough authority nad
   runs the RCLRSC command.
    
   If you come to a situation where RCLRSC is not "enough" to get rid of
   locks, old activation groups, open files, etc., you could always use the
   RRTJOB command instead.  That's much more powerful and less convenient
   since it erases everything except your current library list and your
   joblog history.  It puts you back at your initial menu/program as though
   you just signed-on.

   I hope this helps you.

   Dave Schnee,
   Barsa Consulting Group, LLC

   ----- <sachin.chaudhary@xxxxxx> wrote: -----

   date: Thu, 8 Jun 2006 20:02:52 -0400
   from: "Chaudhary, Sachin \(GE Indust, ES Rail,    consultant\)"
       <sachin.chaudhary@xxxxxx>
   subject: Locks on file objects not released unless RCLRSC is run

   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