Also, what are the actual dataset attributes? DFHSM doesn't do some 
"incomplete" datasets. Are they backed up. DFHSM often doesn't delete if there 
is not a back-up.

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of willie bunter
> Sent: Thursday, January 14, 2016 9:53 AM
> To: [email protected]
> Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT
> 
> Lizette,
> 
> Thanks for the info.  For this dsn in particular there is no migration it is 
> to be
> expired/deleted after 1 day of non-usage.
> 
> You have touched on the point of space management algorithms for
> migration.  I assume that this would also pertain to the deletion of files as
> well. Right?
> 
> --------------------------------------------
> On Thu, 1/14/16, Lizette Koehler <[email protected]> wrote:
> 
>  Subject: Re: DFHSM/SMS QUESTION -  SPACE MANAGEMENT
>  To: [email protected]
>  Received: Thursday, January 14, 2016, 12:45 PM
> 
>  So depending on the
>  version of z/OS - look at On Demand Migration (v2.1 and  above), this might
> help more
> 
>  Second, correct, files are only moved if DFHSM  feels the volume needs to
> have the space back, however, you  could  have a migration policy in the
> management class that  says - if this is still on DASD after 1 month, then
> migrate  the file.
> 
>  It depends on
>  what your requirements are.  You can just let files migrate  as HSM sees fit
> based on its algorithms for space  management, or you can setup a
> management class that says it  gets migrated if unused in XX days.
> 
>  Many choices.
> 
>  Lizette
> 
>  >
>  -----Original Message-----
>  > From: IBM
>  Mainframe Discussion List [mailto:[email protected]]  On  >
> Behalf Of willie bunter  > Sent: Thursday, January 14, 2016 10:23  AM  > To:
> [email protected]  > Subject: DFHSM/SMS QUESTION - SPACE
> MANAGEMENT  >  > Good  Day To All,  >  > I  need to confirm if I my
> understanding about SMS & SPACE  management is  > correct.
>  > We have noticed that there are several  dsns which have been on dasd for
> over  >
>  10 months.  The volumes and dsns are all SMS managed and  DFHSM
> performs the  > necessary migration  and deletion.  I checked the
> MANAGEMENT class and the  dsns  > are to be deleted after 1 day  non-usage
> >  > Expire  after Days Non-usage  . : 1  > Expire  after Date/Days . . . .   
> >    : 1
> >  Retention Limit  . . . . . . .           :
>  0
>  >
>  > Below are the
>  attributes of the Storage Group:
>  >
>  >
>  > Allocation/migration
>  Threshold :            High
>  85   (1-100)  Low . . 1
>  >
>  (0-99)
>  > Alloc/Migr Threshold
>  Track-Managed:  High    85   (1-100)    Low  . . 1   (0-  > 99)  > Guaranteed
> Backup Frequency  . . . . .
>  .                  (1 to 9999 or
>  > NOLIMIT)
>  >
>  BreakPointValue  . . . . . . . . . . . .
>                   (0-65520
>  > or blank)
>  > Processing
>  Priority  . . . . . . . . . . 50
>     (1-100)
>  >
>  > I think that the dsns are not deleted  because SMS did not select some of
> these  > volumes have not met the criteria of the  Low threshold of 1.  I
> remember  >  reading somewhere (on this board the following):
>  >
>  > For primary space
>  management, HSM only looks at the low threshold. If the  > volume exceeds
> the low threshold, then we  will process any data sets that are  >  eligible 
> for
> migration on that volume.
>  >
> 
>  > Could someone confirm if I am
>  correct?
>  >
>  >
>  Thanks.
> 
>  ----------------------------------------------------------------------
>  For IBM-MAIN subscribe / signoff / archive  access instructions,  send email
> to [email protected]  with the message: INFO IBM-MAIN
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to