If you don't have a tool like Trex to either correct the VVDS to BCS entries or
delete the entries you can always try IDCAMS DELETE NVR for non vsam and DELETE
VVR for VSAM (SMS)
//L EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//INVOL0 DD DISP=OLD,UNIT=3390,VOL=SER=xxxxxx
//SYSIN DD *
DEL 'HLQ.MLQ.LLQ' -
FILE(INVOL0) VVR
or
//DELETE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//DD1 DD DSN=HLQ.MLQ.LLQ,
// DISP=SHR,UNIT=3390,VOL=SER=XXXXXX
//SYSIN DD *
DELETE FILE(DD1) -
CATALOG('CATALOG.NAME') NVR
many some iteration of this may help
Carmen
----- Original Message -----
From: "Kirk Wolf" <[email protected]>
To: [email protected]
Sent: Wednesday, August 23, 2017 11:24:02 AM
Subject: SMS dataset woes
I would appreciate some advice on a problem that I'm having on a
development system.
We copied some volumes from an old machine, where the data sets where SMS
managed to a new system where SMS is really not set up and we would prefer
to keep it that way.
We exported the old usercat that had the datasets on these volumes and then
imported it to a new usercat on the new system, which worked fine.
But the problem is that we can't delete any of the old datasets, since they
still have the old SMS "storclass" in the VVDS (I think).
- ISPF delete just says "Deallocation failed"
- TSO/IDCAMS delete does this:
delete ftp.data
IDC0550I ENTRY (A) LISA.FTP.DATA DELETED
IDC3014I CATALOG ERROR+
IDC3009I VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS IGG0CLFO-88
IDC0551I ENTRY LISA.FTP.DATA NOT DELETED
IDC0014I LASTCC=8
RC(8)
So the data set is uncataloged, but remains on the volume and the VVDS.
This error is documented here:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieam600/bb3009i.htm
*88* *Explanation:* A VVR or NVR with the correct component name was found,
but the catalog name did not match. On a delete request, the BCS record
will be deleted, but the VVR or NVR and the format 1 DSCB will not be
scratched. There is no SFI data.
*Programmer Response:* No action is required because this code is for
information only.
Does anyone have any suggestions other than to try to migrate the missing
SMS definitions? We have crap for skills and that area, so an alternative
would be appreciated.
One workaround would be something that would scratch an uncataloged SMS
dataset (and remove from the VVDS). Will IEHPROGM do this? It doesn't
seem like it:
SCRATCH DSNAME=LISA.JOB.LOG,VOL=3390=(VPWRKB),PURGE
IEH207I STATUS OF USERS REQUEST TO SCRATCH DATA SET LISA.JOB.LOG
VOLUME I.D. ACTION TAKEN REASON FOR TAKING THIS ACTION
ERROR
VPWRKB NONE CORRECT PASSWORD NOT AVAILABLE
***
Thanks for any help...
Kirk Wolf
Dovetailed Technologies
http://dovetail.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
