Re: Allocating a *PGM object

Luis, the logic of getting an excusive lock on an object
to control access to a program works by changing
the CL to attempt to obtain the lock on some object
in the system - any object at all - that you a) know will
exist and b) know will only be locked by the process
you are trying to control.  Therefore, while creating
a data area works, it is just one more thing to maintain.
You can lock the program instead because a) you know
it exists and b) it will only be locked by this process.

Locking the program in and of itself does not prevent use, 
but then neither does locking some random data area.

Just think of the program object has a handy thing to
put the lock on.


>>> luisrodriguez@xxxxxxxxxxx 10/26/2005 8:14:15 AM >>>
Jeff,

Thanks for your message. As per the manual (Infamous Center...):

..."When ALCOBJ is executed to get an EXCL lock on a program (*PGM),
only the program object description is locked. The program code is not
locked exclusively. Therefore, the program may still be run by another
user. Changes are not allowed for the program object description while
the actual program can still be used."

I have received (off-site) the idea of creating a *DTAARA in the
process
that I'm trying to protect and trying to lock it. That should work (I
hope :-) )

Thanks again for your help,

Luis Rodriguez