> -----Original Message-----
> From: IBM Mainframe Discussion List
>
> or the changed bit was reset and hsm thought that the dsn had
> not changed and then reconnected?
Since we have a spare volume, we just restored the backup tape again
(DFSMSdss RESTORE FULL PURGE) and I ran a LISTVTOC for the dataset in
question. The Format-1 DSCB at offset 93 (x'5D') contains x'88' which,
according to the DSCB (partial) DSECT, indicates:
X'80' 1... .... LAST VOLUME ON WHICH THE DATA SET RESIDES
...
X'08' .... 1... 1-DATA SET MODIFIED SINCE RECALL
Seems to me that DFSMShsm should NOT have "reconnected" this dataset to
the previous ML2 copy, but it did.
In contrast, the "real" copy of the dataset has been updated today, and
its DSCB contains x'8A' at offset 93 (x'5D'), which additionally
indicates:
X'02' .... ..1. DATASET OPENED FOR OTHER THAN INPUT SINCE LAST
BACKUP COPY MADE
Now I have to wonder which bit is the "changed" bit on which DFSMShsm
relies?
-jc-
----------------------------------------------------------------------
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
