Re: Copy a *PGM object

We use a similar process at the place I am contracting.
After x many days and no issues, we move the objects to the production
library. Programs and other objects can be moved whilst they are in use.
We check for locks first and if none, then we move the objects. The objects
with locks are usually DSPF and maybe PRTF if the program is long running.
We have to wait for users to return to their menu's to do this.

We do not put Physicals or logicals into the temporary library. There
really is no fall back for changed physical files, so we make those changes
directly into the production library. The programs go into the temporary
library but they cannot be removed if there is a problem. We fix in place
or if a major issue, we will then recompile the previous program's version
using the new file(s).

Darryl.

On Thu, Apr 29, 2021 at 3:49 PM John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

[Crossposted to MIDRANGE-L, since this is not specific to RPG]

On Thu, Apr 29, 2021 at 3:25 PM Greg Wilburn
<gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

I would like to copy a program object to a different library, but

maintain the change/usage information.

I don't really have any change management software... so I typically put

new objects in a "PTF" library that is before the production library. Once
all is OK, I move it to the production library. Sometimes the object is in
use and I can't "move" it, but I can copy it.

I think the usual thing to do if you don't have change management
software is to submit a job that runs at a time when you know it won't
be in use and have that job move the object.

At its simplest, that job could consist of the MOVOBJ command. If you
want to be more robust, or you have multiple objects to move, then you
can make a little CLP that does the desired handling (possibly moving
old production objects to a backup location, sprinkled with MONMSG,
etc.). This is the classic "poor man's object promotion" scheme, and
at some shops, this evolves into a permanent nightly job schedule
entry and permanent CLP which moves the entire contents of the
designated staging library (PTF in your case) to the production
library.

John Y.
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com