Creating a summary report
You can request a summary report from the Load Module Scanner by editing and running the CIUJCLLS job.
This job can also produce a separate list of modules that contain possible dependency-causing or affinity-causing commands, for input to the CIUJCLLD or CIUJCLTD job for more detailed reporting.
Before running the CIUJCLLS job, change the following as appropriate:
- The JOB accounting parameters
- The PARM keyword of the EXEC statement:
where:PARM='SUMMARY[,DETAILMODS]'
- SUMMARY
- Specifies that a summary scan and report is required for the entire library, except for CICS® modules, CICS IA modules, CICS tables, and those modules that cannot be loaded, because of an error.
- DETAILMODS
- Specifies that the names of those modules containing at least one possible dependency-causing or affinity-causing command are to be written to the sequential file defined by the INTMOD DD statement. This file might be used to restrict a subsequent detailed report, by specifying it on the DETAIL DD statement of a detailed report run of the Load Module Scanner.
- The STEPLIB DD statement; specify the name of the CICS IA load library in which you have installed the Load Module Scanner program, CIULMS. The default is hlq.SCIULOAD, where hlq is the data set qualifier assigned during installation.
- The INPUT DD statement; specify the name of the load library to be scanned.
- The SYSPRINT DD statement; specify the destination for the summary report.
- The INTMOD DD statement; specify the name of the sequential data set to which the list of modules that contain possible dependency-causing or affinity-causing commands is to be sent. You can edit the data set to alter the list of modules to be scanned before running the Load Module Scanner to produce a detailed report.
- The CIUPRINT DD statement; specify the destination of error messages (SYSOUT=*).
Each summary report has the following content:
- A separate line for the following information about each module
in the library:
- Name
- Size
- Language (if determined)
If a load module is created from several source languages, only one language is indicated.
- Whether it is reentrant.
- Language version: Language Environment® (LE) or non-LE
- Number of possible affinity-causing commands
- Number of possible dependency-causing commands
- Number of possible MVS™ POST commands
- The total count of:
- Modules in the library
- Modules scanned
- CICS modules and tables (not scanned)
- Modules in error (not scanned)
- Modules that contain MVS POST commands
- Modules that contain commands that might cause dependencies
- Modules that contain commands that might cause affinities
- Assembler modules
- C modules
- COBOL modules
- PL/I modules
Figure 1 is an example of a summary report produced by the Load Module Scanner.
Figure 1. Example
of a summary report produced by the Load Module Scanner
CICS INTERDEPENDENCY ANALYZER Version 5.3.0 06/24/13 Page 1
LOAD MODULE SCANNER - SUMMARY LISTING OF CICSTLS.CICS1104.LOADLIB
Module Module Module Re- Language Possible statements.................. Comment
Name Length Language entrant Version Affinities Dependencies MVS POSTs
-------- -------- ---------- ------- -------- ---------- ------------ --------- -------------
DFHPLTPI CICS TABLE
DFHPLTSD CICS TABLE
EMSTESTA 00001FA8 COBOL II Y LE 14 14 0
EMSTESTB 000014A8 COBOL II Y LE 0 0 0
EMSTESTC 00000A48 COBOL II Non LE 3 3 0
CICS INTERDEPENDENCY ANALYZER Version 5.3.0 06/24/13 Page 2
LOAD MODULE SCANNER - SUMMARY LISTING OF CICSTLS.CICS1104.LOADLIB
LOAD LIBRARY STATISTICS
=================================================================
Total modules in library = 5
Total modules scanned = 3
Total CICS modules/tables (not scanned) = 2
Total modules in error (not scanned) = 0
Total modules containing possible MVS POSTs = 0
Total modules containing possible Dependency commands = 2
Total modules containing possible Affinity commands = 2
Total ASSEMBLER modules = 0
Total C/370 modules = 0
Total COBOL modules = 0
Total COBOL II modules = 3
Total PL/I modules = 0
Total number of possible Dependency commands = 17
Total number of possible Affinity commands = 17