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 diagramDFHMCTTYPE=INITIAL,APPLNAME=NO,APPLNAME=YES,COMPRESS=YES,COMPRESS=NO,DPL=0,DPL=number,FILE=8,FILE=number,RMI=YES,RMI=NO,SUFFIX=xx,TSQUEUE=8,TSQUEUE=number

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

Note: The combined length of all the transaction resource monitoring data must not exceed 32244 bytes.
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 call 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 the monitoring data moved at these EMPs by a command MONITOR that is calling these application naming EMPs is preserved until the end of the task, or until it is changed by another call of the EMPS by a subsequent EXEC CICS MONITOR command.
The application naming (DFHAPPL) EMPs are created by CICS as if defined with the 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 Application naming event monitoring points.

COMPRESS={YES|NO}
This option specifies whether you want data compression to be performed for the CICS SMF 110 monitoring records produced by the CICS monitoring facility.
YES
This default specifies that you want monitoring record data compression to be performed for the CICS SMF 110 monitoring records produced by the CICS monitoring facility. For information about data compression, see Data compression for monitoring records.
NO
Specifies that you do not want monitoring record data compression to be performed for the CICS SMF 110 monitoring records output by the CICS monitoring facility.
DPL={0|number}
This option specifies the maximum number of distributed program link (DPL) requests for which you want CICS to perform transaction resource monitoring. This option applies only if transaction resource monitoring is enabled, either by specifying MNRES=ON as a system initialization parameter, or by enabling it dynamically using the monitoring facility transaction CEMN or an EXEC CICS, or CEMT, SET MONITOR command.

CICS standard monitoring performance class data includes totals for all programs accessed by a transaction, including distributed program links. Transaction resource monitoring, alternatively, collects information about individual distributed program links, up to the number specified. The following data is collected:

  • Program name
  • System identifier (sysid) where the request is routed
  • Number of distributed program link (DPL) requests
0
This default specifies that CICS is not to perform transaction resource monitoring for any distributed program links.
number
Specifies the maximum number of distributed program link requests, in the range 0 - 64, for which CICS is to perform transaction resource monitoring. CICS collects monitoring performance data at the resource level for each distributed program link request issued by a transaction, up to the maximum specified by number. If the transaction issues more distributed program link requests than the number specified, any requests over the maximum are ignored, but a flag is set to indicate that the transaction has exceeded the DPL limit.

If you specify DPL=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 distributed program links.

FILE={8|number}
This option specifies the maximum number of files for which you want CICS to perform transaction resource monitoring. This option applies only if transaction resource monitoring is enabled, either by specifying MNRES=ON as a system initialization parameter, or by enabling it dynamically using the monitoring facility transaction CEMN or 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, alternatively, collects information about individual files, up to the number specified. The following data is collected:
  • 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 and number of waits
  • Coupling facility data table (CFDT) I/O wait time and number of waits
  • Exclusive control wait time and number of waits
  • VSAM string wait time and number of waits
8
This default specifies 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 - 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=ON 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={YES|NO}
This option specifies whether you want additional monitoring performance class data to be collected for the resource managers used by your transactions.
YES
This default 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 Performance data in group DFHRMI.

NO
This specifies that you do not want monitoring performance data for the resource managers used by your transactions.
TSQUEUE={8|number}
This option specifies the maximum number of temporary storage queues for which you want CICS to perform transaction resource monitoring. This option applies only if transaction resource monitoring is enabled, either by specifying MNRES=ON as a system initialization parameter, or by enabling it dynamically using the monitoring facility transaction CEMN or 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, alternatively, collects information about individual temporary storage queues, up to the number specified.

number
Specifies the maximum number of temporary storage queues, in the range 0 - 64, 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=ON 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 following data is collected:
  • Temporary storage queue name
  • Number and total time of temporary storage queue get requests
  • Number and total time of temporary storage queue get requests to shared temporary storage
  • 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
  • Number and total time of temporary storage queue put requests to shared 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 obtained from shared temporary storage
  • Total length of all the items written to auxiliary temporary storage
  • Total length of all the items written to main temporary storage
  • Total length of all the items written to shared temporary storage
  • Temporary storage I/O wait time and number of waits
  • Shared temporary storage I/O wait time and number of waits
8
This default specifies that CICS is to perform transaction resource monitoring for a maximum of 8 temporary storage queues.