Setting up event processing
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.
Procedure
Use this task to stop or start event processing.
Results
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
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-MQ adapter.