BPCSDOC came with some instructions for test environments which I found to be inadequate. We have logicals in different libraries from their physicals & when we followed SSA's instructions we ended up with logicals in one environment pointing at logicals in another.
At some historical past point, all files in Live were also defined in Test, then over time various modifications added new stuff to Live and neglected to replicate in Test, so if you not repopulated Test in a while, you need to take an inventory of what is defined in Live that aint defined in Test. This also applies to software modifications. Also the procedure will vary by BPCS version.
Test software should not be an exact replica of Live, so that when people sign on either, it is pretty obvious you in TEST vs. LIVE environment, to avoid people getting confused, keying garbage into LIVE or spend days keying production data into TEST.
Aside from those OS hassles, there has been a revolution in computer security. It is no longer acceptable to have private sensitive data in a test, because software testing and user education is more likely to have a breach than the live area, so even more important not to copy stuff you not want in a news media circus when you have to report what got breached. Several good iSeries articles on facing this challenge are linked from this one.
Hi All, Does Anybody has a proper procedure while doing System Refresh (Copying of the data from Production Environment to Test Environment). I need to do that so that nothing is left out while doing the same. Thanks, vishu
<snip> confidentiality statement that is irrelevant to a public discussion forum.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.