Autogen Action Option › How to Automatically Generate "Using" Elements with Autogen › How Autogen Span Options Work

How Autogen Span Options Work

Autogen generates only those using elements that are in the same logical map as the target component. Autogen Span options also generates using elements that are found in different Systems and Subsystems within the Environment and Stage of the logical map. Using elements are generated at the target Environment and Stage specified in the Autogen request, but in the System and Subsystem of the using element. The Span enhancement makes it easy to locate and generate using elements across Systems or Subsystems.

For all Autogen and Autogen Span results, any generated elements that are not currently at the target location are brought back as sourceless elements. However, an administrator can change the behavior of the Autogen feature, by activating AUTOGEN_SOURCE in the Optional Features Table (ENCOPTBL). When this option is activated, the Generate actions for the using elements are built with the Copyback, instead of the NoSource, option.

Also for all Autogen and Autogen Span results, using elements are not generated if they are located in unmapped Environments or they are located lower in the map than the target location of the component.

You can run any of the Autogen Span options in simulation mode, to preview the effects of an Autogen request.

The following values are valid for the Autogen option:

• Autogen or Autogen Span None: Generates only those using elements that are in the same logical map of the component specified. Whether you specify "Autogen" or "Autogen Span None", the SCL is written as "Autogen Span None".
• Autogen Span All: Generates using elements from all Systems and Subsystems.
• Autogen Span Systems: Generates using elements from all Systems with the same-named Subsystem of the component specified.
• Autogen Span Subsystems: Generates using elements from all Subsystems with the same-named System of the component specified.

The following restrictions apply to the SPAN options:

• Common libraries must be included in the generate processor concatenations of the Systems and Subsystems of the using elements. If the libraries are not included, then the Generate action does include the changes made to the component element when searching across Systems or Subsystems.
• The same Systems and Subsystems must exist in each Environment and Stage location. For example, if ELEMENTA is a using element in the PROD Environment, system A, then system A must exist in the DEV Environment also.
• SPAN only includes using elements from Systems or Subsystems located in the target Environment and higher up the map.
• SPAN does not include using elements from outside the Environment map.