Before you can use event processing, your CICS® system must be correctly configured. You
can stop and start event processing in CICS using
a number of methods, including using IBM® CICS Explorer®.
About this task
You might want to stop event processing for an upgrade
or system maintenance, and then start event processing again. This
task explains the process usingCICS Explorer.
Use
the LOCALCCSID system initialization parameter to specify the coded
character set identifier for your local CICS region.
This is the default code page for application programs. The default
setting for LOCALCCSID is the EBCDIC code page 037. CICS translates the data content of event binding
files into this code page before using it for event capture filtering
operations, and assumes that any captured character data is in this
code page.
Event processing is enabled by default when a START=INITIAL
or START=COLD parameter is used during the startup of your CICS systems.
When a START=WARM
or START=EMERGENCY parameter is used, the settings from the previous
run of CICS are used.
Note: Do not change the status of event processing (that
is, set to start, drain, or stop) while a unit of work that captures
synchronous transactional events is in progress because you might
cause the events to be backed out and the transaction to end abnormally.
Procedure
Use this task to stop or start event processing.
- Using the CICSplex Explorer view in CICS Explorer,
click the CICSplex or CICS region
to select the CICSplex or CICS region
on which you want to stop event processing.
- Using the CICS Explorer toolbar,
click . The status of event
processing is displayed.
- Right-click to select the region on which you want to stop
event processing and click Stop. Then click OK.
Note: The status does not update until you click the refresh icon
at which point the STOPPED status is
displayed in the Event Processing Status column,
indicating that event processing is stopped.
- To restart event processing, right-click to
select the region for which you want to start event processing and
click Start. Then click OK.
Note: The status does not update until you click the refresh icon
at which point the STARTED status is
displayed, indicating that event processing is started.
Results
When event processing is
STOPPED,
event capture is stopped immediately. All events on the dispatcher
queue are deleted.
When event processing is
STARTED,
for in flight transactions, the capture of nontransactional events
starts immediately and the capture of transactional events starts
at the next sync point.
What to do next
You must enable an event binding and an EP adapter before
you can emit any events for processing by an event consumer. For more
information, see
Enabling an event binding in the CICS Explorer product documentation and
Enabling an event adapter in the CICS Explorer product documentation.
If you are using
the WebSphere MQ EP adapter to format and process your events, you
must set up the CICS-WebSphere MQ adapter to provide a connection
between the CICS region and IBM MQ on z/OS®. For instructions to do this,
see Setting up the CICS-WebSphere MQ adapter.