Re: Dataset contention

2021-03-31 Thread Joseph Reichman
> to process this data for /months/. > > I would have expected him to finesse the algorithms, handling dataset > contention etc on test data, or possibly just a handful of examples of > live data - and as you say, I'd have hoped that that would have been > anonymised. > > &

Re: Dataset contention

2021-03-31 Thread Jeremy Nicoll
ns about ways to process this data for /months/. I would have expected him to finesse the algorithms, handling dataset contention etc on test data, or possibly just a handful of examples of live data - and as you say, I'd have hoped that that would have been anonymised. > I deal with very large quan

Re: Dataset contention

2021-03-27 Thread Peter Relson
I have a dataset that is allocated to multiple jobs but with a disp=shr And I am getting contention messages MIM1039I I was always under the impression That if the dataset was allocated with disp=shr I have to believe that MIM would not issue a contention message if all the allocations were

Re: Dataset contention

2021-03-26 Thread Farley, Peter x23353
ave a lot to do with how hard that is to do. Peter -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Friday, March 26, 2021 6:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dataset contention There are both legal and operational issues with progra

Re: Dataset contention

2021-03-26 Thread Seymour J Metz
:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dataset contention Jeremy, I have to disagree with you here about access to read (not modify) production data by application developers. Full read access to production data (especially when the quantities are very large and cannot easily be copied

Re: Dataset contention

2021-03-26 Thread Joseph Reichman
their non-production tools and libraries while using > the production data. I have never seen such a process that actually works > when time is of the essence (e.g., a serious production-stopping issue). > > Peter > > -Original Message- > From: IBM Mainframe Discussi

Re: Dataset contention

2021-03-26 Thread Farley, Peter x23353
Message- From: IBM Mainframe Discussion List On Behalf Of Jeremy Nicoll Sent: Friday, March 26, 2021 11:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dataset contention > if it’s > corrupted I can run it again it won’t happen and like I said it’s not > production if it was that

Re: Dataset contention

2021-03-26 Thread PINION, RICHARD W.
You are welcome Joe! -Original Message- From: IBM Mainframe Discussion List On Behalf Of Joseph Reichman Sent: Friday, March 26, 2021 12:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dataset contention [External Email. Exercise caution when clicking links or opening attachments

Re: Dataset contention

2021-03-26 Thread Paul Gilmartin
On Fri, 26 Mar 2021 15:17:06 +, Jeremy Nicoll wrote: >On Fri, 26 Mar 2021, at 14:06, Joseph Reichman wrote: >> I open the file extend >What? Perhaps Python jargon. "append"? "DISP=MOD"? >... >> number of files on the off chance that 2 jobs write to the duke >Duke? Duplicate? >Surely

Re: Dataset contention

2021-03-26 Thread Joseph Reichman
Richard was the one who resolved by problem I allocated the datasets in rexx and did a submit The contention was between the batch jobs and my TSO session IKJEFT01 When I did the FREE FI problem was resolved Thank you Richard > On Mar 26, 2021, at 11:18 AM, Jeremy Nicoll > wrote: > >

Re: Dataset contention

2021-03-26 Thread Jeremy Nicoll
On Fri, 26 Mar 2021, at 14:06, Joseph Reichman wrote: > I open the file extend What? > I have been tasked with finding data there are > certain cases that are not easily found so I have to search a large > number of files on the off chance that 2 jobs write to the duke Duke? You seem to

Re: Dataset contention

2021-03-26 Thread Joseph Reichman
I open the file extend I have been tasked with finding data there are certain cases that are not easily found so I have to search a large number of files on the off chance that 2 jobs write to the duke if it’s corrupted I can run it again it won’t happen and like I said it’s not production if

Re: Dataset contention

2021-03-26 Thread Paul Gilmartin
On Fri, 26 Mar 2021 09:21:59 -0400, Joseph Reichman wrote: >The chances of two jobs writing to the file are slim and none I am searching >a large number of files because I cannot find the data > https://en.wikipedia.org/wiki/Murphy%27s_law > And most importantly it is NOT a production job > It

Re: Dataset contention

2021-03-26 Thread Joseph Reichman
, March 26, 2021 9:13 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dataset contention On Fri, 26 Mar 2021, at 12:38, Joseph Reichman wrote: > The output file is shared among multiple jobs whenever I get an equal > condition I open put and close That won't work if two jobs simultaneous

Re: Dataset contention

2021-03-26 Thread Jeremy Nicoll
On Fri, 26 Mar 2021, at 12:38, Joseph Reichman wrote: > The output file is shared among multiple jobs whenever I get > an equal condition I open put and close That won't work if two jobs simultaneously try to write to the file. You might not destroy the file, but you will lose the information

Re: Dataset contention

2021-03-26 Thread Joseph Reichman
Richard Thank you I see 2 jobs running now without contention messages > On Mar 26, 2021, at 8:38 AM, Joseph Reichman wrote: > > I am doing a file search over 2000 files looking for specfic data since > there are so > Many files I broke them up in to multiple > Jobs > The rexx exec

Re: Dataset contention

2021-03-26 Thread Joseph Reichman
I am doing a file search over 2000 files looking for specfic data since there are so Many files I broke them up in to multiple Jobs The rexx exec calls the catalog search program IGGCSI00 for the input files They are VB files The output file is shared among multiple jobs whenever I get an

Re: Dataset contention

2021-03-26 Thread Jeremy Nicoll
On Fri, 26 Mar 2021, at 12:07, Joseph Reichman wrote: > I have a dataset that is allocated to multiple jobs but with a disp=shr > > And I am getting contention messages MIM1039I I was always under the > impression > That if the dataset was allocated with disp=shr > It could be used among

Re: Dataset contention

2021-03-26 Thread Joseph Reichman
: IBM-MAIN@LISTSERV.UA.EDU > Subject: Dataset contention > > [External Email. Exercise caution when clicking links or opening attachments.] > > Hi > > I have a dataset that is allocated to multiple jobs but with a disp=shr > > And I am getting contention messages MI

Re: Dataset contention

2021-03-26 Thread PINION, RICHARD W.
, March 26, 2021 8:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Dataset contention [External Email. Exercise caution when clicking links or opening attachments.] Hi I have a dataset that is allocated to multiple jobs but with a disp=shr And I am getting contention messages MIM1039I I was always

Dataset contention

2021-03-26 Thread Joseph Reichman
Hi I have a dataset that is allocated to multiple jobs but with a disp=shr And I am getting contention messages MIM1039I I was always under the impression That if the dataset was allocated with disp=shr It could be used among multiple jobs Without problems Thanks