What FP LOCK ACTV event means ?

The ATF event "FP LOCK ACTV" corresponds to IMS Monitor event SLOG 95 "FP LOCK ACTIVITY" which means an attempt to lock a DEDB resource,regardless of contentions and whether actual DB updates were made or not. If there is a contention then a "DEDB LOCK IWAIT" (SLOG 68/69) is issued. This is the event you should be looking at. ATF shows the DBD and area names associated with it. If you have two IMS transactions xxxx and yyyy update the same DB, and xxxx had no "DEDB LOCK IWAIT" events,we can tell that xxxx was holding the lock and yyyy waited for it to be released. If xxxx and yyyy update different DB then some other transactions may be involved. If those other transactions run on the same IMS, you can use the ATFL screen to filter trace results by DBD name to see all transactions that accessed that DB within the given time window, then zoom to ATVW/ATVD and see which ones show a "DEDB LOCK IWAIT" against that DB and which ones do not.

The "FP LOCK ACTV" is timestamped when the corresponding IMS internal block is dequeued and passed on to ATF as an IMS Monitor event. These blocks are enqueued and dequeued by IMS, so this timestamp value is always somewhat later than the actual lock attempt. Also, the actual sequence of all events combined between ATF and IMS log is not necessarily in the precise chronological order of timestamps. This is because ATF collects data from IMS Monitor events. These events are generated and timestamped by various IMS tasks asynchronously and independently from the IMS tasks that create and timestamp the log records.