Kirk Wolf wrote: >I'm trying to come up with an efficient way to see if a non-VSAM data set has >been changed.
Which changes do you want to check: copy / move / recall / migrate / rename / append / overwrite all or parts? What non-VSAM? PS / PDS / PDS-E? Do you check that ALL parts have been changed or only a subset? Say your non-VSAM spans multiple volsers, but on volser 3 a little overwriting of 1 character must be picked up by your hash? >Flipping the DS1IND08 bit is not an option, nor can I install SMF hooks, etc >in the OS. No hooks? So that also means no SVC99 intercept? >The problem, of course, is that DSCBs don't have "last update timestamps". So I see that after RTFM... Until you get a solution, why not set audit to that dataset for all access attempts and then check for UPDATE or higher attempt? Plus LOGOPTIONS ALWAYS in RACF for datasets? Of course, for APF-ed and Trusted/Privileged STCs, this will perhaps not work... Alternatively, could you be kind to tell us why you want to see if it has been changed or not? Perhaps there are other solutions? What about asking big blue to see if there is some reserved, but unused field you can use? Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
