DSENQSHR on the job card. Tried that too. Didn't work. Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&[email protected] On Tuesday, February 18th, 2025 at 1:54 PM, Allan Staller <[email protected]> wrote: > Classification: Confidential > > There was an option added in one of the recent z/OS releases to "downgrade > the enque" > e.g. step1 "creates" the dataset with an exclusive enque. Once the need for > exclusive control has been satisfied, the enque gets downgraded to shared. > > I don't remember the exact language, but that ius the gist of it. > > HTH, > > -----Original Message----- > From: IBM Mainframe Discussion List [email protected] On Behalf Of > Mark Jacobs > > Sent: Tuesday, February 18, 2025 12:47 PM > To: [email protected] > Subject: Re: Enqueue Question > > [CAUTION: This Email is from outside the Organization. Unless you trust the > sender, Don't click links or open attachments as it may be a Phishing email, > which can steal your Information and compromise your Computer.] > > I tried that. Didn't work. > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get&[email protected] > > > > > On Tuesday, February 18th, 2025 at 1:41 PM, Charles Mills [email protected] > wrote: > > > I am surprised that would fail but I don't know SVC 99 well enough to say > > "no, that's wrong." > > > > Seeing as the job is set up with the dataset already "hard coded" in Step 2 > > -- why not allocate it with JCL in Step 1? > > > > If you do that would the SVC 99 then succeed (so you would not have to > > change your code)? I don't know. > > > > Charles > > > > On Tue, 18 Feb 2025 18:29:37 +0000, Mark Jacobs [email protected] > > wrote: > > > > > I have a two step job. Step 1 attempts to perform a dynamic allocation of > > > a dataset. It's failing since step 2 allocates the dataset DISP=SHR, and > > > the enqueue is already created before the dynamic allocation is attempted. > > > > > > Is there anyway around this problem? > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN > ::DISCLAIMER:: > ________________________________ > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses > in transmission. The e mail and its contents (with or without referred > errors) shall therefore not attach any liability on the originator or HCL or > its affiliates. Views or opinions, if any, presented in this email are solely > those of the author and may not necessarily reflect the views or opinions of > HCL or its affiliates. Any form of reproduction, dissemination, copying, > disclosure, modification, distribution and / or publication of this message > without the prior written consent of authorized representative of HCL is > strictly prohibited. If you have received this email in error please delete > it and notify the sender immediately. Before opening any email and/or > attachments, please check them for viruses and other defects. > ________________________________ > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
