Post configuration tasks
This section describes some optional tasks that you might be required to be perform.
- Creating your own program exclude, transaction exclude, command exclude, and resource compression list
You can use program exclude lists, transaction exclude lists, command exclude lists, and resource compression list to limit the volume of information collected by the Collector. In this section the term, Collector, refers to the Affinity and Dependency collector functions but for command exclude list the term, Collector, refers only to the Dependency collector functions. - Grouping transactions and programs into applications
CICS IA Version 5.1 and later provides utilities so that you can use CICS IA Version 3.2 Application definitions in your CICS IA Version 5.1 or later environment. However, CICS Transaction Server Version 5.1 and later provides the capability to define applications as part of the platform capabilities, and it is now advisable to define applications in this way. - CICS IA Natural support
With CICS IA, you can gather CICS resource information for COBOL, PL/I, and Assembler language programs called from within a Software AG Natural program. - Starting and stopping CICS IA from the PLT
You can start CICS IA from a program list table (PLT) program that is initiated during the third stage of CICS initialization; that is, a program that is specified in the second part of the program list table post initialization (PLTPI) list for the CICS region. - CICS IA supplied modules required in the MVS link list
If you use the MVS™ interactive problem control system (IPCS) to format and analyze CICS system dumps, you can use the CICS IA system dump formatting routines, CIUIADUF and CIUICDUF, to format the CICS IA collector data areas. Creating your translation table
CICS IA uses a translation table to translate the resource name of the CICS IA dependency data before it is loaded to the DB2® CIU_CICS_DATA table or it creates the hlqc.CICS.CSV file.
Parent topic: Configuring CICS IA