Generate an Impact Subtree Report from a Code Search list. The report shows the impact trace subtrees for occurrences of data items in the list in XML format or in a database.


ImpactReportFromList LogFile Workspace Model ListName Category Output [Direction] [Split] [Project] 
Required Parameters Description


Output log file generated when the batch script is executed.


Workspace file (.rwp).


Interactive Analysis model for the listed source files. Some of the commonly used model types are: COBOL, JAVAFILE, JCL, NATURAL, PLI. For more information, see Define Potential Code Anomalies.


Name of the list. The list is assumed to be owned by the current user. If it is owned by another user, append a vertical bar (|) and the user name.
Note: Lists stay active in the workspace. As part of the verification process for an entity, any entry in a list for that entity is removed. The list will need to be recreated post verification. Any script that is used to create the list can be added to a post-verification user exit to the BRP process so they are correctly re-created as part of a BRP run.


List category.

Output Output file. The format of the report depends on the extension. Supported extensions are .xml and .mdb. When Split is set to Y, the path of the folder for .mdb output files.
Optional Parameters Description


Direction of the trace:

  • F or 1, to specify a forward trace.
  • B or 0, to specify a backward trace.

Forward is the default.

Split Whether to use the split program method, Y or N. The split program method generates a separate .mdb output file for each program that contains a data item occurrence in the list. N is the default.


Project. Default is the default project.