CEMT PERFORM commands

The CEMT PERFORM commands are not concerned with resource status. They are used to:

Descriptions of the CEMT PERFORM commands follow in alphabetic order. The operands for each of the commands are also presented in alphabetic order.

CEMT PERFORM CLASSCACHE

Function

You can use the PERFORM CLASSCACHE command to initialize (start or reload) and terminate (phase out, purge or forcepurge) the shared class cache. While you are performing one of these operations, you can use other options on the command to set attributes of the shared class cache, as follows:

Description

The PERFORM CLASSCACHE command is intended to operate on the active shared class cache in the CICS region. The Start and Reload operations only affect this shared class cache. The Phaseout, Purge and Forcepurge operations, however, also act on any 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. For example, if you issue a CEMT PERFORM CLASSCACHE Forcepurge command, all tasks using worker JVMs dependent on a shared class cache are forcepurged, both those dependent on the current shared class cache and those dependent on old shared class caches. Note, though, that JVMs running independently of the shared class cache are not affected by the CEMT PERFORM CLASSCACHE Phaseout, Purge and Forcepurge commands.

When you have issued one command to terminate the shared class cache, you can repeat the CEMT PERFORM CLASSCACHE command to make a stronger attempt to purge the tasks using the JVMs (for example, by using Purge instead of Phaseout). However, you should only repeat the command if autostart for the shared class cache is disabled. If autostart is enabled, and you repeat the command to terminate the shared class cache, the command could operate on the new shared class cache that has been started by the autostart facility, and terminate it.

When you use the Cachesize, Profile and Autostartst options, the new settings override the size, JVM profile and autostart status that were originally set by the system initialization parameters JVMCCSIZE, JVMCCPROFILE and JVMCCSTART. Subsequent CICS restarts use the most recent settings that you made using the PERFORM CLASSCACHE command (or the SET CLASSCACHE command), unless the system is INITIAL or COLD started, or the system initialization parameters are specified as overrides at startup. In these cases, the settings from the system initialization parameters are used.

Syntax

Read syntax diagramSkip visual syntax diagramCEMT PERFORM CLASSCACHE
 
>>-CEMT Perform CLasscache-------------------------------------->
 
>--+-+-Start--+-+-------------------+-+---------------+-+------><
   | '-Reload-' '-Cachesize(number)-' '-Profile(name)-' |
   '-+-PHaseout---+-+----------+------------------------'
     +-PUrge------+ +-Enabled--+
     '-Forcepurge-' '-Disabled-'
 

Options

The operations you can perform with the PERFORM CLASSCACHE command are:

Forcepurge
stops and deletes the shared class cache. All tasks using worker JVMs dependent on the shared class cache are terminated by the SET TASK FORCEPURGE mechanism, and the worker JVMs are terminated. No more JVMs can use the shared class cache, and it is deleted when all the worker JVMs that were dependent on it have been terminated.

If autostart is enabled for the shared class cache, a new shared class cache is started as soon as a new JVM requests it. If autostart is disabled, the CEMT PERFORM CLASSCACHE Start command (or the equivalent EXEC CICS command) must be entered if you want to start a new shared class cache. If you do not restart the shared class cache, requests to run a Java application in a JVM whose profile requires the use of the shared class cache will fail. Specify the Autostartst option to set the status of autostart.

Phaseout
stops and deletes the shared class cache. All worker 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 worker JVMs that were dependent on it have been terminated.

If autostart is enabled for the shared class cache, a new shared class cache is started as soon as a new JVM requests it. If autostart is disabled, the CEMT PERFORM CLASSCACHE Start command (or the equivalent EXEC CICS command) must be entered if you want to start a new shared class cache. If you do not restart the shared class cache, requests to run a Java application in a JVM whose profile requires the use of the shared class cache will fail. Specify the Autostartst option to set the status of autostart.

Purge
stops and deletes the shared class cache. All tasks using worker JVMs dependent on the shared class cache are terminated by the SET TASK PURGE mechanism, and the worker JVMs are terminated. No more JVMs can use the shared class cache, and it is deleted when all the worker JVMs that were dependent on it have been terminated.

If autostart is enabled for the shared class cache, a new shared class cache is started as soon as a new JVM requests it. If autostart is disabled, the CEMT PERFORM CLASSCACHE Start command (or the equivalent EXEC CICS command) must be entered if you want to start a new shared class cache. If you do not restart the shared class cache, requests to run a Java application in a JVM whose profile requires the use of the shared class cache will fail. Specify the Autostartst option to set the status of autostart.

Reload
reloads the shared class cache. Perform this operation to create a new class cache when the status of the shared class cache is STARTED (the option only works if the shared class cache has been started). If specified, the Cachesize and Profile options are used in the creation of the cache. If newer versions of Java classes are available to be loaded, the new class cache uses them. However, worker 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 worker JVMs are given a worker JVM that uses the new cache. These new worker JVMs are started as they are requested by applications, and they replace the worker JVMs that are using the old shared class cache. The worker 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 worker JVMs that are dependent on it have been terminated.
Start
starts the shared class cache. Perform this operation to create a new class cache when the status of the shared class cache is STOPPED. If specified, the Cachesize and Profile options are used in the creation of the shared class cache.

The additional options that you can use on the PERFORM CLASSCACHE command to set attributes of the shared class cache are:

Cachesize(number)
If you are performing the Start operation, you can use Cachesize to specify the size of the shared class cache that is to be started. If you are performing the Reload operation, you can use Cachesize to specify the size of the new shared class cache that is to be loaded. You can specify the size in bytes, or in kilobytes (K), megabytes (M) or gigabytes (G). For example, specifying 20M sets the size of the shared class cache to 20 megabytes. The number you specify can be up to 20 digits.
Disabled
If you are performing the Phaseout, Purge or Forcepurge operations, you can use this option to set the status of autostart for the shared class cache to Disabled. When autostart is disabled, an explicit CEMT PERFORM CLASSCACHE Start command (or the equivalent EXEC CICS command) is required to start the shared class cache. 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.
Enabled
If you are performing the Phaseout, Purge or Forcepurge operations, you can use this option to set the status of autostart for the shared class cache to Enabled. When autostart is enabled, 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.
Profile(name)
If you are performing the Start operation, you can use Profile to specify the eight-character name of the JVM profile that will be used for the master JVM that starts the shared class cache. If you are performing the Reload operation, you can use Profile to specify the eight-character name of the JVM profile that will be used for the master JVM that loads the new shared class cache.

When you use the name of a JVM profile anywhere in CICS, you must enter it using the same combination of upper and lower case characters that is present in the HFS file name. If you need to enter the name of a JVM profile in mixed case when you are using the CEMT transaction, ensure that the terminal you use is correctly configured, with upper case translation suppressed.

If the Start or Reload command is successfully executed but the master JVM fails to start, CICS retains the JVM profile name that you specify, and displays it as the JVM profile for the master JVM. Next time you issue the command to start or reload the shared class cache, the new JVM profile will be used, unless you change it again using the Profile option.

CEMT PERFORM CORBASERVER

Function

The PERFORM CORBASERVER command allows you to:

If no action is specified, the command has no effect.

You can issue a PERFORM CORBASERVER command only when the CorbaServer is in a steady state--that is, when it is in ENABLED or DISABLED state, but not when it is in ENABLING, DISABLING, or DISCARDING state.

In addition to the traditional DFSMS-managed data sets, such as partitioned data sets (PDS), CICS requires access to z/OS UNIX System Services and the hierarchical file store (HFS) in order to launch a JVM. This requires that the CICS region userid is authorized to z/OS UNIX System Services to enable CICS to access the required HFS directories, such as those specified on the JVMPROPS, LIBPATH, and CLASSPATH parameters.

Description

A failure to perform the requested action will be reported by returning a condition and RESP2 value from the command and, in certain cases, by writing messages to CSMT. The requested action may have beens partially successful since a failure does not cause the effects of the command to be backed out. Also, failure does not necessarily stop the command from continuing in order to increase the extent to which it was partially successful.

Syntax

Read syntax diagramSkip visual syntax diagramCEMT PERFORM CORBASERVER
 
>>-CEMT Perform COrbaserver(value)--+-Publish-+----------------><
                                    +-Retract-+
                                    '-Scan----'
 

Options

Corbaserver (value)
specifies the 4-character CorbaServer name.
Publish

publishes:

  • all beans installed in the specified CorbaServer
  • the Generic Factory Interoperable Object Reference (Generic factory) of the specified Corbaserver

Publishing a bean means binding a reference to the home of the bean in the namespace. The naming context in which the bean is bound is named, relative to the initial context defined for the CICS region, using a concatenation of the JNDI PREFIX attribute of the CorbaServer and the name of the bean.

The Generic factory is bound with the name GenericFactory concatenated to the PREFIX attribute of the Corbaserver.

Retract
indicates that all the beans installed in the CorbaServer are to be retracted. Retracting a bean means unbinding a reference to the home of the bean from the namespace. The naming context in which the bean is bound is named, relative to the initial context defined for the CICS region, using a concatenation of the JNDI prefix attribute of the CorbaServer and the name of the bean.
Scan
scans the CorbaServer’s deployed JAR file directory (also known as the pickup directory) for new or updated deployed JAR files.

If CICS finds any new deployed JAR files in the pickup directory, it copies them to its shelf directory and dynamically creates and installs DJAR definitions for them.

If CICS finds any updated deployed JAR files in the pickup directory, it updates both the LASTMODTIME, DATESTAMP, and TIMESTAMP attributes of the installed DJAR definitions and the shelf copies of the deployed JAR files.

Note:
CICS ignores any deployed JAR files in the pickup directory that have the same name and the same date and time stamps as currently-installed DJAR resources. A deployed JAR file with the same name but a later date-and-time stamp than an installed DJAR is treated as an update.

If you receive a "DJAR CONFLICT" message, it means that one or more deployed JAR files have failed to install due to a naming conflict. This error can occur for two reasons:

  1. The name of a DJAR definition created by the scanning mechanism conflicts with that of a previously-installed dynamic definition that targets a different CorbaServer. The scanned-in definition cannot be treated as an update, because the installed definition refers to a different CorbaServer.
  2. The name of a DJAR definition created by the scanning mechanism conflicts with that of a statically-installed definition. You cannot use the scanning mechanism to update a static DJAR definition.

To avoid this error:

  1. If your CICS region contains multiple CorbaServers, use a different pickup directory for each CorbaServer.
  2. Do not place identically-named deployed JAR files into multiple pickup directories in the same CICS region.
  3. If you use static DJAR definitions, do not give them names that might conflict with those created by the scanning mechanism.

For more information about DJAR naming conflicts and how to avoid them, see the CICS® Resource Definition Guide.

CEMT PERFORM DELETSHIPPED

Function

Cause the CICS timeout delete mechanism to be invoked immediately.

Description

The CICS timeout delete mechanism removes any shipped terminal definitions that have not been used for longer than the time specified on the DSHIPIDL system initialization parameter, or on a subsequent SET DELETSHIPPED IDLE command. The interval between scheduled invocations of the mechanism is specified on the DSHIPINT system initialization parameter, or on a subsequent SET DELETSHIPPED INTERVAL command.

PERFORM DELETSHIPPED invokes timeout delete immediately.

Notes:
  1. Shipped definitions are not deleted if there is an automatic initiate descriptor (AID) associated with the terminal.
  2. Issuing a PERFORM DELETSHIPPED command does not reset the start of the time interval until the next invocation of the timeout delete mechanism. In other words, causing the timeout delete mechanism to be invoked immediately does not affect the time remaining until the next scheduled invocation.

Syntax

Read syntax diagramSkip visual syntax diagramCEMT PERFORM DELETSHIPPED
 
>>-CEMT Perform DEletshipped-----------------------------------><
 

CEMT PERFORM DJAR

Function

The PERFORM DJAR command performs certain actions against a specified deployed JAR file. If no action is specified, the command has no effect.

In addition to the traditional DFSMS-managed data sets, such as partitioned data sets (PDS), CICS requires access to z/OS UNIX System Services and the hierarchical file store (HFS) in order to launch a JVM. This requires that the CICS region userid is authorized to z/OS UNIX System Services to enable CICS to access the required HFS directories, such as those specified on the JVMPROPS, LIBPATH, and CLASSPATH parameters.

Description

A failure to perform the requested action will be reported by returning a condition and RESP2 value from the command and, in certain cases, by writing messages to CSMT. The requested action may have beens partially successful since a failure does not cause the effects of the command to be backed out. Also, failure does not necessarily stop the command from continuing in order to increase the extent to which it was partially successful.

Syntax

Read syntax diagramSkip visual syntax diagramCEMT PERFORM DJAR
 
>>-CEMT Perform DJar(value)--+-Publish-+-----------------------><
                             '-Retract-'
 

Options

DJar (value)
specifies the 1-32 character name of a deployed JAR file.
Publish
indicates that all beans installed in the named deployed JAR file are to be published. Publishing a bean means binding a reference to the home of the bean in the namespace. The naming context in which the bean is bound is named, relative to the initial context defined for the CICS region, using a concatenation of the JNDI prefix attribute of the DJAR's CorbaServer and the name of the bean.
Retract
indicates that all the beans installed in the deployed JAR file are to be retracted. Retracting a bean means unbinding a reference to the home of the bean from the namespace. The naming context in which the bean is bound is named, relative to the initial context defined for the CICS region, using a concatenation of the JNDI prefix attribute of the DJAR's CorbaServer and the name of the bean.

CEMT PERFORM DUMP|SNAP

Function

Obtain a CICS system dump.

Description

To get a CICS system to dump and continue processing, you can use either the CEMT PERFORM DUMP command or the CEMT PERFORM SNAP command. Both commands produce a "snapshot" of the CICS system.

The use of CEMT PERFORM DUMP or CEMT PERFORM SNAP prevents all other tasks from running. Consequently, terminal operators may experience delays in response.

Syntax

Read syntax diagramSkip visual syntax diagramCEMT PERFORM DUMP
 
>>-CEMT Perform--+-DUmp-+--+--------------+--------------------><
                 '-SNap-'  '-Title(value)-'
 

Options

DUmp
specifies that a system dump is to be produced.
SNap
specifies that CICS is to issue the MVS SDUMP macro to produce an SDUMP (system dump) of the CICS region.
Title (value)
specifies a title of up to 32 characters; it is added at the beginning of the dump. If your title includes spaces, you must enclose the whole title within single quotation marks (' ').

CEMT PERFORM ENDAFFINITY

Function

End an affinity owned by CICS.

Description

Where CICS is a member of a VTAM generic resource group, PERFORM ENDAFFINITY instructs VTAM to end an affinity owned by CICS, whether or not the connection has been deleted. If the connection has not been deleted, it must be out of service and have no recovery information outstanding--that is, its RECOVSTATUS (as displayed by CEMT INQUIRE/SET CONNECTION) must be NORECOVDATA.

Generic resources and affinities are described in the CICS Intercommunication Guide.

Syntax

Read syntax diagramSkip visual syntax diagramCEMT PERFORM ENDAFFINITY
 
>>-CEMT Perform Endaffinity--NETName(value)--+--------------+--><
                                             '-NETId(value)-'
 

Options

NETId (value)
specifies the 8-character name by which the network containing the connected LU is known to VTAM.

If you do not specify a NETID, CICS takes the value from the installed connection, if it exists. If you do not specify a NETID and the connection does not exist, the command fails.

NETName (value)
specifies the 8-character APPLID of the connected LU. If the connected LU is a member of a generic resource, you must specify its member name, not the generic resource name.
Note:
There is no facility in VTAM for inquiring on affinities, so CICS has no certain knowledge that an affinity exists for a given connection. Whenever there is a possibility that an affinity has been created that you must end explicitly, CICS issues message DFHZC0177. This message gives the NETNAME and NETID to be passed to VTAM.

If a request to end an affinity is rejected by VTAM because no such affinity exists, CICS issues message DFHZC0181. This may mean either that you entered the NETNAME or NETID incorrectly, or that you (or CICS) was wrong in supposing that an affinity existed.

Start of change

CEMT PERFORM PIPELINE

Function

Use the PERFORM PIPELINE command to initiate a scan of the Web service binding directory that is specified in the WSBIND attribute of the PIPELINE definition. If the WSBIND attribute is not specified, there is nothing to scan, and control returns to your program.

If the directory location specified is valid, CICS examines the Web service binding files in the directory to determine if they should be installed into the system:

If, for any reason, CICS fails to install an individual Web service binding file, processing continues with the remaining files in the directory. When the scan completes, the PIPELINE is available for use with whichever of the binding files were installed successfully.

Description

A failure to perform the requested action will be reported by returning a condition and RESP2 value from the command and, in certain cases, by writing messages to CSMT. The requested action may have beens partially successful since a failure does not cause the effects of the command to be backed out. Also, failure does not necessarily stop the command from continuing in order to increase the extent to which it was partially successful.

Syntax

Read syntax diagramSkip visual syntax diagramCEMT PERFORM PIPELINE
 
>>-CEMT Perform PIpeline(value)----Scan------------------------><
 

Options

PIPELINE (value)
specifies the 8-character PIPELINE name.
Scan
Scan the PIPELINE's Web service binding directory
End of change

CEMT PERFORM RESET

Function

Synchronize the CICS date and time-of-day with the system date and time-of-day.

To ensure that the correct local time is used by all CICS functions, use the CEMT PERFORM RESET command immediately whenever you alter the system date or the time-of-day in the MVS TOD clock while a CICS region is running.

For example, when setting clocks forward or back an hour to adjust for Summer and Winter time, use this command to ensure that CICS immediately updates the correct local time.

Note:
To ensure that your applications are receiving the correct time, always use CEMT PERFORM RESET whenever you alter the MVS TOD clock. CICS only obtains and stores the local time offset, at start up, and when the CEMT PERFORM RESET command executes.

Syntax

Read syntax diagramSkip visual syntax diagramCEMT PERFORM RESET
 
>>-CEMT Perform Reset------------------------------------------><
 

CEMT PERFORM SECURITY

Function

Rebuild the in-store RACF resource profiles. The RACF resource profiles are rebuilt by reissuing the RACLIST macro for the active class names.

Syntax

Read syntax diagramSkip visual syntax diagramCEMT PERFORM SECURITY
 
>>-CEMT Perform SEcurity--+---------+--------------------------><
                          '-Rebuild-'
 

If the external security manager is RACF 2.1 or an equivalent product, the PERFORM SECURITY command is not required to refresh the classes used for resource checks. A message of NOT REQUIRED is displayed and no action is taken.

Options

Rebuild
is an optional keyword. It does not alter the action of the transaction.

CEMT PERFORM SHUTDOWN

Function

Shut down the CICS region. The shutdown can be either controlled or immediate. Start of changeIf a shutdown (either normal or immediate) hangs, a subsequent SHUTDOWN IMMEDIATE resumes the shutdown process.End of change

Syntax

Read syntax diagramSkip visual syntax diagramCEMT PERFORM SHUTDOWN
 
>>-CEMT Perform SHUTdown--+------------+--+------------+-------->
                          '-Xlt(value)-'  '-Plt(value)-'
 
>--+---------------+--+--------------------------+-------------->
   +-Sdtran(value)-+  '-Immediate--+-----------+-'
   '-NOSdtran------'               '-NORestart-'
 
>--+----------+--+------+--------------------------------------><
   '-Takeover-'  '-Dump-'
 

Options

Dump
A dynamic storage dump is produced upon completion of the termination process.
Immediate
specifies that the system is shut down immediately, terminating all active tasks and SNA sessions. If IMMEDIATE is not specified, all tasks are allowed to finish, and SNA sessions are allowed to terminate normally.
NORestart
specifies that, if the CICS region is registered to MVS/ESA Automatic Restart Manager (ARM), it is to be deregistered as part of shutdown and not restarted automatically.
NOSdtran
No shutdown assist transaction is to be run at CICS shutdown.

The default shutdown transaction, if neither SDTRAN nor NOSDTRAN are specified, is CESD.

Plt (value)
specifies the 2-character suffix of a program list table (PLT) to be used for the shutdown.
Sdtran
The 4-character identifier of the shutdown assist transaction
Takeover
specifies that this CICS region should be closed down, and the alternate CICS region is to take over. This is valid only if the XRF=YES system initialization parameter was specified for CICS startup.
Xlt (value)
specifies the 2-character suffix of a transaction list table (XLT) to be used for the shutdown.

Transactions listed in the specified XLT can be initiated after the SHUTDOWN request, and before the system quiesces. The default XLT should contain an entry for the master terminal transaction. This ensures that you can issue an immediate shutdown if, for example, a task is found to be suspended after an ordinary (nonimmediate) shutdown has been requested.

Table 5 shows the effect of the TAKEOVER and IMMEDIATE options on the active CICS system.

Table 5. Effect of the TAKEOVER and IMMEDIATE options on the active CICS system
  CEMT PERFORM SHUTDOWN
(normal) TAKEOVER IMMEDIATE
Tasks finish finish terminate
SNA session (XRF) unbind leave leave
SNA session (non-XRF) unbind unbind unbind

Table 6 shows the effect of the TAKEOVER and IMMEDIATE options on the alternate CICS system.

Table 6. Effect of the TAKEOVER and IMMEDIATE options on the alternate CICS system
  CEMT PERFORM SHUTDOWN
(normal) TAKEOVER IMMEDIATE
CICS alternate shuts down takes over takes over

For further information on XRF, see the CICS/ESA 3.3 XRF Guide.

CEMT PERFORM STATISTICS

Function

Write the statistics for a named resource type immediately to the SMF data set, rather than wait for the current statistics-gathering interval to expire. The recording is made irrespective of the ON or OFF setting of statistics. See also topic CEMT INQUIRE STATISTICS and topic  CEMT SET STATISTICS for a description of the CEMT INQUIRE and SET STATISTICS commands.

Description

You can request either statistics for all resources (ALL), or statistics for individual resources in various combinations by selecting one or more keywords from the list.

The message ‘STATS MISSING’ appears when the resource type is either not functioning or not available. As much data is recorded as possible.

See the CICS Operations and Utilities Guide for information about printing statistics using the CICS-supplied utility program DFHSTUP, and for information about the reports produced by DFHSTUP.

Syntax

Read syntax diagramSkip visual syntax diagramCEMT PERFORM STATISTICS
 
>>-CEMT Perform STatistics--+--------+-------------------------->
                            '-RECORd-'
 
   .-----------------------.
   V                       |
>----+-ALl--+----------+-+-+-----------------------------------><
     |      '-RESetnow-' |
     +-AUtoinstall-------+
     +-Bean--------------+
     +-Connection--------+
     +-CORbaserver-------+
     +-DB2---------------+
     +-DIspatcher--------+
     +-Enqueue-----------+
     +-FEpi--------------+
     +-FIle--------------+
     +-Journalname-------+
     +-JVMPOol-----------+
     +-JVMPROFile--------+
     +-JVMPROGram--------+
     +-Lsrpool-----------+
     +-Monitor-----------+
     +-PIpeline----------+
     +-PROGAuto----------+
     +-PROGRam-----------+
     +-RECOVery----------+
     +-REQuestmodel------+
     +-STAts-------------+
     +-STOrage-----------+
     +-STReamname--------+
     +-SYsdump-----------+
     +-TAblemgr----------+
     +-TCLass------------+
     +-TCPIP-------------+
     +-TCPipservice------+
     +-TDqueue-----------+
     +-TErminal----------+
     +-TRAnsaction-------+
     +-TRDump------------+
     +-TSqueue-----------+
     +-Urimap------------+
     +-Vtam--------------+
     '-Webservice--------'
 

Options

ALl
Statistics for all resources are to be written immediately to the SMF data set.

ALL RESETNOW resets the counters for the collection of statistics. RESETNOW only works if the ALL operand is set, that is, ALL RESETNOW.

AUtoinstall
Autoinstall statistics are to be written immediately to the SMF data set.
Bean
Enterprise bean statistics are to be written immediately to the SMF data set.
Connection
Connection statistics are to be written immediately to the SMF data set.
CORbaserver
CorbaServer statistics are to be written immediately to the SMF data set.
DB2
CICS DB2 statistics are to be written immediately to the SMF data set.
DIspatcher
Dispatcher statistics are to be written immediately to the SMF data set.
Enqueue
Enqueue statistics are to be written immediately to the SMF data set.
FEpi
FEPI statistics are to be written immediately to the SMF data set.
FIle
File control statistics are to be written immediately to the SMF data set.
Journalname
CICS journal statistics are to be written immediately to the SMF data set.
Note:
The JOURNALNUM resource name is obsolete, and replaced by the JOURNALNAME resource name.
JVMPOol
JVM pool statistics are to be written immediately to the SMF data set.
JVMPROFile
JVM profile statistics are to be written immediately to the SMF data set.
JVMPROGram
JVM program statistics are to be written immediately to the SMF data set.
Lsrpool
LSRPOOL statistics are to be written immediately to the SMF data set.
Monitor
Monitoring statistics are to be written immediately to the SMF data set.
Start of changePIpelineEnd of change
Start of changePIPELINE statistics are to be written immediately to the SMF data set.End of change
PROGAuto
Autoinstalled program statistics are to be written immediately to the SMF data set.
PROGRam
Program statistics are to be written immediately to the SMF data set.
RECORd
is an optional keyword. It does not alter the action of the transaction.
RECOVery
Recovery statistics are to be written immediately to the SMF data set.
REQuestmodel
Requestmodel statistics are to be written immediately to the SMF data set.
RESetnow
The statistics counters are to be reset.
STAts
Statistics domain statistics are to be written immediately to the SMF data set.
STOrage
Storage manager statistics are to be written immediately to the SMF data set.
STReamname
Log stream statistics are to be written immediately to the SMF data set.
SYsdump
System dump statistics are to be written immediately to the SMF data set.
TAblemgr
Table manager statistics are to be written immediately to the SMF data set.
TCLass
Transaction class statistics are to be written immediately to the SMF data set.
TCPIP
Request global statistics for IP sockets.
TCPipservice
TCP/IP service statistics are to be written immediately to the SMF data set.
TDqueue
Transient data statistics are to be written immediately to the SMF data set.
TErminal
Terminal statistics are to be written immediately to the SMF data set.
TRAnsaction
Transaction statistics are to be written immediately to the SMF data set.
TRDump
Transaction dump statistics are to be written immediately to the SMF data set.
TSqueue
Temporary storage statistics are to be written immediately to the SMF data set.
Start of changeUrimapEnd of change
Start of changeURIMAP statistics are to be written immediately to the SMF data set.End of change
Vtam
VTAM statistics are to be written immediately to the SMF data set.
Start of changeWebserviceEnd of change
Start of changeWEBSERVICE statistics are to be written immediately to the SMF data set.End of change
[[ Contents Previous Page | Next Page Index ]]