On Fri, 15 May 2020 11:39:59 -0500, Kirk Wolf wrote: >Having personally spent a large amount of time dealing with this issue, >what I can tell you is that for non-VSAM data sets that the best that you >can do in most cases (without actually reading the data set) is to look at >the DSCBs to get the last used TTR and then calculate an estimate of the >data set size based on the recfm and blksize. There are some special >cases, like compressed data sets where the catalog can help. > >It would be fantastic if somewhere you could get: >1) the number of logical records > Use CMS.
>2) the total number of bytes > Use zFS. (mutually exclusive with (1).) >3) fine grained timestamp when the data set was last updated > FAMS has this for PDSE members. Why is it a #$%^& trade secret from the user when a file was updated? (But it's visible from an NFS client!) https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.idan400/cpn2co250.htm >4) sha256 hash of the data set > And whatever other metadata a customer wishes for or is useful for web cache validation: https://en.wikipedia.org/wiki/HTTP_ETag -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
