Hmmm.... I tried SNDTCPSPLF on our LPAR system, sending one of my splfs from one partition to another, and it appeared just fine. But if I send someone else's splf, it still appears under my profile. Do all your users have profiles on the new system? (I assume both systems are going to be operational at the same time, judging by your message.) If the users have profiles there, but don't have authority to SNDTCPSPLF, maybe you could write a program that the users could run that does SNDTCPSPLF under adopted authority. That way I think the splfs would arrive on the system under their profiles, under a QPRTJOB job. It's not possible to also maintain the same job name, job number, and splf number on the sent splfs, though. Another way might be to copy them over as you described, using SNDTCPSPLF under someone else's profile. Once they're there, you can use SNDNETSPLF to send a copy to the user, and the splf will then exist under the user's profile, "linking it up" with the user. Then delete the originally-sent splf. Or maybe SNDNETSPLF can do it directly, if the users have an appropriate directory entry pointing to the new system. Or CPYSPLF to a PF (one PF per user with multiple members?), copy the PF, and restore the spools from the PF. Or use Operations Navigator to drag them from one system to another. It appears to run SNDTCPSPLF under the covers, so you have the same problem of the file not belonging to the user if it's not the user who transfers it. Or buy one of a number of tools that save/restore/transfer splfs.