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

Guys,

I'm surprised this is not the same for all objects on the AS/400 eg DSPF.


Oludare


----- Original Message -----
From: "Reger, Bill" <breger@levitz.com>
To: <MIDRANGE-L@midrange.com>
Sent: Tuesday, January 18, 2000 1:47 PM
Subject: RE: Hello! I am new member of list and excited to be part of this.


> Allen,
>
> QRPLOBJ is used to allow you to move new programs into production while
> others (users, etc.) are currently running the old program.  If IBM didn't
> have QRPLOBJ, you would have to ask everyone to get out of the program
> before you could move in the new version.  Once everyone is finished using
> the old version, it will be automatically removed from QRPLOBJ.  If you
want
> everyone to start using the new version, they must exit the program back
to
> a menu and then go into the program again.  Signing off and back on will
do
> the trick too.
>
> William K. Reger
> Senior Project Manager
> Levitz Furniture Corporation
> Phone:  (561) 994-5114
> E-mail:  breger@levitz.com <mailto:breger@levitz.com>
>
> -----Original Message-----
> From: Allen Overeem [mailto:AOvereem@stvgb.org]
> Sent: Tuesday, January 18, 2000 9:31 AM
> To: MIDRANGE-L@midrange.com
> Subject: Hello!  I am new member of list and excited
> to be part of this.
>
> Hello!  I am new member of list and excited to be part of
> this.
> We recently upgraded our system to AS400e to version and
> release 4.  Since then, we have had several instances where a recently
moved
> (from test to production) pgm object needed to be recompiled to function
> properly.
> This happened to me last week.  I had the pgm with changes
> moved into production.  I checked the app to see that all was well and
> noticed that my changes did not seem to be in affect.  I copied the new
> production object back to my library again and ran tests against it.  It
> worked just as expected.  All the while, it was still running incorrectly
in
> production.  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?
> I would also like to know more about what qrplobj is used
> for;  AS400 books tells me that I should not move objects there because
name
> reference problems can occur (this seems to be what is happening to us
> except the call stack tells me the pgm obj is in production??), etc., but
it
> does not tell me what it is really used for.   Also, what reason might an
> intelligent programmer have to force objects into qrplobj in addition to
> archiving the source???
> Thanks for any help!!
>
> Allen L. Overeem
> Information Services
> St.  Vincent  Hospital
> Phone: (920) 431-3111
> E-mail: aovereem@stvgb.org
>
> +---
> | 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
> +---

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