Peter,
Here is a copy of the procedure I use to delete orphaned vsam files. I
last used this on a z/OS 1.12 system (recently).
Ray Overby
01) Change volser to os format VTOC.
Put in valid job card
//*--------------------------------------------------------------------*
//* FUNCTION: TO CHANGE INDEXED VTOC TO OSVTOC.
//*--------------------------------------------------------------------*
//IX2OS EXEC PGM=ICKDSF,PARM='NOREPLYU'
//SYSPRINT DD SYSOUT=*
//DDCARD DD UNIT=(3390,,DEFER),VOL=(PRIVATE,SER=xxxxxx),DISP=OLD
//SYSIN DD *
BUILDIX DDNAME(DDCARD) NOPURGE OS
/*
//
02) Use TSO ZAP command (CBT file 134) to reset/set bits in data and
index vsam file DSCB's to be sequential files.
ZAP 'FORMAT4.DSCB' VOL(xxxxxx)
F'xxxxxxxx.DDIR.I' <- change to your file name.......
+52
S0200 SET PS
+B
S00 TURN OFF X'10' BIT
03) Get into ISPF 3.4. Specify volser xxxxxx. Use the "D" line command
on the orphaned vsam files. They should delete now.
04) Change volser back to indexed format.
Put in valid job card
//*--------------------------------------------------------------------*
//* FUNCTION: THIS JOB WILL CHANGE A PACK FROM NONINDEX TO INDEX VTOC.
//*--------------------------------------------------------------------*
//OSVTOC EXEC PGM=ICKDSF,PARM='NOREPLYU'
//SYSPRINT DD SYSOUT=*
//DDCARD DD UNIT=(3390,,DEFER),VOL=(PRIVATE,SER=xxxxxx),DISP=OLD,
// DSN=SYS1.VTOCIX.Vxxxxxx
//SYSIN DD *
BUILDIX DDNAME(DDCARD) IX
/*
//
On 12/27/2010 14:25 PM, Farley, Peter x23353 wrote:
I have somehow created a data and index component of a VSAM KSDS that are orphaned from
the cluster name. The cluster was deleted and re-created and now has differently named
data and index components, so I don't think I can "connect" the orphaned
components to that cluster name.
All file creation and deletion was done in batch jobs. The orphaned components
were created using the LIKE operand in an IEFBR14 step.
Neither TSO delete nor IDCAMS batch delete will allow me to remove the
components. IDCAMS complains as follows:
IDC2552I ENTRY TYPE IS INVALID FOR DELETE
IDC0551I ** ENTRY HLQC01.HLQC002.HLQ3.HLQ04.ED0399C7 NOT DELETED
IDC2552I ENTRY TYPE IS INVALID FOR DELETE
IDC0551I ** ENTRY HLQC01.HLQC002.HLQ3.HLQ04.O19KLAD7 NOT DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
The IDC2552I explanation in the Fine Manual only says I can't delete these
entry types but doesn't tell me how I *can* delete them.
Is there any way to delete these orphaned components?
TIA for any help, RTFM, etc. you can provide.
Peter
--
This message and any attachments are intended only for the use of the addressee
and
may contain information that is privileged and confidential. If the reader of
the
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
