In the past, to meet a similar requirement, we had all programs declare the file in question as being user open. Then there was a system-wide flag that indicated that the file had changed. Each file interaction checked the flag (user space so just memory access) and if it didn't match its internal setting then it closed and re-opened.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Sep 25, 2018, at 11:50 AM, Kevin Bucknum <Kevin@xxxxxxxxxxxxxxxxxxx> wrote:

If you can never get a lock, then there RFE is required. I would be
surprised if there isn't one already.

At my current job we have a window every night where we can promote
those kinds of changes, and in emergencies we just call everyone and
make them get out. At my previous job, we kept a library above the main
screen/program library. If we had to make a change we placed the
screens/programs in that library. Everyone starting a new job got the
changes. As soon as the production objects where free, we replaced them.
At the next available window, we deleted the objects in the temporary
library. This worked good because for some screens there may have been a
week or more before we got a window. Only bad thing was if for some
reason you had to make two changes.




Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Niels Liisberg
Sent: Tuesday, September 25, 2018 10:37 AM
To: Midrange Systems Technical Discussion
Subject: Is there a way to replace a open display files

Gents / Ladies,

I have a production environment that runs 24/365 and some displayfiles
a
always open and have this annoying lock.

So moving the display file to QRPLOBJ, delete it or rename it will not
work.

Any ideas?

Is this issue a candidate for an RFE?

--
Best regards

Niels Liisberg
Chief Software Architect
System & Method A/S
Phone +45 70 20 30 10
Mobile + 45 31 15 88 61
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.