Skip to content

Rules for Checking Out Components

These rules and restrictions apply to the checkout component function:

  • You can check out a component from a baseline library or a promotion library. When you check out from a promotion library, you are assuming that the component in the promotion library will be installed by the time your package is ready to be installed.

  • You may be able to check out a component into a personal library. Administration Settings for Checkout Component Functions. If you check out to a personal library, the component is also copied to a package staging library.

  • After you check out a component, the status of the component in your package is CHECKOUT.

  • You can check out a component into your package if the component is already in your package in CHECKOUT status. You do not have to delete the component to do so.

  • Checkout can be executed online or in a batch job. Batch checkout releases your terminal while components are copied into staging or personal libraries and component history is built.

  • When you check out to a personal library or data set, ChangeMan ZMF verifies that the data set is cataloged and that you have at least UPDATE authority for the data set in your security system.

  • If checkout to a CA Panvalet or CA Librarian library is allowed, you must use batch checkout to target those proprietary library technologies.

  • When you check out a component that is already checked out to one or more active packages, every user who checked out the same component to an active package is notified with an MVS SEND message.

  • When you check out a component from either baseline or promotion, the vv.mm ISPF statistics in the staging library are set according to this formula, relative to the statistics in the origin library: vv=vv+1, mm=00.

  • When you check out a component that has an associated Component Activity File library type, the Component Activity File member with the same name is checked out into a package staging library, regardless of the whether you choose a staging or personal library as the target for the original component.

  • When you check out a component from a promotion library, if that component has an associated Component Activity File library type, the Component Activity File member is always copied from the 0-level baseline library.

Administration Settings for Checkout Component Functions

Your global and application administrators make settings in ChangeMan ZMF administration that control how the checkout component function works in your application. Ask your administrator if any of the following apply to your application.

  • Require use of the checkout function to add a component to your package if the component is in a baseline library. Prohibit stage from development, or require special security authorization to use stage from development, if the component is in baseline. (Application Administration Parameters: Checkout Enforcement Rule)

  • Restrict checkout of a component to one package at a time. (Application Administration Parameters: Allow Concurrent Checkout)

  • Allow checkout of components into personal libraries. Copies of components checked out to personal libraries are kept in package staging libraries. (Application Administration Parameters: Allow Checkout to Personal Lib).

Exit Programs for Checkout Component Functions

Your ChangeMan ZMF installer or administrator may implement exit programs to alter the behavior ChangeMan ZMF. Ask your administrator if any of the following apply to your application.

  • Add custom processes before and/or after checkout. (Exit program CMNEX019)

  • Bypass the Checkout Enforcement Rule for specified library types to permit stage from development when a component is in baseline. See Checkout Enforcement Rule in Administration Settings for Checkout Component Functions. (Exit program CMNEX030)

  • Restrict the library types displayed on the valid library selection list for checkout, stage, browse baseline, browse compressed listing, compare, scan, scratch/rename, and relink functions. This exit effectively disables these functions for the specified library types. (Exit program CMNEX035)