Delete an OAM Collection Name Catalog Entry: Example 16

In this example, an OAM non-VSAM collection name entry is deleted from a catalog. A FILE parameter and its associated DD statement are provided to allocate the volume where the catalog containing the collection name entry is located.

//DELET15    JOB    ...
//STEP1      EXEC   PGM=IDCAMS
//DD1        DD     VOL=SER=VSER01, UNIT=3380, DISP=OLD
//SYSPRINT   DD     SYSOUT=A
//SYSIN      DD     *
     DELETE -
             OAM.COLLECTION.NONVSAM -
             FILE (DD1) -
             PURGE -
             NOSCRATCH -
             CATALOG(COLNCAT)
/*

The DELETE command deletes the non-VSAM collection name entry from the catalog. Its parameters are:

OAM.COLLECTION.NONVSAM is the name of the collection name entry in the catalog.
FILE specifies the DD statement within the JCL that locates the volume where the catalog containing the collection name entry marked for deletion resides.
PURGE specifies that the retention period for the non-VSAM collection name entry be ignored.
NOSCRATCH specifies that only the collection name entry on the catalog be deleted.
CATALOG identifies the catalog where the collection name entry marked for deletion resides is COLNCAT. If you are trying to delete SMS-managed entries, you must have RACF® ALTER authority.

There must be synchronization between the OAM collection name entries in the catalog and the OAM DB2® Administration Database. Deleting a collection name entry from the catalog will not delete the corresponding entry from the OAM DB2 Administration Database. The above DELETE command should be used in recovery situations to ensure synchronization between the catalog and the OAM DB2 Administration Database.