Tutorial: Mainframe Batch Database Tools (MBDT)

Takes you step by step through the process of migrating a mainframe-based DB2 table on the mainframe to a local SQL Server using Mainframe Batch Database Tools (MBDT).

Assumptions

This tutorial is written from the perspective that all of the following items are true. Specific instructions for setting up your environment to adhere to these assumptions is found in the Before you begin section that follows:

  • Windows File Explorer is set to show file names and extensions.
  • Windows User Account Control (UAC) is turned off.
  • You are running the latest version of Micro Focus Enterprise Developer, which has been installed on your local machine using default installation settings, and including the Rumba+ Desktop option.
  • For mainframe connectivity, you are using Rumba+ Desktop, which is configured to connect to your mainframe.
  • You have installed and can access a supported version of Microsoft SQL Server.
  • Enterprise Developer for Eclipse is started on your local machine using the default work area, and the appropriate Perspective and View are open..
  • Eclipse options are set to build projects automatically.
  • You have addressed all of the items in the Before you begin section below.

Before you begin

Before beginning, be sure you have addressed each of the following items:

Set Windows File Explorer options
These tutorials assume that your Windows File Explorer options are set to use the Details layout, and to show file name extensions. See your Windows documentation for more information.
Turn off Windows User Account Control (UAC)
Depending on the Windows UAC setting on your machine, HCOSS exhibits different behavior for some features. The differences in behavior are dependent on things such as whether or not you are logged in as a standard user or an administrator, whether or not you are a member of the Windows Administrators group, and how you start the HCOSS user interface. These tutorials assume that you have turned UAC off by setting it to Never notify. See your Windows documentation for details.
Start Enterprise Developer
Start Enterprise Developer using the default workspace, which is c:\users\username\workspace where username is your operating system login ID. If you need instructions to get Enterprise Developer started on your local machine, see To start Enterprise Developer.
Open the Team Developer Perspective and Application Explorer View in Eclipse
When you start Enterprise Developer for the first time, the Team Developer perspective starts automatically by default, and shows the Application Explorer view. If this is not the case, open the Team Developer perspective as follows:
  1. From the Eclipse IDE, click Open Perspective Open Perspective.
  2. On the Open Perspective dialog box, select Team Developer (default), and then click Open.

In addition, the Enterprise Development Projects system should be loaded in the Application Explorer view. To confirm this:

  • In the Application Explorer view, you should see the Enterprise Developer system. If the system is not shown, to load it:
    1. Right-click in the Application Explorer view, and then click Add System(s).
    2. In the Add System(s) dialog box, select ED System and click OK.
    3. Expand the top-level Enterprise Developer entry in the Application Explorer view.
    4. Right-click Enterprise Development Projects; then click Load Application.
  • Otherwise, expand the Enterprise Developer system. An entry titled Enterprise Development Projects should appear indicating that the system is loaded.
Set Eclipse to build automatically
By default, the Eclipse Build Automatically option is turned on, which means that Eclipse builds a project automatically each time a change is made. To ensure that this Build Automatically is turned on:
  1. From the Eclipse Main Menu, click Project.
  2. Do one of the following:
    • If the Build Automatically menu option has a check mark to its left, it is already turned on. No further action is required.
    • If the Build Automatically menu option does not have a check mark to its left, click the option to turn it on.

Sequence

To complete this tutorial, progress through these topics in the order presented here. The bottom of each topic provides Next topic and Previous topic navigational links to help you proceed in the proper sequence:

  1. Set Up the HCO_Test SQL Server Database
    Guides you through the steps required to create the HCO_Test SQL Server database, create a schema in the database where you can place your migrated DB2 tables, and create a connection to the database.
  2. Prepare Mainframe Data
    Provides instructions for using DB2 on the mainframe to unload mainframe data and execute the LOAD control statement.
  3. Build the ODBC XA Switch Module
    Guides you through the process of configuring your machine to build the ODBC XA switch module used in these tutorials, and then building the module.
  4. Set Up the JCL1 Project
    Provides step-by-step instructions to create the JCL1 Eclipse project and configure it to use with this tutorial.
  5. Set Up the DSNUTILS Enterprise Server Region
    Walks you through the steps required to create the JCL-enabled DSNUTILS enterprise server region.
  6. Download and Catalog DB2 Data
    Guides you through the steps required to copy the LOAD control statement from the mainframe to your Windows machine using Micro Focus Mainframe Access Drag and Drop, and to copy the unloaded DB2 data to your Windows machine using Micro Focus Mainframe Access command-line tools.
  7. Migrate the Database
    Provides step-by-step instructions to complete the migration of the DB2 database to your SQL Server database by using an Eclipse JCL project and Mainframe Batch Database tools.
Parent topic: Mainframe Tutorials
Related tasks
To start an Enterprise Developer command prompt as an administrator
To start Enterprise Developer
To start the ODBC Data Source Administrator