Update data on a partition

[Guest.Visitor]

What you could also do is to use the OjbectConnect commands (SAVRST). This can work very well in an LPAR situation because of the following. In a normal environment the SAVRST commands create a save file, saves the objects, then sends it to the required system where it is received and the restore made. In an LPAR situation the system does not create the save file it does the save/restore via memory. So can be very fast.

[Guest.Visitor]

We are setting up a development partition on our system which will have copies of several production libraries. Aside from things like remote journals or database triggers, what might be the best way to update the data files on the partition with the updated data on the production partition? The libraries all contain the same 1-member physical files; we rarely add or change files. The update would occur weekly. Most of the files have a "Last Change" field, so we might be able to use that to get updated records. I've tried saving objects to a savefile, then transfering the savefile to the partition DevPttn with CPY OBJ('/qsys.lib/mylib.lib/save.file') TODIR('/qntc/QFileSvr.400/DevPttn/qsys.lib/mylib.lib') but that seems very slow. I imagine FTP would be faster. We might also restore the files from our Full backup on Saturday. Ideas/pros/cons? It's too bad we can't do CPYF MBROPT(*UPDADD) across partitions.

[Guest.Visitor]

Try setting up a virtual LAN and using management central to relocate data with a package definition. The VLan is 1Gbit and is as quick as a 3590e. The redbook 'Slicing the AS400 with Logical Partitioning' is a good start.