Yes, some of the dataset were copied and the target dataset were not
cataloged.
In my earlier JCL, I have not specified Process(SYS1), but still I was
able to copy SYS1 datasets.
Regards
Saurabh Khandelwal
On 4/7/2011 7:24 AM, chen lucky wrote:
I have following question about this ADRDSSU COPY,
1.in original post, there is no 'delete' parameter specified, but even so,
there are still some DataSets had been copied successfully. Do not know why,
may these copied ones are not cataloged? seems not the reason.
2.'PROCESS(SYS1)' is also not specified, but some SYS1.** get copied
successfully, still do not know why, strange……
2011/4/7 Schwarz, Barry A<[email protected]>
I had non-managed VSAM datasets (zFS to be exact) on z/OS 1.8.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Lizette Koehler
Sent: Wednesday, April 06, 2011 5:34 AM
To: [email protected]
Subject: Re: ADRDSSU issue
I see you are at z/OS V1.9. VSAM datasets If I remember are always SMS
Managed and it is not until z/OS V1.12 that you can use indirect VSAM
cataloging. I am not sure you can copy the same name VSAM dataset. You may
need to copy to a new VSAM dataset name
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
