Kirk Wolf wrote: >I'm trying to come up with an efficient way to see if a non-VSAM data set >has been changed.
Kirk, do you have some more details on your particular use case(s) you could share? I started typing a reply with at least a couple possible non-hashing, lower resource approaches -- upon first impression hashing seems like it'd be heavy handed and awkward here -- but I find I'm speculating (guessing?) too much too soon. As examples, which type(s) of non-VSAM data sets? When do you want to know they've changed -- within what time period? (Nightly?) Who/what wants to know? Bill Gates? :-) A program on the same z/OS system? What type of program? Are there any other facilities/features we should assume or not assume are present/eligible to be used on that z/OS system? (You mentioned a couple, duly noted.) What release(s) of z/OS? Is it enough to know there was a *possible* change (e.g. sensing open for writing/input), or is sensing an actual data set change required? Anything else you can think of that I didn't ask? :-) -------------------------------------------------------------------------------------------------------- Timothy Sipples IT Architect Executive, Industry Solutions, IBM z Systems, AP/GCG/MEA E-Mail: [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
