Decommissioning an ADS application.
IDMS/ADS
There are many components in a dialog such as maps, process modules, elements and records. Deleting the dialog load modules will not delete the maps, process modules, records and elements.
Start with running ADSORPTS to identify all the dialogs in the dictionary using this JCL:
//ADSORPTS EXEC PGM=ADSORPTS,REGION=0M
//STEPLIB DD DISP=SHR,DSN=hlq.CAGJLOAD
// DD DISP=SHR,DSN=hlq.CUSTOM.LOADLOAD
//SYSJRNL DD DUMMY
//SYSLST DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIDMS DD *
DICTNAME=dictname DMCL=yourdmcl
LOCAL=OFF
DMLTRACE=OFF
//SYSIPT DD *
LIST=WIDE
DIALOG=ALL
/*
From this you can get all the dialog names, processes. records, elements and maps.
Run IDMDDDL with SYSIPT specifying each dialog from the ADSORPTS report:
//SYSIPT DD *
DEL LOAD MODULE dlgname VERSION is N.
DEL PROCESS NAME IS proc-name VERSION is N .
DEL RECORD IS rec-name VERSION is N.
DEL ELE element-name VERSION is N.
/*
You will need one of these statements for each dialog, process, record and element from the ADSORPTS.
To delete the map source run RHDCMAP1 with:
//SYSIPT DD *
DELETE MAP mapname VERSION n.
/*
You will need a DELETE MAP for each map source to be deleted.
To delete a map load module run RHDCMPUT with:
//SYSIPT DD *
PROCESS=DELETE
MAP=mapname VERSION=n
/*
You will need two of these statements for each map load module.
You could skip all this by removing the segments that have the DDLDML and DDLDCLOD for the dictionary that has these dialogs from the DMCL. The DMCL could be altered to exclude the dictionary segments, then generated, punched and linked. The files/datasets could then be deleted.