Analysis impact report

You can use this information to estimate the time required to complete a change. 

You can use the analysis impact report to understand how the requested changes might impact the availability of the schema definition of your applications. 

During deployment configuration, if you enter a value for the Impact Report PDS and Member Name field in the BMC AMI DevOps Schema Mgmt for Db2 - Schema Mig step, the analysis impact report is created when Analysis runs.

You can view this report on the mainframe, download it to the project workspace, or even receive it by email if you define your pipeline process accordingly.

Impact report data collection

When the impact report is generated, the data will be collected in the BMC AMI DevOps repository tables if you choose to define them. For more information see, BMC-AMI-DevOps-tables-for-Schema-Standards.

The data collection is not required and the impact report generation will function the same without collecting the data but your impact report will give this message in the Summary of All Actions section:

BMC396495I BMC AMI DevOps for Db2 product tables not found, updates bypassed

This topic contains the following sections:

• Sample analysis impact report
• Summary of All Actions section
• Details for Selected Utilities section

Sample analysis impact report

Summary of All Actions section

This section of the analysis impact report displays information in two tables:

• The count of objects per action
• The count of objects per command or utility

The count of objects per action

This table has two columns:

• The Actions column lists the actions performed on objects.

  • The object types listed under each action represent explicit actions in the WorkID analysis.

    Action	Description
    ALTERS	Altered objects in the worklist If multiple alters are performed for a single object in the worklist, the count only increments by 1.For example, if four partitions are altered in a table space, the analysis impact report indicates that only one object is altered even though the worklist contains four separate alter statements. If the alter is performed on a table to create a unique constraint, check constraint, or foreign key, the analysis impact report considers this to be a CREATE action.
    CREATES	Newly created objects in the worklist that are not part of a drop/re-create
    DROPS	Explicitly dropped objects in the worklist that are not part of a drop/re-create The analysis impact report might consider a drop of a single object in the worklist to be the drop of multiple objects.  For example, if the worklist drops a single table space, all the tables, indexes, views, synonyms, constraints, and other objects under the table space are also counted as DROPs in the report.
    DROPS/RE-CREATES	Objects that are dropped in the worklist and then re-created The analysis impact report might consider a drop of a single object in the worklist to be the drop/re-creation of multiple objects. For example, when the worklist drops a single table space, all the tables, indexes, views, synonyms, constraints, and other objects under the table space are re-created. The report increments the count based on the number of re-creates.

• The Objects Impacted column displays the count of unique objects that the action affects. 

  Important

  The total impacted count per action will not always be the sum of the objects impacted per type since all object types are not listed in the summary report.

The count of objects per command or utility

This table has four columns:

• The Commands/Utilities column lists the commands or utilities that the worklist might include:
  • IMAGE COPIES
  • UNLOADS
  • LOADS
  • REORGS
  • RUNSTATS
  • BINDS/REBINDS

• The Info/Vendor column names the vendor for each utility. 

  Important

  The Info/Vendor column displays:

  • NO COPY for IMAGE COPIES if the worklist does not request image copies.
  • FORCE for IMAGE COPIES if the worklist is built with a NOCOPYFORCE request.
  • NO STATS for RUNSTATS if the worklist does not request statistics.
  • The column always displays no value for BINDS/REBINDS.
• The Count column displays the count of objects on which the command or utility acts.

• The Details Listed column displays Y or N for the following utilities:

  • UNLOAD
  • LOAD
  • REORG

  If count > 0 for any of these utilities, Y is displayed in this column, and more information is displayed in the Details for Selected Utilities section.

Details for Selected Utilities section

This section displays the following information for the following utilities:

• REORGS - TS utility

  Column name	Description
  TS Size Estimate	An estimate of the calculated size of the table space partitions that are reorganized This column might display the size of the entire table space for non-partitioned tables or tables for which all partitions are included in the reorganization.
  Cardinality	The total number of rows in all the tables in the table space or in the data in the partitions that are processed
  TABLESPACE	The name of the table space
  Impacted Partitions	The number of partitions in the table space affected by the reorganization If the table space is not partitioned, this column displays Non-partitioned.

• REORGS - IX utility

  Column name	Description
  IX Size Estimate	An estimate of the calculated size of the index
  Cardinality	The number of rows in the index
  INDEX	The name of the index

• UNLOADS/LOADS - TB utility

  Column name	Description
  TB Size Estimate	An estimate of the calculated size of the table
  Cardinality	The number of rows in the table
  TABLE	The name of the table