1) Check the AUTOMIGRATE setting on the STORAGE GROUP 2) Check the high/low thresholds on the storage group. If the volume does not exceed the high threshold, migration will not occur. If migration does occur, the datasets will be migrated in chronological order (oldest to newest) and it may not "get that far" if there are still older datasets to be migrated.
3) Check the settings for automig start times BTW, datasets can be migrated regardless of backup status. By default the will not be automatically deleted unless there is a backup. There is a patch avail to allow deletion of datasets w/o requiring a backup. HTH, <snip> I have a number of datasets whose management class reflects Primary Days of 2 and yet after 2 weeks of non-reference, they still are on dasd. Cmd/Auto Migrate is set to BOTH, Auto-Backup set to No. I can hmigrate it in ispf 3.4 ok to ml2, but wondering why auto-migration is not kicking in. Is there a setting that regulates that a dataset will not auto-migrate if in fact no backup exists? (but apparently has no qualms about manually hmig'ing it?) </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
