question about dfsms management class autobackup=y

Hervey Martinez · Posted: Tue Oct 10, 2017 6:19 pm

We have files that are assigned this management class and are to expire after 46 days. We don't run HSM backups since we use FDR for our backups. The description for this parm says that "backups may be run" for files under this class.

The files don't expire after the 46 days and get flagged by HSM with :

RC= 53, REASON= 0

Just wondering why these files don't go away if the 'autobackup =y' says that backups may be run but it looks like these are required.

Any ideas?

Pete Wilson · Posted: Sat Jun 09, 2018 11:37 pm

DFHSM AutoBackup has nothing to do with Expiration of datasets, it is AutoMigration in combination with the datasets Mgmtclas that does the Expiration. If the Storgrp where the datasets reside does not have AutoMigration enabled it won't expire any of the datasets in it.

And you mention both DFHSM and FDR (maybe FDRABR?), which seems a bit odd. Why would you have both running? That could be a recipe for a lot of trouble.

NOTE: The FDRABR equivalent of DFHSM AutoMigration is AutoArchiving, but you DEFINITELY don't want to have both DFHSM and FDRABR doing that!

If you are using FDRABR to do AutoArchiving rather than DFHSM, then it can use either the Mgmtclas, or FDRABR parameters for dataset level selection, or at Storgrp level or the ABR modelDSCB on the volume to determine if archiving is done at that higher level.

expat · Posted: Mon Jun 11, 2018 11:42 am

You may find that if the management class specifies a number of backups then HSM will not delete the dataset if no backups exist.

Did you look up the error message in the manuals ???

Pete Wilson · Posted: Mon Jun 11, 2018 1:28 pm

Good call Expat

ARC1253I
********

DATA SET NEEDS BACKUP SO IT WAS NOT EXPIRED

Explanation
~~~~~~~~~~~

During SMS expiration processing, the data set was found to still be in need
of backup. It is not expired until the backup is done.

DFSMShsm determines a data set is NOT in need of backup if one of the
following situations exists:

The data set change flag is off in the VTOC entry AND the last backup date
in the catalog is nonzero. Note that DFSMShsm does not verify the existence
of the backup version.

The data set change flag is off in the VTOC entry AND the last backup date
in the catalog is zero AND the management class does not request autobackup
for this data set.

The data set change flag is on in the VTOC entry AND the management class
does not request autobackup for this data set.