Re: menu-screen compile, object in use

The other aspect of this is that the menu in use can still be used, WITHOUT 
problems, but the one just changed MAY have problems, which if this is a 
production machine, will create a number of irate users, who for one reason or 
another are attempting to use an untested object.

>>> Douglas Handy <dhandy1@bellsouth.net> 04/03/01 03:00PM >>>
Jim/Steven,

>It is a pain.  If there is a work around (which I doubt) I would be
>interested in knowing about it also.

What I do is have another, normally empty, library higher in their library list.
If I need to change a menu during the course of a day, I compile it and place
the object in that library.  Anybody who later requests the menu gets the new
one, and if a current user needs it they can sign off/on at their convienence
rather than forcing all people with locks to quit at the same time.

A process which runs at night moves it to the correct library while there are no
object locks active.

This buys me one change per day, which is generally sufficient.  It at least
lessens the pain.

Doug
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com 
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---