So the option of listing datasets, then calling a batch job with DISP=OLD in the last step also means that there's a gap between the submit and the dataset listing. Since I did the listing and "alloc fi(Fn) old" part in REXX, it's only held as long as the REXX runs. I may end up having to wrap the REXX around the entire transfer so that the dataset enqueues are held till the end of the transfer.
– Vignesh Mainframe Infrastructure -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Sankaranarayanan, Vignesh Sent: Friday, June 24, 2016 8:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dynamic enqueue creation Hello Walt and Paul, Thanks for your ideas. This is to cope with MQ FTE's "feature" of not locking datasets for the duration of a transfer. Using ANT scripts to initiate a transfer of a list of datasets that resolve to a wildcard, we've found that in the time gap between the initial resolve of the wildcard and the transfer of datasets found in the wildcard, those datasets are processed by some other entity, leaving the MQ FTE step to fail saying dataset deleted (already processed). There's the outcome=defer option in the ANT script but I don't believe it has led to the job to stay active until the MQ FTE transfer completes fully. – Vignesh Mainframe Infrastructure -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Friday, June 24, 2016 8:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dynamic enqueue creation On Fri, 24 Jun 2016 08:55:20 -0500, Walt Farrell wrote: >On Fri, 24 Jun 2016 07:09:19 +0000, Sankaranarayanan, Vignesh wrote: >> >>I'm looking to retrieve a list of datasets falling under a wildcard and then >>creating an OLD enqueue on those datasets. > >That sounds like a good way to get a list of the data sets, but I'm a bit >concerned about your plans to allocate them. > >First, your TSO allocate commands will fail if anyone else has the data set >allocated already. That may cause unexpected issues for you later. > >Second, it's not clear what the rest of the job will be doing with those data >sets. Depending on what it's doing, and whether the processing is in the same >jobstep as your allocations, various error scenarios may occur. So I think you >should describe your job layout and the processing it's going to do in greater >detail. > Ignoring the question of intent, the list might be used to create JCL for a batch job with a final step, PGM=IEFBR14,COND=(0,LE), with DD DISP=OLD for each data set in the list. All earlier steps will be under ENQ EXC for those DSNs but the allocations will never be performed. JES3 setup might complicate matters. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN MARKSANDSPENCER.COM ________________________________ Unless otherwise stated above: Marks and Spencer plc Registered Office: Waterside House 35 North Wharf Road London W2 1NW Registered No. 214436 in England and Wales. Telephone (020) 7935 4422 Facsimile (020) 7487 2670 www.marksandspencer.com Please note that electronic mail may be monitored. This e-mail is confidential. If you received it by mistake, please let us know and then delete it from your system; you should not copy, disclose, or distribute its contents to anyone nor act in reliance on this e-mail, as this is prohibited and may be unlawful. ---------------------------------------------------------------------- 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
