So both you and Lizette are saying that even I can obtain it, the available timestamp is not very useful. We need to synchronise the mainframe data set with its workstation copy and currently use hashes of each file to see if they are different. This is CPU intensive and I had hoped to avoid it by comparing the last write dates. It looks like my scheme won't work in this case (it works fine for libraries of members like PDSs and Endevor). Hmm.
Thanks Robin -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of retired mainframer Sent: 22 November 2013 00:54 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Getting a VSAM data set's system timestamp For a non-VSAM dataset, the last reference date in the F1 DSCB does not mean the dataset was changed on that date, only that it was opened (and closed?), even if only for input. :>: -----Original Message----- :>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :>: Behalf Of Robin Atwood :>: Sent: Thursday, November 21, 2013 4:48 AM :>: To: IBM-MAIN@LISTSERV.UA.EDU :>: Subject: Getting a VSAM data set's system timestamp :>: :>: I want our file server to be able to tell the clients when a data set :>: last :>: changed. For non-VSAM it's easy (if a bit vague), there's the last :>: reference :>: date in the F1 DSCB. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
