|
View previous topic :: View next topic
|
| Author |
Message |
tchen40
New User
Joined: 12 Sep 2007
Posts: 30
Location: Los Angeles, Ca
|
|
|
|
Somehow, the catalog entry for a dataset and HSM's entry in the MCDS are different. The catalog entry shows it as off to an ML2 volume (MIGRAT2). When I run an HSM command to show me what's in the MCDS, it tells me its on an ML1 volume.
I am trying to do a delete noscratch and then a recatalog on the dataset to volume MIGRAT and devtyp(3390).
I am getting messages:
IDC3014I CATALOG ERROR
IDC3007I ** VSAM CATALOG RETURN CODE IS 38
I could've sworn I have been able to do an IDCAMS delete nscr on a migrated dataset before. Hints anyone ? |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
If you want to delete the dataset, you might try HDEL.
I've not ever tried to catalog a dataset to migrat status  The system always does this.
Talking with your storage management people might be a good thing to do. . . |
|
| Back to top |
|
|
tchen40
New User
Joined: 12 Sep 2007
Posts: 30
Location: Los Angeles, Ca
|
|
|
|
Dick,
I am the storage admin. ;-)
Anyways, I wound up exorcising it from the catalog and now, I'm trying to fix the MCDS record with a whole series of FIXCDS PATCH commands.
Long story short, I really want to be able to recall this dataset. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| I am the storage admin. ;-) |
Oh 
Not my best area, but i seem to recall some hsm utility that would allow dragging a "deleted" file out of an archive and bypassing all of the normal hsm "rules".
The rescued dataset could then be copied back onto the system and be under hsm control again. My memory may have gone over to the dark side also. . . 
My current gig does not have proximity with any storage admins, so i can't simply ask. Maybe soon one of the forum storage heavies will be back online. |
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
| HDEL has always worked for me and so has HMIG (when my userid was authorized). |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
HDEL would wipe the dataset out both from the catalog and HSM.
Which may be OK if a valid backup of the dataset exists. If it does, then issue the HDEL and then recover from the backup and remigrate. This puts HSM and the catalog in sync again. Or even better - RECOVER NEWNAME just to make sure that you can recover before doing HDEL.
If HSM says the dataset is ML1 why do you want to apply FIXSCDS commands to it. Does the corresponding HSMname dataset exist on the ML1 volume specified ? Is there a valid TTOC entry for an ML2 volume for the dataset. |
|
| Back to top |
|
|
tchen40
New User
Joined: 12 Sep 2007
Posts: 30
Location: Los Angeles, Ca
|
|
|
|
HDEL probably works but I definitely didn't want to wipe it out from BOTH the catalog and the MCDS. I did a delete from 3.4 it as a last resort and had to reconstruct the entry (hence the FIXCDS commands). I just wanted to wipe it from the catalog, do a define for the dataset to volume MIGRAT and devtype 3390 (as opposed to 3590 which it had).
There were no easily accessible backups either from HSM nor FDR. I also failed to mention (my fault) than we were trying to recover from corrupted BCDS and MCDS. That's been done from the last viable CDS backup and journals.
It was fun setting bits. Havn't worked on a bit level since coding exits. |
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
I should have added that the only data sets I've ever used HDEL or HMIG on were my own ('userid.xxx.xxx'). I wouldn't recommend it for data sets belonging to someone else unless authorized to do so.  |
|
| Back to top |
|
|
|
|
