|
View previous topic :: View next topic
|
| Author |
Message |
selvamsrinivasan85
New User
Joined: 09 Aug 2010
Posts: 33
Location: Chennai
|
|
|
|
Hi all,
I have very less knowledge on Tape datasets. Currently we have a requirement to mass delete a group of datasets that has PS , VSAM, GDG Base with Versions and Tape datasets.
Most of the tape datasets are migrated and when i try to recall, am getting " Dataset not in catalogue".
When I try to catalogue, it is asking Volume information. What needs to be done?.
Also I have a query on IDCAMS Delete with FORCE and PURGE. Which one is good?. |
|
| Back to top |
|
 |
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1338
Location: Bamberg, Germany
|
|
|
|
| The FORCE is not your desired option using IDCAMS. See Mark Zeldens CMD34 (with Option Reverse) as a good way to do. I also think you have some other problems in your catalog structure. See DFSMShsm Audit Commands as well, and hold a Catalog Utility ready at hand (most shops do). |
|
| Back to top |
|
|
Willy Jensen
Active Member
Joined: 01 Sep 2015
Posts: 736
Location: Denmark
|
|
|
|
"Most of the tape datasets are migrated"
Sorry, that sounds wrong to me. A migrated dataset is a really disk dataset, though stored on a HSM tape, please clarify. |
|
| Back to top |
|
|
selvamsrinivasan85
New User
Joined: 09 Aug 2010
Posts: 33
Location: Chennai
|
|
|
|
| Willy Jensen wrote: |
"Most of the tape datasets are migrated"
Sorry, that sounds wrong to me. A migrated dataset is a really disk dataset, though stored on a HSM tape, please clarify. |
Hi Willy,
I am not sure on that. I am able to see the dataset in 3.4 and it's migrated. When I issue HRECALL, I am getting 'Dataset not in Catalogue'. How to verify that is a tape dataset or disk dataset?. Also how to delete such type of datasets?.
@Joerg,
I even googled about CMD34. Not having luck. Any link would be greatful... |
|
| Back to top |
|
|
Willy Jensen
Active Member
Joined: 01 Sep 2015
Posts: 736
Location: Denmark
|
|
|
|
| If it is migrated, then it is per definition a disk dataset which has been migrated. You can't actually immediately tell if the migrated dataset is on HSM level1, which is disk, or on level 2, which is (virtual most likely) tape. It's been a while, but the TSO HLIST command should give you some more details, see HELP HLIST for details of the command if you do not have the HSM manual readily available. |
|
| Back to top |
|
|
Willy Jensen
Active Member
Joined: 01 Sep 2015
Posts: 736
Location: Denmark
|
|
|
|
What, if anything has changed recently?
If you get a 'not cataloged' for a migrated dataset, it might indicate a catalog issue, like a missing catalog alias. Can you recall any migrated dataset? Can you migrate - see the HMIGRATE comand? |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1338
Location: Bamberg, Germany
|
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1338
Location: Bamberg, Germany
|
|
|
|
| What was my point, and Willy has indicated this as well, is the Alias or DSN level you intend to remove still visible in the catalog? |
|
| Back to top |
|
|
Willy Jensen
Active Member
Joined: 01 Sep 2015
Posts: 736
Location: Denmark
|
|
|
|
| or before we get lost in idle speculation, let's see the actual command and the actual error message |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1338
Location: Bamberg, Germany
|
|
|
|
| RC should be 02 ;) |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2596
Location: Silicon Valley
|
|
|
|
re: deleting a migrated dataset
How about just issuing HDELETE command?
| Code: |
| HDELETE 'my.dsn' NOWAIT |
|
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 592
Location: London
|
|
|
|
| For migrated datasets the volser in a 3.4 list will show as MIGRAT1 or MIGRAT2. Anything else then it is not a migrated dataset and either a DASD or TAPE dataset, or possibly and alias or path name. The volser names are always a local standard so you'd need to ask your Storage people. In fact they're more likely to be able to help you with the whole process anyway rather than trying things blindly and potentially causing problems. |
|
| Back to top |
|
|
selvamsrinivasan85
New User
Joined: 09 Aug 2010
Posts: 33
Location: Chennai
|
|
|
|
| We have contacted storage team. They informed that the actual datasets are deleted and entries are showing up due to IO error in HSM. They are telling these are orphan entries and has no value. They unable to do anything on that. |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1338
Location: Bamberg, Germany
|
|
|
|
| Your storage team should be able to clean up these entries, otherwise they should look to find another job. |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 592
Location: London
|
|
|
|
| Joerg.Findeisen wrote: |
| Your storage team should be able to clean up these entries, otherwise they should look to find another job. |
Indeed, suggest they look at the DFHSM AUDIT commands which will identify the errors and often even produce a fix at the same time.
And if there's an actual structural error in the DFHSM Control datasets they REALLY need to get that sorted out as well otherwise it will bite them. |
|
| Back to top |
|
|
|
|
