Re: DspPgmRef locks objects at *SHRNUP; need to change wait time

Hi Dan -

>Date: Tue, 2 Nov 1999 17:48:24 -0500
>From: "Dan Bale" <dbale@genfast.com>
>Subject: DspPgmRef locks objects at *SHRNUP; need to change wait time
>
>I've got a program cross-reference utility that uses DSPPGMREF to produce an
>outfile.  This morning, the utility hung for a few minutes due to the fact that
>certain applications in a given library were in use and locked with *EXCLRD.
>DSPPGMREF apparently needs to lock objects it interrogates at *SHRNUP (as
>opposed to *SHRRD, which I think would have avoided the problem).
>
>The job log shows that the command waits up to 30 seconds per object.  Not too
>bad if there's only a few objects, but tends to tie up the job queue if there's
>a lot of them.  How can I change the time DSPPGMREF waits for an object from 30
>seconds to, say 1 second, in this utility ONLY?  I.e., I don't want to change
>anything on the program objects.  Would I have more options if I switched to
>using an API?

I don't know about using an API.  You can change the default wait time for
the JOB to 1 second with CHGJOB JOB(*) DFTWAIT(1).  Some internal functions
do not honor the job's wait time, but since this looks like a standard object
lock it should work.

If you need to, you can retrieve the wait time with RTVJOBA, change it to
1 second, do your processing, then change it back to the original wait time
afterward.  Since it sounds like this is a standalone batch job, that probably
isn't necessary.

Ken
Southern Wine and Spirits of Nevada, Inc.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---