ISPF stats are kept in the user data part of the directory entries. IEBCOPY copies directory entries as-is (except for some updates needed for load modules & program objects).
I don't know what NFS is looking at, but it's not ISPF stats. I wouldn't expect it to, so my guess is everything is working as designed. sas On Tue, Jul 19, 2016 at 8:09 PM, Paul Gilmartin < [email protected]> wrote: > On Tue, 19 Jul 2016 15:37:03 -0400, Steve Smith wrote: > > >The first rule of FAMS is you don't talk about FAMS. :-) > > > >I don't think that denying its existence is part of the contract, but I > >can't say anything else about it. > > > Hmmm... If I IEBCOPY a PDSE to another PDSE, ISPF member list shows > that the timestamps from SYSUT1 are replicated in SYSUT2. I believe > this is quite deliberate. > > However, NFS shows for SYSUT2 the timestamps as the time of the > IEBCOPY job step, neither the timestamps shown for SYSUT1 nor the > timestamps shown by ISPF. This seems wrong. Is it APARable? > > (If I submit an SR I'll not talk about FAMS. It seems prudent to be > disingenuous here.) > > Perhaps an RCF? > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
