Re: PDS Member updating via COBOL Program

2019-10-09 Thread S B
Andy  Be aware of thePDSE solution – if your shop is like mine – Shared DASD between two LPARs andnot SYSPlex – PDSE will be your nightmare as it is mine currently and it willbe even more when  Enterprise COBOL V4.2goes out of support on 09/30/2021. Going SYSPlex in our setup is doable but wil

Re: PDS Member updating via COBOL Program

2019-10-08 Thread Seymour J Metz
Mainframe Discussion List on behalf of Pesce, Andy Sent: Tuesday, October 8, 2019 12:15 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: PDS Member updating via COBOL Program I am looking for an explanation and this may be one of those "unpredictable results" may occur. I have "JOBA&q

Re: PDS Member updating via COBOL Program

2019-10-08 Thread Gibney, Dave
m: IBM Mainframe Discussion List On > Behalf Of Don Poitras > Sent: Tuesday, October 08, 2019 10:55 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: PDS Member updating via COBOL Program > > In article <2000189509316059.wa.paulgboulderaim@listserv.ua.edu> > you w

Re: PDS Member updating via COBOL Program

2019-10-08 Thread Don Poitras
In article <2000189509316059.wa.paulgboulderaim@listserv.ua.edu> you wrote: > On Tue, 8 Oct 2019 16:28:30 +, Jesse 1 Robinson wrote: > >This is a classic problem endemic to traditional PDS since the dawn of MVS. > >IBM's solution to this problem is PDSE. If you convert the data set to > >

Re: PDS Member updating via COBOL Program

2019-10-08 Thread Paul Gilmartin
On Tue, 8 Oct 2019 16:28:30 +, Jesse 1 Robinson wrote: >This is a classic problem endemic to traditional PDS since the dawn of MVS. >IBM's solution to this problem is PDSE. If you convert the data set to Library >(PDSE) you may reduce problem occurrence to negligible. OTOH PDSE may >introdu

Re: PDS Member updating via COBOL Program

2019-10-08 Thread Tabari Alexander
>PDSE data sets and members can be shared. If allocated with DISP=SHR, the >PDSE directory can be shared by multiple writers and readers, and each PDSE >member can be shared by a single writer or multiple readers. Any number of >systems can have the same PDSE open for input. If one system has a PDS

Re: PDS Member updating via COBOL Program

2019-10-08 Thread Tom Marchant
On Tue, 8 Oct 2019 16:15:38 +, Pesce, Andy wrote: >I have "JOBA" that executes a COBOL program to update a particular member in a >PDS. Within the program, it calls an internal utility that someone >wrote years ago that puts an enqueue on the dataset and its member that it is >updating. T

Re: PDS Member updating via COBOL Program

2019-10-08 Thread John McKown
On Tue, Oct 8, 2019 at 11:16 AM Pesce, Andy wrote: > I am looking for an explanation and this may be one of those > "unpredictable results" may occur. > > I have "JOBA" that executes a COBOL program to update a particular member > in a PDS. Within the program, it calls an internal utility that

Re: PDS Member updating via COBOL Program

2019-10-08 Thread Jesse 1 Robinson
A.EDU Subject: (External):PDS Member updating via COBOL Program I am looking for an explanation and this may be one of those "unpredictable results" may occur. I have "JOBA" that executes a COBOL program to update a particular member in a PDS. Within the program, it calls

PDS Member updating via COBOL Program

2019-10-08 Thread Pesce, Andy
I am looking for an explanation and this may be one of those "unpredictable results" may occur. I have "JOBA" that executes a COBOL program to update a particular member in a PDS. Within the program, it calls an internal utility that someone wrote years ago that puts an enqueue on the dataset