Creating a detailed report – IBM Transaction Server OS User Manual
Page 43
Creating a detailed report
You can request a detailed report from the Scanner by editing and running the job
CAUJCLLD.
Change the following statements as appropriate:
v
The PARM statement
PARM='$DETAIL[,ALL]'
$DETAIL
Specifies that a detailed scan and report is required. The extent of the scan
is defined by either the ALL parameter or the DETAIL DD statement.
ALL
Specifies that all modules in the load library are to be scanned for possible
affinity-causing EXEC CICS commands and MVS POST commands.
If ALL is omitted, only those modules listed in the file specified on the
DETAIL DD statement are to be scanned. This file would normally be from
the AFFMOD DD output of an Scanner summary report run, which you can
edit before creating a detailed report.
CICS TRANSACTION AFFINITIES UTILITY
1995/11/24 Page
1
LOAD MODULE SCANNER - SUMMARY LISTING OF CICSTEST.LOAD
Module
Module
Module
Affinity
MVS POSTs
Comment
Name
Length
Language
Statements
-------- -------- ---------
----------
---------
------------------------
--------------------
ACSA1
00000198 ASSEMBLER
3
0
Possible affinity commands.
AFFYIC
00000308
0
0
AFFYTS
00000628
0
0
COBACSA
000008B8 COBOL II
4
0
Possible affinity commands.
CRMRPROG 000001A0
0
0
DFHSRT1$
CICS TABLE
0
0
DFHTCTSH
CICS TABLE
0
0
DFHTSTEC
CICS TABLE
0
0
PLIACSA
000003C8 PL/I
3
0
Possible affinity commands.
PLTCCC
00000D48 C/370
2
0
Possible affinity commands.
PLTCOB
000009D8 COBOL II
2
0
Possible affinity commands.
PLTPLI
00000570 PL/I
1
0
Possible affinity commands.
SCRATCH
000006D0
0
0
TRANOUT
000008B8
0
1
Possible MVS POSTs.
CICS TRANSACTION AFFINITIES UTILITY
1995/11/24 Page
2
LOAD MODULE SCANNER - SUMMARY LISTING OF CICSTEST.LOAD
LOAD LIBRARY STATISTICS
==========================================================
Total modules in library
=
14
Total modules scanned
=
11
Total CICS modules/tables (not scanned)
=
3
Total modules in error (not scanned)
=
0
Total modules containing possible MVS POSTs
=
1
Total modules containing possible Affinity commands =
6
Total ASSEMBLER modules
=
1
Total C/370 modules
=
1
Total COBOL modules
=
0
Total COBOL II modules
=
2
Total PL/I modules
=
2
Figure 4. Example of a summary report produced by the Scanner
Chapter 4. Running the Scanner
27