Your developers might be correct but bugs happen. You may find some program is not performing a commit as expected.
One thing you can do is journal the physical file to capture what is occurring to the PF. Then you can interrogate the journal entries. I suggest including the following in the fixed length portion of the journal entries.
*JOB (provides job name, job user and job number)
*USR (provides the effective user profile, also known as current user)
*PGM (provides the name of the program that handled the database record)
*PGMLIB (provides the library the program resided in)
*RMTADR (provides the IP address for the client using the program)
Using journal code R (Record level operations) you can track the following events (entry codes) that occur to your database.
BR - Before-image of record updated for rollback
DL - Record deleted from physical file member
DR - Record deleted for rollback
IL - Increment record limit
PT - Record added to physical file member
PX - Record added directly to physical file member
UB - Before-image of record updated in physical file member
UP - After-image of record updated in physical file member
UR - After-image of record updated for rollback
You could always try STRDBMON as well but my opinion is journaling the PF will get you where you want to go more efficiently.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Piotrowski
Sent: Thursday, September 13, 2012 10:47 AM
To: Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx)
Subject: Tracing Physicial File R/W Actions
We have a physical file that we are having problems retaining data. For some reason, data is being written to the system, but at random times it will delete a random amount of records.
All of the programmers swear that it's nothing they have created that is deleting the records. So with that said, is there any type of a trace/audit that would show me all of the read/writes performed on a physical file?
We tried to set up a monitor in Navigator, but it doesn't appear to have worked. Anybody else have a clue on how to track changes in a PF?
Assistant Mgr. - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Please consider the environment. Don't print this e-mail unless you really need to.
The information contained in this communication is confidential and intended only for the use of those to whom it is addressed. If you have received this communication in error, please notify me by telephone (collect if necessary) and delete or destroy any copies of it. Thank you!
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l