Sorry, meant to say remote database entry instead of DDM.

-----Original Message-----
From: Matt Olson [mailto:Matt.Olson@xxxxxxxx]
Sent: Monday, September 28, 2015 11:26 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Quickest way to copy data from production LPAR to DEV LPAR

I am attempting to copy data from a file in the production LPAR to the DEV LPAR and have yet to find an easy way to do it.

Here is what I looked at so far:


1. iSeries Navigation Export/Import function. No Go, only works with flat files, can not point to other system.

2. DDM (so far not working due to bug in iSeries navigator with base database *LOCAL name on DEV LPAR being same as production LPAR and navigator apparently doesn't understand aliases to overcome this limitation). Apparently if we could get this working you can do a copy/paste from one system to another in iSeries navigator (would be awesome if it worked).

3. SAVF, FTP, restore SAVF, do a rain dance.

So far nothing is easy. I'm about ready to just build a Microsoft SQL Server SSIS data transfer package but it seems like I shouldn't have to do this. Option #3 has been the historical mode of operation but is too time consuming.

Any other thoughts on how to do this quickly with as few steps as possible?

Matt

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



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].