Libset Hierarchy Example

Recall that a Libset is uniquely identified by the Project and Group in the 3-part dataset name, <Project>.<Group>.<Type>; for example, the dataset CSD.DEVL.COBOL is in the Libset CSD.DEVL.

When defining a Libset structure, several considerations must be addressed. The first consideration is the number of IMS systems to be combined to form a COPE Psys. The second is the amount of code that is shared between applications.

For example, suppose that there are two systems that share no code or databases between the applications. For each application, at least two Libsets need to be defined (one for development and one for production).

The arrangement shown in the following figure could be used:

Systems without Common Code. Libset Example

In the above example, two test IMS systems are defined, named PAYSYS and INVSYS (COPE IMS system names can be up to 8 characters long). One system is associated with a Libset whose Project and Group name is PAY.DEVL, and the other is associated with Libset INV.DEVL.

Notice that the above is an example of two unconnected COPE hierarchies. Modules flow (are promoted) along the right-to-left arrows. Promotion copies modules (rather than moves them). There are no vertical arrows, and therefore no concatenations.