One of the things I'm going to test is whether setting S99NORES in S99FLAG2 might work. If so all we need to do is convince the software vendor to support setting it on a job-by-job basis.
Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&[email protected] On Wednesday, February 19th, 2025 at 3:13 AM, Jack Zukt <[email protected]> wrote: > Hi > I had a similar problem awhile ago. The only way that I could find to > overcome it was making it a two job solution. The first job creates it and > the second job uses it. Two jobs in the same PDS member using the same > jobname. When I scheduled it the jobnames were different but with > dependencies. I did like the solution but could not figure out a better > one. > Regards > Jack > > On Wed, Feb 19, 2025, 01:03 Mark Jacobs < > [email protected]> wrote: > > > No. I can do that tomorrow. I just wanted to test whether step 2 was the > > root cause of the enqueue being active during the execution of step 1. > > > > 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 7:58 PM, Paul Gilmartin < > > [email protected]> wrote: > > > > > On Tue, 18 Feb 2025 23:28:24 +0000, Mark Jacobs wrote: > > > > > > > True, but not in the test case I used to verify that the problem > > > > exists in the simplest way I could think of. > > > > > > > > Step 1. A user written program that issues the wait SVC without the > > > > ECB ever being posted. > > > > Step 2. PGM=IEFBR14 with a dataset allocated DISP=SHR > > > > > > > > A D GRS command verified that the enqueue was held by this job while > > > > it was waiting in step 1. > > > > > > Did your test Step 1 reproduce the problem by issuing a DYNALLOC > > > which failed with an ENQ conflict? (You didn't say or show code.) > > > > > > -- gil > > > > > > ---------------------------------------------------------------------- > > > 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 > > > ---------------------------------------------------------------------- > 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
