The data extract and load would be done using an ETL software or using
simple SQL statements:
Here is what it would look like in SQL:
/*Delete data from staging table*/
/*Load new data from production into Test library*/
INSERT INTO TESTLIB.TABLE1 (Col1, Col2, Col3)
SELECT Col1, Col2, Col3 from PRODLIB.TABLE1;
Doesn't seem to terribly complex to me?
Only the data load stuff would need to have libraries defined.
From: Charles Wilt [mailto:charles.wilt@xxxxxxxxx]
Sent: Tuesday, January 28, 2014 4:07 PM
To: Midrange Systems Technical Discussion
Subject: Re: Philosophical question - Staging tables, name and location
I was leaning in that direction. However, obviously there will be
processes that take data out of the staging table and put it into the
production table. If the name is the same, I'd have to qualify each name.
Which doesn't really play well with a IBM i CMS given my development and
production are on the same single LPAR box.
This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact