Re: SETOBJACC Behavior w/Multiple Program Versions

-----Original Message-----
From: DAsmussen@aol.com <DAsmussen@aol.com>

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

Each job will use the correct version of the program based on its library
list, regardless of whether either or both is loaded into memory with
SETOBJACC.  It's no different than if one user has already started one
version of the program (thus loading it into memory), and another user
starts the other one.


---
Dave Shaw, General Nutrition, Greenville, SC (just down the road from BMW -
Bubba Makes Wheels :)
The opinions expressed may not be my employer's unless I'm sufficiently
persuasive...


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