The SET command changes the status of one or more named instances of a
resource (such as a terminal), a particular subgroup of resources (such as
a class of terminals), or all resources of a particular type (such as all
terminals).
The SET command makes the changes that you specify, and displays the new
status of the resources. No changes are made if there are syntax errors in
the SET command.
To change the attributes of a resource, enter SET (or a suitable abbreviation)
on the command line. The keywords you can use with CEMT SET are described
in the rest of this section.
On every SET command, an argument, a generic argument, or ALL must be specified.
For example:
SET TERMINAL(TRM1) INSERVICE
sets terminal TRM1 in
service.
SET TERMINAL(TRM1 TRM2 TRM3) INSERVICE
or
SET TERMINAL(TRM1,TRM2,TRM3) INSERVICE
sets terminals TRM1, TRM2, and TRM3 in service.
SET TERMINAL(TRM*) INSERVICE
sets all terminals with identifiers starting with TRM in service.
SET TERMINAL ALL INSERVICE
sets all terminals in service.
However,
SET TERMINAL INSERVICE
produces an error.
Function
Change autoinstall values.
Description
The CEMT SET AUTOINSTALL command allows you to change some of the values
that control the automatic installation (autoinstall) of VTAM terminals, virtual
terminals including bridge facilities used by the 3270 bridge mechanism, and
MVS consoles. For information about autoinstall, see CICS® Resource Definition Guide.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET AUTOINSTALL (the minimum abbreviation is CEMT S AUTO). You get a display that lists the current status, similar
to that obtained by CEMT INQUIRE AUTOINSTALL. You can then tab to the highlighted
or blank fields and overtype them with the required values.
- Type CEMT SET AUTOINSTALL (CEMT S AUTO) followed
by one or more attribute settings that you wish to change. For example, CEMT S AUT M(NEWVALUE P(NEWNAME) resets the values for maximum number
of requests for a new program.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET AUTOINSTALL
>>-CEMT Set AUToinstall--+----------+--+----------------+------->
+-PROGAUTO-+ '-Maxreqs(value)-'
+-FULLAUTO-+
'-NOAUTO---'
>--+-----------+--+------------+-------------------------------><
'-| SETA2 |-' +-AUTOTERMID-+
'-URMTERMID--'
SETA2
|--Program(value)-----------------------------------------------|
Options
- Aibridge
- Specifies whether the autoinstall user replaceable module (URM) is to
be called for bridge facilities. The values are:
- AUTOTERMID
- Bridge facilities are to be defined automatically by CICS. The autoinstall
URM is not to be called.
- URMTERMID
- The autoinstall URM is to be called.
- Consoles
- specifies whether CICS is to autoinstall an MVS console device when
it receives an MVS MODIFY command from a console that is not defined. The
CVDA values are:
- Progauto
- MVS consoles are to be autoinstalled, and CICS is to call the user autoinstall
control program to obtain the termid and other user-specified information.
- Fullauto
- MVS consoles are to be autoinstalled by CICS automatically, without
calling the user autoinstall control program. CICS assigns the termid for
the console automatically, using the ¬ (logical not) symbol as the
first character.
- Noauto
- Autoinstall for consoles is not allowed.
- Maxreqs (value)
- specifies the largest number of autoinstall requests that are allowed
to queue at one time, in the range 0-999.
You can prevent more terminals
from logging on through autoinstall by setting this value to 0. This allows
autoinstalled entries for terminals currently logged on to be deleted by the
autoinstall program when they log off.
- Program (value)
- specifies the name of the user program that is to control the autoinstall
process. A default program is supplied.
Function
Change auxiliary tracing options.
Description
For more information about traces, see the CICS Problem Determination Guide.
See also the description of the CETR transaction, CETR--trace control.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET AUXTRACE (the minimum abbreviation is CEMT
S AUX). You get a display that lists the current status, similar to
that obtained by CEMT INQUIRE AUXTRACE. You can then tab to the highlighted
or blank fields and overtype them with the required values.
- Type CEMT SET AUXTRACE (CEMT S AUX) followed by
one or more attribute settings that you wish to change. For example, cemt s aux sto a stops auxiliary tracing and causes automatic switching
to occur as necessary.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET AUXTRACE
>>-CEMT Set AUXtrace--+-------+--+----------+--+--------+------><
+-STArt-+ +-NOswitch-+ '-SWitch-'
+-Pause-+ +-NExt-----+
'-STOp--' '-All------'
Options
- All
- Specifies that automatic switching between the two auxiliary trace data
sets is to occur as necessary until the end of this CICS session, without
the need for operator intervention.
- NExt
- Automatic switching of the auxiliary trace data set is to occur when
the current trace data set is full, but not subsequently.
- NOswitch
- Switching between the auxiliary trace data sets is not to occur without
operator intervention.
- Pause
- Auxiliary tracing is to stop, but the data set is to remain open. A
subsequent START request causes trace entries to be written immediately following
those that were written before the PAUSE request.
- STArt
- CICS is to start auxiliary tracing and open the auxiliary trace data
set if it is currently closed.
- STOp
- CICS is to stop auxiliary tracing and close the auxiliary trace data
set. A subsequent START request causes new trace entries to be written at
the start of the data set, thereby overwriting the trace entries that were
written before the STOP request.
- SWitch
- specifies that an immediate switch from the current auxiliary trace
data set is to be made to the alternate trace data set.
Function
Release virtual terminals (bridge facilities) used by the 3270 bridge mechanism.
Description
CEMT SET BRFACILITY allows you to request deletion of the virtual terminal
(bridge facility) used by the 3270 bridge mechanism.
If a transaction is currently running, the bridge facility will be deleted
at the end of the transaction. If the bridge facility is currently AVAILABLE,
the facility will be deleted at the next garbage clearance.
When a bridge facility is released, the delete function of the XFAINTU
global user exit is driven.
Note:
Bridge facilities are deleted only in the region in which
the command is issued. Bridge facilities can exist in both router and AOR
regions. This command deletes the facility in the region on which it is issued.
It does not affect the other region, but this means that the bridge facility
can no longer be used. However in order to free up the storage occupied by
a bridge facility this command should be issued in both regions. This command
can only be issued in the router or AOR region where the bridge facility was
created.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET BRFACILITY (the minimum abbreviation is CEMT S BR) with (value) or ALL. You get a display that lists
the current status, similar to that obtained by CEMT INQUIRE BRFACILITY. You
can then tab to the highlighted field and overtype it with the required value.
- Type CEMT SET BRFACILITY (CEMT S BR) with value
or ALL, followed by one or more attribute settings that you wish to change.
For example, cemt s br(value) rel will release the specified
bridge facility.
To obtain a syntax prompt, enter ?CEMT S BR.

CEMT SET BRFACILITY
>>-CEMT Set BRfacility--+-(value)-+--+----------+--------------><
'-ALl-----' '-RELeased-'
Options
- (value)
- is an 8-byte bridge facility token.
- All
- Any changes you request are made to all resources of the specified type
that you are authorized to access.
- RELeased
- specifies that the bridge facility should be marked for deletion.
Function
Set the status of autostart for the shared class cache.
Description
On an initial or cold start of CICS, the status of autostart is taken from
the system initialization parameter JVMCCSTART. A JVMCCSTART value of YES
or AUTO gives an autostart status of ENABLED, and a JVMCCSTART value of NO
gives an autostart status of DISABLED. You can change the status of autostart
by using the SET CLASSCACHE command, or by using the Enabled or Disabled option
on the CEMT PERFORM CLASSCACHE command (or the equivalent EXEC CICS command)
when you are performing the Phaseout, Purge or Forcepurge operations with
that command.
When you change the status of autostart for the shared class cache while
CICS is running, subsequent CICS restarts use the most recent settings that
you made using the CEMT or EXEC CICS SET CLASSCACHE command (or the CEMT or
EXEC CICS PERFORM CLASSCACHE command), unless the system is INITIAL or COLD
started, or the system initialization parameter JVMCCSTART is specified as
an override at startup. In these cases, the setting from the system initialization
parameter is used.
Syntax

CEMT SET CLASSCACHE
>>-CEMT Set CLasscache--+----------+---------------------------><
+-Enabled--+
'-Disabled-'
Options
- Disabled
- Sets the status of autostart for the shared class cache to Disabled.
When autostart is disabled, if the shared class cache has been stopped or
has not yet been started on this CICS execution, an explicit CEMT PERFORM
CLASSCACHE Start command (or the equivalent EXEC CICS 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.
- Enabled
- Sets the status of autostart for the shared class cache to Enabled.
When autostart is 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.
Function
Change the status of connections linked to specific terminals.
Description
When a connection has been defined as INDIRECT, no information is given
unless the direct connection to which it refers is installed.
If you want to install a new connection definition when one is already
installed, you must set the connection OUTSERVICE and, if it is VTAM-connected,
release it before using the CEDA INSTALL commands for your new definition.
See the CICS Resource Definition Guide for further information about
connections.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET CONNECTION (the minimum abbreviation is CEMT S C) followed by one or more connection identifiers or ALL. You
get a display that lists the current status, similar to that obtained by CEMT
INQUIRE CONNECTION. You can then tab to the highlighted or blank fields and
overtype them with the required values.
- Type CEMT SET CONNECTION (CEMT S C) followed by
one or more connection identifiers or ALL, followed in turn by one or more
attribute settings that you wish to change. For example, cemt s c al
i resets the values for all connections to make them available for
use (inservice).
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET CONNECTION
>>-CEMT Set Connection--+-(value)-+--+------------+------------->
'-ALl-----' '-NOTpending-'
>--+------------+--+----------+--+------------+--+----------+--->
+-INService--+ +-ACquired-+ +-PUrge------+ +-COmmit---+
'-OUtservice-' '-RELeased-' +-FORCEPurge-+ +-Backout--+
+-Kill-------+ +-FORCEUow-+
+-CAncel-----+ '-RESync---'
'-FCancel----'
>--+-------------+--+-------------+----------------------------><
'-ENdaffinity-' '-NORecovdata-'
Options
- (value)
- One or more names (1-4 characters) defined for an interregion
communication (IRC) or an intersystem communication (ISC) connection.
- ACquired (appc only)
- specifies whether CICS is to acquire a session with the logical unit
represented by the CONNECTION name. To get more detailed information about
the availability status of the connection elements, use the CEMT INQUIRE MODENAME
command. A connection cannot be both ACQUIRED and OUTSERVICE.
- ALl
- Any changes you request are made to all resources of the specified type
that you are authorized to access.
- Backout (APPC parallel-session, CICS-to-CICS MRO, and LU61 only)
- All UOWs shunted due to the failure of this connection are to be backed
out. The normal resynchronization process is to be partially overridden: decisions
are taken for any units of work that are in-doubt due to a failure of the connection;
but the decisions are recorded and any data inconsistencies are reported when
the connection is next acquired.
- CAncel
- Automatic initiate descriptors (AIDs) queuing for the specified connection
are to be canceled.
AIDs representing scheduled and allocated requests
waiting in the local CICS system for the specified connection are canceled.
However, TD AIDs with an associated triggered task already started are not
be canceled. In addition, the following CICS system AIDs are not purged unless
FCANCEL is specified.
Table 7. System AIDs requiring FCANCEL to remove them
Description |
Tranid |
Remote delete AIDs |
|
Remote scheduler AIDs |
CRSR |
LU6.2 service manager 1 AIDs |
CLS1 |
LU6.2 service manager 3 AIDs |
CLS3 |
Remote scheduler PURGE AIDs |
CRSQ |
Resource manager resync AIDs |
CRSY |
Autoinstalled terminal delete AIDs |
CATD |
Autoinstalled terminal restart AIDs |
CATR |
When a canceled SCHEDULE request is found to have a precursor
in a remote CICS system; that is, the AID was originally scheduled in a remote
system, the remote AID is canceled asynchronously.
Message DFHTF0100
is written to CSMT to indicate how many AIDs have been deleted for the connection
and how many remain.
An ‘AIDS CANCELED’ message appears on
the CEMT panel whenever AIDs are deleted using the CANCEL option of the CEMT
SET CONNECTION command.
- COmmit (APPC parallel-session, CICS-to-CICS MRO, and LU61 only)
- All UOWs shunted due to the failure of this connection are to be committed.
The normal resynchronization process is to be partially overridden: decisions
are taken for any units of work that are in-doubt due to a failure of the connection;
but the decisions are recorded and any data inconsistencies are reported when
the connection is next acquired.
- ENdaffinity (appc and lu6.1 only)
- specifies, where CICS is a member of a VTAM generic resource group,
that VTAM is to end an affinity owned by CICS. This option is valid only for
APPC and LU6.1 connections. The connection must be out of service and, for
APPC, in NORECOVDATA state.
Notes:
- 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
of the suspect connection.
- If a request to end an affinity is rejected by VTAM because no such affinity
exists, CICS issues message DFHZC0181.
- A response of 'NETID 0 USE PRFRM' means that you cannot use SET
CONNECTION to end the affinity because the value of NETID in the installed
connection is 0. (NETID is the name by which the network containing the connected
LU is known to VTAM.) To end the affinity, you must use the PERFORM ENDAFFINITY
command, on which you must specify the correct NETID.
This response can
also result from repeatedly hitting the ENTER key after the affinity has been
ended.
- Generic resources and affinities are described in the CICS Intercommunication Guide.
- FCancel
- All AIDs, including system AIDs, queuing for the specified connection
are to be canceled. See Table 7 for a list of those system
AIDS that require FCANCEL to remove them. This can lead to unpredictable results
and should be used only in exceptional circumstances.
Note:
FCANCEL
does not remove transient data AIDs with an associated triggered task. These
aids may be removed by purging the associated task.
An ‘AIDS CANCELED’ message appears on the CEMT panel whenever AIDs
are deleted using the FCANCEL option of the CEMT SET CONNECTION command.
- FORCEPurge (vtam only)
- All transactions running on sessions on the connected system are immediately
terminated abnormally. This can lead to unpredictable results and should be
used only in exceptional circumstances.
In some extreme cases (for example,
if an error occurs during backout processing), CICS might terminate abnormally.
FORCEPURGE replaces PURGE FORCE which is retained only for compatibility
purposes. You should use FORCEPURGE in new applications.
- FORCEUow (APPC parallel-session, CICS-to-CICS MRO, and LU61 only)
- All UOWs shunted due to the failure of this connection are to be forced
to back out or commit, as specified in the ACTION option of the TRANSACTION
definition. The normal resynchronization process is to be partially overridden:
decisions are taken for any units of work that are in-doubt due to a failure of the
connection; but the decisions are recorded and any data inconsistencies are
reported when the connection is next acquired.
- INService
- The system is in service; that is, it is available for use.
For an
MRO connection, all sessions are placed in service and the following occurs:
- If both the issuing system and system "sysid" have IRC open, and
the issuing system has status INSERVICE within system "sysid", connections
are established and made available between the two systems.
- Otherwise, the status of the system (and the status of the underlying
sessions) is set INSERVICE, so that when both systems have IRC open and are
INSERVICE with respect to each other, connections are established. Note that
INQUIRE indicates that systems (and their underlying sessions) are INSERVICE
even though no connections can be used.
- The status of the underlying sessions for a system is always the same
as that for the system itself.
For an ISC system, the following occurs:
- LU6.1 system (that is, links to "sysid" are through intersystem
communication)--all underlying sessions are placed in service.
- APPC system--causes the SNASVCMG sessions to be placed in service
thereby enabling the connection subsequently to be established.
- Kill
- The task is to be terminated. System and data integrity is not guaranteed.
The KILL option extends the PURGE and FORCEPURGE options. It should be used
only after an attempt has been made to PURGE or FORCEPURGE a task. The KILL
option does not guarantee integrity of any kind but in some situations it
allows the user to free up a stalled region enabling the region to continue
processing. In some cases, for example, if a task is killed during backout
processing, CICS terminates abnormally.
- NORecovdata (appc only)
- specifies that the normal resynchronization process is to be overridden.
NORECOVDATA forces in-doubt units of work (according to the transaction definitions),
targets any resyncs that were outstanding for the connection, and erases the
logname previously received from the partner system. The state of the connection
is reset.
Note:
You should use SET CONNECTION NORECOVDATA only in
exceptional circumstances. It erases recovery information and may compromise
data integrity for units of work that have updated resources on remote systems.
Examples of circumstances in which you might need to use it are:
- You need to discard a connection, or issue a SET CONNECTION ENDAFFINITY
command, and it is not possible for the quiesce protocols with the partner
system to be completed. (Neither action is possible for an APPC connection
if recovery data is outstanding.)
- An operational or logic error results in a logname mismatch for the connection.
The connection state must be reset to allow the exchange lognames process
to complete.
Note:
If you specify NORECOVDATA you cannot specify COMMIT,
BACKOUT, FORCEUOW, RESYNC, or NOTPENDING.
- NOTpending (appc and cics-to-cics mro only)
- specifies, for either of the following kinds of connection, that the
normal resynchronization process is to be overridden:
- A connection to a CICS Transaction Server for z/OS® partner that has performed an initial start
- A connection to a pre-CICS Transaction Server for z/OS partner that has performed a cold start.
NOTPENDING forces all in-doubt units of work (according to the transaction
definition) that were created by the connection before the initial (or cold)
start of the partner. It also forgets any resyncs (waitforget UOW-links) that
are outstanding for the connection, and created before the initial (or cold)
start of the partner.
The PENDING condition indicates the existence
of recovery information (either shunted UOWs or decisions remembered for
the partner) on a connection that has experienced a lognames mismatch with
its partner. For a CICS Transaction Server for z/OS partner, a lognames mismatch indicates that
the partner has performed an initial start. For a pre-CICS Transaction Server for z/OS partner,
a lognames mismatch indicates that the partner has performed a cold start.
In either case, the recovery protocol has been corrupted by a loss of log
data at the partner.
It is not possible to set a connection to NOTPENDING
state (forcing in-doubt and erasing NOFORGET UOWs) until this system has
made contact with the partner and received a new logname from it.
Decisions for a whole connection can be forgotten, but that does not affect
the memory of a decision for any other connection involved in the UOW.
Notes:
- If you specify NOTPENDING you cannot specify COMMIT, BACKOUT, FORCEUOW,
RESYNC, or NORECOVDATA. For advice on which option to use, see topic CEMT SET CONNECTION - notes on RES ync.
- NOTPENDING has no effect on MRO connections to pre-CICS Transaction Server for z/OS systems.
However, the cold start of a pre-CICS Transaction Server for z/OS MRO partner causes the SET CONNECTION
NOTPENDING function to be performed automatically, session by session.
The exchange lognames function and the resynchronization
function are described in the CICS Intercommunication Guide and the Systems Network Architecture--LU6.2 Reference: Peer Protocols manual.
- OUtservice
- The system is out of service; that is, it is not available for use.
For an MRO connection, all sessions are placed out of service (immediately
if PURGE is specified, or when tasks have terminated if it is not) and the
following occurs:
- If the connection is currently ACQUIRED, the sessions are broken (quiesced).
The connection cannot be used until it is once again placed INSERVICE.
- If the connection is currently RELEASED, the status of the connection
is set OUTSERVICE and it cannot be used until it is INSERVICE again.
- The status of the underlying sessions for a connection is always the same
as that for the connection itself.
For an ISC system, the following occurs:
- LU6.1 system--all underlying sessions owned by the system are released
and placed out of service: immediately if PURGE or FORCEPURGE is specified;
or when tasks have terminated if neither PURGE nor FORCEPURGE is specified.
If the response to an INQUIRE CONNECTION command shows OUTSERVICE, it does
not imply that the connection has been explicitly set as SET OUTSERVICE; in
particular circumstances, you cannot reinstall this connection.
- APPC system--this option is valid only if the system is released.
All sessions owned by the ISC system are then out of service and released.
- PUrge (vtam only and irc only)
- Transactions running on the connected system are abnormally terminated.
Transactions are terminated only if system and data integrity can be maintained.
A transaction is not purged if its definition specifies SPURGE=NO.
- RELeased (appc only)
- specifies whether CICS is to release a session with the logical unit
represented by the CONNECTION name. To get more detailed information about
the availability status of the connection elements, use the CEMT INQUIRE MODENAME
command.
- RESync (mro to CICS Transaction Server for z/OS and later systems
and appc only) (APPC parallel-session, CICS-to-CICS MRO, and LU61 only)
- Any UOWs shunted due to the failure of this connection are to be retried
(that is, exchange lognames resynchronization for this connection is to be
attempted). This process should normally be started automatically when a connection
is acquired or when a UOW is unshunted. The normal resynchronization process
is to be partially overridden: decisions are taken for any units of work that are
in-doubt due to a failure of the connection; but the decisions are recorded
and any data inconsistencies are reported when the connection is next acquired.
Notes:
- The COMMIT, BACKOUT, FORCEUOW and RESYNC operations are synchronous with
setting the state of the UOW; that is, an INQUIRE UOW following SET CONNECTION
BACKOUT, COMMIT, FORCEUOW, or RESYNC returns the new UOW states.
- Specifying one of these options unshunts all units of work that have failed due
to a failure of the connection. Before issuing SET CONNECTION FORCEUOW, you
may want to use the SET UOW command to specify commit or backout for each
in-doubt unit of work explicitly, rather than letting it default, Local procedures
determine the importance of the data and the method of using the INQUIRE UOW,
INQUIRE UOWENQ, and INQUIRE UOWLINK commands to establish the correct actions.
- You can specify only one of the BACKOUT, COMMIT, FORCEUOW, RESYNC, NOTPENDING,
and NORECOVDATA options. SET CONNECTION NORECOVDATA should be used only in
exceptional circumstances.
- To force all in-doubt units of work caused by a failure of the connection in
the same direction, use SET CONNECTION COMMIT or SET CONNECTION BACKOUT.
- The BACKOUT, COMMIT, FORCEUOW, or RESYNC options of SET CONNECTION and
SET UOW do not clear resync information. If you want to do this, you must
use SET CONNECTION NOTPENDING or SET CONNECTION NORECOVDATA.
- You can issue BACKOUT, COMMIT, FORCEUOW, or RESYNC commands before issuing SET CONNECTION NOTPENDING or SET CONNECTION NORECOVDATA.
Function
Enable or disable a CorbaServer, turn its automatic publishing
feature on or off, and set the session bean timeout value.
Description
If the optional attributes are omitted, the command has no effect.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET CORBASERVER (the minimum abbreviation is CEMT S COR) followed by one or more CORBASERVER identifiers or ALL.
You get a display that lists the current status, similar to that obtained
by CEMT INQUIRE CORBASERVER. You can then tab to the highlighted or blank
fields and overtype them with the required values.
- Type CEMT SET CORBASERVER (CEMT S COR) followed
by one or more CORBASERVER identifiers or ALL, followed in turn by one or
more attribute settings that you wish to change. For example, cemt s
c al i resets the values for all CORBASERVERs to make them available
for use (inservice).
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET CORBSERVER
>>-CEMT Set CORbaserver--+-(value)-+--+---------+--------------->
'-ALl-----' +-AUtopub-+
'-Noauto--'
>--+----------+--+---------------------+-----------------------><
+-Disabled-+ '-SEssbeantime(value)-'
'-Enabled--'
Options
- ALl
- Any changes you request are made to all resources of the specified type
that you are authorized to access.
- (value)
- specifies the 1-4 character name of the CorbaServer.
- AUtopub
- specifies that the contents of a deployed JAR file should be automatically
published to the namespace when the DJAR definition is successfully installed
into this CorbaServer.
Changing the setting of AUTOPUBLISH affects only
DJAR definitions installed after the SET CORBASERVER command is executed.
It has no effect on previously-installed DJAR definitions.
- Disabled
- specifies that the CorbaServer is to be disabled.
In a CICS region
containing multiple CorbaServers, putting one of the CorbaServers into disabled
state allows you to apply maintenance to it without bringing down CICS; the
other CorbaServers remain available.
Similarly, in a logical
EJB/CORBA server containing multiple AORs (each containing multiple CorbaServers),
putting a CorbaServer on one of the AORs into disabled state allows you to
apply maintenance to the CorbaServer without needing to remove the AOR from
the routing set.
You can disable a CorbaServer that is in any state
except ENABLING or DISCARDING. When you do so, any currently-executing methods
are allowed to continue to completion. Until all its objects have been destroyed
or passivated, the CorbaServer enters DISABLING state. Note that:
- Any instance of an enterprise bean or CORBA stateless object that is not
participating in an OTS transaction is destroyed or passivated at the end
of the currently-executing method.
- Any instance of an enterprise bean or CORBA stateless object that is participating in an OTS transaction is not destroyed
or passivated until the end of the OTS transaction; typically, any future
method calls against this instance (within the scope of the OTS transaction)
will succeed. At the end of the OTS transaction, the instance is destroyed
or passivated.
If the workload manager directs new work to an AOR in which the
target CorbaServer is in DISABLING or DISABLED state, it is informed that
the CorbaServer is disabled.
Note:
By "new work" we mean:
- Requests for methods that will run under a new OTS transaction. (By a "new" OTS
transaction we mean an OTS transaction in which none of the AORs in the logical
server is already participating, prior to the method call; not necessarily an OTS transaction that is started immediately before
or after the method call.)
- Requests for methods that will run under no OTS transaction.
- Enabled
- specifies that the CorbaServer is to be enabled. You can enable a CorbaServer
that is in any state except DISABLING or DISCARDING.
- Noauto
- specifies that the contents of a deployed JAR file should not be automatically published to the namespace when the DJAR definition
is successfully installed into this CorbaServer.
- SEssbeantime (value)
- specifies the elapsed time period in minutes, in the range 0 through
143999, of inactivity after which a session bean may be discarded. A value
of 0 indicates that beans are not timed out.
Function
Set attributes of the CICS DB2 connection including the pool and command
thread attributes.
Syntax
Press the Clear key to clear the screen. To commence this transaction:
- Type CEMT SET DB2CONN (the minimum abbreviation is CEMT
S DB2C). You get a display that lists the current status, similar to
that obtained by CEMT INQUIRE DB2CONN. You can then tab to the highlighted
or blank fields and overtype them with the required values.
- Type CEMT SET DB2CONN (CEMT S DB2C) followed by
one or more attribute settings that you wish to change.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET DB2CONN
>>-CEMT Set DB2Conn--------------------------------------------->
.------------------------------. .---------------------------------.
V | V |
>----+--------------------------+-+----+-----------------------------+-+-><
+-+-UOW--+-----------------+ +-+-DB2GROUPID(data-area)-+---+
| +-TASK-+ | | '-DB2ID(data-area)------' |
| +-TXID-+ | +-MSGQUEUE1(data-area)--------+
| '-NONE-' | +-MSGQUEUE2(data-area)--------+
+-+-AUTHID(data-area)-+----+ +-MSGQUEUE3(data-area)--------+
| '-+-GROUP--+--------' | +-+-RELEASE---+---------------+
| +-SIGN---+ | | '-NORELEASE-' |
| +-TERM---+ | +-+-PLAN(data-area)---------+-+
| +-TX-----+ | | '-PLANEXITNAME(data-area)-' |
| +-OPID---+ | +-+-HIGH--+-------------------+
| '-USERID-' | | +-EQUAL-+ |
+-+-COMAUTHID(data-area)-+-+ | '-LOW---' |
| '-+-CGROUP--+----------' | +-PURGECYCLEM(data-area)------+
| +-CSIGN---+ | +-PURGECYCLES(data-area)------+
| +-CTERM---+ | +-+-RESYNC---+----------------+
| +-CTX-----+ | | '-NORESYNC-' |
| +-COPID---+ | +-SIGNID(data-area)-----------+
| '-CUSERID-' | +-REBUILD---------------------+
+-COMTHREADLIM(data-area)--+ +-+-NOCONNECT-+---------------+
+-+-ABEND---+--------------+ | +-CONNECT---+ |
| '-SQLCODE-' | | '-RECONNECT-' |
'-+-CONNECTED----+---------' +-STATSQUEUE(data-area)-------+
+-NOTCONNECTED-+ +-TCBLIMIT(data-area)---------+
'-FORCENOTCON--' +-THREADLIMIT(data-area)------+
'-+-TWAIT---+-----------------'
'-NOTWAIT-'
Options
- A ccountrec
- specifies the minimum amount of DB2 accounting required for transactions
requiring pool threads. The specified minimum may be exceeded, as described
in the following options. CVDA values are:
- UOW
- The CICS DB2 attachment facility causes an accounting record to be produced
for each UOW, assuming that the thread has been released at the end of the
UOW.
- TASK
- The CICS DB2 attachment facility causes a minimum of one accounting
record for each CICS task to be produced.
A transaction containing multiple
UOWs may use a different thread for each of its UOWs (assuming the thread
is released at syncpoint). The result may be an accounting record produced
for each UOW.
- TXID
- The CICS DB2 attachment facility causes an accounting record to be produced
when the transid using the thread changes.
Because pool threads are typically
used by a number of different transaction IDs, there is an increased chance
that a transaction containing multiple UOWs will use a different thread for
each UOW (assuming the thread is released at syncpoint. In this case an accounting
record may be produced for each UOW.
- NONE
- No accounting records are required for transactions using pool threads.
DB2 does, however, produce at least one accounting record for each thread
when the thread is terminated. Additionally, authorization changes cause accounting
records to be produced.
- Authid
- specifies what id should be used for security checking for pool threads.
If AUTHID is specified, AUTHTYPE is cleared.
- Authtype
- specifies the type of ID that can be used for pool threads. If AUTHType
is specified AUTHID is cleared. CVDA values are:
- GROUP
- Specifies the 8-character USERID and the connected group name as the
authorization ID. The following table shows how these two values are interpreted
by DB2.
IDs passed to DB2 |
How DB2 interprets values |
CICS sign-on user ID (USERID) |
Represents the primary DB2 authorization ID. |
RACF connected group name |
If the RACF list of group options is not active, then
DB2 uses the connected group name supplied by the CICS attachment facility
as the secondary DB2 authorization ID. If the RACF list of group options is
active, DB2 ignores the connected group name supplied by the CICS attachment
facility, but the value appears in the DB2 list of secondary DB2 authorization
IDs. |
To use the GROUP option the CICS system must have SEC=YES specified
in the CICS system initialization table (SIT).
If no RACF group ID is
available for this USERID, an 8-character field of blanks is passed to DB2
as the group ID.
- SIGN
- Specifies the SIGNID parameter of the DB2CONN should be used as the
resource authorization ID.
- TERM
- Specifies the terminal identification (four characters padded to eight)
as an authorization ID. An authorization ID cannot be obtained in this manner
if a terminal is not connected with the transaction.
If a transaction is
started (using a CICS command) and has no terminal associated with it, AUTHTYPE(TERM)
should not be used.
- TX
- Specifies the transaction identification (four characters padded to
eight) as the authorization ID.
- OPID
- The operator identification associated with the userid that is associated
with the CICS transaction is used as the authorization ID (three characters
padded to eight).
- USERID
- The 8-character USERID associated with the CICS transaction is used
as the authorization ID.
When the DB2 sample sign-on exit DSN3@SGN
is used with AUTHTYPE(USERID), the exit sends the user ID to DB2 as the primary
authorization ID and the RACF group ID to DB2 as the secondary ID. When the
sample sign-on exit is used, there is no difference between AUTHTYPE(USERID)
and AUTHTYPE(GROUP).
- Comauthid
- specifies which id should be used for security checking when using command
threads. If COMAUTHid is specified, COMAUTHType is cleared.
- Comauthtype
- specifies the type of id that can be used for security checking when
using command threads. If COMAUTHType is specified, COMAUTHid is cleared.
CVDA values are:
- CGROUP
- Specifies the 8-character USERID and the connected group name as the
authorization ID. The following table shows how these two values are interpreted
by DB2.
IDs passed to DB2 |
How DB2 interprets values |
CICS sign-on user ID (USERID) |
Represents the primary DB2 authorization ID. |
RACF connected group name |
If the RACF list of group options is not active, then
DB2 uses the connected group name supplied by the CICS attachment facility
as the secondary DB2 authorization ID. If the RACF list of group options is
active, DB2 ignores the connected group name supplied by the CICS attachment
facility, but the value appears in the DB2 list of secondary DB2 authorization
IDs. |
To use the CGROUP option the CICS system must have SEC=YES specified
in the CICS system initialization table (SIT).
If no RACF group ID is
available for this USERID, an 8-character field of blanks is passed to DB2
as the group ID.
- CSIGN
- Specifies the SIGNID parameter of the DB2CONN should be used as the
resource authorization ID.
- CTERM
- Specifies the terminal identification (four characters padded to eight) as an
authorization ID. An authorization ID cannot be obtained in this manner if
a terminal is not connected with the transaction.
If a transaction is started
(using a CICS command) and has no terminal associated with it, the COMAUTHTYPE(TERM)
should not be used.
- CTX
- Specifies the transaction identification (four characters padded to
eight) as the authorization ID.
- COPID
- The operator identification associated with the userid that
is associated with the CICS transaction sign-on facility is used as the authorization
ID (three characters padded to eight).
- CUSERID
- The 8-character userid associated with the CICS transaction is used
as the authorization ID.
When the DB2 sample sign-on exit DSN3@SGN
is used with AUTHTYPE(USERID), the exit sends the USERID to DB2 as the primary
authorization ID and the RACF group ID to DB2 as the secondary ID. When the
sample sign-on exit is used, there is no difference between COMAUTHTYPE(CUSERID)
and COMAUTHTYPE(CGROUP).
- COMTHREADLim
- specifies the current maximum number of command threads that the CICS
DB2 attachment allows active before requests overflow to the pool.
- Connecterror
- returns a value when CICS is not connected to DB2 because the adapter
is in 'standby mode'. The value shows how this information is to be passed
back to an application that has issued a SQL request. CVDA values are:
- ABEND
- The application is abended with abend code AEY9.
- SQLCODE
- The application receives a -923 SQLCODE.
- Connectst
- sets the status of the CICS DB2 connection; that is, to start or to
stop the CICS DB2 connection. CVDA values are:
- CONNECTED
- This is equivalent to issuing DSNC STRT to start the CICS DB2 attachment.
If the requested DB2 subsystem is active, control returns when CICS and DB2
have been connected. If the requested DB2 subsystem is not active, the response
returned is dependant on the setting of STANDBYMODE: If DB2 is not initialized,
and STANDBYMODE(NOCONNECT) is specified on the DB2CONN, INVREQ and RESP2=39
is returned. If you specify STANDBYMODE(CONNECT) or STANDBYMODE(RECONNECT),
NORMAL with RESP2=38 is returned indicating that the CICS DB2 attachment is
in standby mode and will connect to DB2 as soon as it becomes active.
- NOTCONNECTED
- CEMT initiates a quiesce stop of the CICS DB2 connection and implicitly
uses the NOWAIT option, meaning that control returns immediately to CEMT before
the quiesce is complete.
- FORCENOTCON
- FORCENOTCON force stops the connection by force purging transactions
currently using DB2. Control is not returned until the connection is stopped.
- DB2GROUPID
- specifies the name (up to four characters) of a data sharing group of
DB2 subsystems. CICS attempts to connect to any active member of this group,
using group attach. DB2GROUPID can only be changed when CICS is not connected
to a DB2 system. Specifying a DB2GROUPID causes the DB2ID in the installed
DB2CONN definition to be blanked out. If an individual subsystem's DB2ID is
specified in a CEMT or EXEC CICS SET DB2CONN command, or in a DSNC STRT command,
this overrides any DB2GROUPID that is set in the installed DB2CONN definition.
The DB2GROUPID is blanked out, and needs to be set again (using CEDA or a
SET DB2CONN command) to use group attach. Also note that you cannot set a
DB2GROUPID and a DB2ID in the same command -- this causes the command
to fail.
- DB2Id
- specifies the name of the DB2 subsystem that the CICS DB2 attachment
should connect to. DB2ID can only be changed when CICS is not connected to
a DB2 system. Specifying a DB2ID causes the DB2GROUPID in the installed DB2CONN
definition to be blanked out, and the DB2GROUPID needs to be set again to
use group attach. If a DB2GROUPID is specified in a CEMT or EXEC CICS SET
DB2CONN command, this overrides any DB2ID that is set in the installed DB2CONN
definition, and the DB2ID is blanked out. Also note that you cannot set a
DB2ID and a DB2GROUPID in the same command -- this causes the command
to fail.
- MSGQUEUE1
- specifies the first transient data destination to which unsolicited
messages from the CICS DB2 attachment are sent.
- MSGQUEUE2
- specifies the second transient data destination to which unsolicited
messages from the CICS DB2 attachment are sent.
- MSGQUEUE3
- specifies the third transient data destination to which unsolicited
messages from the CICS DB2 attachment are sent.
- Nontermrel
- specifies whether or not non-terminal transactions release threads for
reuse at intermediate syncpoints. CVDA values are:
- RELEASE
- non-terminal transactions release threads for reuse at intermediate
syncpoints.
- NORELEASE
- non-terminal transactions do not release threads for reuse at intermediate
syncpoints.
- PLAN
- specifies the name of the plan to be used for all threads in the pool.
If PLAN is specified, PLANEXITNAME is cleared.
- PLANExitname
- specifies the name of the dynamic plan exit to be used for pool threads.
If you change the PLAN and PLANExitname while there are active transactions
for the pool, the next time the transaction releases the thread, the plan/exit
will be determined using the new rules. If PLANExitname is specified, PLAN
is cleared.
- Priority
- specifies the priority
of the pool thread TCBs relative to the CICS main TCB (QR TCB). If CICS is
connected to DB2 Version 6 or later, the thread TCBs are CICS open L8 TCBs.
If CICS is connected to DB2 Version 5 or earlier, the thread TCBs are private
TCBs created by the CICS-DB2 Attachment Facility. CVDA values are:
- HIGH
- Thread TCBs have a higher
priority than the CICS QR TCB.
- EQUAL
- Thread TCBs have equal
priority with the CICS QR TCB.
- LOW
- Thread TCBs have a lower
priority than the CICS QR TCB.
- PURGECYCLEM
- specifies in minutes the length of time of the protected thread purge
cycle. The default is 0,30; that is, 30 seconds.
A protected thread is
not terminated immediately when it is released. It is terminated only after
two completed purge cycles, if it has not been reused in the meantime. Hence
if the purge cycle is set to 30 seconds after it is released, a protected
thread is purged 30 - 60 seconds after it is released. An unprotected thread
is terminated when it is released (at syncpoint or end of task) if there are
no other transactions waiting for a thread on that DB2ENTRY.
- PURGECYCLES
- specifies in seconds the length of time of the protected thread purge
cycle. The default is 0,30; that is, 30 seconds.
A protected thread is
not terminated immediately when it is released. It is terminated only after
two completed purge cycles, if it has not been reused in the meantime. Hence
if the purge cycle is set to 30 seconds after it is released, a protected
thread is purged 30 - 60 seconds after it is released. An unprotected thread
is terminated when it is released (at syncpoint or end of task) if there are
no other transactions waiting for a thread on that DB2ENTRY.
- Resyncmember
- This applies only if you are using group attach, and specifies the strategy
that CICS adopts if outstanding units of work are being held for the last
DB2 data sharing group member to which CICS was connected. (Units of work
which are shunted indoubt are not included in this process, because CICS itself
is unable to resolve those units of work at this time. Resynchronization for
those UOWs will occur when CICS has resynchronized with its remote coordinator.)
CVDA values are:
- RESYNC
- CICS connects to the same DB2 data sharing group member to resynchronize
the outstanding units of work.
- NORESYNC
- CICS makes one attempt to connect to the same DB2 data sharing group
member, and if that attempt fails, CICS connects to any member of the DB2
data sharing group and issues a warning about the outstanding units of work.
- SECURITY
- specifies the security. CVDA value is:
- REBUILD
- specifies that the CICS DB2 attachment should force all existing threads
to sign-on again at the next thread reuse. It should be used when RACF profiles
have been updated by issuing the following commands:
- CEMT PERFORM SECURITY REBUILD for RACF 1.9.2 or earlier
- TSO SETROP TS RACLIST(xxxxxxxx) REFRESH for RACF 2.1 or later
- SIgnid
- specifies the authorization ID to be used by the CICS DB2 attachment
when signing on to DB2 for pool and DB2ENTRY threads specifying AUTHTYPE(SIGN),
and command threads specifying COMAUTHTYPE(CSIGN).
- Standbymode
- specifies the action to be taken by the CICS DB2 attachment if DB2 is
not active when an attempt is made to start the connection from CICS to DB2.
CVDA values are:
- NOCONNECT
- The CICS DB2 attachment should terminate.
- CONNECT
- The CICS DB2 attachment goes into 'standby mode' to wait for DB2.
- RECONNECT
- The CICS DB2 attachment goes into 'standby mode' and waits for DB2.
Having connected to DB2, if DB2 subsequently fails the CICS DB2 attachment
reverts again to standby mode and subsequently reconnects to DB2 when it comes
up again.
- STATSqueue
- specifies the transient data destination for CICS DB2 attachment statistics
produced when the CICS DB2 attachment is shutdown.
- TCBLimit
- specifies the maximum number of TCBs that can be used to process DB2
requests. When connected to DB2 Version 5 or earlier, the CICS DB2 attachment
facility creates the TCBs in the form of subtasks up to the limit specified
by TCBLIMIT. Each of these subtasks identifies to DB2 and creates a connection
into DB2. When connected to DB2 Version 6 or later, CICS creates open TCBs
(up to the limit specified in the system intialization parameter MAXOPENTCBS).
The TCBLIMIT attribute of the DB2CONN definition governs how many of the open
TCBs can be used to access DB2 -- that is, how many of them can identify
to DB2 and create a connection into DB2.
- THREADLimit
- specifies the current maximum number of pool threads the CICS DB2 attachment
allows active before requests are made to wait or are rejected according to
the THREADWait parameter.
- Threadwait
- specifies whether or not transactions should wait for a pool thread
or be abended if the number of active pool threads reach the THREADlimit number.
The CICS DB2 attachment issues a unique abend code AD3T, message DFHDB2011
when THREADWAIT=NO is coded and the number of pool threads is exceeded. CVDA
values are:
- TWAIT
- If all threads are busy, a transaction must wait until one becomes available.
A transaction can wait as long as CICS allows it to wait, generally until
a thread becomes available.
- NOTWAIT
- If all threads are busy, the transaction is terminated with abend code
AD3T or AD2P.
Note that when you change the value of AUTHId, AUTHType, COMAUTHId, COMAUTHType
or SIgnid, a surrogate user security check is invoked if security is active.
This ensures that the userid under which SET is being executed is authorized
to act on behalf of the userid being set.
Note that when the SET DB2CONN command is specified all parameters, except
the DB2ID (the connected subsystem), can be set when the CICS DB2 attachment
is active. DB2ID can only be changed by stopping and restarting
the attachment.
If you change the PLAN and PLANEXITNAME while there are active transactions
for that entry, or the pool, the next time the transaction releases the thread,
the plan/exit will be determined using the new rules.
Function
Sets the attributes of a particular DB2ENTRY used to define resources for
a specific transaction or a group of transactions when accessing DB2.
Description
The entry is identified by the name it was identified with in CEDA. For
RCTs migrated to the CSD, the name is the name of the first transaction on
the DSNCRCT TYPE=ENTRY statement.
All parameters on SET DB2ENTRY can be set while the CICS DB2 attachment
is active and the transactions are active.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction
- Type CEMT SET DB2ENTRY (the minimum abbreviation is CEMT
S DB2E) with either a value corresponding to a DB2 entry name or ALL.
You get a display that lists the current status, similar to that obtained
by CEMT INQUIRE DB2ENTRY. You can then tab to the highlighted or blank fields
and overtype them with the required values.
- Type CEMT SET DB2ENTRY (CEMT S DB2E) with either
the name of an entry or ALL, followed by one or more attribute settings that
you wish to change. For example, cemt s db2e all ena enables all
DB2ENTRYs.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET DB2ENTRY
>>-CEMT Set DB2Entry--+-------------+--------------------------->
'-(data-area)-'
.---------------------------------.
V |
>----+-----------------------------+-+-------------------------><
+-+-UOW--+--------------------+
| +-TASK-+ |
| +-TXID-+ |
| '-NONE-' |
+-+-AUTHID(data-area)-+-------+
| '-+-GROUP--+--------' |
| +-SIGN---+ |
| +-TERM---+ |
| +-TX-----+ |
| +-OPID---+ |
| '-USERID-' |
+-+-ABEND---+-----------------+
| +-SQLCODE-+ |
| '-POOL----' |
+-+-ENABLED-------+-----------+
| +-DISABLED------+ |
| '-FORCEDISABLED-' |
+-+-PLAN(data-area)---------+-+
| '-PLANEXITNAME(data-area)-' |
+-+-HIGH--+-------------------+
| +-EQUAL-+ |
| '-LOW---' |
+-PROTECTNUM(data-area)-------+
+-THREADLIMIT(data-area)------+
'-+-TWAIT---+-----------------'
+-NOTWAIT-+
'-TPOOL---'
Options
- Accountrec
- specifies the minimum amount of DB2 accounting required for transactions
using this DB2ENTRY. The specified minimum can be exceeded, as described in
the following options. CVDA values are:
- UOW
- The CICS DB2 attachment facility causes an accounting record to be produced
for each UOW, assuming that the thread is released at the end of the UOW.
- TASK
- The CICS DB2 attachment facility causes a minimum of one accounting
record to be produced for each CICS task.
A transaction containing multiple
UOWs can use a different thread for each of its UOWs (assuming the thread
is released at syncpoint). The result can be an accounting record produced
for each UOW.
- TXID
- The CICS DB2 attachment facility produces at least one accounting record
to be produced when the transid using the thread changes.
This option applies
to DB2ENTRYs that are used by more than one transaction ID. As threads are
typically released st syncpoint, a transaction containing multiple UOWs can
use a different thread for each UOW. The result can be that an accounting
record is produced per UOW.
- NONE
- No accounting records are required for transactions using threads from
this DB2ENTRY.
DB2 does, however, produce at least one accounting record
for each thread when the thread is terminated. Additionally, authorization
changes cause accounting records to be produced.
- AUTHID
- specifies the id to be used for security checking when using this DB2ENTRY.
If AUTHId is specified, AUTHTYPE is cleared.
- Authtype
- returns the type of id that can be used for security checking when using
this DB2ENTRY. If AUTHTYpe is specified, AUTHid is cleared. CVDA values are:
- GROUP
- Specifies the 8-character USERID and the connected group name as the
authorization ID. The following table shows how these two values are interpreted
by DB2.
IDs passed to DB2 |
How DB2 interprets values |
CICS sign-on user ID (USERID) |
Represents the primary DB2 authorization ID. |
RACF connected group name |
If the RACF list of group options is not active, then
DB2 uses the connected group name supplied by the CICS attachment facility
as the secondary DB2 authorization ID. If the RACF list of group options is
active, DB2 ignores the connected group name supplied by the CICS attachment
facility, but the value appears in the DB2 list of secondary DB2 authorization
IDs. |
To use the GROUP option the CICS system must have RACF external security
SEC=YES specified in the CICS system initialization table (SIT).
If
no RACF group ID is available for this USERID, an 8-character field of blanks
is passed to DB2 as the group ID.
- SIGN
- Specifies the SIGNID parameter of the DB2CONN should be used as the
resource authorization ID.
- TERM
- Specifies the terminal identification (four characters padded to eight)
as an authorization ID. An authorization ID cannot be obtained in this manner
if a terminal is not connected with the transaction.
If a transaction is
started (using a CICS command) and has no terminal associated with it, AUTHTYPE(TERM)
should not be used.
- TX
- Specifies the transaction identification (four characters padded to
eight) as the authorization ID.
- OPID
- The operator identification associated with the CICS transaction is
used as the authorization ID (three characters padded to eight).
- USERID
- The 8-character USERID associated with the CICS transaction is used
as the authorization ID.
When the DB2 sample sign-on exit DSN3@SGN
is used with AUTHTYPE(USERID), the exit sends the user ID to DB2 as the primary
authorization ID and the RACF group ID to DB2 as the secondary ID. When the
sample sign-on exit is used, there is no difference between AUTHTYPE(USERID)
and AUTHTYPE(GROUP).
- Disabledact
- specifies what CICS is to do with new transactions that access a DB2ENTRY
when it has been disabled or is disabling. CVDA values are:
- POOL
- The CICS DB2 attachment facility routes the request to the pool. Message
DFHDB2072 is sent to the transient data destination specified by MSGQUEUEn
on the DB2CONN for each transaction routed to the pool.
- ABEND
- The CICS DB2 attachment facility abends the transaction.The abend code
is AD26.
- SQLCODE
- An SQLCODE is returned to the application indicating that the DB2ENTRY
is disabled.
- Enabledstatus
- specifies whether the DB2ENTRY can be accessed by applications. CVDA
values are:
- ENABLED
- The DB2ENTRY can be accessed by applications.
- DISABLED
- The DB2ENTRY cannot be accessed by applications. A DB2ENTRY has to be
disabled before it can be reinstalled or discarded.
- FORCEDISABLED
- All tasks using the DB2ENTRY and those queued against the DB2ENTRY are
forcepurged. The DB2ENTRY is then disabled.
- PLAN
- specifies the name of the plan to be used for this DB2ENTRY.
If PLAN
is specified, PLANEXITNAME is cleared.
- PLANEXITNAME
- specifies the name of the dynamic plan exit to be used for this DB2ENTRY.
If you change the PLAN and PLANExitname while there are active transactions
for the DB2ENTRY the next time the transaction releases the thread, the plan/exit
is determined using the new rules. If PLANExitname is specified, PLAN is cleared.
- Priority
- specifies the priority
of the thread TCBs for this DB2ENTRY relative to the CICS main TCB (QR TCB).
If CICS is connected to DB2 Version 6 or later, the thread TCBs are CICS open
L8 TCBs. If CICS is connected to DB2 Version 5 or earlier, the
thread TCBs are private TCBs created by the CICS-DB2 Attachment Facility.
CVDA values are:
- HIGH
- Thread TCBs have a higher
priority than the CICS QR TCB.
- EQUAL
- Thread TCBs have equal
priority with the CICS QR TCB.
- LOW
- Thread TCBs have a lower
priority than the CICS QR TCB.
- PROTECTNUM
- specifies the maximum number of protected threads for this DB2ENTRY.
- THREADLIMIT
- specifies the maximum number of threads for this DB2ENTRY that the CICS
DB2 attachment allows active before requests are made to wait, are rejected,
or are routed to the pool.
- Threadwait
- specifies whether or not transactions should wait for a DB2ENTRY thread,
be abended, or overflow to the pool should the number of active DB2ENTRY threads
reach the THREADLimit number. CVDA values are:
- TWAIT
- If all threads are busy, the transaction waits until one becomes available.
- NOTWAIT
- If all threads are busy, the transaction is terminated with an abend
code AD2P.
- TPOOL
- If all threads are busy, the transaction is diverted to use the pool
of threads. If the pool is also busy, and NOTWAIT has been specified for
the THREADWAIT parameter on the DB2CONN. The transaction is terminated with
abend code AD3T.
All parameters on SET DB2ENTRY can be set whilst the CICS DB2 attachment
is active and the transactions are active.
Function
specify this to set the attributes of a particular DB2TRAN associated with
a DB2ENTRY.
Description
The DB2TRAN is identified by the name it was defined with in CEDA. For
RCTs migrated to the CSD, the name matches the name of the transaction for
which the DB2TRAN is being created.
If a transid is specified on a DB2ENTRY when the DB2ENTRY is installed,
CICS installs a DB2TRAN named DFHxxxx, where xxxx is the transid.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction
- Type CEMT SET DB2TRAN (the minimum abbreviation is CEMT
S DB2T) with either a value corresponding to a DB2 transaction name
or ALL. You get a display that lists the current status, similar to that obtained
by CEMT INQUIRE DB2TRAN. You can then tab to the highlighted or blank fields
and overtype them with the required values.
- Type CEMT SET DB2TRAN (CEMT S DB2T) with either
the name of a DB2TRAN or ALL, followed by one or more attribute settings that
you wish to change. For example, cemt s db2t all db2e(entry1) will
set all DB2TRANs to refer to a DB2ENTRY named entry1.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET DB2TRAN
.-------------------------.
V |
>>-CEMT Set DB2Tran----+---------------------+-+---------------><
+-DB2Entry(data-area)-+
'-Transid(data-area)--'
Options
- DB2Entry
- specifies the name of the DB2ENTRY to which this DB2TRAN refers; that
is, the DB2ENTRY with which this additional transid should be associated.
- Transid
- specifies the transaction id to be associated with the entry. The transaction
id can include wildcard characters (see CICS Resource Definition Guide for
information about use of wildcard characters). If you change TRANSID for a
DB2TRAN while the attachment is active, all transactions with a thread continue
to use the thread from that entry until it is released for reuse. When that
transaction issues the next SQL statement, the thread is acquired from the
entry or pool based upon the new definition.
DB2TRAN parameters may be set at any time.
Function
Change system settings that control the CICS timeout delete mechanism.
Syntax
The CICS timeout delete mechanism is invoked at user-specified intervals
to remove any shipped terminal definitions that have not been used for longer
than a user-specified time.
SET DELETSHIPPED allows you to change the values that control the mechanism.
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET DELETSHIPPED (the minimum abbreviation is CEMT S DE). You get a display that lists the current status, similar
to that obtained by CEMT INQUIRE DELETSHIPPED. You can then tab to the highlighted
or blank fields and overtype them with the required values.
- Type CEMT SET DELETSHIPPED (CEMT S DE), followed
by one or more attributes that you wish to change. For example, cemt
s de idl(0150000) specifies that shipped terminal definitions are to
remain installed for at least fifteen hours after they become inactive.

CEMT SET DELETSHIPPED
>>-CEMT Set DEletshipped--+-----------------+------------------->
'-INterval(value)-'
>--+-------------+---------------------------------------------><
'-IDle(value)-'
Options
- IDle(value)
- specifies, in the form "0hhmmss+",
the minimum time that an inactive shipped terminal
definition must remain installed in this region. When the CICS timeout delete
mechanism is invoked, only those shipped definitions that have been inactive
for longer than this time are deleted.
The time interval can be in the
range 00-99 hours; 00-59 minutes; and 00-59 seconds.
At CICS startup, the interval is set to the value specified on the DSHIPIDL
system initialization parameter.
- INterval(value)
- specifies, in the form "0hhmmss+",
the interval between invocations of the CICS timeout delete mechanism. The
timeout delete mechanism removes any shipped terminal definitions that have
not been used for longer than the time specified by the IDLE option.
The
time interval can be in the range 00-99 hours; 00-59 minutes;
and 00-59 seconds. If you specify 0, the timeout delete mechanism is
not invoked.
At CICS startup, the interval is set to the value specified
on the DSHIPINT system initialization parameter. By resetting the interval,
you can change the time of day at which a mass delete operation takes place.
Note:
The revised interval starts from the
time the command is issued, not from the time the
timeout delete mechanism was last invoked, nor from the time of CICS startup.
Function
Change the system values used by CICS dispatcher.
Note:
Except for
MAXxxxxTCBS
you can also set these dispatcher system
values using the CEMT SET SYSTEM command.
Syntax
Options
- AGing (value)
- specifies the time factor for CICS to use in the priority aging algorithm
for incrementing the priority of a task. The value is expressed as "milliseconds
per unit of priority", and must be in the range 00000-65535. The
priority aging factor is defined initially by the PRTYAGE system initialization
parameter, in which the value represents the number of milliseconds that must
elapse before the priority of a waiting task can be adjusted upward by 1.
See the CICS System Definition Guide for information about the PRTYAGE
system initialization parameter.
- MAXJvmtcbs(value)
- specifies the maximum number of J8
and J9
mode open TCBs that can exist concurrently in the
CICS region. The value specified can be in the range 1 to 999. If you reduce
MAXJVMTCBS from its previously defined value, and the new value is less than
the number of open TCBs currently allocated, CICS detaches TCBs to achieve
the new limit only when they are freed by user tasks. Transactions are not
abended to allow TCBs to be detached to achieve the new limit. If there are
tasks queued waiting for a J8 mode TCB and you increase MAXJVMTCBS from its
previously defined value, CICS attaches a new TCB to resume each queued task,
up to the new limit.
- MAXOpentcbs(value)
- specifies the maximum number of L8
and L9
mode
open TCBs that can exist concurrently in the CICS region. The value specified
can be in the range 1 to
2000
. If you reduce
MAXOPENTCBS from its previously defined value, and the new value is less than
the number of open TCBs currently allocated, CICS detaches TCBs to achieve
the new limit only when they are freed by user tasks. Transactions are not
abended to allow TCBs to be detached to achieve the new limit. If there are
tasks queued waiting for an L8
or L9
mode TCB and
you increase MAXOPENTCBS from its previously defined value, CICS attaches
a new TCB to resume each queued task, up to the new limit.
MAXSsltcbs(value)
specifies the maximum number of S8 mode open TCBs that can exist concurrently
in the CICS region. The value specified can be in the range 1-1024.
MAXXptcbs(value) 
specifies the maximum number of X8 and X9 mode open TCBs that can exist
concurrently in the CICS region. The value specified can be in the range 1
to 999. If you reduce MAXXPTCBS from its previously defined value, and the
new value is less than the number of open TCBs currently allocated, CICS detaches
TCBs to achieve the new limit only when they are freed by user tasks. Transactions
are not abended to allow TCBs to be detached to achieve the new limit. If
there are tasks queued waiting for an X8 or X9 mode TCB and you increase
MAXXPTCBS from its previously defined value, CICS attaches a new TCB to resume
each queued task, up to the new limit.
- MRobatch (value)
- specifies the number of MRO requests from connected regions that are
to be batched before this region is posted. The value is in the range 001-255.
- RUnaway (value)
- specifies the interval, in milliseconds, for which a task can have control
before it is assumed to be looping.
You can specify 0, or a value in the
range 500-2700000. The value chosen is rounded down to a multiple of
500. CICS purges a task if it has not given up control after this interval
(that is, if the task appears to be looping). If you specify zero, runaway
task control is inoperative (that is, tasks do not get purged if they appear
to be looping). The value is independent of, and can be less than, the value
in the TIME operand.
CICS runaway-task detection is based upon task
time, that is, the interval is decremented only when the task has control
of the processor. You do not, therefore, need to allow for the effect of other
jobs when setting the value.
- SCandelay (value)
- specifies the maximum number of milliseconds between the receipt of
a VTAM request, and the time when CICS begins to process the request. The
number must be in the range 0-5000, and must be less than or equal to
the TIME value.
In the summary report of the dispatcher statistics, SCANDELAY
is referred to as ICVTSD.
- Time (value)
- specifies the interval, in milliseconds, for which CICS releases control
to the operating system if no transactions are ready to resume processing.
This interval is known as the ‘region exit interval’.
It can have
a value in the range 100-3600000, and must be greater than or equal
to the SCANDELAY value.
In the summary report of the dispatcher statistics,
TIME is referred to as ICV.
Function
Change the system storage attributes.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET DSAS. You get a display that lists the current
status, similar to that obtained by CEMT INQUIRE DSAS. You can then tab to
the highlighted or blank fields and overtype them with the required values.
- Type CEMT SET DSAS followed by one or more attribute settings
that you wish to change. For example, cemt s dsa ds(value) ed(value) will reset the values for dynamic storage below the 16MB
boundary and above the 16MB boundary.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET DSAS
>>-CEMT Set DSAs--+-----------------+--+------------------+----><
'-Dsalimit(value)-' '-EDsalimit(value)-'
Options
- Dsalimit(value)
- specifies the maximum amount of storage, as a total number of bytes,
within which CICS can dynamically allocate storage for the four individual
DSAs that reside below the 16MB boundary. See the CICS System Definition Guide for
a description of the DSALIM system initialization parameter.) If DSALIMIT
specifies a value lower than the current limit, CICS may not be able to implement
the new limit immediately, but will attempt to do so over time as dynamic
storage is freed in the individual DSAs.
- EDsalimit(value)
- specifies the maximum amount of storage, as a total number of bytes,
within which CICS can dynamically allocate storage for the four individual
DSAs that reside above the 16MB boundary. See the CICS System Definition Guide for
a description of the EDSALIM system initialization parameter.) If EDSALIMIT
specifies a value lower than the current limit, CICS may not be able to implement
the new limit immediately, but will attempt to do so over time as dynamic
storage is freed in the individual DSAs.
Function
Change the status of an external data set.
Description
With the SET DSNAME command, you can change the status of a VSAM base data
set. You can use the command to perform the following actions on a data set:
- Mark a VSAM data set as quiesced, or unquiesced, throughout the sysplex.
- Make a VSAM data set available or unavailable to a CICS region. (The availability
function does not operate across the sysplex--a SET DSNAME(...) AVAILABILITY
command is effective only within the CICS region in which it is issued.)
- Retry all UOW log records that are shunted because of the failures of
this data set (other than in-doubt failures).
- Force any UOWs that are shunted because of in-doubt failures, and which
have updated this data set, to complete.
- Purge shunted UOW log records that hold retained locks (other than those
due to in-doubt failures) for any records in the data set, and release the
retained locks,
- Cancel any attempt to recover lost RLS locks for the data set using the
UOWACTION and ACTION(RESETLOCKS) options.
The SET DSNAME command does not distinguish between data sets accessed
in RLS and non-RLS mode.
The new options for the SET DSNAME command are subject to the following
rules relating to the order of processing and the combinations of keywords
and multiple keywords on the same command:
- If REMOVE is specified, no other attribute is allowed.
- Options are processed in the following order:
- RECOVERED
- UNQUIESCED
- AVAILABLE
- RETRY
- UOWACTION
- RESETLOCKS
- UNAVAILABLE
- QUIESCED.
If you specify RETRY, do not also specify UNAVAILABLE or QUIESCED, because
this would cause backout retries to fail. UNQUIESCE should not be specified
with other attributes, because the other options may fail.
Some of the attributes of a data set cannot be set until the first file
that references the data set has been opened. Where an attribute is not valid
until a file has been opened, an error is returned. Note that QUIESCESTATE
is an attribute that can be set before any files have been opened against
the specified data set.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET DSNAME (the minimum abbreviation is CEMT
S DSN) with either a value corresponding to a data set name or ‘ALL’.
You get a display that lists the current status, similar to that obtained
by CEMT INQUIRE DSNAME. You can then tab to the highlighted or blank fields
and overtype them with the required values.
- Type CEMT SET DSNAME (CEMT S DSN) with either a
dataset_name or ‘ALL’, followed by one or more attributes that you
wish to change. For example, cemt s dsn(applb.*) q quiesces all
data sets with a high-level qualifier of APPLB in all CICS regions
within the sysplex.
Resetting the values takes effect immediately.

CEMT SET DSNAME
>>-CEMT Set DSName--+-(value)-+--+------------+----------------->
'-ALl-----' +-REMOve-----+
+-RECOVEREd--+
+-RESetlocks-+
'-RETRy------'
>--+-------------+--+-------------+--+---------+---------------><
+-AVailable---+ +-Quiesced----+ +-BACkout-+
'-UNAvailable-' +-UNQuiesced--+ +-Commit--+
'-IMmquiesced-' '-FOrce---'
Options
- (value)
- specifies one or more names (1-44 characters) of an external data
set.
- ALl
- If you specify the ALL operand on a SET command, any change you request
is made to all resources of the specified type that you are authorized to
access.
- AVailable
- specifies whether the data set is to be marked in this CICS region as
available for use. This command sets the availability indicator, which is
a local flag that a CICS region maintains in a data set name block (DSNB)
for each data set. CICS can issue either RLS or non-RLS open requests for
this data set.
- BACkout
- Specifies that all shunted in-doubt UOWs that hold locks on this data
set should be backed out.
- Commit
- Specifies that all shunted in-doubt UOWs that hold locks on this data
set should be committed.
- FOrce
- Specifies that all shunted in-doubt UOWs that hold locks on this data
set should be forced to BACKOUT or COMMIT as specified by the ACTION attribute
on the transaction resource definition.
- IMmquiesced
- Causes all existing CICS open RLS-mode files throughout the sysplex
to be closed and the data set to be marked as quiesced in the ICF catalog.
Each CICS in the sysplex abends all in-flight UOWs that are accessing the
data set before closing files, causing in-flight UOWs to back out. Any UOWs that
fail backout are shunted. No RLS-mode files can open against this data set,
but non-RLS-mode open requests are permitted.
In addition to closing open
files, IMMQUIESCED sets the file state to UNENABLED if it was ENABLED. A subsequent
SET DSNAME UNQUIESCED command restores the file state to ENABLED, if it was
set UNENABLED by a QUIESCED or IMMQUIESCED action, but not if the UNENABLED state is due to some other event. This state change
is recorded in the CICS global catalog.
Attention
Using the IMMQUIESCED option causes any tasks currently using the data
set to be terminated immediately, using the CICS task FORCEPURGE mechanism.
In some extreme cases CICS may terminate abnormally. For this reason, setting
a data set as quiesced using the IMMQUIESCED option should be restricted to
exceptional circumstances.
- Quiesced
- Causes all existing CICS files open in RLS mode throughout the sysplex
to be closed and the data set to be marked as quiesced in the ICF catalog.
Each CICS in the sysplex waits until all in-flight UOWs that are accessing
the data set have reached syncpoint before closing the files; that is, the UOWs are
either:
- Successfully committed or
- Successfully backed out, or
- Shunted because they failed in-doubt, or
- Shunted because they failed commit, or
- Shunted because they failed backout.
No files can open in RLS mode against this data set, but non-RLS
open requests are permitted.
In addition to closing open files, QUIESCED
sets the file state to UNENABLED if it was ENABLED. A subsequent SET DSNAME
UNQUIESCED command restores the file state to ENABLED, if it was set UNENABLED
by a QUIESCED or IMMQUIESCED action, but not if the
UNENABLED state is due to some other event. This state change is recorded
in the CICS global catalog.
- RECOVEREd
- The data set has been restored from a backup version and forward recovery
has run and completed successfully. CICS normally updates the backup-while-open
(BWO) attributes for the base cluster data set BASEDSNAME, using MVS/DFP 3.2
Callable Services.
If the BWO attributes are not updated after the restore
of a backup copy of a data set that was taken using BWO, CICS fails a subsequent
file open because the data set is marked as down-level.
- REMOve
- This option is used when a data set is no longer required on the local
system. It deletes the data set name block for the named data set. The REMOVE
option can be used only when there are no file control resource definition
entries that refer to the specified data set. If any file definitions refer
to the data set name when you enter SET DSNAME REMOVE, you receive an error
message indicating that the use count of the data set name block is not zero.
To ensure that no file definitions refer to the data set name:
If you have a base data set with one or more alternate indexes, you
are unable to remove the data set name block for the base until you have removed
all references to the base data set and all references to paths.
- RESetlocks (vsam only)
- Purges shunted UOW log records for backout-failed and commit-failed UOWs that
hold locks on this data set, and releases the retained locks:
- Backout-failed UOWs are those that failed during backout processing.
- Commit-failed UOWs are those that have updated RLS data sets, and have
failed to release locks during the second phase of 2-phase commit syncpoint
processing.
If you specify this option, you are accepting backout failure and
some loss of data integrity rather than retaining locks and delaying transactions,
and therefore it should be used only as a last resort.
For backout-failed
and commit-failed UOWs that hold locks on the data set, all records relating
to this data set are removed from the system log and all retained record locks
held by this CICS for the data set are released. Diagnostic messages are written
to the CSFL transient data queue for each backout-failed log record that is
removed as a result of the RESETLOCKS operation.
RESETLOCKS applies
only to shunted UOW log records that are classed as backout-failed and commit-failed.
Therefore it cannot be issued for a BDAM data set. Backout-failed and commit-failed
log records are not shunted for BDAM data sets.
You might use RESETLOCKS
if backout-failed or commit-failed log records are holding up lost locks recovery
for the data set, and there is no other way of resolving them.
Notes:
- This option does not apply to shunted in-doubt UOWs.
Try to resolve the shunted in-doubt UOWs that hold locks on the data set
in other ways before issuing RESETLOCKS; for example, by using COMMIT, BACKOUT,
or FORCEUOW.
- RESETLOCKS can fail during the commit phase (for example, if an error
occurs while CICS is trying to release the RLS locks), in which case the UOWs revert
to being shunted as commit-failed UOWs.
- RETRy
- Specifies that shunted UOW log records, caused by failed backout and
commit processing as a result of the failure of this data set, should be retried.
This is similar in operation to the EXEC CICS RESYNC command, but applies
to backout-failed and commit-failed UOWs only, and not to in-doubt UOWs.
You should use RETRY when the data set has shunted backout- or commit-failed UOWs associated
with it, and you believe that some or all of the data set problems are either
transient or have been resolved.
Messages, issued at the time of a data
set failure that causes UOWs to be shunted, recommend the actions that are
required to recover from the failure.
RETRY does not affect data integrity,
and can be used safely at any time to enable some failed recovery work to
complete.
- UNAvailable
- Marks the data set as unavailable, and prevents the data set being opened
in either RLS or non-RLS modes. This command sets or unsets the availability
indicator, which is a local flag that a CICS region maintains in a data set
name block (DSNB) for each data set.
- UNQuiesced
- Causes the data set to be marked as unquiesced in the ICF catalog. RLS
or non-RLS mode files can be opened against this data set, the access mode
(RLS or non-RLS) being established by the first open.
If a file has been
set UNENABLED by a SET DSNAME IMMQUIESCED or QUIESCED command, UNQUIESCED
sets it back to ENABLED, provided that there have been no other explicit changes
to the enablement state in the meantime. This state change is recorded in
the CICS global catalog.
Function
Change the attributes of a CICS dump data set.
Description
Using SET DUMPDS, you can open or close the active CICS dump data set,
and specify whether or not the automatic switch to the inactive dump data
set occurs when the active dump data set is full.
For more information about dumps, see the CICS Problem Determination Guide.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET DUMPDS (the minimum abbreviation is CEMT
S DU). You get a display that lists the current status, similar to that
obtained by CEMT INQUIRE DUMPDS. You can then tab to the highlighted or blank
fields and overtype them with the required values.
- Type CEMT SET DUMPDS (CEMT S DU) followed by one
or more attribute settings that you wish to change. For example, cemt
s du o a will open the active dump data set and cause autoswitch to
occur only when the active dump data set is full.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET DUMPDS
>>-CEMT Set DUmpds--+--------+--+--------------+---------------><
+-Open---+ +-Autoswitch---+
+-CLosed-+ '-Noautoswitch-'
'-Switch-'
Options
- Autoswitch
- The switch occurs only when the active dump data
set is full, but not subsequently.
- CLosed
- The active CICS dump data set is closed.
- Noautoswitch
- When the active dump data set is full, there is not to be an automatic
switch to the inactive dump data set.
- Open
- The active CICS dump data set is opened.
- Switch
- The currently active dump data set is to become inactive, and the currently
inactive data set is to become active.
Function
Set the status of enqmodel definitions on the local system.
Description
Each ENQMODEL definition may be in one of the following states
- ENABLED
- Matching ENQ requests will be processed in the normal way.
- DISABLED
- Matching ENQ requests will be rejected, and the issuing task abended
abcode ENQ_DISABLED. Matching INSTALL/CREATE/DISCARD requests will be processed.
- WAITING
- Matching ENQ requests will be rejected, and the issuing task abended
abcode ENQ_DISABLED. There are INSTALL/CREATE/DISCARD requests waiting to
be processed.
This command provides a means for you to set the ENABLED and DISABLED states
for ENQmodel resources installed on the local system. An enqmodel must be
enabled to allow matching EXEC ENQ requests to be processed. It must be disabled
to allow a more specific enqmodel to be enabled.
Enqmodels forming nested generic enqnames must be enabled in order, from
the most to the least specific. For example, enable ABCD* then ABC* then AB*.
If
you attempt to enable a more specific enqmodel when a less specific enqmodel
is already enabled, the result is that message DFHNQ0107 is issued.
You cannot enable/disable an enqmodel which is in the waiting state.
Syntax

CEMT SET ENQMODEL
>>-CEMT Set ENQModel(value)--+----------+----------------------><
+-Enabled--+
'-DIsabled-'
Options
- (value)
- The 8-character identifier of the resource definition
- DISABLED
- The ENQMODEL will be put into the WAITING state (See Inquire Enqmodel)
until there are no enqueues in the local system which match the ENQNAME pattern.
It will then be DISABLED. Once DISabled, matching ENQ requests will be rejected,
and the issuing task abended abcode ENQ_DISABLED.
- ENABLED
- If the enqmodel is DISABLED, it will be ENABLED. Once enabled, matching
ENQ requests will be processed in the normal way.
Comments
For information on CEMT SET FECONNECTION, CEMT SET FEPOOL, CEMT SET FEPROPSET,
and CEMT SET FETARGET, see the CICS Front End Programming Interface User’s Guide.
Function
Change some of the attributes of one or more VSAM or BDAM files.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET FILE (the minimum abbreviation is CEMT S
FI) with either a value corresponding to a file name or ALL. You get
a display that lists the current status, similar to that obtained by CEMT
INQUIRE FILE. You can then tab to the highlighted or blank fields and overtype
them with the required values.
- Type CEMT SET FILE (CEMT S FI) with either the name
of a file or ALL, followed by one or more attribute settings that you wish
to change. For example, cemt s fi al op en attempts to set all
files open and enabled for use.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Reset values take effect immediately.
Note:
Some attributes can be changed only when the specified file
is closed and disabled. In these cases, the reset values take effect when
the file is enabled for use again.

CEMT SET FILE
>>-CEMT Set FIle--+-(value)-+--+------------+--+----------+----->
'-ALl-----' +-OPen-------+ +-ENabled--+
+-CLosed-----+ '-DIsabled-'
'-Forceclose-'
>--+--------+--+----------+--+-----------+--+----------+-------->
+-REAd---+ +-UPdate---+ +-ADdable---+ +-BRowse---+
'-NORead-' '-NOUpdate-' '-NOAddable-' '-NOBrowse-'
>--+----------+--+-------------+--+------------+--+-------+----->
+-DElete---+ +-EXclusive---+ +-EMptyreq---+ +-Old---+
'-NODelete-' '-NOEXclusive-' '-NOEMptyreq-' '-Share-'
>--+--------+--+---------------+--+-----------+--+--------+----->
+-RLs----+ '-DSname(value)-' +-NOTTable--+ +-LOAd---+
'-NOTRls-' +-CIcstable-+ '-NOLoad-'
+-USertable-+
'-CFTable---'
>--+-----------------+--+------------------+--+------------+---->
'-CFDtpool(value)-' '-Tablename(value)-' +-COntention-+
'-LOCking----'
>--+-------------------+--+------------------+------------------>
'-Maxnumrecs(value)-' '-Keylength(value)-'
>--+-------------------+---------------------------------------><
'-RECordsize(value)-'
Options
- (value)
- One or more names (1-8 characters) defined in the file control
table (FCT).
- ADdable
- You can add records to the file.
- ALl
- Any change you request is made to all files that you are authorized
to access.
- BRowse
- You can browse records in the file.
- CFDtpool (value)
- specifies the name of the CFDT pool in which the coupling facility data table resides.
- CFtable
- The file name represents a coupling facility data table.
- CIcstable
- The file name represents a CICS-maintained data table.
- CLosed
- The file is closed; the access method does not allow accesses to the
data until the file is opened. The file can be opened either explicitly by
the user or, if the file has the ENABLED attribute, implicitly by CICS on
the next reference to the file.
When the SET FILE CLOSED command is used,
the file is closed and also disabled (set UNENABLED). (A file disabled in
this way prevents access requests from implicitly opening the file again.)
The close is effected at the time of the command only if there are no tasks
currently accessing the file. If there are current users, the display indicates
CLOSE requested. This means that, when the last user finishes using the file,
it effects the close.
A file that has been disabled by a SET FILE CLOSED
command becomes enabled again by a subsequent SET FILE OPEN command. To distinguish
a file that has been disabled by a SET FILE CLOSED from one that has been
disabled by a SET FILE DISABLED command, the SET FILE CLOSED command closes
the file with the UNENABLED attribute.
A file with the DISABLED attribute
can be enabled only by a SET FILE ENABLED command. A file with the UNENABLED
attribute can be enabled by a SET FILE ENABLED or SET FILE OPEN command.
- COntention (CFDT only)
- The coupling facility data table is to use the contention model, in which records are not
locked when they are read for update, but an error is returned on a subsequent
REWRITE or DELETE if the record has changed or been deleted since it was read
for update.
- DElete
- You can delete records from the file.
- DIsabled
- The file is not available for use by transactions except for those that
are currently using it. If there are any such users, ‘BEING DISABLED’
is also displayed. The CEMT SET FILE DISABLED command has no effect on existing
users; it simply prevents new users from accessing the file.
The file can
be reenabled by a SET FILE ENABLED command. (See also UNENABLED.)
It is not possible to disable a remote file.
- DSname (value)
- specifies the name (1-44 characters) of the VSAM or BDAM data
set with which this file is associated. CEMT SET FILE(value) DSNAME(value) associates the data set with the file and causes the FILECOUNT
of the data set to be incremented by 1. You can use CEMT SET FILE DSNAME
with a null DSNAME value to dissociate a file from its current data set.
Note:
DSNAME replaced OBJECTNAME.
- EMptyreq (vsam only)
- Applies only to a VSAM file that has been defined to VSAM as a cluster
with the REUSE parameter, and which is opened in non-RLS access mode. It indicates
that when a file is next opened, its data is erased.
If the file is opened
in RLS access mode this parameter has no effect.
A CEMT SET FILE EMPTYREC
command can be applied only to files that are closed and either disabled or
unenabled, and has no effect on the data until the file is opened. A SET FILE
EMPTYREQ command can be canceled by a SET FILE NOEMPTYREQ command.
- ENabled
- The file is available for use by transactions and, if closed, it is
opened on the first request. If the command CEMT SET FILE(value)
CLOSED ENABLED is given while the file is in use, the status of the file becomes ‘closed-unenabled’.
If the command CEMT SET FILE(value) CLOSED is given while the file
is in use, the file is disabled to prevent new users accessing the file.
- EXclusive
- Records on the file are protected from simultaneous update by being
placed under exclusive control when a read for update is issued.
- Forceclose
- Similar to SET FILE CLOSED, except that any existing users of the file
are abended (abend code ‘AKC3’ or ‘ATCH’). As for CLOSED,
the close is effected by the last of these users.
Data integrity
Closing a file using the FORCECLOSE option causes tasks of any current
users of the file to be terminated immediately by the CICS task FORCEPURGE
mechanism. Data integrity is not guaranteed with this mechanism. In some extreme
cases (for example, if an error occurs during backout processing) CICS might
terminate abnormally. For this reason, closing files using the FORCECLOSE
option should be restricted to exceptional circumstances.
- Keylength (value)
- Specifies the key length of records in a coupling facility data table that does not require
pre-loading from a source data set. To set a keylength, specify a value in
the range 1 through 16. To clear a keylength (set it to null values),
specify KEYLENGTH(0).
You can specify the key length for a file that does
not currently refer to a coupling facility data table, but which could be switched to use a coupling facility data table
at a later date.
- LOAd
- The coupling facility data table requires loading from a source data set before it is fully
usable; the transactions that use this coupling facility data table rely on it containing the records
from the specified source data set.
- LOCking (CFDT only)
- The coupling facility data table is to use the locking model, in which records are locked
when they are updated.
- Maxnumrecs (value)
- specifies the maximum number of records that the data table for this
file can hold.
For any type of table, if you want to set a limit, specify
a value in the range 1 to 99 999 999. If you do not
want any limit to apply, specify MAXNUMRECS(0), which CICS interprets as no
limit, and sets internally to the maximum positive fullword value (+2147483647
or X'7FFFFFFF').
Note:
The new value takes effect only
when a new data table is created. This happens on each file open for a CICS-maintained
or user-maintained data table, but only when the table does not already exist
for a CF data table. Once a coupling facility data table has been created, you can change the maximum
number of records only through the CFDT server MVS command interface.
To specify MAXNUMRECS for a recoverable coupling facility data table, use a value that
is between 5 and 10% more than the maximum number of records that
the table is expected to contain. This allows for additional records that
might be created internally for processing recoverable requests. The margin
to be left for this internal processing depends on the level of use of the coupling facility data table,
and the nature of that use. An effect of this is that the NOSPACE condition
(with a RESP2 of 102) can be raised on a WRITE or REWRITE request to a recoverable coupling facility data table
that apparently has fewer records than the MAXNUMRECS limit specifies.
- NOAddable
- You cannot add records to the file.
- NOBrowse
- You cannot browse records in the file.
- NODelete
- You cannot delete records from the file.
- NOEMptyreq (vsam only)
- Applies only to VSAM files. It indicates that when a file is next opened,
its data is not erased.
A CEMT SET FILE NOEMPTYREC command can be applied
only to files that are closed and either disabled or unenabled, and cancels
the implicit request in a previous SET FILE EMPTYREQ command.
- NOEXclusive
- Records on the file are not protected from simultaneous update.
- NOLoad
- The coupling facility data table does not require loading from a source data set. It is fully
usable as soon as it is created, and is populated entirely by the transactions
that use it.
- NORead
- You cannot read records in the file.
- NOTRls (vsam only)
- The file is defined to be accessed in a non-RLS mode (LSR or NSR).
For information about switching from RLS to non-RLS mode, see the CICS Recovery and Restart Guide.
- NOTTable
- The file name does not represent a data table.
- NOUpdate
- You cannot update records in the file.
- Old
- The disposition of the data set associated with the file is defined
as unshared for dynamic allocation.
- OPen
- The file is open. If the file is OPEN ENABLED, it is available for data
accesses by CICS transactions. If it is OPEN DISABLED, it must first be enabled
before it is available.
If the file was unenabled by a previous SET FILE
CLOSED command, the SET FILE OPEN command reenables the file implicitly.
- REAd
- You can read records in the file.
- RECordsize
- specifies the maximum record size for a coupling facility data table that does not require
pre-loading from a source data set.
You can specify the record size for
a file that does not currently refer to a coupling facility data table, but which could be switched
to use a coupling facility data table at a later date. Specify a record size of 1- to 32767-bytes,
or specify a record size of zero to remove a previously defined value.
- RLs (vsam only)
- The file is defined to be accessed in RLS mode.
- Share
- The disposition of the data set associated with the file is defined
as shared for dynamic allocation.
- Tablename (value)
- specifies the name of the table for a coupling facility data table.
- UPdate
- You can update records in the file.
- USertable
- The file name represents a user-maintained data table.
Function
Change the status of GTF tracing
Description
SET GTFTRACE allows you to switch CICS tracing to the MVS Generalized Tracing
Facility (GTF) on and off.
This command is intended for use at terminals that do not support the CETR
full-screen tracing transaction.
For guidance on using GTF tracing, see the CICS Problem Determination Guide.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET GTFTRACE (the minimum abbreviation is CEMT
S G). You get a display that lists the current status, similar to that
obtained by CEMT INQUIRE GTFTRACE. You can then tab to the highlighted field
and overtype it with the required value.
- Type CEMT SET GTFTRACE (CEMT S G) followed by the
attribute setting that you wish to change. For example, cemt s g sta will cause CICS GTF tracing to be started.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET GTFTRACE
>>-CEMT Set Gtftrace--+-------+--------------------------------><
+-STArt-+
'-STOp--'
Options
- STArt
- CICS tracing to the MVS Generalized Tracing Facility (GTF) is started.
- STOp
- CICS tracing to the MVS Generalized Tracing Facility (GTF) is stopped.
Function
Enable or disable a virtual host.
Description
The SET HOST command is used to set the status of a virtual host to enabled
or disabled. Disabling a virtual host means that all the URIMAP definitions
that make up the virtual host cannot be accessed. When a virtual host is disabled,
CICS returns an HTTP response with a 503 (Service Unavailable) status code
to Web clients.
When you inquire on an individual URIMAP definition, a special status HDISABLED
is returned to indicate that the virtual host is disabled. You do not need
to change the disabled status of the URIMAP definitions individually; the
SET HOST command can be used to re-enable all the URIMAP definitions that
make up the virtual host. However, note that a URIMAP definition with the HDISABLED
status cannot be discarded. If you want to discard the definition, it must
be disabled individually (using the SET URIMAP command).
Syntax

CEMT SET HOST
>>-CEMT Set Host--+-(value)-+--+-Enabled--+--------------------><
'-ALl-----' '-Disabled-'
Options
- (value)
- specifies the name of the virtual host to which this command applies.
The name of each virtual host is taken from the host name specified in the
URIMAP definitions that make up the virtual host. For example, if your CICS
region contained URIMAP definitions that specified a host name of www.research.ibm.com,
CICS would create a virtual host with the name www.research.ibm.com. A host
name in a URIMAP definition can be up to 120 characters.
- Enabled
- The URIMAP definitions that make up the virtual host can be accessed.
- Disabled
- The URIMAP definitions that make up the virtual host cannot be accessed.
Function
Switch CICS internal tracing on or off.
Description
SET INTTRACE allows you to switch CICS internal tracing on and off.
This command is intended for use at terminals that do not support the full-screen
tracing transaction CETR.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET INTTRACE (the minimum abbreviation is CEMT
S IN). You get a display that lists the current status, similar to that
obtained by CEMT INQUIRE INTTRACE. You can then tab to the highlighted field
and overtype it with the required value.
- Type CEMT SET INTTRACE (CEMT S IN) followed by the
attribute setting that you wish to change. For example, cemt s in sta will cause CICS internal tracing to be started.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET INTTRACE
>>-CEMT Set INttrace--+-------+--------------------------------><
+-STArt-+
'-STOp--'
Options
- STArt
- CICS internal tracing is started.
- STOp
- CICS internal tracing is stopped.
Function
Open or close the interregion communication (IRC) facility.
Description
New MRO connections can be installed without first closing IRC. However,
if you want to modify existing MRO connections, IRC must be closed using the
SET IRC CLOSED command. For example:
CEMT SET IRC CLOSED
CEDA INSTALL GROUP(groupname)
CEMT SET IRC OPEN
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET IRC (the minimum abbreviation is CEMT S
IR). You get a display that lists the current status, similar to that
obtained by CEMT INQUIRE IRC. You can then tab to the highlighted field and
overtype it with the required value.
- Type CEMT SET IRC (CEMT S IR) followed by the attribute
setting that you wish to change. For example, cemt s ir o will
cause interregion communication to be initialized.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET IRC
>>-CEMT SET IRc--+-Open-----+----------------------------------><
+-Closed---+
'-Immclose-'
Options
- Closed
- Interregion communication for this CICS system is to be terminated after
all tasks using IRC sessions have terminated normally.
- Immclose
- All tasks using IRC sessions are to be abended when they next try to
use the session. Interregion communication is terminated when all tasks that
were using IRC have been abended or have terminated normally.
- Open
- Interregion communication for this CICS system is to be initialized.
This allows connections to be established between this system and other systems,
including DL/I batch regions and non-CICS client programs using the external
CICS interface (EXCI). You can control the availability of individual connections
with the INSERVICE|OUTSERVICE settings on the connection names.
The
DFHIR3780 message and CICS interregion communication program (IRP) return
and reason codes are displayed if IRC fails to open. For a description of
DFHIR3780, see the CICS Messages and Codes manual.
Function
Enable or disable a CICS user journal.
Description
The SET JOURNALNAME command allows you to enable or disable a CICS user
journal. It has no effect on a journal that is being used as the forward recovery
log or auto-journal for a VSAM file until the next time the file is opened
or on the system log.
You can use SET JOURNALNAME for a journal name that is not currently known
to CICS. CICS dynamically creates an entry for the specified journal and,
if necessary, defines it to the MVS system logger using a matching JOURNALMODEL
definition (see the CICS Resource Definition Guide.)
Syntax

CEMT SET JOURNALNAME
>>-CEMT Set Journalname(value)--+-(value)-+--+----------+------->
'-+-----+-' +-Enabled--+
'-All-' '-DIsabled-'
>--+-------+---------------------------------------------------><
+-FLush-+
'-Reset-'
Options
- (value)
- Specifies the journal name.
To modify journals defined with a numeric
identifier in the range 1-99, specify journal name DFHJnn, where nn is the journal number.
You
cannot specify DFHLOG or DFHSHUNT, because you are not allowed to modify the
status of the system log.
- All
- specifies that any changes you request are made to all resources of
the specified type that you are authorized to access.
- DIsabled
- The journal is disabled. It cannot be used again until it is reenabled
by a SET JOURNALNAME(...) STATUS(ENABLED) or ACTION(RESET) command.
- Enabled
- The journal is open and is available for use.
- FLush
- The log buffers are written out to the log stream but the journal is
not closed.
You can use this option to ensure that all current records
are written out to the log stream before the stream is processed using a batch
utility.
- Reset
- The journal is disabled, but can be reenabled by the next SET JOURNALNAME
STATUS(ENABLED) or ACTION(RESET) command for this journal.
Function
Change the status of a JVM pool.
Description
The SET JVMPOOL command allows you to enable or disable the
JVM pool, or to terminate the pool altogether. When you terminate the pool,
all the JVMs in the pool, both worker JVMs using the shared class cache and
JVMs running independently of the shared class cache, are terminated. No more
JVMs can use the existing 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.
Syntax
Press the Clear key to clear the screen and enter CEMT SET JVMPOOL (the minimum abbreviation is CEMT S JVMP). This gives you
a display that lists the current status, similar to that obtained by CEMT
INQUIRE JVMPOOL. You can then tab to the highlighted or blank fields and overtype
them with the required values.
Typing ? at the end of the first line or the beginning of
the second line gives a syntax prompt. Resetting the values takes effect immediately.

CEMT SET JVMPOOL
>>-CEMT Set JVmpool--+----------+--+------------+--------------><
+-Enabled--+ +-Phaseout---+
'-Disabled-' +-Purge------+
'-Forcepurge-'
Options
- Disabled
- The pool status is set to disabled, preventing new requests from being
serviced from the pool. Programs that were started before the command is issued
are allowed to excute to completion.
- Enabled
- The pool status is set to enabled for use and Java programs can execute
using JVMs from the pool.
- Forcepurge
- All tasks using JVMs in the pool are terminated by the SET TASK FORCEPURGE
mechanism. The shared class cache is deleted when all the worker JVMs that
were dependent on it have been terminated.
- Phaseout
- All JVMs in the pool are marked for deletion. The JVMs are actually
deleted when they finish running their current Java program. The shared class
cache is deleted when all the worker JVMs that were dependent on it have been
terminated.
- Purge
- All tasks using JVMs in the pool are terminated by the SET TASK PURGE
mechanism, and the JVMs are terminated. The shared class cache is deleted
when all the worker JVMs that were dependent on it have been terminated.
Function
Change the status of a line.
Description
The SET LINE command allows you to purge or forcepurge a line, to put the
line in or out of service, and to adjust the relative line number.
You can specify a list of identifiers (see List of resource identifiers), but
you cannot use the symbols * and + to specify a family of identifiers.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET LINE (the minimum abbreviation is CEMT S
L) with a terminal identifier. You get a display that lists the current
status, similar to that obtained by CEMT INQUIRE LINE. You can then tab to
the highlighted or blank fields and overtype them with the required values.
- Type CEMT SET LINE (CEMT S L) with a termiinal identifier,
followed by one or more attribute settings that you wish to change. For example, cemt s l(value) i will make the line available for use (inservice).
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET LINE
>>-CEMT Set Line(value)--+---------------+---------------------->
'-NUmber(value)-'
>--+----------------+--+------------+--+------------+----------><
'-NEgpoll(value)-' +-Inservice--+ +-Purge------+
'-Outservice-' '-Forcepurge-'
Options
- (value)
- specifies the identifier of a terminal on the line. This request is
valid only for non-VTAM terminals.
- Forcepurge
- All transactions running with terminals on the line are immediately
terminated abnormally. Data integrity is not guaranteed. In some extreme cases
(for example, if an error occurs during backout processing), CICS might terminate
abnormally.
- Inservice
- The line is available for use. Changing the status of the line does
not affect the equivalent status of the terminals on it.
- NUmber (value)
- specifies the relative line number of a pooled line. It is mandatory
when inquiring about pooled lines. For information about pooled lines, see the CICS Resource Definition Guide.
- Outservice
- The line is not available for use. Changing the status of the line does
not affect the equivalent status of the terminals on it.
- Purge
- Tasks running on terminals associated with the line are abnormally terminated,
but task termination occurs only if system and data integrity can be maintained.
Function
Change the status of a mode name.
Description
The SET MODENAME command is used to reset the connection to a remote system
or to another CICS region, change the number of sessions available, and acquire
or close the sessions associated with the mode name.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET MODENAME (the minimum abbreviation is CEMT
S MOD) with either a modename or ALL. You get a display that lists the
current status, similar to that obtained by CEMT INQUIRE MODENAME. You can
then tab to the highlighted or blank fields and overtype them with the required
values.
- Type CEMT SET MODENAME (CEMT S MOD) with either
a modename or ALL, followed by one or more attribute settings that you wish
to change. For example, cemt s mod(modename) acq will cause CICS
to acquire all the negotiated contention-winner sessions within the group
named by modename.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET MODENAME
>>-CEMT Set MODename--+-(value)-+--+-------------------+-------->
'-ALl-----' '-COnnection(value)-'
>--+------------------+--+----------+--------------------------><
'-AVailable(value)-' +-ACQuired-+
'-CLosed---'
Options
- (value)
- specifies one or more names (1-8 characters) of a group of sessions.
Mode names need not be unique. You cannot specify a list of names, but you
can use the symbols * and + to specify a family of mode names.
A mode name
consisting of eight blanks is valid. To specify this name, enclose the string
of blanks within single quotation marks:
MODENAME(' ')
- ACQuired
- CICS is to acquire (or "bind") all the negotiated contention-winner
sessions within the group.
- ALl
- specifies that any changes you request are done to all resources of
the specified type that you are authorized to access.
- AVailable (value)
- specifies the maximum number of sessions within the group that can be
concurrently allocated for use. This value has to be the same for both sides
involved in the session.
- CLosed
- CICS is to release all sessions within the group. The sessions are quiesced
and unbound. No further sessions can be acquired by another CICS system. No
further activity is possible on the sessions within the group until the group
is reacquired by the same CICS system in which it has been closed.
- COnnection (value)
- specifies an identifier (1-4 characters) defined for an IRC or
ISC connection.
Function
Change the status of monitoring.
Description
SET MONITOR allows you to select the classes of monitoring data you want
collected, switch monitoring on or off, and set the status of monitoring options.
For programming information on the monitoring classes, see the CICS Customization Guide.
Notes:
- When you change the status of CICS monitoring from OFF to ON, CICS starts
to accumulate monitoring data, and to write monitoring records for the active
monitoring classes, for all tasks that start after the
change is made. The monitoring status of tasks being processed is not affected.
- When you change the status of CICS monitoring from ON to OFF, CICS stops
writing monitoring data immediately. No monitoring data is accumulated for
tasks that start after the change is made.
- The monitoring class settings can be changed irrespective of whether monitoring
is ON or OFF.
If monitoring is OFF, you can change the class settings as
required in preparation for the next time STATUS is set to ON.
If monitoring
is ON, changes to the class settings have the following effects:
- Changing a class from not-active to active has no effect on the data written
for running tasks.
- Changing a class from active to not-active prevents monitoring data for
that class being written for running tasks as follows:
- Performance
- Any performance class data remaining in the output buffer is recorded,
and no further data is collected.
- Exception
- Monitoring data is not written at the completion of the exception condition.
- Resource
- Any transaction resource monitoring data remaining in the output buffer
is recorded, and no further data is collected.
- Exception class, transaction resource class, and performance
class data are gathered during the life of a running transaction. When you
change these settings, you should be aware of their impact on transactions
that are running. For example, if a transaction is started when the performance
class is set to PERF and monitoring is ON, performance class data is accumulated
for that transaction. If you switch the performance class to NOPERF while
the transaction is running, and then back to PERF before the transaction ends,
performance data will be missing from the final monitoring data for that transaction,
even though, when it started and when it ended, the performance class was
set to PERF. Transaction resource monitoring
is treated the same as the performance class.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET MONITOR (the minimum abbreviation is CEMT
S MON). You get a display that lists the current status, similar to
that obtained by CEMT INQUIRE MONITOR. You can then tab to the highlighted
or blank fields and overtype them with the required values.
- Type CEMT SET MONITOR (CEMT S MON) followed by one
or more attribute settings that you wish to change. For example, cemt
s mon on p ex will set CICS monitoring ON and collect performance-class
and exception-class data.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET MONITOR
>>-CEMT Set MONitor--+-----+--+--------+--+----------+---------->
+-ON--+ +-Perf---+ +-EXcept---+
'-OFf-' '-NOPerf-' '-NOEXcept-'
>--+----------+--+------------+--+-------------+---------------->
+-Resrce---+ +-Converse---+ +-SYncpoint---+
'-NOResrce-' '-NOConverse-' '-NOSyncpoint-'
>--+------------------+----------------------------------------><
'-Frequency(value)-'
Options
- Converse
- Conversational tasks are to have separate performance class records
produced for each pair of terminal control I/O requests (Converse or Send/Receive
pair).
- EXcept
- The exception class of monitoring data is to be collected.
- Frequency (value)
- specifies the interval for which monitoring produces automatically a
transaction performance class record for any long-running transaction that
has been in the system for a greater time than the interval. Frequency times
are 0, or in the range 000100-024000. The default frequency value is
0, which means that FREQUENCY monitoring is inactive (that is, no performance
class records are produced for long-running transactions).
- NOConverse
- Conversational tasks are not to have separate performance class records
produced for each pair of terminal control I/O requests (Converse or Send/Receive
pair).
- NOEXcept
- The exception class of monitoring data is not to be collected.
- NOPerf
- The performance class of monitoring data is not to be collected.
- NOResrce
- Transaction resource monitoring data is not to be collected.
- NOSyncpoint
- A transaction performance class record is not to be produced when a
transaction takes an explicit or implicit syncpoint (unit-of-work), except
when the syncpoint is part of task termination or a syncpoint rollback.
- OFf
- CICS monitoring is to be switched off. When monitoring is OFF, no monitoring
data is accumulated or collected, irrespective of the settings of the monitoring
data classes.
- ON
- CICS monitoring is to be switched on. When monitoring is ON, monitoring
data is accumulated continuously, and is collected (written out to an SMF
data set) for each of the classes of monitoring data that are active.
- Perf
- The performance class of monitoring data is to be collected.
- Resrce
- Transaction resource monitoring data is to be collected.
- SYncpoint
- A transaction performance class record is to be produced when a transaction
takes an explicit or implicit syncpoint (unit-of-work), except when the syncpoint
is part of task termination or a syncpoint rollback.
Function
Change the status of networks.
Description
If you are familiar with network names, you may prefer to use this command
as an alternative to CEMT SET TERMINAL (described under CEMT SET TERMINAL).
However, CEMT SET NETNAME cannot be used for APPC sessions.
"netname" is the name by which the remote system or terminal is
known to the network. The remaining operands for NETNAME are identical to
those for TERMINAL.
Netnames need not be unique, and you cannot specify a list of names.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET NETNAME (the minimum abbreviation is CEMT
S N) with netname or ALL. You get a display that lists the current status,
similar to that obtained by CEMT INQUIRE NETNAME. You can then tab to the
highlighted or blank fields and overtype them with the required values.
- Type CEMT SET NETNAME (CEMT S AUTO) with netname
or ALL, followed by one or more attribute settings that you wish to change.
For example, cemt s n(netname) i at will reset the named remote
system or terminal to inservice and available for use.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET NETNAME
>>-CEMT Set Netname--+-(value)-+--+-----------------+----------->
'-ALl-----' '-PRiority(value)-'
>--+--------------+--+------------+--+-------+--+-------+------->
+-PAgeable-----+ +-Inservice--+ +-ATi---+ +-TTi---+
'-AUtopageable-' '-Outservice-' '-NOAti-' '-NOTti-'
>--+------------+--+----------+--+----------+------------------><
+-PUrge------+ +-ACquired-+ +-CReate---+
'-Forcepurge-' +-COldacq--+ '-NOCreate-'
'-RELeased-'
Options
- (value)
- specifies the name by which the remote terminal is known in the network.
- ACquired (vtam only)
- CICS is in session with the logical unit represented by the terminal.
- ALl
- specifies that any changes you request are made to all resources of
the specified type that you are authorized to access.
- ATi (vtam only)
- The terminal is available for use by transactions that are initiated
automatically from within CICS or, if the terminal is an ISC session, by transactions
that are using this session as an alternative facility to communicate with
another system.
- AUtopageable (vtam only)
- Pages after the first in a series are to be written to the terminal
automatically.
- COldacq (vtam only)
- This is a special form of ACQUIRED, where no resynchronization is required.
If the previous session abended, the use of COLDACQ overrides CICS integrity
control. This could lead to integrity problems. Also, you should check the
CSMT log for an activity keypoint after the restart of a session following
a CICS failure. If there is no activity keypoint, you should issue COLDACQ
again after the next emergency restart.
- CReate (vtam only)
- If the terminal is not in session, CICS is to acquire it if it is needed
to satisfy an ATI request. This cannot be specified for IRC sessions.
- Forcepurge
- All transactions running with this terminal are immediately terminated
abnormally. Data integrity is not guaranteed. In some extreme cases (for example,
if an error occurs during backout processing), CICS might terminate abnormally.
- Inservice (vtam only)
- The terminal is available for use. For VTAM, INSERVICE means that the
terminal can be ACQUIRED.
- NOAti (vtam only)
- The terminal is not available for use by transactions that are initiated
automatically from within CICS or, if the terminal is an ISC session, by transactions
that are using this session as an alternative facility to communicate with
another system.
Note:
A terminal cannot be defined with both NOATI
and NOTTI.
- NOCreate (vtam only)
- If the terminal is not in session, CICS is not to acquire it to satisfy
an ATI request. A session must be started by, for example, a logon request
or a CEMT SET TERMINAL ACQUIRED command before the ATI request can be satisfied.
If NOCREATE is set for an LU6.1 ISC session and there are no allocatable sessions
left, the connection is placed OUTSERVICE.
- NOTti (vtam only)
- This terminal cannot be used by transactions.
Note:
A terminal
cannot be defined with both NOATI and NOTTI.
- Outservice (vtam only)
- The terminal is not available for use. Setting a terminal OUTSERVICE
means that the terminal can no longer be used by transactions. If PURGE or
FORCEPURGE is also specified, any transaction using the terminal is terminated
abnormally. If PURGE or FORCEPURGE is not specified, the transaction is allowed
to terminate normally, but no further transactions are allowed to use the
terminal. For VTAM, setting a terminal OUTSERVICE also causes it to be released
and the operator to be signed off, either immediately or when the current
transaction has terminated.
In an LU6.1 ISC session the connection is set
OUTSERVICE if there are no allocatable sessions left.
To set an IRC
session OUTSERVICE, you must set the connection to the MRO partner OUTSERVICE.
- PAgeable (vtam only)
- Pages after the first in a series are to be written to the terminal
only if you request them to be.
- PRiority (value) (vtam only) (VTAM only)
- specifies the priority of a terminal relative to other terminals. The
priority of a task is the sum of the transaction priority, the terminal priority,
and the operator priority. Priority has no meaning for terminals that are
ISC sessions being used as alternative facilities. The value must be in the
range 0-255, where 255 is the highest priority.
- PUrge
- Tasks running on this terminal are abnormally terminated, but task termination
occurs only if system integrity can be maintained.
- RELeased (vtam only)
- CICS is not in session with the logical unit represented by the terminal.
Setting a terminal RELEASED causes the session to be terminated. Running transactions
are allowed to finish unless PURGE or FORCEPURGE is also specified.
- TTi (vtam only)
- This terminal can be used by transactions.
Function
Enable or disable a PIPELINE.
Description
If the optional attributes are omitted, the command has no effect.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET PIPELINE (the minimum abbreviation is CEMT
S PI) followed by one or more PIPELINE identifiers or ALL. You get a
display that lists the current status, similar to that obtained by CEMT INQUIRE
PIPELINE. You can then tab to the highlighted or blank fields and overtype
them with the required values.
- Type CEMT SET PIPELINE (CEMT S PI) followed by one
or more PIPELINE identifiers or ALL, followed in turn by one or more attribute
settings that you wish to change. For example, cemt s pi al e
resets the values for all PIPELINEs to make them available for use (enabled).
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

SET PIPELINE
.-ALl-----.
>>-CEMT SET PIPELINE--+---------+--+----------+----------------><
'-(value)-' +-Enabled--+
'-Disabled-'
Conditions: NOTAUTH, NOTFND
Options
- ALl
- Any changes you request are made to all resources of the specified type
that you are authorized to access.
- (value)
- specifies the 1-8 character name of the PIPELINE.
- Enablestatus
- Sets the status of the PIPELINE:
- Enabled
- The PIPELINE is ready for use.
- Disabled
- The PIPELINE is not processing requests, and is unable to accept new
work. It may have failed to initialize, or may have been explicitly disabled.
Function
Change the attributes of a CICS business transaction services process-type.
Description
SET PROCESSTYPE enables you to change the current state of audit logging
and the enablement status of BTS PROCESSTYPE definitions installed on this
CICS region.
Note:
Process-types are defined in the process-type table (PTT).
CICS uses the entries in this table to maintain its records of processes (and
their constituent activities) on external data sets. If you are using BTS
in a single CICS region, you can freely use the SET PROCESSTYPE command to
modify your process-types. However, if you are using BTS in a CICSPlex®,
it is strongly recommended that you use CPSM to make such changes. This is
because it is essential to keep resource definitions in step with each other,
across the CICSPlex.
Syntax

CEMT SET PROCESSTYPE
.-ALl-----.
>>-CEMT Set PROCesstype--+---------+--+----------+-------------->
'-(value)-' +-ACtivity-+
+-FUll-----+
+-Off------+
'-Process--'
>--+----------+------------------------------------------------><
+-Enabled--+
'-Disabled-'
Options
- ACtivity|FUll|Off|Process
- specifies the level of audit logging to be applied to processes of this
type.
Note:
If the AUDITLOG attribute of the installed PROCESSTYPE
definition is not set to the name of a CICS journal, an error is returned
if you try to specify any value other than OFF.
The values are:
- ACtivity
- Activity-level auditing. Audit records will be written from:
- The process audit points
- The activity primary audit points.
- FUll
- Full auditing. Audit records will be written from:
- The process audit points
- The activity primary and secondary audit points.
- Off
- No audit trail records will be written.
- Process
- Process-level auditing. Audit records will be written from the process
audit points only.
For details of the records that are written from the process,
activity primary, and activity secondary audit points, see the CICS Business Transaction Servicesmanual.
- ALl
- specifies that any changes you specify are made to all process-types
that you are authorized to access.
- Enabled|Disabled
- specifies whether new processes of this type can be created. The values
are:
- Disabled
- The installed definition of the process-type is disabled. New processes
of this type cannot be defined.
- Enabled
- The installed definition of the process-type is enabled. New processes
of this type can be defined.
- PROCesstype(value)
- specifies the 8-character name of the process-type whose attributes
are to be changed.
Function
Change the attributes of installed programs.
Description
Only programs that have been defined in the CICS system definition (CSD)
file and installed on the running CICS system are accessible through CEMT.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET PROGRAM (the minimum abbreviation is CEMT
S PROG) with pgrmid, CLASS(value), or ALL. You get a display
that lists the current status, similar to that obtained by CEMT INQUIRE PROGRAM.
You can then tab to the highlighted or blank fields and overtype them with
the required values.
- Type CEMT SET PROGRAM (CEMT S PROG) followed by
one or more attribute settings that you wish to change. For example, cemt s prog(pgrmid) e ne will reset the values for the named program
to make it available for use (enabled) and a new copy of the program will
be used when all the transactions currently using the program have finished
(newcopy).
Typing ? at the beginning of either the first or
second line gives a syntax prompt. Resetting the values takes effect immediately.

CEMT SET PROGRAM
>>-CEMT Set Program--+-(value)------+--+----------+------------->
+-ALl----------+ +-Enabled--+
'-CLass(value)-' '-DIsabled-'
.-PRIvate-.
>--+---------+--+---------+--+--------+--+-----------+---------->
'-Shared--' +-NEwcopy-+ +-CEDf---+ +-DPlsubset-+
'-PHasein-' '-NOCedf-' '-Fullapi---'
>--+-----------------+--+-------------------+--+-------+-------><
'-JVMClass(value)-' '-JVMProfile(value)-' +-JVM---+
'-NOJVM-'
Options
- (value)
- specifies a program identifier (1-8 characters), which is the
name of a specific program entry in the table of installed program definitions.
If you omit the program name, the ALL option is assumed by default.
You
cannot specify the CLASS option and a program name.
- ALl
- specifies that any changes you request are to be made to all resources
of the specified type that you are authorized to access.
- CEDf
- When EDF is active, CEDF initiation and termination screens are to be
shown by CEDF while this program is running. Other screens are also to be
shown unless the program was translated using the NOEDF translator option.
- CLass (value)
- specifies the 2-character suffix of a program list table (PLT). Use
this option to inquire on those programs defined in the specified PLT. Note
that, unlike a shutdown PLT, it is not mandatory to define a program definition
for a startup PLT. However, if you want to use the CLASS option, you must
define and install a program resource definition for the PLT specified by "clasid".
If the clasid specified is the suffix of a PLT that does not have a program
definition, the INQUIRE PROGRAM CLASS(clasid) command returns a ‘CLASS
NOT FOUND’ message.
You cannot specify CLASS and a program name.
- DIsabled
- The program is not available for use. Programs beginning with "DFH"
cannot be disabled because these characters are reserved for use by CICS.
- DPlsubset
- The program is restricted to the DPL API subset, as for a distributed
program link request, when it runs in the local CICS region.
A program
is always restricted to the DPL subset when it is invoked in a remote region
via a DPL request, regardless of this option.
- Enabled
- The program is available for use.
- Fullapi
- The program is not restricted to the DPL subset of the CICS API when
it runs in the local CICS region, and can use the full API.
- JVM
- The program is to run under the control of a Java Virtual Machine (JVM).
- JVMClass (value)
- specifies the name of the main JVM class in the Java program that is
to be given control by the JVM.
- JVMProfile (value)
- specifies the 8-character name of a JVM profile that is to be
used for the JVM in which this program runs. Any instances of this program
that are currently running in a JVM with the old JVM profile are unaffected,
and are allowed to finish running.
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.
- NEwcopy
- CICS is to use a new copy of the program whenthe
program ceases to be in use by any transaction. (You can determine whether
a module is in use from the RESCOUNT option in an INQUIRE PROGRAM command;
a value of zero means the program is not in use.) It is possible for CICS
to replace the program with the new version during a single transaction, at
a point when one use of the program has completed, and a subsequent use has
yet to start.
CICS loads the new version either from the DFHRPL library concatenation
or uses an LPA-resident version, depending on the PRIVATE or SHARED options.
PRIVATE is the default setting.
Note:
NEWCOPY cannot be specified
for a program specified with the HOLD option or for a JVM program.
- NOJvm
- The program is not to run under the control a a JVM. Any value in the
JVMCLASS option is ignored and the runtime environment of the program is unknown
until it is next loaded by CICS, at which point its language, and hence whether
it will run with LE370 support, will be determined.
- NOCedf
- All CEDF activities, including initiation and termination screens, are
to stop while this program is being processed.
- PHasein
- CICS is to use a new copy of the program now for all new transaction
requests. CICS continues to use the old copy for all currently running transactions
until they have finished (RESCOUNT equal to zero). CICS loads the new version
either from the DFHRPL library concatenation or uses an LPA-resident version,
depending on the PRIVATE or SHARED options. PRIVATE is the default setting.
Note:
PHASEIN cannot be specified for a program specified with the HOLD
option or for a JVM program.
PHASEIN performs a REFRESH
PROGRAM function to inform the loader domain that a new version of the program
has been cataloged and that this version of the named program should be used
in all future ACQUIRE requests.
Until the program goes to a zero RESCOUNT
and a subsequent ACQUIRE PROGRAM has been performed, CEMT INQUIRE PROGRAM
( ) will return information on the first copy of the program.
- PRIvate
- The next new copy of the program is to be loaded from the DFHRPL library.
This is the default action.
- Shared
- CICS is to use a shared copy of the program from the LPA as the next
new copy of the program. This value is ignored for a JVM program.
Comments
See CEMT SET TDQUEUE. (QUEUE is accepted for INQUIRE commands, but
the correct keyword is TDQUEUE.)
Function
Change statistics attributes.
Description
SET STATISTICS allows you to change some of the values that control the
accumulation and recording of statistics.
For information about printing statistics using the CICS-supplied utility
program DFHSTUP, see the CICS Operations and Utilities Guide.
NEXTTIME cannot be specified on an INQUIRE or SET STATISTICS command, but
its value is displayed when INQUIRE STATISTICS is issued. NEXTTIME indicates
the time at which statistics will next be recorded and reset. If SET STATISTICS
is in the OFF condition, this is at the end of the day. Otherwise, in the
ON condition, it is the earlier time of either the next interval to occur
or the end of the day.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET STATISTICS (the minimum abbreviation is CEMT S ST). You get a display that lists the current status, similar
to that obtained by CEMT INQUIRE STATISTICS. You can then tab to the highlighted
or blank fields and overtype them with the required values.
- Type CEMT SET STATISTICS (CEMT S ST) followed by
one or more attribute settings that you wish to change. For example, cemt s st on res will switch CICS statistics ON and will reset the statistics
counters.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET STATISTICS
>>-CEMT Set STatistics--+-----+--+----------+--+-----------+---->
+-ON--+ '-RESetnow-' '-RECordnow-'
'-OFf-'
>--+------------------+--+------------------+------------------><
'-Interval(hhmmss)-' '-Endofday(hhmmss)-'
Options
- Endofday (hhmmss)
- specifies the end-of-day time for recording statistics. At end-of-day,
the current values of the CICS statistics counters are written out to an SMF
data set and the statistics counters are reset.
End-of-day times must be
in the range 000000-235959. The default end-of-day time is 12 midnight
(000000).
- Interval (hhmmss)
- specifies the length of time during which the statistics counters are
incremented. At the end of each interval, the accumulated statistics are recorded
and the statistics counters are reset.
Interval times must be in the range
000100-240000. The default interval value is 030000. These interval settings
only take place if you set the statistics recording status to ON. You can
set the statistics recording status ON or OFF using the RECORDING option on
this command or by using the STATRCD system initialization parameter.
The arrival of the ENDOFDAY time always causes the current interval to be
ended (possibly prematurely) and a new interval to be started. Only end-of-day
statistics are recorded at the end-of-day time, even if it coincides exactly
with the expiry of an interval.
Changing the ENDOFDAY value has an immediate
effect on the times at which INTERVAL statistics are recorded. New interval
expiry times are recalibrated in accordance with the new end-of-day time.
When you change the INTERVAL value or the ENDOFDAY value (and also
when CICS is initialized), the length of the current (or first) interval is
adjusted so that it expires after an integral number of intervals from the
end-of-day time.
These rules are illustrated by the following example,
where I indicates an interval recording, INTERVAL is
set at 3-hourly intervals, CICS is initialized at 0815 hours, and E indicates the ENDOFDAY setting at 1700 hours.
Note:
In this example, there would have been an interval at
0800 hours if CICS had been initialized earlier.
If you
want your end-of-day recordings to cover 24 hours, set INTERVAL to 240000.
- OFf
- The recording of interval statistics is switched OFF. (End-of-day, requested,
and unsolicited statistics are always recorded.) Counters are still incremented
as usual and the recording of end-of-day, requested, and unsolicited statistics
is still made. Statistics can be recorded at any time by issuing a CEMT PERFORM
STATISTICS command.
- ON
- The recording of interval statistics is switched ON. Counters are incremented
as usual, and are reset at the expiry of each interval and at end-of-day.
Statistics can be recorded at any time by issuing a CEMT PERFORM STATISTICS
command.
- RECordnow
- The existing statistics are to be written to an SMF data set. The statistics
that you are given are those collected since the last ENDOFDAY or INTERVAL
collection, or since the last time the RESETNOW function was used in this
or the PERFORM STATISTICS command. RECORDNOW RESETNOW only takes effect when
the recording status is changed.
Note:
RECORDNOW RESETNOW both resets
the statistics counter and also writes the existing statistics to an SMF data
set. The statistics that you are given are those collected since the last
ENDOFDAY or INTERVAL collection, or since the last time the RESETNOW function
was used in this or the PERFORM STATISTICS command. RECORDNOW RESETNOW only
takes effect when the recording status is changed.
- RESetnow
- The statistics counters are to be reset. The reset takes effect only
if the recording option is changed from OFF to ON or from ON to OFF. For information
about the effect of reset on each individual counter, see the CICS statistics
tables in the CICS Performance Guide.
The action, for each
counter, is one of the following:
- Not reset
- Reset to zero
- Reset to 1
- Reset to current value (this applies to peak values)
- An exception to the above.
Function
Change the attributes of the system dump codes.
Description
SET SYDUMPCODE allows you to define the entries that you require in the
system dump table. You control system dumps by creating an entry in the system
dump table for each dump code that requires a change from the default action.
A system dump code is the CICS message number with the DFH prefix removed.
Typically this leaves a 6-character code comprising 2 alphabetic characters
and 4 numeric characters, for example AP0001. The command syntax permits up
to 8 characters for the dump code, and the dump codes you specify are padded
with trailing spaces.
Each message has its own system default actions that you cannot necessarily
override with the SET command. For example, when a serious error occurs, CICS
shuts down even if you have asked for no shut down. See the CICS Messages and Codes manual for information about the system action for each
message.
There are other system parameters that take priority over your dump table
entries. For example, EXEC CICS SET SYSTEM NOSYSDUMP, or a DUMP=NO system
initialization parameter, inhibits system dumping. For more information on
using dumps, see the CICS Problem Determination Guide.
The transaction dump command SET TRDUMPCODE can also cause CICS to produce
system dumps for the specified transaction dump code.
The SET command allows you to:
- Add a new entry to the system dump table
- Remove an entry from the system dump table
- Indicate whether or not you want a system dump taken
- Indicate whether the system dump request is to be local or related
- Indicate whether or not you want CICS to shut down following the dump
- Set the maximum number of dumps
- Reset the counter of the current number of dumps to zero
- Determine whether or not a dump produced by CICS is eligible for any suppression
by the MVS Dump Analysis and Elimination (DAE) component.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET SYDUMPCODE (the minimum abbreviation is CEMT S SYD) with code or ALL. You get a display that lists the current
status, similar to that obtained by CEMT INQUIRE SYDUMPCODE. You can then
tab to the highlighted or blank fields and overtype them with the required
values.
- Type CEMT SET SYDUMPCODE (CEMT S SYD) with code
or ALL, followed by one or more attribute settings that you wish to change.
For example, to add a system dump code:
CEMT SET SYDUMPCODE(value) ADD
To remove a system dump code:
CEMT SET SYDUMPCODE(value) REMOVE
To change the maximum count to 10:
CEMT SET SYDUMPCODE(value) MAX(10)
Shut down CICS on occurrence of this system
dump code:
CEMT SET SYDUMPCODE(value) SHUTDOWN
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET SYDUMPCODE
>>-CEMT Set SYDumpcode--+-(value)-+--+-----------+-------------->
'-+-----+-' +-SYsdump---+
'-ALl-' '-NOSYsdump-'
>--+------------+--+---------+--+----------------+-------------->
+-SHutdown---+ +-RELated-+ '-Maximum(value)-'
'-NOSHutdown-' '-Local---'
>--+--------+--+-------+---------------------------------------><
+-RESet--+ +-Dae---+
+-REMove-+ '-NODae-'
'-ADd----'
Options
- (value)
- specifies an 8-character system dump code. See the CICS Messages and Codes manual for details of the codes.
- ADd
- This system dump code is added to the system dump code table.
- ALl
- specifies that any changes you request are made to all resources of
the specified type that you are authorized to access.
- Dae
- A system dump is eligible for suppression by the DAE component.
- Local
- A system dump request is not to be sent to other MVS images in the sysplex
for this system dump code.
- Maximum (value)
- specifies the maximum number of dump calls for this system dump code
that result in system dumps being taken. The value must be in the range 0-999;
a value of 999 means the default, ‘no limit’.
- NODae
- A system dump will not be suppressed by the DAE component. (However,
be aware of the SUPPRESS and SUPPRESSALL options in the ADYSETxx parmlib member.
These are controlled by the VRADAE and VRANODAE keys in the SDWA. They may
lead to dump suppression even though NODAE is set here. For information about
DAE, SUPPRESS, and SUPPRESSALL, see the OS/390 MVS Diagnosis: Tools and Service Aids manula.
- NOSHutdown
- CICS is not to be shut down after the occurrence of an error corresponding
to this dump code.
- NOSYsdump
- A system dump is not to be taken for this system dump code.
- RELated
- A system dump request is to be sent to MVS images in the sysplex which
are running XCF/MRO connected CICS regions related to the CICS region on which
the dump is initiated.
Note:
A related CICS region is one in which
the unit of work identifiers, in the form of APPC tokens, of one or more tasks
match those in the CICS region that issued the dump request.
- REMove
- This system dump code is removed from the system dump code table.
- RESet
- The current number of calls for this dump code is reset to zero.
- SHutdown
- CICS is to be shut down.
- SYsdump
- A system dump is to be taken for this system dump code.
Function
Change the system attributes.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET. The SYSTEM keyword does not have to be typed.
If you type just CEMT SET, SYSTEM is assumed as the default. You
get a display that lists the current status, similar to that obtained by CEMT
INQUIRE SYSTEM. You can then tab to the highlighted or blank fields and overtype
them with the required values.
- Type CEMT SET followed by one or more attribute settings that
you wish to change. For example, cemt s ag(value) ma(value) resets the values for priority aging and the maximum number of
tasks allowed at any one time in the CICS system.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET SYSTEM
.-------------------------.
V |
>>-CEMT Set SYStem----+---------------------+-+----------------><
+-AGing(value)--------+
+-AKp(value)----------+
+-+-DEbug---+---------+
| '-NODebug-' |
+-DSAlimit(value)-----+
+-DSRtprogram(value)--+
+-DTrprogram(value)---+
+-EDsalimit(value)----+
+-Forceqr-+-Force---+-+
| '-NOForce-' |
+-Logdefer(value)-----+
+-MAxtasks(value)-----+
+-MRobatch(value)-----+
+-+-CTLGAll----+------+
| +-CTLGModify-+ |
| '-CTLGNone---' |
+-Progautoexit(value)-+
+-+-AUTOActive---+----+
| '-AUTOInactive-' |
+-RUnaway(value)------+
+-SCandelay(value)----+
+-Time(value)---------+
'-+-SYsdump---+-------'
'-NOSysdump-'
Options
- AGing (value)
- specifies the time factor for CICS to use in the priority aging algorithm
for incrementing the priority of a task. The value is expressed as "milliseconds
per unit of priority", and must be in the range 00000-65535. The
priority aging factor is defined initially by the PRTYAGE system initialization
parameter, in which the value represents the number of milliseconds that must
elapse before the priority of a waiting task can be adjusted upward by 1.
See the CICS System Definition Guide for information about the PRTYAGE
parameter.
- AKp (value)
- specifies the activity keypoint trigger value, which is the number of
write requests to the CICS system log stream output buffer between the taking
of keypoints. It must have a value in the range 00200-65535. You cannot
change this value if AKPFREQ=0 was specified at system initialization.
- AUTOActive
- Autoinstall for programs is active. On first use, if a program, mapset,
or partitionset is not defined, the definition is created dynamically.
- AUTOInactive
- Autoinstall is not active. If a program is not defined, a PGMIDERR or
transaction abend occurs when it is referenced.
- CTLGAll
- All autoinstalled program definitions are to be cataloged and restored
on a warm or emergency restart.
- CTLGModify
- Autoinstalled program definitions are to be cataloged only if they are
modified (for example, by a CEMT SET PROGRAM command), so that the modified
definitions are restored on a warm or emergency restart.
- CTLGNone
- No autoinstalled program definitions are to be cataloged. They are autoinstalled
again after a warm or emergency restart.
- DEbug
- Specifies that you want to use CICS debugging profiles to select the
programs that will run under the control of a debugging tool. The following
debugging tools use debugging profiles:
- Debug Tool, for compiled language application programs (programs written
in COBOL, PL/I, C, C++ and Assembler)
- Remote debugging tools (for compiled language application programs and
Java programs)
Other debugging mechanisms, such as the CICS Execution Diagnostic Facility
(CEDF) do not use debugging profiles.
For more information about debugging
profiles, see the CICS Application Programming Guide.
- DSAlimit (value)
- specifies the maximum amount of storage, as a total number of bytes,
within which CICS can dynamically allocate storage for the four individual
DSAs that reside below the 16MB boundary. See the CICS System Definition Guide for
a description of the DSALIM system initialization parameter.) If DSALIMIT
specifies a value lower than the current limit, CICS may not be able to implement
the new limit immediately, but will attempt to do so over time as dynamic
storage is freed in the individual DSAs.
Note:
Dynamic changes to the DSA limit are cataloged in the
local catalog, and override values specified in the system initialization
table during all forms of restart-initial, old, and warm.
The cataloged value is
not used if:
- You specify startup values as system initialization parameters overrides
(for example, in SYSIN).
- You re-initialize the CICS catalog data sets.
- DSRtprogram (value)
- specifies the name of the distributed routing program.
- DTrprogram (value)
- specifies the name of the dynamic routing program.
- EDsalimit (value)
- specifies the maximum amount of storage, as a total number of bytes,
within which CICS can dynamically allocate storage for the four individual
DSAs that reside above the 16MB boundary. See the CICS System Definition Guide for
a description of the EDSALIM system initialization parameter.) If EDSALIMIT
specifies a value lower than the current limit, CICS may not be able to implement
the new limit immediately, but will attempt to do so over time as dynamic
storage is freed in the individual DSAs.
Note:
Dynamic changes to the EDSA limit are cataloged in the
local catalog, and override values specified in the system initialization
table during all forms of restart-initial, old, and warm.
The cataloged value is
not used if:
- You specify startup values as system initialization parameters overrides
(for example, in SYSIN).
- You re-initialize the CICS catalog data sets.
- Force
- Force all
CICSAPI
user application programs
to run under the QR TCB, even if they are defined with the CONCURRENY(THREADSAFE)
attribute.
Force does not apply to OPENAPI programs or
C/C++ programs compiled with XPLINK.
- Logdefer (value)
- specifies the log deferral interval in milliseconds, which is the period
of time used by CICS Log Manager when determining how long to delay a forced
journal write request before invoking the MVS system logger. It is in the
range 0-65535. See the CICS System Definition Guide for information
about the Logdefer parameter and associated SIT parameter LGDFINT.
- MAxtasks (value)
- specifies the maximum number of tasks, both active and suspended, allowed
at any one time in the CICS system. It must have a value in the range 1-999.
Note:
The value assigned to MAXTASKS might be less than the requested
value, because of CICS storage constraints. If this occurs, the message CEILING
REACHED is displayed when the request is made.
- MRobatch (value)
- specifies the number of MRO requests from connected regions that are
to be batched before this region is posted. It must have a value in the range
001-255.
- NODebug
- Specifies that you do not want to use CICS debugging profiles to select
the programs that will run under the control of a debugging tool. The following
debugging tools use debugging profiles:
- Debug Tool, for compiled language application programs (programs written
in COBOL, PL/I, C, C++ and Assembler)
- Remote debugging tools (for compiled language application programs and
Java programs)
Other debugging mechanisms, such as the CICS Execution Diagnostic Facility
(CEDF) do not use debugging profiles.
For more information about using
debugging profiles, see the CICS Application Programming Guide.
- NOForce
- Do not force user application programs to run under the QR TCB. CICS
is to honor the CONCURRENCY(THREADSAFE) attribute on user application programs,
and allow user programs to run on an open TCB to avoid unnecessary TCB switching.
- NOSysdump
- specifies that system dumps are to be suppressed.
- Progautoexit (value)
- specifies the name of the user-provided program that is called by the
program autoinstall code to select or modify a model definition.
- RUnaway (value)
- specifies the interval, in milliseconds, for which a task can have control
before it is assumed to be looping.
You can specify 0, or a value in the
range 500-2700000. The value chosen is rounded down to a multiple of
500. CICS purges a task if it has not given up control after this interval
(that is, if the task appears to be looping). If you specify zero, runaway
task control is inoperative (that is, tasks do not get purged if they appear
to be looping). The value is independent of, and can be less than, the value
in the TIME operand.
CICS runaway-task detection is based upon task
time, that is, the interval is decremented only when the task has control
of the processor. You do not, therefore, need to allow for the effect of other
jobs when setting the value.
- SCandelay (value)
- specifies the maximum number of milliseconds between the receipt of
a VTAM request, and the time when CICS begins to process the request. The
number must be in the range 0-5000, and must be less than or equal to
the TIME value.
In the summary report of the dispatcher statistics, SCANDELAY
is referred to as ICVTSD.
- SYsdump
- specifies that system dumps are not to be suppressed.
- Time (value)
- specifies the interval, in milliseconds, for which CICS releases control
to the operating system if no transactions are ready to resume processing.
This interval is known as the ‘region exit interval’.
It can have
a value in the range 100-3600000, and must be greater than or equal
to the SCANDELAY value.
In the summary report of the dispatcher statistics,
TIME is referred to as ICV.
Function
Change the status of tasks.
Description
You cannot specify a list of identifiers, nor can you use the symbols *
and + to specify a family of tasks.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET TASK (the minimum abbreviation is CEMT S
TA) with (value) or ALL. You get a display that lists the current
status, similar to that obtained by CEMT INQUIRE TASK. You can then tab to
the highlighted or blank fields and overtype them with the required values.
- Type CEMT SET TASK (CEMT S TA) with number or ALL,
followed by one or more attribute settings that you wish to change. For example, cemt s ta(value) pu will make the specified task purgeable
in system-stall conditions.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET TASK
>>-CEMT Set TAsk--+-(value)-+--+-----------------+-------------->
'-All-----' '-PRiority(value)-'
>--+------------+----------------------------------------------><
+-PUrge------+
+-FOrcepurge-+
'-Kill-------'
Options
- (value)
- The CICS-generated task number. This is in the range 1-99999.
- All
- Any changes you request are made to all resources of the specified type
that you are authorized to access.
- FOrcepurge
- The task is to be terminated as soon as it is consistent with system
integrity and without regard to data integrity. CICS cannot always determine
whether a forced purge is safe; it is possible to abend the system when you
specify this option. For example, if a task is forcepurged during backout
processing, CICS terminates abnormally. If you want to terminate a task but
do not want to terminate CICS, you should use PURGE instead of FORCEPURGE.
- Kill
- The task is to be terminated. System and data integrity is not guaranteed.
The KILL option extends the PURGE and FORCEPURGE options. It should be used
only after an attempt has been made to PURGE or FORCEPURGE a task. The KILL
option does not guarantee integrity of any kind but in some situations it
allows the user to free up a stalled region enabling the region to continue
processing. In some cases, for example, if a task is killed during backout
processing, CICS terminates abnormally.
- PRiority (value)
- specifies the priority of the task, in the range 0-255 where 255
is the highest priority.
- PUrge
- The task is terminated as soon as both system and data integrity can
be maintained.
If the task is in any way associated with an open TCB (for
example, it involves a Java program running in a JVM on a J8 or J9 mode TCB),
you could experience a delay of about a minute before the task is finally
purged.
Function
Reset the maximum number of tasks and the purge threshold for a transaction
class.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET TCLASS (the minimum abbreviation is CEMT
S TC) with (value) or ALL. You get a display that lists the
current status, similar to that obtained by CEMT INQUIRE TCLASS. You can then
tab to the highlighted or blank fields and overtype them with the required
values.
- Type CEMT SET TCLASS (CEMT S TC) followed by one
or more attribute settings that you wish to change. For example, cemt
s tc(value) p(3) will reset the purge threshold value to 3.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET TCLASS
>>-CEMT Set TClass--+-(value)-+--+------------------+----------->
'-ALl-----' '-Maxactive(value)-'
>--+--------------------+--------------------------------------><
'-Purgethresh(value)-'
Options
- (value)
- specifies the 8-character transaction class name. If no transaction
class name is assigned, it defaults to DFHTCL00.
- ALl
- specifies that any changes you request are made to all resources of
the specified type that you are authorized to access.
- Maxactive (value)
- specifies the largest number of transactions in the transaction class
which are allowed to run concurrently. The value can be in the range 0-999.
- Purgethresh (value)
- specifies the limit at which the queuing transactions are purged for
the transaction class. It can have a value in the range 0-1000000. Zero
means that the transactions are not purged. A nonzero number "n" means
that the first (n-1) transactions to arrive are queued and the nth is purged.
Function
Open or Close CICS TCP/IP Service.
Description
SET TCPIP allows you to open or close CICS internal sockets support.
Note:
This command has no effect on the sockets support provided
by the TCP/IP for OS/390 CICS Sockets Feature.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET TCPIP (the minimum abbreviation is CEMT
S TCPIP). You get a display that lists the current status, similar to
that obtained by CEMT INQUIRE TCPIP. You can then tab to the highlighted or
blank fields and overtype them with the required values.
- Type CEMT SET TCPIP (CEMT S TCPIP) with (value) or ALL, followed by one or more attribute settings that you wish to
change. For example, cemt s tcpip status open opens CICS
internal sockets support.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET TCPIP
>>-CEMT Set TCPIP--+-(value)-+--+-OPEN-----+-------------------->
'-ALl-----' +-CLOSE----+
'-IMMCLOSE-'
>--MAXSockets(data-value)--------------------------------------><
Options
- Openstatus
- specifies whether or not TCPIP is to be opened (that is, able to process
new incoming work, and complete ongoing work), and if TCP/IP support is to
be closed, how the close should be done. CVDA values are:
- OPEN
- CICS internal sockets support is to be opened.
Note:
If you
are using CEMT SET TCPIP OPEN to initialize CICS sockets, you must also set
TCPIP=YES at CICS initialization by SIT or a SIT override. Otherwise, 'NOT
IN SYSTEM' is returned.
- CLOSE
- CICS internal sockets is to be closed. If it is currently open, CICS
is to quiesce all internal sockets activity and then close any sockets on
which CICS is listening for incoming work. Tasks using CICS internal sockets
are allowed to complete.
- IMMCLOSE
- CICS internal sockets is to be closed. If it is currently enabled, CICS
is to terminate abnormally any tasks using it and then close the socket on
which CICS is listening for incoming work.
- MAXSockets(data-value)
- specifies the maximum number of IP sockets that can be managed by the
CICS sockets domain.
If the userid under which the CICS job is running has
superuser authority, up to 65535 sockets can be managed by the sockets domain.
If the userid under which the CICS job is running does not have superuser
authority, the maximum number of sockets that can be managed by the sockets
domain is limited to the number specified in the MAXFILEPROC parameter in
SYS1.PARMLIB member BPXPRMxx. If you use the SET SYSTEM command to specify
a value greater than that in MAXFILEPROC, CICS resets the limit to MAXFILEPROC.
The message "MAXFILEPROC LIMIT REACHED" is displayed when the request is made.
Note that sockets created by Java programs running on threads that
are not managed by CICS do not count towards the limit.
If you reduce
the limit to less than the number of sockets currently active, CICS prevents
new sockets from being created until the number of active sockets falls below
the limit.
Function
Modify the status of a service using CICS internal TCP/IP support
Description
SET TCPIPSERVICE allows you to update the information relating to a service
which uses CICS internal TCP/IP support.
Note:
This command has no effect on the sockets support provided
by the TCP/IP for OS/390 CICS Sockets Feature.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET TCPIPSERVICE (the minimum abbreviation is CEMT S TCPIPS). You get a display that lists the current status, similar
to that obtained by CEMT INQUIRE TCPIPSERVICE. You can then tab to the highlighted
or blank fields and overtype them with the required values.
- Type CEMT SET TCPIPS (CEMT S TCPIPS) with (value) or ALL, followed by one or more attribute settings that you wish
to change. For example, cemt s tcpips status open opens
CICS internal sockets support.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET TCPIPSERVICE
>>-CEMT Set TCPIPSERVICE--+-(value)-+--+----------------+------->
'-ALl-----' '-Backlog(value)-'
>--+--------------+--+-------------------+--+----------+-------->
'-DEREGIstered-' '-Maxdatalen(value)-' +-OPEN-----+
+-CLOSE----+
'-IMMCLOSE-'
>--+------------+----------------------------------------------><
'-URM(value)-'
Options
- BACKLOG
- changes the maximum number of requests which can be queued in TCP/IP
waiting to be processed by the service. The service must be CLOSED before
you can change this value. If you set BACKLOG to zero, CICS does not receive
any connections.
- DNSSTATUS
- Changes the current state of Workload Manager (WLM)/Domain Name System
(DNS) registration of this TCPIPSERVICE. This can be done independently of
changing the open or closed status of the service.
To account for timing
delays in the deregister request reaching the WLM and the DNS updating its
tables, it is advisable to deregister a service before setting it closed.
This ensures that client applications do not encounter "Connection Refused"
situations during the time between the deregister call being issued and the
DNS server actually updating its tables. The valid CVDA values are:
- DEREGISTERED
- causes CICS to deregister the group name specified by the DNSGROUP attribute
of this TCPIPSERVICE. The OS/390 WLM macro IWMSRDRS is called and CICS will
no longer be a part of the DNS connection optimization. Any other TCPIPSERVICES
that are in the same group (that is, share the same DNSGROUP attribute) are
also deregistered.
MAXDATALEN 
changes the maximum length of data that may be received by CICS as an
HTTP server. This can be 3K through 524288K. The default is 32K.
- OPENSTATUS
- Changes the status of the service. CVDA values are:
- OPEN
- CICS internal TCP/IP sockets support is to start listening for incoming
requests on the specified port.
- CLOSE
- CICS internal TCP/IP sockets support is to stop listening for incoming
work on the specified port. All active tasks using this service are allowed
to complete.
- IMMCLOSE
- CICS internal sockets support is to stop listening for incoming work
on the specified port immediately. Any active tasks using this service are
terminated abnormally.
- URM
- specifies the 8-character name of the program to be used as the Service
User-replaceable module by the attached task. You can specify either an installation
specific program or the CICS-supplied default for the service.
Note:
This program and any programs it invokes must be installed before they can
be used in the program autoinstall process. You can do this either with explicit
PROGRAM definitions or by autoinstall when some other autoinstall program
is in force. Otherwise the program autoinstall process fails when it is next
used, and CICS makes it inactive.
Function
Change the attributes of transient data queues.
Description
The SET TDQUEUE command changes some of the attributes of a transient data
queue. The queue must not be REMOTE or INDIRECT.
You cannot alter the following attributes unless the queue is fully disabled:
- ATIFACILITY
- ATITERMID
- ATITRANID.
To disable a transient data destination, the queue must not currently be
in use. If it is in use, the queue enters a "disable pending" state.
The last unit of work (UOW) to use the queue fully disables it. The TRIGGERLEVEL,
OPENSTATUS, and ENABLESTATUS attributes may be altered regardless of whether
the queue is enabled or disabled. The value of the ENABLESTATUS attribute
cannot be altered while a queue is in a "disable pending" state.
A transient data queue cannot be disabled:
- While it is in use
- While tasks are waiting to use it.
Indirect and remote queues can be disabled at any time because they have
no concept of being "in use".
If tasks are waiting to use an extrapartition queue, a physically recoverable
queue, or a nonrecoverable intrapartition queue and an attempt is made to
disable the queue, the queue enters a "disable pending" state. The
last task to use the extrapartition queue fully disables it.
If an attempt is made to disable a logically recoverable intrapartition
TD queue when there are UOWs enqueued upon it, the queue enters a "disable
pending" state. The last UOW to obtain the enqueue fully disables the
queue. If a UOW has updated a logically recoverable queue and suffers an indoubt
failure, the queue cannot be disabled until the indoubt failure has been resolved.
If a UOW owns an enqueue on a queue that is in a "disable pending"
state, it is allowed to continue making updates.
When a queue is in a "disable pending" state, no new tasks can
alter the queue’s state or its contents. A disabled response is returned
when a READQ, WRITEQ, or DELETEQ request is issued against a destination that
is in a "disable pending" state.
Note:
If a task updates a logically recoverable transient data queue,
and attempts to disable the queue and alter an attribute of the queue (for
example, ATITRANID) within the same UOW, the call fails. This is because the
UOW is a user of the queue, and the queue enters a "disable pending"
state. The SET operation on the queue attribute, in this case ATITRANID, fails.
The queue does not become fully disabled until the UOW commits or backs out
at syncpoint. You are recommended to issue an EXEC CICS SYNCPOINT command
before attempting to update the queue attribute (ATITRANID) using SET TDQUEUE.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET TDQUEUE (the minimum abbreviation is CEMT
S TD) with destid or ALL. You get a display that lists the current status,
similar to that obtained by CEMT INQUIRE TDQUEUE. You can then tab to the
highlighted or blank fields and overtype them with the required values.
- Type CEMT SET TDQUEUE (CEMT S TD) with (value) or ALL, followed by one or more attribute settings that you wish to
change. For example, cemt s td(value) en op will make
a named extrapartition queue accessible by applications and open.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET TDQUEUE
>>-CEMT Set TDqueue--+-(value)-+--+---------------------+------->
'-All-----' '-TRIggerlevel(value)-'
>--+----------+--+--------+------------------------------------><
+-ENabled--+ +-OPen---+
'-DIsabled-' '-Closed-'
Options
- (value)
- specifies the identifier (1-4 characters) of a transient data queue.
- All
- specifies that any changes you request are made to all resources of
the specified type that you are authorized to access.
- Closed
- The queue is closed.
- DIsabled
- The queue cannot be accessed by applications, although it can still
be open. A queue that has suffered an indoubt failure cannot be disabled.
- ENabled
- The queue can be accessed by applications.
- OPen
- The extrapartition queue is open.
- TRIggerlevel (value)
- specifies the number (0-32767) of requests for output to a queue
that there must be before automatic transaction initiation (ATI) occurs. Specifying
zero disables ATI.
Function
Change the attributes of named terminals.
Description
The SET TERMINAL command changes some of the values of a named terminal
defined in the terminal control table (TCT). It cannot be used for APPC sessions.
In an SNA environment, a terminal is the CICS representation of an SNA
logical unit with which CICS can be in communication. (SNA environment means
that CICS is using VTAM as the access method for communication with SNA logical
units.)
This logical unit can be:
- A physical terminal (such as a 3277)
- A function of a cluster controller (such as a 3790 Type 2 batch function)
- An intersystem communication (ISC) or interregion communication (IRC)
session that has been generated by the CEDA transaction.
If you are familiar with network names, you may prefer to use the command
that uses these names. See CEMT SET NETNAME.
The message "TEMP OUT SERVICE" can be displayed if recovery is
in progress for the terminal. The "TEMP OUT SERVICE" indicator is
reset by simply refreshing the screen, or by overtyping the "INS"
field with "INS" or "OUT". If "TEMP OUT SERVICE" continues
to be displayed, the cause of the indicator should be investigated.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET TERMINAL (the minimum abbreviation is CEMT
S TE) with (value), CLASS(value), or ALL. You get
a display that lists the current status, similar to that obtained by CEMT
INQUIRE TERMINAL. You can then tab to the highlighted or blank fields and
overtype them with the required values.
- Type CEMT SET TERMINAL (CEMT S TE) with (value), CLASS(value), or ALL, followed by one or more attribute settings
that you wish to change. For example, cemt s te(value) i cr specifies that a named terminal is available for use (inservice) and
that it can be acquired automatically by ATI transactions (create).
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET TERMINAL
>>-CEMT Set TErminal--+-(value)------+--+-----------------+----->
+-CLass(value)-+ '-PRiority(value)-'
'-ALl----------'
>--+--------------+--+------------+--+-------+--+-------+------->
+-PAgeable-----+ +-Inservice--+ +-ATi---+ +-TTi---+
'-AUtopageable-' '-Outservice-' '-NOAti-' '-NOTti-'
>--+------------+--+----------+--+----------+------------------><
+-PUrge------+ +-ACquired-+ +-CReate---+
+-Forcepurge-+ +-COldacq--+ '-NOCreate-'
+-Kill-------+ '-RELeased-'
'-CAncel-----'
Options
- (value)
- A terminal identifier (1-4 characters) as specified in an installed
terminal definition.
If the terminal name is, for example, S201, this option
is coded thus:
CEMT SET TERMINAL(S201)
- ACquired (vtam only)
- CICS is in session with the logical unit represented by the terminal.
- ALl
- Any changes you request are made to all resources of the specified type
that you are authorized to access.
- ATi (vtam only)
- The terminal is available for use by transactions that are initiated
automatically from within CICS or, if the terminal is an ISC session, by transactions
that are using this session as an alternative facility to communicate with
another system.
- AUtopageable (vtam only)
- Pages after the first in a series are to be written to the terminal
automatically.
- CAncel
- AIDs queuing for the specified terminal are canceled. AIDs representing
scheduled and allocated requests waiting in the local CICS system for the
specified terminal are canceled. However, TD AIDs with an associated triggered
task already started are not canceled.
When a canceled scheduled request
is found to have a precursor in a remote CICS system, this remote AID is canceled
asynchronously. Message DFHTF0100 is written to CSMT to indicate how many
AIDs have been deleted for the terminal and how many remain.
An ‘AIDS
CANCELED’ message appears on the CEMT panel whenever AIDs are deleted
using the CANCEL option of the CEMT SET TERMINAL command.
- CLass (value)
- The 1-or 2-character suffix of a terminal list table (TLT).
- COldacq (vtam only)
- This is a special form of ACQUIRED, where no resynchronization is required.
If the previous session abended, the use of COLDACQ overrides CICS integrity
control. This could lead to integrity problems. Also, you should check the
CSMT log for an activity keypoint after the restart of a session following
a CICS failure. If there is no activity keypoint, you should issue COLDACQ
again after the next emergency restart.
- CReate (vtam only)
- If the terminal is not in session, CICS is to acquire it if it is needed
to satisfy an ATI request.
- Forcepurge
- Any transaction running with this terminal is immediately terminated
abnormally. Data integrity is not guaranteed. In some extreme cases (for example,
if an error occurs during backout processing), CICS might terminate abnormally.
- Inservice
- The terminal is available for use. For VTAM, INSERVICE means that the
terminal can be ACQUIRED.
- Kill
- The task is to be terminated. System and data integrity is not guaranteed.
The KILL option extends the PURGE and FORCEPURGE options. It should be used
only after an attempt has been made to PURGE or FORCEPURGE a task. The KILL
option does not guarantee integrity of any kind but in some situations it
allows the user to free up a stalled region enabling the region to continue
processing. In some cases, for example, if a task is killed during backout
processing, CICS terminates abnormally.
- NOAti (vtam only)
- The terminal is not available for use by transactions that are initiated
automatically from within CICS or, if the terminal is an ISC session, by transactions
that are using this session as an alternative facility to communicate with
another system.
Note:
A terminal cannot be defined with both NOATI
and NOTTI.
- NOCreate (vtam only)
- If the terminal is not in session, CICS is not to acquire it to satisfy
an ATI request. A session must be started by, for example, a logon request
or a CEMT SET TERMINAL ACQUIRED command before the ATI request can be satisfied.
If NOCREATE is set for an LU6.1 ISC session and there are no allocatable sessions
left, the connection is placed OUTSERVICE.
- NOTti (vtam only)
- This terminal cannot be used by transactions that are initiated from
this terminal.
Note:
A terminal cannot be defined with both NOATI
and NOTTI.
- Outservice
- The terminal is not available for use. Setting a terminal OUTSERVICE
means that the terminal can no longer be used by transactions. If PURGE or
FORCEPURGE is also specified, any transaction using the terminal is terminated
abnormally. If PURGE or FORCEPURGE is not specified, the transaction is allowed
to terminate normally, but no further transactions are allowed to use the
terminal. For VTAM, setting a terminal OUTSERVICE also causes it to be released
and the operator to be signed off, either immediately or when the current
transaction has terminated.
In an LU6.1 ISC session the connection is set
OUTSERVICE if there are no allocatable sessions left.
To set an IRC
session OUTSERVICE, you must set the connection to the MRO partner OUTSERVICE.
- PAgeable (vtam only)
- Pages after the first in a series are to be written to the terminal
only if you request them to be.
- PRiority (value) (vtam only)
- specifies the priority of a terminal relative to other terminals. The
priority of a task is the sum of the transaction priority, the terminal priority,
and the operator priority. Priority has no meaning for terminals that are
ISC sessions being used as alternative facilities. The value must be in the
range 0-255, where 255 is the highest priority.
- PUrge
- Any transaction running with this terminal is purged only if system
and data integrity can be maintained.
- RELeased (vtam only)
- CICS is not in session with the logical unit represented by the terminal.
Setting a terminal RELEASED causes the session to be terminated. Running transactions
are allowed to finish unless PURGE or FORCEPURGE is also specified.
- TTi (vtam only)
- This terminal can be used by transactions.
Function
Change some of the attributes of a selected transaction.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET TRANSACTION (the minimum abbreviation is CEMT S TRANS) with (value), CLASS(value), or ALL.
You get a display that lists the current status, similar to that obtained
by CEMT INQUIRE TRANSACTION. You can then tab to the highlighted or blank
fields and overtype them with the required values.
- Type CEMT SET TRANSACTION (CEMT S TRANS) followed
by one or more attribute settings that you wish to change. For example, cemt s trans(value) e pu specifies that a named transaction
is available for use (enabled) and is system-purgeable.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET TRANSACTION
>>-CEMT Set TRAnsaction--+-(value)------+----------------------->
+-CLass(value)-+
'-ALl----------'
>--+-----------------+--+---------------+--+----------+--------->
'-PRIority(value)-' '-TClass(value)-' +-Enabled--+
'-Disabled-'
>--+--------------+--------------------------------------------><
+-PUrgeable----+
'-NOTpurgeable-'
Options
- (value)
- specifies a transaction identifier (1-4 characters).
Only transactions that have been defined in the CICS system definition (CSD)
file and installed on the running CICS system are accessible through CEMT.
- ALl
- specifies that any changes you request are made to all resources of
the specified type that you are authorized to access.
- CLass (value)
- specifies the 2-character suffix of a transaction list table (XLT).
- Disabled
- The transaction is not available for use. Transactions that have identifiers
beginning with "C" cannot be disabled because these are reserved for
use by CICS.
When the CEMT SET TRANSACTION DISABLED command is used, existing
transactions run to completion before being DISABLED.
Note:
If a transaction is disabled, this does not prevent a START command which
names this transaction from being shipped to a remote region. When a task
is attached for the requested transaction, CICS checks that the transaction
is enabled in the remote region.
- Enabled
- The transaction is available for use.
- NOTpurgeable
- The transaction cannot be purged.
- PRIority (value)
- specifies the priority of a transaction relative to other transactions.
When a transaction is running as a CICS task, the priority of a task is the
sum of the transaction priority, the terminal priority, and the operator priority.
The "value" must be in the range 0-255, where 255 is the highest
priority.
- PUrgeable
- The transaction is system-purgeable. This operand relates to the SPURGE
parameter on the transaction resource definition and indicates that CICS can
purge the transaction in a deadlock time-out situation. See the CICS Resource Definition Guide
for information about the SPURGE and DTIMEOUT parameters on a transaction
resource definition.
- TClass (value)
- specifies the 8-character transaction class name to which the transaction
belongs. If the transaction does not belong to a class, DFHTCL00 is returned.
The abbreviation for TCLASS is Tcl. To remove a transaction
from its TCLASS, the Tcl field should be set to DFHTCL00.
A series of blanks can be inserted, in which case, DFHTCL00 is returned. An
added or changed TClass must be defined.
Function
Change the status of a transaction dump.
Description
Using the SET function, you can change entries in the transaction dump
table to request a transaction dump. You can also set the maximum number of
dumps that can be taken. See the CICS Problem Determination Guide for
information on using dumps.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET TRDUMPCODE (the minimum abbreviation is CEMT S TRD) with (value) or ALL. You get a display that lists
the current status, similar to that obtained by CEMT INQUIRE TRDUMPCODE. You
can then tab to the highlighted or blank fields and overtype them with the
required values.
- Type CEMT SET TRDUMPCODE (CEMT S TRD) followed by
one or more attribute settings that you wish to change. For example, cemt s trd(value) t sh specifies that a transaction dump is
to be taken for the named transaction dump code and that the CICS system is
to shut down after the occurrence of an error corresponding to this dump code.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET TRDUMPCODE
>>-CEMT Set TRDumpcode--+-(value)-+--+------------+------------->
'-ALl-----' +-Trandump---+
'-NOTrandump-'
>--+-----------+--+------------+--+---------+------------------->
+-SYsdump---+ +-SHutdown---+ +-RELated-+
'-NOSYsdump-' '-NOSHutdown-' '-Local---'
>--+----------------+--+--------+------------------------------><
'-Maximum(value)-' +-RESet--+
+-REMove-+
'-ADd----'
Options
- (value)
- specifies a 4-byte transaction dump code. See the CICS Messages and Codes manual for a list of transaction dump codes.
- ADd
- The specified transaction dump code is to be added to the dump code
table.
- ALl
- specifies that any changes you request are made to all resources of
the specified type that you are authorized to access.
- Local
- A system dump request is not to be sent to other MVS images in the sysplex
which are running XCF/MRO connected CICS regions related to the CICS region
on which the dump is initiated.
Note:
A related CICS region is one
in which the unit of work identifiers, in the form of APPC tokens, of one
or more tasks match those in the CICS region that issued the dump request.
- Maximum (value)
- specifies the largest number of dump calls for this dump code that result
in dumps being taken. The range is 0-999, though a value of 999 means ‘no
limit’.
- NOSHutdown
- The CICS system is not to shut down.
- NOSYsdump
- A system dump is not to be taken.
- NOTrandump
- A transaction dump is not to be taken.
- RELated
- A system dump request is to be sent to MVS images in the sysplex which
are running XCF/MRO connected CICS regions related to the CICS region on which
the dump is initiated.
Note:
A related CICS region is one in which
the unit of work identifiers, in the form of APPC tokens, of one or more tasks
match those in the CICS region that issued the dump request.
- REMove
- This code is to be removed from the dump code table.
- RESet
- The current count of dump calls for this dump code is to be reset to
zero.
- SHutdown
- The CICS system is to shut down after the occurrence of an error corresponding
to this dump code.
- SYsdump
- A system dump is to be taken.
- Trandump
- A transaction dump is to be taken.
Function
Delete a temporary storage queue (TS queue).
This section applies also to the alternative command, CEMT SET TSQNAME. Use either to delete temporary storage queues (TS queues)
with names up to 8 characters long. Use SET TSQNAME to delete temporary storage
queues (TS queues) with names up to 16 characters long.
Description
The SET TSQUEUE command enables you to delete a temporary storage queue
(TS queue).
The LASTUSEDINT option may be used to ensure that the queue to be deleted
has not been referenced since a previous INQUIRE was issued. It may also be
used to delete queues which have not been referenced within a given interval.
Syntax

CEMT SET TSQUEUE
.-ALl-----.
>>-CEMT Set TSqueue--+---------+--+-----------------+----------->
'-(value)-' +-SYSID(value)----+
'-POOLNAME(value)-'
>--+--------------------+--+-Action(value)-+-------------------><
'-LAstusedint(value)-' '-DELETE--------'
Options
- (value)
- specifies the identifier of the TS queue
- ALl
- specifies that any changes you request are made to all resources of
the specified type that you are authorized to access.
- ACTION(value)
- specifies the action to be taken on the queue. The values are:
- DELETE
- the queue is to be deleted.
- LASTUSEDINT
- if this option is specified, the queue is only deleted if its last used
interval is greater or equal to the value specified.
- POOLNAME(data-value)
- specifies an 8-character pool name.
- SYSID(data-value)
- specifies a 4-character shared sysid.
- TSQUEUE(data-value)
- specifies the 16-character identifier of the TS queue.
Function
Commit or back out a shunted unit of work.
Description
The SET UOW command enables you to commit, back out, or force a unit of work that
has been shunted during the transaction’s in-doubt period.
Syntax

CEMT SET UOW
>>-CEMT Set UOW(value)--+-(value)-+--+-COMmit--+---------------><
'-ALl-----' +-Backout-+
'-Force---'
Options
- (value)
- specifies the 16-character identifier of the UOW to be committed,
backed out, or forced.
- ALl
- specifies that any changes you request are made to all resources of
the specified type that you are authorized to access.
- Backout
- Attempt to force syncpoint backout processing, as specified for this UOW.
- COMmit
- Attempt to force syncpoint commit processing, as specified for this UOW.
- Force
- Attempt to force the UOW to backout or commit, as specified on the
ACTION option of the TRANSACTION resource definition.
Note that all these values are valid only for UOWs that have been shunted
in-doubt. For information about the in-doubt attributes of TRANSACTION definitions,
see the CICS Resource Definition Guide.
Function
Delete a link to a unit of work that was created by a connection that has since
been discarded.
UOWLINKS associated with RRS can be deleted when RRS has cold started.
Description
The association between a unit of work and a connection is known as a UOW-link.
You can use the INQUIRE UOWLINK command to browse all the UOW-links currently
in the system. Some of the UOW-links may have been created by connections that
have since been discarded. If so, you may be able to use the SET UOWLINK command
to delete them. (For information about when it is safe to delete UOW-links,
see the CICS Intercommunication Guide.)
Syntax

CEMT SET UOWLINK
>>-CEMT Set UOWlink(value)--+-(value)-+--Delete----------------><
'-ALl-----'
Options
- (value)
- specifies the 4-character identifier of the UOW-connection dependency
(the UOW-link) to which this command applies.
- ALl
- specifies that any changes you request are made to all resources of
the specified type that you are authorized to access.
- Delete
- specifies that the UOW-link is to be deleted.
Function
Enable or disable a URIMAP definition, and apply or remove redirection
for a URIMAP definition.
Description
If you disable a URIMAP definition, CICS returns an HTTP response to the
Web client with a 503 (Service Unavailable) status code.
You can use the redirection options to set redirection for matching HTTP
requests, and specify a URL to which the requests are redirected. You can
use this command to apply redirection to an existing URIMAP definition, for
example if the application that would normally respond to the HTTP request
is unavailable. You can also use this command to remove redirection from a
URIMAP definition.
Syntax

CEMT SET URIMAP
>>-CEMT Set URimap--+-(value)-+--+-Enabled--+--+-None------+---->
'-ALl-----' '-Disabled-' +-Temporary-+
'-Permanent-'
>--Location(value)---------------------------------------------><
Options
- (value)
- specifies the 8-character name of the URIMAP resource definition to
which this command applies.
- Enabled
- The URIMAP definition can be accessed.
- Disabled
- The URIMAP definition cannot be accessed.
- None
- Requests are not redirected. Any URL specified by the LOCATION option
is ignored.
- Temporary
- Requests are redirected on a temporary basis. The status code used for
the response is 302 (Found).
- Permanent
- Requests are redirected permanently. The status code used for the response
is 301 (Moved Permanently).
- Location (value)
- specifies a URL of up to 255 characters, to which matching HTTP requests
from Web clients can be redirected. This must be a complete URL, including
scheme, host, and path components, and appropriate delimiters. CICS checks
that the URL is complete and correctly delimited, but CICS does not check
that the destination is valid.
The REDIRECTTYPE option is used to specify
the type of redirection. If temporary or permanent redirection is specified,
the URL in the LOCATION attribute is used for redirection. If no redirection
is specified, the URL in the LOCATION option is ignored.
Function
Open or close the VTAM ACB, set the persistent session delay interval (PSDI),
or deregister CICS from membership of a generic resource.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET VTAM (the minimum abbreviation is CEMT S
VT). You get a display that lists the current status, similar to that
obtained by CEMT INQUIRE VTAM. You can then tab to the highlighted or blank
fields and overtype them with the required values.
- Type CEMT SET VTAM (CEMT S VT) followed by one or
more attribute settings that you wish to change. For example, cemt s
vt o specifies that the connection between CICS and VTAM is established.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET VTAM
>>-CEMT Set Vtam--+-Open-------+--+---------------------+------->
+-Closed-----+ '-Psdinterval(hhmmss)-'
+-Immclose---+
'-Forceclose-'
>--+--------------+--------------------------------------------><
'-Deregistered-'
Options
- Closed
- The connection between CICS and VTAM is to terminate normally; that
is, transactions are allowed to complete and terminals are released normally.
- Deregistered
- specifies that CICS is to be removed from the VTAM generic resource
that it is currently a member of. If you deregister a region from membership
of a generic resource, you should end any affinities that it owns--see
the PERFORM ENDAFFINITY command.
Generic resources are described in the CICS Intercommunication Guide.
- Forceclose
- The connection is terminated immediately, and all terminal connections
using the VTAM ACB (access method control block), together with the transactions
associated with them, are terminated abnormally. If transactions do not terminate
because of their state at the time FORCECLOSE was issued, it is necessary
to issue CEMT SET TASK(nn) PURGE or FORCEPURGE before the ACB can be reopened.
The difference between IMMCLOSE and FORCECLOSE is that IMMCLOSE cancels any
task at a VTAM terminal and then closes the terminal sessions tidily. FORCECLOSE
cancels any task and closes the VTAM ACB, terminating all sessions immediately.
- Immclose
- The connection between CICS and VTAM is to be terminated immediately.
Any transactions using VTAM-connected terminals are terminated abnormally,
and all such terminals are lost to CICS.
The difference between IMMCLOSE
and FORCECLOSE is that IMMCLOSE cancels any task at a VTAM terminal and then
closes the terminal sessions tidily. FORCECLOSE cancels any task and closes
the VTAM ACB, terminating all sessions immediately.
- Open
- The connection between CICS and VTAM is established. With ACF/VTAM,
this refers to the opening of the ACF/VTAM ACB through which ACF/VTAM communicates
with CICS.
A CEMT SET VTAM OPEN command will fail with a STILL CLOSING
message if the command is issued while a previous predatory takeover is still
being processed. No attempt is made to open the VTAM ACB, because it is still
being closed as a result of the predatory takeover. After the predatory takeover
completes, the CEMT SET VTAM OPEN command will work as normal. The failure
is notified by a RESP=INVREQ and RESP2=14 condition.
If CICS is using
VTAM multi-node persistent sessions, and VTAM has been restarted after an
abend, opening the VTAM ACB causes CICS to restore the persistent sessions
that VTAM has retained. However, CICS does not restore APPC synclevel 2 sessions,
which are unbound.
- Psdinterval (hhmmss)
- specifies the persistent session delay interval, expressed in the form hhmmss. It specifies if and for how long sessions are
held in recovery-pending state after CICS fails. The permitted range is 000000
to 235959 inclusive.
- 000000
- If CICS fails, sessions are terminated.
- Hhmmss
- If CICS fails, sessions are held in recovery-pending state by VTAM for
up to the interval specified.
Table 8 shows possible CEMT error messages resulting
from unsuccessful attempts to set the persistent session delay interval.
Function
Change Web garbage collection settings, or Web 3270 terminal timeout settings.
Input
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET WEB (the minimum abbreviation is CEMT S
WE). You get a display that lists the current
status, similar to that obtained by CEMT INQUIRE WEB. You can then tab to
the highlighted or blank fields and overtype them with the required values.
- Type CEMT SET WEB (CEMT S WE)
followed by one or more attribute settings that you wish to change. For example, cemt s we g specifies that you want
to change the GARBAGEINT option.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET WEB
>>-CEMT Set Web--+-------------------+--+-------------------+--><
'-Garbageint(value)-' '-Timeoutint(value)-'
Displayed fields
- GARBAGEINT
- is the interval at which the Web garbage collection task runs to clean
up Web 3270 state data for which the terminal timeout interval has expired.
The interval is measured in minutes.
- TIMEOUTINT
- is the period of time after which inactive Web 3270 sessions are eligible
for garbage collection. The period is measured in minutes.
Function
Set the validation status of a WEBSERVICE.
Description
If the optional attributes are omitted, the command has no effect.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET WEBSERVICE (the minimum abbreviation is CEMT S W) followed by one or more WEBSERVICE identifiers or ALL. You
get a display that lists the current status, similar to that obtained by CEMT
INQUIRE WEBSERVICE. You can then tab to the highlighted or blank fields and
overtype them with the required values.
- Type CEMT SET WEBSERVICE (CEMT S W) followed by
one or more WEBSERVICE identifiers or ALL, followed in turn by one or more
attribute settings that you wish to change. For example, cemt s we al
v resets the validation status for all WEBSERVICEs.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

SET WEBSERVICE
.-ALl-----.
>>-CEMT SET WEBSERVICE--+---------+--+--------------+----------><
'-(value)-' +-Validation---+
'-Novalidation-'
Conditions: NOTAUTH, NOTFND
Options
- ALl
- Any changes you request are made to all resources of the specified type
that you are authorized to access.
- (value)
- specifies the 1-8 character name of the WEBSERVICE.
- Validationst
- Specifies whether full validation of SOAP messages is required for this
WEBSERVICE:
- Validation
- Full validation is required.
- Novalidation
- Full validation is not required.
The WEBSERVICE must be INSERVICE before you can turn validation on
and off.
Function
Purge or Forcepurge a specific work request task.
Description
SET WORKREQUEST enables you to terminate specific work requests. You cannot
specify a list of identifiers, nor can you use the symbols * and + to specify
a family of work requests.
Syntax
Press the Clear key to clear the screen. There are two ways of commencing
this transaction:
- Type CEMT SET WORKREQUEST (the minimum abbreviation is CEMT S WO) with (value) or ALL. You get a display that lists
the current status, similar to that obtained by CEMT INQUIRE WORKREQUEST.
You can then tab to the Purgetype field and enter or overtype it with the
required value (PUrge or FOrcepurge).
- Type CEMT SET WORKREQUEST (CEMT S WO) with (value) or ALL, followed by the attribute setting that you wish to change.
For example, cemt s wo(value) pu will purge the specified
work request.
Typing ? at the beginning of either the first or second line gives a syntax
prompt. Resetting the values takes effect immediately.

CEMT SET WORKREQUEST
>>-CEMT Set WOrkrequest--+-(value)-+--+------+------------------>
'-All-----' +-Iiop-+
'-Soap-'
>--+------------+----------------------------------------------><
+-Purge------+
'-Forcepurge-'
Options
- (value)
- An 8-character string to identify the work request. The valid
characters for this token are the 16 hexadecimal digits, 0-9 and A-F.
The
token is generated by CICS. Normal usage begins with an INQUIRE WORKREQUEST
BROWSE command, to identify the token which is of interest. Then the specific
token can be used to issue INQUIRE and SET commands that relate to the task
in question.
- All
- Any action you request is performed for all work requests of the specified
type that you are authorized to access.
- Forcepurge
- The work request is terminated immediately. System integrity is not
guaranteed. In some extreme cases, for example if a work request is forcepurged
during backout processing, CICS terminates abnormally. If you want to terminate
a work request but do not want to terminate CICS, you should use PURGE instead
of FORCEPURGE.
- Iiop
- Specifies that any action you request is limited to IIOP work requests.
Soap 
Specifies that any action you request is limited to Web service work
requests.
- Purge
- The work request is terminated, but termination occurs only when system
and data integrity can be maintained.
[[ Contents Previous Page | Next Page Index ]]