The "stranded" data set has a create date time in the name from 10 months ago. Does not show B or M records in DCOLLECT. Several "current" datasets have create date time from last week to 2 months ago. Shows several B and M records in DCOLLECT over last 3 months.
So the HDEL and HRECOVER on the "stranded" data set isn't going to work. ISPF 3.4 on the "stranded" data set shows nothing. On Tue, Jul 21, 2015 at 1:23 PM, Staller, Allan <[email protected]> wrote: > Are these DCOLLECT entries current? > > If you have review and/or fileaid, get the "mig" DSN from the SDSP and > browse the MCDS to get the "true" dsn. > THEN : > > HDEL 'dataset name' > Delete SDSP > HRECOVER 'dataset name'DSN (from backup) > > HTH, > > <snip> > After doing the freevol, the SDSP contains the high value record and 6 > records for another dataset. Viewing a recent DCOLLECT and searching for the > leading part of the dataset name, we found 2 migrated datasets with time > stamps over the last 2 months and 4 backups of the dataset over the last 3 > months. This dataset has a time stamp about 10 months ago, 3.4 only lists > the newer datasets. > > I am assuming this is a stranded dataset. Besides deleting the SDSP, any > cleanup needed? > </snip> > > ---------------------------------------------------------------------- > 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
