Not totally clear on the scenario. You say you switched from DB2 on z/OS to DB2 LUW on AIX, but that you are still getting updates from the mainframe. Does that mean that this OnDemand app is still on z/OS, or it was also moved?
I'm not familiar enough with db2 luw to know whether there are traces or such that are equivalent to those found in ZOS that could be set to increase your visibility. On Z, I'd just look at my monitor and have an answer fairly quickly. You could always subscribe and ask on the db2 list ( http://www.idug.org/l/pw/rs/ ) There are LUW experts there. If the app is still on the mainframe, seems you could revoke insert/update/delete authority from racf for the app's authid, or do the equivalent of that on LUW if that option is available and watch for the violation messages. Just off the cuff, it would seem to me that worrying about abends resulting from READ ONLY tables isn't necessary. If you have unexpected inserts and updates where you expected none, then your data has become unreliable. No way to trust the data until you can account for them so an abend from a READ ONLY startup wouldn't bother me at all. hth, tom -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Linda Hagedorn Sent: Friday, February 24, 2017 4: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
