Configuration Files Build Options

See Figure 1.

The very first build after installing a new release must be a full build to produce a complete set of configuration files. Furthermore, if a policy database is new, or the build output data set is empty, a full build is required. This means you need to issue a build with option 1 and Type = ALL. For all subsequent builds, option 1 and Type = MODIFIED can be used. Options 2 and 3 build only part of the configuration and are for special situations only.

You can enter one of the following build processes:

1 Build a complete enterprise

Builds all automation configuration files for a complete enterprise.

For the usual configuration file build without special needs it is recommended to use this option together with Type = ALL or Type = MODIFIED.

2 Build sysplex group or stand alone system

Allows the selection of a single sysplex group or a standalone system.

This build option performs a complete build of all objects linked to the selected sysplex or standalone system. For a large policy database, this option helps to reduce build time for small changes.

While this option only updates a single system or sysplex, deleted standalone systems and sysplexes still remain in the configuration files. For example, a deleted sysplex or standalone system is not removed from the ACF map AOFACFMP. So, you may wish to consider issuing a build with option 1 whenever a large number of parts have been deleted, to clean up unnecessary entries from the configuration files.

3 Build entry type or entry name

Allows you to specify an entry type and name to be rebuilt. Only the ACF fragments for that entry will be updated.

If for example, a timer object is modified and linked to another system, a build of this object with option 3 would only build that fragment and update the timestamp in the system include member, but not build the link changes for the system.

The same is true if an object is renamed. A build with option 3 of the new name would not add this new object to the system include member. Instead a build with option 2 is required.

For entry type System, this has the consequence that a selective build is rejected if there is also a link change pending.

However, if this option is used with entries of type Events, Triggers, Service Periods, Application, ApplicationGroup, System, or Group, a check is made as to whether data that affect the automation manager has been changed.

For certain entry types (for example, Service Periods, Events, Triggers) this option cannot be used because they do not have data included that needs to be built into an ACF fragment. In this case, building only the ACF fragment for the requested entry would mean that your previously generated AMC files would no longer be compatible with your current ACF files. To avoid this, a complete build (using build type MOD) will automatically be invoked. Before the build actually starts a confirmation panel is displayed explaining this situation, and allowing you to defer the build.

You will see the same behavior with automation tables if this option is used with entries of type APL or MVC. A check is made as to whether data has been changed that affect the NetView automation table. If so, a confirmation panel is displayed allowing you to defer or to start a complete build (using build option MOD).

If you enter a '?' in this field, SA z/OS displays a list of either entry types or a list of available entry names for the selected entry type, or both.

4 View build report

Allows you to view the build report available on the build output data set. It contains all messages from the In-progress panel of the last build.

5 Delete unused build output members

Allows you to delete members in the build output data set, that are not referenced by the actual configuration. Identified as unused are:

• Members identified as valid configuration files without a reference.
• Members with either no build statistics or which have not been identified, as valid configuration files.

When invoked, all unreferenced members are unlisted and the deletion has to be confirmed.

In the Build options section, you can enter values for the following fields:

Output Data Set

Use this field to specify where you want to store the build output. The data set must be an existing partitioned data set.

If the data set is not empty, but already contains a control file, the policy database name and the configuration name within the data set are compared with those of the requested build. If they do not match, and Type = MODIFIED is selected, a message is issued and the build is not started. If they do not match, and Type = ALL is selected, a warning panel is displayed which allows you to either start the build or cancel it.

Mode

Use this field to specify how to process the BUILD request:

ONLINE

Indicates that the BUILD should run in the foreground.

BATCH

Indicates that the BUILD should run in the background.

The default value is ONLINE (if this field is set to blank).

Type

Use this field to specify which entries are to be processed.

MODIFIED

Indicates that only those entries that have been changed since the last BUILD request should be processed.

Depending on the type of change, the affected objects are identified, and only the necessary parts of the configuration file are rebuilt.

For example:

• If a new timer is linked to one system, only the system include member for that system is rebuilt. For all other system include members only the header timestamps are updated, and the build of the AMC file, AT, MRT, and MPFLSTxx member is skipped, because timer data does not go to the automation manager configuration file, AT, MRT, or MPFLSTxx member.
• If a new application is linked to a Sysplex Application Group, the build determines which systems are linked to that sysplex, and the include members for those systems are rebuilt automatically, together with the AMC, AT, MRT, and MPFLSTxx member for that sysplex.
• If the AT/MRT Scope is changed, only the AT, MRT, and MPFLSTxx member are built.

ALL

Indicates that all entries are to be processed unconditionally, even if there has been no change to those entries since the last BUILD request.

If a build type of ALL is selected together with build option 2, only the configuration files that belong to the selected sysplex or standalone system are rebuilt.

The default value is MODIFIED (if this field is set to blank).

Configuration

This field allows you to select between alternative configurations:

NORMAL

Indicates that only those entries linked to the systems of the NORMAL configuration are processed by the current build.

ALTERNATE

Indicates that only those entries linked to the systems of the ALTERNATE configuration are processed by the current build. These systems must have been marked with a "+" in their MVS system name.

TERTIARY

Indicates that only those entries linked to the systems of the TERTIARY configuration are processed by the current build. These systems must have been marked with a suffix of "-" in their MVS system name.

NORMAL, ALTERNATE, and TERTIARY configurations must be built into different data sets. The default value is NORMAL (if this field is set to blanks).

In the Job statement information section you must enter a valid JOB statement for the batch job, if you specified that the BUILD request should run in BATCH mode.

The information that you specify here is saved in your ISPF profile data set and is used as the initial values the next time you issue the BUILD command.