Removing DBDs and PSBs from IMS by using DDL

If the IMS system you are connected to supports DDL, you can remove databases (DBDs) or program views (PSBs) from an IMS system by using IMS™ Explorer to generate and run DDL DROP statements for the selected resources.

Before you begin

IMS Explorer for Development must be connected to an IMS database. See Connecting to an IMS database

The IMS system you are connecting to must support DDL. DDL is supported by IMS 14 and later systems that are configured to manage the application control blocks (ACBs) for databases and program views in the IMS catalog. For more information about enabling IMS support for DDL and the IMS management of ACBs, see IMS management of ACBs.

Procedure

To generate DDL DROP statements:

  1. In the Data Source Explorer view, right-click a connection node, schema (DBPCB), or table (segment) and click Generate DDL.
    Note: If you select a connection node, DDL is generated for the child catalog (PSB). If you select a table, DDL is generated for the parent schema.
    The Generate DDL wizard opens.
  2. In the Options page, select DROP statements.
  3. In the Objects page, select the model objects that you want to include in the DDL script.
    Program view
    Generates DDL DROP PROGRAMVIEW statements for the selected schemas.
    Important: This option will create a default PROGRAMVIEW name. In the Save and Run DDL page, select Open DDL file for editing and specify a valid PROGRAMVIEW name before you run the DDL on the server.
    Tables
    Generates DDL DROP DATABASE and DROP TABLE statements for the database (DBD) referenced by the selected schemas.
  4. In the Save and Run DDL page, select Open DDL file for editing and click Next > Finish. The DDL opens in an SQL editor, where you can modify and run the DDL script.

Results

When you run the DDL script, statements are submitted to IMS and results are shown in the SQL Results view.

After IMS receives the DDL, IMS drops the database resources automatically without requiring additional steps in IMS.




© Copyright IBM Corporation 2010, 2017.