How to define a Monitoring Control Table (MCT) in CICS

Connor Blair
4 min readAug 21, 2020

--

The CICS Monitoring Control Table (MCT) defines which user and system performance data should be recorded. Using the MCT, you can define your own monitoring performance records and manage system defined performance records. In this tutorial, we are going to exclude system defined performance records.

For this tutorial, I will be using Topaz and ISPW . If you would like to learn more about these tools, checkout the links.

Setup our Environment

From the Topaz home screen, click on the Compuware menu on the toolbar at the top.

Topaz Home Page

Select ISPW from the list. From here we will need to create a container to hold all of our work. From the “ISPW Container” view at the bottom, select “Add New Assignment”.

Creating a Container

After you are done creating your container, open it by double clicking the container.

Defining the MCT CICS Resource Definitions File

First, we need to define the system records we want to exclude. Add a new task to your container in ISPW by clicking on “Add Task”.

Adding a Task to ISPW Container

For my project, I defined the file with the following attributes: Name: GMT00000, Type: PARM (but the type might differ in your ISPW application), Action Code: Normal , and Path: DEV2 (this path might differ in your ISPW application)

Once your file is created, open it and paste the following code:

This file defines all performance data records to be excluded.

Create Load Dataset for MCT Resource Definition Load Module

Before we can create the load module, we need a place to put it. For this tutorial, I’m going to create a new APF authorized dataset. Within the host explorer, right click on “z/OS datasets” then “Allocate” then select “PDS or Sequential Dataset”.

Define the dataset properties and select “Finish”.

Now we need to APF Authorize the dataset. To do that we need to open the console.

Select the console options menu and select “z/OS Console”.

Enter the following command to authorize your dataset.

Create MCT Resource Definition Load Module

Now that the MCT resource definition file is completed, we need to create a load module for CICS to use it. To do this, we are going to add a new PROC member to our container.

Add a new task to your ISPW Container with the following attributes: Name: GMT0000A, Type: PROC (this type might differ in your ISPW application), Action Code: Normal , and Path: DEV2 (this path might differ in your ISPW application).

Once your file is created, open it and paste the following code:

Now we need to create a JCL member to call this PROC. Add a new task to your ISPW Container with the following attributes: Name: GMT00000, Type: JOB (this type might differ in your ISPW application), Action Code: Normal , and Path: DEV2 (this path might differ in your ISPW application). Open it and paste the following:

Right click the job and select “SUBMIT”. After the job is completed, our load module should be ready. To validate that everything worked, check to see if the load module exists by creating a filter.

Including Our New MCT within a CICS Region

Now we just need to let our CICS region know about the new MCT table. To do that, update the DFHRPL and the SYSIN in your CICS startup JCL by doing something similar to the following:

Submit your job and that’s it!

Validation

Open up the Topaz 3270 Emulator.

Connect to your CICS region.

Clear the screen.

Enter the command below to show CICS monitoring information.

The performance class should be turned off.

That’s it!

--

--