Discarding resource definitions

The DISCARD command deletes the definition of a resource installed in the local CICS system, so that the system no longer has access to the resource, or makes a model ineligible for use as a model.

It reverses the effect of the installation of the resource, which can occur at system startup, through a subsequent CREATE command or CEDA transaction, by an automatic installation process, or by a CICSPlex SM BAS command.

Each DISCARD command removes the definition of one resource. You can remove definitions for the following types of resources:
  • Atom feeds
  • Autoinstall models for terminals
  • Bundles
  • Connections
  • CorbaServer (CORBASERVER)
  • DB2Conns
  • DB2Entrys
  • DB2Trans
  • Deployed JAR files (DJAR)
  • Document templates
  • ENQ models
  • Files
  • IPIC connections
  • Journals and journal models
  • LIBRARY concatenations
  • WebSphere MQ connections
  • Partners
  • PIPELINEs
  • Process types
  • Profiles
  • Programs, map sets, and partition sets
  • Request models
  • TCP/IP service
  • Temporary storage queue models
  • Terminals
  • Transaction classes
  • Transactions
  • Transient data queues
  • URIMAPs
  • WEBSERVICEs

You cannot discard a resource that is currently in use. For example, you cannot discard a PROFILE definition if some installed TRANSACTION definition still points to it, or a FILE that is open, or a TRANSACTION that is scheduled for execution.

In addition, some resources are not eligible for discard at all. These include resources whose names begin with the letters DFH (reserved for CICS-supplied definitions), and transactions whose names begin with C (also reserved for CICS).

You cannot discard EP adapters, EP adapter sets, or event bindings. This type of resource can only be discarded by using the DISCARD BUNDLE command.

Some DISCARD commands cause a syncpoint on behalf of the issuing task, as the CREATE commands do. For these commands, the discussion of syncpoint considerations on page Creating resource definitions, applies.

DISCARD commands are recorded in the CICS catalog, so that their effects persist over a warm or emergency restart, but they do not modify the CSD file and are therefore lost on a cold or initial start.