It is helpful when copying VSAM with DFDSS to use SPHERE. What version of z/OS?
Have you done this before successfully with VSAM? You also need to rename the VSAM datasets during copy unless they will be residing in a different LPAR. I am not sure you can copy VSAM as an uncataloged datasets on a new volume. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Mainframe Mainframe > Sent: Wednesday, May 21, 2014 1:16 AM > To: [email protected] > Subject: copy data issue > > Hello, > I am trying for volume level copy of datasets but getting below > error for > some of the dataset. > > //COPY10 EXEC PGM=ADRDSSU > //SYSPRINT DD SYSOUT=* > //IN1 DD DISP=SHR,UNIT=3390,VOL=SER=USER01 > //OT1 DD DISP=SHR,UNIT=3390,VOL=SER=USER02 > //SYSIN DD * > COPY DATASET( - > INCLUDE(**) - > EXCLUDE(SYS1.VTOCIX.**, - > SYS1.VVDS.**, - > ) ) - > INDDNAME(IN1) - > OUTDDNAME(OT1) - > ALLDATA(*) - > ALLEXCP - > TOL(ENQF) - > CANCELERROR > /* > > > 0ADR411W (001)-DDFLT(02), DATA SET SYSL.SMS1.ACDS IN CATALOG > TST.MASTER.CATALOG ON VOLUME USER01 WAS NOT SERIALIZED ON > REQUEST 0ADR468E (001)-DDFLT(04), VSAM DATA SET SYSL.SMS1.ACDS > IN CATALOG TST.MASTER.CATALOG IS NOT PROCESSABLE 0ADR411W > (001)-DDFLT(02), DATA SET SYSL.SMS1.COMMDS IN CATALOG > TST.MASTER.DATA ON VOLUME USER01 WAS NOT SERIALIZED ON > REQUEST > > These dataset are not getting copied to target volume.Any suggestion. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
