Customizing a CICS region to provide usage data

Procedure

Copy the appropriate HSIZFTCx and HSIZEIIx global user exit (GLUE) programs from the SHSIMOD1 library to a DFHRPL library of the CICS region.
Customize and submit the HSISENAX job to create a program that enables the HSIZFTCx and HSIZEIIx exit programs:
1. Customize the sample job for translating, assembling, and binding the enabling program that is provided in the HSISENAX member in the customized JCLLIB library.
  For convenience, you can name this program HSIZENAx, where x is the same suffix character as the suffix of the HSIZFTCx and HSIZEIIx programs that it enables.
2. Check that the name specified in the PROGRAM operand of EXEC CICS ENABLE statement is the name of the enabling program.
3. Check that the name specified in EXEC CICS ENABLE PROGRAM statement is the name of the of the GLUE programs.
4. Link the HSIZENAx enabling program into the same DFHRPL library where you copied the HSIZFTCx and HSIZEIIx GLUE programs.
5. Submit the HSIZENAx job.
Add an entry in the following format to the active program library table (PLT) of the CICS Transaction Server to install the HSIZENAx module:
```
DFHPLT TYPE=ENTRY,PROGRAM=HSIZENA
```
Place the entry before the DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM entry to load it early during CICS initialization and minimize the need for program resource definitions.
Ensure that the PLTPI setting for the CICS region specifies your newly updated PLT.
Optional: Use the HSITAGP tagger program to tag non-vendor application programs that you want to be identified in usage reports.

Results

When you complete this task, the use of programs that are given control by various mechanisms in the CICS Transaction Server are attributed to the CICS region address spaces that invoke them.

What to do next

You can stop data collection from all HSIZFTCx and HSIZEIIx glue programs with the CIC(N) Usage Monitor setting. The CIC(Y) option is the default if you do not issue a CIC Usage Monitor command.