Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Alternate project definitions z/OS ISPF Software Configuration and Library Manager Guide and Reference SC19-3625-00 |
|
You can generate more than one project definition for a project. Each project definition defines the relationships between groups in the project database and the processes that you can perform on the data in the project database. Each project definition can define a different database structure, specify different control options, or support different languages for the project. Limit the use of alternate project definitions to satisfying a temporary need for a capability that the default (primary) project definition does not provide. You can use alternate project definitions successfully if they are never used to introduce or update members controlled under the primary project definition. Thus, you could use an alternate project definition to export data from the database definition or reference data in the primary database definition. However, if you use an alternate project definition to restrict an SCLM verification capability for data that is intended for the primary project definition, you can introduce integrity problems. You can have an unlimited number of alternate project definitions for a project. Figure 1 shows an alternate project definition with a primary non-key integration group (DEPT) defined for the project database structure shown in Figure 1. Figure 1. Sample Alternate Project
Definition
|
Copyright IBM Corporation 1990, 2014
|