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:[email protected]] On Behalf Of 
Schwarz, Barry A
Sent: Friday, April 15, 2011 8:36 AM
To: [email protected]
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:[email protected]] On Behalf Of 
Lester, Bob
Sent: Thursday, April 14, 2011 3:46 PM
To: [email protected]
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 
[email protected] 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 [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to