A "Project" definition creates a CA‑PanAPT system record that associates a special group of libraries, called "Development Libraries" with a group of members defined in one or more Move (Change) Requests. Each Project has a unique name that can be cross‑referenced (or tied) to a specific Move Request. The Description of Move Request panel (accessed by the Move Request Maintenance function) has a Project field that can now be used to associate a specific Project Name. An individual Project Name can be associated with several Move Requests. Therefore, the modules that are associated with the Project's Move Requests are associated with the Project and are eligible to be processed by the CA‑PanAPT Development Facility.
Development Libraries are used to contain modules that are to be modified for a Project. There are two types of Development Libraries that can be defined by a Project:
Typically each developer will have their own private Development Work Libraries. It allows them to make changes without impacting other developers. When you check out a member and your Project is using Development Work Libraries, the members are checked out into the developer's work library. If your Project is not using Development Work Libraries, then members are checked out into the shared Development Test Libraries.
When the developer is done making changes and is ready to promote the changes so the other developers on the Project can share the changes, the developer will then check in the changes to the Development Test Libraries.
Note: In your CA‑PanAPT system, the names Development Work and Development Test might have been changed. As a result, some of your panels might appear different than those in this chapter; the names for the Development Work and Development Test levels appear there. The Development Work level is the lowest level defined to CA‑PanAPT, and the Development Test level is the next level up.
The Development Facility uses a Project definition to determine which Development Library data set is associated with a particular member from a particular Library Code being accessed by a particular user ID. The Project Administration functions described in this chapter can control the association of a physical data set with a Project library for a particular Project and Library Code.
When CA‑PanAPT determines which Development Work Library to use, it performs a search for the Development Work Libraries defined to the developer. Each work library has a lookup criteria that includes a Library Code, a Library Code type, an Access Method, and a Project Name. Wildcard characters (explained in detail later in this chapter) can be specified for any of the lookup criteria, except the Access Method (which also serves as the Access Method of the work data set). The first work library with lookup criteria that matches the actual Library Code, Library Code type, Library Code Development Options Access Method, and Project in use is selected.
Likewise when CA‑PanAPT determines which Development Test Library to use, it performs a search for the Development Test Libraries defined to the Project. Each Development Test Library has the same lookup criteria as a work library, except for a Project Name. The first Development Test Library with lookup criteria that matches the actual Library Code, Library Code type, and Library Code Development Options Access Method is selected.
Usually when CA‑PanAPT searches for a Development Work or Development Test Library, and one cannot be located, the function being performed is aborted. However, some functions, such as a Browse, perform without aborting.
|
Copyright © 2004 CA.
All rights reserved.
|
|