Autogen Action Option › How to Automatically Generate "Using" Elements with Autogen › Autogen and Autogen Span Processing Examples › Example 1: Autogen or Autogen Span None

Example 1: Autogen or Autogen Span None

In this example, a developer changes COPYC1 in DEV Common SYSTEMC, Subsystem SUB1, and then wants to automatically generate all using elements within its same logical map. To do this, the developer performs the following Generate with Autogen or Autogen Span None 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 NONE . 

The effects of this GENERATE request are as follows:

• Copybook COPYC1 is copied back and generated at DEV/SYSTEMC/SUB1/1.
• PGMC1 found up the map at PRD/SYSTEMC/SUB1/2 is generated at DEV/SYSTEMC/SUB1/1 as a NOSOURCE element.
• No other using programs outside the logical map of the component are affected.

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

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