|
View previous topic :: View next topic
|
| Author |
Message |
upendrasri
Active User
Joined: 28 Sep 2017
Posts: 121
Location: India
|
|
|
|
Hi All,
One of my data set is with MIGFILES MC and MC rules as below
| Code: |
Expiration Attributes
Expire after Days Non-usage . : 35
Expire after Date/Days . . . . : NOLIMIT
Retention Limit . . . . . . . : 0
Migration Attributes
Primary Days Non-usage . : 0
Level 1 Days Date/Days . : 0
Level 2 Days Non-usage . : NOLIMIT
Command or Auto Migrate . : BOTH
Size Less Than or Equal to:
Action . . . . . . . . . :
|
As per the MC, File should be migrated to ML2 directly but the below file
TEST.USER.MIGPC155 Which was created on 2014.113 and not in use
Listc details as below:-
| Code: |
CLUSTER ------- TEST.USER.MIGPC155
IN-CAT --- USER.U00O001.CATALOG
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2014.113
RELEASE----------------2 EXPIRATION------0000.000
SMSDATA
STORAGECLASS ---STANDARD MANAGEMENTCLASS-MIGFILES
DATACLASS -----------SCR LBACKUP ---0000.000.0000
CA-RECLAIM---------(YES)
EATTR-------------(NULL)
BWO STATUS------00000000 BWO TIMESTAMP---00000 00:00:00.0
BWO---------------(NULL)
|
My file is not getting Migrated. I have verified ACS Routines and everything looks okay. And other files belongs to this MC are getting Migrated as expected.
Any suggestions on this.
Thanks! |
|
| Back to top |
|
 |
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1247
Location: Bamberg, Germany
|
|
|
|
| It can have certain reasons why a dataset is not migrated or scratched. In this case I'd suggest you have a look on the DFHSM activity log and act accordingly to the RET/RSN codes. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Normal reason is that a backup does not exist where the MGMTCLAS states that one should |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1247
Location: Bamberg, Germany
|
|
|
|
| @expat: That brings you back to what I have written. Look at RET/RSN codes. |
|
| Back to top |
|
|
upendrasri
Active User
Joined: 28 Sep 2017
Posts: 121
Location: India
|
|
|
|
Hi Expact and Joerg,
There is no backup as per MC rules as below
| Code: |
CDS Name . . . . . . : ACTIVE
Management Class Name : MIGFILES
Backup Attributes
Backup frequency . . . . . . . . . . . :
Number of backup versions . . . . . . . :
(Data Set Exists)
Number of backup versions . . . . . . . :
(Data Set Deleted)
Retain days only backup version . . . . :
(Data Set Deleted)
Retain days extra backup versions . . . :
Admin or User Command Backup . . . . . : NONE
Auto Backup . . . . . . . . . . . . . . : NO
Backup copy technique . . . . . . . . . : STANDARD
|
Thanks! |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1247
Location: Bamberg, Germany
|
|
|
|
| Let us know the RET/RSN code from the DFHSM log. |
|
| Back to top |
|
|
upendrasri
Active User
Joined: 28 Sep 2017
Posts: 121
Location: India
|
|
|
|
Hi Joerg,
I have searched information about the above file in DFHSMLOG but no details found.
Please let me know is there any specific way to find RET/RSN code?
Thanks! |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1247
Location: Bamberg, Germany
|
|
|
|
| When you try to migrate the DSN to ML2, it should bring something up. Please try that. |
|
| Back to top |
|
|
upendrasri
Active User
Joined: 28 Sep 2017
Posts: 121
Location: India
|
|
|
|
Hi Joerg,
Sure, I will Migrate it manually and will get the details from DFHSMLOG
Thanks! |
|
| Back to top |
|
|
upendrasri
Active User
Joined: 28 Sep 2017
Posts: 121
Location: India
|
|
|
|
Hi Joerg,
I have manually Migrated dataset to ML2 but no information about this dataset in DFHSMLOG.
But I have executed the below command
| Code: |
HLIST DA('TEST.USER.MIGPC155')MCDS
|
Output of the above command :
| Code: |
DSN=TEST.USER.MIGPC155 MIGVOL=N08269 DSO=VS SDSP=NO
LAST REF=14/04/13 MIG=20/02/24 TRKS=00000698 2K BLKS= ******* TIMES MIG= 00001
16K BLKS=0000001895 LAST MIGVOL=*NONE*
|
Looks like HSM is excluding this dataset?
Thanks! |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 580
Location: London
|
|
|
|
The dataset was migrated on the 24th Feb, presumably by yourself, so there is no issue.
As to why it hadn't migrated without you entering a specific migrate command, then this can depend on a couple of things. As DFHSM goes through a volume to determine what to migrate it prioritises things to minimise the amount of work it has to do. I can't remember exactly, but I think it looks at GDG's beyond their retain on primary limit, then size descending along with Mgmtclas. So it will migrate datasets in this sort of order, until the volume has reached the low threshold value set for the Storgrp, then it stops migration of the volume. Because of this often small datasets never get migrated as they're not in the priority list and the volumes low threshold is reached before it needs to migrate any more data.
You can manually migrate datasets that should be migrated, or issue a migrate command for the volume which will take ALL the eligible datasets based on Mgmtclas criteria. |
|
| Back to top |
|
|
|
|
