From: Billy Rowe To: All

I am trying to send a source file from one AS/400 to another. After I save the file to a *SAVF, then I SNDNETF the file to another AS/400 in the network. After I get the *SAVF file on the other AS/400, I use RSTOBJ to restore the source file QCLSRC to a library. The restore works, but it first renames my existing QCLSRC file to QCLSRC0001, then restores the new file to QCLSRC. The message in my job log is CPI320A (File level identifiers do not match). I don't care if they don't match-I just need to be able to restore a source file directly into another without having to first restore the source file into a temp library and then use CPYSRCF to copy the members into the correct file and correct library.

For example, say I have a source file on SYS-A and the same source file on SYS-B. On SYS-A, I add two new programs, modify two programs and then compile those. I then SAVOBJ the two new programs and two modified programs and their load members to a *SAVF. I then SNDNETF that save file to SYS-B. I want to be able to restore all those members into the source file on SYS-B by using the RSTOBJ command, choosing to restore *ALL members, and then have the two new programs added to the file and the two modi-fied members replaced in the li- brary....Any ideas?

From: Trevor Perry To: Billy Rowe

Are the two AS/400s at different OS/400 releases? Also, after the first one is replaced, if you resend the same file and restore it, what sort of message do you get? Let me know.

From: Billy Rowe To: Trevor Perry

Yes, the AS/400s are at different releases, but I use TGTRLS (Target release) on the SAVOBJ command for the correct release that I am going to. As for your second question, when I add another member to source file and resend it, then restore it on the previous release machine, the file is not renamed this time and the restore works OK.

From: Greg Leister To: Billy Rowe

If you have the ability to use DDM on your systems, it would be much easier to create a DDM file and copy the source from one system to the other. We use DDM on our systems (AS/400 - S/38) and it works great. I also wrote programs that let you select the files, members and libraries, which system to copy from and copy to, plus a few other options. It creates the DDM files, does the copy and cleans up after itself. If you can use DDM and want to try it out, let me know.

From: Paul Yust To: Greg Leister

I also use DDM to copy files between systems. I had been thinking it would not be too difficult to wrap a command and CL program around the process to make it more automatic. No use reinventing the wheel. If you are willing to share your code, I would be interested. Also, does your code handle non-file objects via a behind-the-scenes save file? I had thought this would be possible also, along with a SBMRMTCMD to the target system to restore the save file.

From: Greg Leister To: Paul Yust

No problem on uploading the source. As far as non-file objects, my code is set up to copy source files, but it could be modified easily to try. If you get to it before I do, let me know what happens.

From: Paul Yust To: Greg Leister

Thanks, I got the file and I will give it a try. In the meantime, I found an old set of commands called SNDOBJ and RCVOBJ in the Resource-Library. In concept, these commands are close to what I want. That is, they transmit any and all objects via save files. Just started playing with the command and CL programs. If you are interested, I will upload a copy of my modified commands and CL programs.