Re: Hello! I am new member of list and excited to be part of this.

["Arlene M Soderlund" <Arlene_M_Soderlund/NFCNA.COM@xxxxxxxxx>]

>>>Checking the call stack in wrkactjob, I find that it is "supposedly" running
the >production version of the object.  Doing a wrkobj, I find that the object
also exists >in qrplobj (the old version of the object) and that it was last
changed when the move >was done.
>I scanned for qrplobj and found that our in house move process forces the old
object >into qrplobj.  Our in house recompile application does the same.  Both
dlt the old >qrplobj, then do a movobj on the current production version, then
move the test version >into production.  (we also archive the old source at this
time).  Anyway, recompiling the program with no changes effectively fixed the
problem, but the reason it did remains a mystery to me.  Any ideas?

     ....The Qrplobj library is where IBM compile will put programs, screen &
printer files that are in "USE" while compiling and they stay in use unless you
end the JOB using them.  BEFORE you compile over an exsisting object or move,
make sure you end ANY application using the program, compile and restart.

Some of the ways around this are to have a "Library" where new compiles go into
for live use, objects are kept form about a week then moved to the regular
library.

So your library list would be     NEWCOMPLIB  CURROBJLIB  DATALIB  QGPL  QRPG
etc.

A IPL will clean up the Qrplobj or you can delete them.









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