Doing @Lizette's job for her here <g> there is a DB2 list. Join from www.idug.org . Not criticizing you; just more DB2 experts hanging out there and perhaps better replies.
Do you have any tools like Omegamon, TMON for DB2 or anything like that which could help with this? Yes, you can turn on IFCID 61 and get the perpetrators of INSERT, DELETE and UPDATE -- but there will be some performance impact, and of course you will need some sort of reporting tool to display the data. You can "constrain" the trace on only certain tables, but the reduction in performance impact is apparently minimal. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Linda Hagedorn Sent: Friday, February 24, 2017 1:18 PM To: [email protected] Subject: OnDemand on DB2 Hi. I'm looking for help and ideas with OnDemand on DB2 on z/OS. Background: A large effort was undertaken to move the OnDemand application from DB2 on z/OS (DB2) to DB2 LUW on AIX (LUW). OnDemand is up for a week at a time, coming down only for IPL. The DB2 accounting record is written at that time. The team identified all the sources of OnDemand activity and changed them to point to the new LUW platform. According to the team, all DB2 activity should now be Select only. Problem: The weekly DB2 accounting record for OnDemand show Insert, Update, and Delete activity. The accounting record should have zeros in the fields. Instead, there are 198 inserts, and 396 updates. This means that something on the mainframe is still writing into OnDemand on DB2. The OnDemand system log has been checked, and it doesn't identify who is doing the inserts/updates (as far as I can tell). Since the Accounting record is once a week only, its not useful to find out when the activity occurred, which would lead to logs, undo/redo, etc. Options to find the stragglers: 1. Start the DB2 tables READ ONLY. Downside: will cause abends. 2. Scan all the DB2 logs for the week. Downside: CPU usage to scan a week's worth of logs. 3. Ask IBM-Main for ideas. Any ideas are appreciated. Thanks very much. Linda ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
