sorry it doesn't works? why the dataset cannot migrate to MIGRAT1 after
primary management ?
Auto Migrate . . Y (Y, N, I or P)
Auto Backup . . Y (Y or N)
Auto Dump . . . Y (Y or N)
Allocation/migration Threshold: High . . 60 (1-99) Low . . 10
(0-99)
Migration Attributes
> Primary Days Non-usage . . . . 0 (0 to 9999 or blank)
> Level 1 Days Non-usage . . . . 4 (0 to 9999, NOLIMIT or
blank)
> Command or Auto Migrate . . . . BOTH (BOTH, COMMAND or NONE)
the pool contains only one volume SDHSM1
and you can see only 19 CYL free on volume "SDHSM1"
VTOC #CYL,#TRK,#EXT/#CYL,#TRK USR
STATE
SDHSM1 988C I SPACE=0019,0005,0003/0014,0000 3390 007 PVT/RSDNT
after I issued F HSM1,SETSYS PRIMARYSPMGMTSTART (1703,1720)
ARC0522I SPACE MANAGEMENT STARTING ON VOLUME 405
ARC0522I (CONT.) SDHSM1(SMS) AT 17:03:00 ON 2006/08/14, SYSTEM SYSP
ARC0523I SPACE MANAGEMENT ENDED ON VOLUME SDHSM1, 425
ARC0523I (CONT.) 00000000 DATA SET(S) MIGRATED/DELETED, 00000000
ARC0523I (CONT.) TRACK(S) FREED, MINAGE 0, TIME 17:03:05
why the following files does not migrate to MIGRAT1 after primary
management
-------------------------------------------------------------------------------
SDHSM.HSM.D060814C
SDHSM1
18000 0 1 3390 PS VBS 32760 32760 2006/08/14 ***None***
2006/08/14
-------------------------------------------------------------------------------
SDHSM.HSM.D060814D
SDHSM1
21000 0 1 3390 PS VBS 32760 32760 2006/08/14 ***None***
2006/08/14
-------------------------------------------------------------------------------
SDHSM.HSM.D060814E
SDHSM1
6000 0 1 3390 PS VBS 32760 32760 2006/08/14 ***None***
2006/08/14
-------------------------------------------------------------------------------
SDHSM.HSM.D060814F
SDHSM1
1500 0 2 3390 PS VBS 32760 32760 2006/08/14 ***None***
2006/08/14
-------------------------------------------------------------------------------
I already check the MIGRAT1 volume space and it is ok.
if I issued the command "F HSM1,MIGRATE VOLUME(SDHSM1 MIGRATE(0))" it will
force all file and migrate to MIGRAT1
anyone know why?
thanks
Tommy Tsui, on Sunday, August 13, 2006 at 11:26 PM wrote:
>
>Anyone know why I set the management class attributes "primary days
>non-usage" to "0" but all datasets does not move to primary disk after
>primary management started.
>
>Migration Attributes
> Primary Days Non-usage . . . . 0 (0 to 9999 or blank)
> Level 1 Days Non-usage . . . . 4 (0 to 9999, NOLIMIT or
blank)
> Command or Auto Migrate . . . . BOTH (BOTH, COMMAND or NONE)
My guess is that the utilization for the pool was below the threshold, or
the low threshold was achieved before this dataset was migrated. Since
DFSMShsm does a pretty good job of keeping datasets on the quickest
devices,
it will only migrate data if it has to.
--
***********************************************************
This message contains confidential information which is intended only for the
person or entity to which it is addressed. If you are not the intended
recipient, you should not read, disseminate, distribute or copy this e-mail.
Any opinion contained in this message are those of the author and are not given
or endorsed by BOCHK unless otherwise stated in this message and the authority
of the author to so bind BOCHK is duly verified. We do not guarantee that this
e-mail is virus-free or secure and are not liable in respect of any delay or
omission in the transmission of this message.
***********************************************************
----------------------------------------------------------------------
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
