How to Generate "Using" Elements with Autogen › How to Automatically Generate "Using" Elements with Autogen › Review Prerequisites

Review Prerequisites

Before using the Autogen action option, complete the following prerequisites:

• Verify that the CA Endevor Automated Configuration option has been purchased and enabled for your site. You can use the Display Site panel to determine if this option is activated (ASCM=Y) at your site.
• Verify that Global Type Sequencing is enabled. This processing option causes the batch processing of element actions to occur in a Type sequence defined at the site level. Autogen requires Global Type Sequencing so that the elements that use a component are generated after all of the components have been processed (for example, macros before source, source before load modules). For more information on enabling Global Type Sequencing, see the scenario How to Enable Global Type Sequencing.
• Verify the AUTOGEN_SOURCE setting in the Optional Features table. When AUTOGEN_SOURCE is not turned on, Generate actions for using elements are built with the NoSource option. This is the default. 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.
• This scenario assumes you have the following knowledge:
  • How to perform batch tasks in foreground or using the ISPF panels. For more information, see Performing Batch Tasks in Foreground, in the User Guide.
  • How to code SCL statements. For more information, see the SCL Reference Guide.
• Make sure that you understand how Autogen works. Autogen generates only those using elements that are in the same logical map as the target component. Certain Autogen Span options also generate using elements that are found in different Systems and Subsystems within the Environment and Stage of the logical map. The following topics explain the different Autogen options and how they affect processing:
  • Autogen Action Option
  • How the Autogen Action Option Affects Processing
  • How Autogen Span Options Work
  • Autogen and Autogen Span Processing Examples

Autogen Action Option

When specified on an Add, Update, or Generate action for a component element, the Autogen action option automatically generates using elements. A using element is an element that uses a component element. For example, if Autogen is specified for copybook COPYA, then the programs that use that copybook are known as using elements. Specifying Autogen for an element of Type Macro automatically generates the source elements that use the macro, which then generates the appropriate LNK elements.

Autogen is available in batch only for the Add, Update, and Generate actions and cannot be used in packages. CCIDs and comments from the original generated element are used. Autogen generates only those using elements that are found at the same inventory location as the target component or are found higher up the logical map. To generate using elements located across Systems or Subsystems, you can use the Autogen Span options. For more information about the Span options, see Autogen Spans Across Systems and Subsystems in the Administration Guide.

If you specify the Autogen option on any one of a group of statements, then all of those statements are resolved based on the current inventory contents before any statement is executed. Statements such as GENERATE ELEMENT * create actions based on the location and options of the Generate action. During processing, duplicate Generate actions are eliminated, and the NoSource option is enabled for all the Generate actions built by Autogen. 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.

Autogen improves processing by eliminating duplicate processing of components and reduces the work that is required of users, who no longer must use the Automated Configuration Manager Query facility (ACMQ) to create additional Generate actions for element components and then run another batch job to process them.

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

The following restrictions apply to Autogen:

• Autogen requires Global Type Sequencing so that the elements that use a component are generated after all of the components have been processed (for example, macros before source, source before load modules).
• Autogen only acts on components whose Types are listed in the Global Type Sequencing table. If the component's Type is not listed in the Global Type Sequencing table, the Autogen request is ignored.
• Your site must have purchased and activated the option CA Endevor Automated Configuration. You can use the Display Site panel to determine if this option is activated (ASCM=Y) at your site.
• Autogen cannot be specified on actions that are included in a package, because approvers must see the SCL statements that they are approving.
• Autogen and the bypass generate element (GENERATE ELEMENT=N) options are mutually exclusive.
• Autogen is a batch option. It cannot be specified on foreground requests.