On Wed, 13 Oct 2021 10:24:06 -0400, David Spiegel wrote:
>I agree with your hypothesis ... the PAX fails because it cannot get an
>Exclusive ENQ on MY.PAX
>
>With respect to the spawned (PAX) Address Space, though, it is possible
>that the spawn itself could take longer than the Batch Job switching
>steps and defeat the entire purpose.
>
I consider that unlikely, but I call few things impossible when others have
suggested them earlier in the thread.
>I think coding a SLEEP (or equivalent) in the TSO input could prevent this.
>
I'll suggest:
//SYSTSIN DD. *
call *(BPXWDYN) 'alloc dd(sysut1) dsn(''my.pax'') shr reuse msg(WTP)'
call *(BPXBATCH)
call *(BPXWDYN) 'alloc dd(sysut1) dsn(''my.pax'') shr reuse msg(WTP)'
...
I've found that BPXWDYN( ... msg(WTP)) gives the best diagnostics.
<https://www.ibm.com/docs/en/zos/2.5.0?topic=services-bpxwdyn-text-interface-dynamic-allocation-dynamic-output>
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
