× 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.



On 10/31/13 8:46 AM, Darryl Freinkel wrote:
Done this millions of times. Today it fails.

I am creating a SQLRPGLE program. It fails immediately with the above
error. It is trying to do a RMVM on QTEMP/QSQLTEMP1 which is locked
by the job creating it, my interactive session.

A lock will not conflict in that case. The problem is that the file member was opened, but not closed. Review WRKJOB OPTION(*OPNF) to see the details of the open. Whatever opened the member of the file could be work that is still active in a prior call level for which its close activity might pend returning to that call-level, work in an activation group awaiting reclaim, an open scoped to the job, or an open that is in-error possibly due to a failed close.

<<SNIP>>

Anyone seen this problem before and if so what fixes it?


Effect the member close, and all should again be well.

Depending on how the file was opened, that may be via RCLACTGRP of the ACTGRP to which the open is scoped, CLOF if opened by OPNDBF or OPNQRYF, CLOSE if open by RCVF, RCLRSC if opened to the current or higher call-level, drop to a prior call level such that if not closed there by the application that opened the member then RCLRSC there, and of course if not understood how or too much work to detect what was the open and necessary means to effect the close then just SIGNOFF.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.