Installing deployed JAR files

How to install deployed JAR files using the CICS® scanning mechanism is described in Defining deployed JAR files using the CICS scanning mechanism.

Note:
  1. For performance reasons, CICS installs DJAR definitions in two stages. On receipt of an install request, CICS puts the resource into a pending state. Subsequently, possibly after CICS initialization has ended, CICS completes the installation of any pending resources. If this secondary installation stage (which involves copying the deployed JAR file to the HFS shelf directory and parsing the information it contains) fails, the state of the DJAR becomes UNRESOLVED or UNUSABLE. CICS outputs a message to indicate what is wrong with the JAR file. The message is sent to the CICS log and to the “EJB event” user-replaceable program.
  2. For statically-installed DJARs (those installed from a CSD or by means of CREATE DJAR), installation of the DJAR fails if the deployed JAR file contains a bean with the same name as a bean which is already installed in the specified CorbaServer.
    For dynamically-installed DJARs (those installed by the scanning mechanism), installation of the DJAR fails if:
    1. The deployed JAR file contains a bean with the same name as a bean which is already installed in the specified CorbaServer, and the HFS file names of the two deployed JAR files—the one containing the original bean and the newly-installed one—are different. (If they are the same (but with a different date-and-time stamp), CICS treats the newly-deployed JAR file as an update to the previously-installed version.)

    CICS outputs a message to indicate what is wrong with the JAR file. The message is sent to the CICS log and to the “EJB event” user-replaceable program.

  3. CSD-installed DJAR definitions must be either in the same group as the CORBASERVER definition to which they refer, or in a group that is installed after the group containing the referenced CORBASERVER definition.
  4. When you install a DJAR, CICS checks related resources for consistency:
    • At the end of GROUPLIST installation during CICS initialization.
    • After a group containing a DJAR is installed. In this case, related CORBASERVERs must either be installed before the group containing the DJAR, or as part of the same group.
    • After a DJAR is installed as an individual resource. In this case, related CORBASERVERs must be installed before the DJAR.
  5. To update a static DJAR definition—that is, to replace an existing CSD-installed definition by installing another of the same name—you must first discard the existing definition.
  6. LASTMODTIME, DATESTAMP, and TIMESTAMP are readonly attributes that CICS updates when the DJAR resource is installed or updated; they do not appear on the DEFINE DJAR panel. They can be used to determine whether CICS has refreshed itself after an update is made to a JAR in the pickup directory. The last-modified-time (LASTMODTIME) is a packed-decimal value accessible through the EXEC CICS or CECI INQUIRE DJAR command. The date and time stamps show the same date-and-time information in human-readable form; they are accessible through the CEMT INQUIRE DJAR transaction.