The DELETE macro cancels the effect of a previous LOAD macro. If DELETE cancels the only outstanding LOAD request for the module, and no other requirements exist for the module, the virtual storage occupied by the load module is released and is available for reassignment by the control program.

In the case of nonreentrant and nonreusable modules loaded multiple times, the order of processing occurs in last-loaded first-deleted order. For example, if Program A loads module LOADMODA, then calls Program B, which also loads LOADMODA, then issues a DELETE against LOADMODA, the copy of the load module to be deleted is the one associated with Program B. At this point, a copy of LOADMODA will still exist. The next DELETE request against LOADMODA will delete that copy, regardless of whether Program A or Program B issues the request.

The entry name specified in the DELETE macro must be the same as that specified in the LOAD macro that brought the load module into storage. Also, the DELETE macro must be issued by the same task that issued the LOAD macro.

Any module loaded by a task will not be removed from virtual storage until the DELETE macro is issued or end of task is reached. In addition, any module loaded by a system task will not be removed from virtual storage until a DELETE macro is issued by a system task or end of task is reached.