> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of John Ticic
>
> --- snip ---
> When he recalled it again, the member that he had added was missing.
>
> I checked through SMF and saw the activity. The fact that the dataset
> ([data.set.name]) was on [volser] (a NONSMS volume)
> complicates matters a little.
> --- snip ---
>
> What kind of activity did you see in SMF that shows that a
> data set had an additional member added!
>
> If HSM reconnected the ML2 version, then I would expect that
> the original data set was not changed.
The colleague who reported the anomaly did not furnish SMF data showing
the addition of a member, but did say this:
"We restored the dataset from the full volume backup, and the added
member was present."
The same colleague is currently browsing the IBM-MAIN archives and found
an article from 1994 (!) in which IBM was asked if DFSMSdss resets all
dataset-changed bits on a full-volume restore, and the reply had been
"WAD" (I assume that means "yes"). If (still) true, then I believe we
have our answer. We did use DFSMSdss to perform the full-volume backups
and restores.
-jc-
>
> John
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access
> instructions, send email to [EMAIL PROTECTED] with the
> message: GET IBM-MAIN INFO Search the archives at
> http://bama.ua.edu/archives/ibm-main.html
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
