record lock.

[peacealida]

hi

i have a physical file will update by multiple user and approve the record at the same time via screen.

i need to simulate a situation the record has been locked and enable to approve the record.

how can i do it?
if i use alcobj then the screen program will not run.
i am stressed out thanks plz help

[GLS400]

Re: record lock.

Hi Peacealida:
When you chain to populate your screen use the no-lock option.

/free
      chain(n) (mykey1 : mykey2) myfile ;
/end-free
or in fixed format.......
 c      myklist    chain myfile                   99
 c                 unlock myfile

When you are ready to update the file you must
1. re-chain without the nolock option
2. move the updated fields to output fields
3. then do the update.

Best of Luck
GLS

[Scott Klement]

Re: record lock.

GLS400, your fixed format example is missing the (n)

This works just the same in fixed format as it does in free format. No need to lock it and then subsequently unlock it.

[tomliotta]

Re: record lock.

When you are ready to update the file you must
1. re-chain without the nolock option
2. move the updated fields to output fields
3. then do the update.

There should usually be a step between (1) and (2) that verifies that no intervening changes have happened. If a change is detected, the logic should go through whatever resolution is appropriate, e.g., reject the current update and restart with the recently updated values.

[peacealida]

Re: record lock.

thanks for the solution.
but anyway i can simulate the locking error?

[Zdenko]

Re: record lock.

Hi

Try to allocate record using UPDDTA

[RayGilliesJones]

Re: record lock.

Write yourself a small batch program that reads the record for update (thus locking it) then waits for 10 minutes (use DLYJOB) When you've finished testing your locking code, you can kill the batch job.

[jamief]

Re: record lock.

http://www.code400.com/codepage.php?id=6

[JonBoy]

Re: record lock.

Why write a batch program? To lock the record just run the program you are testing from two different 5250 sessions and try to update the same record. Voila - record lock!

[kpandian]

Re: record lock.

Hello Peacealida,
An additional info on Record lock.

If you want to evaluate the record lock scenario, you could do that in your program logic by checking the value of file status code.
In case of RPG,
C CHAIN(E) Empfile
C IF %ERROR
C select
C when %status = 01218
C 'RecordLocked'DSPLY
....

In case of Cobol, you need to check if the value of file status is "9D" or not.

Upon validating the file status code, you can take the appropriate action.
And, if you also want to identify the JOB which is holding the lock at that moment, you may have to look into the "Error description field" of Program Data structure (i.e. SDS; positions 91 to 170).

As far as replicating the record lock scenario, the easy way is to use UPDDTA or executing the same program from another session.
Hope that helps.

[MichaelCatalani]

Re: record lock.

I've seen UPDDTA mentioned a couple of times in this thread, but I do not believe that will work. (As far as holding a record lock.) UPDDTA will not lock the record while the data is on the screen. It only locks the record for a brief time while the data is being updated.