• Subject: RE: QRPLOBJ Library
  • From: "Sims, Ken" <KSIMS@xxxxxxxxxxxxxxxx>
  • Date: Fri, 28 Jan 2000 20:06:24 -0500

Hi Allen -

>Date: Fri, 28 Jan 2000 14:15:05 -0600
>From: "Allen Overeem" <AOvereem@stvgb.org>
>Subject: RE: QRPLOBJ Library
>
>Lurton wrote:
>____________________________________________________________
>If you compile an object (pgm) with replace yes, it will create a duplicate
>of the object in QRPLOBJ with a strange name like Q34578ikl.  The original
>object name will be in the text. So, if a program is running and you
>recompile, the old program will still be in the job stack until the user
>ends the program.   The next instances will always get the new program
>because the rename process prevents them from calling the old.
>__________________________________________________________
>
>Thanks but this is totally unrelated to the situation I am describing.
First of all, the >program to be moved or recompiled is NOT running!
Second, we are forcing the object into ?>qrplobj  with a cl movobj command
within our inhouse software program that we use to do moves >and recompiles.
The name is not being changed, there is no Q appended by the system-this is
>inhouse software forcing the "move" of the existing object with the same
name to qrplobj just >before moving the new object into production.  What I
need to know is what the OS might do >with the object because of this
force??  Is it possible that there is a change in the OS >between release 2
and 4 (which we upgraded to just before seeing this strange behavior) that
>might cause problems resolving to the "correct" object?? Thanks anyway.

This is hypothetical, but I think that your first sentence is wrong and that
Lurton is on the right track.

If the program is active, it is always called by the pointer, so the old
version will always be used.

You are saying that the program is NOT active.  Even so, a job could still
have a pointer to the program.  Here comes the hypothetical part.  It is
possible that when a call to a program is made and the job has a pointer,
that the object name is retrieved through the pointer and if the name is the
same, the pointer is used, regardless of what library the object is in.  If
the name is not the same, the pointer is discarded and the program located
by name and library or library list.

If this is true, then renaming the object as well as moving it, would take
care of your problem.  You wouldn't have to use the strange names that IBM
does to ensure uniqueness, you could just stick an 'X' on the end or
something (assuming that the object names aren't already 10 characters
long).

Ken
Southern Wine and Spirits of Nevada, Inc.
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone else.

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


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

This mailing list archive is Copyright 1997-2019 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].