Skip to content

Combined Application Area Libraries

Using ERO Global Administration Options, you have two choices for defining the contents of release area libraries:

  • Each joined application can have its own set of area libraries defined by library type.

  • All joined applications can share the same set of area libraries defined by library type.

Area Libraries by Joined Application and Library Type

The ERO Option will allocate a separate set of area libraries by library type for each joined application if you include application as a DSNAME node in the release management dataset name pattern. Such a pattern would include these nodes, not necessarily in this order:

  • High Level Qualifier

  • Release Name

  • Release Area Name

  • Release Application Name

  • Release Library Type (must be the last in the pattern)

Release components are isolated by application throughout the release life cycle, from the starting subsystem area through the final system area. Separate area libraries by application prevent you from overlaying a component with another component having the same name and library type from another joined application.

Area Libraries by Library Type Only

Starting with ChangeMan ZMF 5.5, the ERO Option will allocate one set of area libraries by library type if you exclude application from the release management dataset name pattern. Such a pattern would include these nodes, not necessarily in this order:

  • High Level Qualifier

  • Release Name

  • Release Area Name

  • Release Library Type (must be the last in the pattern)

Release components from all joined applications are combined by library type throughout the release life cycle, from the starting subsystem area through the final system area. However, ERO retains the application identity of components in a Db2 table so that check-in, checkout and retrieve functions are performed by application according to the application authority rules.

Effects of Combined Application Area Libraries

The effects of combining joined applications in release area libraries include:

  • Fewer area libraries are allocated, which may save data center resources. The extent of resource savings depends on how many applications you join to an ERO release.

  • If you eliminate related applications in SYSLIB definitions, the number of libraries in build process JCL may be reduced. This can be important if your SYSLIB concatenation in build JCL approaches the IBM limit of 128 extents.

  • Build processes automatically share components across all applications joined to the release. In contrast, when you have separate application area libraries, you must specify related applications in SYSLIB definitions to share components between joined applications in build processing.

  • Component sharing between joined applications is automatically all-way. For example, Application A can use Application B components in build processing, and Application B can use Application A components. In contrast, if you have separate application area libraries, and if you specify Application B as a related application in a SYSLIB definition for Application A, build processing for Application A will use components from Application B, but Application B build will not automatically use components from Application A.