Additional ERO Functions
These functions are available with ERO and can be performed when necessary.
Detaching a Package from a Release
When you detach a package from a release, you sever all relationships to the release, its areas, and area libraries. You break relationships to components in area libraries for that release, and to components in area libraries which identify that release as a prior release.
Retrieving a Package
The retrieve package function removes all package components from the libraries for an area. You must remove package components from area libraries to:
-
Detach a package from a release
-
Check-in new versions of all package components from a different package
Retrieving from an Area
The retrieve area function removes components from area libraries. You must retrieve components from area libraries to:
-
Detach a package from a release
-
Check-in a new version of the component from a different package
-
Check-in a component by a person different from the person who last checked in the component
Area Promotion
Area promotion populates test environment libraries with components from ERO area libraries. Area demotion removes area components from test libraries.
ERO area promotion is built on standard ChangeMan ZMF services for package promotion. This makes area promotion similar to base ChangeMan ZMF package promotion in some ways and different in other ways. This then makes it possible, for example, for you to:
- Use the promotion sites, levels, and libraries that you have configured in application administration in the base product.
- Execute special functions like Db2 binds and CICS PHASEIN that you have enabled in promotion skeletons.
As a result, sites are able to design their areas to conform to their promotion environments, i.e. DEV area to one place, UNIT area to another, and so on. Within ERO promotion is on an application level and not a single package like base ZMF. A release package can't inadvertently be promoted to a promotion site/level defined to ERO with base ZMF promotion, as it can only be promoted to non ERO-defined promotion sites/levels.
ERO promotion uses the existing application promotion definitions as well as the libraries. They are assigned to different areas of the release and are part of the release life cycle.
Testing an Area
The test area function compares the contents of an area to the contents of packages attached to the release. Error conditions are displayed online.
As you consolidate package components in a release and as you work in packages to correct errors you find in release testing, you may create mismatches between the contents of areas and the contents of packages attached to the release. When you block a release, ERO automatically executes a test to detect mismatches between the final release area and contents of release packages. You can find these errors earlier in the release life cycle by manually executing the test area function against any release area.
Testing a Release
The test release function executes the test area function against the final area of a release. You cannot block a release until all discrepancies between the final area and packages attached to the release are resolved.
If automatic cleanup is enabled in the release definition, then automatic cleanup is executed in test release the same as it is in test area.
More Information