> Microseconds? Milliseconds? Who cares? They're both too small to be much > concerned with.
I'd settle for AM/PM at this point. It would be an improvement in granularity on local calendar days. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Friday, June 07, 2013 4:04 PM To: [email protected] Subject: Re: Age of datasets in hours, not days? On Fri, 7 Jun 2013 15:28:21 -0700, Charles Mills wrote: >The rotation is not constant, and is "too slow." It takes (a very little) more >than 24 hours for the earth to make one rotation. > >What have I started!?! All I wanted to know was whether LISTCAT or the like >supported dataset age granularity finer than one day! > Indeed. And you got only a partial answer. It's in the DS9TIME field of the F9 DSCB, but no advice on interfaces to it. I suppose there's always EXCP. Looking for more information, I found: http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.adru000%2Fow19618.htm 2. For a preallocated target that has F8/F9 DSCBs, the F9 DSCB field DS9CREAT is set ON, and is being scratched and reallocated, these patch byte settings will not be honored. These types of data sets have a field in the F9 DSCB which corresponds to the number of milliseconds past midnight in which the data set was created (DS9TIME). In order for the DS9TIME to be usable, the creation date and the time past midnight of the preallocated target will be preserved as its value prior to scratching. Microseconds? Milliseconds? Who cares? They're both too small to be much concerned with. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
