Skip to main content

SAP on DB2 Universal Database for OS/390 and z/OS: Multiple Components in One Database (MCOD)

An IBM Redbooks publication

Note: This is publication is now archived. For reference only.


Published on 19 February 2003

  1. .PDF (4.5 MB)

Share this page:   

ISBN-10: 0738429007
ISBN-13: 9780738429007
IBM Form #: SG24-6914-00

Authors: Mike Ebbers, Florence Dubois, Kellie Bohlsen, Tim Bohlsen, Bernd Kohler and Gert Ruland

    menu icon


    The Multiple Components in One Database (MCOD) feature of SAP enables a reduction in the number of DB2 systems that need to be installed and maintained. This significantly simplifies overall database administration and is considered one of the major DB2 competitive advantages.

    This IBM Redbooks publication will help systems administrators, database administrators, managers, and operation staff to plan, implement, and administer an SAP MCOD landscape with DB2 Universal Database (UDB) for OS/390 and z/OS as the database management system.

    We describe how to merge existing systems into a single DB2 subsystem. Two different methods are developed, each of them addressing different needs. For small-to-medium SAP systems where high availability is not a requirement, we explain how to use SAP tools. For large systems, where the down time needed by SAP standard procedures is not acceptable, we document a technique to merge SAP components without moving the data.

    We also provide a cloning procedure using the Control Center. We show how to clone one component out of an MCOD landscape. We address the backup and recovery implications in an MCOD environment, to help database administrators plan accordingly. We also describe how to set up and use the Computer Center Management System (CCMS) in an MCOD landscape.

    Table of Contents

    Chapter 1. MCOD in a DB2 UDB for OS/390 and z/OS environment

    Chapter 2. Planning for an MCOD landscape

    Chapter 3. MCOD installation and merge using SAP tools

    Chapter 4. Merging SAP components without moving data

    Chapter 5. Cloning one component out of an MCOD landscape

    Chapter 6. PPT recovery of one system in an MCOD landscape

    Chapter 7. Computer Center Management System (CCMS) and MCOD


    Others who read this also read