JCL

VSAM DELETE using IDCAMS with Examples

In mainframe environments, deleting a VSAM dataset (VSAM DELETE) is not the same as deleting a regular sequential file. VSAM datasets are cataloged objects that often include multiple components, such as a data component and, for KSDS, an index component, so the delete operation is usually performed through IDCAMS. The IDCAMS DELETE command is used to remove VSAM and non-VSAM objects such as CLUSTER, ALTERNATEINDEX, PATH, GDG, USERCATALOG, and other cataloged entries. When you delete a VSAM cluster, the associated data and index components are generally deleted automatically when the cluster entry is deleted.

The DELETE command removes the specified object from the catalog and can also remove the physical dataset from disk, depending on the options used. IBM documents DELETE as a standard Access Method Services operation with examples for different catalog and dataset scenarios.

This command is especially useful when you need to:

Remove an obsolete VSAM file.
Clean up test datasets before redefining them.
Delete non-expired datasets by overriding retention rules with PURGE.
Remove catalog entries for various object types beyond VSAM clusters.

DELETE (entryname[/password][ entryname[/password] ...])
[object-type] 
    [ALIAS  |
    ALTERNATEINDEX  |
    CLUSTER  |
    GENERATIONDATAGROUP  |
    NONVSAM  |
    PAGESPACE  |
    PATH  |
    SPACE  |
    USERCATALOG]
[optional-paramter]
    [ERASE  |  NOERASE]
    [FILE(ddname)]
    [FORCE  |  NOFORCE]
    [PURGE  |  NOPURGE]
    [SCRATCH  |  NOSCRATCH]
    [CATALOG(catname[/password])]

The most important parts are:

entryname: The dataset or catalog entry you want to delete.
CLUSTER: Explicitly identifies the object as a VSAM cluster.
FILE(ddname): Lets you refer to a DD statement instead of coding the dataset name directly.
PURGE: Deletes the entry even if the retention period has not expired.
SCRATCH: Removes both the catalog entry and the VTOC entry for the dataset.
ERASE: Overwrites the components with binary zeroes before deletion.

Important Parameters –

Understanding the options is critical because DELETE behavior changes based on the parameters you use. The defaults are not always what a beginner expects.

Parameter	Meaning
`PURGE`	Deletes the entry even if the dataset has not expired.
`NOPURGE`	Prevents deletion if the retention period is still active; this is the default.
`SCRATCH`	Removes the dataset from both the catalog and the VTOC.
`NOSCRATCH`	Removes only the catalog entry, not the physical dataset entry in the VTOC.
`ERASE`	Overwrites cluster or alternate index components with binary zeroes.
`NOERASE`	Deletes without overwriting the components.
`FORCE`	Allows deletion of some object types such as non-empty GDGs or user catalogs.
`NOFORCE`	Stops deletion for eligible object types when they are not empty; this is generally the default behavior.

VSAM DELETE to delete KSDS File

Below is a simple example of deleting a KSDS using IDCAMS. One published example uses a DD name and the FILE parameter, along with PURGE.

//VSAMDELT JOB (1234),'INDUS',CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1),
//             NOTIFY=&SYSUID,REGION=6M                         
//*************************************************************
//* SAMPLE JCL DELETE VSAM DATASET
//*************************************************************
//STEP01  EXEC PGM=IDCAMS
//SYSPRINT  DD SYSOUT=*
//INPUT    DD   DSNAME=userid.KSDS.INPUT,DISP=SHR
//SYSIN    DD   *
   DELETE FILE (INPUT)   -
   PURGE
/*

In this example, IDCAMS deletes the VSAM dataset referenced by the INPUT DD statement. The PURGE keyword is used so the delete can proceed even if the dataset has not yet reached its expiration date.

VSAM DELETE to delete ESDS File

You can also delete an ESDS by specifying the cluster name directly in SYSIN. A documented example shows the dataset name coded directly on the DELETE statement.

//VSAMDELT JOB (1234),'INDUS',CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1),
//             NOTIFY=&SYSUID,REGION=6M                         
//*************************************************************
//* SAMPLE JCL DELETE ESDS DATASET
//*************************************************************
//STEP01   EXEC PGM=IDCAMS                             
//SYSPRINT DD SYSOUT=*                                 
//SYSIN    DD *                                        
     DELETE XXXXXX.YYYYYY.VSAMFILE.MSTR           
/*

When a cluster is deleted this way, its associated components, such as .DATA and .INDEX, are also removed automatically where applicable. That is why deleting the cluster name is usually enough for KSDS, ESDS, and RRDS cleanup.

Note: When you delete this CLUSTER all associated data components and index components will be deleted automatically.

VSAM DELETE using CLUSTER Keyword

Some installations prefer writing the object type explicitly for readability and control. A common form is:

//STEP1 EXEC PGM=IDCAMS 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD *  
  DELETE SAMPLE.DATA.VSAM CLUSTER 
/*

Using CLUSTER makes the command intent clear, especially in jobs that also handle alternate indexes, paths, or non-VSAM datasets. This style is often seen in reusable delete/define jobs where a VSAM cluster is dropped and recreated in later steps.

Common Use Case: Delete Before Define

A very common pattern in batch jobs is to delete a VSAM file before redefining it. This avoids failures when a previous run has already created the cluster.

For example, a job flow may:

Delete the existing VSAM cluster.
Define the cluster again with IDCAMS.
Load records using REPRO or an application program.

This pattern is useful in development, testing, and restartable batch processes because it keeps the setup repeatable.

Notes and Best Practices

A few practical points matter when using DELETE in production jobs:

Deleting the cluster is normally sufficient; you do not usually delete the .DATA and .INDEX components separately after the cluster is removed.
If the dataset is not expired, DELETE can fail unless you specify PURGE.
SCRATCH and NOSCRATCH affect whether only the catalog entry is removed or whether the physical dataset entry is removed as well.
ERASE is more secure but may take more time because the components are overwritten with binary zeroes.

It is also a good idea to review the SYSPRINT output after execution. IDCAMS messages help confirm whether the cluster entry, data component, and index component were deleted successfully. IBM and community examples show DELETE usage in jobs where output messages are used to verify completion and handle conditions.

Troubleshooting

If the delete fails, the most common reasons are:

The dataset name is incorrect or does not exist in the catalog.
The dataset has not expired and PURGE was not specified.
The object type is not what you coded, for example deleting a PATH or AIX as if it were a CLUSTER.
Security rules or catalog authority prevent deletion. In enterprise environments, delete authority may depend on dataset or catalog permissions.

Another point of confusion is the difference between deleting a VSAM dataset and deleting records inside a VSAM dataset. IDCAMS DELETE removes the dataset object itself, while record-level deletion is a different task handled by application logic or utilities such as DFSORT/ICETOOL patterns, not by dropping the cluster.

VSAM Tutorials

VSAM Define Cluster: Click Here IBM Reference : Click Here

Admin

Next VSAM EXPORT-IMPORT using IDCAMS with Examples »

Previous « VSAM VERIFY EXAMINE using IDCAMS with Examples

Published by

Admin

Tags: DELETEVSAM DELETE

6 years ago

OUTER JOIN Queries: Common Errors and Resolutions
OUTER JOIN Queries are a valuable tool in SQL, allowing you to retrieve data from…
OUTREC control statement use in SORT
OUTREC control statement is used to reformat (adds, deletes, or reformats fields) each record after…
ICETOOL Utilities and Operations with Examples
DFSORT is your go‑to utility for sorting, merging, and transforming data. ICETOOL Utilities takes DFSORT…