INQUIRE CLASSCACHE

Retrieve information about the shared class cache in the CICS region, and report the presence of any old shared class caches that are awaiting deletion.

Read syntax diagramSkip visual syntax diagramINQUIRE CLASSCACHE
 
>>-INQUIRE CLASSCACHE--+-----------------------+---------------><
                       +-AUTOSTARTST(cvda)-----+
                       +-CACHEFREE(data-area)--+
                       +-CACHESIZE(data-area)--+
                       +-OLDCACHES(data-area)--+
                       +-PHASINGOUT(data-area)-+
                       +-PROFILE(data-area)----+
                       +-REUSEST(cvda)---------+
                       +-STARTTIME(data-area)--+
                       +-STATUS(cvda)----------+
                       '-TOTALJVMS(data-area)--'
 

Conditions: NOTAUTH

For more information about the use of CVDAs, see CICS-value data areas (CVDAs).

Description

The INQUIRE CLASSCACHE command returns information about the shared class cache in the CICS region. There can be only one active shared class cache in a CICS region, therefore no name or identifier is required on this command.

Options

AUTOSTARTST(cvda)
returns a CVDA value indicating the status of autostart for the shared class cache. CVDA values are:
ENABLED
If the shared class cache has been stopped by an explicit command 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 by an explicit command or has not yet been started on this CICS execution, an explicit EXEC CICS PERFORM CLASSCACHE INITIALIZE(START) command (or the equivalent CEMT 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.
CACHEFREE(data-area)
returns a doubleword binary value representing the amount of free space in the shared class cache, in bytes.
CACHESIZE(data-area)
returns a doubleword binary value representing the size of the shared class cache, in bytes. If the status of the shared class cache is STOPPED, this option returns the size that will be used by default when the shared class cache is started. If the status of the shared class cache is STARTING or STARTED, this option returns the size of the current shared class cache. If the status of the shared class cache is RELOADING, this option returns the size of the new shared class cache that is being loaded.
OLDCACHES(data-area)
returns a fullword binary value giving the number of old shared class caches that are still present in the region because they are waiting for worker JVMs that are dependent on them to be phased out. If the status of the current shared class cache is STOPPED, and worker JVMs are still dependent on it, then that shared class cache is included in the number of old shared class caches.
PHASINGOUT(data-area)
returns a fullword binary value giving the number of worker 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 worker JVMs that are still dependent on it are included in the number of worker JVMs being phased out.
PROFILE(data-area)
If the status of the shared class cache is STOPPED, this option returns 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.
REUSEST(cvda)
returns a CVDA value indicating the level of reusability for the master JVM that initializes the shared class cache. All the worker JVMs in a CICS region inherit their level of reusability from the master JVM. CVDA values are:
RESET
The master JVM and worker JVMs are resettable.
REUSE
The master JVM and worker JVMs are continuous.
UNKNOWN
The level of reusability for the master JVM and worker JVMs is not known, because the shared class cache is not started.
STARTTIME(data-area)
returns the time when the current shared class cache was started. The time is in ABSTIME format, which is an 8-byte packed decimal field containing the time since 00:00 hours on 1 January 1900 (in milliseconds rounded to the nearest hundredth of a second). You can convert this absolute date and time to an alternative format by using the FORMATTIME command.
STATUS(cvda)
returns the status of the current shared class cache. CVDA values are:
STARTING
The shared class cache is being initialized. If autostart is enabled, the shared class cache is starting either because CICS received a request to run a Java application in a JVM whose profile requires the use of the shared class cache, or because an explicit EXEC CICS PERFORM CLASSCACHE INITIALIZE(START) command (or the equivalent CEMT command) was issued. If autostart is disabled, the shared class cache is starting because an explicit EXEC CICS PERFORM CLASSCACHE INITIALIZE(START) command (or the equivalent CEMT command) was issued. Worker JVMs that require the use of the shared class cache must 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 worker JVMs fail.
STARTED
The shared class cache is ready, and it can be used by worker JVMs.
RELOADING
An EXEC CICS PERFORM CLASSCACHE INITIALIZE(RELOAD) command (or the equivalent CEMT command) has been issued, and a new shared class cache is being loaded to replace the existing shared class cache. Worker 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.
STOPPED
The shared class cache has either not been initialized on this CICS execution, or it has been stopped by an EXEC CICS PERFORM CLASSCACHE TERMINATE command or an EXEC CICS SET JVMPOOL TERMINATE command (or the equivalent CEMT commands). 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 worker JVMs) will fail. If autostart is enabled, a new shared class cache will be initialized 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.
TOTALJVMS(data-area)
returns a fullword binary value giving the number of worker JVMs in the CICS region that are dependent on a shared class cache. This includes both the worker JVMs that are dependent on the current shared class cache, and any worker JVMs that are dependent on an old shared class cache and are being phased out.

Conditions

NOTAUTH
RESP2 value:
100
The user associated with the issuing task is not authorized to use this command.
[[ Contents Previous Page | Next Page Index ]]