Re: SETOBJACC Behavior w/Multiple Program Versions

Hi, Dean

At 04:10 PM 6/25/1998 EDT, you wrote:
>Hey Folks!
>
>Looking to save research dollars again ;-)!  I was in the process of
>implementing a SETOBJACC strategy for a client that was fairly
straightforward
>until this week, when they moved another plant with its' own customized
>version of BPCS onto the same production box on which we wanted to use
>SETOBJACC.  The question is, if I'm running program A from library B out of a
>shared pool, what happens to a job that wants to run program A from
library C?
>Will the instance of program A be determined by the job's library list, or
>will program A in the shared pool always be invoked?  Can both versions of
>program A be placed in memory and the correct version always be called based
>on *LIBL?

The library list will control it. Using SETOBJACC doesn't change how the
system handles objects, just has them persistent in main memory instead of
having to page them in. You could even load both into main memory with
SETOBJACC and be fine.

HTH

Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN  55401-2499
(612) 371-1111 x480


+---
| 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
+---