There shouldn't be any harm in using the SPHERE option on a VSAM dataset copy operation.
SPHERE specifies that, for any VSAM cluster copied, all associated AIX® clusters and paths are to be copied. Individual names of sphere components do not need to be specified. Only the base cluster name is required. If output volumes are specified, the volumes on which the AIX clusters reside do not need to be specified. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&[email protected] ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, May 16, 2020 3:59 PM, Gorham, Steve <[email protected]> wrote: > Sounds like a KSDS. Are there any alternate indexes? Is the dataset > multi-volume? Is not, you should be OK specifying just the base cluster name. > > Steve Gorham, Baltimore > > -----Original Message----- > From: IBM Mainframe Discussion List [email protected] On Behalf Of > [email protected] > Sent: Saturday, May 16, 2020 3:54 PM > To: [email protected] > Subject: [EXTERNAL] Re: DFSMS Move Dataset > > I am Not a DASD Administrator - > . > However I used the following JCL to move a PDS - > //STEP1 EXEC PGM=ADRDSSU > //SYSPRINT DD SYSOUT=A > //DASD1 DD UNIT=3390,VOL=(PRIVATE,SER=USER12),DISP=OLD > //DASD2 DD UNIT=3390,VOL=(PRIVATE,SER=USER01),DISP=OLD > //SYSIN DD * > COPY DATASET(INCLUDE(MONSOON.SRCLIB.BKUP)) - > LOGINDDNAME(DASD1) OUTDDNAME(DASD2) DELETE CATALOG > /* > . > Would Anyone have an example of moving VSAM Datasets Do I specify the base > cluster ? Do I specify the base cluster, data component, and index component > ? An Example would be appreciated ? > > ---------- Original Message ---------- > From: David Spiegel <[email protected]mailto:[email protected]> > To: [email protected]mailto:[email protected] > Subject: Re: DFSMS Move Dataset > Date: Fri, 15 May 2020 14:20:08 -0400 > > Hi Paul, > A bit of advice (I've been using DFSMSdss for 30+ years). > > Unless not possible, ALWAYS obtain your list of Datasets to be processed, via > Logical criteria. > (Do not, unless you have to, use Physical criteria). > The difference between them is that Physical criteria are generated by coding > INDDNAME or INDYNAM. > (If you code LOGINDDNAME or LOGINDYNAM it's Logical.) > > You will likely hear that Physical means Full Volume and that Logical means > by Dataset. > This statement is ABSOLUTELY false. > > One more thing ... always code OPT(4) to read a Cylinder at a time. > > Good luck! > > Regards, > David > > On 2020-05-15 13:39, [email protected]mailto:[email protected] wrote: > > > Hello. > > Does IBM (DFSMS) have a utility that will move VSAM and/or non-VSAM > > dataset to a different VOLUME ? > > . > > Paul D'Angelo > > * > > * > > * > > > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected]mailto:[email protected] with the > > message: INFO IBM-MAIN . > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected]mailto:[email protected] with the message: > INFO IBM-MAIN > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected]mailto:[email protected] with the message: > INFO IBM-MAIN > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
