Re: DSSCOPY and AIX?
The DSS manual clearly states you cannot change the number of qualifiers in a DSN with wild cards; you must use a fully qualified (complete) DSN. If you do a LISTC ALL for the cluster you will get the DSNs of the AIX and any paths. Just add additional pairs of parameters to the RENAMEU operand. I've never done it but it might be easier to use DUMP and RESTORE. DUMP has the NEWNAMEU operand which *appears* to be more inclusive. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lester, Bob Sent: Thursday, April 14, 2011 3:46 PM To: IBM-MAIN@bama.ua.edu Subject: Re: DSSCOPY and AIX? Hi Barry, Mea Culpa! It would probably help if I copy/paste the correct parm cards! Duh. My 1st example should have read RENAMEU(VTOVT). That simply changes the HLQ of the files copied and works fine.. SPHERE is specified in both examples, so the AIX/PATH is copied correctly - at least in my 1st example. Its component names are correct and in the correct catalog - which is different than the source dsn. I'm stumbling on RENAMEU(VOFD.CSLGROUP.MFDM0C0G,VTOVT.CSLGROUP.NEW.MFDM0C0G). I Have the need to add a qualifier to the target dsn, and this form works fine *except* for this dsn with the AIX PATH. I'm using this form of RENAMEU for multiple dsns in the same run - this is the only one with an AIX PATH, and is the only one that fails. I've checked the source file and its component and all looks fine - same catalog for all components, which seems to be what it's complaining about. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DSSCOPY and AIX?
On Fri, 15 Apr 2011 07:35:55 -0700, Schwarz, Barry A wrote: The DSS manual clearly states you cannot change the number of qualifiers in a DSN with wild cards; you must use a fully qualified (complete) DSN. Is there a credible rationale for this irritating restriction? BTW, an Innovation representative posted here quite a while back that FDR suffers no such rule, so it must be mathematically possible. --gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DSSCOPY and AIX?
Hi Barry, From my reading, I would have thought SPHERE would eliminate the need to specify the AIX/PATH entries. The source cluster, and all of its' components are in the same usercat. The target cluster is going to a different usercat. I thought I was getting pretty good a DFSMSdss syntax and usage, but Oh well, I can always use IDCAMS. Thanks! BobL -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Schwarz, Barry A Sent: Friday, April 15, 2011 8:36 AM To: IBM-MAIN@bama.ua.edu Subject: Re: DSSCOPY and AIX? The DSS manual clearly states you cannot change the number of qualifiers in a DSN with wild cards; you must use a fully qualified (complete) DSN. If you do a LISTC ALL for the cluster you will get the DSNs of the AIX and any paths. Just add additional pairs of parameters to the RENAMEU operand. I've never done it but it might be easier to use DUMP and RESTORE. DUMP has the NEWNAMEU operand which *appears* to be more inclusive. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lester, Bob Sent: Thursday, April 14, 2011 3:46 PM To: IBM-MAIN@bama.ua.edu Subject: Re: DSSCOPY and AIX? Hi Barry, Mea Culpa! It would probably help if I copy/paste the correct parm cards! Duh. My 1st example should have read RENAMEU(VTOVT). That simply changes the HLQ of the files copied and works fine.. SPHERE is specified in both examples, so the AIX/PATH is copied correctly - at least in my 1st example. Its component names are correct and in the correct catalog - which is different than the source dsn. I'm stumbling on RENAMEU(VOFD.CSLGROUP.MFDM0C0G,VTOVT.CSLGROUP.NEW.MFDM0C0G). I Have the need to add a qualifier to the target dsn, and this form works fine *except* for this dsn with the AIX PATH. I'm using this form of RENAMEU for multiple dsns in the same run - this is the only one with an AIX PATH, and is the only one that fails. I've checked the source file and its component and all looks fine - same catalog for all components, which seems to be what it's complaining about. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. OppenheimerFunds may, at its sole discretion, monitor, review, retain and/or disclose the content of all email communications. == -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DSSCOPY and AIX?
To give you something else to complain about? :) On Fri, Apr 15, 2011 at 10:49 AM, Paul Gilmartin paulgboul...@aim.comwrote: Is there a credible rationale for this irritating restriction? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
DSSCOPY and AIX?
Hi Folks, This may be an easy one, but I can't find the answer. Copying a dataset with an AIX and path like this works fine: COPY DATASET( - INCLUDE(VOFD.CSLGROUP.MFDM0C0G, -(This is the base cluster name and has an AIX and PATH) ...LOTS MORE DSNS) - FR(REQUIRED) - ALLDATA(*) - ALLEXCP - SPHERE - STORCLAS(STANDARD) - TOL(ENQF) - RENAMEU(VOFD,VTOVT) (These HLQs are in DIFFERENT catalogs) However, it fails when I try this: COPY DATASET( - INCLUDE(VOFD.CSLGROUP.MFDM0C0G, -(This is the base cluster name) ...LOTS MORE DSNS) - FR(REQUIRED) - ALLDATA(*) - ALLEXCP - SPHERE - STORCLAS(STANDARD) - TOL(ENQF) - RENAMEU(VOFD.CSLGROUP.MFDM0C0G,VTOVT.CSLGROUP.NEW.MFDM0C0G) I get the following error: ADR411W (001)-DDFLT(02), DATA SET VOFD.CSLGROUP.MFDM0C0G IN CATALOG USERCAT.PRODVSAM ON VOLUME PRD83B WAS NOT SERIALIZED ON REQUEST ADR711I (001)-NEWDS(01), DATA SET VOFD.CSLGROUP.MFDM0C0G HAS BEEN ALLOCATED WITH NEWNAME VTOVT.CSLGROUP.NEW.MFDM0C0G USING STORCLAS STANDARD, DATACLAS DCSTAND, AND MGMTCLAS NOACTION ADR764E (001)-DDFLT(01), DATA SETS IN SPHERE OF BASE CLUSTER VOFD.CSLGROUP.MFDM0C0G WITH NEWNAME VTOVT.CSLGROUP.NEW.MFDM0C0G WERE DIRECTED TO MORE THAN ONE CATALOG ADR763E (001)-DDFLT(01), DATA SETS IN SPHERE OF BASE CLUSTER VOFD.CSLGROUP.MFDM0C0G WITH NEWNAME VTOVT.CSLGROUP.NEW.MFDM0C0G WERE NOT ALL RENAMED. I'm missing something, since in both examples, the files ARE in different catalogs. But the 1st example works. Any ideas? z/OS 1.11, SMS. Target DSNs do not exist before the runs. Thanks! BobL -- This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. OppenheimerFunds may, at its sole discretion, monitor, review, retain and/or disclose the content of all email communications. == -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DSSCOPY and AIX?
Are you sure you are showing us the actual input? The RENAMEU operand of your first example does not say change the HLQ. Since it has no wildcards, it says rename the dataset whose name is exactly VOFD to exactly VTOVT. (It also seems to be missing a set of parentheses but they may be optional in this case.) Since you probably don't have any single qualifier datasets, no renaming should occur. And since you are not deleting the source dataset, the copy should fail because the target dataset cannot be catalogued. Your second example also has no wildcards to only the cluster gets renamed. The end result is the cluster HLQ is changed to VTOVT while the components' HLQ remain VOFD (which is what the last error message is telling you). Apparently a cluster and its components must be in the same catalog. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lester, Bob Sent: Thursday, April 14, 2011 12:28 PM To: IBM-MAIN@bama.ua.edu Subject: DSSCOPY and AIX? Hi Folks, This may be an easy one, but I can't find the answer. Copying a dataset with an AIX and path like this works fine: COPY DATASET( - INCLUDE(VOFD.CSLGROUP.MFDM0C0G, -(This is the base cluster name and has an AIX and PATH) ...LOTS MORE DSNS) - FR(REQUIRED) - ALLDATA(*) - ALLEXCP - SPHERE - STORCLAS(STANDARD) - TOL(ENQF) - RENAMEU(VOFD,VTOVT) (These HLQs are in DIFFERENT catalogs) However, it fails when I try this: COPY DATASET( - INCLUDE(VOFD.CSLGROUP.MFDM0C0G, -(This is the base cluster name) ...LOTS MORE DSNS) - FR(REQUIRED) - ALLDATA(*) - ALLEXCP - SPHERE - STORCLAS(STANDARD) - TOL(ENQF) - RENAMEU(VOFD.CSLGROUP.MFDM0C0G,VTOVT.CSLGROUP.NEW.MFDM0C0G) I get the following error: ADR411W (001)-DDFLT(02), DATA SET VOFD.CSLGROUP.MFDM0C0G IN CATALOG USERCAT.PRODVSAM ON VOLUME PRD83B WAS NOT SERIALIZED ON REQUEST ADR711I (001)-NEWDS(01), DATA SET VOFD.CSLGROUP.MFDM0C0G HAS BEEN ALLOCATED WITH NEWNAME VTOVT.CSLGROUP.NEW.MFDM0C0G USING STORCLAS STANDARD, DATACLAS DCSTAND, AND MGMTCLAS NOACTION ADR764E (001)-DDFLT(01), DATA SETS IN SPHERE OF BASE CLUSTER VOFD.CSLGROUP.MFDM0C0G WITH NEWNAME VTOVT.CSLGROUP.NEW.MFDM0C0G WERE DIRECTED TO MORE THAN ONE CATALOG ADR763E (001)-DDFLT(01), DATA SETS IN SPHERE OF BASE CLUSTER VOFD.CSLGROUP.MFDM0C0G WITH NEWNAME VTOVT.CSLGROUP.NEW.MFDM0C0G WERE NOT ALL RENAMED. I'm missing something, since in both examples, the files ARE in different catalogs. But the 1st example works. Any ideas? z/OS 1.11, SMS. Target DSNs do not exist before the runs. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DSSCOPY and AIX?
Hi Barry, Mea Culpa! It would probably help if I copy/paste the correct parm cards! Duh. My 1st example should have read RENAMEU(VTOVT). That simply changes the HLQ of the files copied and works fine.. SPHERE is specified in both examples, so the AIX/PATH is copied correctly - at least in my 1st example. Its component names are correct and in the correct catalog - which is different than the source dsn. I'm stumbling on RENAMEU(VOFD.CSLGROUP.MFDM0C0G,VTOVT.CSLGROUP.NEW.MFDM0C0G). I Have the need to add a qualifier to the target dsn, and this form works fine *except* for this dsn with the AIX PATH. I'm using this form of RENAMEU for multiple dsns in the same run - this is the only one with an AIX PATH, and is the only one that fails. I've checked the source file and its component and all looks fine - same catalog for all components, which seems to be what it's complaining about. Thanks! BobL -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Schwarz, Barry A Sent: Thursday, April 14, 2011 4:22 PM To: IBM-MAIN@bama.ua.edu Subject: Re: DSSCOPY and AIX? Are you sure you are showing us the actual input? The RENAMEU operand of your first example does not say change the HLQ. Since it has no wildcards, it says rename the dataset whose name is exactly VOFD to exactly VTOVT. (It also seems to be missing a set of parentheses but they may be optional in this case.) Since you probably don't have any single qualifier datasets, no renaming should occur. And since you are not deleting the source dataset, the copy should fail because the target dataset cannot be catalogued. Your second example also has no wildcards to only the cluster gets renamed. The end result is the cluster HLQ is changed to VTOVT while the components' HLQ remain VOFD (which is what the last error message is telling you). Apparently a cluster and its components must be in the same catalog. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Lester, Bob Sent: Thursday, April 14, 2011 12:28 PM To: IBM-MAIN@bama.ua.edu Subject: DSSCOPY and AIX? Hi Folks, This may be an easy one, but I can't find the answer. Copying a dataset with an AIX and path like this works fine: COPY DATASET( - INCLUDE(VOFD.CSLGROUP.MFDM0C0G, -(This is the base cluster name and has an AIX and PATH) ...LOTS MORE DSNS) - FR(REQUIRED) - ALLDATA(*) - ALLEXCP - SPHERE - STORCLAS(STANDARD) - TOL(ENQF) - RENAMEU(VOFD,VTOVT) (These HLQs are in DIFFERENT catalogs) However, it fails when I try this: COPY DATASET( - INCLUDE(VOFD.CSLGROUP.MFDM0C0G, -(This is the base cluster name) ...LOTS MORE DSNS) - FR(REQUIRED) - ALLDATA(*) - ALLEXCP - SPHERE - STORCLAS(STANDARD) - TOL(ENQF) - RENAMEU(VOFD.CSLGROUP.MFDM0C0G,VTOVT.CSLGROUP.NEW.MFDM0C0G) I get the following error: ADR411W (001)-DDFLT(02), DATA SET VOFD.CSLGROUP.MFDM0C0G IN CATALOG USERCAT.PRODVSAM ON VOLUME PRD83B WAS NOT SERIALIZED ON REQUEST ADR711I (001)-NEWDS(01), DATA SET VOFD.CSLGROUP.MFDM0C0G HAS BEEN ALLOCATED WITH NEWNAME VTOVT.CSLGROUP.NEW.MFDM0C0G USING STORCLAS STANDARD, DATACLAS DCSTAND, AND MGMTCLAS NOACTION ADR764E (001)-DDFLT(01), DATA SETS IN SPHERE OF BASE CLUSTER VOFD.CSLGROUP.MFDM0C0G WITH NEWNAME VTOVT.CSLGROUP.NEW.MFDM0C0G WERE DIRECTED TO MORE THAN ONE CATALOG ADR763E (001)-DDFLT(01), DATA SETS IN SPHERE OF BASE CLUSTER VOFD.CSLGROUP.MFDM0C0G WITH NEWNAME VTOVT.CSLGROUP.NEW.MFDM0C0G WERE NOT ALL RENAMED. I'm missing something, since in both examples, the files ARE in different catalogs. But the 1st example works. Any ideas? z/OS 1.11, SMS. Target DSNs do not exist before the runs. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. OppenheimerFunds may, at its sole discretion, monitor, review, retain and/or disclose the content of all email communications
