Hello,
just a thought but are the datasets being backed up via an "hbackds" command?
they might have an explicit retaindays coded (new in Z/os 1.11 i think) which
would negate the mgmtclas settings.
Also, have another look through the hsm backup logs when expirebv is running
for the datasets in question.
The datasetname would have the dfhsm.back.t****** prefix so all you could
recognise would be the 1st & 2nd qualifiers rather than the full datasetname
but there should still be an entry, which would give you the deletion criteria.
If your system runs daily dcollects with the hsm migd &bacd parms you could
strip out (sas or rexx) pertinent data (See AMS for Catalogs, Appendix F,
record type B) about your missing datasets to help narrow things down.
Good hunting!
Dave
***********************************************************************************************
> EXPIREBV is run daily.
> FWIW, this same problem plagues certain GDG datasets as well. However, this
> is not a system-wide problem.
>David G. Schlecht | Information Technology Professional
>State of Nevada | Department of Administration | Enterprise IT Services
>T:(775)684-4328 | F: (775) 684‐4324 | E:dschle...@admin.nv.gov
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
