Control section—DFHMCT TYPE=INITIAL

The control section name for the MCT is established by the DFHMCT TYPE=INITIAL macro. This macro also creates the necessary linkage editor control statements for subsequent link-editing.
Read syntax diagramSkip visual syntax diagram
                         .-,APPLNAME=NO--.                     
>>-DFHMCT--TYPE=INITIAL--+---------------+--+--------------+---->
                         '-,APPLNAME=YES-'  '-,FILE=number-'   

   .-,RMI=NO--.                                        
>--+-,RMI=YES-+--+------------+--+-----------------+-----------><
                 '-,SUFFIX=xx-'  '-,TSQUEUE=number-'   

For general information about TYPE=INITIAL macros, including the use of the SUFFIX operand, see TYPE=INITIAL (control section).

APPLNAME={NO∨YES}
This option specifies that you want to use the application naming support provided by CICS® monitoring.

Application naming is an enabling function that allows application programs to invoke special CICS event monitoring points. Data collected at these CICS-generated EMPs can be used by any CICS monitoring software package.

NO
Application naming support is not enabled in the CICS region and the application naming event monitoring points, DFHAPPL.1 and DFHAPPL.2, are not generated.
YES
Application naming support is enabled in the CICS region. When you assemble the MCT, CICS generates the application naming event monitoring points (DFHAPPL.1 and DFHAPPL.2). Note that the monitoring data moved at these EMPs by an EXEC CICS MONITOR command invoking these application naming EMPs is preserved until task termination, or until changed by another invocation of the EMPS by a subsquent EXEC CICS MONITOR command. See the MONITOR command in the CICS Application Programming Reference for more information.

The application naming (DFHAPPL) EMPs are created by CICS as if defined with the following TYPE=EMP macro parameters:

DFHMCT TYPE=EMP,CLASS=PERFORM,                                        X
                ID=(DFHAPPL.1),FIELD=(1,APPLNAME)                     X
                PERFORM=(MOVE(0,4))                                    
DFHMCT TYPE=EMP,CLASS=PERFORM,                                        X
                ID=(DFHAPPL.2),                                       X
                PERFORM=(MOVE(4,8))

For more information about how to use the application naming event monitoring points in your applications, see the CICS Customization Guide.

FILE={8∨number}
This option specifies the maximum number of files for which you want CICS to perform transaction resource monitoring. This option is applicable only if transaction resource monitoring is enabled, either by specifying MNRES=ON as a system initialization parameter, or by enabling it dynamically using an EXEC CICS, or CEMT, SET MONITOR command.
CICS standard monitoring performance class data includes totals for all files accessed by a transaction. Transaction resource monitoring, on the other hand, collects information about individual files, up to the number specified. The data collected is:

File name                                                                                  
Number and total time of file get requests          
Number and total time of file put requests        
Number and total time of file browse requests    
Number and total time of file add requests        
Number and total time of file delete requests      
Total number and total time of all requests against the file              
File access method request count                                                
File I/O wait time and number of waits                                        
RLS-mode file I/O wait time                                                        
Coupling facility data table (CFDT) I/O wait time                          

8
This is the default, and means that CICS is to perform transaction resource monitoring for a maximum of 8 files.
number
Specifies the maximum number of files, in the range 0 through 64, for which CICS is to perform transaction resource monitoring. CICS collects monitoring performance data at the resource level for each file accessed by a transaction, up to the maximum specified by number. If the transaction accesses more files than the number specified, any files over the maximum are ignored, but a flag is set to indicate that the transaction has exceeded the file limit.

If you specify FILE=0, specifying MNRES=YES either as a system initialization parameter or dynamically while CICS is running has no effect, and transaction resource monitoring data is not collected for files.

RMI={NO∨YES}
This option specifies whether you want additional monitoring performance class data to be collected for the resource managers used by your transactions.
NO
This is the default and specifies that you do not want monitoring performance data for the resource managers used by your transactions.
YES
Specifies that you do want additional monitoring performance data to be collected for the resource managers used by your transactions.

For information about the data that is collected see the CICS Performance Guide

TSQUEUE={4∨number}
This option specifies the maximum number of temporary storage queues for which you want CICS to perform transaction resource monitoring. This option is applicable only if transaction resource monitoring is enabled, either by specifying MNRES=ON as a system initialization parameter, or by enabling it dynamically using an EXEC CICS, or CEMT, SET MONITOR command.

CICS standard monitoring performance class data includes totals for all temporary storage queues accessed by a transaction. Transaction resource monitoring, on the other hand, collects information about individual temporary storage queues, up to the number specified.

4
This is the default, and means that CICS is to perform transaction resource monitoring for a maximum of 4 temporary storage queues.
number
Specifies the maximum number of temporary storage queues, in the range 0 through 32, for which CICS is to perform transaction resource monitoring. CICS collects monitoring performance data at the resource level for each temporary storage queue accessed by a transaction, up to the maximum specified by number. If the transaction accesses more temporary storage queues than the number specified, any temporary storage queues over the maximum are ignored, but a flag is set to indicate that the transaction has exceeded the temporary storage queue limit.
If you specify TSQUEUE=0, specifying MNRES=YES either as a system initialization parameter or dynamically while CICS is running has no effect, and transaction resource monitoring data is not collected for temporary storage queues. The data collected is:

Temporary storage queue name
Number and total time of temporary storage queue get requests
Number and total time of  temporary storage queue put requests to auxiliary temporary storage
Number and total time of  temporary storage queue put requests to main temporary storage
Total number and total time of all requests against the temporary storage queue
Total length of all the items obtained from temporary storage
Total length of all the items written to auxiliary temporary storage
Total length of all the items written to main temporary storage
Temporary storage I/O wait time and number of waits  
Shared temporary storage I/O wait time and number of waits

Note: The combined length of all the transaction resource monitoring data must not exceed 32244 bytes.