Re: Lock on command processing program ignored

Learn something new every day--I'd've thought that an exclusive lock
would mean no access, but apparently you can still USE a program that is
locked. It's not an authorization thing.

I'll probably still lock the program in the validity checker--if can't
lock it, then drop out.

Still, this is interesting.

Thanks to all.

Dan Bale wrote:
>
> I have tried this before with the results you're getting.  ALCOBJ *EXCL does
> not work on program objects per your usage.  To do what you are trying to
> accomplish, you'll need to lock on to something that will "lock" (like a
> file, does the program use a device file that only that program uses?)
>
> - Dan Bale
>
> > >I want to have only one job runa program at a time. CL Programming
> > >suggests ALCOBJ *EXCL on the program object. In this case, it's a
> > >command processing program that I want to restrict. Calling it directly,
> > >or trying to debug, fail. However, another job can run it through the
> > >command. Is this normal? Is there a way around it?
>
>
--
Vern Hamberg

Would you like to see a challenging little arithmetic puzzle
that might get you or your kids or grandkids more interested
in math? Go to <http://cgi.wff-n-proof.com/MSQ-Ind/I-1E.htm>

Sillygism--

Something is better than nothing.
Nothing is better than a ham sandwich.
Ergo
Something is better than a ham sandwich.