Previous Topic: Construction Change Impact ReportNext Topic: Construction Regeneration Report

Intelligent Regeneration › Impact Analysis and Preview Reporting › Regeneration Impact Analysis Report

Regeneration Impact Analysis Report

The report only includes aggregate object changes that cause CA Gen to flag the components for regeneration.

Instructions for generating JCL for a batch job are at the end of the procedure.

Follow these steps:

  1. Display the Application System Regeneration menu.
  2. Type 3 for Regeneration impact analysis report. Press Enter.

    The Regeneration Impact Analysis Report panel displays.

  3. Type the Host Encyclopedia name of the model.

    Use the Tab key to position the cursor at the field and press the Prompt key for a list of valid choices. Select a model name from the list by typing any character except a period (.) or a space character next to the name, and press Enter.

    1. Scope the business system by placing a slash character (/) opposite the option to enable. Place a period character (.) opposite the option to disable.
    2. Type a business system name only when regenerating a single business system. To regenerate all business systems, leave this field blank.

      Use the Tab key to position the cursor at the field and press the Prompt key for a list of valid choices. Select a business system name from the list by typing any character except a period (.) or a space character next to the name and press Enter.

    3. Scope the load module by placing a slash character (/) opposite the option to enable. Place a period character (.) opposite the option to disable.
    4. Select the Execution mode, online, or batch.
  4. Press Enter.

    The Regeneration Options panel displays as shown in the following illustration:

                                  Regeneration Options
 COMMAND ===> 

  To limit regeneration by date, type a beginning and/or ending date.
  To limit regeneration to a specific user, type the TSO user ID.              
  To limit regeneration to a specific group, type the Group ID.                
  To ignore Target Environment Parameter changes, select Yes.                  
  To mark and record components requiring regeneration, select Yes.            

  Begin date  . . . . . . . . . . . . . . . . .   0___ - 0_ - 0_ YYYY-MM-DD or 0
  End   date  . . . . . . . . . . . . . . . . .   0___ - 0_ - 0_ YYYY-MM-DD or 0
  User ID . . . . . . . . . . . . . . . . . . .   ________ TSO user ID         
  Group ID  . . . . . . . . . . . . . . . . . .   ________ Group ID            
  Ignore Target Environment Parameter Changes . . . . .    / Yes               
                                                           . No                
  Mark & record components requiring regeneration . . .    / Yes               
                                                           . No                

  Limiting regeneration to a particular user/group or by date may cause        
  inconsistencies at generation/installation time.  Some components that       
  are not within these limits may need to be regenerated.
  5. Specify required limitations on the scope of the regeneration for beginning or ending dates, TSO user ID, Group ID, and rejection of the target environment changes and press Enter.

    Limiting regeneration to a particular user/group or by date can cause inconsistencies during generation and installation. Some components that are not within the specified limitations may need regeneration.

  6. To retain the results of the analysis, select Yes for the Mark & record components requiring regeneration option. Selecting Yes updates OK Session Flag and a subsequent regeneration does not list the aggregate changes that caused CA Gen to flag the component for regeneration. Selecting No to get the list of aggregates and the corresponding components requiring regeneration and their reasons for regeneration in subsequent sessions.
  7. When you select No for the Ignore Target Environment Parameter Changes option, Intelligent Regeneration can detect changes to the business system target environment parameters and RI Trigger Target Environment parameters, Dynamically Link RI Triggers option, and RI Trigger Name. Intelligent Regeneration cannot detect other changes to the RI Trigger Target Environment parameters such as DBMS type for RI triggers and it cannot detect the changes to DBMS type for RI triggers. If DBMS type has changed for RI triggers, generate and install the RI triggers using the Application System Construction tools, that is, the regular generation, tools.

    If you chose foreground processing, CA Gen starts the report processing. When complete, the Browse Report File panel displays.

    If you selected background processing, the JCL for the report displays in ISPF Edit mode and you can change the JCL.

    If the Auto-submit option on the Generation Options screen was not set to Yes, type Submit on the COMMAND line and press Enter to submit the job for processing.

    The Application System Regeneration menu displays so you can perform other processing. Omit the remaining steps in this procedure.

  8. Review the report in the Browse Report File panel and click End when finished.

    The Report Print Options panel displays.

  9. Press the appropriate key or type a command on the COMMAND line and press Enter.

    CA Gen returns to the Application System Regeneration menu.

The following illustration is an example of the Regeneration Impact Analysis Report.

2009-11-24                INTELLIGENT REGENERATION                PAGE    1
  06:31               REGENERATION IMPACT ANALYSIS REPORT               

     MODEL NAME:              GEN SAMPLE MODEL                        
                          ALL OBJECTS CHANGED IN MODEL                  
                                  BY ALL USERS                          
                                                                        
  All Business System components and all RI Triggers were flagged for   
  Regeneration.  All Business System components and all RI Triggers were flagged
  for Installation.  Review Construction Regeneration Report for additional
  information.

If no aggregate changes caused CA Gen to flag components, but components were flagged in an earlier session and not regenerated at that time, or components existed that had not been generated or installed, CA Gen displays one of the following mutually exclusive messages:

The following messages could also occur in this report: