Understanding the Relationships between Logical Systems
COPE supports multiple development environments in a single IMS Physical System. A development environment is called a Logical System or Lsys. Each Logical System is a separate virtual IMS system. In many instances there are only slight variations between resources in Logical Systems. To accommodate environments which are very similar, COPE Logical Systems can be set up using a parent/child type of relationship. When a resource is imported into a parent Lsys it becomes available to all child Lsys’s unless that same resource is already in the child Lsys.
The relationship between Logical Systems is defined when COPE is initially configured, by using sub option 1 (Setup) off the COPE ISPF Development System Menu as shown below.
Next select Option 1 (Define Logical Systems) on the screen shown below:
The screen shown below is then accessed. This screen shows an example defining 6 Logical Systems.
The following are the descriptions of the fields on the above screen:
- Project Name: The name of the project (1 to 8-character name for this COPE Environment)
- System Name: The Logical System (Lsys) name
- Prev System: The name of the Logical System this one is related to (parent/child relationship)
- Project Desc: The description of the project name defined above (1 to 40 characters)
In the above example, Lsys’s DBT1 and DBT6 do not contain any value in the ‘Prev System’ field, so all resources available in these two Lsys’s must be directly imported into them.
Lsys’s DBT2, DBT3 and DBT4 all have Lsys DBT1 in the ‘Prev System’ field. This means resources imported into DBT1 are also indirectly imported into Lsys’s DBT2, DBT3 and DBT4 unless they already have that same resource in them.
Lsys DBT5 has DBT4 in the ‘Prev System’ field. This means any resource directly or indirectly imported into DBT4 is also indirectly imported into DBT5 unless that same resource is already in DBT5. This also means any resource imported into DBT1 is also indirectly imported into DBT5 (due to parent/child relationship between DBT1 and DBT4) unless that resource is already in DBT5.