Promote programs into production

When a program I compile is running, it gets moved to QRPLOBJ but does not crash, it just keeps running from QRPLOBJ (you can see it on the program stack).
Seems like a printer file or display file could do the same.

We did this ourselves at one LAWSON implementation in the 1990's . . .
As we started to modify menu screens and application screens - which were likely going to modify pgms and screens again and again -
so in the calling CL we would first do a CRTDUPOBJ into QTEMP of the screens.
The version of the screen that went into QTEMP matched the QRPLOBJ program - and the users could keep working in that older version of both for as long as they wanted to for the rest of the day.
This allowed us to release program changes AND screen changes in the middle of the day when we had staff available to support any fallout problems.

( Aside: The other particularly nasty part of LAWSON was that a File-Inquiry screen was just the File-Maintenance screen and pgm with the DDS Protect keyword turned on.
So a user leaving their Inquiry screen up all night had a record locked until the operator killed the interactive session before doing the backups. )

But all in all, we got the app up and running without too much disruption and we got the users trained to signoff at end of day.

- John Voris