CDO>  DEFINE PARTITION FINAL_RELEASE AUTOPURGE.        1
  CDO>  DEFINE PARTITION FIELDTEST_RELEASE               2
  cont>   PARENT_PARTITION IS FINAL_RELEASE AUTOPURGE.
  CDO>  DEFINE PARTITION SECOND_BASELEVEL
  cont>   PARENT_PARTITION IS FIELDTEST_RELEASE AUTOPURGE.
  CDO>  DEFINE PARTITION FIRST_BASELEVEL
  cont>   PARENT_PARTITION IS SECOND_BASELEVEL AUTOPURGE.
  CDO>  DEFINE PARTITION FRONT_END
  cont>   PARENT_PARTITION IS FIRST_BASELEVEL AUTOPURGE.
  CDO>  DEFINE PARTITION BACK_END                        3
  cont>   PARENT_PARTITION IS FIRST_BASELEVEL
  cont>   LOOKASIDE_PARTITION IS FRONT_END AUTOPURGE.
  CDO>  CHANGE PARTITION FRONT_END                       4
  cont>   LOOKASIDE_PARTITION IS BACK_END.

     .
     .
     .
  CDO>  DEFINE CONTEXT BILL_CONTEXT                      5
  cont>   BASE_PARTITION IS FRONT_END.
  CDO>  DEFINE CONTEXT BETSY_CONTEXT
  cont>   BASE_PARTITION IS BACK_END.
  CDO>  DEFINE CONTEXT QA_CONTEXT
  cont>   BASE_PARTITION IS FIELDTEST_RELEASE.

      In this example, successive DEFINE PARTITION commands create a
      partition hierarchy.

      1  The root partition is FINAL_RELEASE.

      2  Each successive partition in the hierarchy is the child of
         the previous partition.

      3  A partition hierarchy can include multiple children of a
         previous partition; LOOKASIDE_PARTITION makes the contents
         of FRONT_END visible to BACK_END.

      4  The CHANGE PARTITION command makes the contents of BACK_END
         visible to FRONT_END.

      5  The base partition, or lowest visible partition, is set for
         three different contexts.