No, TRANSFER is what it says, the object is transferred, not copied/cloned/xxx
As you do not have the privilege to use DIAG D4 to set the origin, you could create a service machine that has the privilege, it could perform the copies of the spool files x times. 2009/9/22 Gonen Shoham <gone...@sapiens.com> > TRAN RDR does it ok, but deletes the file from my reader. > > Is there anyway to keep the RDR after TRAN RDR ? > > The reason is that I need to TRAN the RDR many times . > > > Thanks > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On > Behalf Of Kris Buelens > Sent: Thursday, September 17, 2009 10:59 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: COPY RDR to another machine > > I doubt that COPYRDR keeps *all* the properties, e.g. creation time will > be changed. > For an exact copy: SPXTAPE to dump the RDR file to tape, then restore on > the target system. > > If you only need to set the origin userid: use Diagnose D4 to set the > alternate userid of the copying user to the sender's userid. As this is > cheating, one needs a special CP class to be able to use Diag D4; and if > an ESM is installed, extra permissions are required in the ESM (for RACF > that is in class VMBATCH). > My RxServer package contains a DIAGD4 MODULE, you would use this > sequence: > DIAGD4 copier sender > EXEC COPYRDR > DIAGD4 copier OFF > > > 2009/9/17 Gonen Shoham <gone...@sapiens.com> > > > Hi > > I have the COPYRDR exec (from long time ago) which sends RDR > file from one machine to another - keeping ALL the original RDR file > properties. > > > > I found out that the USER which sent the original RDR file is > not kept when the RDR is copied to another user. > > > > Can someone suggest a better way to "replicate" RDR file from > one machine to another with keeping the original user ? > > > > many thanks > > > > > -- > Kris Buelens, > IBM Belgium, VM customer support > -- Kris Buelens, IBM Belgium, VM customer support