Time for an RFE. Is there any reason to limit the extended attribute values to NO and OPT. Why not YES, forcing the use of DSCB 8 and 9 even if the dataset is not on an EAV?
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Scott Barry [[email protected]] Sent: Saturday, May 30, 2020 11:59 AM To: [email protected] Subject: Re: TIME a data set was created? Additional consideration is that the dataset must be created on an EAV DASD volume in order to include a time-portion. Additional data-fields included in FORMAT-9 DSCB as of z/OS V1R11 are CREATE JOBNAME, STEPNAME (but not PROC-STEP info). Sadly, I remember that a DFHSM-recalled dataset loses these true JOBNAME, changing to the DFHSM started-task name - but I haven't checked this behavior in several releases. Scott Barry SBBTech LLC On Fri, 29 May 2020 22:58:55 -0700, Ed Jaffe <[email protected]> wrote: >On 5/29/2020 7:00 PM, Peter Vels wrote: >> How does one get the TIME a z/OS data set was created? The date is easy, >> but I'm after the time. > >Data set creation time has been supported by z/OS for many years. To get >it, you must allocate using FMT8/9 DSCBs in the VTOC instead of FMT1. >When you do so, you get this field in the format 9 disk label: > >DS9TIME DS XL6 Number of microseconds since >* midnight, local time, that the data >* set described by its format 8 DSCB >* was created. See creation date >* field, DS1CREDT, for the date @V2A > >-- >Phoenix Software International >Edward E. Jaffe >831 Parkview Drive North >El Segundo, CA 90245 >https://secure-web.cisco.com/1t_YeKtsOFPjbp3UdFoFYpRz0cypc3uA_0Wz5kLbhVOjuUS45vxHbtOwRVOgb-1emcN5y0sLno7m3JRc6XuiMmHHEyqmUivrYJTzzyorxpX_or6prolbSMwh9iUKRxs0rvR02GW2mfngyAm-w0OydKC4e0CknkAQGlkAm_g6DaSUMa_Au3mUfR59GAAgSZ_Xx5qwMWWI1-BxY8SOiFkOCjdEtmGOytZbSbr5F6BII_zzbI8Dmywz0g6TBoTRcNXOmmmqPHe2yAWbd8F0ZWZHjQskXVWcrM85CZYWYl1gx1lHjWq6peuiCzPBGGV8vrEv1EaShbS7iTAM0xE8id6vUrkyMqR062v24oAeZZhCa91c02dWvzUMQ7uhIsvYFVnKKhm0zLTeKMVUdLd0MqRE7eu5uugZrDmYpcCZJ8MlsyoYeUCsZ7IiMXcmAvgaiFBAN/https%3A%2F%2Fwww.phoenixsoftware.com%2F > > >-------------------------------------------------------------------------------- >This e-mail message, including any attachments, appended messages and the >information contained therein, is for the sole use of the intended >recipient(s). If you are not an intended recipient or have otherwise >received this email message in error, any use, dissemination, distribution, >review, storage or copying of this e-mail message and the information >contained therein is strictly prohibited. If you are not an intended >recipient, please contact the sender by reply e-mail and destroy all copies >of this email message and do not otherwise utilize or retain this email >message or any or all of the information contained therein. Although this >email message and any attachments or appended messages are believed to be >free of any virus or other defect that might affect any computer system into >which it is received and opened, it is the responsibility of the recipient >to ensure that it is virus free and no responsibility is accepted by the >sender for any loss or damage arising in any way from its opening or use. > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
