JVM class cache - CLCACHE

The JVM class cache (CLCACHE) views display information about shared class caches for pooled JVMs in the CICS address space.

Supplied views

To access from the main menu, click:

CICS operations views > Enterprise Java component operations views > JVM class cache

Table 1. Views in the supplied JVM class cache (CLCACHE) view set
View Notes
JVM class cache

EYUSTARTCLCACHE.DETAILED

Detailed information about a selected class cache.
JVM class cache

EYUSTARTCLCACHE.FORCEPURGE

Stop and delete the selected shared class cache. All tasks using pooled JVMs dependent on the shared class cache are terminated by the FORCEPURGE mechanism, and the pooled JVMs are terminated. No more JVMs can use the shared class cache, and it is deleted when all the pooled JVMs that were dependent on it have been terminated.
JVM class cache

EYUSTARTCLCACHE.PHASEOUT

Stop and delete the selected shared class cache. All pooled JVMs using the shared class cache are marked for deletion. The JVMs are actually deleted when they finish running their current Java programs. No more JVMs can use the shared class cache, and it is deleted when all the pooled JVMs that were dependent on it have been terminated.
JVM class cache

EYUSTARTCLCACHE.PURGE

Stop and delete the selected shared class cache. All tasks using pooled JVMs dependent on the shared class cache are terminated by the PURGE mechanism, and the pooled JVMs are terminated. No more JVMs can use the shared class cache, and it is deleted when all the pooled JVMs that were dependent on it have been terminated.
JVM class cache

EYUSTARTCLCACHE.RELOAD

Reload the selected shared class cache. Perform this operation to create a new class cache when the status of the shared class cach is STARTED (the option works only if the shared class cache has been started). If newer versions of Java classes are available to be loaded, the new class cache uses them. However, pooled JVMs, both those that are already allocated to tasks and those that are allocated to tasks after you issue the command, continue to use the existing shared class cache and the old versions of the Java classes until the new shared class cache is ready. When the new shared class cache is ready, subsequent requests for pooled JVMs are given a pooled JVM that uses the new cache. These new pooled JVMs are started as they are requested by applications, and they replace the pooled JVMs that are using the old shared class cache. The pooled JVMs that are using the old shared class cache are allowed to finish running their current Java programs, and then they are terminated. The old shared class cache is deleted when all the pooled JVMs that are dependent on it have been terminated.
JVM class cache

EYUSTARTCLCACHE.START

Start the selected shared class cache. Perform this operation to create a new class cache when the status of the shared class cache is STOPPED.
JVM class cache

EYUSTARTCLCACHE.TABULAR

Tabular information about shared class caches in the CICS address space.

Actions

Table 2. Actions available for CLCACHE views
Action Description
FORCEPURGE Stop and delete the selected shared class cache. All tasks using pooled JVMs dependent on the shared class cache are terminated by the FORCEPURGE mechanism, and the pooled JVMs are terminated. No more JVMs can use the shared class cache, and it is deleted when all the pooled JVMs that were dependent on it have been terminated.
PHASEOUT Stop and delete the selected shared class cache. All pooled JVMs using the shared class cache are marked for deletion. The JVMs are actually deleted when they finish running their current Java programs. No more JVMs can use the shared class cache, and it is deleted when all the pooled JVMs that were dependent on it have been terminated.
PURGE Stop and delete the selected shared class cache. All tasks using pooled JVMs dependent on the shared class cache are terminated by the PURGE mechanism, and the pooled JVMs are terminated. No more JVMs can use the shared class cache, and it is deleted when all the pooled JVMs that were dependent on it have been terminated.
RELOAD Reload the selected shared class cache. Perform this operation to create a new class cache when the status of the shared class cach is STARTED (the option works only if the shared class cache has been started). If newer versions of Java classes are available to be loaded, the new class cache uses them. However, pooled JVMs, both those that are already allocated to tasks and those that are allocated to tasks after you issue the command, continue to use the existing shared class cache and the old versions of the Java classes until the new shared class cache is ready. When the new shared class cache is ready, subsequent requests for pooled JVMs are given a pooled JVM that uses the new cache. These new pooled JVMs are started as they are requested by applications, and they replace the pooled JVMs that are using the old shared class cache. The pooled JVMs that are using the old shared class cache are allowed to finish running their current Java programs, and then they are terminated. The old shared class cache is deleted when all the pooled JVMs that are dependent on it have been terminated.
SET Set the status of autostart for the shared class cache.
START Start the selected shared class cache. Perform this operation to create a new class cache when the status of the shared class cache is STOPPED.

Fields

Table 3. Fields in CLCACHE views
Field Attribute name Description
Autostart status AUTOSTARTST The status of autostart for the shared class cache. The values are:
  • Enabled
    • If the shared class cache has been stopped or has not yet been started on this CICS execution, the shared class cache is started as soon as CICS receives a request to run a Java application in a JVM whose profile requires the use of the shared class cache.
  • Disabled
    • If the shared class cache has been stopped or has not yet been started on this CICS execution, an explicit PERFORM CLASSCACHE Start command is required to start it. If the status of the shared class cache is Stopped and autostart is disabled, and CICS receives a request to run a Java application in a JVM whose profile requires the use of the shared class cache, the request fails.
Amount in bytes of free space within the cache CACHEFREE The amount of free space in the shared class cache, in bytes.
Size of the class cache in bytes CACHESIZE If the status of the shared class cache is Starting or Started, this is the size of the current shared class cache. If the status of the shared class cache is the shared class cache is Reloading, this is the size of the new shared class cache that is being loaded.
JVM requests - class cache JVMREQSCACHE The total number of Java programs which requested a JVM that uses the shared class cache.
Number of class caches waiting for JVMs to terminate OLDCACHES The number of old shared class caches that are still present in the region because they are waiting for pooled JVMs that are dependent on them to be phased out. If the status of the current shared class cache is Stopped, and pooled JVMs are still dependent on it, then that shared class cache is included in the number of old shared class caches.
Peak pooled (class cache) JVMs PEAKCACHEJVM The peak number of JVMs in the JVM pool that used the shared class cache.
Number of JVMs being phased-out PHASINGOUT The number of pooled JVMs that are dependent on an old shared class cache, and are being phased out. If the status of the current shared class cache is Stopped, then any pooled JVMs that are still dependent on it are included in the number of pooled JVMs being phased out.
Profile used to start or used to reload the cache PROFILE

Applies only to releases earlier than CICS Transaction Server for z/OS Version 4 Release 1. PROFILE is obsolete in later releases.

If the status of the shared class cache is Stopped, this displays the eight-character name of the JVM profile that will be used for a master JVM to start the shared class cache. If the status of the shared class cache is Started, Starting or Reloading, this displays the eight-character name of the JVM profile that was used for the last valid request to start or reload the shared class cache. This name is displayed even if the shared class cache fails to start or reload. The displayed JVM profile is used next time you issue the command to start or reload the shared class cache, unless you specify a different JVM profile using the Profile option.

JVM reuse status REUSEST For CICS TS 3.2 and later regions, the master JVM that initializes the shared class cache is always a continuous (reusable) JVM. This option indicates the reuse status of the master JVM as follows:
  • Reuse
    • The master JVM and pooled JVMs are continuous.
  • Reset
    • The master JVM and pooled JVMs are resettable.
  • Unknown
    • The class cache is not started. Although CICS cannot identify the reuse status in this situation, the status always becomes Reuse when the shared class cache is started.
The time that the class cache was started STARTTIME The date and time when the current shared class cache was started. This time is expressed as local time.
Class cache status STATUS The status of the current shared class cache. The values are:
  • Started
    • The class cache is ready, and it can be used by pooled JVMs.
  • Stopped
    • The class cache has either not been initialized on this CICS execution, or it has been stopped by a PERFORM CLASSCACHE Phaseout, Purge or Forcepurge command. If autostart is disabled, requests to run a Java application in a JVM whose profile requires the use of the shared class cache (that is, requests for pooled JVMs) will fail.
  • Starting
    • The shared class cache is being initialized, either through the autostart facility or because an explicit Start command was issued. While the shared class cache is starting, pooled JVMs that require the use of the shared class cache wait until the startup process is complete and the shared class cache is ready. If initialization of the shared class cache is unsuccessful, any waiting requests for pooled JVMs fail.
  • Reloading
    • A reload command has been issued, and a new shared class cache is being loaded to replace the existing shared class cache. While the shared class cache is reloading, pooled JVMs, both those that were already allocated to tasks and those that were allocated to tasks after the command was issued, continue to use the existing shared class cache until the new shared class cache is ready.
Number of JVMs dependent on the class cache TOTALJVMS The number of pooled JVMs in the CICS region that are dependent on a shared class cache. This includes both the pooled JVMs that are dependent on the current shared class cache, and any pooled JVMs that are dependent on an old shared class cache and are being phased out.


eyua3clcache.html | Timestamp icon Last updated: Sunday, 4 June 2017