As far as I know there’s no way to track who deleted an object, the only way to do this is scanning the joblogs, but this needs to be activeted in your case. It might be better to create a group-profile for the 9 people and deny them the existence right on objects. In that case they can rename or move the object but can’t delete it. You can make a scheduled job that checks the rights for the group-account and adds/deletes rights for *allusr objects for this group.
The cpysplf only replaces the member, so if something goes wrong with the job, the member can be gone, but the file must still be there. If the system goes down unexpectedly, the object can get damaged and/or moved to the qrecovery library.<b> You can review the audit journals to determine who deleted an object. Your system value QAUDLVL must include *DELETE before this action is logged to the journal.</b>