Auditing a Release Area

Area audit evaluates relationships between different versions of the same component, and it evaluates relationships between components and other components that they include such as copybooks and statically linked load modules.

Area audit examines the components in libraries for a particular release area, as well as libraries for areas in the chain of next areas in the same release, libraries in areas of prior releases that will be installed sooner, and baseline libraries.

Running Audit Release Area

Right-click a release or a release area folder, then select ZDD Network → Audit release area from the popup menu.

The Audit Release Area dialog box displays.

Fields in Audit Release Area

The following table describes the fields on the Audit Release Area dialog box.

Field / Box	Description
Release area	Select a release area to be audited from the drop-down list.
Auto-resolve	Specify how you want audit to resolve out-of-sync conditions:
	None – Report out-of-sync conditions but to not resolve them.
	All – Audit submits build jobs for all like-source and 77like-load.
	Composite only – Audit submits build jobs that create like- load modules, including statically linked composite load modules.
	Subroutines only – Audit submits build jobs that create like-NCAL load modules.
Ignore higher areas	Type an option to specify whether higher areas in the same release are included when area audit is run for non-final areas.
	Available options may be restricted by release administration settings.
	No – Area audit includes higher areas in the same release. The area audit return code is updated.
	Yes – Area audit ignores higher areas in the same release. Areas in prior releases are processed normally. The area audit return code is not updated; audits run with this setting are for information only.
	Conditional – The behavior of area audit is determined by the structure of the current release.
	If the current release has only one starting area, then area audit runs as if the Ignore Higher Areas field is set to Yes.
	If there are multiple starting areas, area audit as if the Ignore Higher Areas field is set to No.
Include related applications	All related applications as well as the baselines belonging to applications attached to the release are to be included.
	Note: Area audit will run longer as the number of baselines included in the release is increased.
Auto-resolve preferred packages	Select this option to choose preferred packages to be used for new (to the release) components generated by the auto- resolve process.
	If you have previously selected preferred packages for this release, your previous selection will be used by default. You need only use this option if you want to view or change the preferred packages prior to submitting the audit.
Job card	Default values are displayed initially. If you change the values, they will be stored in your registry and used as the defaults in the future.
	Each time this dialog displays, the last character of the jobname is incremented alphabetically. If the \&SYSUID parameter in the Notify field is not overridden, the user ID is automatically substituted.