Future? I don't think so. How about an IDCAMS or TSOBATCH print COUNT(1) so you won't have to create any JCL. And z/OS doesn't read the whole file, so size will have little impact, just the files not big enough to fill the buffers will be a little faster..
On Fri, Aug 2, 2024 at 10:06 AM Billy Ashton <[email protected]> wrote: > > Hi friends! Here's another in the series of "Friday Foibles!" (Why these > questions always come up on Fridays is beyond me!) > > We have a need to run a job that will perform a process like the Unix > touch command, so that the last access date of a file is updated. > > We don't want to do things like allocate, open, and print one record, as > some of these files are huge (25-50GB). The list of files is somewhat > dynamic, and may change week to week. > > Does anyone have a job that will update the last access date for a list > of files, and ideally, set the last access date into the future a week > or two, to ensure that the files will not get archived (since I am not > sure we could easily recall some of them again)? > > Thank you and best regards, > Billy Ashton > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
