Stopping a CICS region

You can use CICS® DA to stop a CICS region. When the region is stopping, you can use the System Log and z/OS® Jobs views to monitor the progress.

Before you begin

Before you can stop a CICS region, you must have an active CICS DA connection. You must also have a copy of the system model on your local computer.

About this task

This task stops a CICS region by running the command in the region stop policy. By default, CICS DA submits the stop command F {jobName},COSD if the region is a CMAS, or F {jobName},CEMT P SHUT for other CICS regions. However, you can change the stop policy for individual regions, in the region editor. For more information about specifying the stop policy, see Specifying the region stop policy.

Note: CICS DA issues the z/OS MODIFY command to shut down a CICS region. If your organization uses multiple CICS regions with the same job name, then you cannot stop these regions by using the default stop policy. You must change the default stop policy to the command you use to stop your region. For example, you might change the stop command for the region to be: F jobname.identifier,CEMT P SHUT.

Procedure

  1. In the DA Explorer view, expand the system model to show the CICS region that you want to stop.
  2. You can use one of these choices to stop the CICS region:
    • Right-click the CICS region and click Stop region. If the CICS region is not running, then this option is not available.
    • Open the Region editor by double-clicking the region name, and clicking Stop in the editor.

What to do next

The CICS region stop command is issued. CICS DA does not wait for a response or monitor the progress of the CICS region stop. You must review the spool output for the CICS region job to check for errors or messages. You can refresh the status in CICS DA to show the latest status for the CICS region. For more information about refreshing the model element status, see the related links.

After a refresh is run, the model shows the new status for the CICS region. CICS DA writes a message to the Console view and the audit log recording the action.