Running the Load Module Scanner

The Load Module Scanner scans load modules for instances of program commands that could cause resource dependencies or transaction affinities.

This section describes how to run the CICS® IA Load Module Scanner. The Load Module Scanner works by scanning the load modules for patterns of bits that might be commands.

The Load Module Scanner detects the use of:
You can use the Load Module Scanner to obtain any of the following reports or files:
  • A summary printed report listing the total number of modules scanned, the total that contain possible dependency-causing or affinity-causing commands, and similar conditions by running the CIUJCLLS job.
  • A summary printed report, with a separate list of modules that contain possible dependency-causing or affinity-causing commands, for input to a further job to produce a detailed report by running the CIUJCLLS job.
  • A summary printed report, with or without a separate module list, with updates to the CIU_SCAN_SUMMARY DB2® table by running the CIUJCLTS job. Your own programs can process the scan results by querying the CIU_SCAN_SUMMARY table.
  • A detailed printed report listing each possible dependency-causing or affinity-causing command in the scanned modules, with further information about the command by running the CIUJCLLD job.
  • A detailed printed report as described previously, with updates to the CIU_SCAN_DETAIL DB2 table by running the CIUJCLTD job. Your own programs can process the scan results by querying the CIU_SCAN_DETAIL table.
  • To extract scanner information into CSV files for use by a CICS IA UDB database refer to the Preparing CSV files.
You are recommended to use the Load Module Scanner by:
  1. Create a summary report and module list to identify modules that contain possible dependency-causing or affinity-causing commands. See Creating a summary report.
  2. Produce detailed reports to review modules that the summary report has identified. See Creating a detailed report.