Remove the definition of a specified deployed JAR file from the system, together with any associated beans.
The DISCARD DJAR command removes the definition of a deployed JAR file from the system, together with the shelf copy of the deployed JAR file and the beans it contains. The current set of JVM instances are marked for termination, so that each JVM instance will not be reused after it terminates. New JVM instances load all their classes and do not use old versions of classes whose bytecodes have been replaced.
The copy of the deployed JAR file that was created when the deployed JAR file was installed is deleted from the CorbaServer's shelf.
Passivated stateful session bean instances are not deleted by this operation because, in a workload-managed CICS EJB server, they could be activated by other AORs .
References to the homes of enterprise beans in the deployed JAR file are not retracted from the namespace because other AORs might still have the homes installed. However, before discarding a deployed JAR file from the last AOR in which it is installed, you might wish to issue a PERFORM DJAR RETRACT command to retract references to home interfaces.