Chapter 4. Running the Scanner
This chapter describes how to run the Scanner that scans load modules for instances of API commands that could cause
You can run the Scanner to produce either a summary report and module list to identify suspect modules or a detailed report of modules that contain possible
The recommended way to use the Scanner is by:
vªCreating a summary reportº
vªCreating a detailed reportº on page 27
Creating a summary report
You can request a summary report from the Scanner by editing and running the job CAUJCLLS. This job can also output a list of modules with potential transaction affinities, for input to the CAUJCLLD job for more detailed reporting.
Before running the CAUJCLLS job, change the following as appropriate:
vThe JOB accounting parameters
vThe PARM statement:
PARM=©$SUMMARY[,DETAILMODS]©
where:
$SUMMARY
Speci®es that a summary scan (and report) is required for the entire library, except for CICS modules, CICS tables, and those modules that cannot be loaded (due to some error).
DETAILMODS
Speci®es that the names of those modules containing at least one possible
vThe STEPLIB DD statement
Specify the name of the Transaction Affinities Utility load library where you have installed the Scanner program, CAULMS.
vThe INPUT DD statement
Specify the name of the load library to be scanned.
vThe SYSPRINT DD statement
Specify the destination for the summary report.
© Copyright IBM Corp. 1994, 1999 | 25 |