- Display the Application System Regeneration panel.
Application System Regeneration
COMMAND ===>
Select one of the options below, then press enter.
_ 1. Construction change impact report
2. Regenerate application system
3. Regeneration impact analysis report
4. Construction regeneration report
F1=Help F3=Exit F12=Cancel
- Type 2 for Regenerate application system and press Enter.
Regenerate Application System
COMMAND ===>
Type a model name or request Prompt for list selection. Select the business
system scope. If the business system scope is one business system, type a
business system name or request Prompt for list selection. Select the load
module scope, then press enter.
Model name . . . . . . GEN SAMPLE MODEL________________ +
Business System scope / All business systems
. One
Business System name ________________________________ +
Load Module scope . . / All load modules
. Multiple
F1=Help F3=Exit F4=Prompt F12=Cancel
- Type the Host Encyclopedia name of the model or use the Tab key to move the cursor to 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.
- Scope the business system by placing a slash character (/) opposite the option to enable. Place a period character (.) opposite the option to disable.
- Type a business system name only if you are regenerating a single business system. To regenerate all business systems, do not type a name in this blank.
You can also use the Tab key to move the cursor to 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.
- Scope the load module by placing a slash character (/) opposite the option to enable. Place a period character (.) opposite the option you disable.
- Press Enter.
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.
F1=Help F3=Exit F12=Cancel
- Specify required limitations, if any, on the scope of the regeneration about beginning or ending dates, TSO user ID, Group ID, and rejection of the target environment changes.
Limiting regeneration to a particular user/group or by date cause inconsistencies during generation and installation. Some components that are not within the specified limitations require regeneration.
- To retain the results of the analysis, select Yes for the Mark & record components requiring generation option. This option is useful if no or minimal changes had been made to a model since the last regeneration session but components had been marked for regeneration in that earlier session and the user chose not to regenerate them. If this option is set to No, the next intelligent regeneration operation must extract all of the aggregate changes that are made to the model since the earliest generation date for the set of components. This would degrade performance.
- 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 RI Trigger Target Environment parameter changes, such as DBMS type for RI triggers. If the DBMS type has changed for RI triggers, generate and install the RI triggers using the Application System Construction (regular generation) tools.
- Press Enter.
Regeneration
COMMAND ===>
Select one of the options below, then press enter.
_ 1. Business system
2. Load module
3. Action block
4. Screen
5. Referential integrity triggers
F1=Help F3=Exit F12=Cancel
- Select the appropriate level of detail for the regeneration.
- When Referential Integrity triggers need regeneration, CA Gen selects that option automatically. The Referential Integrity triggers must be generated first.
- When you select Business system, you receive all the business systems within your model that is flagged for regeneration and you can expand components to their lower levels.
- When you select Load module, you receive all the load modules within your model that is flagged for regeneration and can expand components to lower levels.
- When you select Action block, you receive all action blocks within your model that is flagged for regeneration.
- When you select Screen, you receive all the screens within your model that is flagged for regeneration.
- When CA Gen determines that Referential Integrity triggers require regeneration, it displays the Referential Integrity Processing Options panel to select generation options for the RI triggers.