RE: How to tell if an object is in use? -- MIDRANGE-L

Hiya

The pesky lock issues are now transferred to the period when the RGZPFM has to be run - potentially a much longer period of time and more of a pain to deal with. If you use a soft delete as suggested, then alter the file to REUSDLT (presuming you can) and thereby eliminate the RGZPFM and another potential lock conflict.

With respect to the original problem, if the user has just left the screen on, why is the object locked ?

Perhaps altering the maintenance program so the record/object is only locked when an update is actually occurring rather than locking the file when the procedure is entered might be a better way to go

Apologies if this is not what is happening, it's just what it sounds like :)

Regards
Evan Harris

Greg - have you considered handling this using a completely different
method?

After the pgm processes each record in the batch file, mark the record as
deleted (either change a flag value to "D", or actually delete the record).
(I would recommend changing a flag value so you can easily view deleted
records).

Later during the nightly or weekly maintenance runs, when the interactive
system is down, purge the deleted records using a program and/or SQL and
RGZPFM.

Then you will never see those pesky lock issues!!


-----Original Message-----
From: Greg Wenzloff [mailto:GWenzloff@xxxxxxxxxxx]
Sent: Wednesday, February 09, 2005 8:45 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: How to tell if an object is in use?


I have a CLP that will process a file in batch then delete it.   Sometimes a
user first performs maintenance on the file but fails to exit the
maintenance program leaving the file locked.    The CLP which runs in batch
then hangs.

I put the following code in the program that is about to submit the batch
job:

/* SOMETIMES USERS ARE IN MAINTENANCE IN ANOTHER SESSION */
        ALCOBJ OBJ((&FILEE *FILE *EXCL *FIRST)) WAIT(5)
        MONMSG MSGID(CPF0000) EXEC(DO)
                <<< send the user a message to get out of the file  >>>>
                ENDDO
        DLCOBJ     OBJ((&FILEE *FILE *EXCL *FIRST))

This ALCOBJ/DLCOBJ does not seem very elegant.   Is there a better way to
tell if an object is being used by someone?

Thanks,
Greg