Re: Allocating VSAM in JCL was Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-11 Thread Longabaugh, Robert E
I use JCL VSAM for CA Allocate testing

This example was for an in-house program and is from 2005, so 13 years ago 
sounds right.  Obviously KEYLEN and KEYOFF are only needed for RECORG=KS.
//PTFXREF   DD   DISP=(,CATLG,DELETE),DSN=, 
//  STORCLAS=TSO,   
//  LRECL=206,KEYLEN=7,KEYOFF=0,RECORG=KS,  
//  SPACE=(TRK,(10,10)) 


TSO ALLOC can also create VSAM files.  TSO DEFINE would be easier, but 
different syntax.
ALLOC DA('TST.XYZ.LDS') -   
 NEW CATALOG  -  
 TRACKS -
 SPACE(5 5) -
LRECL(4096) -
RECORG(LS) - 
DATACLAS(LDS) -
STORCLAS(SMSLDS) -  
DSNTYPE(EXTREQ) -
DSKEYLBL(TEST.KEY)






-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Clark Morris
Sent: Wednesday, July 11, 2018 10:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Allocating VSAM in JCL was Re: z/OS JCl vs. VSE JCL: VSAM files

CAUTION: This email originated from outside of CA. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.


[Default] On 10 Jul 2018 15:33:56 -0700, in bit.listserv.ibm-main 
johnrcl...@gmail.com (John Clifford) wrote:

>it is not the default but is the only correct way to access a vsam file.
>disp=shr,dsn=.vsam (possible bufno,bufni,...etc)
>
>Never disp=new or delete.   Disp=old can be used if you need to make sure
>you are the only one accessing the file but if it is open in CICS it 
>will hang.

As of over 13 years ago, you could allocate a VSAM file in JCL and even a 
temporary one.  I never used the facility but it is there.

Clark Morris
>
>On Tue, Jul 10, 2018 at 6:07 PM, Tony Thigpen  wrote:
>
>> So, DISP=SHR is not the default, as I thought was implied by John's 
>> statement that "Z/os VSAM is always accessed as DISP=SHR."
>>
>> Tony Thigpen
>>
>> Gibney, Dave wrote on 07/10/2018 05:49 PM:
>>
>>> If DISP=SHR (that is if not DISP is provided), then the JCL Default 
>>> of
>>> (NEW,PASS) would happen and the job would fail
>>>
>>> -Original Message-
>>>> From: IBM Mainframe Discussion List 
>>>> [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Thigpen
>>>> Sent: Tuesday, July 10, 2018 2:43 PM
>>>> To: IBM-MAIN@LISTSERV.UA.EDU
>>>> Subject: Re: z/OS JCl vs. VSE JCL: VSAM files
>>>>
>>>> Then, why does every VSAM DD for every z/OS site I have worked 
>>>> with, always include DISP=SHR?
>>>> (I guess, because it's a habit from non-VSAM files and nobody told 
>>>> them they did not have to do it.)
>>>>
>>>> Tony Thigpen
>>>>
>>>> John Clifford wrote on 07/10/2018 04:16 PM:
>>>>
>>>>> Z/os VSAM is always accessed as  DISP=SHR.
>>>>>
>>>>
>>>> ---
>>>> --- For IBM-MAIN subscribe / signoff / archive access instructions, 
>>>> send email to lists...@listserv.ua.edu with the message: INFO 
>>>> IBM-MAIN
>>>>
>>>
>>> 
>>> -- For IBM-MAIN subscribe / signoff / archive access instructions, 
>>> send email to lists...@listserv.ua.edu with the message: INFO 
>>> IBM-MAIN
>>>
>>>
>>>
>> -
>> - For IBM-MAIN subscribe / signoff / archive access instructions, 
>> send email to lists...@listserv.ua.edu with the message: INFO 
>> IBM-MAIN
>>
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions, send 
>email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Allocating VSAM in JCL was Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-11 Thread Clark Morris
[Default] On 10 Jul 2018 15:33:56 -0700, in bit.listserv.ibm-main
johnrcl...@gmail.com (John Clifford) wrote:

>it is not the default but is the only correct way to access a vsam file.
>disp=shr,dsn=.vsam (possible bufno,bufni,...etc)
>
>Never disp=new or delete.   Disp=old can be used if you need to make sure
>you are the only one accessing the file but if it is open in CICS it will
>hang.

As of over 13 years ago, you could allocate a VSAM file in JCL and
even a temporary one.  I never used the facility but it is there.

Clark Morris
>
>On Tue, Jul 10, 2018 at 6:07 PM, Tony Thigpen  wrote:
>
>> So, DISP=SHR is not the default, as I thought was implied by John's
>> statement that "Z/os VSAM is always accessed as DISP=SHR."
>>
>> Tony Thigpen
>>
>> Gibney, Dave wrote on 07/10/2018 05:49 PM:
>>
>>> If DISP=SHR (that is if not DISP is provided), then the JCL Default of
>>> (NEW,PASS) would happen and the job would fail
>>>
>>> -Original Message-
>>>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
>>>> On Behalf Of Tony Thigpen
>>>> Sent: Tuesday, July 10, 2018 2:43 PM
>>>> To: IBM-MAIN@LISTSERV.UA.EDU
>>>> Subject: Re: z/OS JCl vs. VSE JCL: VSAM files
>>>>
>>>> Then, why does every VSAM DD for every z/OS site I have worked with,
>>>> always include DISP=SHR?
>>>> (I guess, because it's a habit from non-VSAM files and nobody told them
>>>> they
>>>> did not have to do it.)
>>>>
>>>> Tony Thigpen
>>>>
>>>> John Clifford wrote on 07/10/2018 04:16 PM:
>>>>
>>>>> Z/os VSAM is always accessed as  DISP=SHR.
>>>>>
>>>>
>>>> --
>>>> For IBM-MAIN subscribe / signoff / archive access instructions, send
>>>> email to
>>>> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>>>
>>>
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>>
>>>
>>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-11 Thread John McKown
On Wed, Jul 11, 2018 at 8:36 AM Steve Smith  wrote:

> DISP=NEW or OLD is perfectly valid for VSAM and PDSEs.  PDSEs presumably
> use some kind of hidden paging interface like LINEAR and ZFS do, but are
> not VSAM.
>

AFAIK, these use "Media Manager" for their I/O instead of the historic EXCP
or EXCPVR. "Media Manager" is not documented. I think the documentation is
only available to ISPs under an NDA; for a high cost and with no updates
included.



>
> sas
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
There is no such thing as the Cloud. It is just somebody else’s computer.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-11 Thread R.S.

W dniu 2018-07-10 o 22:05, Farley, Peter x23353 pisze:

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.


UNIT? That old JCL keyword commonly used in the dark ages before SMS?
;-)



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.


Sometimes DATACLAS=dataclass can help. So, you can use 
LIKE=ORIGINAL.CLUSTER,DATACLAS=NOREUSE,SPACE=(CYL,(10,10))



--
Radoslaw Skorupka
Lodz, Poland




==


   --
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.plsąd Rejonowy dla m. st. Warszawy XII 
Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców 
KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2018 r. kapitał 
zakładowy mBanku S.A. (w całości wpłacony) wynosi 169.248.488 złotych.
   


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-11 Thread Steve Smith
DISP=NEW or OLD is perfectly valid for VSAM and PDSEs.  PDSEs presumably
use some kind of hidden paging interface like LINEAR and ZFS do, but are
not VSAM.

sas

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Clark Morris
[Default] On 10 Jul 2018 15:08:00 -0700, in bit.listserv.ibm-main
t...@vse2pdf.com (Tony Thigpen) wrote:

>So, DISP=SHR is not the default, as I thought was implied by John's 
>statement that "Z/os VSAM is always accessed as DISP=SHR."

Not only that but I have accessed VSAM DISP=OLD when I wanted
exclusive access.  Normallypeople let the share options rule.

Clark Morris
>
>Tony Thigpen
>
>Gibney, Dave wrote on 07/10/2018 05:49 PM:
>> If DISP=SHR (that is if not DISP is provided), then the JCL Default of 
>> (NEW,PASS) would happen and the job would fail
>> 
>>> -Original Message-
>>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
>>> On Behalf Of Tony Thigpen
>>> Sent: Tuesday, July 10, 2018 2:43 PM
>>> To: IBM-MAIN@LISTSERV.UA.EDU
>>> Subject: Re: z/OS JCl vs. VSE JCL: VSAM files
>>>
>>> Then, why does every VSAM DD for every z/OS site I have worked with,
>>> always include DISP=SHR?
>>> (I guess, because it's a habit from non-VSAM files and nobody told them they
>>> did not have to do it.)
>>>
>>> Tony Thigpen
>>>
>>> John Clifford wrote on 07/10/2018 04:16 PM:
>>>> Z/os VSAM is always accessed as  DISP=SHR.
>>>
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions, send email 
>>> to
>>> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> 
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Hobart Spitz
John wrote:
>it is not the default but is the only correct way to access a vsam file.
>disp=shr,dsn=.vsam (possible bufno,bufni,...etc)
Does any one know it that also applies to PDSEs?  AFAIK, they are VSAM
datasets.

OREXXMan
JCL is the buggy whip of 21st century computing.  Stabilize it.
Put Pipelines in the z/OS base.  Would you rather process data one
character at a time (Unix/C style), or one record at a time?
IBM has been looking for an HLL for program products; REXX is that language.

On Tue, Jul 10, 2018 at 6:33 PM, John Clifford  wrote:

> it is not the default but is the only correct way to access a vsam file.
> disp=shr,dsn=.vsam (possible bufno,bufni,...etc)
>
> Never disp=new or delete.   Disp=old can be used if you need to make sure
> you are the only one accessing the file but if it is open in CICS it will
> hang.
>
> On Tue, Jul 10, 2018 at 6:07 PM, Tony Thigpen  wrote:
>
> > So, DISP=SHR is not the default, as I thought was implied by John's
> > statement that "Z/os VSAM is always accessed as DISP=SHR."
> >
> > Tony Thigpen
> >
> > Gibney, Dave wrote on 07/10/2018 05:49 PM:
> >
> >> If DISP=SHR (that is if not DISP is provided), then the JCL Default of
> >> (NEW,PASS) would happen and the job would fail
> >>
> >> -Original Message-
> >>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> >>> On Behalf Of Tony Thigpen
> >>> Sent: Tuesday, July 10, 2018 2:43 PM
> >>> To: IBM-MAIN@LISTSERV.UA.EDU
> >>> Subject: Re: z/OS JCl vs. VSE JCL: VSAM files
> >>>
> >>> Then, why does every VSAM DD for every z/OS site I have worked with,
> >>> always include DISP=SHR?
> >>> (I guess, because it's a habit from non-VSAM files and nobody told them
> >>> they
> >>> did not have to do it.)
> >>>
> >>> Tony Thigpen
> >>>
> >>> John Clifford wrote on 07/10/2018 04:16 PM:
> >>>
> >>>> Z/os VSAM is always accessed as  DISP=SHR.
> >>>>
> >>>
> >>> --
> >>> For IBM-MAIN subscribe / signoff / archive access instructions, send
> >>> email to
> >>> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >>>
> >>
> >> --
> >> For IBM-MAIN subscribe / signoff / archive access instructions,
> >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >>
> >>
> >>
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread John Clifford
it is not the default but is the only correct way to access a vsam file.
disp=shr,dsn=.vsam (possible bufno,bufni,...etc)

Never disp=new or delete.   Disp=old can be used if you need to make sure
you are the only one accessing the file but if it is open in CICS it will
hang.

On Tue, Jul 10, 2018 at 6:07 PM, Tony Thigpen  wrote:

> So, DISP=SHR is not the default, as I thought was implied by John's
> statement that "Z/os VSAM is always accessed as DISP=SHR."
>
> Tony Thigpen
>
> Gibney, Dave wrote on 07/10/2018 05:49 PM:
>
>> If DISP=SHR (that is if not DISP is provided), then the JCL Default of
>> (NEW,PASS) would happen and the job would fail
>>
>> -Original Message-
>>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
>>> On Behalf Of Tony Thigpen
>>> Sent: Tuesday, July 10, 2018 2:43 PM
>>> To: IBM-MAIN@LISTSERV.UA.EDU
>>> Subject: Re: z/OS JCl vs. VSE JCL: VSAM files
>>>
>>> Then, why does every VSAM DD for every z/OS site I have worked with,
>>> always include DISP=SHR?
>>> (I guess, because it's a habit from non-VSAM files and nobody told them
>>> they
>>> did not have to do it.)
>>>
>>> Tony Thigpen
>>>
>>> John Clifford wrote on 07/10/2018 04:16 PM:
>>>
>>>> Z/os VSAM is always accessed as  DISP=SHR.
>>>>
>>>
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions, send
>>> email to
>>> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>>
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>>
>>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Gibney, Dave
Actually, I think that inside VSAM, what is specified via SHAREOPTIONS would 
override any JCL. But, you need to get past the JCL during allocation before 
VSAM can take over.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Tony Thigpen
> Sent: Tuesday, July 10, 2018 3:08 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: z/OS JCl vs. VSE JCL: VSAM files
> 
> So, DISP=SHR is not the default, as I thought was implied by John's statement
> that "Z/os VSAM is always accessed as DISP=SHR."
> 
> Tony Thigpen
> 
> Gibney, Dave wrote on 07/10/2018 05:49 PM:
> > If DISP=SHR (that is if not DISP is provided), then the JCL Default of
> > (NEW,PASS) would happen and the job would fail
> >
> >> -Original Message-
> >> From: IBM Mainframe Discussion List [mailto:IBM-
> m...@listserv.ua.edu]
> >> On Behalf Of Tony Thigpen
> >> Sent: Tuesday, July 10, 2018 2:43 PM
> >> To: IBM-MAIN@LISTSERV.UA.EDU
> >> Subject: Re: z/OS JCl vs. VSE JCL: VSAM files
> >>
> >> Then, why does every VSAM DD for every z/OS site I have worked with,
> >> always include DISP=SHR?
> >> (I guess, because it's a habit from non-VSAM files and nobody told
> >> them they did not have to do it.)
> >>
> >> Tony Thigpen
> >>
> >> John Clifford wrote on 07/10/2018 04:16 PM:
> >>> Z/os VSAM is always accessed as  DISP=SHR.
> >>
> >> -
> >> - For IBM-MAIN subscribe / signoff / archive access instructions,
> >> send email to lists...@listserv.ua.edu with the message: INFO
> >> IBM-MAIN
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> >
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Gibney, Dave
My memory was wrong on normal termination. I rarely use DISP defaults. I would 
expect you are correct for the MOD instance

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Paul Gilmartin
> Sent: Tuesday, July 10, 2018 3:07 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: z/OS JCl vs. VSE JCL: VSAM files
> 
> On Tue, 10 Jul 2018 21:49:47 +, Gibney, Dave wrote:
> 
> >If DISP=SHR (that is if not DISP is provided), then the JCL Default of
> >(NEW,PASS) would happen and the job would fail
> >
> From the JCL Ref.
> Defaults
> v If you omit the status subparameter, the default is NEW.
> v If you omit the normal termination disposition subparameter, the default
> is
>   DELETE for a NEW data set or KEEP for an existing data set.
> 
> Hmmm.  Does this mean that fmr status MOD the data set will be deleted if
> allocation created it but kept if it existed beforehand?
> 
> -- gil
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Tony Thigpen
So, DISP=SHR is not the default, as I thought was implied by John's 
statement that "Z/os VSAM is always accessed as DISP=SHR."


Tony Thigpen

Gibney, Dave wrote on 07/10/2018 05:49 PM:

If DISP=SHR (that is if not DISP is provided), then the JCL Default of 
(NEW,PASS) would happen and the job would fail


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Tony Thigpen
Sent: Tuesday, July 10, 2018 2:43 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: z/OS JCl vs. VSE JCL: VSAM files

Then, why does every VSAM DD for every z/OS site I have worked with,
always include DISP=SHR?
(I guess, because it's a habit from non-VSAM files and nobody told them they
did not have to do it.)

Tony Thigpen

John Clifford wrote on 07/10/2018 04:16 PM:

Z/os VSAM is always accessed as  DISP=SHR.


--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Paul Gilmartin
On Tue, 10 Jul 2018 21:49:47 +, Gibney, Dave wrote:

>If DISP=SHR (that is if not DISP is provided), then the JCL Default of 
>(NEW,PASS) would happen and the job would fail
> 
From the JCL Ref.
Defaults
v If you omit the status subparameter, the default is NEW.
v If you omit the normal termination disposition subparameter, the default 
is
  DELETE for a NEW data set or KEEP for an existing data set.

Hmmm.  Does this mean that fmr status MOD the data set will be deleted if 
allocation
created it but kept if it existed beforehand?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Tony Thigpen
On z/VSE, there is not a LIKE option in the DLBL card. We must use 
IDCAMS DEFINE with MODEL(other file name) to get the same results as LIKE.


Tony Thigpen

Farley, Peter x23353 wrote on 07/10/2018 04:05 PM:


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



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Tony Thigpen

For normal z/VSE VSAM:
1) you can use DISP=NEW, which resets the High RBA at open if the file 
is defined with REUSE.
2) you can use DISP=DELETE, which resets the High RBA at close if the 
file is defined as REUSE. (note: Space is not released.)
3) with very limited exceptions, you always use IDCAMS to define or 
delete the VSAM file.

4) the default is DISP=(OLD,KEEP,KEEP) is the default.

The limited exception mentioned is when using "VSAM managed SAM files". 
You don't have these on z/OS. (AFAIK) I will discuss them after I 
discuss regular non-VSAM files.


So, for most situations, DISP= is not specified on the z/VSE DLBL card.

Tony Thigpen

Wayne Bickerdike wrote on 07/10/2018 03:52 PM:

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




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Gibney, Dave
If DISP=SHR (that is if not DISP is provided), then the JCL Default of 
(NEW,PASS) would happen and the job would fail

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Tony Thigpen
> Sent: Tuesday, July 10, 2018 2:43 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: z/OS JCl vs. VSE JCL: VSAM files
> 
> Then, why does every VSAM DD for every z/OS site I have worked with,
> always include DISP=SHR?
> (I guess, because it's a habit from non-VSAM files and nobody told them they
> did not have to do it.)
> 
> Tony Thigpen
> 
> John Clifford wrote on 07/10/2018 04:16 PM:
> > Z/os VSAM is always accessed as  DISP=SHR.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Tony Thigpen
Then, why does every VSAM DD for every z/OS site I have worked with, 
always include DISP=SHR?
(I guess, because it's a habit from non-VSAM files and nobody told them 
they did not have to do it.)


Tony Thigpen

John Clifford wrote on 07/10/2018 04:16 PM:

Z/os VSAM is always accessed as  DISP=SHR.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread John Clifford
Z/os VSAM is always accessed as  DISP=SHR.

On Tue, Jul 10, 2018 at 3:52 PM, Wayne Bickerdike  wrote:

> *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
> <000433f07816-dmarc-requ...@listserv.ua.edu
> <000433f07816-dmarc-requ...@listserv.ua.edu>> 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 *
> >
> >
> >
> >
> > * --
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> email
> > to lists...@listserv.ua.edu  with the message:
> > INFO IBM-MAIN *
> >
>
>
>
> 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.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Farley, Peter x23353
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Wayne Bickerdike
Sent: Tuesday, July 10, 2018 3:52 PM
To: IBM-MAIN@LISTSERV.UA.EDU
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
<000433f07816-dmarc-requ...@listserv.ua.edu
<000433f07816-dmarc-requ...@listserv.ua.edu>> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Wayne Bickerdike
*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
<000433f07816-dmarc-requ...@listserv.ua.edu
<000433f07816-dmarc-requ...@listserv.ua.edu>> 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 *
>
>
>
>
> * --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to lists...@listserv.ua.edu  with the message:
> INFO IBM-MAIN *
>



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.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: z/OS JCl vs. VSE JCL: VSAM files

2018-07-10 Thread Paul Gilmartin
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:
>// DLBLTEITEST,'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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN