z/OS DISP=(OLD,DELETE) works without any problem to delete a VSAM cluster that 
you own.  I use that JCL all the time to delete test VSAM files.

Creating a VSAM cluster may often require IDCAMS DEFINE, but the JCL LIKE 
parameter is your friend if for instance you are making a copy of a production 
file for a unit test run.  Just use the UNIT and SPACE parameters to allocate 
space and all else will be copied from the LIKE cluster.

Now if any of the LIKE cluster parameters are incompatible with your immediate 
need (REUSE vs NOREUSE perhaps, or LOG parameters for RLS) then you do need 
DEFINE, but the JCL DELETE works without an issue that I am aware of.

Peter

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Wayne Bickerdike
Sent: Tuesday, July 10, 2018 3:52 PM
To: [email protected]
Subject: Re: z/OS JCl vs. VSE JCL: VSAM files

*How can it infer the difference between KEEP and DELETE?  (Or is thatthe
"mostly" part?)-- gil*


*On Wed, Jul 11, 2018 at 4:48 AM, Paul Gilmartin
<[email protected]
<[email protected]>> wrote:*
>
> *On Tue, 10 Jul 2018 14:23:34 -0400, Tony Thigpen wrote: > >Take a simple
> "I want to use a VSAM file". Here is what is normally used: >z/OS:
> >//POLYUPD  DD DSN=PROD.HKY.VSAM.HPP002P.F03,DISP=SHR >z/VSE: >// DLBL
> TEITEST,'TEI.TEST.VSAM',,VSAM,CAT=VSESPUC > >z/OS (mostly) requires a
> DISP=. VSE (mostly) does not. VSE determines >the correct setting at open
> time. > How can it infer the difference between KEEP and DELETE?  (Or is
> that the "mostly" part?) -- gil *

How does z/OS have a JCL DELETE option for a VSAM file? As far as I know,a
VSAM file has to be explicitly DELETE/DEFINED using IDCAMS.
--


This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to