RE: Replicating Data Between IBM i Prod and Dev

That's how we did it at my last employer. Worked great for us.

We also had a number of RUNSQL commands to obfuscate or tweak some of the data - like email addresses for customers or IP/DNS info so we didn't send/retrieve data from customers from Dev.

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power



-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Robert Rogerson
Sent: Friday, September 27, 2024 1:49 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Replicating Data Between IBM i Prod and Dev

Hi Richard,

The approach taken at one customer I've worked at is that every Sunday
morning they restore all the data from the last production backup (which is
still on site) to the development environment. This is only data libs.

Then they have programs that run that reduce/delete data that is not really
needed in dev.
It works pretty good as often you can test/debug with data that is only a
week old in dev.

Rob

On Fri, Sep 27, 2024 at 4:35 PM Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
wrote:

HI All,

Customer wants to regularly refresh data between Production and Dev
systems. (Once every few weeks be able to refresh)

Please give me some ideas on best practices.

I can think of:
-Replication software. (Probably the MOST up to date)
-Save/restore libraries between systems with save files
-Use DDM files to move data.

Please share your strategies to keep test data relatively fresh on your
dev systems.

Thanks in advance.

Regards,
Richard Schoen
Web: http://www.richardschoen.net/<http://www.richardschoen.net/>
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.