RE: Lock on command processing program ignored

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

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Vernon Hamberg
Sent: Wednesday, February 13, 2002 2:15 PM
To: midrange-l@midrange.com
Subject: Re: Lock on command processing program ignored


This is our own command and program. I want to make sure only one job
can run it at a time.

There are no messages coming out in the joblog.

I will be trying an ALCOBJ *EXCL in the validity checker. I'm just
curious as to why a locked-exclusive CPP can still be used.

Evan Harris wrote:
>
> Vern
>
> any reason why wrapping the command in a CL (or RPG for that matter) is
not
> an option ? Then you could just lock the program you are calling.
>
> It seems to me that locking a CPP might be dangerous (for some reason I am
> getting the impression you are talking about an IBM CPP) as depending on
> the command the program could be in use elsewhere which might or might not
> cause unpredictable results - it might even be exactly what you want :).
>
> As to why it fails, an error message or some code showing what is
happening
> might help suggest an answer.
>
> Regards
> Evan Harris
>
> >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?