Re: Copy a *PGM object

[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.