RE: ALCOBJ *DTAARA & In *Lock in RPG in same job?

The problem of ensuring only one instance of the job running is a common
one. The solution that I have finally decided works the best is to create a
data area with the same name as the job and lock it in my CL. You can even
go one step further and have your C/L program put the job name, user ID, job
number, starting and ending times, etc in the data area for easy reference
later. 

Albert York                          
        

        At 07:57 AM 9/5/2003 -0700, you wrote:
        >This seemed logical to do, but am getting RNX0432 "*LOCK for data
area
        >STUJRNEPRA was not granted" after (in the CL program):
        >1) ALCOBJ OBJ((PRQJRN/PRJRNEPRA *DTAARA *EXCLRD)) WAIT(3)
        >2) called RPG-IV program does an IN *LOCK on this data area so that
I can
        >update it on the OUT op.
        >
        >The reason for the ALCOBJ is that I want to ensure that there is
only one
        >job running this program at any given time.  I am not using any
files, so
        >I can't allocate that.  And I don't want to set an Active/Inactive
status
        >flag in the data area to make the determination of whether this is
running
        >elsewhere in the system, because this NEP job will be subject to
being
        >ended via ENDJOB, ENDSBS, PWRDWNSYS, etc.
        >
        >Since I was allocating the data area, I tried taking out the *Lock
from
        >the In statement, but I got a runtime error when the Out statement
tried
        >to update the data area.
        >
        >Advice / suggestions welcomed.
        >
        >GA


        _______________________________________________
        This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
        To post a message email: MIDRANGE-L@xxxxxxxxxxxx
        To subscribe, unsubscribe, or change list options,
        visit: http://lists.midrange.com/mailman/listinfo/midrange-l
        or email: MIDRANGE-L-request@xxxxxxxxxxxx
        Before posting, please take a moment to review the archives
        at http://archive.midrange.com/midrange-l.