Performing Adoption › Preparing for Adoption › Determine Whether to Adopt All or Adopt Selected Objects › Example Where Many Objects Are Adopted in Separate Sessions

Example Where Many Objects Are Adopted in Separate Sessions

For large-scale adoptions, consider adopting the objects in multiple sessions. Some selectable objects must be adopted during the same session (or previous session); others have no dependencies.

The general rule is that subordinate objects cannot be adopted unless their parents share common ancestry. If you select parent objects for adoption in the same session as the dependent objects, the parent objects are processed first. Therefore, adoption in the same session is sufficient to meet the rule.

Use the following guidelines to group the model objects into multiple aggregate sets and plan the sequence of adoption. If you select aggregate object types in the following sequence, and select all occurrences of each type, you will avoid encountering problems due to a missing object on which a selected object depends.

The following is the recommended Adoption Sequence:

1. USER SUBJECT AREAs
2. ENTITY TYPEs
3. RELATIONSHIP MEMBERs
4. FOREIGN KEY ATTRIBUTEs
5. DATA TABLEs
6. DATABASEs
7. TABLESPACEs
8. WORK ATTRIBUTE SETs
9. BUSINESS SYSTEMs
10. COMMANDs
11. TEMPLATEs
12. EXIT STATEs
13. FUNCTIONs
14. PROCESSes
15. COMMON ACTION BLOCKs (BAA)
16. COMMON ACTION BLOCKs (BSD)
17. PROCEDUREs
18. DIALOG FLOWs
19. ONLINE LOAD MODULEs
20. WEB SERVICE DEFINITIONs
21. WINDOW LOAD MODULEs
22. CONFIGURATION INSTANCEs
23. CUSTOM PROXIES
24. OPERATIONS LIBRARY
25. z/OS LIBRARY
26. USER DEF OBJ CLASS
27. USER DEFINED MATRIX
28. All other Planning objects (no dependencies)

The following three graphics assume all occurrences of all aggregate object types numbered 1-7 are in an aggregate set adopted during session 1, 8-13 in session 2, and 14-21 in session 3.