Autogen Action Option › How to Automatically Generate "Using" Elements with Autogen › Autogen and Autogen Span Processing Examples › Example 4: Autogen Span Subsystems

Example 4: Autogen Span Subsystems

In this example, a developer changes COPYC1 in DEV Common SYSTEMC, Subsystem SUB1, and then wants to automatically generate all using elements that use the copybook in all Subsystems in their current System. To do this, the developer performs the following Generate with Autogen Span Subsystems request:

GENERATE ELEMENT 'COPYC1' 
FROM ENVIRONMENT 'DEV' 
SYSTEM 'SYSTEMC' 
SUBSYSTEM 'SUB1' 
TYPE COPYBOOK 
STAGE NUMBER 1 
OPTIONS CCID REQ#43023 
COMMENT 'EDIT COMMON COPY BOOKS' 
COPYBACK
AUTOGEN SPAN SUBSYSTEMS . 

The effects of this GENERATE request are as follows:

• Copybook COPYC1 is copied back and generated at DEV/SYSTEMC/SUB1/1.
• Element PGMC1, located up the map at PRD/SYSTEMC/SUB1/2 is generated at DEV/SYSTEMC/SUB1/1 as a NOSOURCE element.
• Element PGMC2, located outside the map at PRD/SYSTEMC/SUBC/2 is generated at DEV/SYSTEMC/SUBC/1 as a NOSOURCE element.
• No other Systems are affected with an Autogen Span Subsystems request and thus, using elements in Systems SYSTEM1, SYSTEM2, and SYSTEM3 are not generated.

Now the developer can complete his testing, and create a package with Move actions that includes all the effected elements.

After an Autogen Span Subsystems— The following graphic shows results after a Generate with Autogen Span SubSystems request is performed on COPYC1 at the target location Environment ‘DEV’, Stage 1, System ‘SYSTEMC’, Subsystem ‘SUB1’.